Frame format of response signal to trigger frame

Abstract

The present disclosure relates to a method and apparatus for supporting enhanced long range (ELR) transmission in a wireless LAN system. A station (STA) according to the present disclosure may: receive a multi-user request to send (MU-RTS) trigger frame; and on the basis of an information field included in the frame, transmit a clear to send (CTS) frame in an ELR PPDU format. The MU-RTS trigger frame may comprise PPDU format information of the CTS frame and modulation and coding scheme (MCS) information corresponding to an ELR PPDU. This enables the STA to mitigate CTS reception instability due to a difference in transmit power between downlink (DL) and uplink (UL). In addition, a plurality of STAs may reduce the possibility of collisions in a multi-user environment and reduce transmission delay by simultaneously transmitting ELR PPDU-based CTS frames. Therefore, the present technology improves the reliability and protection efficiency of RTS / CTS procedures and provides stable communication quality even in a high-density network environment.

Description

Frame format of the response signal to the trigger frame

[0001] This specification relates to wireless LAN systems, and more specifically, to operations and devices related to the format of a response signal for a trigger frame in a wireless LAN system.

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

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

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

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

[0006] In order to efficiently perform communication procedures between multiple stations (STAs) in a wireless LAN system, the exchange of Request To Send (RTS) and Clear To Send (CTS) signals to avoid collisions in transmission channels must be performed reliably. However, in conventional technology, due to the difference in transmission power (TX power) between the downlink (DL) and uplink (UL) sections, a problem could arise where a STA that transmitted an RTS frame could not reliably receive the corresponding CTS frame. This problem can lead to signal collisions and failures in protection procedures, particularly in a Multi-User (MU) environment where multiple STAs exist, thereby causing a decrease in overall communication efficiency and reliability.

[0007] Accordingly, to improve the instability of the RTS / CTS procedure caused by the aforementioned transmission and reception power difference, a new physical layer structure is required that can transmit CTS frames with higher reception reliability. In particular, for next-generation high-efficiency transmission technology, it may be necessary to provide technical means to ensure the robustness of CTS frame transmission by utilizing an Extended Long Range (ELR) PPDU capable of applying an extended signal configuration.

[0008] Accordingly, the present specification aims to provide a technology that enables the transmission of CTS frames using ELR PPDUs to multiple STAs by defining MU-RTS trigger frames. Through this, each STA can transmit an ELR PPDU-based CTS response at the same timing, thereby ensuring both signal protection performance and link stability in a multi-user environment.

[0009] One of the various technical objectives of this specification is to improve the reliability of RTS and CTS signal transmission and reception and to reduce the error probability during the protection frame transmission process, thereby improving the efficiency and performance of the overall wireless signal transmission and reception procedure.

[0010] One of the various examples of this specification may relate to a method and / or device for supporting Enhanced Long Range (ELR) transmission in a WLAN system. For example, the ELR transmission may be solicited by a Multi-User Request to Send (MU-RTS) trigger frame.

[0011] For example, the STA of this specification may receive a MU-RTS (multi-user request to send) trigger frame. For example, the MU-RTS trigger frame may include a first information field and a second information field. For example, the first information field may include information regarding the PPDU (physical protocol data unit) format of a CTS (clear to send) frame that is a response to the MU-RTS trigger frame. For example, the PPDU format of the CTS frame may include an ELR (enhanced long range) PPDU format. For example, the second information field may include MCS (modulation and coding scheme) information related to the ELR PPDU format. For example, the first information field may be a special user info field, and the second information field may be a user info field.

[0012] For example, the STA of the present specification can transmit the CTS frame based on the MU-RTS trigger frame.

[0013] According to the technology of the present specification, by transmitting CTS frames using an Extended Long Range (ELR) PPDU during the transmission and reception process of RTS and CTS signals, reception instability caused by the difference in transmission power between the downlink (DL) and the uplink (UL) can be effectively mitigated. Accordingly, the success rate of receiving CTS responses is improved, and the error rate in link initial setup and data transmission procedures can be reduced.

[0014] In addition, by using the MU-RTS trigger frame defined in this specification, a procedure can be efficiently performed in which multiple STAs simultaneously transmit ELR PPDU-based CTS frames. This can contribute to increasing the channel utilization efficiency of the entire network by minimizing transmission delay in a multi-user environment and reducing the possibility of collisions between each STA.

[0015] Furthermore, this technology enables RTS / CTS-based protection procedures to be performed more robustly, thereby reducing interference and packet loss during frame transmission and maintaining stable communication quality even in high-density network environments.

[0016] Accordingly, the ELR PPDU-based CTS frame transmission technology according to the present specification provides the effect of improving signal transmission and reception reliability, protection procedure efficiency, and overall transmission performance throughout the wireless LAN system.

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

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

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

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

[0021] FIG. 5 illustrates a PPDU transmitted / received in an STA of the present specification.

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

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

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

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

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

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

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

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

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

[0031] FIG. 15 shows an example of an ELR PPDU of the present specification.

[0032] FIG. 16 is an example of a User Info field format including the sub-fields described above.

[0033] FIG. 17 shows an example of a special user info format according to the present specification.

[0034] FIG. 18 shows an example of a user info format according to the present specification.

[0035] FIG. 19 shows an example of a user info format according to the present specification.

[0036] FIG. 20 illustrates an example in which a MU-RTS frame and a CTS frame are exchanged according to the present specification.

[0037] FIG. 21 is a flowchart of the procedure according to the present specification.

[0038] FIG. 22 is another example of a procedure flowchart according to the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0118] Additionally or generally, 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 (e.g., 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 (e.g., information regarding preamble puncturing patterns).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0132] TB PPDUs (941, 942) are transmitted at the same time and may be transmitted from multiple STAs (e.g., User STAs) with an AID indicated within a Trigger frame (930). An ACK frame (950) for a TB PPDU may be implemented in various forms. For example, an ACK frame (950) for a TB PPDU may be implemented in the form of a BA (block ACK).

[0133] In FIG. 9, the transmission(s) of the Trigger Frame (930), TB PPDU (941, 942) and / or ACK Frame (950) can be performed within TXOP (925).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] Referring to FIG. 14, a power management module (611) manages power for 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 associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.

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

[0160] ELR PPDU

[0161] This specification proposes various technical features related to the transmission of ELR (extended long range or enhanced long range) PPDUs. The ELR PPDU may be changed to various names. For example, the ELR PPDU may be referred to by various names such as the first, second, TX, RX, ER (extended range), and UHR PPDU. The technical features of this specification are not limited to the name ELR PPDU.

[0162] FIG. 15 illustrates an example of an ELR PPDU of the present specification. As illustrated, the ELR PPDU may include L-STF (1505), L-LTF (1510), L-SIG (1515), RL-SIG (1520), U-SIG (1525), ELR-MARK (1530), UHR-STF (1535), UHR-LTF (1540), ELR-SIG (1545), and Data (1550). For example, some fields of FIG. 15 may be omitted. For example, the order of some fields of FIG. 15 may be changed. Each field disclosed in FIG. 15 may be referred to by various names such as signal / bit.

[0163] For example, the value of the number of spatial streams (e.g., Nss) for an ELR PPDU may be limited to 1. Additionally or generally, for example, an ELR PPDU has a fixed bandwidth of 20 MHz and can be used for both downlink and uplink in 2.4 GHz band operation, but only for uplink in 5 GHz and 6 GHz band operation. In other words, an ELR PPDU may consist only of 20 MHz and may not have bandwidths such as 40 / 80 / 160 / 320 MHz.

[0164] For example, the above L-SIG (1515) and / or RL-SIG (1520) may be identical to the L-SIG and RL-SIG described in FIG. 5. For example, the technical features of the L-SIG and RL-SIG described with respect to FIG. 5 may be equally applicable to the above L-SIG (1515) and / or RL-SIG (1520).

[0165] For example, the ELR-MARK (1530) of FIG. 15 may be composed of two OFDM symbols. The ELR-MARK (1530) may include information regarding an identifier (e.g., BSS_COLOR) indicating the BSS color to which the STA transmitting the corresponding PPDU belongs.

[0166] For example, an example of this specification may relate to improvements to at least one of the fields of FIG. 15: U-SIG (1525), UHR-LTF (1540), ELR-SIG (1545), and Data (1550). Accordingly, further description of the remaining fields / signals, excluding the four fields / signals (1525, 1540, 1545, 1550), may be omitted below.

[0167] For example, the U-SIG (1525) may have the following features. For example, the U-SIG (1525) of this specification may be composed of a signal / field for an ELR PPDU. For example, a PPDU that is not an ELR PPDU (e.g., UHR MU PPDU or UHR TB PPDU) may also include the U-SIG, but the contents of the U-SIG (1525) of this specification may include different contents.

[0168] For example, the U-SIG (1525) of this specification has a length of 2 symbols, and each symbol may be represented as U-SIG-1 and U-SIG-2. For example, bits B0 to B2 of U-SIG-1 may have various names such as the first information or PHY Version Identifier described above, and may include a value (e.g., a value of 1) that identifies that the PHY version of the PPDU is UHR. For example, the positions of bits B0 to B2 may be changed.

[0169] Additionally or generally, bits B3 through B5 of U-SIG-1 may have various names such as the second information or BW information, and may include information regarding the bandwidth of the ELR PPDU. For example, bits B3 through B5 of U-SIG-1 may have only a value of 0. This is because it is desirable for the bandwidth of the ELR PPDU to be fixed at 20 MHz. For example, the positions of bits B3 through B5 may be changed.

[0170] Additionally or generally, the B6 bit of U-SIG-1 may contain information regarding whether the PPDU is transmitted to UL or DL. For example, the position of the B6 bit may be changed.

[0171] Additionally or generally, bits B7 through B12 of U-SIG-1 may represent the ID of the Basic Service Set (BSS). For example, bits B7 through B12 may include ID information (or BSS color information) of the BSS to which the STA transmitting / receiving the PPDU belongs. For example, the positions of bits B7 through B12 may be changed.

[0172] Additionally or generally, bits B13 through B19 of U-SIG-1 may contain information related to the duration of a TXOP (transmission opportunity). For example, the positions of bits B13 through B19 may be changed.

[0173] Additionally or generally, bits B20 through B24 of U-SIG-1 may all be set to 1, and the bits may be called disregard. For example, the positions of bits B20 through B24 may be changed.

[0174] Additionally or generally, the B25 bit of U-SIG-1 may be set to 1, and the bit may be called Validate. For example, the position of the B25 bit may be changed.

[0175] Additionally or generally, bits B0 to B1 of U-SIG-2 may have various names such as the third information or PPDU Type and Compression Mode. Bits B0 to B1 may always have a value of 3 regardless of whether the associated PPDU is a DL PPDU or a UL PPDU, thereby indicating / identifying that the PPDU is an ELR PPDU. For example, the positions of bits B0 to B1 may be changed.

[0176] Additionally or generally, bits B2 through B12 of U-SIG-2 may be composed of a STA ID. For example, bits B2 through B12 may be composed of some 11 bits (e.g., LSB 11 bits or MSB 11 bits) of the Association ID (AID) of the STA transmitting the PPDU. For example, the positions of bits B2 through B12 may be changed.

[0177] Additionally or generally, bits B13 through B15 of U-SIG-2 may be configured as ELR validate. These three bits may be used to identify the ELR PPDU, and these three bits may all be set to 1 (i.e., these three bits have a value of 7). For example, the positions of bits B13 through B15 may be changed.

[0178] Additionally or generally, bits B16 through B19 of U-SIG-2 may be composed of a CRC.

[0179] Additionally or generally, bits B20 through B25 of U-SIG-2 may be configured as a tail, so that all bits are zero.

[0180] For example, the UHR-LTF (1540) may have the following features. The UHR-LTF (1540) may be divided into a signal for ELR communication and a signal for non-ELR communication. For example, the UHR-LTF for ELR communication may be composed of 4x LTF as described above. For example, the UHR-LTF (1540) may be composed based on a sequence in which the first LTF sequence is duplicated 4 times in the frequency domain in 52-tone RU units. For example, the first LTF sequence may have a length of 52. For example, the non-zero elements of the first LTF sequence may be a total of 52.

[0181] Additionally or generally, the UHR-LTF for the ELR communication may be constructed based on a 2x LTF sequence. The 2x LTF sequence may be defined in the range from index -122 to index +122.

[0182] For example, the ELR-SIG (1545) may have the following features. For example, the ELR-SIG (1545) of this specification may have two parts. Each part may be denoted as ELR-SIG-1 and ELR-SIG-2. For example, the B0 bit of ELR-SIG-1 may contain the first ER / ELR-SIG information or ELR Version Identifier described above. For example, the B0 bit of ELR-SIG-1 may contain information for identifying the ELR version, and the ELR Version Identifier included in the ELR PPDU having the technical features described in this specification may have a value of 0. For example, the position of the B0 bit may be changed.

[0183] Additionally or generally, the B1 bit of ELR-SIG-1 may contain a UL / DL field. For example, the bit may contain information regarding whether the ELR PPDU is transmitted as UL / DL. For example, the position of B1 may be changed.

[0184] Additionally or generally, the B2 bit of ELR-SIG-1 may contain an MCS field. For example, the bit may contain information related to MCS information applied to the data field of the ELR PPDU. For example, if the bit is set to a first value (e.g., 0), the bit may indicate that BPSK with a coding rate of 1 / 2 is applied to the data field of the ELR PPDU. For example, if the bit is set to a second value (e.g., 1), the bit may indicate that QPSK with a coding rate of 1 / 2 is applied to the data field of the ELR PPDU. For example, the position of B2 may be changed.

[0185] Additionally or generally, the B3 bit of ELR-SIG-1 may contain a coding (type) field. For example, the bit may contain information related to coding (type) information applied to the data field of the ELR PPDU. For example, if the bit is set to a first value (e.g., 0), the bit may indicate that the BCC technique is applied to the data field of the ELR PPDU. For example, if the bit is set to a second value (e.g., 1), the bit may indicate that the LDPC technique (e.g., LDPC having a word length of 648, 1296, or 1944) is applied to the data field of the ELR PPDU.

[0186] Additionally or generally, bits B4 through B12 of ELR-SIG-1 may contain a length field. For example, the length field may have a length of 9 bits, and the specific bit position may change. For example, the field may contain information regarding the number of symbols in the data field included in the ELR PPDU.

[0187] Additionally or generally, the B13 bit of ELR-SIG-1 may contain information regarding the presence of LDPC extra (OFDM) symbols. For example, such information may include information regarding whether additional OFDM symbols are required for LDPC encoding of the PPDU.

[0188] Additionally or generally, bits B14 through B17 of ELR-SIG-1 may include CRC bits, and bits B18 through B23 of ELR-SIG-1 may include tail bits and have a value of 0.

[0189] Additionally or generally, bits B0 through B10 of ELR-SIG-2 may contain information regarding the STA-ID. For example, the bits may consist of some 11 bits (e.g., LSB 11 bits or MSB 11 bits) of the AID of the STA transmitting the ELR PPDU. For example, the position of the bits may change.

[0190] Additionally or generally, bits B1 through B13 of ELR-SIG-2 may contain disregard fields / information. Each bit of the corresponding 3-bit fields / information may be set to 1.

[0191] Additionally or generally, bits B14 through B17 of ELR-SIG-2 may include CRC bits, and bits B18 through B23 of ELR-SIG-1 may include tail bits and have a value of 0.

[0192] For example, the Data (1550) field may be referred to by various names such as ER / ELR-Data, payload, etc. The Data (1550) field and ELR-SIG (1545) of this specification may be transmitted through four duplicated 52-tone RUs as described below.

[0193] For example, ELR-SIG-1 and ELR-SIG-2 included in ELR-SIG (1545) may each contain information of 24 bits in length (e.g., un-coded bits of 24 bits). BCC encoding at a 1 / 2 code rate may be applied to this information of 24 bits in length (e.g., un-coded bits of 24 bits) to generate coded bits of 48 bits in length. BPSK modulation may be applied to the coded bits to generate 48 BPSK symbols corresponding to ELR-SIG-1 and ELR-SIG-2, respectively. Four pilots are added to these 48 BPSK symbols to generate data corresponding to a total of 52 subcarriers / tones, and this data is included in a 52-tone RU. These 52-tone RUs can be transmitted through 52-tone RUs that are duplicated / repeated four times in the frequency domain (or through four duplicated 52-tone RUs).

[0194] For example, the information contained in Data (1550) can be mapped to a 52-tone RU based on BPSK or QPSK modulation. The 52-tone RU can be transmitted through a 52-tone RU that is duplicated / repeated four times in the frequency domain (or through four duplicated 52-tone RUs).

[0195] Capability Information

[0196] A STA related to this specification (e.g., AP and / or non-AP STA) may include information regarding whether it supports the transmission and / or reception of ELR PPDU in a Management frame (e.g., Beacon frame). For example, an AP may transmit information regarding support for ELR PPDU transmission / reception to non-AP STA(s) within the AP coverage / BSS via a beacon frame. Specifically, the AP's information regarding support for ELR PPDU transmission / reception is transmitted by being included in the beacon frame body and may be defined, for example, using order 95 as follows.

[0197] The above example can be modified in various ways. For example, information regarding ELR PPDU transmission / reception support may be indicated by including it in the UHR Operation Parameters field of the UHR Operation element contained in the beacon frame. For example, the information may be defined as ELR PPDU support and have a length of 1 bit. This 1-bit information may indicate whether it (e.g., AP or non-AP STA) supports ELR PPDU transmission / reception.

[0198] Additionally or generally, the above information (e.g., 1-bit information) may be included in and transmitted within the UHR PHY Capabilities Information in the UHR Capabilities element. For example, the above information may be defined as ELR PPDU support and may consist of 1 bit to indicate whether ELR PPDU (for transmission and / or reception) is supported.

[0199] For example, if information indicating whether the above-mentioned ELR PPDU is supported is included in the UHR Operation Parameters field or the UHR PHY Capabilities Information within the UHR Capabilities element, the information may be transmitted in various Management frames (e.g., probe request / response, (re)association request / response). At this time, through the frame exchange, the AP can identify non-AP STA(s) that support ELR PPDU.

[0200] In other words, the AP may transmit a first management frame to at least one non-AP STA. For example, the first management frame may be a Beacon frame, a probe request / response, a (re)association request / response, etc. The first management frame may include information regarding whether the AP supports ELR PPDU. For example, the information regarding whether the AP supports ELR PPDU may include a) a subfield regarding whether the AP supports the transmission of ELR PPDU, and / or b) a subfield regarding whether the AP supports the reception of ELR PPDU. For example, each of the subfields may have a length of 1 bit.

[0201] Additionally or generally, a non-AP STA may transmit a second management frame to the AP. For example, the second management frame may be a probe request / response, a (re)association request / response, etc. The second management frame may include information regarding whether the non-AP STA supports ELR PPDU. For example, the information regarding whether the non-AP STA supports ELR PPDU may include a) a subfield regarding whether the non-AP STA supports the transmission of ELR PPDU, and / or b) a subfield regarding whether the non-AP STA supports the reception of ELR PPDU. For example, each of the subfields may have a length of 1 bit.

[0202] For example, through the exchange of the first management frame and the second management frame, the AP and non-AP STA(s) can determine whether the transmission and reception of ELR PPDU is possible within the corresponding BSS.

[0203] MU-RTS and CTS frame exchange

[0204] A STA (e.g., AP) may perform MU-RTS and CTS frame exchanges for channel protection to ensure smooth DL transmission and reception and for NAV updates of other STAs. In this case, the AP may request a non-AP STA to transmit a CTS frame using an ELR-PPDU in order to smoothly receive a response to a MU-RTS frame transmitted by a non-AP STA located at the AP coverage boundary or in a coverage hole. Such requests for CTS frame transmission using an ELR PPDU to non-AP STAs can be performed based on various examples described below (e.g., the first / second / third example, etc.).

[0205] For example, this specification proposes a MU-RTS Trigger frame having the following technical features to transmit a CTS frame using the ELR PPDU described in FIG. 15, rather than the conventional non-HT (DUP) PPDU format.

[0206] For example, the MU-RTS Trigger frame of this specification may be a UHR variant MU-RTS Trigger frame. The UHR variant MU-RTS Trigger frame of this specification may reuse an EHT variant MU-RTS Trigger frame defined in a conventional wireless LAN standard. For example, the UHR variant MU-RTS Trigger frame may be identified or distinguished based on a special user info field included in the trigger frame. For example, whether a specific Trigger frame (or MU-RTS Trigger frame) is the UHR variant MU-RTS Trigger frame may be identified based on the 3-bit value of the PHY version identifier included in the special user info field. Specifically, the value of the PHY version identifier field included in the UHR variant MU-RTS Trigger frame is one (1). For example, the value of the PHY version identifier field included in the EHT variant MU-RTS Trigger frame is zero (0).

[0207] Additionally, or generally, the common field of the above UHR variant MU-RTS trigger frame may inherit the common field of the EHT variant MU-RTS trigger frame. For example, a subfield defined only for the EHT variant may be changed and defined as UHR variant information.

[0208] For example, in order to solicit a CTS frame based on an ELR PPDU (format) using the UHR variant MU-RTS trigger frame defined as above, various examples described below (e.g., the first / second / third example, etc.) may be utilized.

[0209] Example 1

[0210] The following example relates to an example of soliciting or indicating a CTS frame using the common field of a MU-RTS trigger frame (UHR variant). In other words, the information contained in the common field of the MU-RTS trigger frame may relate to whether the CTS frame transmitted in response to the MU-RTS trigger frame is an ELR PPDU (format).

[0211] For example, a first STA (e.g., AP) can identify information about at least one second STA (e.g., non-AP) that supports the ELR PPDU. For example, information about at least one second STA (e.g., non-AP) that supports the ELR PPDU can be identified based on the previously described UHR Operation Parameters field or UHR PHY Capabilities Information within the UHR Capabilities element. For example, when transmitting a (UHR variant) MU-RTS trigger frame, the first STA (e.g., AP) can solicit the transmission of a CTS frame using the ELR PPDU (format) to at least one second STA that supports the transmission of the ELR PPDU. For example, information for soliciting the transmission of the CTS frame may be included in the common info field of the (UHR variant) MU-RTS trigger frame. Specifically, it is preferable that the indication soliciting the above ELR PPDU transmission (e.g., CTS frame transmission based on ELR PPDU) be included in the common field of the above (UHR variant) MU-RTS trigger frame.

[0212] For example, an indication soliciting the above ELR PPDU transmission (e.g., CTS frame transmission based on ELR PPDU) may include the following information.

[0213] Information 1: ELR PPDU TX indication

[0214] The first information may have various names such as ELR PPDU TX indication or ELR PPDU TX information / field / subfield. The first information may indicate whether a CTS frame, which is a response frame to a MU-RTS Trigger frame received by a non-AP STA, is transmitted (to the AP) based on the ELR PPDU (format). The first information may have various bit lengths and, for example, may consist of 1-bit information. As described above, the first information may be included in the common info field within the trigger frame, for example, in bits B22, B26, B53, B56 to B62, and / or B63. The first information may indicate that the CTS frame is solicited based on the ELR PPDU based on a first value (e.g., 1). For example, the first information may indicate that the CTS frame is solicited based on a non-HT (Dup) PPDU based on a second value (e.g., 0). For example, if there are multiple STAs (e.g., non-AP STAs) receiving the MU-RTS frame, it is preferable that all of the STAs are UHR non-AP STAs that support ELR PPDU transmission. In other words, it is preferable for the AP to exchange Management frames to verify the capabilities of multiple non-AP STAs located within the BSS, and to transmit a MU-RTS trigger frame having the first value only to the non-AP STAs among the multiple non-AP STAs that support ELR PPDU transmission.

[0215] Additionally or generally, when the first information (e.g., ELR PPDU TX indication) is set to the first value (e.g., 1), the user info field included in the MU-RTS trigger frame may include at least one of the following subfields. Additionally or generally, the user info field described below may be defined by reusing the EHT variant User Info field format. For example, it may include all subfields included in the EHT variant User Info field format, or some of the entire subfields may be defined differently.

[0216] 1st Subfield: RU Allocation Subfield

[0217] The first subfield above may indicate information about a 242-tone RU or 20 MHz subchannel that transmits an ELR PPDU (e.g., an ELR PPDU containing a CTS frame) using an ELR PPDU. For example, through the first subfield (e.g., RU allocation), at least one non-AP STA receiving a MU-RTS trigger frame may indicate information about the RU / subchannel to which the CTS frame will be transmitted. For example, an intended STA (e.g., non-AP STA(s)) that receives a MU-RTS trigger frame may transmit a CTS frame, which is a response frame to the MU-RTS trigger frame it received, using an ELR PPDU based on the first subfield.

[0218] 2nd Subfield: ELR MCS

[0219] For example, the second subfield may contain information about the MCS used when configuring the ELR PPDU for the CTS frame. The second subfield may consist of 1 bit. For example, the first value (e.g., 0) of the second subfield may indicate the MCS0 index, and the second value (e.g., 1) of the second subfield may indicate the MCS1 index. For example, the second subfield may be included in one of the bits B29 to B38 of the user info field. Specifically, the second subfield may be located at bit B29.

[0220] Third Subfield: BW for DL

[0221] For example, the third subfield may indicate the bandwidth for the PPDU to which the MU-RTS trigger frame is transmitted, or the PPDU bandwidth for DL ​​transmission. For example, the bandwidth indicated by the third subfield may be configured based on the following. For example, the third subfield may be composed of 3 bits. The value of the 3 bits may include information regarding 20 / 40 / 80 / 160 / 320 MHz. For example, the third subfield may be defined in such a way that 3 bits are allocated from bits B29 to B38 within the user info field of the trigger frame. For example, the third subfield may be located at bits B30 to B32, taking into account ELR MCS allocation. For example, when the BW is defined as less than 320 MHz, an additional 1 bit may be included or defined to indicate whether the channel / resource / band where the BW is located is P160 (e.g., primary 160 MHz) or S160 (e.g., secondary 160 MHz). For example, the 1 bit may be located in one of the bits B29 to B38 of the user info field. For example, the first value of the 1 bit (e.g., 0) may represent the P160, and the second value of the 1 bit (e.g., 1) may represent the S160. For example, the 1 bit may have an independent or different value distinct from the existing PS160 information present in the user info field. The 1 bit may be the LSB or MSB of bits B31 to B34 of FIG. 16. In this case, among bits B31 to B34 of FIG. 16, the remaining 3 bits can indicate information regarding BW according to the third sub-field.

[0222] FIG. 16 is an example of a User Info field format including the subfields described above. For example, the first subfield described above may be included in bits B12 to B19 as shown in FIG. 16. For example, the second subfield described above may be included in bit B29 as shown in FIG. 16. For example, the third subfield described above (and the 1-bit information described above) may be included in bits B31 to B34 as shown in FIG. 16.

[0223] The example of FIG. 16 can be modified in various ways. For example, the second subfield indicated in bit B29 may be omitted. Since the ELR PPDU TX indication described above may be included in the common info field of the trigger frame containing the corresponding user info field, bit B29 of FIG. 16 may be configured as a reserved bit or may include a bit having a different function.

[0224] Additionally, or generally, the third subfield (and the 3-bit information described above) in FIG. 16 may be omitted. The corresponding positions (e.g., bits B31 to B34) may be composed of reserved bits or may include bits having other functions.

[0225] Example 2

[0226] The following example relates to an example of soliciting or indicating a CTS frame using the special user info field of a MU-RTS trigger frame (UHR variant). In other words, the information contained in the special user info field of the MU-RTS trigger frame may relate to whether the CTS frame transmitted in response to the MU-RTS trigger frame is an ELR PPDU (format). For example, the special user info field may be a field consecutive to the common field and may include extended common info for all receiving STAs receiving the trigger frame.

[0227] The first information (e.g., ELR PPDU TX indication) described in the first example above may be included in the special user info field. In this case, the function performed by the first information (e.g., ELR PPDU TX indication) may be the same as the function in the first example above. For example, if there are multiple STAs (e.g., non-AP STAs) receiving the corresponding MU-RTS frame, it is preferable that all of the STAs are UHR non-AP STAs that support ELR PPDU transmission. In other words, it is preferable for the AP to exchange Management frames to verify the capabilities of multiple non-AP STAs located within the BSS, and to transmit a MU-RTS trigger frame having the first value only to the non-AP STA among the multiple non-AP STAs that supports ELR PPDU transmission.

[0228] For example, the first information (e.g., ELR PPDU TX indication) included in the special user info field may be included in various locations within the special user info field. For example, it may be included in any one of bits B37 to B39 (e.g., bit B37) of the special user info field. For example, if the first information (e.g., ELR PPDU TX indication) indicates the transmission of an ELR PPDU-based CTS frame, the Spatial Reuse field included in the special user info field may be set to disallowed. Additionally or alternatively, if the first information (e.g., ELR PPDU TX indication) indicates the transmission of an ELR PPDU-based CTS frame, the spatial reused field included in the special user info field may be reserved or replaced with a field having a different function.

[0229] For example, the special user info field may include a BW field to indicate a BW for a PPDU in which a MU-RTS trigger frame is transmitted, or a PPDU BW for a DL transmission, and the BW field may be set to 3 / 4 bits. The BW field of 3 / 4 bits described above may be the same as the third subfield described in the first example. For example, as previously described, the BW field or the third subfield may further include 1 bit of information related to P160 / S160.

[0230] FIG. 17 illustrates an example of a special user info format according to the present specification. As illustrated, the first information (e.g., ELR PPDU TX indication) may be included in the B37 bit.

[0231] For example, when an ELR PPDU-based CTS frame is solicited through the aforementioned Special user info field, the user info field(s) included in the corresponding MU-RTS trigger frame may contain information regarding the transmission of the ELR PPDU. For example, the user info field proposed by this specification contains information regarding the MCS used during the transmission of the ELR PPDU. This information may consist of 1 bit. This 1 bit may have various names such as ELR MCS field / bit / information. For example, the first value of this 1 bit (e.g., 0) may indicate that the MCS index of the related ELR PPDU (e.g., CTS frame) is the MCS0 index. For example, the second value of this 1 bit (e.g., 1) may indicate that the MCS index of the related ELR PPDU (e.g., CTS frame) is the MCS1 index.

[0232] For example, when an ELR PPDU transmission (e.g., transmission of a CTS frame) is solicited through a special user info field, the RU allocation subfield in the relevant user info field may be configured as follows. For example, the RU allocation subfield may include information regarding a 242 RU or 20 MHz subchannel through which a STA (e.g., non-AP STA) transmits a CTS frame using an ELR PPDU. For example, information regarding a 20 MHz channel or a 242 tone RU through which a STA (e.g., non-AP STA) transmits a CTS frame may be indicated through the RU allocation subfield. For example, the 20 MHz channels allocated to each STA are determined differently, and it is possible for an AP to receive CTS frames from multiple STAs through different 20 MHz channels. Accordingly, information regarding the 20 MHz channel through which a CTS frame is transmitted via an ELR PPDU is indicated through the RU allocation field. In other words, through the above RU allocation subfield, a STA (e.g., non-AP STA) can transmit CTS frames in units of 20 MHz or 242 tone RU within the BW.

[0233] FIG. 18 illustrates an example of a user info format according to the present specification. As illustrated, information regarding the MCS described above may be included in the example of FIG. 18, and said information may be included in various locations such as the B29 bit.

[0234] Third Example

[0235] The following example relates to an example of soliciting or indicating a CTS frame using the user info field of a MU-RTS trigger frame (UHR variant). In other words, the information contained in the user info field of the MU-RTS trigger frame may relate to whether the CTS frame transmitted in response to the MU-RTS trigger frame is an ELR PPDU (format).

[0236] For example, the first information (e.g., ELR PPDU TX indication) described in the first example above may be included in the user info field. In this case, as described above, the corresponding subfield / information (e.g., ELR PPDU TX indication) indicates the use of ELR PPDU when transmitting a CTS frame and may be defined as 1 bit. For example, the corresponding subfield / information (e.g., ELR PPDU TX indication) may be located in one bit (e.g., B29) among bits B29 to B38 within the user info field. For example, if the corresponding subfield / information (e.g., ELR PPDU TX indication) has a first value (e.g., 0), the CTS frame corresponding to MU-RTS may be transmitted based on non-HT (DUP) PPDU. For example, if the corresponding subfield / information (e.g., ELR PPDU TX indication) has a second value (e.g., 1), the CTS frame corresponding to MU-RTS may be transmitted based on ELR PPDU.

[0237] For example, if there are multiple STAs (e.g., non-AP STAs) receiving the MU-RTS frame, it is desirable that all of the STAs are UHR non-AP STAs that support ELR PPDU transmission. In other words, it is desirable for the AP to exchange Management frames to identify the capabilities of multiple non-AP STAs located within the BSS, and to transmit a MU-RTS trigger frame having the first value only to the non-AP STA among the multiple non-AP STAs that supports ELR PPDU transmission.

[0238] The user info related to the third example may further include information regarding the ELR MCS. For example, the user info field proposed by this specification includes information regarding the MCS used when transmitting an ELR PPDU, and such information may consist of 1 bit. Such 1 bit may have various names such as ELR MCS field / bit / information. For example, the first value of such 1 bit (e.g., 0) may indicate that the MCS index of the related ELR PPDU (e.g., CTS frame) is the MCS0 index. For example, the second value of such 1 bit (e.g., 1) may indicate that the MCS index of the related ELR PPDU (e.g., CTS frame) is the MCS1 index.

[0239] FIG. 19 illustrates an example of a user info format according to the present specification. As illustrated, information regarding the MCS described above may be included in the example of FIG. 19, and such information may be included in various locations such as the B30 bit. Additionally, information related to the ELR PPDU TX indication described above may be included in the example of FIG. 19, and such information may be included in various locations such as the B29 bit.

[0240] As described above, when soliciting an ELR PPDU through the ELR PPDU TX subfield of the user info field, the RU allocation subfield included in the user info field may be composed of information about the 242 tone RU or 20 MHz subchannel used when the ELR PPDU is transmitted.

[0241] FIG. 20 illustrates an example of the exchange of MU-RTS frames and CTS frames according to the present specification. As illustrated, the transmission of a CTS frame using an ELR PPDU can be requested through a MU-RTS trigger frame.

[0242] As illustrated in FIG. 20, a MU-RTS trigger frame may be configured. The MU-RTS trigger frame may be configured with common info, special user info, and / or user info based on the first to third Examples. A CTS frame may be transmitted in response to the MU-RTS trigger frame of FIG. 20. As described above, the CTS frame may be configured based on an ELR PPDU rather than a conventional non-HT PPDU. As illustrated in FIG. 20, the IFS of the MU-RTS trigger frame and the CTS frame may be set to Short IFS (SIFS).

[0243] FIG. 21 is a flowchart of the procedure according to the present specification.

[0244] The procedure of FIG. 21 can be performed in various STAs. For example, the operation of FIG. 21 can be performed in non-AP STA(s), non-AP MLD(s), AP(s), or AP MLD(s), etc. For example, the operation of FIG. 21 can be performed in a non-AP STA(s) that receives a trigger frame.

[0245] According to step S2110, the STA may receive a MU-RTS (multi-user request to send) trigger frame. For example, the MU-RTS trigger frame of step S2110 may be the MU-RTS trigger frame of FIG. 20. For example, the MU-RTS trigger frame of step S2110 may include at least one of the information fields of FIG. 16 to FIG. 19 (e.g., common info, special user info, user info, etc.).

[0246] For example, the MU-RTS trigger frame may include a first information field and a second information field. For example, the first information field may include at least one of common info, special user info, and user info. For example, the second information field may include at least one of common info, special user info, and user info.

[0247] For example, the first information field may be a special user info field. For example, the second information field may be a user info field. For example, the special user info may be located immediately after the common information field. For example, the first information field or the special user info field may carry extended common info that is not provided in the common information field. For example, the common information field may include at least one technical feature related to an example of FIG. 16. For example, the special user info field may include at least one technical feature related to an example of FIG. 17. For example, the user info field may include at least one technical feature related to an example of FIG. 18 or FIG. 19. For example, the second information field or the user info field may include an ultra-high reliability (UHR) variant user info field.

[0248] For example, information regarding the PPDU format of the CTS frame may have a length of 1 bit. For example, information regarding the PPDU format of the CTS frame may be the PPDU TX indication described above. For example, based on the information regarding the PPDU format of the CTS frame having a first value, the PPDU format of the CTS frame may be determined as an ELR PPDU format. For example, based on the information regarding the PPDU format of the CTS frame having a second value, the PPDU format of the CTS frame may be determined as a non-HT (non-High Throughout) PPDU format.

[0249] For example, the MCS information related to the ELR PPDU format may have a length of 1 bit. For example, the MCS information related to the ELR PPDU format may be the ELR MCS field / bit / information described above. For example, based on the fact that the MCS information related to the ELR PPDU format has a first value, the CTS frame may be constructed based on the MCS index zero (0). For example, based on the fact that the MCS information related to the ELR PPDU format has a second value, the CTS frame may be constructed based on the MCS index one (1). For example, the MCS index zero (0) is related to a code rate of 1 / 2 and Binary Phase Shift Keying (BPSK) and may be expressed as an MCS0 index, etc. For example, the MCS index one (1) is related to a code rate of 1 / 2 and Quadrature Phase Shift Keying (QPSK) and may be expressed as an MCS1 index, etc.

[0250] According to step S2120, the STA may transmit the CTS frame based on the MU-RTS trigger frame. For example, the CTS frame of step S2120 may be the CTS frame of FIG. 20. Whether the CTS frame of step S2120 is based on the ELR PPDU format or the non-HT (DUP) PPDU format may be based on information regarding the PPDU format of the CTS frame. An MCS0 index or an MCS1 index may be applicable to the ELR PPDU format, and which MCS index is used may be determined based on MCS information related to the ELR PPDU format. In other words, whether the MCS related to the CTS frame is used may be determined based on MCS information related to the ELR PPDU format. For example, information regarding a 242-tone RU and / or 20 MHz subchannel allocated for a CTS frame transmitted / received based on the ELR PPDU format can be determined based on the RU allocation subfield information included in the trigger frame. The RU allocation subfield may be referred to by various names such as the first / second / third information field, the first / second / third information bit, control information, and radio resource allocation information. For example, the RU allocation subfield may be configured based on an example of FIG. 18 and / or FIG. 19.

[0251] For example, the above CTS frame may include an RA field and not include a TA field. For example, the above RA field may include a value related to the address of the STA (station) that transmitted the MU-RTS trigger frame. For example, the above TA field may be related to the address of the STA (station) that transmitted the CTS frame.

[0252] FIG. 22 is another example of a procedure flowchart according to the present specification.

[0253] The procedure of FIG. 22 can be performed in various STAs. For example, the operation of FIG. 22 can be performed in non-AP STA(s), non-AP MLD(s), AP(s), or AP MLD(s), etc. For example, the operation of FIG. 22 can be performed in an AP that transmits a trigger frame.

[0254] According to step S2210, the STA may transmit a MU-RTS (multi-user request to send) trigger frame. The trigger frame of step S2210 may be the same as the trigger frame of step S2110. For convenience of explanation, redundant descriptions may be omitted.

[0255] According to step S2220, the STA may receive the CTS frame based on the MU-RTS trigger frame. The CTS frame of step S2220 may be the same as the CTS frame of step S2120. For convenience of explanation, redundant descriptions may be omitted.

[0256] The technical features of this specification may be performed by various devices. The device of this specification may be the device described in FIG. 1 / 14. The device of this specification may include at least one processor; and at least one computer memory that is operabably connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor.

[0257] For example, the processor may be the processor described in FIG. 1 and / or FIG. 14. That is, as described above, the processor of this specification 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). The processor includes computers having various architectures, such as single / multi-processor architectures and sequential (Von Neumann) / parallel architectures, as well as specialized circuits such as FPGAs, ASICs, signal processing units, and other devices. For example, the processor of this specification may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or a processor enhanced therefrom.

[0258] For example, the above instructions may refer to computer program instructions executed by the at least one processor. The above (computer program) instructions provide logic and / or routines that enable the technical features of the present specification to be performed by the processor. By reading the at least one memory, the at least one processor can load and execute the computer program.

[0259] The computer program(s) defined by the above instruction may arrive at the device of this specification (e.g., STA) through an appropriate delivery mechanism. The delivery mechanism may be, for example, a computer-readable storage medium, a computer program product, a memory device, a recording medium such as a CD-ROM or DVD, or a manufactured product that tangibly embodies the computer program. The delivery mechanism may be a signal configured to reliably transmit the computer program via a wireless or electrical connection.

[0260] The above (computer program) instructions may include software or firmware for a programmable processor (e.g., programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array, or programmable logic device, etc.).

[0261] For example, the memory described above may be the memory described in FIG. 1 and / or FIG. 14. That is, as described above, the memory of the present specification may store control information related to the operation of the STA of the present specification or information regarding signals transmitted and received by the STA (e.g., PPDU containing a management / control / data frame).

[0262] The technical features of this specification may be implemented in at least one computer-readable medium (CRM). The CRM includes instructions based on execution by at least one processor described above. Instructions stored in the CRM may be the computer program instructions described above.

[0263] The device of the present specification may further include a transceiver. The transceiver may be operabably connectable to the memory / processor, etc. The transceiver may be the transceiver illustrated in FIG. 1 and / or FIG. 14.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. Receive a MU-RTS (multi-user request to send) trigger frame, The above MU-RTS trigger frame includes a first information field and a second information field, and The first information field above includes information regarding the PPDU (physical protocol data unit) format of the CTS (clear to send) frame, which is the response to the MU-RTS trigger frame, and The PPDU format of the above CTS frame includes the ELR (enhanced long range) PPDU format, and The second information field above includes MCS (modulation and coding scheme) information related to the ELR PPDU format, and Step, wherein the first information field is a special user info field and the second information field is a user info field; and A step of transmitting the CTS frame based on the above MU-RTS trigger frame A method including 2. In claim 1, the MU-RTS trigger frame includes a common info field, and The first information field or the special user information field carries extended common info that is not provided in the common information field, and The above special user information field is located immediately after the above common information field, method.

3. In paragraph 1, the second information field or the user info field comprises an ultra-high reliability (UHR) variant user info field. method.

4. In paragraph 1, the information regarding the PPDU format of the CTS frame has a length of 1 bit, and Based on the fact that the information regarding the PPDU format of the above CTS frame has a first value, the PPDU format of the above CTS frame is determined to be an ELR PPDU format, and Based on the fact that the information regarding the PPDU format of the above CTS frame has a second value, the PPDU format of the above CTS frame is determined to be a non-HT (non-High Throughout) PPDU format. method.

5. In paragraph 1, the MCS information related to the ELR PPDU format has a length of 1 bit, and Based on the fact that the MCS information related to the above ELR PPDU format has a first value, the above CTS frame is configured based on the MCS index zero (0), and Based on the fact that the MCS information related to the above ELR PPDU format has a second value, the above CTS frame is configured based on the MCS index one (1), and The above MCS index zero (0) is related to a code rate of 1 / 2 and BPSK (Binary Phase Shift Keying), and The above MCS index (1) is related to a code rate of 1 / 2 and QPSK (Quadrature Phase Shift Keying), method.

6. In paragraph 1, the MU-RTS trigger frame further comprises a third information field, wherein the third information field comprises allocation information related to a 242-tone RU (resource unit) or a 20 MHz subchannel allocated for the CTS frame, and The above CTS frame is transmitted based on the above third information field, method.

7. Regarding STA(station), At least one processor; and It includes at least one computer memory that is operablely connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, Receive a MU-RTS (multi-user request to send) trigger frame, The above MU-RTS trigger frame includes a first information field and a second information field, and The first information field above includes information regarding the PPDU (physical protocol data unit) format of the CTS (clear to send) frame, which is the response to the MU-RTS trigger frame, and The PPDU format of the above CTS frame includes the ELR (enhanced long range) PPDU format, and The second information field above includes MCS (modulation and coding scheme) information related to the ELR PPDU format, and Step, wherein the first information field is a special user info field and the second information field is a user info field; and A step of transmitting the CTS frame based on the above MU-RTS trigger frame Performing an operation that includes STA.

8. In Paragraph 7 The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 1 to 6. STA.

9. Send a MU-RTS (multi-user request to send) trigger frame, but The above MU-RTS trigger frame includes a first information field and a second information field, and The first information field above includes information regarding the PPDU (physical protocol data unit) format of the CTS (clear to send) frame, which is the response to the MU-RTS trigger frame, and The PPDU format of the above CTS frame includes the ELR (enhanced long range) PPDU format, and The second information field above includes MCS (modulation and coding scheme) information related to the ELR PPDU format, and Step, wherein the first information field is a special user info field and the second information field is a user info field; and A step of receiving the CTS frame based on the above MU-RTS trigger frame A method including 10. In Paragraph 9 The STA (station) transmitting the above MU-RTS trigger frame performs an operation related to any one of claims 1 to 6. method.

11. Regarding STA(station), At least one processor; and It includes at least one computer memory that is operablely connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, Transmit a MU-RTS (multi-user request to send) trigger frame, The above MU-RTS trigger frame includes a first information field and a second information field, and The first information field above includes information regarding the PPDU (physical protocol data unit) format of the CTS (clear to send) frame, which is the response to the MU-RTS trigger frame, and The PPDU format of the above CTS frame includes the ELR (enhanced long range) PPDU format, and The second information field above includes MCS (modulation and coding scheme) information related to the ELR PPDU format, and Step, wherein the first information field is a special user info field and the second information field is a user info field; and A step of receiving the CTS frame based on the above MU-RTS trigger frame Performing an operation that includes STA.

12. In Paragraph 11 The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 1 to 6. STA.

13. In a wireless local area network (WLAN) system, at least one computer-readable medium comprising an instruction based on execution by at least one processor, Receive a MU-RTS (multi-user request to send) trigger frame, The above MU-RTS trigger frame includes a first information field and a second information field, and The first information field above includes information regarding the PPDU (physical protocol data unit) format of the CTS (clear to send) frame, which is the response to the MU-RTS trigger frame, and The PPDU format of the above CTS frame includes the ELR (enhanced long range) PPDU format, and The second information field above includes MCS (modulation and coding scheme) information related to the ELR PPDU format, and Step, wherein the first information field is a special user info field and the second information field is a user info field; and A step of transmitting the CTS frame based on the above MU-RTS trigger frame Performing an operation that includes Recording media.

Images