Method and apparatus for receiving a PPDU through multiple RUs in a wireless LAN system

Abstract

A method and apparatus for receiving a PPDU in a wireless LAN system are proposed. Specifically, a receiving STA receives a PPDU from a transmitting STA through a wideband and decodes the PPDU. The PPDU includes a control field and a data field. When the wideband is a 320 / 160+160 MHz band including a first 80 MHz sub-channel to a fourth 80 MHz sub-channel, the first 80 MHz sub-channel includes a first 996 RUs, the second 80 MHz sub-channel includes a second 996 RUs, the third 80 MHz sub-channel includes a third 996 RUs, and the fourth 80 MHz sub-channel includes a first 484 RUs. The data field is received through a first plurality of RUs in which the first 996 RUs to the third 996 RUs and the first 484 RUs are aggregated.

Description

Technical Field

[0001] The present disclosure relates to a technique for receiving a PPDU through multiple RUs in a WLAN system, and more particularly, to a method and apparatus for transmitting and receiving a PPDU in a non - OFDMA scheme by aggregating multiple RUs combined into a large RU. Background Art

[0002] Wireless Local Area Networks (WLANs) have been improved in various ways. For example, the IEEE 802.11ax standard proposes an improved communication environment using Orthogonal Frequency Division Multiple Access (OFDMA) and Downlink Multi - User Multiple - Input Multiple - Output (DL MU MIMO) techniques.

[0003] This specification presents technical features that can be utilized in new communication standards. For example, the new communication standard can be the Extremely High Throughput (EHT) standard currently under discussion. The EHT standard can use newly proposed increased bandwidth, enhanced PHY layer Protocol Data Unit (PPDU) structure, enhanced sequences, Hybrid Automatic Repeat reQuest (HARQ) schemes, etc. The EHT standard can be referred to as the IEEE 802.11be standard.

[0004] In the new wireless LAN standard, an increased number of spatial streams may be used. In this case, in order to appropriately use the increased number of spatial streams, it may be necessary to improve the signaling technology in the WLAN system. Summary of the Invention

[0005] Technical Problem

[0006] The present disclosure proposes a method and apparatus for receiving a PPDU through multiple RUs in a WLAN system.

[0007] Technical Solution

[0008] An example of this specification proposes a method for receiving a PPDU through multiple RUs.

[0009] This embodiment can be executed in a network environment supporting a next - generation wireless LAN system (e.g., IEEE 802.11be or EHT wireless LAN system). The next - generation wireless LAN system is a wireless LAN system improved from the 802.11ax system and can satisfy backward compatibility with the 802.11ax system.

[0010] This embodiment presents a method and apparatus for transmitting and receiving a PPDU based on multiple RUs configured through a combination between large RUs. In this case, a large RU means a resource unit having more than 242 tones. In particular, this embodiment presents a method for configuring multiple RUs for transmitting a PPDU in a non-OFDMA scheme.

[0011] A receiving station (STA) receives a physical protocol data unit (PPDU) from a transmitting STA over a wideband.

[0012] The receiving STA decodes the PPDU.

[0013] The PPDU includes a control field and a data field.

[0014] When the wideband is a 320 / 160+160 MHz band including a first 80 MHz subchannel to a fourth 80 MHz subchannel, the first 80 MHz subchannel includes a first 996 resource units (RUs), the second 80 MHz subchannel includes a second 996 RUs, the third 80 MHz subchannel includes a third 996 RUs, and the fourth 80 MHz subchannel includes a first 484 RUs.

[0015] The data field is received through a first plurality of RUs in which the first 996 RUs to the third 996 RUs and the first 484 RUs are aggregated. That is, the data field can be received through a plurality of RUs in which three 996 RUs and one 484 RU are aggregated. As described above, the wideband may include four 80 MHz subchannels. The three 996 RUs and one 484 RU may be respectively assigned to each of the four 80 MHz subchannels. In this case, the first 996 RUs to the third 996 RUs may be RUs composed of 996 tones, and the first 484 RU may be an RU composed of 484 tones.

[0016] Technical Effects

[0017] According to the embodiments presented in this specification, by supporting preamble puncturing and aggregation of large RUs of various sizes in non-OFDMA, there is a new effect of increasing transmission efficiency and throughput. Brief Description of the Drawings

[0018] Figure 1 Illustrates an example of a transmitting device and / or a receiving device of this specification.

[0019] Figure 2 Is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0020] Figure 3 Illustrates a general link setup process.

[0021] Figure 4Illustrates an example of a PPDU used in the IEEE standard.

[0022] Figure 5 Illustrates the layout of resource units (RUs) used in a 20 MHz frequency band.

[0023] Figure 6 Illustrates the layout of resource units (RUs) used in a 40 MHz frequency band.

[0024] Figure 7 Illustrates the layout of resource units (RUs) used in an 80 MHz frequency band.

[0025] Figure 8 Illustrates the structure of the HE-SIG-B field.

[0026] Figure 9 Illustrates an example of assigning multiple user STAs to the same RU through the MU-MIMO scheme.

[0027] Figure 10 Illustrates UL-MU-based operations.

[0028] Figure 11 Illustrates an example of a trigger frame.

[0029] Figure 12 Illustrates an example of the common information field of a trigger frame.

[0030] Figure 13 Illustrates an example of the subfields included in each user information field.

[0031] Figure 14 Describes the technical features of the UORA scheme.

[0032] Figure 15 Illustrates an example of a channel used / supported / defined in the 2.4 GHz frequency band.

[0033] Figure 16 Illustrates an example of a channel used / supported / defined in the 5 GHz frequency band.

[0034] Figure 17 Illustrates an example of a channel used / supported / defined in the 6 GHz frequency band.

[0035] Figure 18 Illustrates an example of a PPDU used in this specification.

[0036] Figure 19 Illustrates an example of a modified transmitting device and / or receiving apparatus / device used in this specification.

[0037] Figure 20Shows an example of the PHY transmission process for HE SU PPDU.

[0038] Figure 21 Shows an example of a block diagram of a transmitting device for generating each field of HE PPDU.

[0039] Figure 22 Shows the channel structure of 80 MHz.

[0040] Figure 23 Shows an example of preamble puncturing in non - OFDMA 80 MHz transmission.

[0041] Figure 24 Shows an example of additional preamble puncturing in non - OFDMA 80 MHz transmission.

[0042] Figure 25 Shows an example of 160 / 80 + 80 MHz channel configuration.

[0043] Figure 26 Is an example of 240 / 160 + 80 MHz derived from continuous 320 MHz.

[0044] Figure 27 Is an example of continuous 240 MHz derived from continuous 320 MHz.

[0045] Figure 28 Is an example of non - continuous 160 + 80 MHz derived from non - continuous 160 + 160 MHz.

[0046] Figure 29 Shows the channel structure of 320 / 160 + 160 MHz.

[0047] Figure 30 Shows an example of the EHT PPDU format.

[0048] Figure 31 Shows an example of the U - SIG format.

[0049] Figure 32 Is a flowchart illustrating the operation of the transmitting device according to this embodiment.

[0050] Figure 33 Is a flowchart illustrating the operation of the receiving device according to this embodiment.

[0051] Figure 34 Is a flowchart illustrating the process in which the transmitting STA transmits the PPDU according to this embodiment.

[0052] Figure 35 Is a flowchart illustrating the process for the receiving STA to receive the PPDU according to this embodiment. Detailed implementation mode

[0053] In this specification, "A or B" may mean "only A", "only B", or "both A and B". In other words, in this specification, "A or B" can 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".

[0054] The slashes ( / ) or commas used in this specification may mean "and / or". For example, "A / B" may mean "A and / or B". Therefore, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0055] 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 expression "at least one of A or B" or "at least one of A and / or B" may be interpreted as "at least one of A and B".

[0056] Furthermore, in this specification, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "any combination of A, B, and C". Additionally, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".

[0057] Moreover, the parentheses used in this specification may mean "for example". Specifically, when indicated as "control information (EHT-signal)", it may indicate that "EHT-signal" is proposed as an example of "control information". In other words, the "control information" in this specification is not limited to "EHT-signal", and "EHT-signal" can be proposed as an example of "control information". Additionally, when indicated as "control information (i.e., EHT-signal)", it may also mean that "EHT-signal" is proposed as an example of "control information".

[0058] The technical features described separately in one drawing of this specification can be implemented separately or simultaneously.

[0059] The following examples of this specification can be applied to various wireless communication systems. For example, the following examples of this specification can be applied to a Wireless Local Area Network (WLAN) system. For example, this specification can be applied to the IEEE 802.11a / g / n / ac standards or the IEEE 802.11ax standard. Additionally, this specification can also be applied to the newly proposed EHT standard or the IEEE 802.11be standard. Furthermore, the examples of this specification can also be applied to a new WLAN standard enhanced from the EHT standard or the IEEE 802.11be standard. Additionally, the examples of this specification can be applied to a mobile communication system. For example, it can be applied to a Long-Term Evolution (LTE) based on the 3rd Generation Partnership Project (3GPP) standards and a mobile communication system evolved based on LTE. Additionally, the examples of this specification can be applied to a communication system based on the 5G NR standard of the 3GPP standards.

[0060] Hereinafter, in order to describe the technical features of this specification, the technical features applicable to this specification will be described.

[0061] Figure 1 Examples of the transmitting device and / or receiving device of this specification are shown.

[0062] In Figure 1 the examples, various technical features described below can be performed. Figure 1 It relates to at least one Station (STA). For example, the STAs 110 and 120 of this specification can also be referred to by various terms such as mobile terminals, wireless devices, Wireless Transmit / Receive Units (WTRUs), User Equipments (UEs), Mobile Stations (MSs), mobile subscriber units or simply referred to as users. The STAs 110 and 120 of this specification can also be referred to by various terms such as networks, base stations, Node Bs, Access Points (APs), repeaters, routers, relays, etc. The STAs 110 and 120 of this specification can also be referred to by various names such as receiving devices, transmitting devices, receiving STAs, transmitting STAs, receiving equipments, transmitting equipments, etc.

[0063] For example, the STAs 110 and 120 can be used as APs or non-APs. That is, the STAs 110 and 120 of this specification can be used as APs and / or non-APs.

[0064] In addition to the IEEE 802.11 standard, the STAs 110 and 120 of this specification can support various communication standards together. For example, communication standards based on 3GPP standards (such as LTE, LTE-A, 5G NR standards, etc.) can be supported. In addition, the STAs of this specification can be implemented as various devices such as mobile phones, vehicles, personal computers, etc. In addition, the STAs of this specification can support communication for various communication services such as voice calls, video calls, data communication, and self-driving (autonomous driving).

[0065] The STAs 110 and 120 of this specification can include a Media Access Control (MAC) compliant with the IEEE 802.11 standard and a physical layer interface for the radio medium.

[0066] The following will refer to Figure 1 subfigure (a) of to describe the STAs 110 and 120.

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

[0068] The transceiver 113 of the first STA performs signal transmission / reception operations. Specifically, IEEE 802.11 packets (such as IEEE 802.11a / b / g / n / ac / ax / be, etc.) can be transmitted / received.

[0069] For example, the first STA 110 can perform operations expected of an AP. For example, the processor 111 of the AP can receive a signal through the transceiver 113, process the received (RX) signal, generate a transmitted (TX) signal, and provide control for signal transmission. The memory 112 of the AP can store the signal received through the transceiver 113 (such as the RX signal), and can store the signal to be transmitted through the transceiver (such as the TX signal).

[0070] For example, the second STA 120 can perform operations expected of a non-AP STA. For example, the transceiver 123 of the non-AP performs signal transmission / reception operations. Specifically, IEEE 802.11 packets (such as IEEE 802.11a / b / g / n / ac / ax / be packets, etc.) can be transmitted / received.

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

[0072] For example, the operations of the device indicated as an AP in the specification described below can be executed in the first STA 110 or the second STA 120. For example, if the first STA 110 is an AP, the operations of the device indicated as an AP can be controlled by the processor 111 of the first STA 110, and the relevant signals can be transmitted or received via the transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, the control information related to the operations of the AP or the TX / RX signals of the AP can be stored in the memory 112 of the first STA 110. Additionally, if the second STA 120 is an AP, the operations of the device indicated as an AP can be controlled by the processor 121 of the second STA 120, and the relevant signals can be transmitted or received via the transceiver 123 controlled by the processor 121 of the second STA 120. Additionally, the control information related to the operations of the AP or the TX / RX signals of the AP can be stored in the memory 122 of the second STA 120.

[0073] For example, in the specification described below, the operations of the device indicated as a non-AP (or user STA) can be executed in the first STA 110 or the second STA 120. For example, if the second STA 120 is a non-AP, the operations of the device indicated as a non-AP can be controlled by the processor 121 of the second STA 120, and the relevant signals can be transmitted or received via the transceiver 123 controlled by the processor 121 of the second STA 120. Additionally, the control information related to the operations of the non-AP or the TX / RX signals of the non-AP can be stored in the memory 122 of the second STA 120. For example, if the first STA 110 is a non-AP, the operations of the device indicated as a non-AP can be controlled by the processor 111 of the first STA 110, and the relevant signals can be transmitted or received via the transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, the control information related to the operations of the non-AP or the TX / RX signals of the non-AP can be stored in the memory 112 of the first STA 110.

[0074] In the following description of the specification, devices such as (transmitting / receiving) STAs, first STAs, second STAs, STA1, STA2, APs, first APs, second APs, AP1, AP2, (transmitting / receiving) terminals, (transmitting / receiving) devices, (transmitting / receiving) apparatuses, networks, etc. may imply Figure 1 STAs 110 and 120 of Figure 1 For example, devices such as (but without specific labels) (transmitting / receiving) STAs, first STAs, second STAs, STA1, STA2, APs, first APs, second APs, AP1, AP2, (transmitting / receiving) terminals, (transmitting / receiving) devices, (transmitting / receiving) apparatuses, networks, etc. may imply Figure 1 STAs 110 and 120 of Figure 1 For example, in the following examples, operations for various STAs to transmit / receive signals (e.g., PPDUs) may be performed in Figure 1 transceivers 113 and 123 of

[0075] Figure 1 The aforementioned device / STA in sub - figure (a) of Figure 1 may be modified as shown in sub - figure (b) of Figure 1 In the following, STAs 110 and STA120 of this specification will be described based on

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

[0077] The mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, user, user STA, network, base station, Node B, access point (AP), repeater, router, repeater, receiving unit, transmitting unit, receiving STA, transmitting STA, receiving device, transmitting device, receiving means and / or transmitting means described below can mean Figure 1 the STAs 110 and 120 shown in sub - figure (a) / (b) of Figure 1 , or can mean Figure 1 the processing chips 114 and 124 shown in sub - figure (b) of Figure 1 . That is, the technical features of this specification can be executed in the STAs 110 and 120 shown in sub - figure (a) / (b) of Figure 1 , or can be executed only in the processing chips 114 and 124 shown in sub - figure (b) of Figure 1 the transceivers 113 and 123 shown in sub - figure (a) / (b) of Figure 1 . For example, the technical feature that the transmitting STA transmits a control signal can be understood as the technical feature of transmitting, by the transceiver 113 shown in sub - figure (a) / (b) of Figure 1 , the control signal generated in the processors 111 and 121 shown in sub - figure (a) / (b) of

[0078] . Alternatively, the technical feature that the transmitting STA transmits a control signal can be understood as the technical feature of generating, in the processing chips 114 and 124 shown in sub - figure (b) of Figure 1 , the control signal to be transmitted to the transceivers 113 and 123. Figure 1 For example, the technical feature that the receiving STA receives a control signal can be understood as the technical feature of receiving the control signal through the transceivers 113 and 123 shown in sub - figure (a) of Figure 1The technical features of the control signals received by transceivers 113 and 123 shown in sub - figure (a). Alternatively, the technical features of the control signals received by the receiving STA can be understood as obtained by Figure 1 processing chips 114 and 124 shown in sub - figure (b) of Figure 1 The technical features of the control signals received by transceivers 113 and 123 shown in sub - figure (b).

[0079] Reference Figure 1 Regarding sub - figure (b) of , software codes 115 and 125 can be included in memories 112 and 122. Software codes 115 and 125 can include instructions for controlling the operations of processors 111 and 121. Software codes 115 and 125 can be included in various programming languages.

[0080] Figure 1 The processors 111 and 121 or processing chips 114 and 124 of can include application - specific integrated circuits (ASICs), other chip sets, logic circuits, and / or data processing devices. The processor can be an application processor (AP). For example, Figure 1 The processors 111 and 121 or processing chips 114 and 124 of can include at least one of the following: digital signal processors (DSPs), central processing units (CPUs), graphics processing units (GPUs), and modulators and demodulators (modems). For example, Figure 1 The processors 111 and 121 or processing chips 114 and 124 of can be the SNAPDRAGONTM processor series manufactured by the EXYNOSTM processor series manufactured by the processor series manufactured by the HELIOTM processor series manufactured by the ATOMTM processor series manufactured by or processors enhanced from these processors.

[0081] In this specification, the uplink can mean a link for communication from a non - AP STA to an SP STA, and uplink PPDUs / packets / signals, etc. can be sent through the uplink. Additionally, in this specification, the downlink can mean a link for communication from an AP STA to a non - AP STA, and downlink PPDUs / packets / signals, etc. can be sent through the downlink.

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

[0083] Figure 2The upper part shows the structure of an infrastructure basic service set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11.

[0084] Reference Figure 2 In the upper part, a wireless LAN system may include one or more infrastructure BSSs 200 and 205 (hereinafter referred to as BSSs). BSSs 200 and 205, which are a set of APs and STAs (e.g., access point (AP) 225 and station (STA1) 200-1) that have successfully synchronized to communicate with each other, are not a concept indicating a specific area. BSS 205 may include one or more STAs 205-1 and 205-2 that can be associated with one AP 230.

[0085] A BSS may include at least one STA, an AP that provides distributed services, and a distribution system (DS) 210 that connects multiple APs.

[0086] The distribution system 210 may implement an extended service set (ESS) 240 that is extended by connecting multiple BSSs 200 and 205. The ESS 240 can be used as a term indicating a network configured by connecting one or more APs 225 or 230 via the distribution system 210. The APs included in one ESS 240 may have the same service set identifier (SSID).

[0087] The portal 220 may be used as a bridge to connect a wireless LAN network (IEEE 802.11) and another network (e.g., 802.X).

[0088] In Figure 2 In the BSS shown in the upper part, a network between APs 225 and 230 and a network between APs 225 and 230 and STAs 200-1, 205-1, and 205-2 can be implemented. However, a network is configured between STAs to perform communication even in the absence of APs 225 and 230. A network that performs communication by configuring a network between STAs even in the absence of APs 225 and 230 is defined as an ad hoc network or an independent basic service set (IBSS).

[0089] Figure 2 The lower part shows a conceptual diagram illustrating an IBSS.

[0090] Reference Figure 2At the lower part of, an IBSS is a BSS operating in the ad - hoc mode. Since the IBSS does not include an access point (AP), there is no centralized management entity that performs management functions at the center. That is, in the IBSS, STAs 250 - 1, 250 - 2, 250 - 3, 255 - 4, and 255 - 5 are managed in a distributed manner. In the IBSS, all STAs 250 - 1, 250 - 2, 250 - 3, 255 - 4, and 255 - 5 can be composed of mobile STAs and are not allowed to access the DS to form a self - contained network.

[0091] Figure 3 The figure shows a general link establishment process.

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

[0093] Figure 3 The figure shows a network discovery operation including an active scanning process. In active scanning, the STA performing the scanning sends a probe request frame and waits for a response to the probe request frame to identify which APs exist around while moving to channels. The responder sends a probe response frame to the STA that has sent the probe request frame as a response to the probe request frame. Here, the responder can be the STA that sent the last beacon frame in the BSS of the channel being scanned. In the BSS, since the AP sends the beacon frame, the AP is the responder. In the IBSS, since the STAs in the IBSS send beacon frames in turn, the responder is not fixed. For example, when the STA sends a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA can store the BSS - related information included in the received probe response frame, move to the next channel (e.g., channel 2), and can perform scanning by the same method (e.g., send a probe request and receive a probe response via channel 2).

[0094] Although Figure 3is not shown and the scanning can be performed by a passive scanning method. In the passive scanning, the STA performing the scanning can wait for beacon frames while moving to channels. A beacon frame is one of the management frames in IEEE 802.11 and is periodically transmitted to indicate the existence of a wireless network and enable the STA performing the scanning to find and join the wireless network. In a BSS, an AP is used to periodically transmit beacon frames. In an IBSS, the STAs in the IBSS take turns to transmit beacon frames. When receiving a beacon frame, the STA performing the scanning 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. The STA that receives the 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 by the same method.

[0095] After discovering the network, the STA can perform an authentication process in S320. This authentication process can be referred to as the first authentication process to clearly distinguish it from the security establishment operation in S340 subsequently. The authentication process in S320 can include the process of the STA sending an authentication request frame to the AP and the AP sending an authentication response frame to the STA as a response. The authentication frame for authentication request / response is a management frame.

[0096] The authentication frame can include information about the authentication algorithm number, authentication transaction sequence number, status code, challenge text, Robust Security Network (RSN), and finite cyclic group.

[0097] The STA can send an authentication request frame to the AP. The AP can determine whether to allow the authentication of the STA based on the information included in the received authentication request frame. The AP can provide the authentication processing result to the STA via the authentication response frame.

[0098] When the STA is successfully authenticated, the STA can perform an association process in S330. The association process includes the process of the STA sending an association request frame to the AP and the AP sending an association response frame to the STA as a response. For example, the association request frame can include information about various capabilities, beacon listening interval, Service Set Identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operation classes, Traffic Indication Map (TIM) broadcast request, and interworking service capabilities. For example, the association response frame can include information about various capabilities, status code, Association ID (AID), supported rates, Enhanced Distributed Channel Access (EDCA) parameter set, Received Channel Power Indicator (RCPI), Received Signal-to-Noise Ratio Indicator (RSNI), mobility domain, timeout interval (association recovery time), overlapping BSS scan parameters, TIM broadcast response, and QoS map.

[0099] In S340, the STA can perform security establishment processing. The security establishment processing in S340 can include processing for establishing a private key through a four-way handshake (e.g., through Extensible Authentication Protocol over LAN (EAPOL) frames).

[0100] Figure 4 Illustrates an example of a PPDU used in the IEEE standard.

[0101] As shown, various types of Physical Layer Protocol Data Units (PPDUs) are used in the IEEE a / g / n / ac standards. Specifically, the LTF and STF include training signals, SIG-A and SIG-B include control information for the receiving STA, and the data field includes user data corresponding to the PSDU (MAC PDU / aggregated MAC PDU).

[0102] Figure 4 Also includes an example of a HE PPDU according to IEEE 802.11ax. According to Figure 4 the HE PPDU is an exemplary PPDU for multiple users. HE-SIG-B may be included only in the PPDU for multiple users, and HE-SIG-B may be omitted in the PPDU for a single user.

[0103] As Figure 4 illustrated, the HE-PPDU for multiple users (MU) may include a legacy short training field (L-STF), a legacy long training field (L-LTF), a legacy signal (L-SIG), a high efficiency signal A (HE-SIG A), a high efficiency signal B (HE-SIGB), a high efficiency short training field (HE-STF), a high efficiency long training field (HE-LTF), a data field (alternatively, MAC payload), and a packet extension (PE) field. Each field may be transmitted within the indicated time period (i.e., 4 or 8 μs).

[0104] Next, the resource unit (RU) for the PPDU is described. The RU may include multiple subcarriers (or tones). The RU can be used to send signals to multiple STAs according to OFDMA. In addition, the RU can also be defined to send signals to one STA. The RU can be used for the STF, LTF, data field, etc.

[0105] Figure 5 Illustrates the layout of the resource unit (RU) used in a 20 MHz frequency band.

[0106] As Figure 5As shown, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) can be used to form some fields of the HE-PPDU. For example, resources can be allocated for the HE-STF, HE-LTF, and data fields in the illustrated RUs.

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

[0108] Figure 5 The layout of the RUs in [] can be used not only for multiple users (MUs) but also for a single user (SU). In this case, one 242-unit can be used and three DC tones can be inserted, as Figure 5 shown at the bottom.

[0109] Although Figure 5 RUs of various sizes are proposed, i.e., 26-RU, 52-RU, 106-RU, and 242-RU, the size of a specific RU can be extended or increased. Therefore, this embodiment is not limited to each RU of a specific size (i.e., the number of corresponding tones).

[0110] Figure 6 Illustrates the layout of the RUs used in a 40 MHz band.

[0111] Similar to [] using RUs of various sizes, Figure 5 in Figure 6 's example, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. can be used. In addition, five DC tones can be inserted at the center frequency, 12 tones can be used for the guard band in the leftmost band of the 40 MHz band, and 11 tones can be used for the guard band in the rightmost band of the 40 MHz band.

[0112] As Figure 6 shown, when the layout of the RUs is used for a single user, 484-RU can be used. The specific number of RUs can be changed similar to Figure 5 '.

[0113] Figure 7 Illustrates the layout of the RUs used in an 80 MHz band.

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

[0115] As Figure 7 shown, when the layout of the RU is for a single user, 996-RU can be used, and in this case, five DC tones can be inserted.

[0116] The RUs described in this specification can be used in uplink (UL) communication and downlink (DL) communication. For example, when performing UL-MU communication through a trigger frame request, the transmitting STA (e.g., AP) can allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA through the trigger frame, and can allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. Thereafter, the first STA can send a first trigger-based PPDU based on the first RU, and the second STA can send a second trigger-based PPDU based on the second RU. The first / second trigger-based PPDUs are sent to the AP in the same (or overlapping) time period.

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

[0118] Information related to the layout of the RU can be signaled through HE-SIG-B.

[0119] Figure 8 Illustrate the structure of the HE-SIG-B field.

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

[0121] As Figure 8 shown, the common field 820 and the user-specific field 830 may be encoded separately.

[0122] The common field 820 may include N*8-bit RU allocation information. For example, the RU allocation information may include information related to the position of the RU. For example, when using a 20 MHz channel as Figure 5 shown, the RU allocation information may include information related to a specific frequency band where a specific RU (26-RU / 52-RU / 106-RU) is arranged.

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

[0124] [Table 1]

[0125]

[0126] As Figure 5 shown in the example, up to nine 26-RUs can be allocated to a 20 MHz channel. When the RU allocation information of the common field 820 is set to "00000000" as shown in Table 1, nine 26-RUs can be allocated to the corresponding channel (i.e., 20 MHz). Additionally, when the RU allocation information of the common field 820 is set to "00000001" as shown in Table 1, seven 26-RUs and one 52-RU are arranged in the corresponding channel. That is, in Figure 5 the example, the 52-RU can be allocated to the rightmost side, and seven 26-RUs can be allocated to its left.

[0127] The example of Table 1 only shows some RU positions where the RU allocation information can be displayed.

[0128] For example, the RU allocation information may include the example in Table 2 below.

[0129] [Table 2]

[0130]

[0131] "01000y2y1y0" involves an example of allocating 106 - RUs to the left - most part of a 20 - MHz channel and five 26 - RUs to its right. In this case, multiple STAs (e.g., user STAs) can be allocated to the 106 - RUs based on the MU - MIMO scheme. Specifically, up to 8 STAs (e.g., user STAs) can be allocated to the 106 - RUs, and the number of STAs (e.g., user STAs) allocated to the 106 - RUs is determined based on 3 - bit information (y2y1y0). For example, when the 3 - bit information (y2y1y0) is set to N, the number of STAs (e.g., user STAs) allocated to the 106 - RUs based on the MU - MIMO scheme can be N + 1.

[0132] Generally, multiple STAs (e.g., user STAs) that are different from each other can be allocated to multiple RUs. However, multiple STAs (e.g., user STAs) can be allocated to one or more RUs with at least a specific size (e.g., 106 sub - carriers) based on the MU - MIMO scheme.

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

[0134] For example, when the RU allocation is set to "01000y2y1y0", multiple STAs can be allocated to the 106 - RUs arranged on the left - most side through the MU - MIMO scheme, and five user STAs can be allocated to the five 26 - RUs arranged on its right through the non - MU MIMO scheme. This case is illustrated by Figure 9 the example of.

[0135] Figure 9 The figure shows an example of allocating multiple user STAs to the same RU through the MU - MIMO scheme.

[0136] For example, when as Figure 9When the RU allocation shown is set to "01000010", 106 - RU can be allocated to the leftmost side of a specific channel, and five 26 - RUs can be allocated to its right side. Additionally, three user STAs can be allocated to the 106 - RU through the MU - MIMO scheme. As a result, since eight user STAs are allocated, the user - specific field 830 of HE - SIG - B can include eight user fields.

[0137] The eight user fields can be represented in Figure 9 the order shown. Additionally, as Figure 8 shown, two user fields can be implemented using one user - block field.

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

[0139] Each user field can have the same size (e.g., 21 bits). For example, the user field of the first format (the first MU - MIMO scheme) can be configured as follows.

[0140] For example, the first bit (i.e., B0 - B10) in the user field (i.e., 21 bits) can include the identification information (e.g., STA - ID, partial AID, etc.) of the user STA to which the corresponding user field is allocated. Additionally, the second bit (i.e., B11 - B14) in the user field (i.e., 21 bits) can include information related to the spatial configuration. Specifically, examples of the second bit (i.e., B11 - B14) can be as shown in Table 3 and Table 4 below.

[0141] [Table 3]

[0142]

[0143] [Table 4]

[0144]

[0145] As shown in Table 3 and / or Table 4, the second bit (e.g., B11 - B14) can include information related to the number of spatial streams allocated to multiple user STAs allocated based on the MU - MIMO scheme. For example, when as Figure 9When three user STAs are assigned to 106-RU based on the MU-MIMO scheme as shown, N_user is set to "3". Therefore, the values of N_STS[1], N_STS[2], and N_STS[3] can be determined as shown in Table 3. For example, when the value of the second bit (B11 - B14) is "0011", it can be set that N_STS[1]=4, N_STS[2]=1, N_STS[3]=1. That is, in Figure 9 the example of, four spatial streams can be allocated to user field 1, one spatial stream can be allocated to user field 1, and one spatial stream can be allocated to user field 3.

[0146] As shown in the examples of Table 3 and / or Table 4, the information related to the number of spatial streams for the user STA (i.e., the second bit, B11 - B14) can be composed of 4 bits. Additionally, the information related to the number of spatial streams for the user STA (i.e., the second bit, B11 - B14) can support up to eight spatial streams. Additionally, the information related to the number of spatial streams for the user STA (i.e., the second bit, B11 - B14) can support up to four spatial streams for one user STA.

[0147] Additionally, the third bit (i.e., B15 - 18) in the user field (i.e., 21 bits) can include modulation and coding scheme (MCS) information. The MCS information can be applied to the data field in the PPDU including the corresponding SIG-B.

[0148] The MCS, MCS information, MCS index, MCS field, etc. used in this specification can be indicated by index values. For example, the MCS information can be indicated by index 0 to index 11. The MCS information can include information related to the constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information related to the coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6e, etc.). Information related to the channel coding type (e.g., LCC or LDPC) may not be included in the MCS information.

[0149] Additionally, the fourth bit (i.e., B19) in the user field (i.e., 21 bits) can be a reserved field.

[0150] Additionally, the fifth bit (i.e., B20) in the user field (i.e., 21 bits) can include information related to the coding type (e.g., BCC or LDPC). That is, the fifth bit (i.e., B20) can include information related to the type of channel coding (e.g., BCC or LDPC) applied to the data field in the PPDU including the corresponding SIG-B.

[0151] The above example relates to the user field of the first format (the format of the MU-MIMO scheme). Examples of the user field of the second format (the format of the non-MU-MIMO scheme) are as follows.

[0152] The first bits (e.g., B0 - B10) in the user field of the second format may include identification information of the user STA. Additionally, the second bits (e.g., B11 - B13) in the user field of the second format may include information related to the number of spatial streams applied to the corresponding RU. Additionally, the third bits (e.g., B14) in the user field of the second format may include information related to whether a beamforming steering matrix is applied. The fourth bits (e.g., B15 - B18) in the user field of the second format may include modulation and coding scheme (MCS) information. Additionally, the fifth bits (e.g., B19) in the user field of the second format may include information related to whether dual-carrier modulation (DCM) is applied. Additionally, the sixth bits (i.e., B20) in the user field of the second format may include information related to the coding type (e.g., BCC or LDPC).

[0153] Figure 10 Illustrates UL-MU-based operation. As shown, the transmitting STA (e.g., AP) may perform channel access through contention (e.g., backoff operation) and may send a trigger frame 1030. That is, the transmitting STA may send a PPDU including the trigger frame 1030. Upon receiving a PPDU including the trigger frame, a trigger-based (TB) PPDU is sent after a delay corresponding to the SIFS.

[0154] TB PPDUs 1041 and 1042 may be sent in the same time period and may be sent from multiple STAs (e.g., user STAs) having the AID indicated in the trigger frame 1030. The ACK frame 1050 for the TB PPDU may be implemented in various forms.

[0155] Reference Figures 11 to 13 Describes the specific features of the trigger frame. Even when using UL-MU communication, an orthogonal frequency division multiple access (OFDMA) scheme or a MU MIMO scheme may be used, and the OFDMA and MU-MIMO schemes may be used simultaneously.

[0156] Figure 11 Illustrates an example of the trigger frame. Figure 11 The trigger frame allocates resources for uplink multi-user (MU) transmission and may be sent, for example, from the AP. The trigger frame may be configured by a MAC frame and may be included in the PPDU.

[0157] Figure 11Each of the fields shown may be partially omitted, and another field may be added. Additionally, the length of each field may be changed to be different from that shown in the figure.

[0158] Figure 11 The frame control field 1110 of Figure 11 may include information related to the MAC protocol version and additional control information. The duration field 1120 may include time information for NAV configuration or information related to the identifier of the STA (e.g., AID).

[0159] Additionally, the RA field 1130 may include the address information of the receiving STA of the corresponding trigger frame and may optionally be omitted. The TA field 1140 may include the address information of the STA (e.g., AP) that sends the corresponding trigger frame. The common information field 1150 includes common control information applied to the receiving STA that receives the corresponding trigger frame. For example, it may include a field indicating the length of the L-SIG field of the uplink PPDU transmitted in response to the corresponding trigger frame or information for controlling the content of the SIG-A field (i.e., HE-SIG-A field) of the uplink PPDU transmitted in response to the corresponding trigger frame. Additionally, as common control information, it may include information related to the length of the CP of the uplink PPDU transmitted in response to the corresponding trigger frame or information related to the length of the LTF field.

[0160] Additionally, it is preferably included with the receiving Figure 11 per-user information fields 1160#1 to 1160#N corresponding to the number of receiving STAs of the trigger frame. The per-user information field may also be referred to as the "allocation field".

[0161] Additionally, Figure 11 the trigger frame of

[0161] may include a padding field 1170 and a frame check sequence field 1180.

[0162] Figure 11 Each of the per-user information fields 1160#1 to 1160#N shown may include multiple sub-fields.

[0163] Figure 12 An example of the common information field of the illustrated trigger frame. Figure 12 The sub-fields of Figure 12 may be partially omitted, and additional sub-fields may be added. Additionally, the length of each of the shown sub-fields may be changed.

[0164] The length field 1210 shown has the same value as the length field of the L-SIG field of the uplink PPDU transmitted in response to the corresponding trigger frame, and the length field of the L-SIG field of the uplink PPDU indicates the length of the uplink PPDU. As a result, the length field 1210 of the trigger frame can be used to indicate the length of the corresponding uplink PPDU.

[0165] In addition, the cascade identifier field 1220 indicates whether a cascade operation is performed. The cascade operation means that the downlink MU transmission and the uplink MU transmission are performed together in the same TXOP. That is, it means that the downlink MU transmission is performed, and then the uplink MU transmission is performed after a preset time (e.g., SIFS). During the cascade operation, only one transmitting device (e.g., an AP) can perform downlink communication, and multiple transmitting devices (e.g., non-APs) can perform uplink communication.

[0166] The CS request field 1230 indicates whether the wireless medium status or NAV, etc. must be considered when the receiving device that receives the corresponding trigger frame sends the corresponding uplink PPDU.

[0167] The HE-SIG-A information field 1240 may include information for controlling the content of the SIG-A field (i.e., the HE-SIG-A field) of the uplink PPDU in response to the corresponding trigger frame.

[0168] The CP and LTF type field 1250 may include information related to the CP length and the LTF length of the uplink PPDU transmitted in response to the corresponding trigger frame. The trigger type field 1260 may indicate the purpose of using the corresponding trigger frame, such as a typical trigger, a trigger for beamforming, a request for block ACK / NACK, etc.

[0169] It may be assumed that the trigger type field 1260 of the trigger frame in this specification indicates a trigger frame of a basic type for a typical trigger. For example, a trigger frame of a basic type may be referred to as a basic trigger frame.

[0170] Figure 13 Illustrate an example of the subfields included in the per-user information field. Figure 13 The user information field 1300 may be understood as any one of the per-user information fields 1160#1 to 1160#N mentioned above with reference to Figure 11 The subfields included in the user information field 1300 may be partially omitted, and additional subfields may be added. In addition, the lengths of the respective subfields shown may be changed. Figure 13 The user identifier field 1310 indicates the identifier of the STA (i.e., the receiving STA) corresponding to the per-user information. An example of the identifier may be all or part of the association identifier (AID) value of the receiving STA.

[0171] Figure 13

[0172] ​Additionally, an RU allocation field 1320 may be included. That is, when the receiving STA identified by the user identifier field 1310 sends a TB PPDU in response to a trigger frame, the TB PPDU is sent using the RU indicated by the RU allocation field 1320. In this case, the RU indicated by the RU allocation field 1320 may be Figure 5 , Figure 6 and Figure 7 the RUs shown.

[0173] Figure 13 The subfield of

[0173] Figure 13 may include a coding type field 1330. The coding type field 1330 may indicate the coding type of the TB PPDU. For example, when BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to "1", and when LDPC coding is applied, the coding type field 1330 may be set to "0".

[0174] Additionally, Figure 13 the subfield of Figure 13 may include an MCS field 1340. The MCS field 1340 may indicate the MCS scheme applied to the TB PPDU. For example, when BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to "1", and when LDPC coding is applied, the coding type field 1330 may be set to "0".

[0175] Hereinafter, a random access based on UL OFDMA (UORA) scheme will be described.

[0176] Figure 14 Describe the technical features of the UORA scheme.

[0177] The transmitting STA (e.g., an AP) may allocate six RU resources through a trigger frame as shown in Figure 14 . Specifically, the AP may allocate the 1st RU resource (AID 0, RU 1), the 2nd RU resource (AID 0, RU 2), the 3rd RU resource (AID 0, RU 3), the 4th RU resource (AID 2045, RU 4), the 5th RU resource (AID 2045, RU 5), and the 6th RU resource (AID 3, RU 6). Information related to AID 0, AID 3, or AID 2045 may be included in, for example, Figure 13 the user identifier field 1310. Information related to RUs 1 to 6 may be included in, for example, Figure 13 the RU allocation field 1320. AID = 0 may mean the UORA resource for an associated STA, and AID = 2045 may mean the UORA resource for a non-associated STA. Therefore, Figure 14 the 1st to 3rd RU resources of Figure 14 can be used as UORA resources for an associated STA,Figure 14 The 4th RU resource and the 5th RU resource of Figure 14 can be used as UORA resources for non-associated STAs, and the 6th RU resource of

[0178] In Figure 14 the example of , the OFDMA random access backoff (OBO) of STA1 is reduced to 0, and STA1 randomly selects the 2nd RU resource (AID 0, RU 2). Additionally, since the OBO counters of STA2 / 3 are greater than 0, uplink resources are not allocated to STA2 / 3. Additionally, regarding Figure 14 STA4 in , since the AID of STA4 (e.g., AID = 3) is included in the trigger frame, the resource of RU 6 is allocated without backoff.

[0179] Specifically, since Figure 14 STA1 of is an associated STA, the total number of eligible RA RUs for STA1 is 3 (RU1, RU 2, and RU 3), so STA1 decrements the OBO counter by 3 to make the OBO counter become 0. Additionally, since Figure 14 STA2 of is an associated STA, the total number of eligible RA RUs for STA2 is 3 (RU 1, RU 2, and RU 3), so STA2 decrements the OBO counter by 3, but the OBO counter is greater than 0. Additionally, since Figure 14 STA3 of is a non-associated STA, the total number of eligible RA RUs for STA3 is 2 (RU 4, RU 5), so STA3 decrements the OBO counter by 2, but the OBO counter is greater than 0.

[0180] Figure 15 The figure shows an example of channels used / supported / defined within the 2.4 GHz band.

[0181] The 2.4 GHz band can be referred to by other terms such as the first band. Additionally, the 2.4 GHz band can mean the frequency domain that uses / supports / defines channels with a center frequency close to 2.4 GHz (e.g., channels with a center frequency within 2.4 to 2.5 GHz).

[0182] Multiple 20 MHz channels can be included in the 2.4 GHz band. The 20 MHz within 2.4 GHz can have multiple channel indices (e.g., index 1 to index 14). For example, the center frequency of the 20 MHz channel assigned with channel index 1 can be 2.412 GHz, the center frequency of the 20 MHz channel assigned with channel index 2 can be 2.417 GHz, and the center frequency of the 20 MHz channel assigned with channel index N can be (2.407 + 0.005 * N) GHz. The channel index can be referred to by various terms such as channel number. The specific values of the channel index and the center frequency can be changed.

[0183] Figure 15 Four channels within the 2.4 GHz band are exemplified. Each of the first to fourth frequency domains 1510 to 1540 shown herein can include one channel. For example, the first frequency domain 1510 can include channel 1 (the 20 MHz channel with index 1). In this case, the center frequency of channel 1 can be set to 2412 MHz. The second frequency domain 1520 can include channel 6. In this case, the center frequency of channel 6 can be set to 2437 MHz. The third frequency domain 1530 can include channel 11. In this case, the center frequency of channel 11 can be set to 2462 MHz. The fourth frequency domain 1540 can include channel 14. In this case, the center frequency of channel 14 can be set to 2484 MHz.

[0184] Figure 16 An example of channels used / supported / defined within the 5 GHz band is illustrated.

[0185] The 5 GHz band can be referred to by other terms such as the second band. The 5 GHz band can mean a frequency domain that uses / supports / defines channels with a center frequency greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz). Alternatively, the 5 GHz band can include multiple channels between 4.5 GHz and 5.5 GHz. Figure 16 The specific values shown can be changed.

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

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

[0188] Figure 17 The figure shows an example of channels used / supported / defined within the 6 GHz band.

[0189] The 6 GHz band can be referred to by other terms such as the third band, etc. The 6 GHz band can mean the frequency domain that uses / supports / defines channels with a center frequency greater than or equal to 5.9 GHz. Figure 17 The specific values shown can be changed.

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

[0191] Therefore, Figure 17 the index (or channel number) of the 2 MHz channel can be 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, 201, 205, 209, 213, 217, 221, 225, 229, 233. Additionally, according to the above (5.940 + 0.005 * N) GHz rule, Figure 17The indices of the 40 MHz channels can be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.

[0192] Although FIGS. 20, 40, 80, and 160 MHz channels are illustrated in the examples of Figure 17 240 MHz channels or 320 MHz channels can be additionally added.

[0193] Hereinafter, the PPDUs transmitted / received in the STA of the present specification will be described.

[0194] Figure 18 Illustrate an example of the PPDU used in the present specification.

[0195] Figure 18 The PPDUs of

[0196] Figure 18 can be referred to by various terms such as EHT PPDU, TX PPDU, RX PPDU, the first type, or the Nth type of PPDU. For example, in the present specification, the PPDU or EHT PPDU can be referred to by various terms such as TX PPDU, RX PPDU, the first type, or the Nth type of PPDU. Additionally, the EHT PPDU can be used in the EHT system and / or the new WLAN system enhanced from the EHT system. Figure 18 The examples of Figure 18 can be used for both single-user (SU) mode and multi-user (MU) mode. In other words, Figure 18 the PPDUs of Figure 18 can be PPDUs for one receiving STA or multiple receiving STAs. When Figure 18 the PPDUs of

[0197] In Figure 18 L-STF to EHT-LTF can be referred to as the preamble or physical preamble and can be generated / transmitted / received / acquired / decoded in the physical layer.

[0198] It is possible to Figure 18The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields is determined to be 312.5 kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF, and data fields can be determined to be 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields can be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and data fields can be expressed in units of 78.125 kHz.

[0199] In Figure 18 the PPDU of, the L-LTF and L-STF can be the same as those in the conventional fields.

[0200] Figure 18 The L-SIG field of can include, for example, 24-bit bit information. For example, the 24-bit information can 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 can include information related to the length or duration of the PPDU. For example, the 12-bit length field can be determined based on the type of the PPDU. For example, when the PPDU is a non-HT, HT, VHT PPDU, or EHT PPDU, the value of the length field can be determined to be a multiple of 3. For example, when the PPDU is a HE PPDU, the length field can be determined to be "a multiple of 3" + 1 or "a multiple of 3" + 2. In other words, for a non-HT, HT, VHT PPDU, or EHT PPDU, the value of the length field can be determined to be a multiple of 3, and for a HE PPDU, the value of the length field can be determined to be "a multiple of 3" + 1 or "a multiple of 3" + 2.

[0201] For example, the transmitting STA can apply BCC encoding with a 1 / 2 coding rate to the 24-bit information in the L-SIG field. Thereafter, the transmitting STA can obtain 48 BCC-encoded bits. BPSK modulation can be applied to the 48 encoded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions other than the pilot subcarriers {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols can be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can additionally map the signal {-1, -1, -1, 1} to subcarrier indices {-28, -27, +27, +28}. The foregoing signal can be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

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

[0203] The Universal SIG (U-SIG) can be inserted after Figure 18 the RL-SIG. The U-SIG can be referred to by various terms such as the first SIG field, the first SIG, the first type of SIG, the control signal, the control signal field, the first (type) control signal, etc.

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

[0205] With the U-SIG (or U-SIG field), for example, A bits of information (e.g., 52 uncoded bits) can be sent. The first symbol of the U-SIG can send the first X bits of information of the A bits of information (e.g., 26 uncoded bits), and the second symbol of the U-SIG can send the remaining Y bits of information of the A bits of information (e.g., 26 uncoded bits). For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional coding (i.e., BCC coding) at a rate of R = 1 / 2 to generate 52 coded bits, and can perform interleaving on the 52 coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols to be assigned to each U-SIG symbol. Except for the DC index 0, one U-SIG symbol can be sent based on 65 tones (subcarriers) from subcarrier index -28 to subcarrier index +28. The 52 BPSK symbols generated by the transmitting STA can be sent based on the remaining tones (subcarriers) except for the pilot tones, i.e., tones -21, -7, +7, +21.

[0206] For example, the A bits of information (e.g., 52 uncoded bits) generated by the U-SIG can include a CRC field (e.g., a field with a length of 4 bits) and a tail field (e.g., a field with a length of 6 bits). The CRC field and the tail field can be sent by the second symbol of the U-SIG. The CRC field can be generated based on the 26 bits assigned to the first symbol of the U-SIG and the remaining 16 bits in the second symbol except for the CRC / tail field, and can be generated based on a conventional CRC calculation algorithm. Additionally, the tail field can be used to terminate the trellis of the convolutional decoder and can be set to, for example, "000000".

[0207] The A bits of information (e.g., 52 uncoded bits) sent by the U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the version-independent bits can have a fixed or variable size. For example, the version-independent bits can be assigned only to the first symbol of the U-SIG, or the version-independent bits can be assigned to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be referred to in various terms such as the first control bit, the second control bit, etc.

[0208] 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 TX / RX PPDU. For example, the first value of the 3 - bit PHY version identifier may indicate that the TX / RX PPDU is an EHT PPDU. In other words, when the transmitting STA sends an EHT PPDU, the 3 - bit PHY version identifier can be set to the first value. In other words, the receiving STA can determine that the RX PPDU is an EHT PPDU based on the PHY version identifier having the first value.

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

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

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

[0212] For example, U - SIG may include: 1) a bandwidth field including information related to the bandwidth; 2) a field including information related to the MCS scheme applied to the EHT - SIG; 3) an indication field including information related to whether the dual - carrier modulation (DCM) scheme is applied to the EHT - SIG; 4) a field including information related to the number of symbols for the EHT - SIG; 5) a field including information related to whether the EHT - SIG is generated across the entire frequency band; 6) a field including information related to the type of the EHT - LTF / STF; and 7) information related to the field indicating the EHT - LTF length and the CP length.

[0213] Preamble punching can be applied to the Figure 18 PPDU. Preamble punching means that punching is applied to a part of the entire frequency band (e.g., the secondary 20 - MHz band). For example, when transmitting an 80 - MHz PPDU, the STA can apply punching to the secondary 20 - MHz band in the 80 - MHz frequency band and can transmit the PPDU only through the primary 20 - MHz band and the secondary 40 - MHz band.

[0214] For example, the pattern of preamble perforation can be pre-configured. For example, when applying the first perforation pattern, perforation can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when applying the second perforation pattern, perforation can be applied only to any one of the two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when applying the third perforation pattern, perforation can be applied only to the secondary 20 MHz band in the primary 80 MHz band included in the 160 MHz band (or 80 + 80 MHz band). For example, when applying the fourth perforation pattern, perforation can be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band when the primary 40 MHz band exists in the 80 MHz band included in the 160 MHz band (or 80 + 80 MHz band).

[0215] Information related to the preamble perforation applied to the PPDU can be included in the U-SIG and / or EHT-SIG. For example, the first field of the U-SIG can include information related to the contiguous bandwidth, and the second field of the U-SIG can include information related to the preamble perforation applied to the PPDU.

[0216] For example, based on the following method, the U-SIG and EHT-SIG can include information related to preamble perforation. When the bandwidth of the PPDU exceeds 80 MHz, the U-SIG can be configured individually in units of 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU can 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 can include information related to the 160 MHz bandwidth, and the second field of the first U-SIG can include information related to the preamble perforation applied to the first 80 MHz band (i.e., information related to the preamble perforation pattern). Additionally, the first field of the second U-SIG can include information related to the 160 MHz bandwidth, and the second field of the second U-SIG can include information related to the preamble perforation applied to the second 80 MHz band (i.e., information related to the preamble perforation pattern). Meanwhile, the EHT-SIG contiguous to the first U-SIG can include information related to the preamble perforation applied to the second 80 MHz band (i.e., information related to the preamble perforation pattern), and the EHT-SIG contiguous to the second U-SIG can include information related to the preamble perforation applied to the first 80 MHz band (i.e., information related to the preamble perforation pattern).

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

[0218] The U-SIG can be configured in units of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG can be replicated. That is, four identical U-SIGs can be included in the 80 MHz PPDU. A PPDU with a bandwidth exceeding 80 MHz can include different U-SIGs.

[0219] The U-SIG can be configured in units of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG can be replicated. That is, four identical U-SIGs can be included in the 80 MHz PPDU. A PPDU with a bandwidth exceeding 80 MHz can include different U-SIGs.

[0220] Figure 18 The EHT-SIG in [ ] can include control information for the receiving STA. The EHT-SIG can be transmitted through at least one symbol, and one symbol can have a length of 4 μs. Information related to the number of symbols for the EHT-SIG can be included in the U-SIG.

[0221] The EHT-SIG can include references Figure 8 and Figure 9 the technical features of the HE-SIG-B described. For example, the EHT-SIG can include common fields and user-specific fields as in the example in Figure 8 The common fields of the EHT-SIG can be omitted, and the number of user-specific fields can be determined based on the number of users.

[0222] As in the example in Figure 8 the common fields of the EHT-SIG and the user-specific fields of the EHT-SIG can be encoded separately. One user block field included in the user-specific fields can include information for two users, but the last user block field included in the user-specific fields can include information for one user. That is, one user block field of the EHT-SIG can include up to two user fields. As in the example in Figure 9 each user field can be related to MU-MIMO allocation or can be related to non-MU-MIMO allocation.

[0223] As in the example inFigure 8 In the example of, the common fields of the EHT-SIG may include CRC bits and tail bits. The length of the CRC bits may be determined to be 4 bits. The length of the tail bits may be determined to be 6 bits and may be set to "000000".

[0224] As in Figure 8 In the example of, the common fields of the EHT-SIG may include RU allocation information. The RU allocation information may refer to information related to the positions of the RUs to which multiple users (i.e., multiple receiving STAs) are allocated. The RU allocation information may be configured in units of 8 bits (or N bits), as shown in Table 1.

[0225] The examples in Tables 5 to 7 are examples of 8-bit (or N-bit) information for various RU allocations. The indexes shown in each table may be modified, and some entries in Tables 5 to 7 may be omitted, and entries (not shown) may be added.

[0226] The examples in Tables 5 to 7 relate to information related to the positions of the RUs allocated to the 20 MHz band. For example, "Index 0" in Table 5 may be used in the case of separately allocating nine 26-RUs (e.g., in the case of separately allocating the nine 26-RUs shown in Figure 5 .

[0227] In addition, multiple RUs may be allocated to one STA in the EHT system. For example, regarding "Index 60" in Table 6, one 26-RU may be allocated to the leftmost user (i.e., receiving STA) in the 20 MHz band, one 26-RU and one 52-RU may be allocated to its right, and five 26-RUs may be separately allocated to its right.

[0228] [Table 5]

[0229]

[0230] [Table 6]

[0231]

[0232] [Table 7]

[0233]

[0234] A mode that supports omitting the common fields of the EHT-SIG is available. The mode of omitting the common fields of the EHT-SIG may be referred to as a compression mode. When using the compression mode, multiple users (i.e., multiple receiving STAs) can decode a PPDU (e.g., the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) received through the same frequency band. In addition, when using the non-compression mode, multiple users of the EHT PPDU can decode a PPDU (e.g., the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU can receive the PPDU (e.g., the data field of the PPDU) through different frequency bands.

[0235] The EHT-SIG can be configured based on various MCS schemes. As described above, information related to the MCS scheme applied to the EHT-SIG can be included in the U-SIG. The EHT-SIG can be configured based on the DCM scheme. For example, among the N data tones (e.g., 52 data tones) allocated for the EHT-SIG, a first modulation scheme can be applied to half of the consecutive tones, and a second modulation scheme can be applied to the remaining half of the consecutive tones. That is, the transmitting STA can use the first modulation scheme to modulate specific control information through the first symbol and allocate it to half of the consecutive tones, and can use the second modulation scheme to modulate the same control information by using the second symbol and allocate it to the remaining half of the consecutive tones. As described above, information (e.g., a 1-bit field) regarding whether the DCM scheme is applied to the EHT-SIG can be included in the U-SIG. Figure 18 The HE-STF can be used to improve the automatic gain control estimation in a multiple-input multiple-output (MIMO) environment or an OFDMA environment. Figure 18 The HE-LTF can be used to estimate the channel in a MIMO environment or an OFDMA environment.

[0236] Can be set in various types Figure 18The EHT-STF. For example, a first type of STF (e.g., 1x STF) can be generated based on a first type of STF sequence in which non-zero coefficients are arranged at intervals of 16 subcarriers. The STF signal generated based on the first type of STF sequence can have a period of 0.8 μs, and the 0.8-μs period signal can be repeated 5 times to become a first type of STF with a length of 4 μs. For example, a second type of STF (e.g., 2x STF) can be generated based on a second type of STF sequence in which non-zero coefficients are arranged at intervals of 8 subcarriers. The STF signal generated based on the second type of STF sequence can have a period of 1.6 μs, and the 1.6-μs period signal can be repeated 5 times to become a second type of STF with a length of 8 μs. Hereinafter, examples of sequences for configuring the EHT-STF (i.e., EHT-STF sequences) are presented. The following sequences can be modified in various ways.

[0237] The EHT-STF can be configured based on the following sequence M.

[0238] <Equation 1>

[0239] M = {–1, –1, –1, 1, 1, 1, –1, 1, 1, 1, –1, 1, 1, –1, 1}

[0240] The EHT-STF for a 20-MHz PPDU can be configured based on the following equation. The following example can be a first type (i.e., 1x STF) sequence. For example, the first type of sequence can be included in an EHT-PPDU rather than a trigger-based (TB) PPDU. In the following equation, (a:b:c) can mean a duration defined as b tone intervals (i.e., subcarrier intervals) from a tone index (i.e., subcarrier index) 'a' to a tone index 'c'. For example, Equation 2 below can represent a sequence defined as 16 tone intervals from tone index -112 to tone index 112. Since a subcarrier interval of 78.125 kHz is applied to the EHT-STR, 16 tone intervals can mean that the EHT-STF coefficients (or elements) are arranged at intervals of 78.125 * 16 = 1250 kHz. Additionally, * means multiplication, and sqrt() means square root. Additionally, j means an imaginary number.

[0241] <Equation 2>

[0242] EHT-STF(–112:16:112) = {M} * (1 + j) / sqrt(2)

[0243] EHT-STF(0) = 0

[0244] The EHT-STF for a 40 MHz PPDU can be configured based on the following formula. The following example can be a first type (i.e., 1xSTF) sequence.

[0245] <Formula 3>

[0246] EHT-STF(-240:16:240) = {M, 0, -M} * (1 + j) / sqrt(2)

[0247] The EHT-STF for an 80 MHz PPDU can be configured based on the following formula. The following example can be a first type (i.e., 1xSTF) sequence.

[0248] <Formula 4>

[0249] EHT-STF(-496:16:496) = {M, 1, –M, 0, –M, 1, –M} * (1 + j) / sqrt(2)

[0250] The EHT-STF for a 160 MHz PPDU can be configured based on the following formula. The following example can be a first type (i.e., 1xSTF) sequence.

[0251] <Formula 5>

[0252] EHT-STF(-1008:16:1008) = {M, 1, –M, 0, –M, 1, –M, 0, –M, –1, M, 0, –M, 1, –M} * (1 + j) / sqrt(2)

[0253] In the EHT-STF for an 80 + 80 MHz PPDU, the sequence for the lower 80 MHz can be the same as Formula 4. In the EHT-STF for an 80 + 80 MHz PPDU, the sequence for the higher 80 MHz can be configured based on the following formula.

[0254] <Formula 6>

[0255] EHT-STF(-496:16:496) = {-M, -1, M, 0, –M, 1, –M} * (1 + j) / sqrt(2)

[0256] The following Formulas 7 to 11 are related to examples of the second type (i.e., 2x STF) sequences.

[0257] <Formula 7>

[0258] EHT-STF(-120:8:120) = {M, 0, -M} * (1 + j) / sqrt(2)

[0259] The EHT-STF for a 40 MHz PPDU can be configured based on the following formula.

[0260] <Equation 8>

[0261] EHT - STF(-248:8:248) = {M, –1, –M, 0, M, –1, M}*(1 + j) / sqrt(2)

[0262] EHT - STF(-248) = 0

[0263] EHT - STF(248) = 0

[0264] The EHT - STF for an 80 MHz PPDU can be configured based on the following equation.

[0265] <Equation 9>

[0266] EHT - STF(-504:8:504) = {M, –1, M, –1, –M, –1, M, 0, –M, 1, M, 1, –M, 1, –M}*(1 + j) / sqrt(2)

[0267] The EHT - STF for a 160 MHz PPDU can be configured based on the following equation.

[0268] <Equation 10>

[0269] EHT - STF(-1016:16:1016) = {M, –1, M, –1, –M, –1, M, 0, –M, 1, M, 1, –M, 1, –M, 0, –M, 1, –M, 1, M, 1, –M, 0, –M, 1, M, 1, –M, 1, –M}*(1 + j) / sqrt(2)

[0270] EHT - STF(-8) = 0, EHT - STF(8) = 0,

[0271] EHT - STF(-1016) = 0, EHT - STF(1016) = 0

[0272] In the EHT - STF for an 80 + 80 MHz PPDU, the sequence for the lower 80 MHz can be the same as Equation 9. In the EHT - STF for an 80 + 80 MHz PPDU, the sequence for the higher 80 MHz can be configured based on the following equation.

[0273] <Equation 11>

[0274] EHT - STF(-504:8:504) = {–M, 1, –M, 1, M, 1, –M, 0, –M, 1, M, 1, –M, 1, –M}*(1 + j) / sqrt(2)

[0275] EHT - STF(-504) = 0,

[0276] EHT - STF(504) = 0

[0277] The EHT - LTF can have first, second, and third types (i.e., 1x, 2x, 4x LTF). For example, the first / second / third type LTF can be generated based on an LTF sequence in which non - zero coefficients are arranged at intervals of 4 / 2 / 1 sub - carriers. The first / second / third type LTF can have a time length of 3.2 / 6.4 / 12.8 μs. Additionally, GIs of various lengths (e.g., 0.8 / 1 / 6 / 3.2 μs) can be applied to the first / second / third type LTF.

[0278] Information related to the type of STF and / or LTF (including information related to the GI applied to the LTF) can be included in Figure 18 the SIG - A field and / or SIG - B field, etc.

[0279] It can be configured based on Figure 5 and Figure 6 examples of Figure 18 the PPDU (e.g., EHT - PPDU).

[0280] For example, the EHT PPDU transmitted on a 20 MHz frequency band can be configured based on the RU of Figure 5 , i.e., the 20 MHz EHTPPDU. That is, the positions of the RUs of the EHT - STF, EHT - LTF, and data fields included in the EHT PPDU can be determined as shown in Figure 5 .

[0281] The EHT PPDU transmitted on a 40 MHz frequency band can be configured based on the RU of Figure 6 , i.e., the 40 MHz EHT PPDU. That is, the positions of the RUs of the EHT - STF, EHT - LTF, and data fields included in the EHT PPDU can be determined as shown in Figure 6 .

[0282] Since Figure 6 the RU position corresponds to 40 MHz, the tone - plan for 80 MHz can be determined when the pattern of Figure 6 is repeated twice. That is, the 80 MHz EHT PPDU can be transmitted based on a new tone - plan in which the RU that is not Figure 7 but Figure 6 is repeated twice.

[0283] When Figure 6When the pattern is repeated twice, 23 tones can be configured in the DC region (i.e., 11 guard tones + 12 guard tones). That is, the tone plan for an 80 MHz EHT PPDU allocated based on OFDMA can have 23 DC tones. In contrast, an 80 MHz EHT PPDU allocated based on non-OFDMA (i.e., non-OFDMA full bandwidth 80 MHz PPDU) can be configured based on 996-RU and can include 5 DC tones, 12 left guard tones, and 11 right guard tones.

[0284] It is possible to configure the tone plan for 160 / 240 / 320 MHz in such a way that the pattern of Figure 6 is repeated several times.

[0285] The Figure 18 PPDU can be determined (or identified) as an EHT PPDU based on the following method.

[0286] The receiving STA can determine the type of the RX PPDU as an EHT PPDU based on the following aspects. For example, 1) when the first symbol after the L-LTF signal in the RXPPDU is a BPSK symbol; 2) when an RL-SIG in which the L-SIG of the RX PPDU is repeated is detected; and 3) when the result of applying "mod 3" to the value of the length field of the L-SIG of the RX PPDU is "0", the RX PPDU can be determined as an EHT PPDU. When the RX PPDU is determined as an EHT PPDU, the receiving STA can detect the type of the EHT PPDU (e.g., SU / MU / trigger-based / extended range type) based on the bit information included in the symbols after the Figure 18 RL-SIG of . In other words, the receiving STA can determine the RX PPDU as an EHT PPDU based on the following: 1) the first symbol after the L-LTF signal, which is a BPSK symbol; 2) the RL-SIG that is consecutive with and the same as the L-SIG field; 3) the L-SIG including the length field, where the result of applying "mod 3" is set to "0"; and 4) the 3-bit PHY version identifier of the aforementioned U-SIG (e.g., the PHY version identifier having a first value).

[0287] For example, the receiving STA can determine the type of the RX PPDU as an EHT PPDU based on the following aspects. For example, 1) when the first symbol after the L-LTF signal is a BPSK symbol; 2) when an RL-SIG in which the L-SIG is repeated is detected; and 3) when the result of applying "mod 3" to the value of the length field of the L-SIG is "1" or "2", the RX PPDU can be determined as a HEPPDU.

[0288] For example, a receiving STA can determine the type of an RX PPDU as a non-HT, HT, and VHT PPDU based on the following aspects. For example, 1) when the first symbol after the L-LTF signal is a BPSK symbol; and 2) when an RL-SIG in which the L-SIG is repeated is not detected, the RX PPDU can be determined as a non-HT, HT, and VHT PPDU. Additionally, even if the receiving STA detects an RL-SIG repetition, when it is detected that the result of applying "mod 3" to the length value of the L-SIG is "0", the RX PPDU can also be determined as a non-HT, HT, and VHT PPDU.

[0289] In the following examples, signals represented as (TX / RX / UL / DL) signals, (TX / RX / UL / DL) frames, (TX / RX / UL / DL) packets, (TX / RX / UL / DL) data units, (TX / RX / UL / DL) data, etc. can be signals transmitted / received based on Figure 18 the PPDU. Figure 18 The PPDU of Figure 18 can be used to transmit / receive various types of frames. For example, Figure 18 the PPDU of Figure 18 can be used for control frames. Examples of control frames can include Request To Send (RTS), Clear To Send (CTS), Power Save Poll (PS-poll), BlockACKReq, BlockAck, Null Data Packet (NDP) Announcement, and Trigger Frame. For example, Figure 18 the PPDU of

[0290] Figure 19 illustrates an example of a modified transmitting device and / or receiving device of this specification.

[0291] Figure 1 Each device / STA of sub-graph (a) / (b) of Figure 19 can be modified as shown in Figure 19 The transceiver 630 of Figure 1 can be the same as the transceivers 113 and 123 of Figure 19 The transceiver 630 of

[0292] Figure 19 The processor 610 of Figure 1 can be the same as the processors 111 and 121 of Figure 19The processor 610 can be the same as Figure 1 the processing chips 114 and 124.

[0293] Figure 19 The memory 620 can be the same as Figure 1 the memories 112 and 122. Alternatively, Figure 19 the memory 620 can be a separate external memory that is different from Figure 1 the memories 112 and 122.

[0294] Refer to Figure 19 , the power management module 611 manages the power for the processor 610 and / or the transceiver 630. The battery 612 supplies power to the power management module 611. The display 613 outputs the results processed by the processor 610. The keypad 614 receives the inputs to be used by the processor 610. The keypad 614 can be displayed on the display 613. The SIM card 615 can be an integrated circuit for securely storing the International Mobile Subscriber Identity (IMSI) and its associated keys, which are used to identify and authenticate users on mobile phone devices (such as mobile phones and computers).

[0295] Refer to Figure 19 , the speaker 640 can output the results related to the sound processed by the processor 610. The microphone 641 can receive the inputs related to the sound to be used by the processor 610.

[0296] 1. Tone plan in the 802.11ax WLAN system

[0297] In this specification, the tone plan relates to the rules for determining the size and / or the position of the resource unit (RU). Hereinafter, the PPDU based on the IEEE 802.11ax standard, that is, the tone plan applied to the HE PPDU, will be described. In other words, hereinafter, the RU size and the RU position applied to the HE PPDU are described, and the control information related to the RU applied to the HE PPDU is described.

[0298] In this specification, the control information related to the RU (or the control information related to the tone plan) may include the size and position of the RU, the information of the user STA assigned to a specific RU, the frequency bandwidth of the PPDU including the RU, and / or the control information regarding the modulation scheme applied to a specific RU. The control information related to the RU may be included in the SIG field. For example, in the IEEE 802.11ax standard, the control information related to the RU is included in the HE-SIG-B field. That is, in the process of generating the TX PPDU, the transmitting STA may allow the control information regarding the RU included in the PPDU to be included in the HE-SIG-B field. Additionally, the receiving STA may receive the HE-SIG-B included in the RX PPDU and obtain the control information included in the HE-SIG-B, so as to determine whether there is an RU assigned to the receiving STA based on the HE-SIG-B and decode the assigned RU.

[0299] In the IEEE 802.11ax standard, the HE-STF, HE-LTF, and data fields can be configured in units of RUs. That is, when configuring the first RU for the first receiving STA, the STF / LTF / data fields for the first receiving STA can be transmitted / received through the first RU.

[0300] In the IEEE 802.11ax standard, the PPDU for one receiving STA (i.e., the SU PPDU) and the PPDU for multiple receiving STAs (i.e., the MU PPDU) are defined separately, and their respective tone plans are defined separately. Specific details will be described below.

[0301] The RU defined in 11ax may include multiple subcarriers. For example, when the RU includes N subcarriers, it can be expressed by an N-tone RU or an N RU. The position of a specific RU can be expressed by a subcarrier index. The subcarrier index can be defined in units of the subcarrier frequency interval. In the 11ax standard, the subcarrier frequency interval is 312.5 kHz or 78.125 kHz, and the subcarrier frequency interval of the RU is 78.125 kHz. That is, the subcarrier index of the RU +1 may mean a position that is 78.125 kHz more increased than the DC tone, and the subcarrier index of the RU -1 may mean a position that is 78.125 kHz less than the DC tone. For example, when the position of a specific RU is expressed by [-121:-96], the RU can be located in the area from subcarrier index -121 to subcarrier index -96. As a result, the RU can include 26 subcarriers.

[0302] The N-tone RU may include preset pilot tones.

[0303] 2. Null Subcarriers and Pilot Subcarriers

[0304] Subcarriers and resource allocation in the 802.11ax system will be described.

[0305] An OFDM symbol consists of subcarriers, and the number of subcarriers can serve as the bandwidth of the PPDU. In the WLAN 802.11 system, data subcarriers for data transmission, pilot subcarriers for phase information and parameter tracking, and unused subcarriers not used for data transmission and pilot transmission are defined.

[0306] The HE MU PPDU transmitted using OFDMA can be sent by mixing 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, and 996-tone RUs.

[0307] Here, a 26-tone RU consists of 24 data subcarriers and 2 pilot subcarriers. A 52-tone RU consists of 48 data subcarriers and 4 pilot subcarriers. A 106-tone RU consists of 102 data subcarriers and 4 pilot subcarriers. A 242-tone RU consists of 234 data subcarriers and 8 pilot subcarriers. A 484-tone RU consists of 468 data subcarriers and 16 pilot subcarriers. A 996-tone RU consists of 980 data subcarriers and 16 pilot subcarriers.

[0308] 1) Null subcarriers

[0309] As Figures 5 to 7 shown, there are null subcarriers between the 26-tone RU, 52-tone RU, and 106-tone RU positions. The null subcarriers are located near the DC or edge tones to avoid leakage of the transmitted center frequency, receiver DC offset, and interference from adjacent RUs. The energy of the null subcarriers is zero. The indices of the null subcarriers are listed as follows.

[0310]

[0311] The positions of the null subcarriers in each 80 MHz frequency segment of the 80 + 80 MHz HE PPDU should follow the positions of the 80 MHz HE PPDU.

[0312] 2) Pilot subcarriers

[0313] If pilot subcarriers are present in the HE-LTF field of a HE SU PPDU, HE MU PPDU, HE ER SU PPDU, or HE TB PPDU, the positions of the pilot sequences in the HE-LTF field and the data field may be the same as those of 4x HE-LTF. In 1x HE-LTF, the positions of the pilot sequences in the HE-LTF are configured by multiplying the pilot subcarriers of the data field by 4. If pilot subcarriers are present in 2x HE-LTF, the positions of the pilot subcarriers shall be the same as those of the pilots in 4x data symbols. All pilot subcarriers are located at the even-numbered indices listed below.

[0314]

[0315] At 160 MHz or 80+80 MHz, for the bilateral 80 MHz, the positions of the pilot subcarriers shall use the same 80 MHz positions.

[0316] 3. HE Transmission Procedures and Phase Rotation

[0317] In an 802.11ax wireless local area network (WLAN) system, the transmission procedure (or sending procedure) in the physical layer (PHY) includes the procedure for a HE single-user (SU) PPDU, the transmission procedure for a HE extended range (ER) SU PPDU, the transmission procedure for a HE multi-user (MU) PPDU, and the transmission procedure based on a HE trigger (TB) PPDU. The FORMAT field of PHY-TXSTART.request(TXVECTOR) may be the same as that of HE_SU, HE_MU, HE_ER_SU, or HE_TB. The transmission procedure does not describe the operations of optional features, such as dual-carrier modulation (DCM). Among the diverse transmission procedures, Figure 21 only the PHY transmission procedure of a HE SU PPDU is shown.

[0318] Figure 20 An example of the PHY transmission procedure of a HE SU PPDU is shown.

[0319] To send data, the MAC generates a PHY-TXSTART.request primitive, which causes the PHY entity to enter the transmit state. In addition, the PHY is configured to operate at an appropriate frequency via the PLME through the station management. Other transmission parameters, such as HE-MCS, coding type, and transmission power, are configured using the PHY-TXSTART.request (TXVECTOR) primitive via the PHY-SAP. After transmitting the PPDU of the transmission (or communication) trigger frame, the MAC sublayer may issue a PHY-TRIGGER.request along with the TRIGVECTOR parameter, which provides the information required to demodulate the expected HE TB PPDU response of the PHY entity.

[0320] The PHY indicates the status of the primary channel and another channel via the PHY-CCA.indication. The transmission of the PPDU should be started by the PHY after receiving the PHY-TXSTART.request (TXVECTOR) primitive.

[0321] After the start of the PHY preamble transmission, the PHY entity immediately initiates data scrambling and data encoding. The coding method for the data field is based on the FEC_CODING, CH_BANDWIDTH, NUM_STS, STBC, MCS, and NUM_USERS parameters of the TXVECTOR.

[0322] In the transmitter (or sending device) block diagram, the SERVICE field and the PSDU are encoded, which will be described later. Data should be exchanged between the MAC and the PHY via the PHY-DATA.request (DATA) primitive issued by the MAC and the PHY-DATA.confirm primitive issued by the PHY. PHY padding bits are applied to the PSDU to set the number of bits of the encoded PSDU to an integer multiple of the number of encoded bits per OFDM symbol.

[0323] The MAC ends the transmission promptly (or rapidly) via the PHY-TXEND.request primitive. The PSDU transmission ends upon receiving the PHY-TXEND.request primitive. Each PHY-TXEND.request primitive can be notified of its reception along with the PHY-TXEND.confirm primitive from the PHY.

[0324] Packet extension and / or signal extension may be present in the PPDU. The PHY-TXEND.confirm primitive is generated at the actual end time of the most recent PPDU, the end time of the packet extension, and the end time of the signal extension.

[0325] In the PHY, a guard interval (GI) indicated together with the GI duration in the GI_TYPE parameter of the TXVECTOR is inserted into all data OFDM symbols as a solution to delay spread.

[0326] If the PPDU transmission is completed, the PHY entity enters the receive state.

[0327] Figure 21 An example of a block diagram of a transmitting device for generating each field of the HE PPDU is shown.

[0328] To generate each field of the HE PPDU, the following block diagram is used.

[0329] a) Pre-FEC PHY padding

[0330] b) Scrambler

[0331] c) FEC (BCC or LDPC) encoder

[0332] d) Post-FEC PHY padding

[0333] e) Stream parser

[0334] f) Segment parser (for contiguous 160 MHz and non-contiguous 80 + 80 MHz transmissions)

[0335] g) BCC interleaver

[0336] h) Constellation mapper

[0337] i) DCM tone mapper

[0338] j) Pilot insertion

[0339] k) Duplication over multiple 20 MHz (for BW > 20 MHz)

[0340] l) Multiplication by the first column of the PHE-LTF

[0341] m) LDPC tone mapper

[0342] n) Segment parser

[0343] o) Space-time block code (STBC) encoder for one spatial stream

[0344] p) Cyclic shift diversity (CSD) for each STS insertion

[0345] q) Spatial mapper

[0346] r) Frequency mapping

[0347] s) Inverse discrete Fourier transform (IDFT)

[0348] f) Cyclic Shift Diversity (CSD) for each chain insertion

[0349] u) Guard Interval (GI) insertion

[0350] v) Windowing

[0351] Figure 21 A block diagram (or transmitter block diagram) of a transmitting device for generating a data field of a HE single - user (SU) PPDU that is LDPC - coded and transmitted at 160 MHz is shown. If the transmitter block diagram is used to generate the data field of a HE SU PPDU transmitted in the 80 + 80 MHz band, a segment de - parser is not used, as Figure 21 shown. That is, in the case where the frequency band is divided into an 80 MHz band and another 80 MHz band using a segment parser, the block diagram of the transmitter (or transmitting device) is used for each 80 MHz band.

[0352] Refer to Figure 21 , the LDPC encoder can encode a data field (or data bit stream). The data bit stream input to the LDPC encoder can be scrambled by a scrambler.

[0353] The stream parser divides the data bit stream encoded by the LDPC encoder into a plurality of spatial streams. At this time, the encoded data bit stream divided into each spatial stream can be referred to as a spatial block. The number of spatial blocks can be determined by the number of spatial streams used to transmit the PPDU and can be set to be equal to the number of spatial streams.

[0354] The stream parser divides each spatial block into at least one or more data segments. As Figure 21 shown, when transmitting a data field in the 160 MHz band, the 160 MHz band is divided into two 80 MHz bands, and the data field is divided into a first data segment and a second data segment for each 80 MHz band. Then, the first and second data segments can be constellation - mapped to their respective 80 MHz bands and can be LDPC - mapped.

[0355] In HE MU transmission, except that the cyclic shift diversity (CSD) is performed based on the information of the space - time stream starting index of the corresponding user, for each user and even for the input to the space - mapping block, the PPDU encoding processor operates independently in a resource unit (RU). All user data of the RU is mapped through a transmission chain coupled to the space - mapping block.

[0356] In 802.11ax, phase rotation can be applied to fields from the legacy preamble to the field just before the HE-STF, and the phase rotation value can be defined in units of 20 MHz bands. In other words, phase rotation can be applied to L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B among the fields of the HE PPDU defined in 802.11ax.

[0357] The L-STF field of the HE PPDU can be constructed as follows.

[0358] a) Determine the channel bandwidth from the TXVECTOR parameter CH_BANDWIDTH.

[0359] b) Sequence generation: Generate the L-STF sequence over the channel bandwidth as described in 27.3.11.3 (L-STF). If transmitting a HE ER SU PPDU, apply a 3 dB power boost as described in 27.3.11.3 (L-STF).

[0360] c) Phase rotation: Apply the appropriate phase rotation to each 20 MHz subchannel as described in 27.3.10 (Mathematical description of signals) and 21.3.7.5 (Definition of tone rotation).

[0361] d) Per-STS CSD: If the TXVECTOR parameter BEAM_CHANGE is 0, apply the per-STS CSD to each spatial stream and frequency segment as described in 27.3.11.2.2 (Cyclic shift of the HE modulation field).

[0362] e) Spatial mapping: If the TXVECTOR parameter BEAM_CHANGE is 0, apply the A matrix and Q matrix as described in 27.3.11.3 (L-STF).

[0363] f) IDFT: Calculate the inverse discrete Fourier transform.

[0364] g) Per-chain CSD: If the TXVECTOR parameter BEAM_CHANGE is 1 or does not exist, apply the per-chain CSD to each transmit chain and frequency segment as described in 27.3.11.2.1 (Cyclic shift of the pre-HE modulation field).

[0365] h) Insert GI and apply windowing: Insert the prefix GI (T GI,Pre-HE ) and apply windowing as described in 27.3.10 (Mathematical description of signals).

[0366] i) Analog and RF: Upconvert the complex baseband waveform of the result associated with each transmit chain to an RF signal according to the center frequency of the desired channel and transmit. For details, refer to 27.3.10 (Mathematical description of signals) and 27.3.11 (HE preamble).

[0367] The L-LTF field of the HE PPDU can be constructed as follows.

[0368] a) Determine the channel bandwidth from the TXVECTOR parameter CH_BANDWIDTH.

[0369] b) Sequence generation: Generate the L-STF sequence over the channel bandwidth as described in 27.3.11.4 (L-STF). If transmitting a HE ER SU PPDU, apply a 3 dB power boost as described in 27.3.11.4 (L-STF).

[0370] c) Phase rotation: Apply the appropriate phase rotation to each 20 MHz subchannel as described in 27.3.10 (Mathematical description of signals) and 21.3.7.5 (Definition of tone rotation).

[0371] d) CSD per STS: If the TXVECTOR parameter BEAM_CHANGE is 0, apply CSD per STS to each spatial-temporal stream and frequency segment before spatial mapping as described in 27.3.11.2.2 (Cyclic shift of the HE modulation field).

[0372] e) Spatial mapping: If the TXVECTOR parameter BEAM_CHANGE is 0, apply the A matrix and Q matrix as described in 27.3.11.4 (L-STF).

[0373] f) IDFT: Compute the inverse discrete Fourier transform.

[0374] g) CSD per chain: If the TXVECTOR parameter BEAM_CHANGE is 1 or does not exist, apply CSD per chain to each transmit chain and frequency segment as described in 27.3.11.2.1 (Cyclic shift of the pre-HE modulation field).

[0375] h) Insert GI and apply windowing: Insert the prefix GI (T GI,Pre-HE ) and apply windowing as described in 27.3.10 (Mathematical description of signals).

[0376] i) Analog and RF: Upconvert the complex baseband waveform of the result associated with each transmit chain to an RF signal according to the center frequency of the desired channel and transmit. For details, refer to 27.3.10 (Mathematical description of signals) and 27.3.11 (HE preamble).

[0377] The L-SIG field of the HE PPDU can be constructed as follows.

[0378] a) Set the RATE subfield in the SIGNAL field to 6 Mb / s. Set the LENGTH, Parity, and Tail fields in the SIGNAL field as described in 27.3.11.5 (L-SIG).

[0379] b) BCC Encoder: Encode the SIGNAL field by a convolutional encoder at a rate of R = 1 / 2 as described in 27.3.12.5.1 (BCC compilation and puncturing).

[0380] c) BCC Interleaver: Interleave (BCC interleaver) as described in 17.3.5.7.

[0381] d) Constellation Mapper: BPSK modulation as described in 27.3.12.9 (constellation mapping).

[0382] e) Pilot Insertion: Insert pilots as described in 27.3.11.5 (L-SIG).

[0383] f) Additional Subcarrier Insertion: Insert four additional subcarriers at k ∈ {-28, -27, 27, 28} for channel estimation, and the values on these four additional subcarriers are {-1, -1, -1, 1} respectively.

[0384] If transmitting an HE ER SU PPDU, apply a 3 dB power boost to the four additional subcarriers as described in 27.3.11.5 (L-SIG).

[0385] g) Duplication and Phase Rotation: Duplicate the L-SIG field on each occupied 20 MHz subchannel of the channel bandwidth. Apply appropriate phase rotation to each occupied 20 MHz subchannel as described in 27.3.10 (mathematical description of the signal) and 21.3.7.5 (definition of tone rotation).

[0386] h) CSD per STS: If the TXVECTOR parameter BEAM_CHANGE is 0, apply CSD per STS to each spatial stream and frequency segment before spatial mapping as described in 27.3.11.2.2 (cyclic shift of the HE modulation field).

[0387] i) Spatial Mapping: If the TXVECTOR parameter BEAM_CHANGE is 0, apply the A matrix and Q matrix as described in 27.3.11.5 (L-SIG).

[0388] j) IDFT: Calculate the inverse discrete Fourier transform.

[0389] k) CSD per chain: If the TXVECTOR parameter BEAM_CHANGE is 1 or does not exist, apply the CSD per chain for each transmit chain and frequency segment, as described in 27.3.11.2.1 (Cyclic shift of the pre-HE modulation field).

[0390] l) Insert GI and apply windowing: Prepend the GI (T GI,Pre-HE ) and apply windowing, as described in 27.3.10 (Mathematical description of the signal).

[0391] m) Analog and RF: Up-convert the complex baseband waveform of the result associated with each transmit chain. For details, refer to 27.3.10 (Mathematical description of the signal) and 27.3.11 (HE preamble).

[0392] The RL-SIG field of the HE PPDU can be constructed as follows.

[0393] a) Set the RATE subfield in the repeated SIGNAL field to 6 Mb / s. Set the LENGTH Parity and Tail fields in the repeated SIGNAL field, as described in 27.3.11.6 (RL-SIG).

[0394] b) BCC encoder: Encode the repeated SIGNAL field by a convolutional encoder at a rate of R = 1 / 2, as described in 27.3.12.5.1 (BCC coding and puncturing).

[0395] c) BCC interleaver: Interleave (BCC interleaver) as described in 17.3.5.7.

[0396] d) Constellation mapper: BPSK modulation as described in 27.3.12.9 (Constellation mapping).

[0397] e) Pilot insertion: Insert pilots as described in 27.3.11.6 (RL-SIG).

[0398] f) Additional subcarrier insertion: Insert four additional subcarriers at k ∈ {-28, -27, 27, 28} for channel estimation, and the values on these four additional subcarriers are {-1, -1, -1, 1} respectively.

[0399] If transmitting an HE ER SU PPDU, apply a 3 dB power boost to the four additional subcarriers, as described in 27.3.11.6 (RL-SIG).

[0400] g) Replication and Phase Rotation: The RL-SIG field is replicated on each occupied 20 MHz subchannel of the channel bandwidth. An appropriate phase rotation is applied to each occupied 20 MHz subchannel, as described in 27.3.10 (Mathematical Description of Signals) and 21.3.7.5 (Definition of Tone Rotation).

[0401] h) CSD per STS: If the TXVECTOR parameter BEAM_CHANGE is 0, the CSD per STS is applied to each spatial stream and frequency segment before spatial mapping, as described in 27.3.11.2.2 (Cyclic Shift of HE Modulation Field).

[0402] i) Spatial Mapping: If the TXVECTOR parameter BEAM_CHANGE is 0, the A matrix and Q matrix are applied, as described in 27.3.11.6 (RL-SIG).

[0403] j) IDFT: Compute the inverse discrete Fourier transform.

[0404] k) CSD per Chain: If the TXVECTOR parameter BEAM_CHANGE is 1 or does not exist, the CSD per chain is applied to each transmit chain and frequency segment, as described in 27.3.11.2.1 (Cyclic Shift of Pre-HE Modulation Field).

[0405] l) Insert GI and Apply Windowing: Prepend the GI (T GI,Pre-HE ) and apply windowing, as described in 27.3.10 (Mathematical Description of Signals).

[0406] m) Analog and RF: Upconvert the complex baseband waveform of the result associated with each transmit chain. For details, refer to 27.3.10 (Mathematical Description of Signals) and 27.3.11 (HE Preamble).

[0407] 4. Embodiments Applicable to the Present Disclosure

[0408] In a wireless LAN 802.11 system, to increase the peak throughput, it is considered to use a wider frequency band than the existing 11ax or to transmit additional streams by using more antennas. In addition, this specification also considers methods of aggregating multiple links or aggregating multiple RUs and allocating them to one STA for transmission.

[0409] In this specification, a method of allocating and transmitting multiple RUs to one STA is considered, and in this case, a method of aggregating RUs in various bandwidths is proposed. In particular, this specification focuses on and proposes a method of aggregating large RUs in non-OFDMA transmission.

[0410] In the existing 802.11ax, preamble puncturing is not considered during non - OFDMA transmission. Therefore, non - OFDMA transmission can only use the entire bandwidth of 20 / 40 / 80 / 160 / 160 + 160 MHz, and the RUs used at this time are as follows.

[0411] 242 / 484 / 996 / 2x996 RU

[0412] The above RUs will be referred to as large RUs.

[0413] In 802.11be, preamble puncturing is introduced in non - OFDMA transmission to improve efficiency. This may be based on 20 - MHz puncturing, similar to the preamble puncturing in the OFDMA of 802.11ax. In this case, non - OFDMA transmission can be performed by combining multiple large RUs. In this specification, various combinations of large RUs in non - OFDMA transmission will be presented as follows for each bandwidth case. However, the case where the preamble puncturing part does not exceed 50% of the total bandwidth is considered.

[0414] In addition, in order to minimize the interference during preamble puncturing in each 80 - MHz sub - channel of various bandwidths, the tone plan of adjacent 20 - MHz channels can be replaced with a 20 - MHz tone plan, or a tone plan in which only the 20 - MHz part of the 80 - MHz tone plan is partially shifted can be used. Of course, without changing the tone plan of adjacent 20 - MHz channels by using hardware / filters that can effectively control interference, the original 80 - MHz tone plan can be used as it is, and data can be sent using the remaining channels except for the 20 - MHz preamble puncturing.

[0415] Alternatively, the tone plan is used as it is, but when the adjacent channel of the 20 - MHz channel of the preamble puncturing uses a 242 - tone RU, the 242 - tone RU method of 802.11ax is encoded as it is. Alternatively, during transmission, some tones adjacent to the puncturing channel among the 242 - tone RUs can be sent by forced puncturing or reducing power. Here, the adjacent 20 - MHz channel means the 20 - MHz channel in each 40 - MHz sub - channel except for the 20 - MHz channel of the preamble puncturing when each 80 - MHz sub - channel is divided into a lower 40 - MHz and a higher 40 - MHz.

[0416] In addition, in the lower 40 MHz or the higher 40 MHz without performing leading perforation, 484-tone RUs (484-tone RUs in the corresponding 40 MHz in the 80 MHz tone plan) can be used for data transmission. 242-tone RUs (242-tone RUs in 20 MHz in the 80 MHz tone plan or 242-tone RUs in 20 MHz in a tone plan changed to reduce interference) can be used for data transmission in the 20 MHz adjacent to the 20 MHz with leading perforation. This method can be directly applied to all the following leading perforation scenarios.

[0417] 4.1. 80 MHz

[0418] Figure 22 Shows the channel structure of 80 MHz.

[0419] Although it is assumed in Figure 22 that P20 is located at the lowest frequency, the position can be different and the position of another 20 MHz channel can be different. Transmissions using 996 RUs considering the use of the entire 80 MHz can be considered, and this will be referred to as PC80.

[0420] Figure 23 Shows an example of leading perforation in non-OFDMA 80 MHz transmission.

[0421] In non-OFDMA 80 MHz transmission, the leading perforation applied to the 80 MHz transmission of existing 11ax OFDMA can be applied as it is, as Figure 23 shown.

[0422] Figure 23 , non-OFDMA transmission is possible through the combination of 484 + 242 RUs. This combination will be referred to as PC60.

[0423] Figure 24 Shows an example of additional leading perforation in non-OFDMA 80 MHz transmission.

[0424] In addition, Figure 24 the leading perforation of

[0425] can be considered. Figure 24 Referring to

[0426] The following summarizes various RU combinations, and the order and position of RUs in each combination can be changed. The meaning of the parentheses indicates each 80 MHz RU combination. That is, the order and position of RUs can be changed within the parentheses (i.e., within each 80 MHz), and the order and position of the parentheses can also be changed (i.e., the position and sequence diagram of each 80 MHz). Since it is 80 MHz, each combination has only one parenthesis.

[0427] (242 + 242), (484 + 242), (996)

[0428] 4.2.160 / 80 + 80 MHz

[0429] Figure 25 An example of a 160 / 80 + 80 MHz channel configuration is shown.

[0430] Figure 25 The channel structure of 160 / 80 + 80 MHz is shown. For the 160 / 80 + 80 MHz tone plan, the 80 MHz tone plan is repeated twice.

[0431] 1) In P80, two combinations of PC60 and PC40 proposed in 4.1.80 MHz transmission can be considered.. In addition, the case of transmitting only the main 40 (P40) in P80 can be considered, and transmission using 484 RUs (hereinafter referred to as PC40 of the combination with 242 + 242 RUs) is possible. In addition, transmission using 242 RUs of only P20 can be considered and is referred to as PC20. In addition, transmission using 996 RUs of the entire P80 can be considered and is referred to as PC80.

[0432] 2) When considering the preamble puncturing in the existing 802.11ax, at least one 20 MHz puncturing does not need to be performed in S80. In this case, various combinations of RUs can be considered in S80 as follows.

[0433] 242 RUs: This will be referred to as SC20.

[0434] 484 RUs, 242 + 242 RUs: This will be referred to as SC40.

[0435] 484 + 242 RUs: This will be referred to as SC60.

[0436] 996 RUs: This will be referred to as SC80.

[0437] The RU combinations of P80 include PC20, PC40, PC60, and PC80, and the RU combinations of S80 include SC20, SC40, SC60, and SC80.

[0438] In this case, considering the 160 / 80 + 80 MHz preamble puncturing, the following various combinations can be proposed, which is the case where the channels that are not always punctured are 50% or more.

[0439] PC40 + SC40 、 PC40 + SC60 、 PC40 + SC80 、 PC60 + SC20 、PC60 + SC40、 PC60 + SC60 、 PC60 + SC80

[0440] PC20 + SC60、 PC20 + SC80 、PC80 + SC20、PC80 + SC40、PC80 + SC60、 PC80 + SC80 (996 + 996 RU or 2x996 RU)

[0441] The meaning of the underlines above is to indicate only the representative combinations that exclude duplicate combinations among all combinations. If PC40 + SC60 is expressed as RU, it can be expressed as (484 RU)+(484 + 242 RU) or (242 + 242 RU)+(484 + 242 RU). If PC60 + SC40 is expressed as RU, it can be expressed as (484 + 242 RU)+(484 RU) or (484 + 242 RU)+(242 + 242 RU). The meaning of the parentheses means the combination within the 80 MHz channel. Therefore, the combinations of PC40 + SC60 and PC60 + SC40 are the same, and one of them can be excluded. All the combinations with the following underlines have the same meaning.

[0442] The following summarizes various RU combinations, and the order and position of RU in each combination can be changed. The meaning of the parentheses means the RU combination for each 80 MHz. That is, the order and position of RU can be changed within the parentheses (i.e., within each 80 MHz), and the order and position of the parentheses can also be changed (i.e., the position and sequence diagram of each 80 MHz).

[0443] (242)+(484 + 242)、(242)+(996)、(242 + 242)+(242 + 242)、(242 + 242)+(484)、(484)+(484)、(242 + 242)+(484 + 242)、(484)+(484 + 242)、(242 + 242)+(996)、(484)+(996)、(484 + 242)+(484 + 242)、(484 + 242)+(996)、(996)+(996) / 2x996

[0444] Specifically, it is possible to consider only one 20 MHz punctured (484 + 242) + (996) and one continuous 40 MHz punctured (484) + (996). Additionally, we can consider (242) + (996) and (484) + (484 + 242), where only one continuous 60 MHz is punctured (in the case where the continuous 60 MHz puncture is at the boundary between two 80 MHz), and (484 + 242) + (484 + 242), where only one continuous 40 MHz is punctured (in the case where the continuous 40 MHz puncture is at the boundary of two 80 MHz). Additionally, (242 + 242) + (996), where only one continuous 40 MHz is punctured (in the case of a continuous 40 MHz starting from the center of a specific 80 MHz, i.e., when two central 20 MHz are punctured) can be additionally considered. Additionally, (484) + (484), (242) + (484 + 242) (in the case of a continuous 80 MHz puncture at the boundary of two 80 MHz) where only one continuous 80 MHz is punctured can be additionally considered.

[0445] Combinations where only one continuous 20 or 40 MHz is punctured in each primary and secondary 80 can be considered. For example, it may have combinations of (484 + 242) + (484 + 242), (484) + (484), (484) + (242 + 242), and (242 + 242) + (242 + 242). As another example, it may have combinations of (484 + 242) + (484) and (484 + 242) + (242 + 242).

[0446] 4.3.240 / 160 + 80 MHz

[0447] Figure 26 Examples of 240 / 160 + 80 MHz are derived from continuous 320 MHz.

[0448] Assume that the 240 / 160 + 80 MHz channel is fixed to three specific 80 MHz channels. In this case, the 240 / 160 + 80 MHz channel configuration can consider the following three cases. For the 240 / 160 + 80 MHz tone plan, the 80 MHz tone plan is repeated 3 times.

[0449] Case 1: Primary 80 (P80) + Secondary 80 (S80) + Lower 80 (L80)

[0450] Case 2: Primary 80 (P80) + Secondary 80 (S80) + Higher 80 (H80)

[0451] Case 3: Primary 80 (P80) + Lower 80 (L80) + Higher 80 (H80)

[0452] P80 and S80 form the main 160 (P160), and L80 and H80 form the auxiliary 160 (S160).

[0453] Figure 27 is an example of continuous 240 MHz derived from continuous 320 MHz.

[0454] For 240 / 160 + 80 MHz derived from continuous 320 MHz, only continuous 240 MHz can be considered, as Figure 27 shown.

[0455] Figure 28 is an example of discontinuous 160 + 80 MHz derived from discontinuous 160 + 160 MHz.

[0456] For 240 / 160 + 80 MHz derived from discontinuous 160 + 160 MHz, only discontinuous 160 + 80 MHz can be considered, as Figure 28 shown.

[0457] 1) In these three cases, the RU combinations in P80 can be used, as suggested in 4.1. and 4.2.

[0458] 2) In case 1, at least one 20 MHz in L80 should not be punctured, and thus, the RU combinations in S80 suggested in 4.2. can be used as they are. In case 1, if at least one 20 MHz in S80 is not punctured, the RU combinations in S80 proposed in 4.2. can be used as they are. The various RU combinations in the total bandwidth in case 1 can be proposed as follows. It is assumed that the number of channels that are not always punctured is 50% or more.

[0459] If all of S80 are punctured

[0460] PC40 + SC80 、 PC60 + SC60 、 PC60 + SC80

[0461] PC80 + SC40, PC80 + SC60, PC80 + SC80 (996 + 996 RU or 2x996 RU)

[0462] If at least one 20 MHz in S80 is not punctured

[0463] PC40 + SC20 + SC60 、 PC40 + SC20 + SC80 、 PC40 + SC40 + SC40 、 PC40 + SC40 + SC60 、 PC40 + SC40 + SC80, PC40 + SC60 + SC20, PC40 + SC60 + SC40, PC40 + SC60 + SC60 , PC40 + SC60 + SC80 , PC40 + SC80 + SC20, PC40 + SC80 + SC40, PC40 + SC80 + SC60, PC40 + SC80 + SC80 , PC60 + SC20 + SC40, PC60 + SC20 + SC60 , PC60 + SC20 + SC80 , PC60 + SC40 + SC20, PC60 + SC40 + SC40, PC60 + SC40 + SC60, PC60 + SC40 + SC80, PC60 + SC60 + SC20, PC60 + SC60 + SC40, PC60 + SC60 + SC60 , PC60 + SC60 + SC80 , PC60 + SC80 + SC20, PC60 + SC80 + SC40, PC60 + SC80 + SC60, PC60 + SC80 + SC80

[0464] PC20 + SC20 + SC80 , PC20 + SC40 + SC60, PC20 + SC40 + SC80, PC20 + SC60 + SC40, PC20 + SC60 + SC60, PC20 + SC60 + SC80, PC20 + SC80 + SC20, PC20 + SC80 + SC40, PC20 + SC80 + SC60, PC20 + SC80 + SC80 , PC80 + SC20 + SC20, PC80 + SC20 + SC40, PC80 + SC20 + SC60, PC80 + SC20 + SC80, PC80 + SC40 + SC20, PC80 + SC40 + SC40, PC80 + SC40 + SC60, PC80 + SC40 + SC80, PC80 + SC60 + SC20, PC80 + SC60 + SC40, PC80 + SC60 + SC60, PC80 + SC60 + SC80, PC80 + SC80 + SC20, PC80 + SC80 + SC40, PC80 + SC80 + SC60, PC80 + SC80 + SC80 (or 996 + 996 + 996 RU or 996 + 2x996 RU or 3x996 RU)

[0465] 2) In case 2, at least one 20 MHz in H80 should not be punctured, so the RU combinations in S80 recommended in 4.2. can be used as they are. In case 2, if at least one 20 MHz in S80 is not punctured, the RU combinations in S80 proposed in 4.2. can be used as they are. Therefore, in case 2, the various RU combinations in the total bandwidth are the same as in case 1.

[0466] 3) In Case 3, at least one 20 MHz should not be punctured in S160, and one 20 MHz does not have to be punctured in the 80 MHz of L80 or H80, and the case where all other 80 MHz may or may not be punctured can be considered. Therefore, in Case 3, the various RU combinations in the total bandwidth are the same as in Case 1.

[0467] The following summarizes the various RU combinations, and the order and position of the RUs in each combination can be changed. The meaning of the parentheses means the RU combination of each 80 MHz. That is, the order and position of the RUs can be changed within the parentheses (i.e., within each 80 MHz), and the order and position of the parentheses can also be changed (i.e., the position and sequence diagram of each 80 MHz).

[0468] (242 + 242)+(996), (484)+(996), (484 + 242)+(484 + 242), (484 + 242)+(996), (996)+(996) / 2x996

[0469] (242)+(242)+(996), (242)+(242 + 242)+(484 + 242), (242)+(484)+(484 + 242), (242)+(242 + 242)+(996), (242)+(484)+(996), (242)+(484 + 242)+(484 + 242), (242)+(484 + 242)+(996), (242)+(996)+(996), (242 + 242)+(242 + 242)+(242 + 242), (242 + 242)+(242 + 242)+(484), (242 + 242)+(484)+(484), (484)+(484)+(484), (242 + 242)+(242 + 242)+(484 + 242), (242 + 242)+(484)+(484 + 242), (484)+(484)+(484 + 242), (242 + 242)+(242 + 242)+(996), (242 + 242)+(484)+(996), (484)+(484)+(996), (242 + 242)+(484 + 242)+(484 + 242), (484)+(484 + 242)+(484 + 242), (242 + 242)+(484 + 242)+(996), (484)+(484 + 242)+(996), (242 + 242)+(996)+(996), (484)+(996)+(996), (484 + 242)+(484 + 242)+(484 + 242), (484 + 242)+(484 + 242)+(996), (484 + 242)+(996)+(996), (996)+(996)+(996) / 2x996 + 996 / 3x996

[0470] In particular, it is possible to consider only (484)+(996)+(996) in which only one consecutive 40 MHz is punctured and (996)+(996) in which only one consecutive 80 MHz is punctured. Additionally, it is possible to consider (484 + 242)+(484 + 242)+(996) in which only one consecutive 40 MHz is punctured (in the case where the consecutive 40 MHz puncturing is at the boundary between two specific 80 MHz) and (242)+(996)+(996), (484)+(484 + 242)+(996), and (484 + 242)+(996), (484)+(484)+(996), and (242)+(484 + 242)+(996) in which only one consecutive 60 MHz is punctured (in the case where the consecutive 60 MHz puncturing is at the boundary between two specific 80 MHz) and (484 + 242)+(996) in which only one consecutive 80 MHz is punctured (in the case where the consecutive 80 MHz puncturing is at the boundary between two specific 80 MHz). Additionally, (242 + 242)+(996)+(996) in which only one consecutive 40 MHz is punctured (in the case of consecutive 40 MHz starting from the center of a specific 80 MHz, i.e., when two central 20 MHz are punctured) can be additionally considered.

[0471] Combinations where only one consecutive 40 MHz or 60 MHz is punctured in each 80, 160 MHz block can be considered. For example, there may be combinations of (484)+(484)+(996), (484)+(242 + 242)+(996), (484)+(484 + 242)+(484 + 242), (242 + 242)+(484)+(996), (242 + 242)+(242 + 242)+(996), (242 + 242)+(484 + 242)+(484 + 242), (242)+(242)+(996), (242)+(484)+(484 + 242).

[0472] As another example, there may be combinations of (484)+(242)+(996), (484)+(484)+(484 + 242), (242 + 242)+(242)+(996), (242 + 242)+(484)+(484 + 242), (242)+(484)+(996), (242)+(242 + 242)+(996), (242)+(484)+242)+(484 + 242).

[0473] 4.4.3 20 / 160 + 160 MHz

[0474] Figure 29Shows a channel structure of 320 / 160 + 160 MHz. For the 320 / 160 + 160 MHz tone plan, the 80 MHz tone plan is repeated four times.

[0475] In 320 / 160 + 160 MHz, the preamble puncturing pattern may vary depending on the channel configuration of 240 / 160 + 80 MHz, and considering the channel configuration cases of 240 / 160 + 80 MHz shown below, RU combinations are proposed. In these three cases, the RU combinations in P80 can be used according to the suggestions in 4.1. and 4.2.

[0476] 4.4.1. 240 / 160 + 80 MHz Channel Configuration Case 1

[0477] At least one of the 20 MHz channels in H80 must not be punctured, and therefore, the RU combinations in S80 proposed in 4.2. can be used as they are. If at least one 20 MHz in S80 or L80 is not punctured, the RU combinations in S80 proposed in 4.2. can be used as they are. Various RU combinations in the entire bandwidth can be proposed as follows. This is the case where the number of channels that are not always punctured is 50% or more.

[0478] If both S80 and L80 are punctured

[0479] PC20 + SC80, PC40 + SC80, PC60 + SC60, PC60 + SC80, PC80 + SC80

[0480] Except for PC80 + SC80, the above cases are not considered because the non - punctured channels do not exceed 50%.

[0481] If at least one 20 MHz within 80 MHz of S80 or L80 is not punctured

[0482] [[ID=278 , ​ , PC40 + SC60 + SC80 , PC40 + SC80 + SC40, PC40 + SC80 + SC60, PC40 + SC80 + SC80 , PC60 + SC20 + SC80 , PC60 + SC40 + SC60, PC60 + SC40 + SC80, PC60 + SC60 + SC40, PC60 + SC60 + SC60 , PC60 + SC60 + SC80, PC60 + SC80 + SC20, PC60 + SC80 + SC40, PC60 + SC80 + SC60, PC60 + SC80 + SC80

[0483] PC20 + SC60 + SC80, PC20 + SC80 + SC60,PC20 + SC80 + SC80 、 PC80 + SC20 + SC60, PC80 + SC20 + SC80, PC80 + SC40 + SC40, PC80 + SC40 + SC60, PC80 + SC40 + SC80, PC80 + SC60 + SC20, PC80 + SC60 + SC40, PC80 + SC60 + SC60, PC80 + SC60 + SC80, PC80 + SC80 + SC20, PC80 + SC80 + SC40, PC80 + SC80 + SC60, PC80 + SC80 + SC80 (or 996 + 996 + 996 RU or 996 + 2x996 RU or 3x996 RU)

[0484] If at least one 20 MHz within 80 MHz of both S80 and L80 is not perforated

[0485] PC40 + SC20 + SC20 + SC80 、 PC40 + SC20 + SC40 + SC60 、 PC40 + SC20 + SC40 + SC80 、 PC40 + SC20 + SC60 + SC40, PC40 + SC20 + SC60 + SC60 、 PC40 + SC20 + SC60 + SC80 、 PC40 + SC20 + SC80 + SC20, PC40 + SC20 + SC80 + SC40, PC40 + SC20 + SC80 + SC60, PC40 + SC20 + SC80 + SC80 、 PC40 + SC40 + SC20 + SC60, PC40 + SC40 + SC20 + SC80, PC40 + SC40 + SC40 + SC40 、 PC40 + SC40 + SC40 + SC60 、 PC40 + SC40 + SC40 + SC80 、 PC40 + SC40 + SC60 + SC20, PC40 + SC40 + SC60 + SC40, PC40 + SC40 + SC60 + SC60 、 PC40 + SC40 + SC60 + SC80 、 PC40 + SC40 + SC80 + SC20, PC40 + SC40 + SC80 + SC40, PC40 + SC40 + SC80 + SC60, PC40 + SC40 + SC80 + SC80 、 PC40 + SC60 + SC20 + SC40, PC40 + SC60 + SC20 + SC60, PC40 + SC60 + SC20 + SC80, PC40 + SC60 + SC40 + SC20, PC40 + SC60 + SC40 + SC40, PC40 + SC60 + SC40 + SC60, PC40 + SC60 + SC40 + SC80, PC40 + SC60 + SC60 + SC20, PC40 + SC60 + SC60 + SC40, PC40 + SC60 + SC60 + SC60 、 PC40 + SC60 + SC60 + SC80, PC40 + SC60 + SC80 + SC20, PC40 + SC60 + SC80 + SC40, PC40 + SC60 + SC80 + SC60, PC40 + SC60 + SC80 + SC80 , PC40 + SC80 + SC20 + SC20, PC40 + SC80 + SC20 + SC40, PC40 + SC80 + SC20 + SC60, PC40 + SC80 + SC20 + SC80, PC40 + SC80 + SC40 + SC20, PC40 + SC80 + SC40 + SC40, PC40 + SC80 + SC40 + SC60, PC40 + SC80 + SC40 + SC80, PC40 + SC80 + SC60 + SC20, PC40 + SC 80 + SC60 + SC40, PC40 + SC80 + SC60 + SC60, PC40 + SC80 + SC60 + SC80, PC40 + SC80 + SC80 + SC20, PC40 + SC80 + SC80 + SC40, PC40 + SC80 + SC80 + SC60, PC40 + SC80 + SC80 + SC80

[0486] PC60 + SC20 + SC20 + SC60 , PC60 + SC20 + SC20 + SC80 , PC60 + SC20 + SC40 + SC40, PC60 + SC20 + SC40 + SC60, PC60 + SC20 + SC40 + SC80, PC60 + SC20 + SC60 + SC20, PC60 + SC20 + SC60 + SC40, PC60 + SC20 + SC60 + SC60 , PC60 + SC20 + SC60 + SC80 , PC60 + SC20 + SC80 + SC20, PC60 + SC20 + SC80 + SC40, PC60 + SC20 + SC80 + SC60, PC60 + SC20 + SC80 + SC80, PC60 + SC40 + SC20 + SC40, PC60 + SC40 + SC20 + SC60, PC60 + SC40 + SC20 + SC80, PC60 + SC40 + SC40 + SC20, PC60 + SC40 + SC40 + SC40, PC60 + SC40 + SC40 + SC60, PC60 + SC40 + SC40 + SC80, PC60 + SC40 + SC60 + SC20, PC60 + SC40 + SC60 + SC40, PC60 + SC40 + SC60 + SC60, PC60 + SC40 + SC60 + SC80, PC60 + SC40 + SC80 + SC20, PC60 + SC40 + SC80 + SC40, PC60 + SC40 + SC80 + SC60, PC60 + SC40 + SC80 + SC80, PC60 + SC60 + SC20 + SC20, PC60 + SC60 + SC20 + SC40, PC60 + SC60 + SC20 + SC60, PC60 + SC60 + SC20 + SC80, PC60 + SC60 + SC40 + SC20, PC60 + SC60 + SC40 + SC40, PC60 + SC60 + SC40 + SC60, PC60 + SC60 + SC40 + SC80, PC60 + SC60 + SC60 + SC20, PC60 + SC60 + SC60 + SC40, PC60 + SC60 + SC60 + SC60 , PC60 + SC60 + SC60 + SC80 , PC60 + SC60 + SC80 + SC20, PC60 + SC60 + SC80 + SC40, PC60 + SC60 + SC80 + SC60, PC60 + SC60 + SC80 + SC80 , PC60 + SC80 + SC20 + SC20, PC60 + SC80 + SC20 + SC40, PC60 + SC80 + SC20 + SC60, PC60 + SC 80 + SC20 + SC80, PC60 + SC80 + SC40 + SC20, PC60 + SC80 + SC40 + SC40, PC60 + SC80 + SC40 + SC60, PC60 + SC80 + SC40 + SC80, PC60 + SC80 + SC60 + SC20, PC60 + SC80 + SC60 + SC40, PC60 + SC80 + SC60 + SC60, PC60 + SC80 + SC60 + SC80, PC60 + SC80 + SC80 + SC20, PC60 + SC80 + SC80 + SC40, PC60 + SC80 + SC80 + SC60, PC60 + SC80 + SC80 + SC80

[0487] PC20 + SC20 + SC40 + SC80, PC20 + SC20 + SC60 + SC60, PC20 + SC20 + SC60 + SC80, PC20 + SC20 + SC80 + SC40, PC20 + SC20 + SC80 + SC60, PC20 + SC20 + SC80 + SC80 , PC20 + SC40 + SC20 + SC80, PC20 + SC40 + SC40 + SC60, PC20 + SC40 + SC40 + SC80, PC20 + SC40 + SC60 + SC40, PC20 + SC40 + SC60 + SC60, PC20 + SC40 + SC60 + SC80, PC20 + SC40 + SC80 + SC20, PC20 + SC40 + SC80 + SC40, PC20 + SC40 + SC80 + SC60, PC20 + SC40 + SC80 + SC80, PC20 + SC60 + SC20 + SC60, PC20 + SC60 + SC20 + SC80, PC20 + SC60 + SC40 + SC40, PC20 + SC60 + SC40 + SC60, PC20 + SC60 + SC40 + SC80, PC20 + SC60 + SC60 + SC20, PC20 + SC60 + SC60 + SC40, PC20 + SC60 + SC60 + SC60, PC20 + SC60 + SC60 + SC80, PC20 + SC60 + SC80 + SC20, PC20 + SC60 + SC80 + SC40, PC20 + SC60 + SC80 + SC60, PC20 + SC60 + SC80 + SC80, PC20 + SC80 + SC20 + SC40, PC20 + SC80 + SC20 + SC60, PC20 + SC80 + SC20 + SC80, PC20 + SC80 + SC40 + SC20, PC20 + SC80 + SC40 + SC40, PC20 + SC80 + SC40 + SC60, PC20 + SC80 + SC40 + SC80, PC20 + SC80 + SC60 + SC20, PC20 + SC80 + SC60 + SC40, PC20 + SC80 + SC60 + SC60, PC20 + SC80 + SC60 + SC80, PC20 + SC80 + SC80 + SC20, PC20 + SC80 + SC80 + SC40, PC20 + SC80 + SC80 + SC60, PC20 + SC80 + SC80 + SC80

[0488] PC80 + SC20 + SC20 + SC40, PC80 + SC20 + SC20 + SC60, PC80 + SC20 + SC20 + SC80, PC80 + SC20 + SC40 + SC20, PC80 + SC20 + SC40 + SC40, PC80 + SC20 + SC40 + SC60, PC80 + SC20 + SC40 + SC80, PC80 + SC20 + SC60 + SC20, PC80 + SC20 + SC60 + SC40, PC80 + SC20 + SC60 + SC60, PC80 + SC20 + SC60 + SC80, PC80 + SC20 + SC80 + SC20, PC80 + SC20 + SC80 + SC40, PC80 + SC20 + SC80 + SC60, PC80 + SC20 + SC80 + SC80, PC80 + SC40 + SC20 + SC20, PC80 + SC40 + SC20 + SC40, PC80 + SC40 + SC20 + SC60, PC80 + SC40 + SC20 + SC80, PC80 + SC40 + SC40 + SC20, PC80 + SC40 + SC40 + SC40, PC80 + SC40 + SC40 + SC60, PC80 + SC40 + SC40 + SC80, PC80 + SC40 + SC60 + SC20, PC80 + SC40 + SC60 + SC40, PC80 + SC40 + SC60 + SC60, PC80 + SC40 + SC60 + SC80, PC80 + SC40 + SC80 + SC20, PC80 + SC40 + SC80 + SC40, PC80 + SC40 + SC80 + SC60, PC80 + SC40 + SC80 + SC80, PC80 + SC60 + SC20 + SC20, PC80 + SC60 + SC20 + SC40, PC80 + SC60 + SC20 + SC60, PC80 + SC60 + SC20 + SC80, PC80 + SC60 + SC40 + SC20, PC80 + SC60 + SC40 + SC40, PC80 + SC60 + SC40 + SC60, PC80 + SC60 + SC40 + SC80, PC80 + SC60 + SC60 + SC20, PC80 + SC60 + SC60 + SC40, PC80 + SC60 + SC60 + SC60, PC80 + SC60 + SC60 + SC80, PC80 + SC60 + SC80 + SC20, PC80 + SC60 + SC80 + SC40, PC80 + SC60 + SC80 + SC60, PC80 + SC60 + SC80 + SC80, PC80 + SC80 + SC20 + SC20, PC80 + SC80 + SC20 + SC40, PC80 + SC80 + SC20 + SC60,PC80 + SC80 + SC20 + SC80, PC80 + SC80 + SC40 + SC20, PC80 + SC80 + SC40 + SC40, PC80 + SC80 + SC40 + SC60, PC80 + SC80 + SC40 + SC80, PC80 + SC80 + SC60 + SC20, PC80 + SC80 + SC60 + SC40, PC80 + SC80 + SC60 + SC60, PC80 + SC80 + SC60 + SC80, PC80 + SC80 + SC80 + SC20, PC80 + SC80 + SC80 + SC40, PC80 + SC80 + SC80 + SC60 PC80 + SC80 + SC80 + SC80 (or 2x996 + 2x996 RU or 996 + 996 + 2x996 RU or 996 + 3x996 RU or 996 + 996 + 996 + 996RU)

[0489] 4.4.2. 240 / 160 + 80MHz Channel Configuration Case 2

[0490] At least one of the 20MHz channels of L80 cannot be punctured, and thus, the RU combinations in S80 proposed in 4.2. can be used as they are. If at least one 20MHz in S80 or H80 is not punctured, the RU combinations in S80 proposed in 4.2. can be used as they are. Therefore, the combinations of various RUs in the entire bandwidth are the same as those proposed in 4.4.1.

[0491] 4.4.3. 240 / 160 + 80MHz Channel Configuration Case 3

[0492] At least one of the 20MHz channels of L80 should not be punctured, and thus, the RU combinations in S80 proposed in 4.2. can be used as they are. Additionally, at least one 20MHz in S160 must not be punctured, which means that one 20MHz in the 80MHz of L80 or H80 does not have to be punctured, and the other 80MHz can be punctured or not punctured. Therefore, when at least one 20MHz within the 80MHz of S80 or L80 is not punctured, and in both S80 and L80, if at least one 20MHz within the 80MHz is not punctured, the combinations of various RUs in the entire bandwidth are the same as the proposed combinations among the RU combinations proposed in 4.4.1.

[0493] The following summarizes various RU combinations, and the order and position of RUs in each combination can be changed. The meaning of the parentheses refers to the RU combination of each 80MHz. That is, the order and position of RUs can be changed within the parentheses (i.e., within each 80MHz), and the order and position of the parentheses can also be changed (i.e., the position and sequence diagram of each 80MHz).

[0494] (996)+(996) / 2x996

[0495] (242)+(484 + 242)+(996), (242)+(996)+(996), (242 + 242)+(242 + 242)+(996), (242 + 242)+(448)+(996), (448)+(448)+(996), (242 + 242)+(484 + 242)+(484 + 242), (484)+(484 + 242)+(484 + 242), (242 + 242)+(484 + 242)+(996), (484)+(484 + 242)+(996), (242 + 242)+(996)+(996), (484)+(996)+(996), (484 + 242)+(484 + 242)+(484 + 242), (484 + 242)+(484 + 242)+(996), (484 + 242)+(996)+(996), (996)+(996)+(996) / 2x996 + 996 / 3x996

[0496] (242)+(242)+(242+242)+(996)、(242)+(242)+(484)+(996)、(242)+(242)+(484+242)+(484+242)、(242)+(242)+(484+242)+(996)、(242)+(242)+(996)+(996)、(242)+(242+242)+(242+242)+(484+242)、(242)+(242+242)+(484)+(484+242)、(242)+(484)+(484)+(484+242)、(242)+(242+242)+(242+242)+(996)、(242)+(242+242)+(484)+(996)、(242)+(484)+(484)+(996)、(242)+(242+242)+(484+242)+(484+242)、(242)+(484)+(484+242)+(484+242)、(242)+(242+242)+(484+242)+(996)、(242)+(484)+(484+242)+(996)、(242)+(242+242)+(996)+(996)、(242)+(484)+(996)+(996)、(242)+(484+242)+(484+242)+(484+242)、(242)+(484+242)+(484+242)+(996)、(242)+(484+242)+(996)+(996)、(242)+(996)+(996)+(996)、(242+242)+(242+242)+(242+242)+(242+242)、(242+242)+(242+242)+(242+242)+(484)、(242+242)+(242+242)+(484)+(484)、(242+242)+(484)+(484)+(484)、(484)+(484)+(484)+(484)、(242+242)+(242+242)+(242+242)+(484+242)、(242+242)+(242+242)+(484)+(484+242)、(242+242)+(484)+(484)+(484+242)、(484)+(484)+(484)+(484+242)、(242+242)+(242+242)+(242+242)+(996)、(242+242)+(242+242)+(484)+(996)、(242 + 242) + (484) + (484) + (996), (484) + (484) + (484) + (996), (242 + 242) + (242 + 242) + (484 + 242) + (484 + 242), (242 + 242) + (484) + (484 + 242) + (484 + 242), (484) + (484) + (484 + 242) + (484 + 242), (242 + 242) + (242 + 242) + (484 + 242) + (996), (242 + 242) + (484) + (484 + 242) + (996), (484) + (484) + (484 + 242) + (996), (242 + 242) + (242 + 242) + (996) + (996), (242 + 242) + (484) + (996) + (996), (484) + (484) + (996) + (996), (242 + 242) + (484 + 242) + (484 + 242) + (484 + 242), (484) + (484 + 242) + (484 + 242) + (484 + 242), (242 + 242) + (484 + 242) + (484 + 242) + (996), (484) + (484 + 242) + (484 + 242) + (996), (242 + 242) + (484 + 242) + (996) + (996), (484) + (484 + 242) + (996) + (996), (242 + 242) + (996) + (996) + (996), (484) + (996) + (996) + (996), (484 + 242) + (484 + 242) + (484 + 242) + (484 + 242), (484 + 242) + (484 + 242) + (484 + 242) + (996), (484 + 242) + (484 + 242) + (996) + (996), (484 + 242) + (996) + (996) + (996), (996) + (996) + (996) + (996) / 996 + 996 + 2 x 996 / 2 x 996 + 2 x 996 / 996 + 3 x 996 / 4 x 996,

[0497] Specifically, it is possible to consider only (484)+(996)+(996)+(996) where only one continuous 40 MHz is punctured and (996)+(996)+(996) where only one continuous 80 MHz is punctured. Additionally, it is possible to consider only (484+242)+(484+242)+(996)+(996) where only one continuous 40 MHz is punctured (in the case where the continuous 40 MHz puncture is at the boundary between two specific 80 MHz), (242)+(996)+(996)+(996) where only one continuous 60 MHz is punctured (in the case where the continuous 60 MHz puncture is at the boundary between two specific 80 MHz), (484)+(484+242)+(996)+(996), (484)+(484)+(996)+(996), and (484)+(484)+(996)+(996) and (242)+(484+242)+(996)+(996) where only one continuous 80 MHz is punctured (in the case where the continuous 80 MHz puncture is at the boundary between two specific 80 MHz). Furthermore, (242+242)+(996)+(996)+(996) where only one continuous 40 MHz is punctured (in the case of continuous 40 MHz starting from the center of a specific 80 MHz, i.e., when two central 20 MHz are punctured) can be additionally considered.

[0498] Combinations where only one continuous 40, 60, or 80 MHz is punctured in each primary and secondary 160 can be considered. For example, there may be combinations such as (484)+(996)+(484)+(996), (484)+(996)+(484+242)+(484+242), (484)+(996)+(242+242)+(996), (484+242)+(484+242)+(484+242)+(484+242), (484+242)+(484+242)+(242+242)+(996), (242+242)+(996)+(242+242)+(996), (242)+(996)+(242)+(996), (242)+(996)+(484)+(484+242), (484)+(484+242)+(484)+(484+242), (996)+(996), (996)+(484)+(484), (996)+(242)+(484+242), (484)+(484)+(484)+(484), (484)+(484)+(242)+(484+242), (242)+(484+242)+(242)+(484+242).

[0499] As another example, combinations such as (484)+(996)+(242)+(996), (484)+(996)+(484)+(484+242), (484+242)+(484+242)+(242)+(996), (484+242)+(484+242)+(484)+(484+242), (242+242)+(996)+(242)+(996), (242+242)+(996)+(484)+(484+242) may exist.

[0500] Combinations such as (484)+(996)+(996), (484)+(996)+(484)+(484), (484)+(996)+(242)+(484+242), (484+242)+(484+242)+(996), (484+242)+(484+242)+(484)+(484), (484+242)+(484+242)+(242)+(484+242), (242+242)+(996)+(996), (242+242)+(996)+(484)+(484), (242+242)+(996)+(242)+(484+242) may exist.

[0501] Combinations such as (242)+(996)+(996), (242)+(996)+(484)+(484), (242)+(996)+(242)+(484+242), (484)+(484+242)+(996), (484)+(484+242)+(484)+(484), (484)+(484+242)+(242)+(484+242) may exist.

[0502] Next, a method for indicating or scheduling the above punching patterns and RU aggregation is proposed.

[0503] 4.5. Signaling method

[0504] Figure 30 An example of the EHT PPDU format is shown.

[0505] Figure 31 An example of the U-SIG format is shown.

[0506] The above indicator for RU aggregation can be sent within the EHT-SIG of the Figure 30 EHT PPDU or within the Figure 31 U-SIG.

[0507] Figure 31 The version - independent fields can include a 3 - bit version identifier indicating Wi - Fi versions after 802.11be, a 1 - bit DL / UL field, BSS color, TXOP duration, etc. Figure 31 The version - related fields can include information such as PPDU type and bandwidth.

[0508] In U - SIG, two symbols are jointly encoded, and each 20 MHz consists of 52 data tones and 4 pilot tones. In addition, U - SIG is modulated in the same way as HE - SIG - A. That is, U - SIG is modulated at a BPSK 1 / 2 code rate.

[0509] EHT - SIG can be divided into common fields and user - specific fields, can be encoded with variable MCS, and can indicate information about the exact puncturing pattern and RU aggregation for transmission in the common fields. In addition, in order to indicate whether to apply a shifted tone plan in adjacent 20 MHz channels, or change to a 20 MHz tone plan, or whether to use the tone plan as it is but puncture some tones or transmit some tones at low power when applying preamble puncturing, one - bit information can be sent in the version - related fields of U - SIG or the common fields of EHT - SIG.

[0510] Figure 32 is a process flow chart illustrating the operation of the transmitting device according to this embodiment.

[0511] Figure 32 Examples of can be executed by a transmitting device (AP and / or non - AP STA). For example, Figure 24 Examples of can be executed by an AP transmitting an EHT SU PPDU, an EHT ER SU PPDU, or an EHT MU PPDU. Figure 32 Examples of can be executed by a non - AP transmitting an EHTSU PPDU, an EHT ER SU PPDU, and an EHT MU PPDU.

[0512] Figure 32 Some steps in each step (or the detailed sub - steps to be described later) of the examples of can be omitted or changed.

[0513] In step S3210, the transmitting device (i.e., the transmitting STA) configures the bandwidth (BW) and RU allocation, and allocates multiple RUs to a specific user or STA through the multi - RU aggregation combination in paragraph 4.2 of the above description. In addition, the transmitting device can perform a channel access operation.

[0514] In step S3220, the transmitting STA may configure the PPDU. For example, the PPDU may be an EHT SU PPDU, an EHT ERSU PPDU, or an EHT MU PPDU. The PPDU may include an EHT-SIG as shown in Figure 18 .

[0515] The transmitting STA may perform step S3220 based on the BW, RU allocation, and multi-RU aggregation determined in step S3210.

[0516] That is, as described above, information of a specific (RU allocation) n bits (e.g., 8 bits) may be included in the common field of the EHT-SIG, and information regarding multi-RU aggregation may be included in the user-specific field.

[0517] In step S3230, the transmitting device may send the PPDU configured in step S3220 to the receiving device based on step S3230.

[0518] When performing step S3230, the transmitting device may perform at least one of CSD, spatial mapping, IDFT / IFFT operations, GI insertion, etc.

[0519] The signal / field / sequence constructed according to this specification may be sent in the form of Figure 18 .

[0520] For example, the above EHT-SIG may be sent based on several OFDM symbols. For example, one OFDM symbol may include 26 bits of information. The 26 bits of information may include the above 4-bit BW information. Any m bits of information may be used instead of the 26 bits of information.

[0521] For the 26 bits of information, BCC coding with a 1 / 2 low efficiency may be applied. Interleaving by an interleaver may be applied to the bits compiled by BCC (i.e., 52 bits). Mapping by a constellation mapper may be performed on the interleaved 52 bits. Specifically, a BPSK module may be applied to generate 52 BPSK symbols. The 52 BSPK symbols may be mapped to the remaining frequency domain (-28 to +28) except for the DC tone and pilot tones (-21, -7, +7, +21) tones. Thereafter, it may be sent to the receiving STA through phase rotation, CSD, spatial mapping, IDFT / IFFT operations, etc.

[0522] The above PPDU may be sent based on the device of Figure 1 .

[0523] Figure 1 The example of

[0524] As Figure 1 shown, the transmitting device (or transmitter) may include a memory 112, a processor 111, and a transceiver 113.

[0525] The memory 112 may store information about a plurality of tone schedules / RUs described in this specification.

[0526] The processor 111 may generate various RUs and configure the PPDU based on the information stored in the memory 112. An example of the PPDU generated by the processor 111 may be as Figure 18 shown.

[0527] The processor 111 may perform Figure 32 all / part of the operations shown.

[0528] The illustrated transceiver 113 includes an antenna and may perform analog signal processing. Specifically, the processor 111 may control the transceiver 113 to transmit the PPDU generated by the processor 111.

[0529] Alternatively, the processor 111 may generate a transmission PPDU and store information about the transmission PPDU in the memory 112.

[0530] Figure 33 is a process flowchart illustrating the operation of the receiving device according to this embodiment.

[0531] Figure 33 Examples of may be performed in the receiving device (AP and / or non-AP STA).

[0532] Figure 33 Examples of may be performed by the receiving device (AP and / or non-AP STA). For example, Figure 33 examples of may be performed by a non-AP that receives an EHT SU PPDU, an EHT ER SU PPDU, or an EHT MU PPDU. Figure 33 Examples of may be performed by an AP that transmits an EHT SU PPDU, an EHT ER SU PPDU.

[0533] Figure 33 Some steps in each step of the example of (or the detailed sub-steps to be described later) may be omitted.

[0534] In step S3310, the receiving device (receiving STA) may receive all or part of the PPDU through step S3310. The received signal may be in the form of Figure 18 shown.

[0535] The sub-steps of step S3310 may be based on Figure 32Determined by step S3230 of. That is, in step S3310, operations can be performed to restore the results of the CSD, spatial mapping, IDFT / IFFT operations, and GI insertion operations applied in step S3230.

[0536] In step S3320, the receiving STA can obtain information about the BW, RU allocation, and multi-RU aggregation of the EHT PPDU by decoding the information included in the U-SIG or EHT-SIG.

[0537] By doing so, the receiving STA can complete the decoding of other fields / symbols of the received PPDU.

[0538] As a result, the receiving STA can decode the data field included in the PPDU through step S3320. Thereafter, the receiving STA can perform a processing operation of transmitting the data decoded from the data field to a higher layer (e.g., the MAC layer). In addition, when a signal generation is indicated from the upper layer to the PHY layer in response to the data transmitted to the upper layer, subsequent operations can be performed.

[0539] The above PPDU can be based on Figure 1 the device of.

[0540] As Figure 1 shown in, the receiving device can include a memory 112, a processor 111, and a transceiver 113.

[0541] The transceiver 123 can receive the PPDU based on the control of the processor 121. For example, the transceiver 123 can include a plurality of sub-units (not shown). For example, the transceiver 123 can include at least one receiving antenna and a filter for the corresponding receiving antenna.

[0542] The PPDU received through the transceiver 123 can be stored in the memory 122. The processor 121 can process the decoding of the PPDU received through the memory 122. The processor 121 can obtain control information (e.g., EHT-SIG) about the tone plan / RU included in the PPDU and store the obtained control information in the memory 122.

[0543] The processor 121 can perform decoding on the received PPDU. Specifically, operations can be performed to restore the results of the CSD, spatial mapping, IDFT / IFFT operations, and GI insertion applied to the PPDU. The operations of CSD, spatial mapping, IDFT / IFFT operations, and restoring the results of GI insertion can be performed by a plurality of processing units (not shown) separately implemented in the processor 121.

[0544] In addition, the processor 121 may decode the data field of the PPDU received through the transceiver 123.

[0545] In addition, the processor 121 may process the decoded data. For example, the processor 121 may perform a processing operation of transmitting information about the decoded data field to an upper layer (e.g., the MAC layer). In addition, subsequent operations may be performed when a signal generation is indicated from the upper layer to the PHY layer in response to the data transmitted to the upper layer.

[0546] Hereinafter, reference will be made to Figures 1 to 33 describe the foregoing embodiments.

[0547] Figure 34 is a flowchart illustrating a process in which a transmitting STA transmits a PPDU according to the present embodiment.

[0548] may be performed in a network environment supporting a next-generation wireless LAN system (e.g., IEEE 802.11be or an EHT wireless LAN system) Figure 34 example. The next-generation wireless LAN system is a wireless LAN system improved from the 802.11ax system and may satisfy backward compatibility with the 802.11ax system.

[0549] Figure 34 example is performed by a transmitting STA, and the transmitting STA may correspond to an access point (AP). Figure 34 The receiving STA of

[0550] This embodiment proposes a method and apparatus for transmitting and receiving a PPDU based on a plurality of RUs configured by a combination between large RUs. In this case, a large RU means a resource unit having more than 242 tones. In particular, this embodiment proposes a method of configuring a plurality of RUs for transmitting a PPDU in a non-OFDMA scheme.

[0551] In step S3410, a transmitting station (STA) generates a physical protocol data unit (PPDU).

[0552] In step S3420, the transmitting STA transmits the PPDU to the receiving STA through a wideband.

[0553] The PPDU includes a control field and a data field.

[0554] When the wideband is a 320 / 160+160 MHz band including first to fourth 80 MHz sub-channels, the first 80 MHz sub-channel includes a first 996 resource units (RUs), and the second 80 MHz sub-channel includes a second 996 RUs, the third 80 MHz sub-channel includes a third 996 RUs, and the fourth 80 MHz sub-channel includes a first 484 RUs.

[0555] The data field is received through a first plurality of RUs in which the first to third 996 RUs and the first 484 RUs are aggregated. That is, the data field can be received through a plurality of RUs in which three 996 RUs and one 484 RU are aggregated. As described above, the wideband can include four 80 MHz sub-channels. The three 996 RUs and one 484 RU can be respectively allocated to each of the four 80 MHz sub-channels. In this case, the first to third 996 RUs can be RUs composed of 996 tones, and the first 484 RU can be an RU composed of 484 tones.

[0556] The PPDU can be transmitted based on a non-orthogonal frequency division multiple access (OFDMA) scheme.

[0557] The first plurality of RUs can be obtained by puncturing the 484 RUs in the fourth 80 MHz sub-channel. In this case, since only the first 484 RUs are used in the fourth 80 MHz sub-channel, it can be seen that the remaining 484 RUs (or a continuous 40 MHz band) are punctured.

[0558] The control field can include allocation information about the first plurality of RUs. The receiving STA can decode the allocation information about the first plurality of RUs and confirm that the first plurality of RUs are the RUs allocated to itself.

[0559] One of the first to fourth 80 MHz sub-channels can be a primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel can be secondary 80 MHz channels (specifically, a secondary 80 MHz channel, a lower 80 MHz channel of a secondary 160 MHz, and a higher 80 MHz channel of a secondary 160 MHz). The primary 80 MHz channel and the secondary 80 MHz channels can be configured regardless of the frequency size. Here, the primary 80 MHz channel can include a primary 20 MHz channel, a secondary 20 MHz channel, and a secondary 40 MHz channel. The primary 20 MHz channel is not (always) punctured.

[0560] As another example, when the wideband is a 320 / 160+160 MHz band including fifth to eighth 80 MHz sub-channels, the fifth 80 MHz sub-channel can include a fourth 996 RUs, the sixth 80 MHz sub-channel can include a fifth 996 RUs, and the seventh 80 MHz sub-channel can include a sixth 996 RUs.

[0561] The data field can be received via a second plurality of RUs in which the fourth to sixth 996 RUs are aggregated. That is, the data field can be received via a plurality of RUs in which three 996 RUs are aggregated. As described above, the wideband can include four 80 MHz sub-channels. Three 996 RUs can be allocated to each of the remaining three 80 MHz sub-channels except for one punctured 80 MHz sub-channel. In this case, the fourth to sixth 996 RUs can be RUs composed of 996 tones.

[0562] The second plurality of RUs is obtained by puncturing the eighth 80 MHz sub-channel. This indicates that the eighth 80 MHz sub-channel is punctured because it is not used when transmitting the data field.

[0563] The control field can include allocation information regarding the second plurality of RUs. The receiving STA can decode the allocation information regarding the second plurality of RUs and confirm that the second plurality of RUs are the RUs allocated to itself.

[0564] One of the fifth to eighth 80 MHz sub-channels can be the primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel can be secondary 80 MHz channels (specifically, a secondary 80 MHz channel, a lower 80 MHz channel of a secondary 160 MHz, and a higher 80 MHz channel of a secondary 160 MHz). The primary 80 MHz channel and the secondary 80 MHz channels can be configured regardless of the frequency size. Here, the primary 80 MHz channel is not (always) punctured.

[0565] As another example, when the wideband is a 320 / 160+160 MHz band including the fifth to eighth 80 MHz sub-channels, the fifth 80 MHz sub-channel can include the fourth 996 RU, the sixth 80 MHz sub-channel can include the fifth 996 RU, and the seventh 80 MHz sub-channel can include the second 484 RU.

[0566] The data field can be received via a third plurality of RUs in which the fourth to fifth 996 RUs and the second 484 RU are aggregated. That is, the data field can be received via a plurality of RUs in which two 996 RUs and one 484 RU are aggregated. As described above, the wideband can include four 80 MHz sub-channels. Two 996 RUs and one 484 RU can be respectively allocated to each of the other three 80 MHz sub-channels except for one punctured 80 MHz sub-channel. In this case, the fourth to fifth 996 RUs can be RUs composed of 996 tones, and the second 484 RU can be an RU composed of 484 tones.

[0567] The third plurality of RUs can be obtained by puncturing 484 RUs in the seventh 80 MHz sub-channel and puncturing the eighth 80 MHz sub-channel. This is because the eighth 80 MHz sub-channel is not used when transmitting the data field, so it can be seen that the eighth 80 MHz sub-channel is punctured, and only the second 484 RUs are used in the seventh 80 MHz sub-channel, and it can be seen that the remaining 484 RUs (or a continuous 40 MHz frequency band) are punctured.

[0568] The control field may include allocation information about the third plurality of RUs. The receiving STA can decode the allocation information about the third plurality of RUs and confirm that the second plurality of RUs are the RUs allocated to itself.

[0569] One of the fifth to eighth 80 MHz sub-channels may be the primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel may be secondary 80 MHz channels (specifically, the secondary 80 MHz channel, the lower 80 MHz channel of the secondary 160 MHz, and the upper 80 MHz channel of the secondary 160 MHz). The primary 80 MHz channel and the secondary 80 MHz channels can be configured regardless of the frequency size. Here, the primary 80 MHz channel may include a primary 40 MHz channel and a secondary 40 MHz channel. The primary 40 MHz channel or the primary 80 MHz channel is not punctured.

[0570] This embodiment proposes a method for configuring a plurality of RUs (large RU combinations) for transmitting a PPDU in a 320 / 160+160 MHz frequency band in a non-OFDMA scheme.

[0571] In addition, this embodiment may propose a method for configuring a plurality of RUs (large RU combinations) for transmitting a PPDU in an 80 MHz frequency band in a non-OFDMA scheme. In this case, the 80 MHz frequency band may include first to second 20 MHz sub-channels and a first 40 MHz sub-channel. One of the first and second 20 MHz sub-channels may include 242 RUs, and the first 40 MHz sub-channel may include 484 RUs. The data field may be received through a plurality of RUs in which 242 RUs and 484 RUs are aggregated. The plurality of RUs can be obtained by puncturing one of the first and second 20 MHz sub-channels.

[0572] In addition, this embodiment may propose a method for configuring a plurality of RUs (large RU combinations) for transmitting a PPDU in a 160 / 80+80 MHz frequency band in a non-OFDMA scheme.

[0573] First, the 160 / 80 + 80 MHz band may include first to second 40 MHz sub-channels and a first 80 MHz sub-channel. One of the first and second 40 MHz sub-channels may include 484 RUs, and the first 80 MHz sub-channel may include 996 RUs. A data field may be received through a plurality of RUs aggregating 484 RUs and 996 RUs. Multiple RUs may be obtained by puncturing one of the first and second 40 MHz sub-channels.

[0574] In addition, the 160 / 80 + 80 MHz band may include first and second 20 MHz sub-channels, a first 40 MHz sub-channel, and a first 80 MHz sub-channel. One of the first and second 20 MHz sub-channels may include 242 RUs, the first 40 MHz sub-channel may include 484 RUs, and the first 80 MHz sub-channel may include 996 RUs. A data field may be received through a plurality of RUs aggregating 242 RUs, 484 RUs, and 996 RUs. Multiple RUs may be obtained by puncturing one of the first and second 20 MHz sub-channels.

[0575] The control field includes a first control field supporting a legacy wireless LAN system and a second control field supporting an 802.11be wireless LAN system. The second control field may include a Universal Signal (U-SIG) or an Extremely High Throughput Signal (EHT-SIG). The second control field may include allocation information regarding the RUs to which the data field will be sent. This embodiment describes a case where the RUs to which the data field is sent are multiple RUs in which a plurality of RUs are aggregated with each other. An RU means a resource unit in which a data field is sent.

[0576] The EHT-SIG may include EHT-SIG-A and EHT-SIG-B (or EHT-SIG-C field). The EHT-SIG-B may include Resource Unit (RU) information. A transmitting STA may notify information regarding the tone plan of a wideband through the EHT-SIG-B. In addition, the EHT-STF, EHT-LTF, and the data field included in the second control field may be transmitted / received through a plurality of RUs included in the tone plan of the wideband.

[0577] Figure 35 is a flowchart illustrating a process in which a receiving STA receives a PPDU according to this embodiment.

[0578] Figure 35 Examples of may be executed in a network environment supporting a next-generation wireless LAN system (e.g., IEEE 802.11be or EHT wireless LAN system). The next-generation wireless LAN system is a wireless LAN system improved from an 802.11ax system and may satisfy backward compatibility with the 802.11ax system.

[0579] Figure 35 Examples of this are performed by the transmitting STA, and the transmitting STA can correspond to an access point (AP). Figure 35 The receiving STA of this can correspond to an STA supporting an extremely high throughput (EHT) WLAN system.

[0580] This embodiment proposes a method and apparatus for transmitting and receiving a PPDU based on a plurality of RUs, which are configured by combining between large RUs. In this case, a large RU means a resource unit having more than 242 tones. In particular, this embodiment proposes a method for configuring a plurality of RUs for transmitting a PPDU in a non-OFDMA scheme.

[0581] In step S3510, a receiving station (STA) receives a physical protocol data unit (PPDU) from a transmitting STA over a wideband.

[0582] In step S3520, the receiving STA decodes the PPDU.

[0583] The PPDU includes a control field and a data field.

[0584] When the wideband is a 320 / 160+160 MHz band including first to fourth 80 MHz sub-channels, the first 80 MHz sub-channel includes a first 996 resource unit (RU), and the second 80 MHz sub-channel includes a second 996 RU, the third 80 MHz sub-channel includes a third 996 RU, and the fourth 80 MHz sub-channel includes a first 484 RU.

[0585] The data field is received through a first plurality of RUs in which the first to third 996 RUs and the first 484 RU are aggregated. That is, the data field can be received through a plurality of RUs in which three 996 RUs and one 484 RU are aggregated. As described above, the wideband can include four 80 MHz sub-channels. The three 996 RUs and one 484 RU can be respectively assigned to each of the four 80 MHz sub-channels. In this case, the first to third 996 RUs can be RUs composed of 996 tones, and the first 484 RU can be an RU composed of 484 tones.

[0586] The PPDU can be transmitted based on a non-orthogonal frequency division multiple access (OFDMA) scheme.

[0587] The first plurality of RUs can be obtained by puncturing the 484 RU in the fourth 80 MHz sub-channel. In this case, since only the first 484 RU is used in the fourth 80 MHz sub-channel, it can be seen that the remaining 484 RUs (or a continuous 40 MHz band) are punctured.

[0588] The control field may include allocation information regarding the first plurality of RUs. The receiving STA can decode the allocation information of the first plurality of RUs and confirm that the first plurality of RUs are the RUs allocated to itself.

[0589] One of the first to fourth 80 MHz sub-channels may be the primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel may be secondary 80 MHz channels (specifically, the secondary 80 MHz channel, the lower 80 MHz channel of the secondary 160 MHz, and the higher 80 MHz channel of the secondary 160 MHz). The primary 80 MHz channel and the secondary 80 MHz channels can be configured regardless of the frequency size. Here, the primary 80 MHz channel may include the primary 20 MHz channel, the secondary 20 MHz channel, and the secondary 40 MHz channel. The primary 20 MHz channel is not (always) punctured.

[0590] As another example, when the wideband is a 320 / 160 + 160 MHz band including the fifth to eighth 80 MHz sub-channels, the fifth 80 MHz sub-channel may include the fourth 996 RUs, the sixth 80 MHz sub-channel may include the fifth 996 RUs, and the seventh 80 MHz sub-channel may include the sixth 996 RUs.

[0591] The data field may be received through a second plurality of RUs in which the fourth to sixth 996 RUs are aggregated. That is, the data field may be received through a plurality of RUs in which three 996 RUs are aggregated. As described above, the wideband may include four 80 MHz sub-channels. The three 996 RUs may be allocated to each of the remaining three 80 MHz sub-channels except for one punctured 80 MHz sub-channel. In this case, the fourth to sixth 996 RUs may be RUs composed of 996 tones.

[0592] The second plurality of RUs is obtained by puncturing the eighth 80 MHz sub-channel. This indicates that the eighth 80 MHz sub-channel is punctured because the eighth 80 MHz sub-channel is not used when transmitting the data field.

[0593] The control field may include allocation information regarding the second plurality of RUs. The receiving STA can decode the allocation information regarding the second plurality of RUs and confirm that the second plurality of RUs are the RUs allocated to itself.

[0594] One of the fifth to eighth 80 MHz sub-channels may be the primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel may be secondary 80 MHz channels (specifically, the secondary 80 MHz channel, the lower 80 MHz channel of the secondary 160 MHz, and the higher 80 MHz channel of the secondary 160 MHz). The primary 80 MHz channel and the secondary 80 MHz channels can be configured regardless of the frequency size. Here, the primary 80 MHz channel is not (always) punctured.

[0595] As another example, when the wideband is a 320 / 160+160 MHz band including the fifth to eighth 80 MHz sub-channels, the fifth 80 MHz sub-channel may include the fourth 996 RUs, the sixth 80 MHz sub-channel may include the fifth 996 RUs, and the seventh 80 MHz sub-channel may include the second 484 RUs.

[0596] The data field may be received through a third plurality of RUs in which the fourth to fifth 996 RUs and the second 484 RUs are aggregated. That is, the data field may be received through a plurality of RUs in which two 996 RUs and one 484 RU are aggregated. As described above, the wideband may include four 80 MHz sub-channels. Two 996 RUs and one 484 RU may be respectively assigned to each of the other three 80 MHz sub-channels except for one punctured 80 MHz sub-channel. In this case, the fourth to fifth 996 RUs may be RUs composed of 996 tones, and the second 484 RU may be an RU composed of 484 tones.

[0597] The third plurality of RUs may be obtained by puncturing 484 RUs in the seventh 80 MHz sub-channel and puncturing the eighth 80 MHz sub-channel. This is because the eighth 80 MHz sub-channel is not used when transmitting the data field, so it can be seen that the eighth 80 MHz sub-channel is punctured, and only the second 484 RUs are used in the seventh 80 MHz sub-channel, and it can be seen that the remaining 484 RUs (or a continuous 40 MHz band) are punctured.

[0598] The control field may include allocation information about the third plurality of RUs. The receiving STA may decode the allocation information of the third plurality of RUs and confirm that the second plurality of RUs are the RUs assigned to itself.

[0599] One of the fifth to eighth 80 MHz sub-channels may be a primary 80 MHz channel, and the remaining three sub-channels except the primary 80 MHz channel may be secondary 80 MHz channels (specifically, a secondary 80 MHz channel, a lower 80 MHz channel of the secondary 160 MHz, and a higher 80 MHz channel of the secondary 160 MHz). The primary 80 MHz channel and the secondary 80 MHz channels may be configured regardless of the frequency size. Here, the primary 80 MHz channel may include a primary 40 MHz channel and a secondary 40 MHz channel. The primary 40 MHz channel or the primary 80 MHz channel is not punctured.

[0600] This embodiment proposes a method for configuring a plurality of RUs (large RU combinations) for transmitting a PPDU in a 320 / 160+160 MHz band in a non-OFDMA scheme.

[0601] In addition, this embodiment may propose a method for configuring a plurality of RUs (large RU combinations) for transmitting a PPDU in an 80 MHz frequency band using a non-OFDMA scheme. In this case, the 80 MHz frequency band may include first to second 20 MHz sub-channels and a first 40 MHz sub-channel. One of the first and second 20 MHz sub-channels may include 242 RUs, and the first 40 MHz sub-channel may include 484 RUs. The data field may be received through a plurality of RUs in which 242 RUs and 484 RUs are aggregated. The plurality of RUs may be obtained by puncturing one of the first and second 20 MHz sub-channels.

[0602] In addition, this embodiment may propose a method for configuring a plurality of RUs (large RU combinations) for transmitting a PPDU in a 160 / 80+80 MHz frequency band using a non-OFDMA scheme.

[0603] First, the 160 / 80+80 MHz frequency band may include first to second 40 MHz sub-channels and a first 80 MHz sub-channel. One of the first and second 40 MHz sub-channels may include 484 RUs, and the first 80 MHz sub-channel may include 996 RUs. The data field may be received through a plurality of RUs aggregating 484 RUs and 996 RUs. The multi-RU may be obtained by puncturing one of the first and second 40 MHz sub-channels.

[0604] In addition, the 160 / 80+80 MHz frequency band may include first and second 20 MHz sub-channels, a first 40 MHz sub-channel, and a first 80 MHz sub-channel. One of the first and second 20 MHz sub-channels may include 242 RUs, the first 40 MHz sub-channel may include 484 RUs, and the first 80 MHz sub-channel may include 996 RUs. The data field may be received through a plurality of RUs aggregating 242 RUs, 484 RUs, and 996 RUs. The plurality of RUs may be obtained by puncturing one of the first and second 20 MHz sub-channels.

[0605] The control field includes a first control field supporting a legacy wireless LAN system and a second control field supporting an 802.11be wireless LAN system. The second control field may include a Universal Signal (U-SIG) or an Extremely High Throughput Signal (EHT-SIG). The second control field may include allocation information regarding the RUs to which the data field will be transmitted. This embodiment describes the case where the RUs to which the data field is transmitted are multi-RUs in which a plurality of RUs are aggregated with each other. An RU means a resource unit in which a data field is transmitted.

[0606] The EHT-SIG may include EHT-SIG-A and EHT-SIG-B (or the EHT-SIG-C field). The EHT-SIG-B may include resource unit (RU) information. The transmitting STA may notify information about the tone plan of the wideband through the EHT-SIG-B. In addition, the EHT-STF, EHT-LTF, and the data field included in the second control field may be transmitted / received by multiple RUs included in the tone plan of the wideband.

[0607] 5. Device / Equipment Configuration

[0608] The technical features of the present specification described above can be applied to various devices and methods. For example, the above technical features of the present specification can be implemented / supported by Figure 1 and / or Figure 19 devices. For example, the above technical features of the present specification can be applied only to Figure 1 and / or Figure 19 a part of. For example, the above technical features of the present specification are implemented based on Figure 1 processing chips 114 and 124, or based on Figure 1 processors 111 and 121 and memories 112 and 122, or can be implemented based on Figure 19 processors 610 and memories 620. For example, the device of the present specification can receive a physical protocol data unit (PPDU) from a transmitting STA through a wideband; and decode the PPDU.

[0609] The technical features of the present specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed in the present specification is at least one computer-readable medium, including at least one computer-readable medium, which includes instructions based on being executed by at least one processor.

[0610] The CRM can store instructions for performing operations, including: receiving a physical protocol data unit (PPDU) from a transmitting STA through a wideband; and decoding the PPDU. The instructions stored in the CRM of the present specification can be executed by at least one processor. The at least one processor related to the CRM in the present specification can be Figure 1 processors 111 and 121 or processing chips 114 and 124, or Figure 19 processor 610. At the same time, the CRM of the present specification can be Figure 1 memories 112 and 122, Figure 19 memories 620, or a separate external memory / storage medium / disk.

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

[0612] Artificial intelligence refers to the field of study related to artificial intelligence or methods for creating artificial intelligence, while machine learning refers to the field of study related to methods for defining and solving various problems in the field of artificial intelligence. Machine learning is also defined as an algorithm that improves operational performance through a stable operational experience.

[0613] An artificial neural network (ANN) is a model used in machine learning and can refer to a model for overall problem-solving, including artificial neurons (nodes) that form a network by combining synapses. An artificial neural network can be defined by the connection pattern between neurons in different layers, the learning process for updating model parameters, and the activation function for generating output values.

[0614] An artificial neural network can include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and an artificial neural network can include synapses that connect the neurons. In an artificial neural network, each neuron can output the function value of the activation function of the input signal input through the synapse, weight, and bias.

[0615] Model parameters refer to parameters determined through learning and include the weights of synapse connections and the biases of neurons. Hyperparameters refer to parameters to be set before learning in machine learning algorithms and include the learning rate, number of iterations, mini-batch size, and initialization function.

[0616] Learning an artificial neural network may aim to determine model parameters for minimizing a loss function. The loss function can be used as a metric for determining the optimal model parameters during the process of learning an artificial neural network.

[0617] Machine learning can be divided into supervised learning, unsupervised learning, and reinforcement learning.

[0618] Supervised learning refers to a method of training an artificial neural network using labels given to training data, where when the training data is input into the artificial neural network, the label can indicate the correct answer (or result value) that the artificial neural network needs to infer. Unsupervised learning can refer to a method of training an artificial neural network without labels given to the training data. Reinforcement learning can refer to a training method for training an agent defined in an environment to select actions or sequences of actions to maximize the cumulative reward in each state.

[0619] Machine learning implemented using a deep neural network (DNN) including multiple hidden layers in an artificial neural network is called deep learning, and deep learning is part of machine learning. Hereinafter, machine learning is explained to include deep learning.

[0620] The foregoing technical features can be applied to wireless communication of a robot.

[0621] A robot can refer to a machine that automatically processes or operates a given task using its own capabilities. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation can be called an intelligent robot.

[0622] According to the use or field, robots can be classified into industrial, medical, household, military robots, etc. A robot can include an actuator or a driver including a motor to perform various physical operations, such as moving a robot joint. In addition, a mobile robot can include wheels, brakes, propellers, etc. in the driver to travel on the ground or fly in the air through the driver.

[0623] The foregoing technical features can be applied to a device that supports extended reality.

[0624] Extended reality is collectively referred to as virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphics technology that provides real-world objects and backgrounds only in CG images, AR technology is a computer graphics technology that provides virtual CG images on real object images, and MR technology is a computer graphics technology that provides virtual objects mixed and combined with the real world.

[0625] MR technology is similar to AR technology in that real objects and virtual objects can be displayed together. However, in AR technology, virtual objects are used as a supplement to real objects, while in MR technology, virtual objects and real objects are used in an equal state.

[0626] XR technology can be applied to a head-mounted display (HMD), a head-up display (HUD), a mobile phone, a tablet computer, a laptop computer, a desktop computer, a television, a digital signage, etc. A device to which XR technology is applied can be called an XR device.

[0627] The claims disclosed in this specification can be combined in various ways. For example, the technical features in the method claims of this specification can be combined to be implemented as a device, and the technical features in the device claims of this specification can be combined to be implemented by a method. In addition, the technical features in the method claims and the device claims of this specification can be combined to be implemented as a device, and the technical features in the method claims and the device claims of this specification can be combined to be implemented by a method.

Claims

1. A method in a wireless local area network (LAN) system, the method comprising: Receiving, by a receiving station (STA), a physical protocol data unit (PPDU) including a control field and a data field from a transmitting STA via a wideband; And Obtaining, by the receiving STA, the control field; And Decoding, by the receiving STA, the data field based on the control field, Wherein the control field includes allocation information regarding a plurality of resource units (RUs), Wherein, based on the wideband being a 320 MHz band including first to fourth 80 MHz sub-channels, the first 80 MHz sub-channel includes a first 996 RUs, the second 80 MHz sub-channel includes a second 996 RUs, the third 80 MHz sub-channel includes a third 996 RUs, and the fourth 80 MHz sub-channel includes a first 484 RUs, Wherein the data field is received via the plurality of RUs in which the first to third 996 RUs and the first 484 RUs are aggregated, Wherein the PPDU is received based on a non-orthogonal frequency division multiple access (non-OFDMA) scheme, and Wherein the plurality of RUs are obtained when the 484 RUs are punctured in the fourth 80 MHz sub-channel of the 320 MHz band.

2. The method according to claim 1, wherein The first to third 996 RUs are RUs composed of 996 tones, Wherein the 484 RUs are RUs composed of 484 tones.

3. The method according to claim 1, wherein, One of the first to fourth 80 MHz sub-channels is a primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel are secondary 80 MHz channels, Wherein the primary 80 MHz channel includes a primary 20 MHz channel, a secondary 20 MHz channel, and a secondary 40 MHz channel, Wherein the primary 20 MHz channel is not punctured.

4. A receiving station (STA) in a wireless local area network (LAN), the receiving STA comprising: A memory; A transceiver; And A processor operably coupled to the memory and the transceiver, Wherein the processor is configured to: Receive, from a transmitting STA via a wideband, a physical protocol data unit (PPDU) including a control field and a data field; Obtain the control field; and Decode the data field based on the control field, Wherein the control field includes allocation information regarding a plurality of resource units (RUs), wherein, based on the wideband being a 320 MHz band including first to fourth 80 MHz sub-channels, the first 80 MHz sub-channel includes a first 996 RUs, the second 80 MHz sub-channel includes a second 996 RUs, the third 80 MHz sub-channel includes a third 996 RUs, and the fourth 80 MHz sub-channel includes a first 484 RUs, Wherein the data field is received via the plurality of RUs in which the first to third 996 RUs and the first 484 RUs are aggregated, Wherein the PPDU is received based on a non-orthogonal frequency division multiple access (non-OFDMA) scheme, The multiple RUs are obtained when 484 RUs are punctured in the fourth 80 MHz sub-channel of the 320 MHz band.

5. A method in a wireless local area network (LAN), the method comprising: configuring, by a transmitting station (STA), a control field; configuring, by the transmitting STA based on the control field, a physical protocol data unit (PPDU); and transmitting, by the transmitting STA over a wideband, the PPDU including a data field to a receiving STA, wherein the control field includes allocation information regarding a plurality of resource units (RUs), wherein, based on the wideband being a 320 MHz band including first to fourth 80 MHz sub-channels, the first 80 MHz sub-channel includes a first 996 RUs, the second 80 MHz sub-channel includes a second 996 RUs, the third 80 MHz sub-channel includes a third 996 RUs, and the fourth 80 MHz sub-channel includes a first 484 RUs, wherein the data field is received through the plurality of RUs in which the first to third 996 RUs and the first 484 RUs are aggregated, wherein the PPDU is transmitted based on a non-orthogonal frequency division multiple access (non-OFDMA) scheme, and wherein the multiple RUs are obtained when 484 RUs are punctured in the fourth 80 MHz sub-channel of the 320 MHz band.

6. The method according to claim 5, wherein, The first to third 996 RUs are RUs composed of 996 tones, wherein the 484 RU is an RU composed of 484 tones.

7. The method according to claim 5, wherein, One of the first to fourth 80 MHz sub-channels is a primary 80 MHz channel, and the remaining three sub-channels other than the primary 80 MHz channel are secondary 80 MHz channels, wherein the primary 80 MHz channel includes a primary 20 MHz channel, a secondary 20 MHz channel, and a secondary 40 MHz channel, and wherein the primary 20 MHz channel is not punctured.

Images