CN117413476A - Method and apparatus for transmitting capability information of receiving STA in wireless LAN system - Google Patents

Abstract

The present disclosure proposes a method and apparatus for transmitting capability information of a receiving STA in a wireless LAN system. Specifically, the receiving STA generates capability information of the receiving STA and transmits it to the transmitting STA. The capability information of the receiving STA includes HE capability elements and EHT capability elements. The HE capability element includes a supported channel width setting field. The EHT capability element includes supported EHT-MCS and NSS settings fields. The supported EHT-MCS and NSS setting fields include first through fourth subfields. When the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

Description

Method and apparatus for transmitting capability information of receiving STA in wireless LAN system

Technical Field

The present specification relates to a technology of transmitting capability information of a receiving STA in a wireless LAN system, and more particularly, to a method and apparatus of transmitting information on the maximum number of spatial streams per MCS according to a channel and a frequency band for the receiving STA to operate.

Background

Wireless Local Area Networks (WLANs) have been improved in various ways. For example, the IEEE 802.11ax standard proposes an improved communication environment by using Orthogonal Frequency Division Multiple Access (OFDMA) and downlink multi-user multiple input multiple output (DL MU MIMO) techniques.

The present specification proposes technical features that can be used in new communication standards. For example, the new communication standard may be the very high throughput (EHT) standard currently in question. The EHT standard may use newly proposed increased bandwidth, enhanced PHY layer protocol data unit (PPDU) structure, enhanced sequences, hybrid automatic repeat request (HARQ) scheme, etc. The EHT standard may be referred to as the IEEE 802.11be standard.

In the new WLAN standard, an increased number of spatial streams may be used. In this case, in order to properly use an increased number of spatial streams, it may be necessary to improve signaling techniques in the WLAN system.

Disclosure of Invention

Technical problem

The present specification proposes a method and apparatus for transmitting capability information of a receiving STA in a wireless LAN system.

Technical proposal

Examples of the present specification propose a method of transmitting capability information of a receiving STA.

The present embodiment may be performed in a network environment supporting a next generation WLAN system (IEEE 802.11be or EHT WLAN system). The next generation wireless LAN system is a WLAN system enhanced from the 802.11ax system, and thus can satisfy backward compatibility with the 802.11ax system.

This embodiment is performed in a receiving STA, and the receiving STA may correspond to a non-access point (non-AP) STA. The transmitting STA may correspond to an Access Point (AP) STA.

This embodiment proposes a signaling method including in capability information the maximum number of spatial streams that can be transmitted or received for each MCS when a receiving STA is allocated a transmission bandwidth greater than a channel for its operation and operates in a 2.4GHz band.

A receiving Station (STA) generates capability information of the receiving STA.

The receiving STA transmits capability information of the receiving STA to the transmitting STA.

The capability information of the receiving STA includes a High Efficiency (HE) capability element and an Extremely High Throughput (EHT) capability element.

The HE capability element includes a supported channel width setting field. The EHT capability element includes supported EHT-MCS (modulation and coding scheme) and NSS (number of spatial streams) setting fields.

The supported EHT-MCS and NSS setting fields include first through fourth subfields. The first subfield may correspond to an EHT-MCS mapping (20 MHz only non-AP STA), the second subfield may correspond to an EHT-MCS mapping (BW < = 80MHz, except for 20MHz only non-AP STA), the third subfield may correspond to an EHT-MCS mapping (BW = 160 MHz) subfield, and the fourth subfield may correspond to an EHT-MCS mapping (BW = 320 MHz) subfield.

When the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in 5GHz and 6GHz bands, when the second to fourth bits (B1, B2, B3) of the supported channel width setting field are all set to 0, there is a first subfield, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz.

When the receiving STA operates in the 2.4GHz band, when the first bit (B0) of the supported channel width setting field is set to 0, there is a first subfield, and the first transmission bandwidth is 20MHz or 40MHz.

That is, even if the receiving STA is a non-AP STA operating only at 20MHz, it may be allocated to a first transmission bandwidth larger than a 20MHz channel for the receiving STA to operate. Specifically, even when the receiving STA operates in the 2.4GHz band, the receiving STA may transmit the maximum number of spatial streams that can be transmitted or received for each MCS to the transmitting STA through the first subfield.

When the receiving STA is a non-AP STA operating at 80MHz or more and is allocated to the second transmission bandwidth, the second subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, the second subfield exists when the second bit of the supported channel width setting field is set to 1, and the second transmission bandwidth may be 20MHz, 40MHz, or 80MHz.

When the receiving STA operates in the 2.4GHz band, the second subfield exists when the first bit of the supported channel width setting field is set to 1, and the second transmission bandwidth may be 20MHz or 40MHz.

That is, even if the receiving STA is a non-AP STA operating at 80MHz or more, it can be allocated to a second transmission bandwidth greater than the channel of 80MHz or more for the receiving STA to operate. Specifically, even when the receiving STA operates in the 2.4GHz band, the receiving STA may transmit the maximum number of spatial streams that can be transmitted or received for each MCS to the transmitting STA through the second subfield.

When the receiving STA is a non-AP STA operating at 20MHz or 80MHz and is allocated to the third transmission bandwidth, the second subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, the second subfield exists when the second bit of the supported channel width setting field is set to 1, and the third transmission bandwidth may be 160MHz or 320MHz.

That is, even if the receiving STA is a non-AP STA operating at 20MHz or 80MHz, it may be allocated to a third transmission bandwidth larger than the 20MHz or 80MHz channel for the receiving STA to operate, at which time the receiving STA may transmit the maximum number of spatial streams that may be transmitted or received for each MCS to the transmitting STA through the second subfield.

When the receiving STA is a non-AP STA operating at 160MHz or more and is allocated to the fourth transmission bandwidth, the third subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, when the third bit of the supported channel width setting field is set to 1, there is a third subfield, and the fourth transmission bandwidth may be 160MHz.

When the receiving STA is a non-AP STA operating at 160MHz and is allocated to a fifth transmission bandwidth, the third subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, when the third bit of the supported channel width setting field is set to 1, there is a third subfield, and the fifth transmission bandwidth may be 320MHz.

That is, even if the receiving STA is a non-AP STA operating at 160MHz, it may be allocated to a fifth transmission bandwidth larger than the 160MHz channel for the receiving STA to operate, at which time the receiving STA may transmit the maximum number of spatial streams that may be transmitted or received for each MCS to the transmitting STA through the third subfield.

When the receiving STA is a non-AP STA operating at 320MHz and is allocated to a sixth transmission bandwidth, the fourth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

The EHT capability element may also include a 320MHz subfield in 6GHz supported.

When the receiving STA operates in the 5GHz or 6GHz band, when the 320MHz subfield in the 6GHz supported is set to 1, there is a fourth subfield, and the sixth transmission bandwidth may be 320MHz.

Advantageous effects

According to the embodiments presented in the present specification, when a receiving STA is allocated a transmission bandwidth greater than a channel for its operation and operates in a 2.4GHz band, information on the maximum number of spatial streams that can be transmitted or received for each supportable MCS may be signaled by being included in capability information. This has the effect of improving overall throughput by applying the maximum number of spatial streams in more diverse situations.

Drawings

Fig. 1 shows an example of a transmitting device and/or a receiving device of the present specification.

Fig. 2 is a conceptual diagram illustrating a structure of a Wireless Local Area Network (WLAN).

Fig. 3 illustrates a general link establishment procedure.

Fig. 4 illustrates an example of a PPDU used in the IEEE standard.

Fig. 5 illustrates a layout of Resource Units (RUs) used in a 20MHz band.

Fig. 6 illustrates a layout of RU used in a band of 40 MHz.

Fig. 7 illustrates a layout of RU used in a band of 80 MHz.

Fig. 8 illustrates a structure of the HE-SIG-B field.

Fig. 9 illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme.

Fig. 10 illustrates an example of a PPDU used in the present specification.

Fig. 11 illustrates an example of a modified transmitting device and/or receiving device of the present specification.

Fig. 12 shows the format of the EHT capability element.

Fig. 13 shows the formats of the supported EHT-MCS and NSS setting fields.

Fig. 14 is a format of an EHT-MCS mapping (20 MHz only STA) subfield.

Fig. 15 is a format of EHT-MCS mapping (bw+.80 MHz, except for only 20MHz non-AP STAs), EHT-MCS mapping (bw=160 MHz), and EHT-MCS mapping (bw=320 MHz) subfields.

Fig. 16 is a flowchart illustrating the operation of the transmitting apparatus/device according to the present embodiment.

Fig. 17 is a flowchart illustrating the operation of the receiving apparatus/device according to the present embodiment.

Fig. 18 is a flowchart illustrating a procedure in which a transmitting STA receives capability information of a receiving STA according to the present embodiment.

Fig. 19 is a flowchart illustrating a procedure in which a receiving STA transmits capability information of the receiving STA to a transmitting STA according to the present embodiment.

Detailed Description

In the present specification, "a or B" may mean "a only", "B only", or "both a and B". In other words, in the present specification, "a or B" may be interpreted as "a and/or B". For example, in this specification, "A, B or C" may represent any combination of "a only", "B only", "C only" or "A, B, C".

Slash (/) or comma as used in this specification may mean "and/or". For example, "A/B" may represent "A and/or B". Thus, "a/B" may mean "a only", "B only" or "both a and B". For example, "A, B, C" may represent "A, B or C".

In the present specification, "at least one of a and B" may mean "a only", "B only", or "both a and B". In addition, in the present specification, the expression "at least one of a or B" or "at least one of a and/or B" may be interpreted as "at least one of a and B".

In addition, in the present specification, at least one of "A, B and C" may mean "a only", "B only", "C only", or "A, B and C in any combination. In addition, "at least one of A, B or C" or "A, B and/or at least one of C" may mean "at least one of A, B and C".

In addition, brackets used in this specification may represent "for example". Specifically, when indicated as "control information (EHT-signal)", it may represent that "EHT-signal" is proposed as an example of "control information". In other words, the "control information" of the present specification is not limited to the "EHT-signal", and the "EHT-signal" may be proposed as an example of the "control information". In addition, when indicated as "control information (i.e., EHT signal)", it may also mean that "EHT signal" is proposed as an example of "control information".

The technical features described separately in one drawing of the present specification may be implemented separately or may be implemented simultaneously.

The following examples of the present specification are applicable to various wireless communication systems. For example, the following examples of the present specification may be applied to a Wireless Local Area Network (WLAN) system. For example, the present description may be applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11ax standard. In addition, the present specification is also applicable to the newly proposed EHT standard or IEEE 802.11be standard. In addition, the examples of the present specification are also applicable to new WLAN standards enhanced from EHT standards or IEEE 802.11be standards. In addition, examples of the present specification are applicable to a mobile communication system. For example, it is applicable to a mobile communication system based on Long Term Evolution (LTE) relying on the 3 rd generation partnership project (3 GPP) standard and LTE-based evolution. In addition, examples of the present specification are applicable to a communication system based on the 5G NR standard of the 3GPP standard.

Hereinafter, in order to describe technical features of the present specification, technical features applicable to the present specification will be described.

Fig. 1 shows an example of a transmitting device and/or a receiving device of the present specification.

In the example of fig. 1, various technical features described below may be performed. Fig. 1 relates to at least one Station (STA). For example, STA 110 and STA 120 of the present description may also be referred to by various terms such as mobile terminals, wireless devices, wireless transmit/receive units (WTRUs), user Equipment (UEs), mobile Stations (MSs), mobile subscriber units, or simply users. STA 110 and STA 120 of the present description may also be referred to by various terms such as networks, base stations, node bs, access Points (APs), repeaters, routers, repeaters, and the like. The STA 110 and the STA 120 of the present description may also be referred to by various names such as a receiving device, a transmitting device, a receiving STA, a transmitting STA, a receiving apparatus, a transmitting apparatus, and the like.

For example, STA 110 and STA 120 may function as an AP or a non-AP. That is, STA 110 and STA 120 of the present description may function as an AP and/or a non-AP.

In addition to the IEEE 802.11 standard, STA 110 and STA 120 of the present description may together support various communication standards. For example, communication standards based on 3GPP standards (e.g., LTE-A, 5G NR standards) and the like may be supported. In addition, the STA of the present description may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, and the like. In addition, the STA of the present specification may support communication for various communication services such as voice call, video call, data communication, and self-driving (autonomous driving).

STA 110 and STA 120 of the present description may include a Medium Access Control (MAC) compliant with the IEEE 802.11 standard and a physical layer interface for a radio medium.

STA 110 and STA 120 will be described below with reference to sub-diagram (a) of fig. 1.

The first STA 110 may include a processor 111, a memory 112, and a transceiver 113. The illustrated processes, memories, and transceivers may be implemented separately as separate chips or at least two blocks/functions may be implemented in a single chip.

The transceiver 113 of the first STA performs a signal transmission/reception operation. Specifically, IEEE 802.11 packets (e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received.

For example, the first STA 110 may perform operations expected by the AP. For example, the processor 111 of the AP may receive signals through the transceiver 113, process Received (RX) signals, generate Transmit (TX) signals, and provide control over signal transmission. The memory 112 of the AP may store signals (e.g., RX signals) received through the transceiver 113 and may store signals (e.g., TX signals) to be transmitted through the transceiver.

For example, the second STA 120 may perform operations expected by a non-AP STA. For example, the non-AP transceiver 123 performs a signal transmission/reception operation. Specifically, IEEE 802.11 packets (e.g., IEEE 802.11a/b/g/n/ac/ax/be packets, etc.) may be transmitted/received.

For example, the processor 121 of the non-AP STA may receive signals through the transceiver 123, process RX signals, generate TX signals, and provide control over signal transmission. The memory 122 of the non-AP STA may store signals (e.g., RX signals) received through the transceiver 123 and may store signals (e.g., TX signals) to be transmitted through the transceiver.

For example, the operations of the apparatus indicated as an AP in the description described below may be performed in the first STA 110 or the second STA 120. For example, if the first STA 110 is an AP, the operation of the device indicated as an AP may be controlled by the processor 111 of the first STA 110, and the related signals may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the AP or TX/RX signals of the AP may be stored in the memory 112 of the first STA 110. In addition, if the second STA 120 is an AP, the operation of the device indicated as the AP may be controlled by the processor 121 of the second STA 120, and the related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the AP or TX/RX signals of the AP may be stored in the memory 122 of the second STA 120.

For example, in the description described below, the operation of a device indicated as a non-AP (or user STA) may be performed in the first STA 110 or the second STA 120. For example, if the second STA 120 is non-AP, the operation of the device indicated as non-AP may be controlled by the processor 121 of the second STA 120, and the related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the non-AP or the TX/RX signal of the non-AP may be stored in the memory 122 of the second STA 120. For example, if the first STA 110 is non-AP, the operation of the device indicated as non-AP may be controlled by the processor 111 of the first STA 110, and the related signals may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to operation of the non-AP or TX/RX signals of the non-AP may be stored in the memory 112 of the first STA 110.

In the description below, devices referred to as (transmitting/receiving) STA, first STA, second STA, STA 1, STA 2, AP, first AP, second AP, AP 1, AP 2, (transmitting/receiving) terminal, (transmitting/receiving) device, (transmitting/receiving) apparatus, network, and the like may mean STA 110 and STA 120 of fig. 1. For example, devices indicated (but not specifically numbered) (transmitting/receiving) STA, first STA, second STA, STA 1, STA 2, AP, first AP, second AP, AP 1, AP 2, (transmitting/receiving) terminal, (transmitting/receiving) device, (transmitting/receiving) apparatus, network, etc. may mean STA 110 and STA 120 of fig. 1. For example, in the following examples, operations of various STAs transmitting/receiving signals (e.g., PPDUs) may be performed in the transceivers 113 and 123 of fig. 1. In addition, in the following examples, operations of various STAs generating TX/RX signals or performing data processing and calculation in advance for the TX/RX signals may be performed in the processors 111 and 121 of fig. 1. Examples of operations for generating TX/RX signals or performing data processing and computation in advance may include, for example: 1) An operation of determining/obtaining/configuring/calculating/decoding/encoding bit information of a subfield (SIG, STF, LTF, data) included in the PPDU; 2) An operation of determining/configuring/obtaining time resources or frequency resources (e.g., subcarrier resources) for a subfield (SIG, STF, LTF, data) included in the PPDU, etc.; 3) An operation of determining/configuring/obtaining a specific sequence (e.g., pilot sequence, STF/LTF sequence, additional sequence applied to SIG) for a subfield (SIG, STF, LTF, data) field included in the PPDU, etc.; 4) Power control operation and/or power save operation applied to the STA; and 5) operations related to determination/acquisition/configuration/decoding/encoding of an ACK signal, and the like. In addition, in the following examples, various information (e.g., information related to fields/subfields/control fields/parameters/power, etc.) used by various STAs to determine/obtain/configure/calculate/decode TX/RX signals may be stored in the memories 112 and 122 of fig. 1.

The foregoing apparatus/STA of sub-graph (a) of fig. 1 may be modified as shown in sub-graph (b) of fig. 1. Hereinafter, STA 110 and STA 120 of the present specification will be described based on sub-diagram (b) of fig. 1.

For example, transceivers 113 and 123 shown in sub-graph (b) of fig. 1 may perform the same functions as the aforementioned transceivers shown in sub-graph (a) of fig. 1. For example, the processing chips 114 and 124 shown in sub-graph (b) of fig. 1 may include processors 111 and 121 and memories 112 and 122. The processors 111 and 121 and memories 112 and 122 shown in sub-graph (b) of fig. 1 may perform the same functions as the aforementioned processors 111 and 121 and memories 112 and 122 shown in sub-graph (a) of fig. 1.

A mobile terminal, wireless device, wireless transmit/receive unit (WTRU), user Equipment (UE), mobile Station (MS), mobile subscriber unit, user STA, network, base station, node B, access Point (AP), repeater, router, repeater, receive unit, transmit unit, receive STA, transmit STA, receive device, transmit device, receive apparatus, and/or transmit apparatus described below may mean STAs 110 and 120 shown in sub-graph (a)/(B) of fig. 1, or may mean processing chips 114 and 124 shown in sub-graph (B) of fig. 1. That is, technical features of the present specification may be performed in STAs 110 and 120 shown in sub-graph (a)/(b) of fig. 1, or transceivers 113 and 123 shown in sub-graph (a)/(b) of fig. 1 may be performed only in processing chips 114 and 124 shown in sub-graph (b) of fig. 1. For example, the technical feature of the transmitting STA transmitting the control signal may be understood as the technical feature of transmitting the control signal generated in the processors 111 and 121 illustrated in the sub-diagram (a)/(b) of fig. 1 through the transceiver 113 illustrated in the sub-diagram (a)/(b) of fig. 1. Alternatively, the technical feature of the transmitting STA transmitting the control signal may be understood as the technical feature of generating the control signal to be transmitted to the transceivers 113 and 123 in the processing chips 114 and 124 shown in the sub-graph (b) of fig. 1.

For example, the technical feature of the receiving STA receiving the control signal may be understood as the technical feature of receiving the control signal through the transceivers 113 and 123 shown in the sub-graph (a) of fig. 1. Alternatively, the technical features of the receiving STA to receive the control signal may be understood as the technical features of obtaining the control signal received in the transceivers 113 and 123 shown in the sub-graph (a) of fig. 1 through the processors 111 and 121 shown in the sub-graph (a) of fig. 1. Alternatively, the technical features of the receiving STA to receive the control signal may be understood as the technical features of the receiving STA to obtain the control signals received in the transceivers 113 and 123 shown in the sub-graph (b) of fig. 1 through the processing chips 114 and 124 shown in the sub-graph (b) of fig. 1.

Referring to sub-graph (b) of fig. 1, software codes 115 and 125 may be included in memories 112 and 122. The software codes 115 and 125 may include instructions for controlling the operation of the processors 111 and 121. Software codes 115 and 125 may be included as various programming languages.

The processors 111 and 121 or the processing chips 114 and 124 of fig. 1 may include Application Specific Integrated Circuits (ASICs), other chipsets, logic circuits, and/or data processing devices. The processor may be an Application Processor (AP). For example, processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may include at least one of the following: a Digital Signal Processor (DSP), a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modulator and demodulator (modem). For example, processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may be implemented by Manufactured snapdagantm processor family, consisting ofEXYNOSTM processor series manufactured by +.>Processor series manufactured by ∈>HELIOTM processor series manufactured by +.>The ATOMTM processor family is manufactured or processors enhanced from these processors.

In the present specification, the uplink may mean a link for communication from a non-AP STA to an SP STA, and an uplink PPDU/packet/signal or the like may be transmitted through the uplink. In addition, in the present specification, the downlink may mean a link for communication from an AP STA to a non-AP STA, and a downlink PPDU/packet/signal or the like may be transmitted through the downlink.

Fig. 2 is a conceptual diagram illustrating a structure of a Wireless Local Area Network (WLAN).

The upper part of fig. 2 shows the structure of an infrastructure Basic Service Set (BSS) of Institute of Electrical and Electronics Engineers (IEEE) 802.11.

Referring to the upper part of fig. 2, the wireless LAN system may include one or more infrastructure BSSs 200 and 205 (hereinafter, referred to as BSSs). BSSs 200 and 205, which are sets of an AP and an STA (e.g., an Access Point (AP) 225 and a station (STA 1) 200-1) that are successfully synchronized to communicate with each other, are not concepts indicating a specific area. BSS205 may include one or more STAs 205-1 and 205-2 that may join an AP 230.

The BSS may include at least one STA, an AP providing a distributed service, and a Distributed System (DS) 210 connecting the plurality of APs.

The distributed system 210 may implement an Extended Service Set (ESS) 240 extended by connecting the plurality of BSSs 200 and 205. ESS240 may be used as a term indicating a network configured by connecting one or more APs 225 or 230 via distributed system 210. The APs included in one ESS240 may have the same Service Set Identification (SSID).

Portal 220 may serve as a bridge connecting a wireless LAN network (IEEE 802.11) and another network (e.g., 802. X).

In the BSS shown in the upper part of fig. 2, a network between the APs 225 and 230 and the STAs 200-1, 205-1, and 205-2 may be implemented. However, the network is configured to perform communication between STAs even without the APs 225 and 230. A network that performs communication by configuring a network between STAs even without the APs 225 and 230 is defined as an ad hoc network or an Independent Basic Service Set (IBSS).

The lower part of fig. 2 illustrates a conceptual diagram illustrating an IBSS.

Referring to the lower part of fig. 2, the IBSS is a BSS operating under the ad hoc pattern. Since the IBSS does not include an Access Point (AP), there is no centralized management entity that performs management functions in the center. That is, in an IBSS, the STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In an IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 may be comprised of removable STAs and are not allowed to access the DS to form a self-contained network.

Fig. 3 illustrates a general link establishment procedure.

In S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order to access the network, the STA needs to discover the participating network. The STA needs to identify a compatible network before joining a wireless network, and the process of identifying a network existing in a specific area is called scanning. The scanning method comprises active scanning and passive scanning.

Fig. 3 illustrates network discovery operations including active scanning processing. In the active scanning, the STA performing the scanning transmits a probe request frame and waits for a response to the probe request frame in order to identify which AP exists around while moving to a channel. The responder transmits a probe response frame to the STA that has transmitted the probe request frame as a response to the probe request frame. Here, the responder may be an STA transmitting the last beacon frame in the BSS of the channel being scanned. In the BSS, the AP is a responder since the AP transmits a beacon frame. In IBSS, the responders are not stationary because STAs in the IBSS send beacon frames in turn. For example, when the STA transmits a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA may store BSS-related information included in the received probe response frame, may move to the next channel (e.g., channel 2), and may perform scanning by the same method (e.g., transmit a probe request and receive a probe response via channel 2).

Although not shown in fig. 3, scanning may be performed by a passive scanning method. In passive scanning, a STA performing scanning may wait for a beacon frame while moving to a channel. The beacon frame is one of management frames in IEEE 802.11, and is periodically transmitted to indicate the presence of a wireless network and enable STAs performing scanning to find and join the wireless network. In a BSS, an AP is configured to periodically transmit a beacon frame. In an IBSS, STAs in the IBSS transmit beacon frames in turn. Upon receiving the beacon frame, the STA performing scanning stores information about BSSs included in the beacon frame and records beacon frame information in respective channels while moving to another channel. The STA that receives the beacon frame may store BSS-related information included in the received beacon frame, may move to the next channel, and may perform scanning in the next channel by the same method.

After discovering the network, the STA may perform authentication processing in S320. This authentication process may be referred to as a first authentication process to be clearly distinguished from the security establishment operation in S340 that follows. The authentication process in S320 may include a process in which the STA transmits an authentication request frame to the AP and the AP transmits an authentication response frame to the STA in response. The authentication frame for authentication request/response is a management frame.

The authentication frame may include information about an authentication algorithm number, an authentication transaction sequence number, a status code, challenge text, a Robust Secure Network (RSN), and a limited loop group.

The STA may transmit an authentication request frame to the AP. The AP may determine whether to allow authentication of the STA based on information included in the received authentication request frame. The AP may provide the authentication processing result to the STA via an authentication response frame.

When the STA is successfully authenticated, the STA may perform association processing in S330. The association processing includes processing in which the STA transmits an association request frame to the AP and the AP transmits an association response frame to the STA in response. For example, the association request frame may include information about various capabilities, beacon listening intervals, service Set Identifiers (SSID), supported rates, supported channels, RSNs, mobile domains, supported operation categories, traffic Indication Map (TIM) broadcast requests, and interworking service capabilities. For example, the association response frame may include information about various capabilities, status codes, association IDs (AID), supported rates, enhanced Distributed Channel Access (EDCA) parameter sets, received Channel Power Indicator (RCPI), received signal-to-noise indicator (RSNI), mobility domain, time out interval (association recovery time), overlapping BSS scan parameters, TIM broadcast response, and QoS map.

In S340, the STA may perform security establishment processing. The security establishment process in S340 may include a process of establishing a private key through a four-way handshake (e.g., through an Extensible Authentication Protocol (EAPOL) frame via a LAN).

Fig. 4 illustrates an example of a PPDU used in the IEEE standard.

As shown, various types of PHY Protocol Data Units (PPDUs) are used in the IEEE a/g/n/ac standard. Ext> specificallyext>,ext> theext> LTFext> andext> theext> STFext> includeext> trainingext> signalsext>,ext> SIGext> -ext> aext> andext> SIGext> -ext> bext> includeext> controlext> informationext> forext> aext> receivingext> staext>,ext> andext> aext> dataext> fieldext> includesext> userext> dataext> correspondingext> toext> aext> psduext> (ext> macext> pduext> /ext> aggregateext> macext> pduext>)ext>.ext>

Fig. 4 also shows an example of a HE PPDU according to IEEE 802.11 ax. The HE PPDU according to fig. 4 is an exemplary PPDU for a plurality of users. HE-SIG-B may be included only in PPDUs for multiple users, and HE-SIG-B may be omitted in PPDUs for a single user.

As illustrated in fig. 4, the HE-PPDU for a plurality of users (MUs) may include a legacy short training field (L-STF), a legacy long training field (L-LTF), a legacy signal (L-SIG), a high efficiency signal a (HE-SIG a), a high efficiency signal B (HE-SIG B), a high efficiency short training field (HE-STF), a high efficiency long training field (HE-LTF), a data field (alternatively, a MAC payload), and a Packet Extension (PE) field. The various fields may be transmitted within the time period shown (i.e., 4 mus or 8 mus).

Hereinafter, a Resource Unit (RU) for PPDU is described. An RU may include a plurality of subcarriers (or tones). The RU may be used to transmit signals to a plurality of STAs according to OFDMA. In addition, an RU may also be defined to transmit a signal to one STA. RU may be used for STF, LTF, data fields, etc.

Fig. 5 illustrates a layout of Resource Units (RUs) used in a 20MHz band.

As illustrated in fig. 5, resource Units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to form some fields of the HE-PPDU. For example, resources may be allocated for HE-STF, HE-LTF, and data fields in the illustrated RUs.

As illustrated in the uppermost part of fig. 5, 26 units (i.e., units corresponding to 26 tones) may be arranged. Six tones may be used for guard bands in the leftmost band of the 20MHz band, and five tones may be used for guard bands in the rightmost band of the 20MHz band. Further, seven DC tones may be inserted in the center frequency band (i.e., DC frequency band), and 26 units corresponding to 13 tones on each of the left and right sides of the DC frequency band may be arranged. Other frequency bands may be allocated 26, 52, and 106 units. The receiving STA (i.e., user) may be assigned various units.

The layout of the RU in fig. 5 may be used not only for Multiple Users (MUs) but also for a Single User (SU), in which case one 242 unit may be used and three DC tones may be inserted, as shown in the lowermost part of fig. 5.

Although fig. 5 proposes RUs having various sizes, i.e., 26-RU, 52-RU, 106-RU, and 242-RU, RU of a specific size may be expanded or added. Therefore, the present embodiment is not limited to each RU of a specific size (i.e., the number of corresponding tones).

Fig. 6 illustrates a layout of RU used in a band of 40 MHz.

Similar to fig. 5 using RUs of various sizes, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. may be used in the example of fig. 6. Further, five DC tones may be inserted in the center frequency, 12 tones may be used for guard bands in the leftmost band of the 40MHz band, and 11 tones may be used for guard bands in the rightmost band of the 40MHz band.

As shown in fig. 6, 484-RU may be used when the layout of RU is for a single user. The specific number of RUs may vary similarly to fig. 5.

Fig. 7 illustrates a layout of RU used in a band of 80 MHz.

Similar to fig. 5 and 6 using RUs of various sizes, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. may be used in the example of fig. 7. Further, seven DC tones may be inserted in the center frequency, 12 tones may be used for guard bands in the leftmost band of the 80MHz band, and 11 tones may be used for guard bands in the rightmost band of the 80MHz band. In addition, 26-RUs corresponding to 13 tones on each of the left and right sides of the DC band may be used.

As shown in fig. 7, a 996-RU may be used when the layout of the RU is for a single user, in which case five DC tones may be inserted.

RU described in this specification may be used in Uplink (UL) communication and Downlink (DL) communication. For example, when performing UL-MU communication requested by a trigger frame, a transmitting STA (e.g., AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA through the trigger frame and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. Thereafter, the first STA may transmit a first trigger-based PPDU based on the first RU, and the second STA may transmit a second trigger-based PPDU based on the second RU. The first/second trigger-based PPDUs are transmitted to the AP at the same (or overlapping) time periods.

For example, when configuring a DL MU PPDU, a transmitting STA (e.g., AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. That is, a transmitting STA (e.g., AP) may transmit HE-STF, HE-LTF, and data fields for a first STA through a first RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and data fields for a second STA through a second RU.

Information about the layout of the RU may be signaled through the HE-SIG-B.

Fig. 8 illustrates a structure of the HE-SIG-B field.

As shown, the HE-SIG-B field 810 includes a public field 820 and a user-specific field 830. The common field 820 may include information commonly applied to all users (i.e., user STAs) receiving SIG-B. The user-specific field 830 may be referred to as a user-specific control field. When SIG-B is transmitted to multiple users, the user-specific field 830 may be applied to only any one of the multiple users.

As shown in fig. 8, the common field 820 and the user-specific field 830 may be encoded separately.

The common field 820 may include RU allocation information of N x 8 bits. For example, RU allocation information may include information regarding the location of an RU. For example, when a 20MHz channel is used as shown in fig. 5, RU allocation information may include information about a specific frequency band in which a specific RU (26-RU/52-RU/106-RU) is arranged.

An example of the case where RU allocation information consists of 8 bits is as follows.

TABLE 1

As shown in the example of fig. 5, up to nine 26-RUs may be allocated to a 20MHz channel. When RU allocation information of the common field 820 is set to "00000000" as shown in table 1, nine 26-RUs may be allocated to a corresponding channel (i.e., 20 MHz). In addition, when RU allocation information of the common field 820 is set to "00000001" as shown in table 1, seven 26-RUs and one 52-RU are arranged in the corresponding channel. That is, in the example of FIG. 5, 52-RUs may be allocated to the far right side and seven 26-RUs may be allocated to the left side thereof.

The example of table 1 shows only some RU locations where RU allocation information can be displayed.

For example, RU allocation information may include the following examples of table 2.

TABLE 2

"01000y2y1y0" refers to an example in which 106-RUs are allocated to the leftmost side of a 20MHz channel, and five 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (e.g., user STAs) may be allocated to the 106-RU based on the MU-MIMO scheme. Specifically, up to 8 STAs (e.g., user STAs) may be allocated to the 106-RU, and the number of STAs (e.g., user STAs) allocated to the 106-RU is determined based on the 3-bit information (y 2y1y 0). For example, when 3-bit information (y 2y1y 0) is set to N, the number of STAs (e.g., user STAs) allocated to 106-RU based on the MU-MIMO scheme may be n+1.

In general, a plurality of STAs (e.g., user STAs) different from each other may be allocated to a plurality of RUs. However, a plurality of STAs (e.g., user STAs) may be allocated to one or more RUs having at least a specific size (e.g., 106 subcarriers) based on the MU-MIMO scheme.

As shown in fig. 8, the user-specific field 830 may include a plurality of user fields. As described above, the number of STAs (e.g., user STAs) allocated to a specific channel may be determined based on RU allocation information of the common field 820. For example, when RU allocation information of the common field 820 is "00000000", one user STA may be allocated to each of nine 26-RUs (e.g., nine user STAs may be allocated). That is, up to 9 user STAs may be allocated to a specific channel through the OFDMA scheme. In other words, up to 9 user STAs may be allocated to a specific channel through a non-MU-MIMO scheme.

For example, when RU allocation is set to "01000y2y1y0", a plurality of STAs may be allocated to 106-RU disposed at the leftmost side through the MU-MIMO scheme, and five user STAs may be allocated to five 26-RU disposed at the right side thereof through the non-MU MIMO scheme. This is illustrated by the example of fig. 9.

Fig. 9 illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme.

For example, when RU allocation is set to "01000010" as shown in fig. 9, 106-RUs may be allocated to the leftmost side of a specific channel, and five 26-RUs may be allocated to the right side thereof. In addition, three user STAs may be allocated to the 106-RU through the MU-MIMO scheme. As a result, since eight user STAs are allocated, the user-specific field 830 of the HE-SIG-B may include eight user fields.

The eight user fields may be represented in the order shown in fig. 9. In addition, as shown in fig. 8, two user fields may be implemented using one user block field.

The user fields shown in fig. 8 and 9 may be configured based on two formats. That is, user fields related to MU-MIMO schemes may be configured in a first format and user fields related to non-MIMO schemes may be configured in a second format. Referring to the example of fig. 9, user fields 1 through 3 may be based on a first format, and user fields 4 through 8 may be based on a second format. The first format or the second format may include bit information of the same length (e.g., 21 bits).

The individual user fields may be of the same size (e.g., 21 bits). For example, the user field of the first format (first MU-MIMO scheme) may be configured as follows.

For example, the first bit (i.e., B0-B10) in the user field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of the user STA allocated the corresponding user field. In addition, the second bit (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to spatial configuration.

In addition, the third bit (i.e., B15-18) in the user field (i.e., 21 bits) may include Modulation and Coding Scheme (MCS) information. The MCS information may be applied to a data field in a PPDU including the corresponding SIG-B.

MCS, MCS information, MCS index, MCS field, etc. used in the present specification may be indicated by an index value. For example, MCS information may be indicated by index 0 to index 11. The MCS information may include information about constellation modulation types (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information about coding rates (e.g., 1/2, 2/3, 3/4, 5/6e, etc.). Information about a channel coding type (e.g., LCC or LDPC) may not be included in the MCS information.

In addition, the fourth bit (i.e., B19) in the user field (i.e., 21 bits) may be a reserved field.

In addition, the fifth bit (i.e., B20) in the user field (i.e., 21 bits) may include information about a coding type (e.g., BCC or LDPC). That is, the fifth bit (i.e., B20) may include information about a type of channel coding (e.g., BCC or LDPC) applied to a data field in a PPDU including the corresponding SIG-B.

The above examples relate to the user field of the first format (format of MU-MIMO scheme). Examples of the user field of the second format (a format other than MU-MIMO scheme) are as follows.

The first bit (e.g., B0-B10) in the user field of the second format may include identification information of the user STA. In addition, a second bit (e.g., B11-B13) in the user field of the second format may include information about the number of spatial streams applied to the corresponding RU. In addition, a third bit (e.g., B14) in the user field of the second format may include information regarding whether to apply beamforming steering matrices. The fourth bit (e.g., B15-B18) in the user field of the second format may include Modulation and Coding Scheme (MCS) information. In addition, a fifth bit (e.g., B19) in the user field of the second format may include information about whether Dual Carrier Modulation (DCM) is applied. In addition, the sixth bit (i.e., B20) in the user field of the second format may include information about a coding type (e.g., BCC or LDPC).

Hereinafter, PPDUs transmitted/received in STAs of the present specification will be described.

Fig. 10 illustrates an example of a PPDU used in the present specification.

The PPDU of fig. 10 may be referred to by various terms such as an EHT PPDU, a TX PPDU, an RX PPDU, a first type or an nth type PPDU, etc. For example, in the present specification, a PPDU or an EHT PPDU may be referred to by various terms such as TX PPDU, RX PPDU, first type or nth type PPDU, and the like. In addition, the EHT PPDU may be used in an EHT system and/or a new WLAN system enhanced from the EHT system.

The PPDU of fig. 10 may indicate all or part of a PPDU type used in the EHT system. For example, the example of fig. 10 may be used for both Single User (SU) and multi-user (MU) modes. In other words, the PPDU of fig. 10 may be a PPDU for one receiving STA or a plurality of receiving STAs. When the PPDU of fig. 10 is used in a Trigger (TB) -based mode, the EHT-SIG of fig. 10 may be omitted. In other words, an STA that has received a trigger frame for an uplink MU (UL-MU) may transmit a PPDU omitting the EHT-SIG in the example of fig. 10.

In fig. 10, L-STF to EHT-LTF may be referred to as a preamble or a physical preamble, and may be generated/transmitted/received/obtained/decoded in a physical layer.

The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields of FIG. 10 may be determined to be 312.5kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF, and data fields may be determined to be 78.125kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG fields can be expressed in units of 312.5kHz, and the tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and data fields can be expressed in units of 78.125kHz.

In the PPDU of fig. 10, the L-LTF and the L-STF may be the same as those in the conventional field.

The L-SIG field of fig. 10 may include bit information of, for example, 24 bits. For example, the 24-bit information may include a rate field of 4 bits, a reserved bit of 1 bit, a length field of 12 bits, a parity bit of 1 bit, and a tail bit of 6 bits. For example, a length field of 12 bits may include information related to the length or duration of the PPDU. For example, a length field of 12 bits may be determined based on the type of PPDU. For example, when the PPDU is a non-HT, VHT PPDU or EHT PPDU, the value of the length field may be determined as a multiple of 3. For example, when the PPDU is a HE PPDU, the value of the length field may be determined as "multiple of 3" +1 or "multiple of 3" +2. In other words, for a non-HT, VHT PPDI, or EHT PPDU, the value of the length field may be determined as a multiple of 3, and for an HE PPDU, the value of the length field may be determined as a "multiple of 3" +1 or a "multiple of 3" +2.

For example, the transmitting STA may apply BCC encoding based on a 1/2 coding rate to 24 bits of information of the L-SIG field. Thereafter, the transmitting STA may obtain 48 bits of BCC coding bits. BPSK modulation may be applied to the 48-bit coded bits, thereby generating 48 BPSK symbols. The transmitting STA may map 48 BPSK symbols to positions other than pilot subcarriers { subcarrier index-21, -7, +7, +21} and DC subcarrier { subcarrier index 0 }. As a result, 48 BPSK symbols can be mapped to subcarrier indexes-26 to-22, -20 to-8, -6 to-1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map signals of { -1, -1,1} to subcarrier indexes { -28, -27, +27, +28}. The aforementioned signals may be used for channel estimation in the frequency domain corresponding to { -28, -27, +27, +28}.

The transmitting STA may generate a RL-SIG generated in the same manner as the L-SIG. BPSK modulation may be applied to the RL-SIG. Based on the presence of the RL-SIG, the receiving STA may know that the RX PPDU is a HE PPDU or an EHT PPDU.

A common SIG (U-SIG) may be inserted after the RL-SIG of fig. 10. The U-SIG may be referred to in various terms such as a first SIG field, a first SIG, a first-type SIG, a control signal field, a first (type) control signal, and so forth.

The U-SIG may include N bits of information and may include information for identifying the type of the EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4 μs. Each symbol of the U-SIG may be used to transmit 26 bits of information. For example, each symbol of the U-SIG may be transmitted/received based on 52 data tones and 4 pilot tones.

With the U-SIG (or U-SIG field), for example, a-bit information (e.g., 52 uncoded bits) may be transmitted. The first symbol of the U-SIG may transmit the first X bits of information (e.g., 26 uncoded bits) of the a-bit information, and the second symbol of the U-SIG may transmit the remaining Y bits of information (e.g., 26 uncoded bits) of the a-bit information. For example, the transmitting STA may obtain 26 uncompiled bits included in each U-SIG symbol. The transmitting STA may perform convolutional encoding (i.e., BCC encoding) based on a rate of r=1/2 to generate 52 coded bits, and may perform interleaving on the 52 coded bits. The transmitting STA may perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols to be allocated to each U-SIG symbol. In addition to DC index 0, one U-SIG symbol may be transmitted based on 65 tones (subcarriers) from subcarrier index-28 to subcarrier index +28. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on remaining tones (subcarriers) other than pilot tones (i.e., tones-21, -7, +7, +21).

For example, the a-bit information (e.g., 52 uncompiled bits) generated by the U-SIG may include a CRC field (e.g., a field of 4 bits in length) and a tail field (e.g., a field of 6 bits in length). The CRC field and the tail field may be transmitted over a second symbol of a U-SIG. The CRC field may be generated based on 26 bits of the first symbol allocated to the U-SIG and the remaining 16 bits of the second symbol other than the CRC/tail field, and may be generated based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate a trellis (trellis) of the convolutional decoder, and may be set to, for example, "000000".

The a-bit information (e.g., 52 uncompiled bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, the version independent bits may have a fixed or variable size. For example, version-independent bits may be allocated to only the first symbol of the U-SIG, or version-independent bits may be allocated to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and version-dependent bits may be referred to in various terms such as first control bits, second control bits, and the like.

For example, the version independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the TX/RX PPDU. For example, a first value of a 3-bit PHY version identifier may indicate that the TX/RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits the EHT PPDU, the PHY version identifier of 3 bits may be set to the first value. In other words, the receiving STA may determine that the RX PPDU is an EHT PPDU based on the PHY version identifier having the first value.

For example, the version independent bits of the U-SIG may include a 1-bit UL/DL flag field. A first value of the UL/DL flag field of 1 bit is associated with UL communication and a second value of the UL/DL flag field is associated with DL communication.

For example, the version independent bits of the U-SIG may include information related to the TXOP length and information related to the BSS color ID.

For example, when the EHT PPDU is divided into various types (e.g., various types such as an EHT PPDU related to SU mode, an EHT PPDU related to MU mode, an EHT PPDU related to TB mode, an EHT PPDU related to extended range transmission, etc.), information related to the type of the EHT PPDU may be included in version-related bits of the U-SIG.

For example, the U-SIG may comprise: 1) A bandwidth field including information related to a bandwidth; 2) A field including information related to an MCS scheme applied to the EHT-SIG; 3) An indication field including information regarding whether a dual subcarrier modulation (DCM) scheme is applied to the EHT-SIG; 4) A field including information related to a number of symbols for the EHT-SIG; 5) A field including information related to whether to generate an EHT-SIG across a full frequency band; 6) A field including information related to a type of EHT-LTF/STF; and 7) information related to fields indicating the EHT-LTF length and the CP length.

The preamble puncturing may be applied to the PPDU of fig. 10. The preamble puncturing means puncturing is applied to a portion of the full frequency band (e.g., the secondary 20MHz band). For example, when transmitting an 80MHz PPDU, the STA may apply puncturing to a secondary 20MHz band among 80MHz bands, and may transmit the PPDU only through the primary 20MHz band and the secondary 40MHz band.

For example, the pattern of the pilot puncture may be preconfigured. For example, when the first puncturing pattern is applied, puncturing may be applied only to the secondary 20MHz band within the 80MHz band. For example, when the second puncturing pattern is applied, puncturing may be applied only to any one of two secondary 20MHz bands among the secondary 40MHz bands included in the 80MHz band. For example, when the third puncturing pattern is applied, puncturing may be applied only to the secondary 20MHz band included in the primary 80MHz band within the 160MHz band (or the 80mhz+80mhz band). For example, when the fourth puncturing pattern is applied, puncturing may be applied to at least one 20MHz channel not belonging to the main 40MHz band in the presence of the main 40MHz band included in the 80MHz band (or the 80mhz+80mhz band).

Information related to preamble puncturing applied to the PPDU may be included in the U-SIG and/or the EHT-SIG. For example, a first field of the U-SIG may include information related to a contiguous bandwidth, and a second field of the U-SIG may include information related to a preamble puncturing applied to the PPDU.

For example, the U-SIG and the EHT-SIG may include information related to preamble puncturing based on the following method. When the bandwidth of the PPDU exceeds 80MHz, the U-SIG may be individually configured in units of 80 MHz. For example, when the bandwidth of the PPDU is 160MHz, the PPDU may include a first U-SIG for a first 80MHz band and a second U-SIG for a second 80MHz band. In this case, the first field of the first U-SIG may include information related to a 160MHz bandwidth, and the second field of the first U-SIG may include information related to a preamble puncturing pattern applied to the first 80MHz band (i.e., information related to a preamble puncturing pattern). In addition, the first field of the second U-SIG may include information related to a 160MHz bandwidth, and the second field of the second U-SIG may include information related to a preamble puncturing pattern applied to the second 80MHz band (i.e., information related to a preamble puncturing pattern). Further, the EHT-SIG consecutive to the first U-SIG may include information related to a preamble puncturing applied to the second 80MHz band (i.e., information related to a preamble puncturing pattern), and the EHT-SIG consecutive to the second U-SIG may include information related to a preamble puncturing applied to the first 80MHz band (i.e., information related to a preamble puncturing pattern).

Additionally or alternatively, the U-SIG and the EHT-SIG may include information related to preamble puncturing based on the following method. The U-SIG may include information related to preamble puncturing for all frequency bands (i.e., information related to preamble puncturing patterns). That is, the EHT-SIG may not include information related to the preamble puncturing, but only the U-SIG may include information related to the preamble puncturing (i.e., information related to the preamble puncturing pattern).

The U-SIG may be configured in units of 20 MHz. For example, when an 80MHz PPDU is configured, the U-SIG may be duplicated. That is, four identical U-SIGs may be included in an 80MHz PPDU. PPDUs exceeding the 80MHz bandwidth may include different U-SIG.

The EHT-SIG of fig. 10 may include control information for the receiving STA. The EHT-SIG may be transmitted by at least one symbol, and one symbol may have a length of 4 μs. Information related to the number of symbols for the EHT-SIG may be included in the U-SIG.

The EHT-SIG may include the technical features of the HE-SIG-B described with reference to FIGS. 8 and 9. For example, the EHT-SIG may include common fields and user-specific fields as in the example of FIG. 8. The common field of the EHT-SIG may be omitted and the number of user-specific fields may be determined based on the number of users.

As in the example of fig. 8, the common field of the EHT-SIG and the user-specific field of the EHT-SIG may be compiled separately. One user block field included in the user-specific field may include information for two users, but the last user block field included in the user-specific field may include information for one user. That is, one user block field of the EHT-SIG may include up to two user fields. As in the example of fig. 9, each user field may be associated with a MU-MIMO allocation or may be associated with a non-MU-MIMO allocation.

As in the example of fig. 8, the common field of the EHT-SIG may include CRC bits and tail bits. The length of the CRC bits may be determined to be 4 bits. The length of the tail bit may be determined to be 6 bits and may be set to "000000".

As in the example of fig. 8, the common field of the EHT-SIG may include RU allocation information. RU allocation information may mean information related to locations of RU to which a plurality of users (i.e., a plurality of receiving STAs) are allocated. RU allocation information may be configured in units of 8 bits (or N bits), as shown in table 1.

A mode may be supported in which the common field of the EHT-SIG is omitted. Omitting the mode in the common field of the EHT-SIG may be referred to as a compressed mode. When the compressed mode is used, a plurality of users (i.e., a plurality of receiving STAs) may decode a PPDU (e.g., a data field of the PPDU) based on non-OFDMA. That is, a plurality of users of the EHT PPDU may decode PPDUs (e.g., data fields of PPDUs) received through the same frequency band. Further, when the non-compressed mode is used, a plurality of users of the EHT PPDU may decode the PPDU (e.g., a data field of the PPDU) based on the OFDMA. That is, multiple users of the EHT PPDU may receive the PPDU (e.g., a data field of the PPDU) through different frequency bands.

The EHT-SIG may be configured based on various MCS schemes. As described above, information related to an MCS scheme applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on a DCM scheme. For example, among N data tones (e.g., 52 data tones) allocated for an EHT-SIG, a first modulation scheme may be applied to one half of consecutive tones, and a second modulation scheme may be applied to the remaining half of consecutive tones. That is, the transmitting STA may modulate specific control information with a first symbol and assign it to one half of the continuous tones using a first modulation scheme, and may modulate the same control information with a second symbol and assign it to the remaining half of the continuous tones using a second modulation scheme. As described above, information (e.g., a 1-bit field) regarding whether to apply the DCM scheme to the EHT-SIG may be included in the U-SIG. The EHT-STF of fig. 10 may be used to improve automatic gain control estimation in a multiple-input multiple-output (MIMO) environment or an OFDMA environment. The EHT-LTF of fig. 10 may be used to estimate channels in a MIMO environment or an OFDMA environment.

Ext> informationext> relatedext> toext> theext> typeext> ofext> STFext> andext> /ext> orext> LTFext> (ext> includingext> informationext> relatedext> toext> theext> GIext> appliedext> toext> theext> LTFext>)ext> mayext> beext> includedext> inext> theext> SIGext> -ext> aext> fieldext> andext> /ext> orext> SIGext> -ext> bext> fieldext> ofext> fig.ext> 10ext>,ext> etcext>.ext>

The PPDU of fig. 10 (e.g., EHT-PPDU) may be configured based on the examples of fig. 5 and 6.

For example, an EHT PPDU transmitted on a 20MHz band, i.e., a 20MHz EHT PPDU, may be configured based on the RU of fig. 5. That is, the locations of the EHT-STF, the EHT-LTF, and the RU of the data field included in the EHT PPDU may be determined as shown in fig. 5.

The EHT PPDU transmitted on the 40MHz band, i.e., the 40MHz EHT PPDU, may be configured based on the RU of fig. 6. That is, the locations of the EHT-STF, the EHT-LTF, and the RU of the data field included in the EHT PPDU may be determined as shown in fig. 6.

Since the RU position of fig. 6 corresponds to 40MHz, a tone plan (tone-plan) for 80MHz can be determined when the pattern of fig. 6 is repeated twice. That is, the 80MHz EHT PPDU may be transmitted based on a new tone plan that is repeated twice not the RU of fig. 7 but the RU of fig. 6.

When the pattern of fig. 6 is repeated twice, 23 tones (i.e., 11 guard tones +12 guard tones) may be configured in the DC region. That is, the tone plan for an 80MHz EHT PPDU based on OFDMA allocation may have 23 DC tones. In contrast, an 80MHz EHT PPDU based on non-OFDMA allocation (i.e., a non-OFDMA full bandwidth 80MHz PPDU) may be configured based on 996-RUs and may include 5 DC tones, 12 left guard tones, and 11 right guard tones.

The tone plan for 160MHz/240MHz/320MHz may be configured in such a way that the pattern of fig. 6 is repeated several times.

The PPDU of fig. 10 may be determined (or identified) as an EHT PPDU based on the following method.

The receiving STA may determine the type of the RX PPDU as the EHT PPDU based on the following aspects. For example, 1) when the first symbol following the L-LTF signal of the RX PPDU is a BPSK symbol; 2) When detecting the RL-SIG repeated by the L-SIG of the RX PPDU; and 3) when it is detected that the result of applying "modulo 3" to the value of the length field of the L-SIG of the RX PPDU is "0", the RX PPDU may be determined as an EHT PPDU. When the RX PPDU is determined as the EHT PPDU, the receiving STA may detect the type of the EHT PPDU (e.g., SU/MU/trigger-based/extension range type) based on bit information included in a symbol after the RL-SIG of fig. 10. In other words, the receiving STA may determine the RX PPDU as an EHT PPDU based on: 1) The first symbol after the L-LTF signal, which is a BPSK symbol; 2) A RL-SIG continuous with the L-SIG field and identical to the L-SIG; 3) An L-SIG including a length field, wherein a result of applying "modulo 3" is set to "0"; and 4) a 3-bit PHY version identifier (e.g., a PHY version identifier having a first value) of the aforementioned U-SIG.

For example, the receiving STA may determine the type of the RX PPDU as an EHT PPDU based on the following aspects. For example, 1) when the first symbol following the L-LTF signal is a BPSK symbol; 2) When a L-SIG repeated RL-SIG is detected; and 3) when it is detected that the result of applying "modulo 3" to the value of the length field of the L-SIG is "1" or "2", the RX PPDU may be determined as a HE PPDU.

For example, the receiving STA may determine the type of the RX PPDU as non-HT, and VHT PPDUs based on the following aspects. For example, 1) when the first symbol following the L-LTF signal is a BPSK symbol; and 2) when the L-SIG repeated RL-SIG is not detected, the RX PPDU may be determined as a non-HT, and VHT PPDU. In addition, even if the receiving STA detects RL-SIG repetition, when it detects that the result of applying "modulo 3" to the length value of the L-SIG is "0", the RX PPDU may be determined as non-HT, and VHT PPDUs.

In the following examples, signals represented as (TX/RX/UL/DL) signals, (TX/RX/UL/DL) frames, (TX/RX/UL/DL) packets, (TX/RX/UL/DL) data units, (TX/RX/UL/DL) data, etc. may be signals transmitted/received based on the PPDU of fig. 10. The PPDU of fig. 10 may be used to transmit/receive various types of frames. For example, the PPDU of fig. 10 may be used for the control frame. Examples of control frames may include Request To Send (RTS), clear To Send (CTS), power save poll (PS-poll), blockACKReq, blockAck, null Data Packet (NDP) advertisement, and trigger frames. For example, the PPDU of fig. 10 may be used for management frames. Examples of the management frame may include a beacon frame, (re) association request frame, (re) association response frame, probe request frame, and probe response frame. For example, the PPDU of fig. 10 may be used for a data frame. For example, the PPDU of fig. 10 may be used to simultaneously transmit at least two or more of a control frame, a management frame, and a data frame.

Fig. 11 illustrates an example of a modified transmitting device and/or receiving device of the present specification.

Each device/STA of sub-graph (a)/(b) of fig. 1 may be modified as shown in fig. 11. Transceiver 630 of fig. 11 may be identical to transceivers 113 and 123 of fig. 1. The transceiver 630 of fig. 11 may include a receiver and a transmitter.

Processor 610 of fig. 11 may be identical to processors 111 and 121 of fig. 1. Alternatively, the processor 610 of FIG. 11 may be identical to the processing chips 114 and 124 of FIG. 1.

Memory 620 of fig. 11 may be identical to memories 112 and 122 of fig. 1. Alternatively, memory 620 of FIG. 11 may be a separate external memory from memories 112 and 122 of FIG. 1.

Referring to fig. 11, a power management module 611 manages power for the processor 610 and/or the transceiver 630. The battery 612 provides power to the power management module 611. The display 613 outputs the result processed by the processor 610. The keyboard 614 receives input to be used by the processor 610. A keyboard 614 may be displayed on the display 613. The SIM card 615 may be an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and its associated keys for identifying and authenticating subscribers on mobile telephone devices, such as mobile telephones and computers.

Referring to fig. 11, a speaker 640 may output results related to sound processed by the processor 610. The microphone 641 may receive input related to sounds to be used by the processor 610.

1. Embodiments suitable for use in the present disclosure

WLAN 802.11 systems consider using a wider frequency band or more antennas than the existing 11ax frequency band to transmit the added streams to improve peak throughput. In addition, the present specification also contemplates methods of aggregating and using various frequency bands/links.

In addition, an EHT capability element is defined to indicate the capabilities of the STA, and supported EHT-MCS and NSS setting fields are set forth therein.

The AP and the STA may exchange capabilities of the STA (or AP) at an association stage after the beacon transmission, and at this time, HE and EHT capability elements may be used.

The HE capability element includes a supported channel width setting subfield (7 bits). The supported channel width setting subfield is defined as follows.

TABLE 3

Fig. 12 shows the format of the EHT capability element.

The STA declares it an EHT STA by transmitting an EHT capability element. The EHT capability element includes a plurality of fields for advertising the EHT capability of the EHT STA.

Referring to fig. 12, the EHT capability element includes an element field, a length field, an element ID extension field, an EHT MAC capability information field, an EHT PHY capability information field, supported EHT-MCS and NSS setting fields, and an EHT PPE threshold (optional) field.

Fig. 13 shows the formats of the supported EHT-MCS and NSS setting fields.

The supported EHT-MCS and NSS settings field indicates a combination of EHT-MCS 0-13 supporting the transmission of the STA and the number of spatial streams NSS and a combination of EHT-MCS 0-13 supporting the reception of the STA and the number of spatial streams NSS.

The EHT-MCSs 14 and 15 can only be combined with a single stream and are indicated in the EHT PHY capability information field.

Referring to fig. 13, the supported EHT-MCS and NSS setting fields include an EHT-MCS mapping (20 MHz non-AP STA only) subfield, an EHT-MCS mapping (bw.ltoreq.80 MHz, except for 20MHz non-AP STA only) subfield, an EHT-MCS mapping (bw=160 MHz) subfield, and an EHT-MCS mapping (bw=320 MHz) subfield.

The definition and encoding of the subfields included in the supported EHT-MCS and NSS setting fields are described as follows.

TABLE 4

TABLE 5

TABLE 6

1.1. Additional definition of existing subfields

The definition of the EHT-MCS mapping (20 MHz-only STA) subfield means the maximum Nss (number of spatial streams) that only 20MHz STAs (or 20MHz operating STAs) can receive or transmit in each MCS. However, only 20MHz STAs (or 20MHz operating STAs) may transmit and receive through RU/MRU assigned to a particular 20MHz channel having a wider bandwidth (i.e., 40/80/160/320 MHz). Thus, the EHT-MCS mapping (20 MHz-only STA) subfield may be a subfield applied not only to 20MHz BW but also when allocating and using a corresponding 20 MHz-only STA (or 20 MHz-operating STA) in the 40/80/160/320MHz BW case. STAs that may be allocated in the wider bandwidth may be limited to non-AP STAs, so the maximum NSS indication for each MCS in the wider bandwidth may also be limited to non-AP STAs only.

Fig. 14 is a format of an EHT-MCS mapping (20 MHz only STA) subfield.

Referring to fig. 14, an EHT-MCS mapping (20 MHz-only STA) subfield may have a size of 4 octets, and an EHT-MCS mapping (20 MHz-only STA) subfield may include 8 subfields, each subfield having 4 bits. Each subfield indicates a maximum Nss value supported in a specific EHT-MCS transmission/reception scenario.

Referring to fig. 14, the EHT-MCS mapping (only 20MHz STA) subfield includes an Rx Max Nss subfield supporting EHT-MCS 0-7, an Rx Max Nss subfield supporting EHT-MCS 8-9, an Tx Max Nss subfield supporting EHT-MCS 8-9, an Rx Max Nss subfield supporting EHT-MCS10-11, an Tx Max Nss subfield supporting EHT-MCS10-11, an Rx Max Nss subfield supporting EHT-MCS12-13, and an Tx Max Nss subfield supporting EHT-MCS 12-13.

Fig. 15 is a format of EHT-MCS mapping (bw+.80 MHz, except for only 20MHz non-AP STAs), EHT-MCS mapping (bw=160 MHz), and EHT-MCS mapping (bw=320 MHz) subfields.

Referring to fig. 15, since EHT-MCS mapping (bw+.80 MHz except for only 20MHz non-AP STAs), EHT-MCS mapping (bw=160 MHz) and EHT-MCS mapping (bw=320 MHz) subfields may have a size of 3 octets, EHT-MCS mapping (bw+.80 MHz except for only 20MHz non-AP STAs), EHT-MCS mapping (bw=160 MHz) and EHT-MCS mapping (bw=320 MHz) subfields may include 6 subfields, each of which consists of 4 bits. Each subfield indicates a maximum Nss value supported in a specific EHT-MCS transmission/reception scenario.

Referring to fig. 15, each of the EHT-MCS mapping (BW is less than or equal to 80MHz except for only 20MHz non-AP STAs), EHT-MCS mapping (bw=160 MHz), and EHT-MCS mapping (bw=320 MHz) subfields includes an Rx Max Nss subfield supporting EHT-MCS 0-9, a Tx Max Nss subfield supporting EHT-MCS 0-9, an Rx Max Nss subfield supporting EHT-MCS10-11, a Tx Max Nss subfield supporting EHT-MCS10-11, an Rx Max Nss subfield supporting EHT-MCS12-13, and a Tx Max Nss subfield supporting EHT-MCS 12-13.

Each 4-bit subfield in fig. 14 and 15 may be encoded as follows. The following table shows the coding of the maximum NSS value for a particular MCS value.

TABLE 7

Max Nss subfield value	Maximum number of spatial streams supporting a specified MCS set
		0	Not support
1	1
		2	2
3	3
		4	4
5	5
		6	6
7	7
		8	8
9-15	Reservation of

The Rx Max NSS subfield supporting EHT-MCS 0-7 and the Tx Max NSS subfield supporting EHT-MCS 0-7 are encoded according to Table 7 above.

The Rx Max NSS subfield supporting EHT-MCS 0-9 and the Tx Max NSS subfield supporting EHT-MCS 0-9 are encoded according to Table 7 above.

The Rx Max NSS subfield supporting EHT-MCS10-11 and the Tx Max NSS subfield supporting EHT-MCS10-11 are encoded according to Table 7 above.

The Rx Max NSS subfield supporting EHT-MCS12-13 and the Tx Max NSS subfield supporting EHT-MCS12-13 are encoded according to Table 7 above.

The reserved values in table 7 above indicate a maximum Nss of greater than 8 spatial streams.

The definition of the EHT-MCS mapping (BW < = 80MHz except for only 20MHz STAs) subfield means the maximum Nss that STAs operating above 80MHz can receive or transmit in each MCS of the 20/40/80MHz PPDU. However, an 80MHz operating STA may transmit and receive through RU/MRU within a particular 80MHz channel that is assigned to a wider bandwidth (i.e., 160/320 MHz). Thus, the EHT-MCS mapping (BW < = 80MHz except for only 20MHz STAs) subfield may be a subfield that is applied not only to 80MHz BW but also when corresponding 80MHz operating STAs (STAs not adapted to operate above 80 MHz) are allocated and used in the 160/320MHz BW case. In addition, the EHT-MCS mapping (BW < = 80MHz except for 20MHz STAs) subfield may be a subfield applied not only to 20/40/80MHz BW but also to STAs whose operation bandwidth is reduced to 20/40MHz in the 160/320MHz BW case (regardless of actual capability, i.e., when STAs whose actual capability is 80/160/320MHz operation channel width are changed to 20/40MHz operation channel width). STAs that may be allocated in the wider bandwidth may be limited to non-AP STAs, so the maximum NSS indication for each MCS in the wider bandwidth may also be limited to non-AP STAs only.

Fig. 15 is a format of an EHT-MCS mapping (BW < =80 MHz except for only 20MHz STAs) subfield, and a 4-bit encoding method is the same as table 7 above.

The definition of the EHT-MCS mapping (bw=160 MHz) subfield means the maximum Nss that STAs operating above 160MHz can receive or transmit in each MCS of the 160MHz PPDU. However, 160MHz operating STAs may transmit and receive through RU/MRU within a particular 160MHz channel assigned to a wider bandwidth (320 MHz). Thus, the EHT-MCS mapping (bw=160 MHz) subfield may be a subfield applied not only to 160MHz BW but also to allocate and use a corresponding 160MHz operating STA (not applicable to STAs operating above 160 MHz) in the 320MHz BW case. STAs that may be allocated in the wider bandwidth may be limited to non-AP STAs, so the maximum NSS indication for each MCS in the wider bandwidth may also be limited to non-AP STAs only.

The format of the EHT-MCS mapping (bw=160 MHz) subfield is the same as in fig. 15, and the 4-bit encoding method is the same as table 7 above.

1.1.1.2.4GHz sub-field definition

There is a 40MHz operating STA in 2.4GHz, and for this purpose, an EHT-MCS mapping (40 MHz in BW < = 2.4GHz except for 20MHz STAs) subfield may be defined in the supported EHT-MCS and NSS settings fields (another name may be used). The definition of the EHT-MCS mapping (40 MHz in BW < = 2.4GHz except for only 20MHz STAs) subfield may be 40MHz operating STAs in 2.4GHz and STAs with reduced operating channel width of 20MHz (the original capability of the STA is 40MHz operating channel width but when reduced to 20MHz channel width) may be the maximum Nss that can be received or transmitted in each MCS of the 20/40MHz PPDU. In addition, the format of the EHT-MCS mapping (40 MHz in BW < = 2.4GHz except for only 20MHz STAs) subfield may be the same as fig. 15, and the 4-bit encoding method may be the same as table 7 above. Only for STAs operating at 40MHz at 2.4GHz, there may be EHT-MCS mapping (40 MHz in BW < = 2.4GHz, except for only 20MHz STAs) subfields. That is, in the case of 2.4GHz, B0 of the supported channel width setting field in the HE PHY capability information field is 1.

Alternatively, an EHT-MCS mapping (20 MHz in bw=2.4 GHz except for only 20MHz STAs) and an EHT-MCS mapping (40 MHz in bw=2.4 GHz) subfield may be defined for STAs operating at 40MHz in 2.4 GHz. (other names may be used). Each may be a 40MHz operating STA at 2.4GHz and an STA having an operating channel width reduced by 20MHz (the original capability of the STA is a 40MHz operating channel width but reduced to a 20MHz channel width) may receive or transmit a maximum Nss in each MCS of a 20MHz PPDU and a 40MHz operating STA at 2.4GHz and an STA having an operating channel width reduced by 20MHz (the original capability of the STA is a 40MHz operating channel width but reduced to a 20MHz channel width) may receive or transmit a maximum Nss in each MCS of a 40MHz PPDU. In addition, the format of the EHT-MCS mapping (20 MHz in bw=2.4 GHz except for only 20MHz STAs) and EHT-MCS mapping (40 MHz in bw=2.4 GHz) subfields may be the same as fig. 15. The 4-bit encoding method may be the same as table 7 above. In the case of a STA operating at 40MHz only at 2.4GHz, there may be an EHT-MCS mapping (20 MHz in bw=2.4 GHz except for only 20MHz STAs) sub-field and an EHT-MCS mapping (40 MHz in bw=2.4 GHz) sub-field. That is, in the case of 2.4GHz, B0 of the supported channel width setting field in the HE PHY capability information field is 1.

Alternatively, a 40MHz operating STA in 2.4GHz may use an EHT-MCS mapping (BW < = 80MHz, except for only 20MHz STAs) subfield. In this case, the EHT-MCS mapping (BW < = 80MHz except for only 20MHz STAs) subfield may represent 40MHz operating STAs at 2.4GHz and STAs with reduced operating channel width of 20MHz (the original capability of the STAs is 40MHz operating channel width, but when reduced to 20MHz channel width) may be the maximum Nss received or transmitted in each MCS of the 20/40MHz PPDU. Only for STAs operating at 40MHz at 2.4GHz, there may be EHT-MCS mapping (BW < = 80MHz except for only 20MHz STAs) subfields. That is, in the case of 2.4GHz, B0 of the supported channel width setting field in the HE PHY capability information field is 1.

A 2.4GHz 20 MHz-only STA may use the EHT-MCS mapping (20 MHz-only STA) subfield as it is. However, in this case, the EHT-MCS mapping (20 MHz STA only) subfield may represent Max NSS in each MCS when corresponding to a 20/40MHz BW case where only 20MHz STA (or 20MHz operating STA) is allocated and used at 2.4 GHz. This subfield may only exist in the case of only 20MHz STAs (or 20MHz operating STAs) at 2.4 GHz. That is, in the case of 2.4GHz, B0 of the supported channel width setting field in the HE PHY capability information field is 0. STAs that may be allocated in a wider bandwidth may be limited to non-AP STAs. Thus, the maximum NSS indication for each MCS in the wider bandwidth may also be limited to non-AP STAs.

A new EHT-MCS mapping (only 20MHz STA in 2.4 GHz) subfield may be additionally defined for only 20MHz STAs in 2.4GHz. In the case of 20/40MHz BW at 2.4GHz, each MCS may indicate Max NSS when a corresponding 20 MHz-only STA (or 20MHz operating STA) is allocated and used. The format of the EHT-MCS mapping (only 20MHz STA in 2.4 GHz) subfield may be the same as fig. 15, and the 4-bit encoding method may be the same as table 7 above. The EHT-MCS mapping (20 MHz only STA in 2.4 GHz) subfield may only exist in the case of 20MHz only STA (or 20MHz operating STA) in 2.4GHz. That is, in the case of 2.4GHz, B0 of the supported channel width setting field in the HE PHY capability information field is 0. STAs that may be allocated in the wider bandwidth may be limited to non-AP STAs, so the maximum NSS indication for each MCS in the wider bandwidth may also be limited to non-AP STAs only.

1.2. When STA-based operation channel width limitations are removed from each subfield

1.2.1. Identical subfields used at 2.4GHz and 5/6GHz

In addition, subfields within the new supported EHT-MCS and NSS settings fields may be designed as shown below (names other than the names of subfields named below may be used). Each of the following subfields may always exist regardless of the operation channel width of the STA (there may be only subfields for each 2.4GHz or 5/6GHz band). Each subfield below may mean the maximum Nss that can be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire BW (same or wider operating STA as BW) or to some RU/MRU (this applies not only to smaller operating channel widths but also to same or wider operating STAs as BW).

EHT-MCS mapping (bw=20 MHz) subfield

EHT-MCS mapping (bw=40 MHz) subfield

EHT-MCS mapping (bw=80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz). The EHT-MCS mapping (bw=20 MHz) subfield and the EHT-MCS mapping (bw=40 MHz) subfield may be used in both 2.4GHz and 5/6 GHz. Alternatively, the EHT-MCS mapping (bw=40 MHz) subfield may be defined only for STAs operating in the 2.4GHz band, in which case the EHT-MCS mapping (bw=80 MHz) subfield may be defined only for STAs operating in the 5/6GHz band. In this case it may comprise up to 40MHz (or up to 20/40 MHz).

Alternatively, it may be composed of subfields as shown below, and different names may be used. As described above, each subfield may always exist regardless of the operation channel width of the STA (only subfields for each 2.4GHz or 5/6GHz band may exist), and may mean the maximum Nss that may be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire STA (same or wider operation STA as BW) or to some RU/MRUs in each BW (this applies not only to smaller operation channel widths but also to same or wider operation STAs as BW). However, in the case where the STA operates at 2.4GHz, the interpretation of the EHT-MCS mapping (BW < = 80 MHz) subfield is required may mean the maximum Nss that each MCS may receive or transmit when assigned to RU/MRU of a 20MHz or 40MHz PPDU in the 2.4GHz band. That is, the EHT-MCS mapping (BW < = 80 MHz) subfield may be used in both 2.4GHz and 5/6 GHz.

EHT-MCS mapping (BW < =80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz).

Alternatively, it may be composed of subfields as shown below, and different names may be used. As described above, each subfield below may always exist (only subfields for each 2.4GHz or 5/6GHz band may exist) regardless of the operation channel width of the STA. Each subfield below may mean the maximum Nss that can be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire STA in each BW (same or wider operating STA as BW) or to some RU/MRU (this applies not only to smaller operating channel widths but also to same or wider operating STAs as BW). However, in the case of a 20MHz operating STA, the interpretation of the EHT-MCS mapping (BW < = 80 MHz) subfield may mean the maximum Nss that may be received or transmitted by each MCS when assigned to fewer PPDUs or RU/MRUs of 80MHz, with 20MHz excluded. This explanation may be applied to STAs with different operating channel widths, but simply assigning to a smaller PPDU (i.e., including 20 MHz) or an RU/MRU of 80MHz may mean the maximum Nss that may be received or transmitted in each MCS. In addition, in the case of a 20/40MHz operating STA operating at 2.4GHz, the interpretation of the EHT-MCS mapping (bw=20 MHz) subfield may mean the maximum Nss that may be received or transmitted by each MCS when assigned to RU/MRU of a 20MHz PPDU in the 2.4GHz band. In the case of a 20/40MHz operating STA operating at 2.4GHz, the interpretation of the EHT-MCS mapping (BW < = 80 MHz) subfield may mean the maximum Nss that may be received or transmitted by each MCS when assigned to the RU/MRU of a 20MHz or 40MHz PPDU in the 2.4GHz band. Since the EHT-MCS mapping (bw=20 MHz) subfield may contain information related to 2.4GHz 20MHz PPDU allocation, this may mean the maximum Nss that each MCS may receive or transmit when RU/MRU excluding a 40MHz PPDU of 20MHz is allocated. That is, the EHT-MCS mapping (bw=20 MHz) subfield and the EHT-MCS mapping (BW < =80 MHz) subfield may be used in both 2.4GHz and 5/6 GHz.

EHT-MCS mapping (bw=20 MHz) subfield

EHT-MCS mapping (BW < =80 MHz) subfield or EHT-MCS mapping (bw=40/80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz). The above configuration has the advantage of using the structure of the supported EHT-MCS and NSS setting fields previously defined.

1.2.2. Subfields used in 2.4GHz and 5/6GHz are defined differently.

It may consist of subfields as shown below, and may use different names. As described above, each subfield below may always exist (only subfields for each 2.4GHz or 5/6GHz band may exist) regardless of the operation channel width of the STA. Each subfield below may mean the maximum Nss that can be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire STA in each BW (same or wider operating STA as BW) or to some RU/MRU (this applies not only to smaller operating channel widths but also to same or wider operating STAs as BW). The EHT-MCS mapping (BW < = 40MHz in 2.4 GHz) subfield is a subfield for STAs operating in the 2.4GHz band, and may mean the maximum Nss that may be received or transmitted by each MCS when assigned to RU/MRU of a 20MHz or 40MHz PPDU in the 2.4GHz band. The remaining subfields are for STAs operating in the 5/6GHz band, and the EHT-MCS mapping (BW < = 80 MHz) subfield may mean the maximum Nss that may be received or transmitted in each MCS when assigned to fewer PPDUs or RU/MRUs of 80 MHz.

EHT-MCS mapping (BW < = 40MHz in 2.4 GHz) subfield

EHT-MCS mapping (BW < =80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz).

Alternatively, it may be composed of subfields as shown below, and different names may be used. As described above, each subfield below may always exist (only subfields for each 2.4GHz or 5/6GHz band may exist) regardless of the operation channel width of the STA. Each subfield below may mean the maximum Nss that can be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire STA in each BW (same or wider operating STA as BW) or to some RU/MRU (this applies not only to smaller operating channel widths but also to same or wider operating STAs as BW). The EHT-MCS mapping (BW < = 40MHz in 2.4 GHz) subfield is a subfield for STAs operating in the 2.4GHz band, and may mean the maximum Nss that may be received or transmitted by each MCS when assigned to RU/MRU of a 20MHz or 40MHz PPDU in the 2.4GHz band. The remaining subfields are used for STAs operating in the 5/6GHz band. In the case of a 20MHz operating STA in the 5/6GHz band, the interpretation of the EHT-MCS mapping (BW < = 80 MHz) subfield may mean the maximum Nss that may be received or transmitted by each MCS when assigned to fewer PPDUs or RU/MRUs of 80MHz, with 20MHz excluded. This explanation may be applied to STAs with different operating channel widths, but simply assigning to fewer PPDUs (i.e., including 20 MHz) or RU/MRU of 80MHz may mean the maximum Nss that may be received or transmitted in each MCS.

EHT-MCS mapping (BW < = 40MHz in 2.4 GHz) subfield

EHT-MCS mapping (bw=20 MHz) subfield

EHT-MCS mapping (BW < =80 MHz) subfield or EHT-MCS mapping (bw=40/80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz).

Alternatively, it may be composed of subfields as shown below, and different names may be used. As described above, each subfield below may always exist (only subfields for each 2.4GHz or 5/6GHz band may exist) regardless of the operation channel width of the STA. Each subfield below may mean the maximum Nss that can be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire BW (same or wider operating STA as BW) or to some RU/MRU (this applies not only to smaller operating channel widths but also to same or wider operating STAs as BW). The EHT-MCS mapping (bw=20 MHz in 2.4 GHz) subfield and the EHT-MCS mapping (bw=40 MHz in 2.4 GHz) subfield are subfields when STAs for operation in the 2.4GHz band are assigned to 20MHz and 40MHz PPDUs, respectively. The remaining subfields are used for STAs operating in the 5/6GHz band. In the case of a 20MHz operating STA in the 5/6GHz band, the interpretation of the EHT-MCS mapping (BW < = 80 MHz) subfield may mean the maximum Nss that may be received or transmitted by each MCS when assigned to fewer PPDUs or RU/MRUs of 80MHz, with 20MHz excluded. This explanation may be applied to STAs with different operating channel widths, but simply assigning to fewer PPDUs (i.e., including 20 MHz) or RU/MRU of 80MHz may mean the maximum Nss that may be received or transmitted in each MCS.

EHT-MCS mapping (bw=20 MHz in 2.4 GHz) subfield

EHT-MCS mapping (bw=40 MHz in 2.4 GHz) subfield

EHT-MCS mapping (bw=20 MHz) subfield

EHT-MCS mapping (BW < =80 MHz) subfield or EHT-MCS mapping (bw=40/80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz).

Alternatively, it may be composed of subfields as shown below, and different names may be used. As described above, each subfield below may always exist (only subfields for each 2.4GHz or 5/6GHz band may exist) regardless of the operation channel width of the STA. Each subfield below may mean the maximum Nss that can be received or transmitted by each MCS of the PPDU using BW, regardless of whether the STA is assigned to the entire STA in each BW (same or wider operating STA as BW) or to some RU/MRU (this applies not only to smaller operating channel widths but also to same or wider operating STAs as BW). The EHT-MCS mapping (bw=20 MHz in 2.4 GHz) subfield and the EHT-MCS mapping (bw=40 MHz in 2.4 GHz) subfield are subfields when STAs for operation in the 2.4GHz band are assigned to 20MHz and 40MHz PPDUs, respectively. The remaining subfields are used for STAs operating in the 5/6GHz band. The EHT-MCS mapping (BW < = 80 MHz) subfield may mean the maximum Nss that each MCS may receive or transmit when STAs are allocated to fewer PPDUs or RU/MRUs of 80 MHz.

EHT-MCS mapping (bw=20 MHz in 2.4 GHz) subfield

EHT-MCS mapping (bw=40 MHz in 2.4 GHz) subfield

EHT-MCS mapping (BW < =80 MHz) subfield

EHT-MCS mapping (bw=160 MHz) subfield

EHT-MCS mapping (bw=320 MHz) subfield

Each subfield may be composed of 3 octets or 4 octets, and when composed of 3 octets, each subfield may have the same format as fig. 15. When composed of 4 octets, each subfield may have the same format as fig. 14. However, in view of 20MHz operating STAs, it may be advantageous to have the same format as fig. 14, where all subfields are always composed of 4 octets. Alternatively, depending on the operating channel width of the STA, all subfields may be composed of 4 octets (for a STA operating only at 20MHz or a STA operating at 20 MHz) or 3 octets (for a STA having an operating channel width exceeding 20 MHz).

In all of the above proposals 1.1 and 1.2, in the case of a 2.4GHz Basic Service Set (BSS), a meaningful NSS value may be indicated in only a sub-field defined by 2.4GHz (this may be a sub-field containing meaningful information even in the case of a 5/6GHz BSS), and the maximum NSS value may simply be set to 0 for the other sub-fields or the sub-field may not exist. In addition, in the case of the 5/6GHz BSS in all of the above proposals 1.1 and 1.2, the maximum NSS value of the subfield defined only at 2.4GHz (which is a subfield that does not contain meaningful information in the case of the 5/6GHz BSS) may simply be set to 0 or the subfield may not exist. As in the various proposals above, various subfields are defined within the supported EHT-MCS and NSS setting fields, but from an overhead or implementation point of view, when indicating actual capabilities, it may be desirable to configure the fields to include only subfields used in the operating band.

Fig. 16 is a flowchart illustrating the operation of the transmitting apparatus/device according to the present embodiment.

The example of fig. 16 may be performed by a transmitting device (AP and/or non-AP STA).

Some of each step of the example of fig. 16 (or detailed sub-steps to be described later) may be skipped/omitted.

The transmitting apparatus (transmitting STA) can obtain information on the above tone plan through step S1610. As described above, the information on the tone plan includes the size and location of the RU, control information related to the RU, information on a frequency band including the RU, information on a STA receiving the RU, and the like.

The transmitting apparatus may construct/generate a PPDU based on the acquired control information through step S1620. Configuring/generating the PPDU may include configuring/generating each field of the PPDU. That is, step S1620 includes configuring an EHT-SIG field including control information about a tone plan. That is, step S1620 includes configuring a field including control information (e.g., an N bitmap) indicating the size/position of the RU; and/or a field configured to include an identifier (e.g., AID) of a STA receiving the RU.

In addition, step S1620 may include generating an STF/LTF sequence transmitted through a specific RU. The STF/LTF sequence may be generated based on a preset STF generation sequence/LTF generation sequence.

Further, step S1620 may include generating a data field (i.e., MPDU) transmitted through a specific RU.

The transmitting apparatus may transmit the PPDU constructed through step S1620 to the receiving apparatus based on step S1630.

When performing step S1630, the transmitting device may perform at least one of operations such as CSD, spatial mapping, IDFT/IFFT operation, and GI insertion.

Signals/fields/sequences constructed in accordance with the present description may be transmitted in the form of fig. 10.

Fig. 17 is a flowchart illustrating the operation of the receiving apparatus/device according to the present embodiment.

The foregoing PPDU may be received according to the example of fig. 17.

The example of fig. 17 may be performed by a receiving device/apparatus (AP and/or non-AP STA).

Some of each step of the example of fig. 17 (or detailed sub-steps to be described later) may be skipped/omitted.

The reception apparatus (reception STA) may receive all or a part of the PPDU through step S1710. The received signal may be in the form of fig. 10.

The substep of step S1710 may be determined based on step S1630 of fig. 16. That is, in step S1710, an operation of restoring the results of the CSD, the spatial mapping, the IDFT/IFFT operation, and the GI insertion operation applied in step S1630 may be performed.

In step S1720, the reception apparatus may decode all/a portion of the PPDU. Further, the receiving apparatus may obtain control information related to a tone plan (i.e., RU) from the decoded PPDU.

More specifically, the receiving apparatus may decode the L-SIG and EHT-SIG of the PPDU based on the legacy STF/LTF and obtain information included in the L-SIG and EHT SIG fields. Information about various tone plans (i.e., RUs) described in the present specification may be included in the EHT-SIG, and the receiving STA may obtain information about the tone plans (i.e., RUs) through the EHT-SIG.

In step S1730, the reception apparatus may decode the remaining portion of the PPDU based on the information on the tone plan (i.e., RU) acquired through step S1720. For example, the receiving STA may decode the STF/LTF field of the PPDU based on information about one schedule (i.e., RU). In addition, the receiving STA may decode a data field of the PPDU based on information about a tone plan (i.e., RU) and obtain MPDUs included in the data field.

In addition, the reception apparatus may perform a processing operation of transmitting the data decoded through step S1730 to a higher layer (e.g., MAC layer). In addition, when generation of a signal is instructed from an upper layer to a PHY layer in response to data transmitted to the upper layer, a subsequent operation may be performed.

Hereinafter, the above-described embodiments will be described with reference to fig. 1 to 17.

Fig. 18 is a flowchart illustrating a procedure in which a transmitting STA receives capability information of a receiving STA according to the present embodiment.

The example of fig. 18 may be performed in a network environment supporting a next generation WLAN system (IEEE 802.11be or EHT WLAN system). The next generation wireless LAN system is a WLAN system enhanced from the 802.11ax system, and thus can satisfy backward compatibility with the 802.11ax system.

The example of fig. 18 is performed in a transmitting STA, and the transmitting STA may correspond to an Access Point (AP) STA. The receiving STA may correspond to a non-AP STA.

This embodiment proposes a signaling method including in capability information the maximum number of spatial streams that can be transmitted or received for each MCS when a receiving STA is allocated a transmission bandwidth greater than a channel for its operation and operates in a 2.4GHz band.

In step S1810, a transmitting Station (STA) receives capability information of a receiving STA from the receiving STA.

In step S1820, the transmitting STA decodes capability information of the receiving STA.

The capability information of the receiving STA includes a High Efficiency (HE) capability element and an Extremely High Throughput (EHT) capability element.

The HE capability element includes a supported channel width setting field. The EHT capability element includes supported EHT-MCS (modulation and coding scheme) and NSS (number of spatial streams) setting fields.

The supported EHT-MCS and NSS setting fields include first through fourth subfields. The first subfield may correspond to an EHT-MCS mapping (20 MHz only non-AP STA), the second subfield may correspond to an EHT-MCS mapping (BW < = 80MHz, except for 20MHz only non-AP STA), the third subfield may correspond to an EHT-MCS mapping (BW = 160 MHz) subfield, and the fourth subfield may correspond to an EHT-MCS mapping (BW = 320 MHz) subfield.

When the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in 5GHz and 6GHz bands, when the second to fourth bits (B1, B2, B3) of the supported channel width setting field are all set to 0, there is a first subfield, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz.

When the receiving STA operates in the 2.4GHz band, when the first bit (B0) of the supported channel width setting field is set to 0, there is a first subfield, and the first transmission bandwidth is 20MHz or 40MHz.

That is, even if the receiving STA is a non-AP STA operating only at 20MHz, it may be allocated to a first transmission bandwidth larger than a 20MHz channel for the receiving STA to operate. Specifically, even when the receiving STA operates in the 2.4GHz band, the receiving STA may transmit the maximum number of spatial streams that can be transmitted or received for each MCS to the transmitting STA through the first subfield.

When the receiving STA is a non-AP STA operating at 80MHz or more and is allocated to the second transmission bandwidth, the second subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, the second subfield exists when the second bit of the supported channel width setting field is set to 1, and the second transmission bandwidth may be 20MHz, 40MHz, or 80MHz.

When the receiving STA operates in the 2.4GHz band, the second subfield exists when the first bit of the supported channel width setting field is set to 1, and the second transmission bandwidth may be 20MHz or 40MHz.

When the receiving STA is a non-AP STA operating at 20MHz or 80MHz and is allocated to the third transmission bandwidth, the second subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, the second subfield exists when the second bit of the supported channel width setting field is set to 1, and the third transmission bandwidth may be 160MHz or 320MHz.

That is, even if the receiving STA is a non-AP STA operating at 20MHz or 80MHz, it may be allocated to a third transmission bandwidth greater than a 20MHz or 80MHz channel for the receiving STA to operate, at which time the receiving STA may transmit the maximum number of spatial streams that may be transmitted or received for each MCS to the transmitting STA through the second subfield.

When the receiving STA is a non-AP STA operating at 160MHz or more and is allocated to the fourth transmission bandwidth, the third subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, when the third bit of the supported channel width setting field is set to 1, there is a third subfield, and the fourth transmission bandwidth may be 160MHz.

When the receiving STA is a non-AP STA operating at 160MHz and is allocated to a fifth transmission bandwidth, the third subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, when the third bit of the supported channel width setting field is set to 1, there is a third subfield, and the fifth transmission bandwidth may be 320MHz.

That is, even if the receiving STA is a non-AP STA operating at 160MHz, it may be allocated to a fifth transmission bandwidth larger than a 160MHz channel for the receiving STA to operate, at which time the receiving STA may transmit the maximum number of spatial streams that may be transmitted or received for each MCS to the transmitting STA through the third subfield.

When the receiving STA is a non-AP STA operating at 320MHz and is allocated to a sixth transmission bandwidth, the fourth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

The EHT capability element may also include a 320MHz subfield in 6GHz supported.

When the receiving STA operates in the 5GHz or 6GHz band, when the 320MHz subfield in the 6GHz supported is set to 1, there is a fourth subfield, and the sixth transmission bandwidth may be 320MHz.

That is, this embodiment proposes a method of signaling implemented by including information on the maximum number of spatial streams that can be transmitted or received for each supportable MCS in capability information when a receiving STA is allocated a transmission bandwidth greater than a channel for its operation and operates in a 2.4GHz band. This has the effect of improving overall throughput by applying the maximum number of spatial streams in more diverse situations.

The first subfield may include fifth through twelfth subfields. The fifth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS 0-7, the sixth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 0-7, the seventh subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS 8-9, the eighth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 8-9, the ninth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS10-11, the tenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS10-11, the eleventh subfield may correspond to a Max NSS subfield supporting EHT-MCS12-13, and the twelfth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 12-13.

The fifth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 7. The sixth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 0 to 7. The seventh subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 8 to 9. The eighth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 8 to 9. The ninth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11. The tenth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 10 to 11. The eleventh subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13. The twelfth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

Each of the second through fourth subfields may include thirteenth through eighteenth subfields. The thirteenth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS 0-9, the fourteenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 0-9, the fifteenth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS10-11, the sixteenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS10-11, the seventeenth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS12-13, and the eighteenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 12-13.

The thirteenth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 9. The fourteenth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 0 to 9. The fifteenth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11. The sixteenth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 10 to 11. The seventeenth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13. The eighteenth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

The fifth through eighteenth subfields may be composed of 4 bits. When the value of 4 bits is 1 to 8, the maximum number of spatial streams that the receiving STA can transmit in the specified MCS may be 1 to 8. When the value of 4 bits is 9 to 15, it is set to a reserved value, which may mean that the maximum number of spatial streams that a receiving STA can transmit in a specified MCS is greater than 8.

Fig. 19 is a flowchart illustrating a procedure in which a receiving STA transmits capability information of the receiving STA to a transmitting STA according to the present embodiment.

The example of fig. 19 may be performed in a network environment supporting a next generation WLAN system (IEEE 802.11be or EHT WLAN system). The next generation wireless LAN system is a WLAN system enhanced from the 802.11ax system, and thus can satisfy backward compatibility with the 802.11ax system.

The example of fig. 19 is performed in a receiving STA, and the receiving STA may correspond to a non-access point (non-AP) STA. The transmitting STA may correspond to an AP STA.

This embodiment proposes a signaling method including in capability information the maximum number of spatial streams that can be transmitted or received for each MCS when a receiving STA is allocated a transmission bandwidth greater than a channel for its operation and operates in a 2.4GHz band.

In step S1910, a receiving Station (STA) generates capability information of the receiving STA.

In step S1920, the receiving STA transmits the capability information of the receiving STA to the transmitting STA.

The capability information of the receiving STA includes a High Efficiency (HE) capability element and an Extremely High Throughput (EHT) capability element.

The HE capability element includes a supported channel width setting field. The EHT capability element includes supported EHT-MCS (modulation and coding scheme) and NSS (number of spatial streams) setting fields.

The supported EHT-MCS and NSS setting fields include first through fourth subfields. The first subfield may correspond to an EHT-MCS mapping (20 MHz only non-AP STA), the second subfield may correspond to an EHT-MCS mapping (BW < = 80MHz, except for 20MHz only non-AP STA), the third subfield may correspond to an EHT-MCS mapping (BW = 160 MHz) subfield, and the fourth subfield may correspond to an EHT-MCS mapping (BW = 320 MHz) subfield.

When the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in 5GHz and 6GHz bands, when the second to fourth bits (B1, B2, B3) of the supported channel width setting field are all set to 0, there is a first subfield, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz.

When the receiving STA operates in the 2.4GHz band, when the first bit (B0) of the supported channel width setting field is set to 0, there is a first subfield, and the first transmission bandwidth is 20MHz or 40MHz.

That is, even if the receiving STA is a non-AP STA operating only at 20MHz, it may be allocated to a first transmission bandwidth larger than a 20MHz channel for the receiving STA to operate. Specifically, even when the receiving STA operates in the 2.4GHz band, the receiving STA may transmit the maximum number of spatial streams that can be transmitted or received for each MCS to the transmitting STA through the first subfield.

When the receiving STA is a non-AP STA operating at 80MHz or more and is allocated to the second transmission bandwidth, the second subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, the second subfield exists when the second bit of the supported channel width setting field is set to 1, and the second transmission bandwidth may be 20MHz, 40MHz, or 80MHz.

When the receiving STA operates in the 2.4GHz band, the second subfield exists when the first bit of the supported channel width setting field is set to 1, and the second transmission bandwidth may be 20MHz or 40MHz.

When the receiving STA is a non-AP STA operating at 20MHz or 80MHz and is allocated to the third transmission bandwidth, the second subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, the second subfield exists when the second bit of the supported channel width setting field is set to 1, and the third transmission bandwidth may be 160MHz or 320MHz.

That is, even if the receiving STA is a non-AP STA operating at 20MHz or 80MHz, it may be allocated to a third transmission bandwidth greater than a 20MHz or 80MHz channel for the receiving STA to operate, at which time the receiving STA may transmit the maximum number of spatial streams that may be transmitted or received for each MCS to the transmitting STA through the second subfield.

When the receiving STA is a non-AP STA operating at 160MHz or more and is allocated to the fourth transmission bandwidth, the third subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, when the third bit of the supported channel width setting field is set to 1, there is a third subfield, and the fourth transmission bandwidth may be 160MHz.

When the receiving STA is a non-AP STA operating at 160MHz and is allocated to a fifth transmission bandwidth, the third subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

When the receiving STA operates in the 5GHz or 6GHz band, when the third bit of the supported channel width setting field is set to 1, there is a third subfield, and the fifth transmission bandwidth may be 320MHz.

That is, even if the receiving STA is a non-AP STA operating at 160MHz, it may be allocated to a fifth transmission bandwidth larger than a 160MHz channel for the receiving STA to operate, at which time the receiving STA may transmit the maximum number of spatial streams that may be transmitted or received for each MCS to the transmitting STA through the third subfield.

When the receiving STA is a non-AP STA operating at 320MHz and is allocated to a sixth transmission bandwidth, the fourth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS.

The EHT capability element may also include a 320MHz subfield in 6GHz supported.

When the receiving STA operates in the 5GHz or 6GHz band, when the 320MHz subfield in the 6GHz supported is set to 1, there is a fourth subfield, and the sixth transmission bandwidth may be 320MHz.

That is, this embodiment proposes a method of signaling implemented by including information on the maximum number of spatial streams that can be transmitted or received for each supportable MCS in capability information when a receiving STA is allocated a transmission bandwidth greater than a channel for its operation and operates in a 2.4GHz band. This has the effect of improving overall throughput by applying the maximum number of spatial streams in more diverse situations.

The first subfield may include fifth through twelfth subfields. The fifth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS 0-7, the sixth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 0-7, the seventh subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS 8-9, the eighth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 8-9, the ninth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS10-11, the tenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS10-11, the eleventh subfield may correspond to a Max NSS subfield supporting EHT-MCS12-13, and the twelfth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 12-13.

The fifth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 7. The sixth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 0 to 7. The seventh subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 8 to 9. The eighth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 8 to 9. The ninth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11. The tenth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 10 to 11. The eleventh subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13. The twelfth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

Each of the second through fourth subfields may include thirteenth through eighteenth subfields. The thirteenth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS 0-9, the fourteenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 0-9, the fifteenth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS10-11, the sixteenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS10-11, the seventeenth subfield may correspond to an Rx Max NSS subfield supporting EHT-MCS12-13, and the eighteenth subfield may correspond to a Tx Max NSS subfield supporting EHT-MCS 12-13.

The thirteenth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 9. The fourteenth subfield may include information on the maximum number of spatial streams that the receiving STA may transmit when the MCS is 0 to 9. The fifteenth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11. The sixteenth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 10 to 11. The seventeenth subfield may include information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13. The eighteenth subfield may include information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

The fifth through eighteenth subfields may be composed of 4 bits. When the value of 4 bits is 1 to 8, the maximum number of spatial streams that the receiving STA can transmit in the specified MCS may be 1 to 8. When the value of 4 bits is 9 to 15, it is set to a reserved value, which may mean that the maximum number of spatial streams that a receiving STA can transmit in a specified MCS is greater than 8.

2. Device configuration

The technical features of the present disclosure may be applied to various apparatuses and methods. For example, features of the present disclosure may be performed/supported by the apparatus of fig. 1 and/or 11. For example, the technical features of the present disclosure may be applied to only a portion of fig. 1 and/or 11. For example, the technical features of the present disclosure may be implemented based on the processing chips 114 and 124 of fig. 1, or based on the processors 111 and 121 and the memories 112 and 122, or based on the processor 610 and the memory 620 of fig. 11. For example, an apparatus according to the present disclosure generates capability information of a receiving Station (STA); and transmitting capability information of the receiving STA to the transmitting STA.

The technical features of the present disclosure may be implemented based on a Computer Readable Medium (CRM). For example, CRM in accordance with the present disclosure is at least one computer-readable medium comprising instructions designed to be executed by at least one processor.

The CRM may store instructions to perform operations including generating capability information of a receiving Station (STA); and transmitting capability information of the receiving STA to the transmitting STA. The at least one processor may execute instructions stored in the CRM according to the present disclosure. The at least one processor associated with CRM of the present disclosure may be the processors 111, 121 of fig. 1, the processing chips 114, 124 of fig. 1, or the processor 610 of fig. 11. Further, CRM of the present disclosure may be memory 112, 122 of fig. 1, memory 620 of fig. 11, or a separate external memory/storage medium/disk.

The above technical features of the present specification can be applied to various applications or business models. For example, the above technical features may be applied to wireless communication of an Artificial Intelligence (AI) -enabled device.

Artificial intelligence refers to a research field about artificial intelligence or a method for creating artificial intelligence, and machine learning refers to a research field about a method for defining and solving various problems in the artificial intelligence field. Machine learning is also defined as an algorithm that improves operational performance through a steady operational experience.

An Artificial Neural Network (ANN) is a model used in machine learning, and may refer to a model that solves a problem as a whole, including artificial neurons (nodes) that form a network by combining synapses. The artificial neural network may be defined by a connection pattern between neurons of different layers, a learning process to update model parameters, and an activation function to generate output values.

The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron may output a function value of an activation function of an input signal input through synapses, weights, and deviations.

Model parameters refer to parameters determined by learning and include weights of synaptic connections and deviations of neurons. Super-parameters refer to parameters to be set before learning in a machine learning algorithm and include learning rate, number of iterations, minimum batch size, and initialization function.

Learning the artificial neural network may be aimed at determining model parameters for minimizing the loss function. The loss function may be used as an index to determine optimal model parameters in learning the artificial neural network.

Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning.

Supervised learning refers to a method of training an artificial neural network with labels given to training data, where when the training data is input to the artificial neural network, the labels may indicate correct answers (or result values) that the artificial neural network needs to infer. Unsupervised learning may refer to a method of training an artificial neural network without a tag given to training data. Reinforcement learning may refer to a training method for training agents defined in an environment to select actions or sequences of actions to maximize the jackpot per state.

Machine learning, which is implemented using a Deep Neural Network (DNN) including a plurality of hidden layers, among artificial neural networks is called deep learning, and deep learning is a part of machine learning. Hereinafter, machine learning is interpreted to include deep learning.

The foregoing technical features may be applied to wireless communication of a robot.

Robots may refer to machines that utilize their own capabilities to automatically process or operate a given task. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation may be referred to as an intelligent robot.

Robots can be classified into industrial, medical, home, military robots, etc., according to the purpose or field. The robot may include actuators or drives including motors to perform various physical operations, such as moving a robot joint. In addition, the movable robot may include wheels, brakes, propellers, etc. in the drive to travel on the ground or fly in the air by the drive.

The foregoing technical features may be applied to a device supporting augmented reality.

Augmented reality is collectively referred to as Virtual Reality (VR), augmented Reality (AR), and Mixed Reality (MR). VR technology is a computer graphics technology that provides real world objects and background only in CG images, AR technology is a computer graphics technology that provides virtual CG images on real object images, and MR technology is a computer graphics technology that provides virtual objects mixed and combined with the real world.

MR technology is similar to AR technology in that real and virtual objects can be displayed together. However, in the AR technique, a virtual object is used as a supplement to a real object, whereas in the MR technique, a virtual object and a real object are used as equivalent states.

XR technology may be applied to Head Mounted Displays (HMDs), head Up Displays (HUDs), mobile phones, tablets, laptops, desktop computers, televisions, digital signage, and the like. Devices that employ XR technology may be referred to as XR devices.

The claims disclosed in this specification may be combined in various ways. For example, the technical features in the method claims of the present specification may be combined to be implemented as a device, and the technical features in the device claims of the present specification may be combined to be implemented by a method. Furthermore, the technical features in the method claims and the apparatus claims of the present specification may be combined to be implemented as an apparatus, and the technical features in the method claims and the apparatus claims of the present specification may be combined to be implemented by a method.

Claims (20)

1. A method in a wireless local area network, WLAN, system, the method comprising the steps of:

Generating capability information of a receiving Station (STA); and

transmitting the capability information of the receiving STA to a transmitting STA by the receiving STA,

wherein the capability information of the receiving STA includes a high efficiency HE capability element and an extremely high throughput EHT capability element,

wherein the HE capability element includes a supported channel width setting field,

wherein the EHT capability element includes a supported EHT-modulation and coding scheme MCS and a spatial stream number NSS set field,

wherein the supported EHT-MCS and NSS setting fields include first through fourth subfields,

wherein when the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in 5GHz and 6GHz bands, the first subfield exists when the second to fourth bits of the supported channel width setting field are all set to 0, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz or 320MHz, and

wherein when the receiving STA operates in a 2.4GHz band, the first subfield exists when a first bit of the supported channel width setting field is set to 0, and the first transmission bandwidth is 20MHz or 40MHz.

2. The method of claim 1, wherein, when the receiving STA is a non-AP STA operating at 80MHz or more and is allocated to a second transmission bandwidth, the second subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the second subfield exists when a second bit of the supported channel width setting field is set to 1, and the second transmission bandwidth is 20MHz, 40MHz, or 80MHz, and

wherein when the receiving STA operates in a 2.4GHz band, the second subfield exists when a first bit of the supported channel width setting field is set to 1, and the second transmission bandwidth is 20MHz or 40MHz.

3. The method of claim 2, wherein, when the receiving STA is a non-AP STA operating at 20MHz or 80MHz and is allocated to a third transmission bandwidth, the second subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the second subfield exists when a second bit of the supported channel width setting field is set to 1, and the third transmission bandwidth is 160MHz or 320MHz.

4. The method of claim 3, wherein when the receiving STA is a non-AP STA operating at 160MHz or higher and is allocated to a fourth transmission bandwidth, a third subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the third subfield exists when a third bit of the supported channel width setting field is set to 1, and the fourth transmission bandwidth is 160MHz.

5. The method of claim 4, wherein when the receiving STA is a non-AP STA operating at 160MHz and is allocated to a fifth transmission bandwidth, the third subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the third subfield exists when a third bit of the supported channel width setting field is set to 1, and the fifth transmission bandwidth is 320MHz.

6. The method of claim 5, wherein, when the receiving STA is a non-AP STA operating at 320MHz and is allocated to a sixth transmission bandwidth, the fourth subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

Wherein the EHT capability element is further capable of including a 320MHz subfield in 6GHz,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the fourth subfield exists when the 320MHz subfield in the 6 GHz-capable band is set to 1, and the sixth transmission bandwidth is 320MHz.

7. The method of claim 6, wherein the first subfield includes fifth to twelfth subfields,

wherein the fifth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 7,

wherein the sixth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 0 to 7,

wherein the seventh subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 8 to 9,

wherein the eighth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 8 to 9,

wherein the ninth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11,

wherein the tenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 10 to 11,

Wherein the eleventh subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13,

wherein the twelfth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

8. The method of claim 7, wherein each of the second through fourth subfields includes thirteenth through eighteenth subfields,

wherein the thirteenth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 9,

wherein the fourteenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 0 to 9,

wherein the fifteenth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11,

wherein the sixteenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 10 to 11,

wherein the seventeenth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13,

wherein the eighteenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

9. A receiving station STA in a wireless local area network WLAN system, the receiving STA comprising:

a memory;

a transceiver; and

a processor operatively connected to the memory and the transceiver,

wherein the processor is configured to:

generating capability information of the receiving STA; and

transmitting the capability information of the receiving STA to a transmitting STA,

wherein the capability information of the receiving STA includes a high efficiency HE capability element and an extremely high throughput EHT capability element,

wherein the HE capability element includes a supported channel width setting field,

wherein the EHT capability element includes a supported EHT-modulation and coding scheme MCS and a spatial stream number NSS set field,

wherein the supported EHT-MCS and NSS setting fields include first through fourth subfields,

wherein when the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in 5GHz and 6GHz bands, the first subfield exists when the second to fourth bits of the supported channel width setting field are all set to 0, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz or 320MHz, and

Wherein when the receiving STA operates in a 2.4GHz band, the first subfield exists when a first bit of the supported channel width setting field is set to 0, and the first transmission bandwidth is 20MHz or 40MHz.

10. A method in a wireless local area network, WLAN, system, the method comprising the steps of:

receiving, by a transmitting station STA, capability information of a receiving STA from the receiving STA; and

decoding the capability information of the receiving STA by the transmitting STA,

wherein the capability information of the receiving STA includes a high efficiency HE capability element and an extremely high throughput EHT capability element,

wherein the HE capability element includes a supported channel width setting field,

wherein the EHT capability element includes a supported EHT-modulation and coding scheme MCS and a spatial stream number NSS set field,

wherein the supported EHT-MCS and NSS setting fields include first through fourth subfields,

wherein when the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

Wherein when the receiving STA operates in 5GHz and 6GHz bands, the first subfield exists when the second to fourth bits of the supported channel width setting field are all set to 0, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz or 320MHz, and

wherein when the receiving STA operates in a 2.4GHz band, the first subfield exists when a first bit of the supported channel width setting field is set to 0, and the first transmission bandwidth is 20MHz or 40MHz.

11. The method of claim 10, wherein when the receiving STA is a non-AP STA operating at 80MHz or more and is allocated to a second transmission bandwidth, the second subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the second subfield exists when a second bit of the supported channel width setting field is set to 1, and the second transmission bandwidth is 20MHz, 40MHz, or 80MHz, and

wherein when the receiving STA operates in a 2.4GHz band, the second subfield exists when a first bit of the supported channel width setting field is set to 1, and the second transmission bandwidth is 20MHz or 40MHz.

12. The method of claim 11, wherein when the receiving STA is a non-AP STA operating at 20MHz or 80MHz and is allocated to a third transmission bandwidth, the second subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the second subfield exists when a second bit of the supported channel width setting field is set to 1, and the third transmission bandwidth is 160MHz or 320MHz.

13. The method of claim 12, wherein when the receiving STA is a non-AP STA operating at 160MHz or more and is allocated to a fourth transmission bandwidth, a third subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the third subfield exists when a third bit of the supported channel width setting field is set to 1, and the fourth transmission bandwidth is 160MHz.

14. The method of claim 13, wherein when the receiving STA is a non-AP STA operating at 160MHz and is allocated to a fifth transmission bandwidth, the third subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

Wherein when the receiving STA operates in a 5GHz or 6GHz band, the third subfield exists when a third bit of the supported channel width setting field is set to 1, and the fifth transmission bandwidth is 320MHz.

15. The method of claim 14, wherein, when the receiving STA is a non-AP STA operating at 320MHz and is allocated to a sixth transmission bandwidth, the fourth subfield includes information on a maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein the EHT capability element is further capable of including a 320MHz subfield in 6GHz,

wherein when the receiving STA operates in a 5GHz or 6GHz band, the fourth subfield exists when the 320MHz subfield in the 6 GHz-capable band is set to 1, and the sixth transmission bandwidth is 320MHz.

16. The method of claim 15, wherein the first subfield includes fifth to twelfth subfields,

wherein the fifth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 7,

wherein the sixth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 0 to 7,

Wherein the seventh subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 8 to 9,

wherein the eighth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 8 to 9,

wherein the ninth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11,

wherein the tenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 10 to 11,

wherein the eleventh subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13,

wherein the twelfth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

17. The method of claim 16, wherein each of the second through fourth subfields includes thirteenth through eighteenth subfields,

wherein the thirteenth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 0 to 9,

wherein the fourteenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 0 to 9,

Wherein the fifteenth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 10 to 11,

wherein the sixteenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 10 to 11,

wherein the seventeenth subfield includes information on the maximum number of spatial streams that the receiving STA can receive when the MCS is 12 to 13,

wherein the eighteenth subfield includes information on the maximum number of spatial streams that the receiving STA can transmit when the MCS is 12 to 13.

18. A transmitting station STA in a wireless local area network WLAN system, the transmitting STA comprising:

a memory;

a transceiver; and

a processor operatively connected to the memory and the transceiver,

wherein the processor is configured to:

receiving capability information of a receiving STA from the receiving STA; and

decoding the capability information of the receiving STA,

wherein the capability information of the receiving STA includes a high efficiency HE capability element and an extremely high throughput EHT capability element,

wherein the HE capability element includes a supported channel width setting field,

Wherein the EHT capability element includes a supported EHT-modulation and coding scheme MCS and a spatial stream number NSS set field,

wherein the supported EHT-MCS and NSS setting fields include first through fourth subfields,

wherein when the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in 5GHz and 6GHz bands, the first subfield exists when the second to fourth bits of the supported channel width setting field are all set to 0, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz or 320MHz, and

wherein when the receiving STA operates in a 2.4GHz band, the first subfield exists when a first bit of the supported channel width setting field is set to 0, and the first transmission bandwidth is 20MHz or 40MHz.

19. A computer-readable medium comprising instructions that are executed by at least one processor and perform a method comprising:

Generating capability information of a receiving Station (STA); and

transmitting the capability information of the receiving STA to a transmitting STA,

wherein the capability information of the receiving STA includes a high efficiency HE capability element and an extremely high throughput EHT capability element,

wherein the HE capability element includes a supported channel width setting field,

wherein the EHT capability element includes a supported EHT-modulation and coding scheme MCS and a spatial stream number NSS set field,

wherein the supported EHT-MCS and NSS setting fields include first through fourth subfields,

wherein when the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in 5GHz and 6GHz bands, the first subfield exists when the second to fourth bits of the supported channel width setting field are all set to 0, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz or 320MHz, and

wherein when the receiving STA operates in a 2.4GHz band, the first subfield exists when a first bit of the supported channel width setting field is set to 0, and the first transmission bandwidth is 20MHz or 40MHz.

20. An apparatus in a wireless local area network, WLAN, system, the apparatus comprising:

a memory; and

a processor operatively connected to the memory,

wherein the processor is configured to:

generating capability information of a receiving Station (STA); and

transmitting the capability information of the receiving STA to a transmitting STA,

wherein the capability information of the receiving STA includes a high efficiency HE capability element and an extremely high throughput EHT capability element,

wherein the HE capability element includes a supported channel width setting field,

wherein the EHT capability element includes a supported EHT-modulation and coding scheme MCS and a spatial stream number NSS set field,

wherein the supported EHT-MCS and NSS setting fields include first through fourth subfields,

wherein when the receiving STA is a non-AP STA operating only at 20MHz and is allocated to a first transmission bandwidth, the first subfield includes information on the maximum number of spatial streams that the receiving STA can transmit and receive in each MCS,

wherein when the receiving STA operates in 5GHz and 6GHz bands, the first subfield exists when the second to fourth bits of the supported channel width setting field are all set to 0, and the first transmission bandwidth is 20MHz, 40MHz, 80MHz, 160MHz or 320MHz, and

Wherein when the receiving STA operates in a 2.4GHz band, the first subfield exists when a first bit of the supported channel width setting field is set to 0, and the first transmission bandwidth is 20MHz or 40MHz.