Method and device for transmitting ELR PPDU on basis of trigger frame in wireless LAN system

Abstract

Proposed are a method and device for transmitting an ELR PPDU on the basis of a trigger frame in a wireless LAN system. Specifically, a plurality of receiving STAs receive a trigger frame from a transmission STA. The plurality of receiving STAs transmit an ELR PPDU to the transmission STA on the basis of the trigger frame. The trigger frame includes a user information field. The user information field includes indication information for transmission of the ELR PPDU.

Description

Method and device for transmitting ELR PPDU based on trigger frame in wireless LAN system

[0001] The present specification relates to a technique for transmitting an ELR PPDU based on a trigger frame in a wireless LAN system, and more specifically, to a method and device for requesting transmission of an ELR PPDU to a plurality of non-AP STAs by configuring a common information field, a special user information field, and a user information field of the trigger frame.

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

[0003] The EHT specification supports high throughput and high data rates, which may include wide bandwidth (e.g., 160 / 320 MHz), 16 streams, and / or multi-link (or multi-band) operation.

[0004] In the EHT specification, wide bandwidth (e.g., 160 / 240 / 320 MHz) can be used to achieve high throughput. Preamble puncturing and multiple RU transmissions can also be used to efficiently utilize bandwidth.

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

[0006] WLAN systems perform media access based on primary channels. For example, information about a primary channel with a bandwidth of 20 MHz is transmitted to multiple STAs via management frames, and any STA attempting to exchange frames can access the primary channel.

[0007] The present specification proposes a method and device for transmitting an ELR PPDU based on a trigger frame in a wireless LAN system.

[0008] An example of this specification proposes a method for transmitting an ELR PPDU based on a trigger frame.

[0009] The present 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 the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0010] The present embodiment is performed in a receiving STA, and the receiving STA may correspond to at least one STA (station) or non-AP MLD (non-access point Multi-link Device). The transmitting STA of the present embodiment may correspond to an AP (access point) or AP MLD.

[0011] The present embodiment proposes a method for configuring a trigger frame for soliciting ELR PPDU transmission from a plurality of non-AP STAs. Specifically, the present embodiment proposes a method for requesting ELR PPDU transmission for all non-AP STAs based on a common information field or a special user information field of the trigger frame, or for requesting ELR PPDU transmission for a specific non-AP STA based on a user information field of the trigger frame. Accordingly, since the AP already knows information included in the legacy preamble of the ELR PPDU transmitted by the plurality of non-AP STAs (because the AP requested it through the trigger frame), the performance of the L-SIG of the legacy preamble does not act as a bottleneck or obstacle compared to the performance of the data.

[0012] Multiple receiving STAs (stations) receive a trigger frame from a transmitting STA.

[0013] The above plurality of receiving STAs transmit an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) to the transmitting STA based on the trigger frame.

[0014] The above trigger frame includes a user information field. The user information field includes instruction information for transmission of the ELR PPDU.

[0015] Specifically, the user information field may further include at least one of an AID12 subfield, a RU (Resource Unit) allocation subfield, a UL (uplink) FEC (Forward Error Correction) coding type subfield, a UL UHR-MCS (Ultra High Reliability-Modulation and Coding Scheme) subfield, an SS (Spatial Stream) allocation subfield, a PS160 subfield, and a Trigger Dependent User Info subfield.

[0016] The AID12 subfield may include an AID (Association IDentifier) ​​of a receiving STA transmitting the ELR PPDU. The RU allocation subfield may include allocation information for a 20MHz or 242-tone RU through which the ELR PPDU is transmitted. The UL FEC coding type subfield may include information about BCC (Binary Convolutional Code) or LDPC (Low-Density Parity Check) coding. The UL UHR-MCS subfield may include information about UHR-MCS 0 or UHR-MCS 1 used when transmitting the ELR PPDU. The PS160 subfield may include information about a 160MHz channel in which a 20MHz or 242-tone RU through which the ELR PPDU is transmitted exists.

[0017] For example, the SS allocation subfield may include a Starting Spatial Stream subfield and a Number of Spatial Streams subfield. However, if the number of spatial streams used to transmit the ELR PPDU is fixed to one, there is no need to transmit information about the number of spatial streams, so the Number of Spatial Streams subfield may be reserved.

[0018] As another example, the SS allocation subfield may include a Starting Spatial Stream subfield, a Number of Spatial Streams subfield, and indication information for transmission of the ELR PPDU. Similarly, if the number of spatial streams used for transmitting the ELR PPDU is fixed to one, the Number of Spatial Streams subfield may be set to 1 bit or reserved. The indication information for transmission of the ELR PPDU may be set to 1 bit. Since the Number of Spatial Streams subfield is changed from the existing 2 bits to 1 bit, the remaining 1 bit may be used as indication information for transmission of the ELR PPDU.

[0019] As another example, the indication information for transmission of the ELR PPDU may be included in the trigger dependent user information subfield.

[0020] A specific example of requesting transmission of ELR PPDUs from multiple non-AP STAs through the above trigger frame is as follows.

[0021] Based on the trigger frame being transmitted in an 80 MHz band and the plurality of receiving STAs including first to fourth receiving STAs, the user information field may include first user information for the first receiving STA, second user information for the second receiving STA, third user information for the third receiving STA, and fourth user information for the fourth receiving STA.

[0022] The RU allocation subfield included in the first user information may include information about a first RU through which the first receiving STA transmits the ELR PPDU. The RU allocation subfield included in the second user information may include information about a second RU through which the second receiving STA transmits the ELR PPDU. The RU allocation subfield included in the third user information may include information about a third RU through which the third receiving STA transmits the ELR PPDU. The RU allocation subfield included in the fourth user information may include information about a fourth RU through which the fourth receiving STA transmits the ELR PPDU.

[0023] The information about the first to fourth RUs may be information about the index of a 20MHz or 242-tone RU through which the ELR PPDU is transmitted. For example, the information about the first RU may indicate the first 20MHz or first 242-tone RU in the 80MHz band. The information about the second RU may indicate the second 20MHz or second 242-tone RU in the 80MHz band. The information about the third RU may indicate the third 20MHz or third 242-tone RU in the 80MHz band. The information about the fourth RU may indicate the fourth 20MHz or fourth 242-tone RU in the 80MHz band.

[0024] That is, the RU allocation subfield of the user information field only indicates the index of the 20MHz or 242-tone RU allocated to each receiving STA for transmitting the ELR PPDU, and the RU actually used for transmitting the ELR PPDU is preset as follows. Specifically, each of the first to fourth RUs may be a resource unit in which a 52-tone RU is replicated four times in the frequency domain or a resource unit in which a 106-tone RU is replicated twice in the frequency domain.

[0025] That is, the present embodiment proposes a method for requesting ELR PPDU transmission of a plurality of non-AP STAs based on a user information field of a trigger frame (i.e., a request per user). Specifically, the user information field may be defined by adding instruction information for transmission of the ELR PPDU, or the AID12 subfield, the RU allocation subfield, the UL FEC coding type subfield, the UL UHR-MCS subfield, the SS allocation subfield, the PS160 subfield, etc. included in the user information field may be changed to request ELR PPDU transmission of the plurality of non-AP STAs.

[0026] According to the method proposed by the present embodiment, since the AP already knows the information included in the legacy preamble of the ELR PPDU transmitted by the plurality of non-AP STAs (because the AP requested it through the trigger frame), there is an effect that the performance of the L-SIG of the legacy preamble does not act as a bottleneck or obstacle compared to the performance of the data. In addition, by performing transmission of ELR PPDUs to the plurality of non-AP STAs in the uplink, there is also an effect that the signal transmission and reception performance for a plurality of non-AP STAs located at a long range can be improved.

[0027] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0028] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

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

[0030] Figure 4 illustrates one embodiment of a multi-link (ML).

[0031] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0032] Figure 6 is a diagram showing the layout of resource units (RUs) used for 20MHz PPDU.

[0033] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0034] Figure 8 is a diagram showing the layout of resource units (RUs) used for 80MHz PPDU.

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

[0036] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0037] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0038] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

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

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

[0041] Figure 15 illustrates an example of a UHR ELR PPDU format.

[0042] Figure 16 illustrates an example where RRU52 is repeated four times in a UHR ELR PPDU.

[0043] Figure 17 is a graph showing the performance difference between the legacy preamble and data field during LE / ELR transmission.

[0044] Figure 18 shows an example of the UHR variant common info field format of a trigger frame.

[0045] Figure 19 shows an example of the special user info field format of a trigger frame.

[0046] Figure 20 shows an example of the UHR variant user info field format of a trigger frame.

[0047] Figure 21 shows an example of the SS Allocation subfield format of the UHR variant user info field.

[0048] Figure 22 illustrates an example of LR / ELR transmission based on a trigger frame.

[0049] Figure 23 illustrates another example of the LR / ELR PPDU format.

[0050] Figure 24 shows an example of the U-SIG format when U-SIG is repeated in one symbol unit.

[0051] Figure 25 shows an example of the U-SIG format when U-SIG is repeated in two symbol units.

[0052] Figure 26 illustrates a procedure for multiple non-AP STAs to perform trigger-based ELR transmissions at 80 MHz.

[0053] Figure 27 illustrates a procedure in which multiple non-AP STAs perform ELR transmission at 80 MHz.

[0054] Figure 28 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0055] Fig. 29 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0056] FIG. 30 is a flowchart illustrating a procedure in which a transmitting STA according to the present embodiment instructs or requests an ELR PPDU based on a trigger frame.

[0057] FIG. 31 is a flowchart illustrating a procedure for a receiving STA to transmit an ELR PPDU based on a trigger frame according to the present embodiment.

[0058] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0059] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0060] In this specification, “at least one of A and B” can 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” can be interpreted identically to “at least one of A and B.”

[0061] In addition, parentheses used in this specification may mean “for example.” Specifically, when “control information (UHR-Signal field)” is indicated, the “UHR-Signal field” may be suggested as an example of “control information.” In other words, the “control information” in this specification is not limited to the “UHR-Signal field,” and the “UHR-Signal field” may be suggested as an example of “control information.” In addition, even when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be suggested as an example of “control information.”

[0062] Additionally, as used herein, “a / an” can mean “at least one” or “one or more.” Additionally, terms ending in “(s)” can mean “at least one” or “one or more.”

[0063] Additionally, the expressions “based on” or “on the basis of” or “according to” used herein mean “based at least in part on” and not “based solely on.”

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

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

[0066] In order to explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0067] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0068] 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 the present specification may also be referred to by various names such as a mobile terminal, a wireless device, a Wireless Transmit / Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a Mobile Subscriber Unit, or simply a user. The STA (110, 120) of the present specification may also be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) of the present specification may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

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

[0070] The STA (110, 120) of this specification can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard). In addition, the STA of this specification can be implemented in various devices such as a mobile phone, a vehicle, a personal computer, etc. In addition, the STA of this specification can support communication for various communication services such as voice calls, video calls, data communications, and autonomous driving (self-driving, autonomous-driving).

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

[0072] Based on the sub-drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0073] The first STA (110) may include a processor (111), a 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.

[0074] The transceiver (113) of the first STA performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0075] 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 transmission signal, and perform control for signal transmission. The memory (112) of the AP can store a signal received through the transceiver (113) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

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

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

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

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

[0080] In the following specification, devices called (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. without specific drawing symbols may also refer to the STA (110, 120) of FIG. 1. For example, in the example below, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. In addition, in the example below, 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 that generates a transmission / reception signal or performs data processing or operation in advance for a transmission / reception signal may include 1) an operation of determining / obtaining / configuring / computing / decoding / encoding bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU, 2) an operation of determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 3) an operation of determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (112, 122) of FIG. 1.

[0081] The device / STA of the sub-drawing (a) of the above-described Fig. 1 can be modified as in the sub-drawing (b) of Fig. 1. Hereinafter, the STA (110, 120) of the present specification will be described based on the sub-drawing (b) of Fig. 1.

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

[0083] 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, Access Point (AP), 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) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.

[0084] For example, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal being received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1 being acquired by a processor (111, 121) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 being acquired by a processing chip (114, 124) illustrated in sub-drawing (b) of FIG.

[0085] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the 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.

[0086] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device. 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 an enhanced processor thereof.

[0087] In this specification, uplink may mean a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packet / signal, etc. may be transmitted through the uplink. In addition, in this specification, downlink may mean a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packet / signal, etc. may be transmitted through the downlink.

[0088] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0089] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0090] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0091] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter, BSS). The BSSs (200, 205) are a collection of APs and STAs, such as an access point (AP) 225 and a station (STA1, 200-1), that have successfully synchronized and can communicate with each other, and are not a concept that designates a specific area. The BSS (205) may also include one or more STAs (205-1, 205-2) that can be associated with one AP (230).

[0092] A BSS may include at least one STA, an AP (225, 230) providing a distribution service, and a distribution system (DS, 210) connecting multiple APs.

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

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

[0095] In a BSS such as the upper part 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 and perform communication between STAs without an AP (225, 230). A network that establishes a network and performs communication between STAs without an AP (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0096] The bottom of Figure 2 is a conceptual diagram showing IBSS.

[0097] 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 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 access to the distributed system is not permitted, forming a self-contained network.

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

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

[0100] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover which APs exist in the vicinity while moving between channels and waits for a response. A responder transmits a probe response frame to the STA that transmitted the probe request frame in response to the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In a BSS, the AP transmits the beacon frame, so the AP becomes the responder. In an IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not constant. 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 (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0101] Although not shown in the example of FIG. 3, the scanning operation can also be performed in a passive scanning manner. An STA performing scanning based on passive scanning can wait for a beacon frame while moving between channels. A beacon frame is one of the management frames in IEEE 802.11. It announces the presence of a wireless network and is periodically transmitted so that the scanning STA can find the wireless network and participate in the wireless network. In the BSS, the AP periodically transmits the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. An STA that receives a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.

[0102] An STA that discovers a 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 below. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and the AP responds by transmitting an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

[0103] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group.

[0104] An STA can transmit an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

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

[0106] 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 four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame.

[0107] Figure 4 illustrates one embodiment of a multi-link (ML).

[0108] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate over a remote link. The MLDs can be categorized into AP MLDs including multiple AP STAs and non-AP MLDs including multiple non-AP STAs. That is, the AP MLD can include affiliated APs (i.e., AP STAs), and the non-AP MLD can include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0109] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be allocated to the first and second links. The first and second multilinks may be identified through 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 second link may be configured in different bands.

[0110] The AP MLD of FIG. 4 includes three affiliated APs. In the 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 the 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. Furthermore, in the 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. Furthermore, in the 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.

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

[0112] 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.

[0113] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0114] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) of the present specification can transmit and / or receive the PPDU of FIG. 5. The PPDU described in the present specification may have, for example, the structure of FIG. 5. In addition, the PPDU described in the present specification may be called by various names such as a transmission PPDU, a reception PPDU, a first type PPDU, or an Nth type PPDU, etc. The PPDU described in the present specification can be used in a WLAN system defined according to IEEE 802.11bn and / or a next-generation WLAN system that improves IEEE 802.11bn.

[0115] 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 a single-user (SU) mode / type / transmission, a multi-user (MU) mode / type / transmission, and a null data packet (NDP) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the Data field illustrated may be omitted. If the PPDU of FIG. 5 is used for a trigger-based (TB) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU with the UHR-SIG omitted in the example of FIG. 5.

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

[0117] Each block illustrated in Fig. 5 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 5, 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.

[0118] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in FIG. 5 may be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields may 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 may be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields may be expressed in units of 78.125 kHz.

[0119] In the PPDU of Fig. 5, L-LTF and L-STF may be identical to conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0120] The L-SIG field of FIG. 5 may include, 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 include information about 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 UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is a 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, 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 an UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0121] For example, (non-AP and AP) STAs can apply BCC encoding based on a code rate of 1 / 2 to the 24 bits of information in the L-SIG field. Then, the transmitting STA can obtain 48 BCC coded bits. BPSK modulation can be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarriers {subcarrier index -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, 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 {-1, -1, -1, 1} to the subcarrier indices {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0122] For example, (non-AP and AP) STA can generate RL-SIG, which is generated in the same manner as L-SIG. BPSK modulation can be applied to RL-SIG. Receiving (non-AP and AP) STA can determine whether the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of RL-SIG. In other words, if RL-SIG is present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of HE PPDU, EHT PPDU, or UHR PPDU. In other words, if RL-SIG is not present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of non-HT PPDU, HT PPDU, or VHT PPDU. 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.

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

[0124] A U-SIG can contain N bits of information and can include information for identifying the type of EHT PPDU. For example, a U-SIG can be formed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., an OFDM symbol) for a U-SIG can have a duration of 4 microseconds. Each symbol of a U-SIG can be used to transmit 26 bits of information. For example, each symbol of a U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0125] For example, A bit information (e.g., 52 uncoded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bits of information (e.g., 26 uncoded bits) out of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bits of information (e.g., 26 uncoded bits) out of the total A bit information. For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52 coded bits, and perform interleaving on the 52 coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols allocated to each U-SIG symbol. 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. The 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.

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

[0127] The A bit information (e.g., 52 uncoded bits) transmitted by the 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 can be assigned only to the first symbol of the U-SIG, or the version-independent bits can be assigned to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.

[0128] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.

[0129] In other words, when the (AP / non-AP) STA transmits an EHT PPDU, it can set the 3-bit PHY version identifier to the first value. In other words, the 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 an UHR PPDU based on the PHY version identifier having the second value.

[0130] 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 relates to UL communication, and the second value of the UL / DL flag field relates to DL communication.

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

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

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

[0134] Preamble puncturing may be applied to the PPDU of FIG. 5. Preamble puncturing refers to applying puncturing to a portion of the entire bandwidth of the PPDU (e.g., the secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA may apply puncturing to the secondary 20 MHz band within the 80 MHz band, and transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

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

[0136] 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.

[0137] 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 individually configured in units of 80 MHz. 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 about a 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern). Meanwhile, the UHR-SIG consecutive to the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern), and the UHR-SIG consecutive to the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about a preamble puncturing pattern).

[0138] Additionally or alternatively, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. 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).

[0139] 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 can contain different U-SIGs.

[0140] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted via at least one symbol, and each 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.

[0141] UHR-SIG provides additional signals to the U-SIG field to enable STAs to interpret / decode UHR PPDUs. The UHR-SIG field may contain U-SIG overflow bits that are common to all users. The UHR-SIG field also contains resource allocation information, allowing STAs to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

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

[0143] FIG. 6 is a diagram illustrating the layout of resource units (RUs) used for a 20 MHz PPDU. That is, the 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.

[0144] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for a receiving station, i.e., a user.

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

[0146] In the example of Fig. 6, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are proposed. Since the specific sizes 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 represented as N-tone RU, etc. For example, 26-RU may be represented as 26-tone RU.

[0147] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0148] As in the example of Fig. 6 where RUs of various sizes were used, the example of Fig. 7 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0149] Additionally, as illustrated, 484 RUs 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.

[0150] Figure 8 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of resource units (RUs) used in this specification may vary. For example, the layout of resource units (RUs) used in the 80MHz band may vary.

[0151] Figure 9 illustrates an operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) may perform channel access through contending (i.e., backoff operation) and transmit a trigger frame (930). That is, the transmitting STA (e.g., AP) may transmit a PPDU including a trigger frame (930). When a PPDU including a trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

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

[0153] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0154] The 2.4 GHz band may be referred to by other names, such as the first band (band). Furthermore, 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 between 2.4 and 2.5 GHz) are used / supported / defined.

[0155] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz 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 channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned channel index N may be (2.407 + 0.005*N) GHz. The channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of the channel indices and center frequencies may change.

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

[0157] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0158] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with a center frequency greater than or equal to 5 GHz 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 are subject to change.

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

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

[0161] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0162] The 6 GHz band may also be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, or defined. The specific figures shown in Figure 12 are subject to change.

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

[0164] Accordingly, the indexes (or channel numbers) of the 20 MHz channels of 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, It can be 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule mentioned above, the indices of the 40 MHz channels in Fig. 12 can 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.

[0165] Below, the structure and types / subtypes of MAC frames are described.

[0166] Fig. 13 illustrates an example of a header of a MAC frame. As illustrated, the MAC frame may include a frame control field / information of 2 octets in length, a duration field / information of 2 octets in length, a RA (Receiver Address) field / information of 6 octets in length, and a TA (Transmitter Address) field / information of 6 octets in length. As illustrated in Fig. 13, the four fields may be consecutive to each other. 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.

[0167] The MAC header illustrated in Fig. 13 may be positioned at the very front of a MAC frame. That is, the MAC frame may include a MAC header as illustrated in Fig. 13 and MAC body fields / information subsequent to the MAC header. The MAC frame including the MAC header of Fig. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) illustrated in Fig. 5.

[0168] The MAC frames included in the data field of the PPDU of this specification can be classified into various types. For example, the MAC frames of this specification can be classified into control frames, management frames, and data frames.

[0169] For example, the 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 WLAN. For the management frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are set to 00. In addition, 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).

[0170] For example, the control frame includes 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 WLAN. For the control frame, the value of the type field (B3 and B2) in FIG. 13 is 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).

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

[0172] The MAC frame / signal used in this specification can be identified through the type field / information and subtype field / information described above. For example, “frame” in this specification can mean a MAC frame in which the type bits B3 and B2 bits in the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 bits in 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 PPDUs).

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

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

[0175] The processor (610) of FIG. 14 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (610) of FIG. 14 may be identical to the processing chip (114, 124) of FIG. 1.

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

[0177] Referring to FIG. 14, a power management module (611) manages power to a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0178] Referring to FIG. 14, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related input to be used by the processor (610).

[0179] 1. Definition of ELR (Enhanced Long Range) PPDU format

[0180] Next Wi-Fi (beyond 802.11be or 802.11bn) aims to support ultra-high reliability when transmitting signals to STAs, and various technologies are being considered for this purpose, such as high throughput, low latency, and extended range support. Therefore, the UHR long range PPDU (or UHR ELR (extended long range) PPDU) format is defined to reliably transmit signals over long distances in 802.11bn and provide smooth signal transmission and services to STAs located at the boundary of AP coverage.

[0181] Figure 15 illustrates an example of a UHR ELR PPDU format.

[0182] Referring to FIG. 15, unlike the existing UHR MU PPDU, the UHR ELR PPDU has an additional ELR-MARK field and includes an ELR-SIG field instead of the UHR-SIG field.

[0183] UHR ELR PPDU can be used to overcome link budget imbalance between downlink and uplink or to achieve higher data rates than direct sequence spread spectrum (DSSS) PPDU.

[0184] The UHR ELR PPDU is applicable to the 2.4 GHz, 5 GHz, and 6 GHz bands in the uplink, and only to the 2.4 GHz band in the downlink. The UHR PPDU is defined only for UHR-MCS 0 and 1 with 20 MHz PPDU bandwidth, a single spatial stream, and four frequency domain overlaps via 52-tone regular RUs (RRU52s or 52-tone RRUs) on the primary 20 MHz channel. The UHR ELR PPDU supports binary convolutional code (BCC) and low-density parity check (LDPC) coding with a codeword block length of up to 1944 bits. The UHR ELR PPDU has the PPDU Type And Compression Mode subfield of the U-SIG field set to 3 and includes the ELR-MARK field immediately following the U-SIG field. Additionally, the UHR ELR PPDU further includes an ELR-SIG field between the UHR-LTF and Data fields.

[0185] Specifically, to identify a UHR ELR PPDU, bits B0-B1 (PPDU Type And Compression Mode subfield) of the U-SIG-2 field are set to 3, and auxiliary bits B13-B15 (ELR Validate subfield) of the U-SIG-2 field are set to 7.

[0186] The ELR-MARK field provides additional signaling to distinguish UHR ELR PPDUs from other PPDUs. It utilizes predefined tone patterns for cross-correlation, improves performance in low-SNR (Signal-to-Noise Ratio) environments, and supports coherent combining across multiple receive antennas to enhance detection performance.

[0187] Additionally, the ELR-MARK field contains BSS_COLOR, a unique identifier that indicates the BSS color of the STA. The BSS_COLOR value ranges from 0 to 63. A 64 x 96 matrix H, called the ELR-MARK matrix, specifies 64 orthogonal sequences. Each row corresponds to a BSS color, and each column corresponds to data carried on each subcarrier of two ELR-MARK symbols. These orthogonal sequences allow the STA to determine whether a UHR ELR PPDU is transmitted on the OBSS.

[0188] The ELR-SIG field contains information necessary to interpret the UHR ELR PPDU. The integer field of the ELR-SIG field is transmitted in unsigned binary format with the Least Significant Bit (LSB) first, and the LSB is located in the lowest numbered bit position.

[0189] Figure 16 illustrates an example where RRU52 is repeated four times in a UHR ELR PPDU.

[0190] Referring to Figure 16, the ELR-SIG and the payload portion of the UH ELR PPDU are transmitted over a 52-tone generic RU (RRU52) and are replicated four times in the frequency domain across four RRU52s (RRU52 4x DUP) at 20 MHz. The replication in the frequency domain is described as follows.

[0191] - After encoding and BPSK or QPSK modulation are performed on 52-tone RRU 1 in 20MHz PPDU, 52-tone RRU 1 is replicated to 52-tone RRU 2, 52-tone RRU 3, and 52-tone RRU 4 in 20MHz PPDU.

[0192] - To reduce PAPR, a phase rotation of -1 is applied to the data subcarriers of the lower half of the 52-tone RRU 3 and the upper half of the 52-tone RRU 4 in a 20MHz PPDU. At this time, a phase rotation of -1 is not applied to the pilot subcarriers.

[0193] - For four 52-tone RRUs, frequency domain replication occurs after the LDPC tone mapping operation when using LDPC encoding, and after the constellation mapping operation when using BCC encoding.

[0194] 2. Trigger-based ELR transmission for a single user

[0195] In Next Wi-Fi, long-range transmission can be considered to ensure smooth signal transmission and reception for STAs within the coverage boundary of the AP and to address coverage imbalance caused by the difference in TX power between the AP and non-AP STAs. At this time, long-range transmission can be considered in the UL (uplink) by considering the TX power of non-AP STAs. The TX power difference between the AP and non-AP STAs has a link margin of approximately 6 dB in both the DL (downlink) and UL. Therefore, to overcome this link margin, LR / ELR transmission can be transmitted using the following limited transmission parameters.

[0196] i. LR / ELR transmission is transmitted using 20MHz BW, and the number of SS (Spatial Stream) used during transmission can be limited to 1 or 2.

[0197] ii. To increase reliability and robustness for LR / ELR transmission, data can be structured using MCS0 or MCS15.

[0198] iii. Data is transmitted repeatedly in small size RUs to compensate for link margin (ex. 6 dB) caused by TX power differences.

[0199] iii-A. For example, data can be transmitted repeatedly using 52 tone RU or 106 tone RU.

[0200] iii-B. When using 52 tone RU, data is repeatedly transmitted to four 52 tone RUs within 20 MHz, thereby achieving a 6 dB link budget.

[0201] iii-C. As another example, when using 106 tone RU, data is transmitted by repeating modulated symbols within 106 tone RU using MCS15, and the 106 tone RU configured in this way is repeated once within 20 MHz.

[0202] As mentioned above, through repeated transmission of small-size RUs and use of the lowest MCS, the data field can improve performance by supplementing the link margin. However, the performance of the legacy preamble included in the LR / ELR transmission PPDU, i.e., the performance of L-SIG, is worse than the performance of the data. Therefore, the L-SIG or legacy preamble can become a bottleneck (bottleneck or obstacle) during LR / ELR transmission.

[0203] Figure 17 is a graph showing the performance difference between the legacy preamble and data field during LE / ELR transmission.

[0204] Referring to Figure 17, for both graphs (Channel D, Channel B), the required SNR (Signal-to-Noise Ratio) for data (52tone - 4 rep) is 4 based on PER 10%, whereas the required SNR for U-SIG is 6 based on PER 1%, and the required SNR for L-SIG is 5 based on PER 1%, so it can be seen that the performance of L-SIG / U-SIG is worse than the performance of data.

[0205] In order to prevent performance degradation due to the performance difference between the legacy preamble and the data field during LR / ELR transmission as shown in Fig. 17, this embodiment proposes a method of performing LR / ELR transmission based on a trigger frame within a BSS.

[0206] To solicit LR / ELR transmission, the AP transmits a trigger frame to a non-AP STA, and the non-AP STA performs LR / ELR transmission based on information determined through the received trigger frame. In this way, since LR / ELR transmission is performed based on the trigger frame transmitted by the AP, the information included in the legacy preamble and SIG fields of the LR / ELR PPDU transmitted by the non-AP STA may be information already known to the AP. Therefore, the L-SIG and SIG fields included in the LR / ELR PPDU can be ignored by the AP when transmitting and receiving LR / ELR. Accordingly, the performance of the L-SIG and SIG fields when transmitting and receiving LR / ELR does not act as a bottleneck for LR / ELR data transmission.

[0207] Additionally, protection can be performed on LR / ELR PPDUs transmitted by non-AP STAs within AP coverage through the Trigger frame transmitted by the AP.

[0208] The trigger frame may include a common info field and a user info field. There are four variants for the user info field, namely, a special user info field, a HE variant user info field, an EHT variant user info field and a UHR variant user info field. The user info field addressed to a non-AP STA is one of the HE variant, EHT variant or UHR variant. The special user info field is identified by the value of AID12 being 2007 and is optionally present in a trigger frame generated by an EHT AP or a UHR AP. When the special user info field is present, it is located immediately after the common info field of the trigger frame, and the special user info field conveys information about the U-SIG field of the EHT or UHR TB PPDU.

[0209] Figure 18 shows an example of the UHR variant common info field format of a trigger frame.

[0210] A non-AP HE STA interprets the common info field as a HE variant common info field. A non-AP EHT STA interprets the common info field as a HE variant common info field if B54 and B55 of the common info field are 1, otherwise it interprets the common info field as an EHT variant common info field. A non-AP UHR STA interprets the common info field as a HE variant common info field if B54 and B55 of the common info field are 1, and interprets the common info field as an EHT or UHR variant common info field depending on the PHY Version Identifier subfield of the special user info field.

[0211] Referring to Figure 18, bits B22, B26, B53, and B63 of the UHR variant common info field are reserved.

[0212] Figure 19 shows an example of the special user info field format of a trigger frame.

[0213] Referring to Figure 19, bits B37 to B39 of the special user info field are reserved.

[0214] Figure 20 shows an example of the UHR variant user info field format of a trigger frame.

[0215] Figure 21 shows an example of the SS Allocation subfield format of the UHR variant user info field.

[0216] Referring to FIGS. 20 and 21, the SS Allocation subfield of the UHR variant user info field is changed to 5 bits (from the existing 6 bits) unlike the EHT variant, because up to 4 spatial streams are supported.

[0217] The LR / ELR transmission procedure performed based on the trigger frame described above can be defined as follows.

[0218] Figure 22 illustrates an example of LR / ELR transmission based on a trigger frame.

[0219] As shown in Fig. 22, the AP transmits a trigger frame to a non-AP STA to perform LR / ELR transmission. At this time, the trigger frame transmitted by the AP to the non-AP STA may be configured to include the following information to instruct LR / ELR transmission.

[0220] <LR / ELR 전송에 대한 지시자를 포함한 trigger frame에 대한 정의>

[0221] The trigger frame transmitted by the AP to solicit LR / ELR transmission performs instructions for LR / ELR transmission using the following method.

[0222] 2-1. Include LR / ELR indicators in the common info field of the trigger frame.

[0223] As an example, the embodiment of the common info field of the Trigger frame described below is proposed based on the UHR variant, and can be applied equally to other variants.

[0224] The indicator information for LR / ELR transmission consists of 1 bit and can be defined as, for example, the LR / ELR field.

[0225] The LR / ELR field can be defined using one of the B22, B26, B53, or B63 bits of the common info field, but this is only an example and can be defined using other bits.

[0226] When the LR / ELR field is set to 1, it indicates triggered LR / ELR transmission, and when the LR / ELR field is set to 0, it indicates normal TB PPDU transmission.

[0227] When the LR / ELR field of the Common info field is set to 1 and LR / ELR transmission is solicited, the RA (Resource Allocation) subfield for data transmission can be set as follows.

[0228] - The RU allocation subfield for LR / ELR transmission is transmitted using existing RA information, and a non-AP STA repeatedly transmits the allocated RU within 20 MHz when the LR / ELR field of the common info field is set to 1.

[0229] For example, when using a 52 tone RU, the RA is configured with information pointing to 52 tone RU index 1, and the non-AP STA that receives this transmits the allocated RU four times repeatedly.

[0230] As another example, when using 106 tone RU, RA is configured with information pointing to 106 tone RU index 1, and the non-AP STA that receives it transmits the allocated RU twice repeatedly.

[0231] - As another example, different from the above, RA information for RU repeat transmission can be newly defined and used to provide instructions.

[0232] For example, the RU size used for LR / ELR transmission can be defined as 52 tone RU or 106 tone RU / both 52 tone RU and 106 tone RU.

[0233] In the above case, RA information is composed of the following information.

[0234] For example, RA information for LR / ELR can be defined using values ​​107 to 127 of the RU Allocation subfield of the UHR variant user info field.

[0235] For example, information for each RU can be defined as follows:

[0236] - 52 tone RU with 4 repetitions = value 107

[0237] - 106 tone RU with 2 repetitions = value 108

[0238] 2-2. Include LR / ELR indicators in the special user info field of the trigger frame.

[0239] As another example, instructions for LR / ELR transmission can be performed via a special user info field included in the trigger frame.

[0240] The LR / ELR field is defined when the value of the PHY version identifier field of the special user info field is set to a non-zero value.

[0241] The above LR / ELR field is a special user info field that can be defined using one bit from B37 to B39, and the above 1 bit is set to 1 to indicate that LR / ELR transmission is solicited.

[0242] Even when the instruction information for LR / ELR transmission is transmitted through the special user info field, the RA information can be configured in the same way as when the instruction is made through the common field, and the RA information for LR / ELR transmission can be transmitted to the non-AP STA.

[0243] 2-3. Include LR / ELR indicators in the user info field of the trigger frame.

[0244] When using the User info field, instructions for LR / ELR transmission are performed using the following method.

[0245] 2-3-1) Define the LR / ELR field in the User info field to instruct LR / ELR transmission.

[0246] A. The user info field is configured to include a LR / ELR field consisting of 1 bit, so that the AP can solicit LR / ELR transmission only to STAs that support LR / ELR.

[0247] Ai. As an example, since Nss is fixed to 1 when transmitting LR / ELR, the LR / ELR subfield can be defined using some bits of the SS Allocation subfield.

[0248] B. As another example, LR / ELR transmission can be defined by defining a LR / ELR subfield in the Trigger Dependent User Info field.

[0249] C. When LR / ELR transmission is indicated by defining the LR / ELR field in the User info field as described above, information on the RU or allocated RU used by the triggered non-AP STA for LR / ELR transmission can be set by applying the same method as suggested above.

[0250] 2-3-2) Instructions for LR / ELR transmission through RA information in the User info field

[0251] A. By defining RU allocation information for LR / ELR transmission and allocating the above RA information, the STA can recognize that the transmission is LR / ELR transmission.

[0252] RA information by Ai. LR / ELR transmission can be defined as follows.

[0253] Ai-1. RA information for LR / ELR can be defined using values ​​107 to 127 of the RU Allocation subfield of the UHR variant user info field.

[0254] For example, information for each RU can be defined as follows:

[0255] i. 52 tone RU with 4 repetitions = value 107

[0256] ii. 106 tone RU with 2 repetitions = value 108

[0257] Ai-2. Since LR / ELR transmission is indicated using the RA information defined as above, there is no need to define additional fields, so there is an advantage in that complexity does not increase.

[0258] 2-4. LR / ELR TB PPDU Format Definition

[0259] The PPDU used in trigger-based LR / ELR transmission can be transmitted using the previously defined RU using the previously defined EHT TB PPDU. As another example, the LR / ELR PPDU format defined as follows can be used to increase SNR gain for the legacy preamble and SIG field.

[0260] Figure 23 illustrates another example of the LR / ELR PPDU format.

[0261] As shown in Fig. 23, in order to increase the reception SNR for L-SIG, L-SIG is transmitted twice repeatedly and U-SIG is also transmitted repeatedly.

[0262] Figure 24 shows an example of the U-SIG format when U-SIG is repeated in one symbol unit.

[0263] Figure 25 shows an example of the U-SIG format when U-SIG is repeated in two symbol units.

[0264] U-SIG is transmitted by repeating in units of two symbols as in Fig. 25, or in units of one symbol as in Fig. 24. At this time, the repetition can be repeated a total of three times, the same as L-SIG.

[0265] 3. Trigger-based ELR transmission for multiple users

[0266] Using the ELR transmission method defined as above, an AP can receive signals using ELR transmission from multiple non-AP STAs using a wide bandwidth.

[0267] The above wide bandwidth refers to 40, 80, 160, and 320 MHz. Although the BW (bandwidth) considering preamble puncturing is not specifically mentioned in this specification, the proposed method can be applied equally. That is, it can be equally applied to preamble puncturing and MRU (multiple resource unit) defined in 802.11be.

[0268] The AP solicits ELR transmission by transmitting a trigger frame to multiple STAs to receive signals using ELR from multiple non-AP STAs in the UL. At this time, ELR transmission of each STA solicited by the AP is performed using 20MHz units within the AP's operating BW, and such transmission can be represented as shown in Figure 26.

[0269] Figure 26 illustrates a procedure for multiple non-AP STAs to perform trigger-based ELR transmissions at 80 MHz.

[0270] As shown in Figure 26, in order for an AP to solicit ELR transmission to multiple non-AP STAs, a trigger frame can be configured as follows.

[0271] 3-1. The AP configures a trigger frame to solicit ELR transmission to multiple non-AP STAs.

[0272] A request or instruction for ELR transmission can be performed using the common info field, special user info field, or user info field of the Trigger frame, and can be indicated by defining a specific field within the above fields.

[0273] In order to trigger ELR transmission for multiple STAs when a request and instruction for ELR transmission is performed using a specific field or subfield of the Trigger frame, the Trigger frame can be configured as follows.

[0274] 3-1-1) When performing ELR transmission for multiple STAs, the RA field for each non-AP STA is set to RU allocation information for the 20MHz or 242 tone RU for which each STA will perform ELR transmission.

[0275] As shown in Fig. 26, an AP can request ELR transmission to multiple STAs using 20MHz BW within a wide bandwidth, and in order to request ELR transmission within a wide bandwidth to each non-AP STA, the RA field included in the user info field for STAs performing ELR is set as follows.

[0276] In order to indicate which 20MHz within the wide bandwidth or AP operating BW to use for ELR transmission, when performing ELR transmission for multiple STAs, the RA field for each non-AP STA is set to RU allocation information for the 20MHz or 242 tone RU on which each STA will perform ELR transmission.

[0277] For example, when requesting ELR transmission to four non-AP STAs within 80MHz, each non-AP STA receives RA information for 20MHz or 242 tone RU within 80MHz through the RA field as follows.

[0278] RA field of non-AP STA 1: first order 242 RU index

[0279] RA field of non-AP STA 2: second order 242 RU index

[0280] RA field of non-AP STA 3: third order 242 RU index

[0281] RA field of non-AP STA 4: fourth order 242 RU index

[0282] The RU or subchannel allocated through the above RA information is information about a 20MHz channel that performs ELR transmission, and the RU size actually used for ELR transmission is different from the above RU allocation information.

[0283] Using the instruction information for ELR transmission received through the trigger frame and the information about the 20MHz or 242 tone RU that performed the ELR transmission, the non-AP STA can perform ELR transmission using a specific 20MHz within the wide bandwidth.

[0284] In the case where the RU size and transmission method for ELR transmission described above are fixed and used, the non-AP STA uses the ELR instruction or request information included in the Trigger frame received from the AP and the RA information in the User field to perform ELR transmission using the determined RU size and transmission method at the allocated 20 MHz or 242 tone RU location.

[0285] 3-1-2) Reset SS allocation field for ELR transmission

[0286] As another example from the above, when the RU size and transmission method for ELR transmission are not fixed to one and one of the proposed methods is used, the following method can be used to perform instructions for the RU size and transmission mode for ELR transmission.

[0287] Considering that ELR transmission is generally robust, it can be transmitted with Nss=1 fixed. Therefore, the Number Of Spatial Streams subfield defined using 2 bits in the SS allocation field included in the user info field of the trigger frame can be redefined as follows.

[0288] The Number Of Spatial Streams subfield: 1bit

[0289] When transmitting ELR, the value of the above 1 bit indicates Nss = 1 and is always set to 0.

[0290] When the Number Of Spatial Streams subfield is defined as above, the remaining 1 bit (B4 or B5) is used to indicate the RU size and transmission mode used in ELR transmission, and the remaining 1 bit can be defined as the ELR mode subfield as follows.

[0291] -> ELR mode subfield (1 bit)

[0292] For example, when the ELR mode subfield is set to 0, it indicates 52 tone RU and 4 repetitions, and when the ELR mode subfield is set to 1, it indicates 106 tone RU and 2 repetitions.

[0293] An example of the SS allocation field for ELR transmission is as follows:

[0294] FieldsStarting Spatial StreamThe Number Of Spatial StreamsELR modeBits3(or 4)11

[0295] 3-2. ELR transmission solicited through the trigger frame transmitted by the AP uses the ELR PPDU format, not the TB PPDU.

[0296] As another example, ELR transmission solicited through a Trigger frame transmitted by an AP can transmit and receive signals using the ELR PPDU format rather than the TB PPDU format.

[0297] In order to solicit ELR PPDUs from multiple STAs, the AP transmits a trigger frame including an indicator that it solicits ELR PPDUs. At this time, the indicator can be transmitted through the common info field or special user info field of the trigger frame.

[0298] An indicator for ELR PPDU transmission can be defined as, for example, an ELR PPDU request field or an ELR PPDU transit field, and a field defined as above can consist of 1 bit.

[0299] For example, when the ELR PPDU request field or the ELR PPDU transit field is transmitted through a common info field, the ELR PPDU request field or the ELR PPDU transit field may be defined by allocating one bit among B22, B26, B53, B56 to B63 of the common info field. As another example, when the ELR PPDU request field or the ELR PPDU transit field is transmitted through a special user info field, the ELR PPDU request field or the ELR PPDU transit field may be defined by allocating one bit among B37 to 39 in the special user info field.

[0300] The ELR PPDU request field or ELR PPDU transit field may be set to 1 to instruct the STA that has received the trigger frame to transmit an ELR PPDU. If the ELR PPDU request field or ELR PPDU transit field is set to 0, the non-AP STA that has received it transmits a TB PPDU.

[0301] The value of the PHY identifier field of the special user info field included in the ELR PPDU request field or ELR PPDU transit field is set to 1 or a value greater than 0.

[0302] When ELR PPDU transmission is solicited from the AP using a trigger frame, information about ELR PPDU transmission of a non-AP STA is transmitted through the user info field of the trigger frame.

[0303] The user info field of a trigger frame soliciting an ELR PPDU can be configured to include the following information:

[0304] AID12: AID of non-AP STA transmitting ELR PPDU

[0305] RU allocation: Consists of information about the 20MHz or 242 tone RU on which the ELR PPDU is transmitted.

[0306] UL FEC Coding Type: BCC or LDPC

[0307] UL UHR-MCS: If the data rate for ELR PPDU transmission is fixed or MCS0 is fixedly used when transmitting ELR PPDU, the UL UHR-MCS field may be omitted. As another example, when transmitting ELR PPDU, only robust MCS may be considered, so only MCS0 and MCS1 may be used. To indicate this, the UL UHR-MCS field may be defined as 1 bit, or in order to maintain consistency with the MCS field included in the user info field, the remaining values ​​of the UL UHR-MCS field may be reserved except for the values ​​indicating MCS0 and MCS1.

[0308] For example, UHR-MCS 0 and UHR-MCS 1 for ELR PPDU transmission can be defined as follows.

[0309] UHR-MCSModulationRateN BPSCS N SD N CPBS N DPBS Data rate (Mb / s) 1.6us GI0BPSK1 / 214848241.671QPSK1 / 224896483.33

[0310] SS Allocation: When the Nss used for ELR PPDU transmission is fixed to 1, there is no need to transmit information about the Nss, and in this case, the SS Allocation field can be composed of a Starting Spatial Stream (3 bits) and a reserved bit (2 or 3 bits).

[0311] In contrast, even if the Nss allocated to a non-AP STA is set to 1 when transmitting an ELR PPDU, the SS Allocation field can be composed of Starting Spatial Stream and Number Of Spatial Streams to maintain consistency in the configuration of SS Allocation, and each field can be composed of 3 bits. At this time, Number Of Spatial Streams is set to a value indicating one spatial stream, and other values ​​can be reserved.

[0312] PS160: It can be indicated for 160MHz where 20MHz or 242 tone RU exists to transmit ELR PPDU.

[0313] Figure 27 illustrates a procedure in which multiple non-AP STAs perform ELR transmission at 80 MHz.

[0314] Referring to FIG. 27, an AP transmits a trigger frame to solicit ELR transmission to a plurality of non-AP STAs, and the plurality of non-AP STAs can transmit ELR PPDUs, not TB PPDUs, through their respective allocated RUs.

[0315] Figure 28 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0316] An example of FIG. 28 may be performed at a transmitting STA or transmitting device (AP and / or non-AP STA).

[0317] Some of the steps (or detailed sub-steps described below) in the example of Fig. 28 may be omitted or changed.

[0318] Through step S2810, the transmitting device (transmitting STA) can obtain information regarding the aforementioned 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.

[0319] Through step S2820, the transmitting device can configure / generate a PPDU based on the acquired control information. The step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, step S2820 may include a step of configuring a UHR-SIG field including control information regarding a Tone Plan. That is, step S2820 may include a step of configuring a field including control information indicating the size / position of the RU (e.g., an N bitmap) and / or a step of configuring a field including an identifier (e.g., an AID) of an STA receiving the RU.

[0320] Additionally, step S2820 may include a step of generating an STF / LTF sequence to be transmitted through a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0321] Additionally, step S2820 may include a step of generating a data field (i.e., an MPDU) to be transmitted via a specific RU. The step of generating the data field may include a step of configuring it by applying UEQM / EQM.

[0322] The transmitting device can transmit the PPDU configured through step S2820 to the receiving device based on step S2830.

[0323] While performing step S2830, the transmitting device may perform at least one of operations such as CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion.

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

[0325] Fig. 29 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

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

[0327] An example of FIG. 29 may be performed at a receiving STA or receiving device (AP and / or non-AP STA).

[0328] Some of the steps (or detailed sub-steps described below) in the example of Fig. 29 may be omitted.

[0329] A receiving device (receiving STA) may receive all or part of a PPDU through step S2910. The received signal may have the form of FIG. 5.

[0330] The sub-step of step S2910 can be determined based on step S2830 of Fig. 28. That is, step S2910 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operations, and GI insert operations applied in step S2830.

[0331] At step S2920, the receiving device can decode 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.

[0332] 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 included in the L-SIG, U-SIG, and UHR SIG fields. Information regarding various Tone Plans (i.e., RUs) described herein can be included in the UHR-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RUs) through the UHR-SIG. In addition, information regarding the application of UEQM / EQM can be obtained through the UHR-SIG.

[0333] In step S2930, the receiving device can decode the remaining portion of the PPDU based on the information about the Tone Plan (i.e., RU) and UEQM / EQM acquired through step S2920. For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about one Plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the Tone Plan (i.e., RU) and the UEQM / EQM information, and acquire the MPDU included in the data field.

[0334] Additionally, the receiving device may perform a processing operation to transmit the decoded data to a higher layer (e.g., MAC layer) through step S2930. Additionally, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, a subsequent operation may be performed.

[0335] Hereinafter, the above-described embodiment will be described with reference to FIGS. 1 to 29.

[0336] FIG. 30 is a flowchart illustrating a procedure in which a transmitting STA according to the present embodiment instructs or requests an ELR PPDU based on a trigger frame.

[0337] An example of FIG. 30 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 on the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0338] An example of FIG. 30 is performed at a transmitting STA, which may correspond to an access point (AP) or an AP Multi-link Device (MLD). The receiving STA of FIG. 30 may correspond to at least one STA (station) or non-AP MLD.

[0339] The present embodiment proposes a method for configuring a trigger frame for soliciting ELR PPDU transmission from a plurality of non-AP STAs. Specifically, the present embodiment proposes a method for requesting ELR PPDU transmission for all non-AP STAs based on a common information field or a special user information field of the trigger frame, or for requesting ELR PPDU transmission for a specific non-AP STA based on a user information field of the trigger frame. Accordingly, since the AP already knows information included in the legacy preamble of the ELR PPDU transmitted by the plurality of non-AP STAs (because the AP requested it through the trigger frame), the performance of the L-SIG of the legacy preamble does not act as a bottleneck or obstacle compared to the performance of the data.

[0340] In step S3010, a transmitting STA (station) transmits a trigger frame to multiple receiving STAs.

[0341] In step S3020, the transmitting STA receives an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame from the plurality of receiving STAs.

[0342] The above trigger frame includes a user information field. The user information field includes instruction information for transmission of the ELR PPDU.

[0343] Specifically, the user information field may further include at least one of an AID12 subfield, a RU (Resource Unit) allocation subfield, a UL (uplink) FEC (Forward Error Correction) coding type subfield, a UL UHR-MCS (Ultra High Reliability-Modulation and Coding Scheme) subfield, an SS (Spatial Stream) allocation subfield, a PS160 subfield, and a Trigger Dependent User Info subfield.

[0344] The AID12 subfield may include an AID (Association IDentifier) ​​of a receiving STA transmitting the ELR PPDU. The RU allocation subfield may include allocation information for a 20MHz or 242-tone RU through which the ELR PPDU is transmitted. The UL FEC coding type subfield may include information about BCC (Binary Convolutional Code) or LDPC (Low-Density Parity Check) coding. The UL UHR-MCS subfield may include information about UHR-MCS 0 or UHR-MCS 1 used when transmitting the ELR PPDU. The PS160 subfield may include information about a 160MHz channel in which a 20MHz or 242-tone RU through which the ELR PPDU is transmitted exists.

[0345] For example, the SS allocation subfield may include a Starting Spatial Stream subfield and a Number of Spatial Streams subfield. However, if the number of spatial streams used to transmit the ELR PPDU is fixed to one, there is no need to transmit information about the number of spatial streams, so the Number of Spatial Streams subfield may be reserved.

[0346] As another example, the SS allocation subfield may include a Starting Spatial Stream subfield, a Number of Spatial Streams subfield, and indication information for transmission of the ELR PPDU. Similarly, if the number of spatial streams used for transmitting the ELR PPDU is fixed to one, the Number of Spatial Streams subfield may be set to 1 bit or reserved. The indication information for transmission of the ELR PPDU may be set to 1 bit. Since the Number of Spatial Streams subfield is changed from the existing 2 bits to 1 bit, the remaining 1 bit may be used as indication information for transmission of the ELR PPDU.

[0347] As another example, the indication information for transmission of the ELR PPDU may be indicated through the RU allocation subfield of the user information field.

[0348] A specific example of requesting transmission of ELR PPDUs from multiple non-AP STAs through the above trigger frame is as follows.

[0349] Based on the trigger frame being transmitted in an 80 MHz band and the plurality of receiving STAs including first to fourth receiving STAs, the user information field may include first user information for the first receiving STA, second user information for the second receiving STA, third user information for the third receiving STA, and fourth user information for the fourth receiving STA.

[0350] The RU allocation subfield included in the first user information may include information about a first RU through which the first receiving STA transmits the ELR PPDU. The RU allocation subfield included in the second user information may include information about a second RU through which the second receiving STA transmits the ELR PPDU. The RU allocation subfield included in the third user information may include information about a third RU through which the third receiving STA transmits the ELR PPDU. The RU allocation subfield included in the fourth user information may include information about a fourth RU through which the fourth receiving STA transmits the ELR PPDU.

[0351] The information about the first to fourth RUs may be information about the index of a 20MHz or 242-tone RU through which the ELR PPDU is transmitted. For example, the information about the first RU may indicate the first 20MHz or first 242-tone RU in the 80MHz band. The information about the second RU may indicate the second 20MHz or second 242-tone RU in the 80MHz band. The information about the third RU may indicate the third 20MHz or third 242-tone RU in the 80MHz band. The information about the fourth RU may indicate the fourth 20MHz or fourth 242-tone RU in the 80MHz band.

[0352] That is, the RU allocation subfield of the user information field only indicates the index of the 20MHz or 242-tone RU allocated to each receiving STA for transmitting the ELR PPDU, and the RU actually used for transmitting the ELR PPDU is preset as follows. Specifically, each of the first to fourth RUs may be a resource unit in which a 52-tone RU is replicated four times in the frequency domain or a resource unit in which a 106-tone RU is replicated twice in the frequency domain.

[0353] That is, the present embodiment proposes a method for requesting ELR PPDU transmission of a plurality of non-AP STAs based on a user information field of a trigger frame (i.e., a request per user). Specifically, the user information field may be defined by adding instruction information for transmission of the ELR PPDU, or the AID12 subfield, the RU allocation subfield, the UL FEC coding type subfield, the UL UHR-MCS subfield, the SS allocation subfield, the PS160 subfield, etc. included in the user information field may be changed to request ELR PPDU transmission of the plurality of non-AP STAs. Accordingly, since the AP already knows the information included in the legacy preamble of the ELR PPDU transmitted by the plurality of non-AP STAs (because the AP requested it through the trigger frame), the performance of the L-SIG of the legacy preamble does not act as a bottleneck or obstacle compared to the performance of the data. In addition, by transmitting ELR PPDUs to multiple non-AP STAs in the uplink, there is also an effect of improving signal transmission and reception performance for multiple non-AP STAs located at a long range.

[0354] Additionally, the present embodiment proposes a method for requesting ELR PPDU transmission of multiple non-AP STAs based on a common information field or a special user information field (i.e., request for all users) of a trigger frame.

[0355] The trigger frame may further include the common information field and the special user information field.

[0356] For example, the common information field may include indication information for transmission of the ELR PPDU. In this case, the indication information for transmission of the ELR PPDU may be defined based on one of bits B22, B26, B53, and B63 of the common information field (bits reserved in the UHR variant common information field).

[0357] As another example, the special user information field may include indication information for transmission of the ELR PPDU. At this time, the indication information for transmission of the ELR PPDU may be defined based on one of bits B37, B38, and B39 of the special user information field (reserved bits in the special user information field). At this time, the PHY Version Identifier subfield of the special user information field may be set to 1 or a value greater than 0.

[0358] Even when requesting ELR PPDU transmission of multiple non-AP STAs based on the common information field or the special user information field, the RU allocation subfield of the user information field may equally include allocation information for the 20MHz or 242-tone RU through which the ELR PPDU is transmitted (i.e., information about the index of the 20MHz or 242-tone RU through which the ELR PPDU is transmitted).

[0359] The above ELR PPDU may include an L-STF (Legacy-Short Training Field), an L-LTF (Legacy-Long Training Field), an L-SIG (Legacy-Signal) field, an RL-SIG (Repeated L-SIG) field, a U-SIG (Universal-Signal) field, an ELR-MARK field, an UHR-STF (Ultra High Reliability-STF), an UHR-LTF, an ELR-SIG field, and a data field.

[0360] The above ELR PPDU may be defined only for a single spatial stream and UHR-MCS (Modulation and Coding Scheme) 0 and 1, with a bandwidth of 20 MHz. The ELR-SIG field and the data field may be transmitted through a resource unit in which a 52-tone Regular Resource Unit (RRU) is replicated four times in the frequency domain at the 20 MHz (or a resource unit in which a 106-tone RRU is replicated twice in the frequency domain).

[0361] FIG. 31 is a flowchart illustrating a procedure for a receiving STA to transmit an ELR PPDU based on a trigger frame according to the present embodiment.

[0362] An example of FIG. 31 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 on the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0363] An example of FIG. 31 is performed at a receiving STA, which may correspond to at least one STA (station) or non-AP MLD (non-access point Multi-link Device). The transmitting STA of FIG. 31 may correspond to an AP (access point) or AP MLD.

[0364] The present embodiment proposes a method for configuring a trigger frame for soliciting ELR PPDU transmission from a plurality of non-AP STAs. Specifically, the present embodiment proposes a method for requesting ELR PPDU transmission for all non-AP STAs based on a common information field or a special user information field of the trigger frame, or for requesting ELR PPDU transmission for a specific non-AP STA based on a user information field of the trigger frame. Accordingly, since the AP already knows information included in the legacy preamble of the ELR PPDU transmitted by the plurality of non-AP STAs (because the AP requested it through the trigger frame), the performance of the L-SIG of the legacy preamble does not act as a bottleneck or obstacle compared to the performance of the data.

[0365] In step S3110, multiple receiving STAs (stations) receive a trigger frame from a transmitting STA.

[0366] In step S3120, the plurality of receiving STAs transmit an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) to the transmitting STA based on the trigger frame.

[0367] The above trigger frame includes a user information field. The user information field includes instruction information for transmission of the ELR PPDU.

[0368] Specifically, the user information field may further include at least one of an AID12 subfield, a RU (Resource Unit) allocation subfield, a UL (uplink) FEC (Forward Error Correction) coding type subfield, a UL UHR-MCS (Ultra High Reliability-Modulation and Coding Scheme) subfield, an SS (Spatial Stream) allocation subfield, a PS160 subfield, and a Trigger Dependent User Info subfield.

[0369] The AID12 subfield may include an AID (Association IDentifier) ​​of a receiving STA transmitting the ELR PPDU. The RU allocation subfield may include allocation information for a 20MHz or 242-tone RU through which the ELR PPDU is transmitted. The UL FEC coding type subfield may include information about BCC (Binary Convolutional Code) or LDPC (Low-Density Parity Check) coding. The UL UHR-MCS subfield may include information about UHR-MCS 0 or UHR-MCS 1 used when transmitting the ELR PPDU. The PS160 subfield may include information about a 160MHz channel in which a 20MHz or 242-tone RU through which the ELR PPDU is transmitted exists.

[0370] For example, the SS allocation subfield may include a Starting Spatial Stream subfield and a Number of Spatial Streams subfield. However, if the number of spatial streams used to transmit the ELR PPDU is fixed to one, there is no need to transmit information about the number of spatial streams, so the Number of Spatial Streams subfield may be reserved.

[0371] As another example, the SS allocation subfield may include a Starting Spatial Stream subfield, a Number of Spatial Streams subfield, and indication information for transmission of the ELR PPDU. Similarly, if the number of spatial streams used for transmitting the ELR PPDU is fixed to one, the Number of Spatial Streams subfield may be set to 1 bit or reserved. The indication information for transmission of the ELR PPDU may be set to 1 bit. Since the Number of Spatial Streams subfield is changed from the existing 2 bits to 1 bit, the remaining 1 bit may be used as indication information for transmission of the ELR PPDU.

[0372] As another example, the indication information for transmission of the ELR PPDU may be indicated through the RU allocation subfield of the user information field.

[0373] A specific example of requesting transmission of ELR PPDUs from multiple non-AP STAs through the above trigger frame is as follows.

[0374] Based on the trigger frame being transmitted in an 80 MHz band and the plurality of receiving STAs including first to fourth receiving STAs, the user information field may include first user information for the first receiving STA, second user information for the second receiving STA, third user information for the third receiving STA, and fourth user information for the fourth receiving STA.

[0375] The RU allocation subfield included in the first user information may include information about a first RU through which the first receiving STA transmits the ELR PPDU. The RU allocation subfield included in the second user information may include information about a second RU through which the second receiving STA transmits the ELR PPDU. The RU allocation subfield included in the third user information may include information about a third RU through which the third receiving STA transmits the ELR PPDU. The RU allocation subfield included in the fourth user information may include information about a fourth RU through which the fourth receiving STA transmits the ELR PPDU.

[0376] The information about the first to fourth RUs may be information about the index of a 20MHz or 242-tone RU through which the ELR PPDU is transmitted. For example, the information about the first RU may indicate the first 20MHz or first 242-tone RU in the 80MHz band. The information about the second RU may indicate the second 20MHz or second 242-tone RU in the 80MHz band. The information about the third RU may indicate the third 20MHz or third 242-tone RU in the 80MHz band. The information about the fourth RU may indicate the fourth 20MHz or fourth 242-tone RU in the 80MHz band.

[0377] That is, the RU allocation subfield of the user information field only indicates the index of the 20MHz or 242-tone RU allocated to each receiving STA for transmitting the ELR PPDU, and the RU actually used for transmitting the ELR PPDU is preset as follows. Specifically, each of the first to fourth RUs may be a resource unit in which a 52-tone RU is replicated four times in the frequency domain or a resource unit in which a 106-tone RU is replicated twice in the frequency domain.

[0378] That is, the present embodiment proposes a method for requesting ELR PPDU transmission of a plurality of non-AP STAs based on a user information field of a trigger frame (i.e., a request per user). Specifically, the user information field may be defined by adding instruction information for transmission of the ELR PPDU, or the AID12 subfield, the RU allocation subfield, the UL FEC coding type subfield, the UL UHR-MCS subfield, the SS allocation subfield, the PS160 subfield, etc. included in the user information field may be changed to request ELR PPDU transmission of the plurality of non-AP STAs. Accordingly, since the AP already knows the information included in the legacy preamble of the ELR PPDU transmitted by the plurality of non-AP STAs (because the AP requested it through the trigger frame), the performance of the L-SIG of the legacy preamble does not act as a bottleneck or obstacle compared to the performance of the data. In addition, by transmitting ELR PPDUs to multiple non-AP STAs in the uplink, there is also an effect of improving signal transmission and reception performance for multiple non-AP STAs located at a long range.

[0379] Additionally, the present embodiment proposes a method for requesting ELR PPDU transmission of multiple non-AP STAs based on a common information field or a special user information field (i.e., request for all users) of a trigger frame.

[0380] The trigger frame may further include the common information field and the special user information field.

[0381] For example, the common information field may include indication information for transmission of the ELR PPDU. In this case, the indication information for transmission of the ELR PPDU may be defined based on one of bits B22, B26, B53, and B63 of the common information field (bits reserved in the UHR variant common information field).

[0382] As another example, the special user information field may include indication information for transmission of the ELR PPDU. At this time, the indication information for transmission of the ELR PPDU may be defined based on one of bits B37, B38, and B39 of the special user information field (reserved bits in the special user information field). At this time, the PHY Version Identifier subfield of the special user information field may be set to 1 or a value greater than 0.

[0383] Even when requesting ELR PPDU transmission of multiple non-AP STAs based on the common information field or the special user information field, the RU allocation subfield of the user information field may equally include allocation information for the 20MHz or 242-tone RU through which the ELR PPDU is transmitted (i.e., information about the index of the 20MHz or 242-tone RU through which the ELR PPDU is transmitted).

[0384] The above ELR PPDU may include an L-STF (Legacy-Short Training Field), an L-LTF (Legacy-Long Training Field), an L-SIG (Legacy-Signal) field, an RL-SIG (Repeated L-SIG) field, a U-SIG (Universal-Signal) field, an ELR-MARK field, an UHR-STF (Ultra High Reliability-STF), an UHR-LTF, an ELR-SIG field, and a data field.

[0385] The above ELR PPDU may be defined only for a single spatial stream and UHR-MCS (Modulation and Coding Scheme) 0 and 1, with a bandwidth of 20 MHz. The ELR-SIG field and the data field may be transmitted through a resource unit in which a 52-tone Regular Resource Unit (RRU) is replicated four times in the frequency domain at the 20 MHz (or a resource unit in which a 106-tone RRU is replicated twice in the frequency domain).

[0386] <Device Configuration>

[0387] The technical features of the present specification described above can be applied to various devices and methods. For example, the technical features of the present specification described above can be performed / supported by the devices of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above can be applied only to a part of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above can 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 (610) and memory (620) of FIG. 14. For example, the device of the present specification receives a trigger frame from a transmitting STA (station); and transmits an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) to the transmitting STA based on the trigger frame.

[0388] The technical features of this specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable recording medium containing instructions that are executed by at least one processor.

[0389] The CRM may store instructions for performing operations including: receiving a trigger frame from a transmitting STA (station); and transmitting an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame to the transmitting STA. The instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to the CRM of the present specification may be the processor (111, 121) or the processing chip (114, 124) of FIG. 1, or the processor (610) of FIG. 14. Meanwhile, the CRM of the present specification may be the memory (112, 122) of FIG. 1, the memory (620) of FIG. 14, or a separate external memory / storage medium / disk, etc.

[0390] The technical features of this specification described above are applicable to various applications and business models. For example, the technical features described above can be applied to wireless communication in devices that support artificial intelligence (AI).

[0391] Artificial intelligence (AI) is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0392] An artificial neural network (ANN) is a model used in machine learning. It can refer to a model with problem-solving capabilities, consisting of artificial neurons (nodes) formed by the connection of synapses to form a network. An ANN can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.

[0393] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network may include synapses connecting neurons. In an artificial neural network, each neuron can output a function value of an activation function based on input signals, weights, and biases received through the synapses.

[0394] Model parameters are parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters are parameters that must be set before learning in machine learning algorithms, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0395] The goal of artificial neural network training can be seen as determining model parameters that minimize a loss function. The loss function can be used as an indicator for determining optimal model parameters during the artificial neural network training process.

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

[0397] Supervised learning refers to a method for training an artificial neural network when given labels for the training data. The labels can refer to the correct answer (or output value) that the artificial neural network must infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method for training an artificial neural network when the training data is not given labels. Reinforcement learning can refer to a learning method in which an agent defined within a given environment is trained to select actions or action sequences that maximize the cumulative reward in each state.

[0398] Machine learning implemented with a deep neural network (DNN) containing multiple hidden layers among artificial neural networks is also called deep learning, and deep learning is a subset of machine learning. Hereinafter, the term "machine learning" is used to encompass deep learning.

[0399] Additionally, the above-described technical features can be applied to wireless communication of robots.

[0400] A robot can be defined as a machine that automatically performs or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making independent judgments, and performing actions can be called an intelligent robot.

[0401] Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with actuators or motors, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots incorporate wheels, brakes, and propellers into their actuators, enabling them to move on the ground or fly in the air.

[0402] Additionally, the above-described technical features can be applied to devices that support extended reality.

[0403] Extended reality is a general term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology presents real-world objects and backgrounds as CG images only, AR technology presents virtual CG images over images of real objects, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.

[0404] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.

[0405] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

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

Claims

1. In a wireless LAN system, A step in which a plurality of receiving STAs (stations) receive a trigger frame from a transmitting STA; and The step of the plurality of receiving STAs further comprising transmitting an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame to the transmitting STA, The above trigger frame includes a user information field, and The above user information field contains instruction information for transmission of the ELR PPDU. method.

2. In paragraph 1, The above user information field further includes at least one of an AID12 subfield, a RU (Resource Unit) allocation subfield, an UL (uplink) FEC (Forward Error Correction) coding type subfield, a UL UHR-MCS (Ultra High Reliability-Modulation and Coding Scheme) subfield, an SS (Spatial Stream) allocation subfield, a PS160 subfield, and a Trigger Dependent User Info subfield. The above AID12 subfield includes the AID (Association IDentifier) ​​of the receiving STA transmitting the ELR PPDU, The RU allocation subfield includes allocation information for the 20MHz or 242-tone RU on which the ELR PPDU is transmitted, The above UL FEC coding type subfield contains information about BCC (Binary Convolutional Code) or LDPC (Low-Density Parity Check) coding, The above UL UHR-MCS subfield contains information about UHR-MCS 0 or UHR-MCS 1 used when transmitting the ELR PPDU, The PS160 subfield contains information about the 160MHz channel on which the ELR PPDU is transmitted or on which the 20MHz or 242-tone RU exists. method.

3. In paragraph 2, The SS allocation subfield includes a Starting Spatial Stream subfield, a Number of Spatial Streams subfield, and indication information for transmission of the ELR PPDU. The number subfield of the above spatial stream is set to 1 bit or reserved, The instruction information for transmission of the above ELR PPDU is set to 1 bit. method.

4. In paragraph 2, The indication information for transmission of the above ELR PPDU is indicated through the RU allocation subfield of the above user information field. method.

5. In paragraph 2, Based on the above trigger frame being transmitted in the 80 MHz band and the plurality of receiving STAs including the first to fourth receiving STAs, The user information field includes first user information for the first receiving STA, second user information for the second receiving STA, third user information for the third receiving STA, and fourth user information for the fourth receiving STA, The RU allocation subfield included in the first user information includes information about the first RU to which the first receiving STA transmits the ELR PPDU, The RU allocation subfield included in the second user information includes information about the second RU to which the second receiving STA transmits the ELR PPDU, The RU allocation subfield included in the third user information includes information about the third RU to which the third receiving STA transmits the ELR PPDU, The RU allocation subfield included in the fourth user information includes information about the fourth RU to which the fourth receiving STA transmits the ELR PPDU, The information about the first to fourth RUs is information about the index of the 20MHz or 242-tone RU through which the ELR PPDU is transmitted, Each of the first to fourth RUs above is a resource unit in which a 52-tone RU is replicated four times in the frequency domain or a 106-tone RU is replicated twice in the frequency domain. method.

6. In paragraph 1, The above ELR PPDU includes an L-STF (Legacy-Short Training Field), an L-LTF (Legacy-Long Training Field), an L-SIG (Legacy-Signal) field, an RL-SIG (Repeated L-SIG) field, a U-SIG (Universal-Signal) field, an ELR-MARK field, an UHR-STF (Ultra High Reliability-STF), an UHR-LTF, an ELR-SIG field, and a data field. The above ELR PPDU has a bandwidth of 20MHz and is defined only for a single spatial stream and UHR-MCS (Modulation and Coding Scheme) 0 and 1. method.

7. In a wireless LAN system, multiple receiving STAs (stations) memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Receive a trigger frame from a transmitting STA; and Transmit an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame to the transmitting STA. The above trigger frame includes a user information field, and The above user information field contains instruction information for transmission of the ELR PPDU. Multiple receiving STAs.

8. In a wireless LAN system, A step in which a transmitting STA (station) transmits a trigger frame to multiple receiving STAs; and The transmitting STA comprises a step of receiving an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame from the plurality of receiving STAs, The above trigger frame includes a user information field, and The above user information field contains instruction information for transmission of the ELR PPDU. method.

9. In paragraph 8, The above user information field further includes at least one of an AID12 subfield, a RU (Resource Unit) allocation subfield, an UL (uplink) FEC (Forward Error Correction) coding type subfield, a UL UHR-MCS (Ultra High Reliability-Modulation and Coding Scheme) subfield, an SS (Spatial Stream) allocation subfield, a PS160 subfield, and a Trigger Dependent User Info subfield. The above AID12 subfield includes the AID (Association IDentifier) ​​of the receiving STA transmitting the ELR PPDU, The RU allocation subfield includes allocation information for the 20MHz or 242-tone RU on which the ELR PPDU is transmitted, The above UL FEC coding type subfield contains information about BCC (Binary Convolutional Code) or LDPC (Low-Density Parity Check) coding, The above UL UHR-MCS subfield contains information about UHR-MCS 0 or UHR-MCS 1 used when transmitting the ELR PPDU, The PS160 subfield contains information about the 160MHz channel on which the ELR PPDU is transmitted or on which the 20MHz or 242-tone RU exists. method.

10. In paragraph 9, The SS allocation subfield includes a Starting Spatial Stream subfield, a Number of Spatial Streams subfield, and indication information for transmission of the ELR PPDU. The number subfield of the above spatial stream is set to 1 bit or reserved, The instruction information for transmission of the above ELR PPDU is set to 1 bit. method.

11. In paragraph 9, The indication information for transmission of the above ELR PPDU is indicated through the RU allocation subfield of the above user information field. method.

12. In paragraph 9, Based on the above trigger frame being transmitted in the 80 MHz band and the plurality of receiving STAs including the first to fourth receiving STAs, The user information field includes first user information for the first receiving STA, second user information for the second receiving STA, third user information for the third receiving STA, and fourth user information for the fourth receiving STA, The RU allocation subfield included in the first user information includes information about the first RU to which the first receiving STA transmits the ELR PPDU, The RU allocation subfield included in the second user information includes information about the second RU to which the second receiving STA transmits the ELR PPDU, The RU allocation subfield included in the third user information includes information about the third RU to which the third receiving STA transmits the ELR PPDU, The RU allocation subfield included in the fourth user information includes information about the fourth RU to which the fourth receiving STA transmits the ELR PPDU, The information about the first to fourth RUs is information about the index of the 20MHz or 242-tone RU through which the ELR PPDU is transmitted, Each of the first to fourth RUs above is a resource unit in which a 52-tone RU is replicated four times in the frequency domain or a 106-tone RU is replicated twice in the frequency domain. method.

13. In paragraph 8, The above ELR PPDU includes an L-STF (Legacy-Short Training Field), an L-LTF (Legacy-Long Training Field), an L-SIG (Legacy-Signal) field, an RL-SIG (Repeated L-SIG) field, a U-SIG (Universal-Signal) field, an ELR-MARK field, an UHR-STF (Ultra High Reliability-STF), an UHR-LTF, an ELR-SIG field, and a data field. The above ELR PPDU has a bandwidth of 20MHz and is defined only for a single spatial stream and UHR-MCS (Modulation and Coding Scheme) 0 and 1. method.

14. In a wireless LAN system, a transmitting STA (station) memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Transmitting a trigger frame to multiple receiving STAs; and Receive an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame from the plurality of receiving STAs, The above trigger frame includes a user information field, and The above user information field contains instruction information for transmission of the ELR PPDU. Transmitting STA.

15. At least one computer-readable medium containing instructions based on being executed by at least one processor, A step of receiving a trigger frame from a transmitting STA (station); and Further comprising a step of transmitting an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame to the transmitting STA, The above trigger frame includes a user information field, and The above user information field contains instruction information for transmission of the ELR PPDU. Recording medium.

16. In a wireless LAN system, in the device, memory; and A processor operatively coupled to the memory, the processor comprising: Receive a trigger frame from a transmitting STA (station); and Transmit an ELR (Enhanced Long Range) PPDU (Physical Protocol Data Unit) based on the trigger frame to the transmitting STA. The above trigger frame includes a user information field, and The above user information field contains instruction information for transmission of the ELR PPDU. device.

Images