Method and device for exchanging capability information in wireless LAN system

Abstract

The present disclosure relates to a method and a device for exchanging capability information about whether UL MU-MIMO is supported for a partial bandwidth in a wireless LAN system. Specifically, an AP exchanges capability information with a non-AP STA and transmits a trigger frame to the non-AP STA. The capability information includes information about whether the UL MU-MIMO is supported for the partial bandwidth. The trigger frame requests a TB PPDU based on a bandwidth that is greater than or equal to 160 MHz. The trigger frame includes allocation information about an RU or an MRU in which the UL MU-MIMO is supported for the partial bandwidth. For the partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks.

Description

Method and device for exchanging capability information in a wireless LAN system

[0001] This specification relates to wireless LAN systems, and more specifically, to methods and apparatus related to partial bandwidth UL (uplink) MU-MIMO (Multi-User Multiple Input Multiple Output).

[0002] Wireless LANs or WLANs (wireless local area networks) have been improved in various ways. For example, the Extreme High Throughput (EHT) standard can utilize newly proposed increased bandwidth, an improved PPDU (PHY layer protocol data unit) structure, improved sequencing, and the Hybrid Automatic Repeat Request (HARQ) technique. The EHT standard can be referred to as the IEEE 802.11be standard.

[0003] To support high throughput and high data rates, the EHT standard may use wide bandwidth (e.g., 160 / 320 MHz), 16 streams, and / or multi-link (or multi-band) operation.

[0004] In the EHT standard, wide bandwidth (e.g., 160 / 240 / 320 MHz) can be used for high throughput. In addition, preamble puncturing and multiple RU transmission can be used to efficiently utilize bandwidth.

[0005] WLAN systems can be further improved through the Ultra High Reliability (UHR) standard. The UHR system may be referred to as the IEEE 802.11bn standard. The UHR system aims to support ultra-high reliability during signal transmission to STAs. To achieve this, various technologies are being considered for high throughput, low latency, and extended range support.

[0006] Additionally or generally, next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs, and to this end, various technologies are being considered to support high throughput, low latency, and extended range. For example, to increase spectrum efficiency, Multi-User Multiple Input Multiple Output (MU-MIMO) can be used for partial bandwidths.

[0007] The present specification proposes a method and apparatus for exchanging capability information for an RU or MRU that supports UL MU-MIMO for a partial bandwidth in a wireless LAN system.

[0008] For example, the technical problem to be solved in this specification may be as follows.

[0009] For example, to improve signal transmission and reception efficiency using UL MU-MIMO in a wireless LAN system, MU-MIMO operation based on partial bandwidth rather than the total bandwidth may be considered. In particular, UL MU-MIMO combined with OFDMA transmission in high-bandwidth environments can provide flexibility in terms of resource utilization; however, if the method of applying MU-MIMO at the partial bandwidth level is not clearly established, there is a possibility of unnecessary complexity arising during the system design and operation process.

[0010] For example, to apply UL MU-MIMO to a partial bandwidth, the size and shape of the RU or MRU to be used for the transmission must be defined in advance; however, conventional technology has not sufficiently provided consistent criteria for RU / MRU configuration based on bandwidth size (e.g., 160 MHz or 320 MHz) and whether preamble puncturing is performed. As a result, additional control signal exchange or complex decision logic may be required during the resource allocation and scheduling process between the AP and the non-AP STA.

[0011] Furthermore, if capability information regarding UL MU-MIMO support is not clearly distinguished in terms of full bandwidth and partial bandwidth, there is a possibility of mutual misunderstanding or inefficient transmission configuration during the process of requesting or configuring trigger-based UL transmissions (TB PPDU). Accordingly, systematically organizing the applicable range of UL MU-MIMO by bandwidth size and transmission method, and providing signaling procedures based on this, can be recognized as a technical challenge.

[0012] One example of the present specification proposes a method for conveying information about an RU or MRU that supports UL MU-MIMO for a partial bandwidth through a trigger frame set based on capability information regarding whether UL MU-MIMO is supported for a partial bandwidth.

[0013] This embodiment can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0014] This embodiment can be performed at an access point (AP). The AP can be replaced with an access point Multi-link Device (AP MLD). The non-access point Station (non-AP STA) of this embodiment can be replaced with a non-AP MLD.

[0015] The present embodiment proposes a method for exchanging capability information regarding whether UL MU-MIMO is supported for a partial bandwidth in order to efficiently transmit TB PPDU using UL MU-MIMO. Specifically, it proposes a method for transmitting allocation information regarding a RU or MRU that supports UL MU-MIMO by transmitting a trigger frame based on capability information regarding whether UL MU-MIMO is supported for a partial bandwidth.

[0016] AP (access point) exchanges capability information with non-AP STA (non-access point station).

[0017] The above AP transmits a trigger frame to the above non-AP STA based on the above capability information.

[0018] The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth.

[0019] The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more.

[0020] The above trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the above partial bandwidth.

[0021] For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. That is, in order to efficiently transmit and receive TB PPDU (Trigger-Based Physical Protocol Data Unit) using defined transmission constraints or rules when UL OFDMA (Uplink Orthogonal Frequency Division Multiple Access) and MU-MIMO (Multi-User Multiple Input Multiple Output) are used simultaneously, the UHR (Ultra High Reliability) AP and non-AP STA exchange capability information. After the capability information is exchanged, the AP transmits a trigger frame requesting a TB PPDU in order to use UL OFDMA and MU-MIMO together when transmitting the TB PPDU.

[0022] In this specification, MU-MIMO during UL OFDMA is supported when the BW (Bandwidth) of the TB PPDU is 160 MHz or higher.

[0023] For example, based on the fact that the bandwidth of the TB PPDU is 160 MHz, the RU or MRU that supports the UL MU-MIMO for the said partial bandwidth may be limited to 996-tone RU if there is no preamble puncturing in the TB PPDU, and may be limited to 484+242-tone MRU if there is preamble puncturing in the TB PPDU.

[0024] The bandwidth of the above TB PPDU can be composed of two consecutive 80 MHz frequency subblocks.

[0025] The above 484+242-tone MRU may exist within one of the two consecutive 80 MHz frequency subblocks.

[0026] As another example, based on the fact that the bandwidth of the TB PPDU is 320 MHz, the RU or MRU that supports the UL MU-MIMO for the said partial bandwidth may be limited to 2x996-tone RU or 3x996-tone RU if there is no preamble puncturing in the TB PPDU, and may be limited to 996+484-tone MRU or 2x996+484-tone MRU if there is preamble puncturing in the TB PPDU.

[0027] The bandwidth of the above TB PPDU can be composed of four consecutive 80 MHz frequency subblocks.

[0028] The above 996+484-tone MRU may exist within two consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks.

[0029] The above 2x996+484-tone MRU may exist within three consecutive 80 MHz frequency subblocks among the above four consecutive 80 MHz frequency subblocks.

[0030] That is, the present embodiment proposes a method for setting a trigger frame to request a TB PPDU transmitted over a 160 MHz or 320 MHz bandwidth when UL MU-MIMO is supported for a partial bandwidth. Specifically, the present embodiment proposes a method for transmitting the TB PPDU based on OFDMA and UL MU-MIMO by allocating a limited RU or MRU that supports UL MU-MIMO through the trigger frame.

[0031] The effects of this specification may be expressed in various ways as follows.

[0032] For example, according to the method proposed in this specification, by setting a trigger frame based on capability information regarding whether UL MU-MIMO is supported for a partial bandwidth, the use of MU-MIMO is increased during signal transmission using OFDMA, and the MU-MIMO can be used efficiently. By setting constraints on the size of the RU or MRU that supports UL MU-MIMO for a partial bandwidth, spectral efficiency can be increased.

[0033] More specifically, in one embodiment according to the present specification, an approach may be proposed to define the size and combination of available RUs or MRUs based on bandwidth size and whether preamble puncturing is performed, so that UL MU-MIMO can be applied in a partial bandwidth unit in an OFDMA transmission environment. This configuration may contribute to mitigating processing complexity on the AP and non-AP STA sides by limiting the range of resource selections to be considered when operating UL MU-MIMO.

[0034] In addition, predictability during the TB PPDU setup process can be increased through a structure that exchanges capability information regarding whether UL MU-MIMO is supported for a partial bandwidth and includes RU / MRU allocation information in the trigger frame based on this. This can help flexibly configure UL transmission in various bandwidth environments (e.g., 160 MHz or 320 MHz) and, consequently, contribute to increasing the utilization of OFDMA-based UL MU-MIMO transmission.

[0035] In addition, by distinguishing between whether UL MU-MIMO is supported for the entire bandwidth and whether it is supported for a partial bandwidth, it is possible to provide room to selectively operate OFDMA-based transmission and non-OFDMA-based transmission depending on the situation. This structure can contribute to securing scalability from the perspective of system implementation and is expected to have a positive effect in promoting relatively efficient UL MU-MIMO transmission even in environments where various combinations of STA capabilities are mixed.

[0036] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

[0037] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0038] Figure 3 is a diagram illustrating a general link setup process.

[0039] FIG. 4 illustrates an example of a multi-link (ML).

[0040] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.

[0041] Figure 6 is a diagram showing the arrangement of resource units (RU) used for a 20 MHz PPDU.

[0042] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0043] Figure 8 is a diagram showing the arrangement of resource units (RU) used for an 80 MHz PPDU.

[0044] Figure 9 shows the operation according to UL-MU.

[0045] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0046] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0047] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0048] Figure 13 shows an example of a MAC frame header.

[0049] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.

[0050] Figure 15 illustrates an example of the UHR Capabilities Information field.

[0051] FIG. 16 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0052] FIG. 17 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0053] FIG. 18 is a flowchart illustrating a procedure for an AP to transmit a trigger frame based on capability information exchanged with a non-AP according to the present embodiment.

[0054] FIG. 19 is a flowchart illustrating the procedure for a non-AP STA to receive a trigger frame from an AP according to the present embodiment.

[0055] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0056] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "B or C."

[0057] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0058] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (UHR-Signal field)," the "UHR-Signal field" may be proposed as an example of "control information." In other words, the "control information" of this specification is not limited to the "UHR-Signal field," and the "UHR-Signal field" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (UHR-Signal field)," the "UHR-Signal field" may be proposed as an example of "control information."

[0059] Additionally, "a / an" as used in this specification may mean "at least one" or "one or more." Also, terms ending in "(s)" may mean "at least one" or "one or more."

[0060] Additionally, the expressions "based on," "on the basis of," or "according to" as used in this specification mean "based at least in part on" and do not mean "based only on".

[0061] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0062] The following examples of this specification may be applied to various wireless communication systems. For example, the following examples of this specification may be applied to wireless local area network (WLAN) systems. For example, this specification may be applied to IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification may be applied to Ultra High Reliability (UHR) standards or next-generation wireless LAN standards that enhance IEEE 802.11bn. In addition, the examples of this specification may be applied to mobile communication systems. For example, they may be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on 3GPP (3rd Generation Partnership Project) standards.

[0063] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0064] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

[0065] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of this specification may also be referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. The STA (110, 120) of this specification may also be referred to by various names such as network, base station, Node-B, Access Point (AP), repeater, router, relay, etc. The STA (110, 120) of this specification may also be referred to by various names such as receiving apparatus, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.

[0066] For example, the STA (110, 120) can perform the role of an access point (AP) or a non-AP. That is, the STA (110, 120) of this specification can perform the functions of an AP and / or a non-AP. In this specification, an AP may also be indicated as an AP STA.

[0067] The STA (110, 120) of this specification may support various communication standards other than the IEEE 802.11 standard. For example, it may support communication standards according to 3GPP standards (e.g., LTE, LTE-A, 5G NR standards). In addition, the STA of this specification may be implemented in various devices such as mobile phones, vehicles, and personal computers. Furthermore, the STA of this specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving.

[0068] In this specification, the STA (110, 120) may include a medium access control (MAC) that complies with the provisions of the IEEE 802.11 standard and a physical layer interface for the wireless medium.

[0069] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0070] The first STA (110) may include a processor (111), memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.

[0071] The transceiver (113) of the first STA performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0072] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmitted signal, and perform control for transmitting the signal. The memory (112) of the AP can store the signal received through the transceiver (113) (i.e., the received signal) and the signal to be transmitted through the transceiver (i.e., the transmitted signal).

[0073] For example, the second STA (120) can perform the intended operation of a Non-AP STA. For example, the non-AP transceiver (123) performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0074] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmitted signal, and perform control for transmitting the signal. The memory (122) of the Non-AP STA can store the signal received through the transceiver (123) (i.e., the received signal) and can store the signal to be transmitted through the transceiver (i.e., the transmitted signal).

[0075] For example, the operation of the device indicated as AP in the following specification may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (111) of the first STA (110), and related signals may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). Additionally, control information related to the operation of the AP or the transmission / reception signals of the AP may be stored in the memory (112) of the first STA (110). Additionally, if the second STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signals of the AP can be stored in the memory (122) of the second STA (110).

[0076] For example, the operation of a device indicated as non-AP (or User-STA) in the following specification may be performed in the 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 is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signals of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of the device marked as non-AP is controlled by the processor (111) of the first STA (110), and the related signal can be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signal of the AP can be stored in the memory (112) of the first STA (110).

[0077] In the following specification, a device referred to as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, a device indicated without specific drawing symbols as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may also refer to the STA (110, 120) of FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. Additionally, in the following example, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation to generate a transmission / reception signal or to perform data processing or operations in advance for a transmission / reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of sub-fields (SIG, STF, LTF, Data) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 4) a power control operation and / or power saving operation applied to the STA; and 5) an operation related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (112, 122) of FIG. 1.

[0078] The device / STA of the aforementioned supplementary drawing (a) of FIG. 1 can be modified as shown in supplementary drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of this specification will be described based on supplementary drawing (b) of FIG. 1.

[0079] For example, the transceiver (113, 123) shown in side drawing (b) of FIG. 1 can perform the same function as the transceiver shown in side drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) shown in side drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and memory (112, 122) shown in side drawing (b) of FIG. 1 can perform the same function as the processor (111, 121) and memory (112, 122) shown in side drawing (a) of FIG. 1 described above.

[0080] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, User STA, network, Base Station, Node-B, AP (Access Point), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or the processing chip (114, 124) shown in side drawing (b) of FIG. 1. That is, the technical features of the present specification may be performed in the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or only in the processing chip (114, 124) shown in side drawing (b) of FIG. 1. For example, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal generated in the processor (111, 121) shown in side drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) shown in side drawings (a) / (b) of FIG. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal to be transmitted from the processing chip (114, 124) shown in side drawing (b) of FIG. 1 is generated to the transceiver (113, 123).

[0081] For example, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal being received by the transceivers (113, 123) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceivers (113, 123) shown in side view (a) of FIG. 1 being acquired by the processor (111, 121) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceivers (113, 123) shown in side view (b) of FIG. 1 being acquired by the processing chip (114, 124) shown in side view (b) of FIG. 1.

[0082] Referring to side view (b) of FIG. 1, software code (115, 125) may be included in memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.

[0083] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or a processor enhanced therefrom.

[0084] In this specification, an uplink may refer to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted through the uplink. Additionally, in this specification, a downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted through the downlink.

[0085] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0086] The top of Figure 2 shows the structure of the basic service set (BSS) infrastructure of IEEE (Institute of Electrical and Electronic Engineers) 802.11.

[0087] The top of Figure 2 shows the structure of the basic service set (BSS) infrastructure of IEEE (Institute of Electrical and Electronic Engineers) 802.11.

[0088] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter BSS). The BSS (200, 205) is a set of APs and STAs, such as an AP (access point, 225) and STA1 (Station, 200-1), that can communicate with each other by successfully synchronizing, and is not a concept referring to a specific area. The BSS (205) may include one or more STAs (205-1, 205-2) that can be combined with one AP (230).

[0089] The BSS may include at least one STA, an AP (225, 230) that provides a distribution service, and a distribution system (DS, 210) that connects multiple APs.

[0090] A distributed system (210) can implement an extended service set (ESS, 240) by connecting multiple BSSs (200, 205). The term ESS (240) may be used to refer to a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) may have the same service set identification (SSID).

[0091] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) with another network (e.g., 802.X).

[0092] In a BSS like the one at the top of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network between STAs and perform communication without APs (225, 230). A network that establishes a network between STAs and performs communication without APs (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0093] The bottom of Fig. 2 is a conceptual diagram showing IBSS.

[0094] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity that performs management functions centrally. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and since access to the distributed system is not allowed, they form a self-contained network.

[0095] Figure 3 is a diagram illustrating a general link setup process.

[0096] In the described S310 step, the STA can perform a network discovery operation. The network discovery operation may include the STA's scanning operation. That is, in order for the STA to access a network, it must find a network it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0097] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels and transmits a probe request frame to search for nearby APs, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame, whereas in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (i.e., transmit and receive probe request / response on channel 2).

[0098] Although not shown in the example of Fig. 3, scanning operations may also be performed using a passive scanning method. An STA performing scanning based on passive scanning can wait for a beacon frame while switching between channels. A beacon frame is one of the management frames in IEEE 802.11, which announces the presence of a wireless network and is periodically transmitted to allow a scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS take turns transmitting beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. An STA that has received a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner.

[0099] The STA that discovered the network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described later. The authentication process of S320 may include the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.

[0100] The authentication frame may include information regarding the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), Finite Cyclic Group, etc.

[0101] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.

[0102] A successfully authenticated STA may perform an association process based on step S330. The association process includes the STA sending an association request frame to the AP, and in response, the AP sending an association response frame to the STA. For example, the association request frame may include information regarding various capabilities, beacon listen interval, service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, Traffic Indication Map Broadcast request, interworking service capabilities, etc. For example, a connection response frame may include information related to various capabilities, status code, AID (Association ID), support rate, EDCA (Enhanced Distributed Channel Access) parameter set, RCPI (Received Channel Power Indicator), RSNI (Received Signal to Noise Indicator), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS map, etc.

[0103] Subsequently, in step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame.

[0104] FIG. 4 illustrates an example of a multi-link (ML).

[0105] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate through a multi-link. The MLDs can be classified into an AP MLD containing multiple AP STAs and a non-AP MLD containing multiple non-AP STAs. That is, the AP MLD may include affiliated APs (i.e., AP STAs), and the non-AP MLD may include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0106] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be assigned to the first and second links. The first and second multilinks may be identified by a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the link may be configured in different bands.

[0107] The AP MLD of FIG. 4 includes three affiliated APs. In one example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In one example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Additionally, in one example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Additionally, in one example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.

[0108] In one example of FIG. 4, AP1 can initiate a multilink setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In one example of FIG. 4, non-AP STA1 can transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) shown in FIG. 4 may be the same as the AP shown in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) shown in FIG. 4 may be the same as the STA shown in FIG. 1 and / or FIG. 2 (i.e., user-STA or non-AP STA).

[0109] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.

[0110] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.

[0111] The STAs of this specification (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) can transmit and / or receive the PPDU of FIG. 5. The PPDU described in this specification may have the structure of FIG. 5, for example. Additionally, the PPDU described in this specification, the Ultra High Reliability (UHR) PPDU, may be referred to by various names such as transmit PPDU, receive PPDU, first type or N type PPDU. The PPDU described in this specification may be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that improve upon IEEE 802.11bn.

[0112] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of SU (single-user) mode / type / transmission, MU (multi-user) mode / type / transmission, and NDP (null data packet) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the illustrated Data field may be omitted. If the PPDU of FIG. 5 is used for TB (Trigger-based) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that receives a Trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU in which the UHR-SIG is omitted in the example of FIG. 5.

[0113] In FIG. 5, L-STF to UHR-LTF can be called a preamble or physical preamble and can be generated / transmitted / received / acquired / decoded at the physical layer (included in the transmitting / receiving STA).

[0114] Each block illustrated in FIG. 5 may be referred to as a field / subfield / signal, etc. As illustrated in FIG. 5, the names of these fields / subfields / signals may be L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.

[0115] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in Fig. 5 can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be displayed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be displayed in units of 78.125 kHz.

[0116] The PPDU of Fig. 5, L-LTF and L-STF, may be the same as conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0117] The L-SIG field of FIG. 5 may contain, for example, 24 bits of bit information. For example, the 24 bits of information may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity bit, and a 6-bit Tail bit. For example, the 12-bit Length field may contain information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU, or a UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is an HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, or EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High-Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in a UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0118] For example, a (non-AP and AP) STA can apply BCC encoding based on a code rate of 1 / 2 to 24 bits of information in the L-SIG field. Subsequently, the transmitting STA can obtain 48 bits of BCC encoding. BPSK modulation can be applied to the 48 bits of encoding to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarrier {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. Consequently, the 48 BPSK symbols can be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can additionally map the signal of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0119] For example, the (non-AP and AP) STA can generate an RL-SIG that is identical to the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine that the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the HE PPDU, EHT PPDU, or UHR PPDU if the RL-SIG is present. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the non-HT PPDU, HT PPDU, or VHT PPDU if the RL-SIG is not present. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.

[0120] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be referred to by various names such as the first SIG field, first SIG, first type SIG, control signal, control signal field, first (type) control signal, common control field, and common control signal.

[0121] U-SIG may contain N bits of information and may contain information to identify the type of EHT PPDU. For example, U-SIG may be constructed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol for U-SIG (e.g., OFDM symbol) may have a duration of 4 us. Each symbol of U-SIG may be used to transmit 26 bits of information. For example, each symbol of U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.

[0122] For example, A bit information (e.g., 52 un-coded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bit information (e.g., 26 un-coded bits) of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bit information (e.g., 26 un-coded bits) of the total A bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can generate 52-coded bits by performing convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 and can perform interleaving on the 52-coded bits. The transmitting STA can generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers), excluding the pilot tones -21, -7, +7, and +21.

[0123] For example, A bit information (e.g., 52 un-coded bits) transmitted by U-SIG may include a CRC field (e.g., a field of 4 bits) and a tail field (e.g., a field of 6 bits). The CRC field and the tail field may be transmitted through a second symbol of U-SIG. The CRC field may be generated based on 26 bits assigned to the first symbol of U-SIG and the remaining 16 bits within the second symbol excluding the CRC / tail field, and may be generated based on a conventional CRC calculation algorithm. Additionally, the tail field may be used to terminate the trellis of a convolutional decoder and may be set, for example, to "000000".

[0124] A bit information (e.g., 52 un-coded bits) transmitted by U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.

[0125] For example, the version-independent bits of 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 transmitted and received PPDU. For example, a first value of the 3-bit PHY version identifier (e.g., a value of 000) may indicate that the transmitted and received PPDU is an EHT PPDU. Additionally, a second value of the 3-bit PHY version identifier (e.g., a value of 001) may indicate that the transmitted and received PPDU is a UHR PPDU.

[0126] In other words, when an (AP / non-AP) STA transmits an EHT PPDU, it can set a 3-bit PHY version identifier to a first value. In other words, a receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is a UHR PPDU based on the PHY version identifier having the second value.

[0127] For example, the version-independent bits of U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.

[0128] For example, the version-independent bits of U-SIG may include information regarding the length of the TXOP (transmission opportunity) and information regarding the BSS color ID.

[0129] For example, if the UHR PPDU is classified into various types (e.g., type related to SU transmission (performed based on UL or DL), type related to DL transmission, type related to NDP transmission, type related to DL non-MU-MIMO, type related to DL MU-MIMO, type related to Multi-AP operation, type related to CBF (Coordinated beamforming) and SR (Spatial Reuse), type related to C-OFDMA (Coordinated OFDMA), type related to C-TDMA (Coordinated TDMA)), information regarding the type of the EHT PPDU (e.g., 2-bit or 3-bit information) may be included in the version-dependent bits of the U-SIG.

[0130] For example, U-SIG may include: 1) a bandwidth field containing information regarding bandwidth; 2) a field containing information regarding the MCS technique applied to UHR-SIG; 3) an indication field containing information regarding whether the dual subcarrier modulation (DCM) technique is applied to UHR-SIG; 4) a field containing information regarding the number of symbols used for UHR-SIG; 5) a field containing information regarding whether UHR-SIG is generated across the entire band; 6) a field containing information regarding the type of UHR-LTF / STF; and 7) information regarding a field indicating the length of UHR-LTF and CP length.

[0131] Preamble puncturing may be applied to the PPDU of Fig. 5. Preamble puncturing means applying puncturing to a portion of the total band of the PPDU (e.g., a secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band within the 80 MHz band and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0132] For example, the pattern of preamble puncturing can be pre-set. For example, when a first puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band within an 80 MHz band. For example, when a second puncturing pattern is applied, puncturing may be applied only to one of two secondary 20 MHz bands included in a secondary 40 MHz band within an 80 MHz band. For example, when a third puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band included in a primary 80 MHz band within a 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, within the 160 MHz band (or 80+80 MHz band), the primary 40 MHz band included in the primary 80 MHz band is present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.

[0133] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.

[0134] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured individually in 80 MHz units. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information regarding a 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern). Meanwhile, the UHR-SIG following the first U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern), and the UHR-SIG following the second U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding a preamble puncturing pattern).

[0135] Additionally or generally, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).

[0136] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth may contain different U-SIGs.

[0137] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.

[0138] UHR-SIG provides additional signals to the U-SIG field, enabling the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that apply commonly to all users. Additionally, the UHR-SIG field contains resource allocation information, making it possible for the STA to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

[0139] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on a RU (resource unit) defined by a plurality of subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through a RU (resource unit) defined by a plurality of subcarriers / tones.

[0140] FIG. 6 is a diagram showing the arrangement of resource units (RUs) used for a 20 MHz PPDU. That is, UHR-LTF, UHR-STF and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.

[0141] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) may be arranged. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Additionally, seven DC tones are inserted into the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on the left and right sides of the DC band. Furthermore, 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

[0142] Meanwhile, the RU arrangement of Fig. 6 is utilized not only for situations involving multiple users (MU) but also for situations involving a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of Fig. 4, and in this case, three DC tones can be inserted.

[0143] In the example of FIG. 6, various sizes of RUs, namely 26-RU, 52-RU, 106-RU, 242-RU, etc., are proposed. Since the specific size of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be indicated as N-tone RU, etc. For example, 26-RU may be indicated as 26-tone RU.

[0144] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0145] Just as various sizes of RUs were used in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may also be used in the example of FIG. 7. Additionally, 5 DC tones may be inserted at the center frequency, 12 tones may be used as guard bands in the leftmost band of the 40 MHz band, and 11 tones may be used as guard bands in the rightmost band of the 40 MHz band.

[0146] In addition, as described, 484-RU may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.

[0147] FIG. 8 is a diagram showing the arrangement of resource units (RUs) used for an 80 MHz PPDU. The arrangement of resource units (RUs) used in this specification may be varied. For example, the arrangement of resource units (RUs) used in the 80 MHz band may be varied.

[0148] FIG. 9 illustrates the operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can establish a channel connection through contending (i.e., Backoff operation) and transmit a Trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU containing the Trigger frame (930). When the PPDU containing the Trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

[0149] TB PPDUs (941, 942) may be transmitted at the same time and may be transmitted from multiple STAs (e.g., User STAs) with AIDs indicated within the Trigger frame (930). The ACK frame (950) for the TB PPDU may be implemented in various forms.

[0150] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0151] The 2.4 GHz band may be referred to by other names, such as the first band (band). Additionally, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency located between 2.4 and 2.5 GHz) are used / supported / defined.

[0152] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz channels within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned to channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned to channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned to channel index N may be (2.407 + 0.005*N) GHz. Channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of channel indices and center frequencies may change.

[0153] FIG. 10 illustrates four channels within a 2.4 GHz band as an example. The illustrated first frequency range (1010) to fourth frequency range (1040) may each include one channel. For example, the first frequency range (1010) may include channel 1 (a 20 MHz channel having index 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency range (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency range (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency range (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0154] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0155] The 5 GHz band may be referred to by other names such as the second band / band. The 5 GHz band may refer to a frequency range in which channels with a center frequency of 5 GHz or higher and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 may be changed.

[0156] Multiple channels within the 5 GHz band include UNII (Unlicensed National Information Infrastructure)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency regions referred to as UNII Mid and UNII-2 Extended. UNII-3 may be referred to as UNII-Upper.

[0157] Multiple channels may be configured within the 5 GHz band, and the bandwidth of each channel may be varied, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency range within UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency range may be divided into four channels through a 40 MHz frequency range. The 5170 MHz to 5330 MHz frequency range may be divided into two channels through an 80 MHz frequency range. Alternatively, the 5170 MHz to 5330 MHz frequency range may be divided into one channel through a 160 MHz frequency range.

[0158] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0159] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with a center frequency of 5.9 GHz or higher are used / supported / defined. The specific figures shown in FIG. 12 are subject to change.

[0160] For example, the 20 MHz channel of FIG. 12 can be defined starting from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 may have index 1 (or channel index, channel number, etc.), and the center frequency may be assigned as 5.945 GHz. That is, the center frequency of the index N channel may be determined as (5.940 + 0.005*N) GHz.

[0161] Accordingly, the indices (or channel numbers) of the 20 MHz channel in FIG. 12 are 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, It may be 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule described above, the index of the 40 MHz channel of FIG. 12 may be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.

[0162] The structure and types / subtypes of MAC frames are described below.

[0163] FIG. 13 shows an example of a MAC frame header. As illustrated, the MAC frame may include a frame control field / information of 2 octets, a duration field / information of 2 octets, a Receiver Address (RA) field / information of 6 octets, and a Transmitter Address (TA) field / information of 6 octets. As illustrated in FIG. 13, the four fields may be consecutive. The MAC header of FIG. 13 may be modified in various ways, and a new field may be inserted between the four illustrated fields, or at least one of the illustrated fields may be omitted.

[0164] The MAC header shown in FIG. 13 may be located at the very beginning of the MAC frame. That is, the MAC frame may include a MAC header such as that in FIG. 13 and a MAC body field / information following the MAC header. The MAC frame containing the MAC header of FIG. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) shown in FIG. 5.

[0165] MAC frames included in the data fields of the PPDU of this specification may be classified into various types. For example, MAC frames of this specification may be classified into control frames, management frames, and data frames.

[0166] For example, a management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLANs. For the management frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are set to 00. Additionally, the values ​​of the subtype fields (B7, B6, B5, B4) in FIG. 13 are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).

[0167] For example, the control frame includes the Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLANs. For the control frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are set to 01. Also, the values ​​of the subtype fields (B7, B6, B5, B4) of FIG. 13 are as follows: Trigger(0010), Beamforming Report Poll(0100), NDP Announcement(0101), Control Frame Extension(0110), Control Wrapper(0111), BlockAckReq(1000), BlockAck(1001), PS-Poll(1010), RTS(1011), CTS(1100), Ack(1101), CF-End(1110).

[0168] For example, the data frame includes (QoS) Data, (QoS) Null, etc., defined in conventional WLANs. For the management frame, the value of the type field (B3 and B2) in FIG. 13 is set to 10.

[0169] MAC frames / signals used in this specification can be identified through the type field / information and subtype field / information described above. For example, "frame" in this specification may refer to a MAC frame in which the type bits B3 and B2 within the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 within the frame control field are set to 0010. Various MAC frames described in this specification are inserted / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDU).

[0170] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.

[0171] The device illustrated in FIGS. 1 to 4 (e.g., AP STA, non-AP STA) can be modified as in FIG. 14. The transceiver (1430) of FIG. 14 may be identical to the transceiver (113, 123) of FIG. 1. The transceiver (1430) of FIG. 14 may include a receiver and a transmitter.

[0172] The processor (1410) of FIG. 14 may be the same as the processor (111, 121) of FIG. 1. Or, the processor (1410) of FIG. 14 may be the same as the processing chip (114, 124) of FIG. 1.

[0173] The memory (1420) of FIG. 14 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (1420) of FIG. 14 may be a separate external memory different from the memory (112, 122) of FIG. 1.

[0174] Referring to FIG. 14, a power management module (1411) manages power for a processor (1410) and / or a transceiver (1430). A battery (1412) supplies power to the power management module (1411). A display (1413) outputs results processed by the processor (1410). A keypad (1414) receives input to be used by the processor (1410). The keypad (1414) may be displayed on the display (1413). A SIM card (1415) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.

[0175] Referring to FIG. 14, the speaker (1440) can output sound-related results processed by the processor (1410). The microphone (1441) can receive sound-related inputs to be used by the processor (1410).

[0176] 1. MU-MIMO and OFDMA Technology

[0177] One example of this specification relates to MU-MIMO (Multi-User Multiple-Input Multiple-Output) and OFDMA (Orthogonal Frequency Division Multiple Access) used in wireless LAN systems.

[0178] For example, the above MU-MIMO is a multi-user transmission technology that utilizes a spatial domain, and may refer to a method in which an AP uses multiple antennas to simultaneously transmit different spatial streams to different users. Specifically, multiple users can receive data through different beams or spatial channels within the same frequency band and the same time interval. For example, the above MU-MIMO may be based on beamforming based on Channel State Information (CSI), and may have the characteristic that transmission efficiency improves as spatial orthogonality between users is secured.

[0179] For example, the above OFDMA is a technology that supports multiple users by dividing the frequency domain, dividing a single channel bandwidth into multiple resource units (RUs), and allocating each RU to different users to perform simultaneous transmission. For example, in OFDMA, when each user (e.g., each non-AP STA) uses a different subcarrier set, interference between users is minimized, which is advantageous for reducing latency and increasing channel utilization in environments where small amounts of data are frequently transmitted and received.

[0180] For example, the above MU-MIMO can increase transmission speed and capacity through spatial multiplexing, and the above OFDMA can achieve efficiency in simultaneous connection of multiple devices and low latency through frequency multiplexing.

[0181] For example, the device of this specification (e.g., AP, non-AP STA, AP MLD, non-AP MLD) may adaptively select or combine the MU-MIMO mode and the OFDMA mode based on the type of traffic (e.g., UL or DL ​​traffic), the size of the data, and the density information of the connected station.

[0182] 2. Transmission where OFDMA and MU-MIMO are applied together

[0183] Specifically, in UHR systems and / or Next Wi-Fi systems (e.g., systems improved or evolved from UHR systems), signals can be transmitted by applying MU-MIMO to the large-size RU / MRU allocated during OFDMA transmission to increase high throughput and spectral efficiency. In order to transmit signals by applying MU-MIMO to the large-size RU / MRU allocated during OFDMA transmission in this manner, a UHR-SIG configuration is required to efficiently indicate this. This specification may propose an improved UHR-SIG configuration method for transmission in which OFDMA and MU-MIMO are applied together.

[0184] The technical features of this specification may be expressed in various terms. For example, if only MU-MIMO is applied to a single PPDU (e.g., UL-PPDU or DL-PPDU), it may be expressed that Full Bandwidth MU-MIMO is applied to that PPDU. For example, if OFDMA is applied together with MU-MIMO to a single PPDU (e.g., UL-PPDU) or DL-PPDU, it may be expressed that Partial Bandwidth MU-MIMO is applied to that PPDU. Specifically, when OFDMA is used together with MU-MIMO, various terms such as Partial Bandwidth MU-MIMO may be used, as it can be expressed that MU-MIMO is applied to a specific bandwidth and OFDMA is applied to the remaining bandwidth.

[0185] For example, for transmissions performed in a UHR system or next wi-fi system, MU-MIMO application can be applied to 242 tone RUs or a bandwidth of 20 MHz or more, just as in 11be or 11ax. Additionally, MU-MIMO applied during OFDMA transmission can also be applied to RU / MRUs of 242 tone RUs or more, just like this. In other words, an example is possible where the RU / MRU for Partial Bandwidth MU-MIMO is limited only to 242 tone RUs or more.

[0186] Transmission in which OFDMA and MU-MIMO are applied together is applicable for a bandwidth of 80 MHz or more, and the RU / MRU to which MU-MIMO is applied for each bandwidth can be applied as follows. In addition, for a bandwidth of 80 MHz or more, OFDMA and MU-MIMO can be applied for each 80 MHz separately. In other words, the RU and MRU supported on partial BW DL MU-MIMO and / or partial BW UL MU-MIMO can be defined as follows.

[0187] 2.1 Example of RU / MRU for MU-MIMO in OFDMA

[0188] For example, for 80 MHz (transmit / receive), the following RU / MRU may be supported / selected for MU-MIMO in OFDMA. In other words, within a PPDU with a bandwidth of 80 MHz, the RUs for partial BW DL MU-MIMO and / or partial BW UL MU-MIMO may be as follows.

[0189] 1) 80MHz

[0190] 484+242-tone MRU (for non-punctured case)

[0191] For example, for 160 MHz (transmit / receive), the following RU / MRU may be supported / selected for MU-MIMO in OFDMA. In other words, within a PPDU with a bandwidth of 160 MHz, the RUs for partial BW DL MU-MIMO and / or partial BW UL MU-MIMO may be as follows.

[0192] 2) 160MHz

[0193] 484+242-tone MRU

[0194] 996+484-tone MRU

[0195] 996+484+242-tone MRU (for non-punctured case)

[0196] For example, for 320 MHz (transmit / receive), the following RU / MRU may be supported / selected for MU-MIMO in OFDMA. In other words, within a PPDU with a bandwidth of 320 MHz, the RUs for partial BW DL MU-MIMO and / or partial BW UL MU-MIMO may be as follows.

[0197] 3) 320MHz

[0198] 484+242-tone MRU

[0199] 996+484-tone MRU

[0200] 996+484+242-tone MRU

[0201] 2x996-tone MRU

[0202] 2x996+484-tone MRU

[0203] 3x996-tone MRU

[0204] 3Х996+484-tone MRU (for non-punctured case)

[0205] 2.2 Constraints on RU and MRU Used in Partial BW MU-MIMO

[0206] For example, in Ultra High Reliability (UHR), the supported Resource Units (RU) and Multi-Resource Units (MRU) for partial bandwidth DL (downlink) and UL (Uplink) MU-MIMO (Multi-User Multiple Input Multiple Output) may be limited only to cases where the Physical Protocol Data Unit (PPDU) bandwidth is 160 MHz or 320 MHz. An example of a specific constraint related to this may be as follows.

[0207] 1) At most two RU or MRUs can be used in DL or UL MU-MIMO.

[0208] 2) Each 80 MHz segment can use only one of OFDMA or MU-MIMO.

[0209] 3) For a 160 MHz PPDU, MU-MIMO can only be transmitted over a 996-tone RU, or over a 484+242-tone MRU if puncturing is applied.

[0210] 4) For a 320 MHz PPDU, MU-MIMO can be transmitted only on 2x996-tone RUs or 3x996-tone MRUs, or, if puncturing is applied, on 996+484-tone MRUs or 2x996+484-tone RUs.

[0211] 3. Capability Information Exchange and Constraints for Efficient UL MU-MIMO Transmission and Usage

[0212] In order to increase the use and efficiency of MU-MIMO (Multi-User Multiple Input Multiple Output) when transmitting signals using UL (Uplink) OFDMA in UHR (Ultra High Reliability) or 802.11bn, the following constraints are defined to increase the use of MU-MIMO by non-AP STA (non-access point station) and improve spectrum efficiency when transmitting signals using UL (Uplink) OFDMA.

[0213] 3.1 Constraints for Partial Bandwidth UL MU-MIMO Transmission

[0214] Signals can be transmitted by applying the constraints for MU-MIMO transmission during OFDMA defined only when the Partial Bandwidth UL MU-MIMO subfield in the UHR Capabilities Information field is set to the first value (e.g., 1). That is, the constraints described below can be applied only when the AP and the Non-AP STA support Partial Bandwidth MU-MIMO.

[0215] In this specification, partial bandwidth MU-MIMO may be supported when the bandwidth (or BW) of the TB PPDU (Trigger-Based Physical Protocol Data Unit) is 160 MHz or more.

[0216] For example, if the bandwidth of the TB PPDU is 80 MHz or less, UL OFDMA + MU-MIMO transmission may not be supported.

[0217] For example, if preamble puncturing is not considered, UL OFDMA + MU-MIMO transmission can be applied for at least 80 MHz or 996 RU or more.

[0218] For example, if preamble puncturing is considered, UL OFDMA + MU-MIMO transmission can be applied to at least 484+242-tone MRUs.

[0219] The above definition can be applied to both AP and non-AP STAs.

[0220] When the bandwidth (BW) is 160 MHz or higher, MU-MIMO is applied only to the RU / MRU size defined for each BW as follows.

[0221] 3.1.1 When the TB PPDU bandwidth is 160 MHz

[0222] For example, if Preamble puncturing is not considered, partial BW MU-MIMO can be applied only to 996-tone RU.

[0223] For example, when preamble puncturing is considered, partial BW MU-MIMO is applied only to 484+242-tone MRUs. In this case, 484+242-tone MRUs may exist within a single 80 MHz frequency segment (or, 80 MHz frequency subblock).

[0224] During the above OFDMA transmission, OFDMA or MU-MIMO can be applied to each 80 MHz frequency segment within 160 MHz, respectively.

[0225] 3.1.2 When the TB PPDU bandwidth is 320 MHz

[0226] For example, if Preamble puncturing is not considered, partial BW MU-MIMO may be applied only to 2x996-tone RU / MRU or 3x996-tone RU / MRU.

[0227] For example, if preamble puncturing is considered, partial BW MU-MIMO may be applied only to 996+484-tone RU / MRU or 2x996+484-tone RU / MRU. In this case, 996+484-tone RU / MRU may exist within two consecutive 80 MHz frequency segments (or 80 MHz frequency subblocks). Additionally, 2x996+484-tone RU / MRU may exist within three consecutive 80 MHz frequency segments (or 80 MHz frequency subblocks).

[0228] For example, during the above OFDMA transmission, OFDMA or MU-MIMO can be applied to each 80 MHz frequency segment within 320 MHz, respectively.

[0229] 3.2 Constraints for Full Bandwidth UL MU-MIMO Transmission

[0230] For example, MU-MIMO can be applied using full bandwidth (or non-OFDMA) in UL, and the rules and constraints for applying MU-MIMO may be applied differently from the OFDMA case.

[0231] Full Bandwidth UL MU-MIMO transmission can be applied to the following bandwidths (BW).

[0232] BW = 20 / 40 / 60 / 80 / 160 / 320MHz

[0233] In addition, it can be applied to RU / MRUs that occupy the entire PPDU BW (the entire bandwidth of the PPDU) defined by considering preamble puncturing.

[0234] For example, the minimum RU size for full bandwidth (or, non-OFDMA) UL MU-MIMO transmission is a 242-tone RU. As another example, it may be applied when the RU size is larger than a 242-tone RU.

[0235] 3.3 Capability Negotiation Procedures for AP and Non-AP STAs

[0236] For example, in order to efficiently transmit and receive TB PPDUs using the UL OFDMA+ MU-MIMO transmission constraints or rules defined as above, the AP and Non-AP STA in UHR or 11bn can perform capability negotiation (or exchange).

[0237] For capability negotiation, AP and non-AP STA may include information regarding UL MU-MIMO transmission in the UHR Capabilities Information field of FIG. 15. FIG. 15 illustrates an example of the UHR Capabilities Information field.

[0238] The UL MU-MIMO related subfields included in the UHR Capabilities Information field of Fig. 15 may include the following information.

[0239] 3.3.1 Partial Bandwidth UL MU-MIMO Information / Field / Subfield

[0240] For example, the above information / field / subfield (e.g., Partial Bandwidth UL MU-MIMO) may indicate whether MU-MIMO transmission is allowed along with OFDMA using a specific size RU / MRU when transmitting UL TB PPDU.

[0241] For example, when the above information / field / subfield is set to a first value (e.g., 1), the above information / field / subfield may indicate that MU-MIMO is supported during UL OFDMA transmission. When the above field is set to a second value (e.g., 0), the above information / field / subfield may indicate that MU-MIMO is not supported during UL OFDMA transmission.

[0242] Additionally, MU-MIMO may not be applied when the UL BW is 80 MHz or less, as defined above, during UL OFDMA transmission. In other words, this may mean that UL MU-MIMO transmission is allowed only when the UL BW is 160 MHz or more (meaning 160 MHz or 320 MHz, which may be expanded in the future).

[0243] When the above subfield is set to the first value (e.g., 1), the AP may indicate that it supports receiving TB PPDU transmitted through the method defined as above.

[0244] When the above subfield is set to the first value (e.g. 1), the non-AP STA may indicate that it supports TB PPDU transmission using MU-MIMO with the above definition applied.

[0245] 3.3.2 Non-OFDMA UL MU-MIMO (BW <= 80 MHz) Information / Fields / Subfields

[0246] For example, when the BW of a UL PPDU (i.e., UHR TB PPDU) is 80 MHz or less (e.g., 20 MHz, 40 MHz, or 80 MHz), the AP can indicate support for full-bandwidth UL MU-MIMO reception through the above information / fields / subfields, etc. For example, in cases where puncturing is supported, support for UL MU-MIMO transmission can be indicated through the above information even if the size of the RU / MRU allocated within the PPDU BW spans the entire PPDU BW. For example, in the case where the PPDU BW is 20 MHz, a 20 MHz only non-AP UHR STA can indicate support for UL MU-MIMO transmission through the above information.

[0247] For example, if the 20MHz only limited capabilities support subfield within the UHR Capabilities Information field is set to a first value (e.g., 1) and the 20MHz only UL MU-MIMO support field within the UHR Capabilities Information field is set to a first value (e.g., 1), the 20MHz only non-AP UHR STA can support UL MU-MIMO. As an example, the UHR Capabilities Information field is configured to include the 20MHz only limited capabilities support subfield and the 20MHz only UL MU-MIMO support field. For example, the 20MHz only UL MU-MIMO support field and / or the 20MHz only limited capabilities support subfield may be freely changed to other names.

[0248] 3.3.3 Non-OFDMA UL MU-MIMO (BW = 160 MHz) Information / Field / Subfield

[0249] For example, when the BW of a UL PPDU (e.g., UHR TB PPDU) is 160 MHz, the information / field / subfield may indicate that the AP supports full bandwidth UL MU-MIMO reception. For example, when Puncturing is supported, even if the size of the RU / MRU allocated within the PPDU BW spans the entire PPDU BW, the information / field / subfield may have the same value.

[0250] 3.3.4 Non-OFDMA UL MU-MIMO (BW = 320 MHz) Information / Fields / Subfields

[0251] For example, when the BW of a UL PPDU (i.e., UHR TB PPDU) is 320 MHz, the AP may indicate that the information / field / subfield supports full bandwidth UL MU-MIMO reception. For example, when Puncturing is supported, even if the size of the RU / MRU allocated within the PPDU BW spans the entire PPDU BW, the information / field / subfield may have the same value.

[0252] 3.4 Trigger frame requesting a TB PPDU to use Partial Bandwidth UL MU-MIMO

[0253] In order to receive a TB PPDU using OFDMA + UL MU-MIMO according to the rules and constraints defined as above, the AP can configure a trigger frame requesting a TB PPDU using the following definitions and rules.

[0254] As defined above, when an AP requests a TB PPDU with a BW of 160 MHz or more, it may request transmission via OFDMA+ UL MU-MIMO from a non-AP STA. In this case, the RU Allocation subfield of the user field of the Trigger frame may be composed of RU / MRU of the following sizes.

[0255] 1) When the BW of the TB PPDU is 160 MHz

[0256] 996 tone RU or 484+242 tone RU (with preamble puncturing)

[0257] 2) When the BW of the TB PPDU is 320MHz

[0258] 2x996 tone RU / MRU, 3x996 tone RU / MRU, 996+484 tone RU / MRU (with preamble puncturing), 2x996+484 RU / MRU (with preamble puncturing)

[0259] Meanwhile, the indication for 2x996 tones within the RU allocation subfield at 320 MHz can be defined as shown in Table 1 below.

[0260] PS160subfieldB0 of the RUAllocation subfieldB7-B1 ofthe RU Allocation subfieldBandwidth (MHz)RU or MRU sizeRU or MRU index0068160, or 3202x996RU1113202x996RU2

[0261] FIG. 16 is a flowchart illustrating the operation of a transmitting device according to the present embodiment. An example of FIG. 16 may be performed at a transmitting STA or a transmitting device (AP and / or non-AP STA). Some of the steps (or detailed sub-steps described below) of the example of FIG. 16 may be omitted or changed.

[0262] Through step S1610, the transmitting device (transmitting STA) can obtain information regarding the above-described Tone Plan. As described above, the information regarding the Tone Plan includes the size and location of the RU, control information related to the RU, information regarding the frequency band in which the RU is included, information regarding the STA receiving the RU, etc.

[0263] Through step S1620, the transmitting device can construct / generate a PPDU based on the acquired control information. The step of constructing / generating the PPDU may include the step of constructing / generating each field of the PPDU. For example, step S1620 may include the step of constructing a UHR-SIG field containing control information regarding a Tone Plan. That is, step S1620 may include the step of constructing a field containing control information (e.g., N bitmap) indicating the size / location of the RU and / or the step of constructing a field containing an identifier (e.g., AID) of the STA receiving the RU.

[0264] Additionally, step S1620 may include the step of configuring a trigger-based (TB) PPDU based on the received trigger frame information.

[0265] Additionally, step S1620 may include the step of generating an STF / LTF sequence transmitted through a specific RU. The STF / LTF sequence may be generated based on a pre-configured STF generation sequence / LTF generation sequence.

[0266] Additionally, step S1620 may include a step of generating a data field (i.e., MPDU) transmitted through a specific RU. The step of generating the data field may include a step of configuring it by applying UEQM / EQM.

[0267] The transmitting device can transmit the PPDU configured through step S1620 to the receiving device based on step S1630.

[0268] While performing step S1630, the transmitting device may perform at least one of the following operations: CSD, Spatial Mapping, IDFT / IFFT operation, GI insertion, etc.

[0269] A signal / field / sequence configured according to the present specification can be transmitted in the form of FIG. 5.

[0270] FIG. 17 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0271] The above-described PPDU can be received according to an example of FIG. 17.

[0272] An example of FIG. 17 can be performed on a receiving STA or a receiving device (AP and / or non-AP STA).

[0273] Some of the steps of each example in Fig. 17 (or detailed sub-steps described later) may be omitted.

[0274] A receiving device (receiving STA) can receive all or part of the PPDU through step S1710. The received signal may be in the form of FIG. 5.

[0275] The sub-step of step S1710 can be determined based on step S1630 of FIG. 16. That is, step S1710 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insert operation applied in step S1630.

[0276] In step S1720, the receiving device can perform decoding of all or part of the PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.

[0277] More specifically, the receiving device can decode the L-SIG, U-SIG, and UHR-SIG of the PPDU based on the Legacy STF / LTF and obtain information contained in the L-SIG, U-SIG, and UHR-SIG fields. Information regarding various Tone Plans (i.e., RU) described herein may be included in the UHR-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the UHR-SIG. Additionally, information regarding the application of UEQM / EQM can be obtained through the UHR-SIG.

[0278] In addition, at step S1720, the receiving device can decode the L-SIG and U-SIG of the PPDU based on the Legacy STF / LTF and obtain information contained in the L-SIG and U-SIG fields. For example, the receiving STA can confirm the reception of the TB PPDU through the U-SIG and obtain information regarding the Tone Plan (e.g., RU) based on the transmitted Trigger frame information.

[0279] In step S1730, the receiving device can decode the remainder of the PPDU based on information regarding the Tone Plan (i.e., RU) and UEQM / EQM obtained through step S1720. For example, the receiving STA can decode the STF / LTF field of the PPDU based on information regarding the one Plan (i.e., RU). Additionally, the receiving STA can decode the data field of the PPDU based on information regarding the Tone Plan (i.e., RU) and UEQM / EQM information, and obtain the MPDU contained in the data field.

[0280] Additionally, the receiving device can perform a processing operation to transmit the decoded data through step S1730 to an upper layer (e.g., MAC layer). Furthermore, if the generation of a signal is instructed from the upper layer to the PHY layer in response to the data transmitted to the upper layer, a subsequent operation can be performed.

[0281] Hereinafter, the above-described embodiment will be explained with reference to FIGS. 1 to 17.

[0282] FIG. 18 is a flowchart illustrating a procedure for an AP to transmit a trigger frame based on capability information exchanged with a non-AP according to the present embodiment.

[0283] An example of FIG. 18 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0284] This embodiment can be performed at an access point (AP). The AP can be replaced with an access point Multi-link Device (AP MLD). The non-access point Station (non-AP STA) of this embodiment can be replaced with a non-AP MLD.

[0285] The present embodiment proposes a method for exchanging capability information regarding whether UL MU-MIMO is supported for a partial bandwidth in order to efficiently transmit TB PPDU using UL MU-MIMO. Specifically, it proposes a method for transmitting allocation information regarding a RU or MRU that supports UL MU-MIMO by transmitting a trigger frame based on capability information regarding whether UL MU-MIMO is supported for a partial bandwidth.

[0286] In step S1810, the access point (AP) can exchange capability information with the non-access point station (non-AP STA).

[0287] In step S1820, the AP can transmit a trigger frame to the non-AP STA based on the capability information.

[0288] For example, the capability information may include information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for a partial bandwidth (Partial Bandwidth UL MU-MIMO subfield of FIG. 15).

[0289] For example, the above trigger frame can solicit a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more.

[0290] For example, the trigger frame may include allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth.

[0291] For example, regarding the above partial bandwidth, the UL MU-MIMO can be used in units of 80 MHz frequency subblocks. Specifically, in order to efficiently transmit and receive TB PPDUs (Trigger-Based Physical Protocol Data Units) using defined transmission constraints or rules when UL OFDMA (Uplink Orthogonal Frequency Division Multiple Access) and MU-MIMO (Multi-User Multiple Input Multiple Output) are used simultaneously, the UHR (Ultra High Reliability) AP and the non-AP STA can exchange capability information. After the capability information is exchanged, the AP can transmit a trigger frame requesting a TB PPDU in order to use UL OFDMA and MU-MIMO together when transmitting the TB PPDU.

[0292] In this specification, MU-MIMO during UL OFDMA may be supported when the BW (Bandwidth) of the TB PPDU is 160 MHz or more.

[0293] For example, based on the fact that the bandwidth of the TB PPDU is 160 MHz, the RU or MRU that supports the UL MU-MIMO for the said partial bandwidth may be limited to 996-tone RU if there is no preamble puncturing in the TB PPDU, and may be limited to 484+242-tone MRU if there is preamble puncturing in the TB PPDU.

[0294] For example, the bandwidth of the above TB PPDU may be composed of two consecutive 80 MHz frequency subblocks. For example, the above 484+242-tone MRU may exist within one of the two consecutive 80 MHz frequency subblocks.

[0295] As another example, based on the fact that the bandwidth of the TB PPDU is 320 MHz, the RU or MRU that supports the UL MU-MIMO for the said partial bandwidth may be limited to 2x996-tone RU or 3x996-tone RU if there is no preamble puncturing in the TB PPDU, and may be limited to 996+484-tone MRU or 2x996+484-tone MRU if there is preamble puncturing in the TB PPDU.

[0296] For example, the bandwidth of the above TB PPDU may be composed of four consecutive 80 MHz frequency subblocks. The 996+484-tone MRU may exist within two consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks. The 2x996+484-tone MRU may exist within three consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks.

[0297] In other words, the present embodiment may propose a method for setting a trigger frame to request a TB PPDU transmitted over a 160 MHz or 320 MHz bandwidth when UL MU-MIMO is supported for a partial bandwidth. Specifically, the present embodiment proposes a method for transmitting the TB PPDU based on OFDMA and UL MU-MIMO by allocating a limited RU or MRU that supports UL MU-MIMO through the trigger frame.

[0298] For example, the capability information may further include first to third information regarding whether the UL MU-MIMO is supported for the entire bandwidth. For example, the first information (the Non-OFDMA UL MU-MIMO (BW <= 80 MHz) subfield of FIG. 15) may include information regarding whether the AP or the non-AP STA supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 80 MHz or less.

[0299] Based on the fact that the bandwidth of the above TB PPDU is 20 MHz and the above non-AP STA is a 20 MHz only non-AP STA that operates only at 20 MHz, the first information may be set as information on whether the 20 MHz only non-AP STA supports UL MU-MIMO for the entire bandwidth based on the 20 MHz only limited capabilities support subfield and the 20 MHz only UL MU-MIMO support field.

[0300] For example, the above 20MHz only limited capabilities support subfield and the above 20MHz only UL MU-MIMO support field may be included in the UHR (Ultra High Reliability) Capabilities information field. Specifically, when the 20MHz only limited capabilities support subfield within the UHR Capabilities Information field is set to a first value (e.g., 1) and the 20MHz only UL MU-MIMO support field within the UHR Capabilities Information field is set to a first value (e.g., 1), the above 20MHz only non-AP UHR STA can support UL MU-MIMO. For example, the names of the above specific fields may be changed in various ways.

[0301] For example, the second information (e.g., Non-OFDMA UL MU-MIMO (BW = 160 MHz) subfield of FIG. 15) may include information on whether the AP supports UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 160 MHz.

[0302] For example, the third information (e.g., Non-OFDMA UL MU-MIMO (BW = 320 MHz) subfield of FIG. 15) may include information on whether the AP supports UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 320 MHz.

[0303] For example, the above capability information may be included in the above UHR Capabilities information field (UHR Capabilities Information field in FIG. 15). For example, the above UHR Capabilities information field may be included in the UHR capabilities element. For example, the above UHR capabilities element may be included in the management frame.

[0304] For example, based on the fact that the UL MU-MIMO is supported for the above partial bandwidth, the TB PPDU can be transmitted based on OFDMA (Orthogonal Frequency Division Multiple Access) and the UL MU-MIMO.

[0305] For example, based on the fact that the UL MU-MIMO is supported for the entire bandwidth, the TB PPDU can be transmitted based on non-OFDMA and the UL MU-MIMO.

[0306] For example, based on the fact that the bandwidth of the TB PPDU is 160 MHz, the TB PPDU can be transmitted using the UL MU-MIMO through the 996-tone RU or the 484+242-tone MRU.

[0307] For example, based on the fact that the bandwidth of the TB PPDU is 320 MHz, the TB PPDU can be transmitted using the UL MU-MIMO through the 2x996-tone RU, the 3x996-tone RU, the 996+484-tone MRU, or the 2x996+484-tone MRU.

[0308] FIG. 19 is a flowchart illustrating the procedure for a non-AP STA to receive a trigger frame from an AP according to the present embodiment.

[0309] An example of FIG. 19 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0310] This embodiment can be performed at an access point (AP). The AP can be replaced with an access point Multi-link Device (AP MLD). The non-access point Station (non-AP STA) of this embodiment can be replaced with a non-AP MLD.

[0311] The present embodiment proposes a method for exchanging capability information regarding whether UL MU-MIMO is supported for a partial bandwidth in order to efficiently transmit TB PPDU using UL MU-MIMO. Specifically, it proposes a method for transmitting allocation information regarding a RU or MRU that supports UL MU-MIMO by transmitting a trigger frame based on capability information regarding whether UL MU-MIMO is supported for a partial bandwidth.

[0312] In step S1910, non-AP STAs (non-access point stations) can exchange capability information with APs (access points).

[0313] In step S1920, the non-AP STA can receive a trigger frame from the AP based on the capability information.

[0314] For example, the capability information may include information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for a partial bandwidth (Partial Bandwidth UL MU-MIMO subfield of FIG. 15).

[0315] For example, the above trigger frame can solicit a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more.

[0316] For example, the trigger frame may include allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth.

[0317] For example, regarding the above partial bandwidth, the UL MU-MIMO can be used in units of 80 MHz frequency subblocks. Specifically, in order to efficiently transmit and receive TB PPDUs (Trigger-Based Physical Protocol Data Units) using defined transmission constraints or rules when UL OFDMA (Uplink Orthogonal Frequency Division Multiple Access) and MU-MIMO (Multi-User Multiple Input Multiple Output) are used simultaneously, the UHR (Ultra High Reliability) AP and the non-AP STA can exchange capability information. After the capability information is exchanged, the AP can transmit a trigger frame requesting a TB PPDU in order to use UL OFDMA and MU-MIMO together when transmitting the TB PPDU.

[0318] In this specification, MU-MIMO during UL OFDMA may be supported when the BW (Bandwidth) of the TB PPDU is 160 MHz or more.

[0319] For example, based on the fact that the bandwidth of the TB PPDU is 160 MHz, the RU or MRU that supports the UL MU-MIMO for the said partial bandwidth may be limited to 996-tone RU if there is no preamble puncturing in the TB PPDU, and may be limited to 484+242-tone MRU if there is preamble puncturing in the TB PPDU.

[0320] For example, the bandwidth of the above TB PPDU may be composed of two consecutive 80 MHz frequency subblocks. For example, the above 484+242-tone MRU may exist within one of the two consecutive 80 MHz frequency subblocks.

[0321] As another example, based on the fact that the bandwidth of the TB PPDU is 320 MHz, the RU or MRU that supports the UL MU-MIMO for the said partial bandwidth may be limited to 2x996-tone RU or 3x996-tone RU if there is no preamble puncturing in the TB PPDU, and may be limited to 996+484-tone MRU or 2x996+484-tone MRU if there is preamble puncturing in the TB PPDU.

[0322] For example, the bandwidth of the above TB PPDU may be composed of four consecutive 80 MHz frequency subblocks. The 996+484-tone MRU may exist within two consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks. The 2x996+484-tone MRU may exist within three consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks.

[0323] In other words, the present embodiment may propose a method for setting a trigger frame to request a TB PPDU transmitted over a 160 MHz or 320 MHz bandwidth when UL MU-MIMO is supported for a partial bandwidth. Specifically, the present embodiment proposes a method for transmitting the TB PPDU based on OFDMA and UL MU-MIMO by allocating a limited RU or MRU that supports UL MU-MIMO through the trigger frame.

[0324] For example, the capability information may further include first to third information regarding whether the UL MU-MIMO is supported for the entire bandwidth. For example, the first information (the Non-OFDMA UL MU-MIMO (BW <= 80 MHz) subfield of FIG. 15) may include information regarding whether the AP or the non-AP STA supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 80 MHz or less.

[0325] Based on the fact that the bandwidth of the above TB PPDU is 20 MHz and the above non-AP STA is a 20 MHz only non-AP STA that operates only at 20 MHz, the first information may be set as information on whether the 20 MHz only non-AP STA supports UL MU-MIMO for the entire bandwidth based on the 20 MHz only limited capabilities support subfield and the 20 MHz only UL MU-MIMO support field.

[0326] For example, the above 20MHz only limited capabilities support subfield and the above 20MHz only UL MU-MIMO support field may be included in the UHR (Ultra High Reliability) Capabilities information field. Specifically, when the 20MHz only limited capabilities support subfield within the UHR Capabilities Information field is set to a first value (e.g., 1) and the 20MHz only UL MU-MIMO support field within the UHR Capabilities Information field is set to a first value (e.g., 1), the above 20MHz only non-AP UHR STA can support UL MU-MIMO. For example, the names of the above specific fields may be changed in various ways.

[0327] For example, the second information (e.g., Non-OFDMA UL MU-MIMO (BW = 160 MHz) subfield of FIG. 15) may include information on whether the AP supports UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 160 MHz.

[0328] For example, the third information (e.g., Non-OFDMA UL MU-MIMO (BW = 320 MHz) subfield of FIG. 15) may include information on whether the AP supports UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 320 MHz.

[0329] For example, the above capability information may be included in the above UHR Capabilities information field (UHR Capabilities Information field in FIG. 15). For example, the above UHR Capabilities information field may be included in the UHR capabilities element. For example, the above UHR capabilities element may be included in the management frame.

[0330] For example, based on the fact that the UL MU-MIMO is supported for the above partial bandwidth, the TB PPDU can be transmitted based on OFDMA (Orthogonal Frequency Division Multiple Access) and the UL MU-MIMO.

[0331] For example, based on the fact that the UL MU-MIMO is supported for the entire bandwidth, the TB PPDU can be transmitted based on non-OFDMA and the UL MU-MIMO.

[0332] For example, based on the fact that the bandwidth of the TB PPDU is 160 MHz, the TB PPDU can be transmitted using the UL MU-MIMO through the 996-tone RU or the 484+242-tone MRU.

[0333] For example, based on the fact that the bandwidth of the TB PPDU is 320 MHz, the TB PPDU can be transmitted using the UL MU-MIMO through the 2x996-tone RU, the 3x996-tone RU, the 996+484-tone MRU, or the 2x996+484-tone MRU.

[0334] The technical features of the specification described above may be applied to various devices and methods. For example, the technical features of the specification described above may be performed or supported through the device of FIG. 1 and / or FIG. 14. For example, the technical features of the specification described above may be applied only to parts of FIG. 1 and / or FIG. 14. For example, the technical features of the specification described above may be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and memory (112, 122) of FIG. 1, or based on the processor (1410) and memory (1420) of FIG. 14. For example, the device of the specification exchanges capability information with a non-AP STA (non-access point station) and transmits a trigger frame based on the capability information.

[0335] The technical features of this specification may be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable medium comprising instructions based on execution by at least one processor.

[0336] The above CRM may store instructions for performing operations including the step of exchanging capability information with a non-AP STA (non-access point station) and transmitting a trigger frame based on the capability information. Instructions stored in the CRM of this specification may be executed by at least one processor. At least one processor associated with the CRM of this specification may be the processor (111, 121) or processing chip (114, 124) of FIG. 1, or the processor (1410) of FIG. 14. Meanwhile, the CRM of this specification may be the memory (112, 122) of FIG. 1, the memory (1420) of FIG. 14, or a separate external memory / storage medium / disk, etc.

[0337] The technical features of the present specification described above are applicable to various applications or business models. For example, the technical features described above may be applied for wireless communication in devices supporting Artificial Intelligence (AI).

[0338] Artificial intelligence refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems addressed within the field of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0339] An Artificial Neural Network (ANN) is a model used in machine learning that can refer to any model capable of problem-solving, composed of artificial neurons (nodes) that form a network through the connection of synapses. An artificial neural network can be defined by connection patterns between neurons in different layers, a learning process that updates model parameters, and an activation function that generates output values.

[0340] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer may include 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 for input signals, weights, and biases input through the synapses.

[0341] Model parameters refer to parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters, on the other hand, refer to parameters that must be set prior to training in a machine learning algorithm, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0342] The objective of training an artificial neural network can be viewed as determining model parameters that minimize the loss function. The loss function can be used as an indicator to determine optimal model parameters during the training process of an artificial neural network.

[0343] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.

[0344] Supervised learning refers to a method of training an artificial neural network with labels provided for the training data; a label can refer to the correct answer (or result) that the neural network must infer when the training data is input. Unsupervised learning refers to a method of training an artificial neural network without labels provided for the training data. Reinforcement learning refers to a learning method in which an agent defined within an environment is trained to select an action or sequence of actions that maximizes the cumulative reward in each state.

[0345] Machine learning implemented using a Deep Neural Network (DNN) that includes multiple hidden layers among artificial neural networks is also called Deep Learning, and Deep Learning is a part of Machine Learning. Hereinafter, Machine Learning is used in a sense that includes Deep Learning.

[0346] In addition, the aforementioned technical features can be applied to the wireless communication of robots.

[0347] A robot can refer to a machine that automatically processes or operates a given task based on its own capabilities. In particular, a robot that has the ability to perceive its environment, make decisions on its own, and perform actions can be called an intelligent robot.

[0348] Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, and propellers in their drive units, enabling them to drive on the ground or fly in the air.

[0349] In addition, the aforementioned technical features can be applied to devices that support augmented reality.

[0350] Extended Reality is a collective term for Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on real-world images, and MR technology is a computer graphics technology that mixes and combines virtual objects with the real world.

[0351] MR technology is similar to AR technology in that it displays real-world objects and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual objects and real-world objects are used as equals in MR technology.

[0352] XR technology can be applied to HMDs (Head-Mount Displays), HUDs (Head-Up Displays), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

[0353] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.

Claims

1. In a wireless LAN system, A step in which an AP (access point) exchanges capability information with a non-AP STA (non-access point station); and The above AP includes the step of transmitting a trigger frame to the above non-AP STA based on the capability information, wherein The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth, and The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more, and The trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth, and For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. method.

2. In Paragraph 1, Based on the fact that the bandwidth of the above TB PPDU is 160 MHz, For the above partial bandwidth, the RU or MRU supporting the UL MU-MIMO is limited to a 996-tone RU if there is no preamble puncturing in the TB PPDU, and is limited to a 484+242-tone MRU if there is preamble puncturing in the TB PPDU, and The bandwidth of the above TB PPDU consists of two consecutive 80 MHz frequency subblocks, and The above 484+242-tone MRU exists within one of the two consecutive 80 MHz frequency subblocks. method.

3. In Paragraph 1, Based on the fact that the bandwidth of the above TB PPDU is 320 MHz, For the above partial bandwidth, the RU or MRU supporting the UL MU-MIMO is limited to 2x996-tone RU or 3x996-tone RU if there is no preamble puncturing in the TB PPDU, and is limited to 996+484-tone MRU or 2x996+484-tone MRU if there is preamble puncturing in the TB PPDU, and The bandwidth of the above TB PPDU consists of four consecutive 80 MHz frequency subblocks, and The above 996+484-tone MRU exists within two consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks, and The above 2x996+484-tone MRUs exist within three consecutive 80 MHz frequency subblocks among the above four consecutive 80 MHz frequency subblocks. method.

4. In Paragraph 1, The above capability information further includes first to third information regarding whether the UL MU-MIMO is supported for the entire bandwidth, and The first information includes information on whether the AP or the non-AP STA supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 80 MHz or less, and The second information above includes information on whether the AP supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 160 MHz, and The third information includes information on whether the AP supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 320 MHz. method.

5. In Paragraph 4, Based on the fact that the bandwidth of the above TB PPDU is 20 MHz and the above non-AP STA is a 20 MHz only non-AP STA that operates only at 20 MHz, The first information is set as information regarding whether the 20 MHz only non-AP STA supports the UL MU-MIMO for the entire bandwidth based on the 20 MHz only limited capabilities support subfield and the 20 MHz only UL MU-MIMO support field, and The above 20MHz only limited capabilities support subfield and the above 20MHz only UL MU-MIMO support field are included in the UHR (Ultra High Reliability) Capabilities information field method.

6. In Paragraph 4, Based on the fact that the UL MU-MIMO is supported for the above partial bandwidth, the TB PPDU is transmitted based on OFDMA (Orthogonal Frequency Division Multiple Access) and the UL MU-MIMO, and Based on the fact that the UL MU-MIMO is supported for the entire bandwidth, the TB PPDU is transmitted based on non-OFDMA and the UL MU-MIMO. method.

7. In Paragraph 5, The above capability information is included in the above UHR Capabilities information field, and The above UHR Capabilities information field is included in the UHR capabilities element, and The above UHR capabilities elements are included in the management frame method.

8. In Paragraph 1, Based on the fact that the bandwidth of the above TB PPDU is 160 MHz, the above TB PPDU is transmitted using the UL MU-MIMO through the 996-tone RU or the 484+242-tone MRU, and Based on the fact that the bandwidth of the above TB PPDU is 320 MHz, the above TB PPDU is transmitted using the UL MU-MIMO through the 2x996-tone RU, the 3x996-tone RU, the 996+484-tone MRU, or the 2x996+484-tone MRU. method.

9. In a wireless LAN system, an AP (access point) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Exchange capability information with non-AP STAs (non-access point stations); and Transmit a trigger frame to the above non-AP STA based on the above capability information, The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth, and The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more, and The trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth, and For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. AP.

10. In wireless LAN systems, A step in which a non-AP STA (non-access point station) exchanges capability information with an AP (access point); and The above non-AP STA includes the step of receiving a trigger frame from the AP based on the capability information, wherein The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth, and The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more, and The trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth, and For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. method.

11. In Paragraph 10, Based on the fact that the bandwidth of the above TB PPDU is 160 MHz, For the above partial bandwidth, the RU or MRU supporting the UL MU-MIMO is limited to a 996-tone RU if there is no preamble puncturing in the TB PPDU, and is limited to a 484+242-tone MRU if there is preamble puncturing in the TB PPDU, and The bandwidth of the above TB PPDU consists of two consecutive 80 MHz frequency subblocks, and The above 484+242-tone MRU exists within one of the two consecutive 80 MHz frequency subblocks. method 12. In Paragraph 10, Based on the fact that the bandwidth of the above TB PPDU is 320 MHz, For the above partial bandwidth, the RU or MRU supporting the UL MU-MIMO is limited to 2x996-tone RU or 3x996-tone RU if there is no preamble puncturing in the TB PPDU, and is limited to 996+484-tone MRU or 2x996+484-tone MRU if there is preamble puncturing in the TB PPDU, and The bandwidth of the above TB PPDU consists of four consecutive 80 MHz frequency subblocks, and The above 996+484-tone MRU exists within two consecutive 80 MHz frequency subblocks among the four consecutive 80 MHz frequency subblocks, and The above 2x996+484-tone MRUs exist within three consecutive 80 MHz frequency subblocks among the above four consecutive 80 MHz frequency subblocks. method.

13. In Paragraph 10, The above capability information further includes first to third information regarding whether the UL MU-MIMO is supported for the entire bandwidth, and The first information includes information on whether the AP or the non-AP STA supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 80 MHz or less, and The second information above includes information on whether the AP supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 160 MHz, and The third information includes information on whether the AP supports the UL MU-MIMO for the entire bandwidth based on the fact that the bandwidth of the TB PPDU is 320 MHz. method.

14. In Paragraph 13, Based on the fact that the bandwidth of the above TB PPDU is 20 MHz and the above non-AP STA is a 20 MHz only non-AP STA that operates only at 20 MHz, The first information is set as information regarding whether the 20 MHz only non-AP STA supports the UL MU-MIMO for the entire bandwidth based on the 20 MHz only limited capabilities support subfield and the 20 MHz only UL MU-MIMO support field, and The above 20MHz only limited capabilities support subfield and the above 20MHz only UL MU-MIMO support field are included in the UHR (Ultra High Reliability) Capabilities information field method.

15. In Paragraph 13, Based on the fact that the UL MU-MIMO is supported for the above partial bandwidth, the TB PPDU is transmitted based on OFDMA (Orthogonal Frequency Division Multiple Access) and the UL MU-MIMO, and Based on the fact that the UL MU-MIMO is supported for the entire bandwidth, the TB PPDU is transmitted based on non-OFDMA and the UL MU-MIMO. method.

16. In Paragraph 14, The above capability information is included in the above UHR Capabilities information field, and The above UHR Capabilities information field is included in the UHR capabilities element, and The above UHR capabilities elements are included in the management frame method.

17. In Paragraph 10, Based on the fact that the bandwidth of the above TB PPDU is 160 MHz, the above TB PPDU is transmitted using the UL MU-MIMO through the 996-tone RU or the 484+242-tone MRU, and Based on the fact that the bandwidth of the above TB PPDU is 320 MHz, the above TB PPDU is transmitted using the UL MU-MIMO through the 2x996-tone RU, the 3x996-tone RU, the 996+484-tone MRU, or the 2x996+484-tone MRU. method.

18. In a wireless LAN system, a non-AP STA (non-access point station) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Exchange AP (access point) and capability information; and Receive a trigger frame from the above AP based on the above capability information, The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth, and The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more, and The trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth, and For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. non-AP STA.

19. At least one computer-readable medium comprising an instruction based on execution by at least one processor, Exchange capability information with non-AP STAs (non-access point stations); and Transmit a trigger frame to the above non-AP STA based on the above capability information, The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth, and The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more, and The trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth, and For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. Recording media.

20. In a device in a wireless LAN system, Memory; and The processor comprises the above memory and operablely coupled thereto, wherein the processor is: Exchange capability information with non-AP STAs (non-access point stations); and Transmit a trigger frame to the above non-AP STA based on the above capability information, The above capability information includes information on whether UL MU-MIMO (Uplink Multi-User Multiple Input Multiple Output) is supported for partial bandwidth, and The above trigger frame requests a TB PPDU (Trigger-Based Physical Protocol Data Unit) based on a bandwidth of 160 MHz or more, and The trigger frame includes allocation information regarding a Resource Unit (RU) or Multi Resource Unit (MRU) that supports the UL MU-MIMO for the partial bandwidth, and For the above partial bandwidth, the UL MU-MIMO is used in units of 80 MHz frequency subblocks. device.

Images