WO2021112621A1

WO2021112621A1 - Method for transmitting signal through preamble puncturing in wireless communication system

Info

Publication number: WO2021112621A1
Application number: PCT/KR2020/017644
Authority: WO
Inventors: 임동국; 천진영; 최진수; 박은성; 김진민
Original assignee: 엘지전자 주식회사
Priority date: 2019-12-05
Filing date: 2020-12-04
Publication date: 2021-06-10

Abstract

According to various embodiments, a reception STA may receive a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from a transmission STA. The first signal field may include 4-bit information about a preamble puncturing pattern in an 80 MHz bandwidth of the total bandwidth of the PPDU. The second signal field may include second information about a preamble puncturing pattern of the total bandwidth.

Description

Signal transmission technique through preamble puncturing in wireless communication system

The present specification relates to a signal transmission technique through preamble puncturing in a WLAN system, and more particularly, to a method for transmitting information on preamble puncturing in multi-link communication and an apparatus supporting the same.

A wireless local area network (WLAN) has been improved in various ways. For example, the IEEE 802.11ax standard proposes an improved communication environment using OFDMA (orthogonal frequency division multiple access) and DL MU downlink multi-user multiple input, multiple output (MIMO) techniques.

This specification proposes technical features that can be used in a new communication standard. For example, the new communication standard may be the Extreme High Throughput (EHT) specification, which is being discussed recently. The EHT standard may use a newly proposed increased bandwidth, an improved PHY layer protocol data unit (PPDU) structure, an improved sequence, a hybrid automatic repeat request (HARQ) technique, and the like. The EHT standard may be referred to as an IEEE 802.11be standard.

In the EHT standard, a wide bandwidth (eg, 160/320 MHz), 16 streams, and/or multi-link (or multi-band) operation may be used to support high throughput and high data rate.

In the EHT standard (ie, Beyond 11ax), multiple RU allocation for allocating a plurality of resource units to one terminal (or STA) has been proposed to improve throughput. When a signal is transmitted to one STA using a plurality of RUs, a technical feature for efficiently transmitting information on multiple RUs allocated to the terminal may be required.

Therefore, in the present specification, when a signal is transmitted to one STA by allocating multiple resource units, a technical feature for reducing overhead for a control field and efficiently transmitting RU allocation information may be proposed.

According to various embodiments, the receiving STA receives a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from the transmitting STA, wherein the first signal field is 80 MHz of the total bandwidth of the PPDU 4 bit information about the preamble puncturing pattern of the bandwidth, the 4 bit information includes first information on whether puncturing is applied in units of 20 MHz among the 80 MHz bandwidth, and the second signal field is including second information about the preamble puncturing pattern of the entire bandwidth; and decoding the PPDU based on the first signal field and the second signal field.

According to various embodiments, the receiving STA may obtain information about the preamble puncturing pattern of the 80 MHz bandwidth among the entire bandwidth of the received PPDU, based on the first signal field. Accordingly, there is an effect that the receiving STA can quickly confirm that preamble puncturing is applied to the received PPDU. In addition, the receiving STA may obtain information about the preamble puncturing pattern of the entire bandwidth of the PPDU based on the second signal field. According to various embodiments, information about the preamble puncturing pattern may be transmitted through 4-bit information. Accordingly, there is an effect of reducing the overhead.

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

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

3 is a view for explaining a general link setup process.

4 is a diagram illustrating an example of a PPDU used in the IEEE standard.

5 is a diagram illustrating an arrangement of resource units (RUs) used on a 20 MHz band.

6 is a diagram illustrating an arrangement of a resource unit (RU) used on a 40 MHz band.

7 is a diagram illustrating an arrangement of a resource unit (RU) used on an 80 MHz band.

8 shows the structure of the HE-SIG-B field.

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

10 shows an operation according to UL-MU.

11 shows an example of a trigger frame.

12 shows an example of a common information field of a trigger frame.

13 shows an example of a subfield included in a per user information field.

14 illustrates the technical features of the UORA technique.

15 shows an example of a channel used/supported/defined in the 2.4 GHz band.

16 shows an example of a channel used/supported/defined within the 5 GHz band.

17 shows an example of a channel used/supported/defined within the 6 GHz band.

18 shows an example of a PPDU used in this specification.

19 shows a modified example of a transmitting apparatus and/or a receiving apparatus of the present specification.

20 shows an example of a HE-PPDU.

21 shows an example of an EHT PPDU.

22 shows an example of U-SIG.

23 shows RU allocation at 80 MHz.

24 is a flowchart for explaining an operation of a transmitting STA.

25 is a flowchart illustrating an operation of a receiving STA.

In this specification, "A or B (A or B)" may mean "only A", "only B", or "both A and B". In other words, “A or B (A or B)” in the present specification may be interpreted as “A and/or B (A and/or B)”. For example, "A, B or C(A, B or C)" herein means "only A", "only B", "only C", or "any and any combination of A, B and C ( any combination of A, B and C)".

As used herein, a slash (/) or a comma (comma) may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.

As used herein, “at least one of A and B” may mean “only A”, “only B” or “both A and B”. Also, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” means “at least one of A and/or B”. It can be interpreted the same as "A and B (at least one of A and B)".

Also, as used herein, "at least one of A, B and C" means "only A", "only B", "only C", or "A, B and C" any combination of A, B and C". Also, “at least one of A, B or C” or “at least one of A, B and/or C” means can mean "at least one of A, B and C".

In addition, parentheses used herein may mean "for example". Specifically, when displayed as “control information (EHT-Signal)”, “EHT-Signal” may be proposed as an example of “control information”. In other words, "control information" in the present specification is not limited to "EHT-Signal", and "EHT-Signal" may be proposed as an example of "control information". Also, even when displayed as “control information (ie, EHT-signal)”, “EHT-signal” may be proposed as an example of “control information”.

In this specification, technical features that are individually described within one drawing may be implemented individually or simultaneously.

The following examples of the present specification may be applied to various wireless communication systems. For example, the following example of the present specification may be applied to a wireless local area network (WLAN) system. For example, the present specification may be applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11ax standard. In addition, this specification may be applied to a newly proposed EHT standard or IEEE 802.11be standard. In addition, an example of the present specification may be applied to the EHT standard or a new wireless LAN standard that is an enhancement of IEEE 802.11be. Also, an example of the present specification may be applied to a mobile communication system. For example, it may be applied to a mobile communication system based on Long Term Evolution (LTE) based on the 3rd Generation Partnership Project (3GPP) standard and its evolution. In addition, an example of the present specification may be applied to a communication system of the 5G NR standard based on the 3GPP standard.

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

The example of FIG. 1 may perform various technical features described below. 1 relates to at least one STA (station). For example, the

STAs

110 and 120 of the present specification are a mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), It may also be called by various names such as a mobile station (MS), a mobile subscriber unit, or simply a user. The

STAs

110 and 120 of the present specification may be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, and a relay. In the present specification, the

STAs

110 and 120 may be referred to by various names such as a receiving device (apparatus), a transmitting device, a receiving STA, a transmitting STA, a receiving device, and a transmitting device.

For example, the

STAs

110 and 120 may perform an access point (AP) role or a non-AP role. That is, the

STAs

110 and 120 of the present specification may perform AP and/or non-AP functions. In this specification, the AP may also be indicated as an AP STA.

The

STAs

110 and 120 of the present specification may support various communication standards other than the IEEE 802.11 standard. For example, a communication standard (eg, LTE, LTE-A, 5G NR standard) according to the 3GPP standard may be supported. In addition, the STA of the present specification may be implemented in various devices such as a mobile phone, a vehicle, and a personal computer. In addition, the STA of the present specification may support communication for various communication services such as voice call, video call, data communication, and autonomous driving (Self-Driving, Autonomous-Driving).

In the present specification, the

STAs

110 and 120 may include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a wireless medium.

The

STAs

110 and 120 will be described based on the sub-drawing (a) of FIG. 1 as follows.

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

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

For example, the first STA 110 may perform an intended operation of the AP. For example, the processor 111 of the AP may receive a signal through the transceiver 113 , process the received signal, generate a transmission signal, and perform control for signal transmission. The memory 112 of the AP may store a signal (ie, a received signal) received through the transceiver 113 and may store a signal to be transmitted through the transceiver (ie, a transmission signal).

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

For example, the processor 121 of the non-AP STA may receive a signal through the transceiver 123 , process the received signal, generate a transmission signal, and perform control for signal transmission. The memory 122 of the non-AP STA may store a signal (ie, a received signal) received through the transceiver 123 and may store a signal (ie, a transmission signal) to be transmitted through the transceiver.

For example, an operation of a device denoted as an AP in the following specification may be performed by the first STA 110 or the second STA 120 . For example, when the first STA 110 is an AP, the operation of the device marked as AP is controlled by the processor 111 of the first STA 110 , and is controlled by the processor 111 of the first STA 110 . Related signals may be transmitted or received via the controlled transceiver 113 . In addition, control information related to an operation of the AP or a transmission/reception signal of the AP may be stored in the memory 112 of the first STA 110 . In addition, when the second STA 110 is an AP, the operation of the device indicated by the AP is controlled by the processor 121 of the second STA 120 and controlled by the processor 121 of the second STA 120 . A related signal may be transmitted or received via the transceiver 123 . In addition, control information related to an operation of the AP or a transmission/reception signal of the AP may be stored in the memory 122 of the second STA 110 .

For example, an operation of a device indicated as a non-AP (or User-STA) in the following specification may be performed by the first STA 110 or the second STA 120 . For example, when the second STA 120 is a non-AP, the operation of the device marked as non-AP is controlled by the processor 121 of the second STA 120, and the processor ( A related signal may be transmitted or received via the transceiver 123 controlled by 121 . In addition, control information related to the operation of the non-AP or the AP transmit/receive signal may be stored in the memory 122 of the second STA 120 . For example, when the first STA 110 is a non-AP, the operation of the device marked as non-AP is controlled by the processor 111 of the first STA 110 , and the processor ( Related signals may be transmitted or received via transceiver 113 controlled by 111 . In addition, control information related to the operation of the non-AP or the AP transmission/reception signal may be stored in the memory 112 of the first STA 110 .

In the following specification (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device , (transmission/reception) apparatus, network, and the like may refer to the

STAs

110 and 120 of FIG. 1 . For example, without specific reference numerals (transmitting/receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting/receiving) Terminal, (transmitting) A device indicated by a /receiver) device, a (transmit/receive) apparatus, and a network may also refer to the

STAs

110 and 120 of FIG. 1 . For example, in the following example, an operation in which various STAs transmit and receive signals (eg, PPPDUs) may be performed by the

transceivers

113 and 123 of FIG. 1 . In addition, in the following example, an operation in which various STAs generate a transmit/receive signal or perform data processing or calculation in advance for the transmit/receive signal may be performed by the

processors

111 and 121 of FIG. 1 . For example, an example of an operation of generating a transmission/reception signal or performing data processing or operation in advance for a transmission/reception signal is 1) Determining bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU /Acquisition/configuration/computation/decoding/encoding operation, 2) time resource or frequency resource (eg, subcarrier resource) used for the subfield (SIG, STF, LTF, Data) field included in the PPDU, etc. operation of determining / configuring / obtaining, 3) a specific sequence (eg, pilot sequence, STF / LTF sequence, SIG) used for the subfield (SIG, STF, LTF, Data) field included in the PPDU operation of determining / configuring / obtaining an extra sequence), etc., 4) a power control operation and / or a power saving operation applied to the STA, 5) an operation related to determination / acquisition / configuration / operation / decoding / encoding of the ACK signal may include In addition, in the following example, various information used by various STAs for determination/acquisition/configuration/computation/decoding/encoding of transmit/receive signals (for example, information related to fields/subfields/control fields/parameters/power, etc.) may be stored in the memories 112 and 122 of FIG. 1 .

The device/STA of the sub-view (a) of FIG. 1 described above may be modified as shown in the sub-view (b) of FIG. 1 . Hereinafter, the

STAs

110 and 120 of the present specification will be described based on the sub-drawing (b) of FIG. 1 .

For example, the

transceivers

113 and 123 illustrated in (b) of FIG. 1 may perform the same function as the transceivers illustrated in (a) of FIG. 1 . For example, the

processing chips

114 and 124 illustrated in (b) of FIG. 1 may include

processors

111 and 121 and

memories

112 and 122 . The

processors

111 and 121 and the

memories

112 and 122 shown in (b) of FIG. 1 are the

processors

111 and 121 and the

memories

112 and 122 shown in (a) of FIG. ) can perform the same function.

As described below, a mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile Mobile Subscriber Unit, user, user STA, network, base station, Node-B, access point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, Receiving Device, Transmitting Device, Receiving Apparatus, and/or Transmitting Apparatus means the

STAs

110 and 120 shown in the sub-drawings (a)/(b) of FIG. ) may mean the

processing chips

114 and 124 shown in FIG. That is, the technical features of the present specification may be performed on the

STAs

110 and 120 shown in the sub-drawing (a)/(b) of FIG. 1, and the processing chip ( 114 and 124). For example, a technical feature in which a transmitting STA transmits a control signal is that the control signals generated by the

processors

111 and 121 shown in the sub-drawings (a)/(b) of FIG. 1 are (a) of FIG. ) / (b) can be understood as a technical feature transmitted through the

transceivers

113 and 123 shown in (b). Alternatively, the technical feature in which the transmitting STA transmits the control signal is a technical feature in which the control signal to be transmitted to the

transceivers

113 and 123 is generated from the

processing chips

114 and 124 shown in the sub-view (b) of FIG. can be understood

For example, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal is received by the

transceivers

113 and 123 shown in the sub-drawing (a) of FIG. 1 . Alternatively, the technical feature in which the receiving STA receives the control signal is that the control signal received by the

transceivers

113 and 123 shown in the sub-drawing (a) of FIG. 1 is the processor shown in (a) of FIG. 111, 121) can be understood as a technical feature obtained by. Alternatively, the technical feature for the receiving STA to receive the control signal is that the control signal received by the

transceivers

113 and 123 shown in the sub-view (b) of FIG. 1 is the processing chip shown in the sub-view (b) of FIG. It can be understood as a technical feature obtained by (114, 124).

Referring to (b) of FIG. 1 ,

software codes

115 and 125 may be included in the

memories

112 and 122 . The

software codes

115 and 125 may include instructions for controlling the operations of the

processors

111 and 121 .

Software code

115, 125 may be included in a variety of programming languages.

The

processors

111 and 121 or the

processing chips

114 and 124 shown in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and/or data processing devices. The processor may be an application processor (AP). For example, the

processors

111 and 121 or the

processing chips

114 and 124 shown in FIG. 1 may include a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (Modem). and demodulator). For example, the

processors

111 , 121 or

processing chips

114 , 124 shown in FIG. 1 may include a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, and a processor manufactured by Apple®. It may be an A series processor, a HELIOTM series processor manufactured by MediaTek®, an ATOMTM series processor manufactured by INTEL®, or an enhanced processor.

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

The upper part of FIG. 2 shows the structure of an infrastructure basic service set (BSS) of the Institute of Electrical and Electronic Engineers (IEEE) 802.11.

Referring to the upper part of FIG. 2 , a wireless LAN system may include one or more infrastructure BSSs 200 and 205 (hereinafter, BSSs). The

BSSs

200 and 205 are a set of APs and STAs, such as an access point (AP) 225 and a station 200-1 (STA1) that can communicate with each other through successful synchronization, and are not a concept indicating a specific area. The BSS 205 may include one or more combinable STAs 205 - 1 and 205 - 2 to one AP 230 .

The BSS may include at least one STA, the

APs

225 and 230 providing a distribution service, and a distribution system (DS) 210 connecting a plurality of APs.

The distributed system 210 may implement an extended service set (ESS) 240 that is an extended service set by connecting

several BSSs

200 and 205 . The ESS 240 may be used as a term indicating one network in which one or several APs are connected through the distributed system 210 . APs included in one ESS 240 may have the same service set identification (SSID).

The portal 220 may serve as a bridge connecting a wireless LAN network (IEEE 802.11) and another network (eg, 802.X).

In the BSS as shown in the upper part of FIG. 2 , a network between the

APs

225 and 230 and a network between the

APs

225 and 230 and the STAs 200 - 1 , 205 - 1 and 205 - 2 may be implemented. However, it may also be possible to establish a network and perform communication between STAs without the

APs

225 and 230 . A network that establishes a network and performs communication even between STAs without the

APs

225 and 230 is defined as an ad-hoc network or an independent basic service set (IBSS).

The lower part of FIG. 2 is a conceptual diagram illustrating the IBSS.

Referring to the lower part of FIG. 2 , the IBSS is a BSS operating in an ad-hoc mode. Since IBSS does not include an AP, there is no centralized management entity that performs a centralized management function. That is, in the IBSS, the STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and access to a distributed system is not allowed, so a self-contained network network) is formed.

3 is a view for explaining a general link setup process.

In the illustrated step S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access the network, it must find a network in which it can participate. An STA must identify a compatible network before participating in a wireless network. The process of identifying a network existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

3 exemplarily illustrates a network discovery operation including an active scanning process. In active scanning, an STA performing scanning transmits a probe request frame to discover which APs exist around it while moving channels, and waits for a response. A responder transmits a probe response frame in response to the probe request frame to the STA that has transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In the BSS, since the AP transmits a beacon frame, the AP becomes the responder. In the IBSS, the STAs in the IBSS rotate and transmit the beacon frame, so the responder is not constant. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 stores BSS-related information included in the received probe response frame and channel) to perform scanning (ie, probe request/response transmission/reception on channel 2) in the same way.

Although not shown in the example of FIG. 3 , the scanning operation may be performed in a passive scanning manner. An STA performing scanning based on passive scanning may wait for a beacon frame while moving channels. The beacon frame is one of the management frames in IEEE 802.11, and is periodically transmitted to inform the existence of a wireless network, and to allow a scanning STA to search for a wireless network and participate in the wireless network. In the BSS, the AP plays a role of periodically transmitting a beacon frame, and in the IBSS, the STAs in the IBSS rotate and transmit the beacon frame. When the STA performing the scanning receives the beacon frame, it stores information on the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. Upon receiving the beacon frame, the STA may store BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.

The STA discovering the network may perform an authentication process through step S320. This authentication process may be referred to as a first authentication process in order to clearly distinguish it from the security setup operation of step S340 to be described later. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and in response thereto, the AP transmits an authentication response frame to the STA. An authentication frame used for an authentication request/response corresponds to a management frame.

The authentication frame includes an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group), etc. may be included.

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

The successfully authenticated STA may perform a connection process based on step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and in response, the AP transmits an association response frame to the STA. For example, the connection request frame includes information related to various capabilities, a beacon listening interval, a service set identifier (SSID), supported rates, supported channels, RSN, and a mobility domain. , supported operating classes, TIM broadcast request (Traffic Indication Map Broadcast request), interworking service capability, and the like may include information. For example, the connection response frame includes information related to various capabilities, status codes, Association IDs (AIDs), support rates, Enhanced Distributed Channel Access (EDCA) parameter sets, Received Channel Power Indicator (RCPI), Received Signal to Noise (RSNI). indicator), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS map, and the like.

Thereafter, in step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of private key setup through 4-way handshaking through an Extensible Authentication Protocol over LAN (EAPOL) frame. .

4 is a diagram illustrating an example of a PPDU used in the IEEE standard.

As shown, various types of PHY protocol data units (PPDUs) are used in standards such as IEEE a/g/n/ac. Specifically, the LTF and STF fields include training signals, SIG-A and SIG-B include control information for the receiving station, and the data field includes user data corresponding to MAC PDU/Aggregated MAC PDU (PSDU). included

4 also includes an example of an HE PPDU of the IEEE 802.11ax standard. The HE PPDU according to FIG. 4 is an example of a PPDU for multiple users. HE-SIG-B may be included only for multiple users, and the corresponding HE-SIG-B may be omitted from the PPDU for a single user.

As shown, HE-PPDU for multiple users (Multiple User; MU) is L-STF (legacy-short training field), L-LTF (legacy-long training field), L-SIG (legacy-signal), HE-SIG-A (high efficiency-signal A), HE-SIG-B (high efficiency-signal-B), HE-STF (high efficiency-short training field), HE-LTF (high efficiency-long training field) , a data field (or MAC payload) and a packet extension (PE) field. Each field may be transmitted during the illustrated time interval (ie, 4 or 8 μs, etc.).

Hereinafter, a resource unit (RU) used in the PPDU will be described. A resource unit may include a plurality of subcarriers (or tones). The resource unit may be used when transmitting a signal to a plurality of STAs based on the OFDMA technique. In addition, a resource unit may be defined even when a signal is transmitted to one STA. The resource unit may be used for STF, LTF, data field, and the like.

As shown in FIG. 5 , resource units (RUs) corresponding to different numbers of tones (ie, subcarriers) may be used to configure some fields of the HE-PPDU. For example, resources may be allocated in units of RUs shown for HE-STF, HE-LTF, and data fields.

As shown at the top of FIG. 5 , 26-units (ie, units corresponding to 26 tones) may be deployed. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and 5 tones may be used as a guard band in the rightmost band of the 20 MHz band. In addition, 7 DC tones are inserted into the center band, that is, the DC band, and 26-units corresponding to each of 13 tones may exist on the left and right sides of the DC band. In addition, 26-units, 52-units, and 106-units may be allocated to other bands. Each unit may be assigned for a receiving station, ie a user.

On the other hand, the RU arrangement of FIG. 5 is utilized not only in a situation for a plurality of users (MU), but also in a situation for a single user (SU). In this case, as shown at the bottom of FIG. 5, one 242-unit is used. It is possible to use and in this case 3 DC tones can be inserted.

In the example of FIG. 5 , RUs of various sizes, ie, 26-RU, 52-RU, 106-RU, 242-RU, etc., have been proposed. Since the specific size of these RUs can be extended or increased, this embodiment is not limited to the specific size of each RU (ie, the number of corresponding tones).

As in the example of FIG. 5, RUs of various sizes are used, in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. may be used. In addition, 5 DC tones can be inserted into the center frequency, 12 tones are used as a guard band in the leftmost band of the 40MHz band, and 11 tones are used in the rightmost band of the 40MHz band. This can be used as a guard band.

Also, as shown, when used for a single user, 484-RU may be used. Meanwhile, the fact that the specific number of RUs can be changed is the same as the example of FIG. 4 .

As in the example of FIGS. 5 and 6 , RUs of various sizes are used, in the example of FIG. 7, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. may be used. have. In addition, 7 DC tones can be inserted into the center frequency, 12 tones are used as a guard band in the leftmost band of the 80MHz band, and 11 tones are used in the rightmost band of the 80MHz band. This can be used as a guard band. In addition, 26-RU using 13 tones located on the left and right of the DC band can be used.

Also, as shown, when used for a single user, 996-RU may be used, and in this case, 5 DC tones may be inserted.

The RU described in this specification may be used for uplink (UL) communication and downlink (DL) communication. For example, when UL-MU communication solicited by a Trigger frame is performed, a transmitting STA (eg, AP) provides a first RU (eg, 26/52/106) to the first STA through a Trigger frame. /242-RU, etc.), and a second RU (eg, 26/52/106/242-RU, etc.) may be allocated to the second STA. Thereafter, the first STA may transmit a first trigger-based PPDU based on the first RU, and the second STA may transmit a second trigger-based PPDU based on the second RU. The first/second trigger-based PPDUs are transmitted to the AP in the same time interval.

For example, when the DL MU PPDU is configured, the transmitting STA (eg, AP) allocates a first RU (eg, 26/52/106/242-RU, etc.) to the first STA, and A second RU (eg, 26/52/106/242-RU, etc.) may be allocated to the 2 STAs. That is, the transmitting STA (eg, AP) may transmit the HE-STF, HE-LTF, and Data fields for the first STA through the first RU within one MU PPDU, and the second through the second RU. HE-STF, HE-LTF, and Data fields for 2 STAs may be transmitted.

Information on the arrangement of the RU may be signaled through HE-SIG-B.

8 shows the structure of the HE-SIG-B field.

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 commonly applied to all users (ie, user STAs) receiving SIG-B. The user-individual field 830 may be referred to as a user-individual control field. The user-individual field 830 may be applied only to some of the plurality of users when the SIG-B is delivered to a plurality of users.

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

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

An example of a case in which the RU allocation information consists of 8 bits is as follows.

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

An example of Table 1 shows only some of the RU locations that can be indicated by the RU allocation information.

For example, the RU allocation information may include an example of Table 2 below.

"01000y2y1y0" relates to an example in which 106-RU is allocated to the leftmost side of a 20 MHz channel and 5 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (eg, User-STAs) may be allocated to the 106-RU based on the MU-MIMO technique. Specifically, a maximum of 8 STAs (eg, User-STAs) may be allocated to the 106-RU, and the number of STAs (eg, User-STAs) allocated to the 106-RU is 3-bit information (y2y1y0). ) is determined based on For example, when 3-bit information (y2y1y0) is set to N, the number of STAs (eg, User-STAs) allocated to the 106-RU based on the MU-MIMO technique may be N+1.

In general, a plurality of different STAs (eg, user STAs) may be allocated to a plurality of RUs. However, a plurality of STAs (eg, user STAs) may be allocated to one RU of a specific size (eg, 106 subcarriers) or more based on the MU-MIMO technique.

As shown in FIG. 8 , the user-individual field 830 may include a plurality of user fields. As described above, the number of STAs (eg, user STAs) allocated to a specific channel may be determined based on the RU allocation information of the common field 820 . For example, when the RU allocation information of the common field 820 is “00000000”, one user STA may be allocated to each of the nine 26-RUs (that is, a total of nine user STAs are allocated). That is, a maximum of 9 user STAs may be allocated to a specific channel through the OFDMA technique. In other words, up to 9 user STAs may be allocated to a specific channel through the non-MU-MIMO technique.

For example, when the RU allocation is set to "01000y2y1y0", a plurality of user STAs are allocated to the 106-RU disposed on the leftmost side through the MU-MIMO technique, and five 26-RUs disposed on the right side have Five user STAs may be allocated through the non-MU-MIMO technique. This case is embodied through an example of FIG. 9 .

For example, when RU allocation is set to "01000010" as shown in FIG. 9, based on Table 2, 106-RU is allocated to the leftmost side of a specific channel, and 5 26-RUs are allocated to the right side. can In addition, a total of three user STAs may be allocated to the 106-RU through the MU-MIMO technique. As a result, since a total of 8 User STAs are allocated, the user-individual field 830 of HE-SIG-B may include 8 User fields.

Eight user fields may be included in the order shown in FIG. 9 . Also, as shown in FIG. 8 , two user fields may be implemented as one user block field.

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

Each user field may have the same size (eg, 21 bits). For example, the user field of the first format (the format of the MU-MIMO technique) may be configured as follows.

For example, the first bit (eg, B0-B10) in the user field (ie, 21 bits) is identification information of the user STA to which the corresponding user field is allocated (eg, STA-ID, partial AID, etc.) may include. In addition, the second bit (eg, B11-B14) in the user field (ie, 21 bits) may include information about spatial configuration. Specifically, examples of the second bits (ie, B11-B14) may be as shown in Tables 3 to 4 below.

As shown in Table 3 and/or Table 4, the second bit (ie, B11-B14) may include information about the number of spatial streams allocated to a plurality of user STAs allocated according to the MU-MIMO technique. have. For example, when three user STAs are allocated to 106-RU based on the MU-MIMO technique as shown in FIG. 9, N_user is set to "3", and accordingly, as shown in Table 3, N_STS[1], Values of N_STS[2] and N_STS[3] may be determined. For example, when the value of the second bits B11-B14 is “0011”, N_STS[1]=4, N_STS[2]=1, N_STS[3]=1 may be set. That is, in the example of FIG. 9 , four spatial streams may be allocated to user field 1, one spatial stream may be allocated to user field 2, and one spatial stream may be allocated to user field 3 in the example of FIG.

As an example of Table 3 and/or Table 4, information about the number of spatial streams for a user STA (ie, the second bit, B11-B14) may consist of 4 bits. In addition, information on the number of spatial streams (ie, second bits, B11-B14) for a user STA may support up to 8 spatial streams. In addition, information on the number of spatial streams (ie, the second bit, B11-B14) may support up to four spatial streams for one user STA.

In addition, the third bit (ie, B15-18) in the user field (ie, 21 bits) may include modulation and coding scheme (MCS) information. The MCS information may be applied to a data field in the PPDU including the corresponding SIG-B.

MCS, MCS information, MCS index, MCS field, etc. used in this specification may be indicated by a specific index value. For example, MCS information may be indicated by index 0 to index 11. MCS information includes information about a constellation modulation type (eg, BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.), and a coding rate (eg, 1/2, 2/ 3, 3/4, 5/6, etc.). Information on a channel coding type (eg, BCC or LDPC) may be excluded from the MCS information.

Also, the fourth bit (ie, B19) in the User field (ie, 21 bits) may be a Reserved field.

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

The above-described example relates to the User Field of the first format (the format of the MU-MIMO technique). An example of the user field of the second format (a format of the non-MU-MIMO technique) is as follows.

The first bit (eg, B0-B10) in the user field of the second format may include identification information of the user STA. In addition, the second bit (eg, B11-B13) in the user field of the second format may include information about the number of spatial streams applied to the corresponding RU. In addition, the third bit (eg, B14) in the user field of the second format may include information on whether a beamforming steering matrix is applied. A fourth bit (eg, B15-B18) in the user field of the second format may include modulation and coding scheme (MCS) information. In addition, a fifth bit (eg, B19) in the user field of the second format may include information on whether Dual Carrier Modulation (DCM) is applied. In addition, the sixth bit (ie, B20) in the user field of the second format may include information about a coding type (eg, BCC or LDPC).

10 shows an operation according to UL-MU. As shown, the transmitting STA (eg, AP) may perform channel access through contending (ie, backoff operation) and transmit a trigger frame 1030 . That is, the transmitting STA (eg, AP) may transmit the PPDU including the Trigger Frame 1330 . When a PPDU including a trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

The

TB PPDUs

1041 and 1042 are transmitted in the same time zone, and may be transmitted from a plurality of STAs (eg, user STAs) in which AIDs are indicated in the trigger frame 1030 . The ACK frame 1050 for the TB PPDU may be implemented in various forms.

Specific features of the trigger frame will be described with reference to FIGS. 11 to 13 . Even when UL-MU communication is used, an orthogonal frequency division multiple access (OFDMA) technique or MU MIMO technique may be used, and OFDMA and MU MIMO technique may be used simultaneously.

11 shows an example of a trigger frame. The trigger frame of FIG. 11 allocates resources for uplink multiple-user transmission (MU), and may be transmitted, for example, from an AP. The trigger frame may be composed of a MAC frame and may be included in a PPDU.

Each field shown in FIG. 11 may be partially omitted, and another field may be added. Also, the length of each field may be changed differently from that shown.

The frame control field 1110 of FIG. 11 includes information about the version of the MAC protocol and other additional control information, and the duration field 1120 includes time information for NAV setting or an STA identifier (eg, For example, information about AID) may be included.

In addition, the RA field 1130 includes address information of the receiving STA of the corresponding trigger frame, and may be omitted if necessary. The TA field 1140 includes address information of an STA (eg, AP) that transmits the trigger frame, and the common information field 1150 is a common information field applied to the receiving STA that receives the trigger frame. Contains control information. For example, a field indicating the length of the L-SIG field of the uplink PPDU transmitted in response to the trigger frame or the SIG-A field (ie, HE-SIG-A) in the uplink PPDU transmitted in response to the trigger frame. field) may include information controlling the content. In addition, as common control information, information on the length of the CP of the uplink PPDU transmitted in response to the trigger frame or information on the length of the LTF field may be included.

In addition, it is preferable to include per user information fields 1160#1 to 1160#N corresponding to the number of receiving STAs receiving the trigger frame of FIG. 11 . The individual user information field may be referred to as an “allocation field”.

Also, the trigger frame of FIG. 11 may include a padding field 1170 and a frame check sequence field 1180 .

Each of the per user information fields 1160#1 to 1160#N shown in FIG. 11 may again include a plurality of subfields.

12 shows an example of a common information field of a trigger frame. Some of the subfields of FIG. 12 may be omitted, and other subfields may be added. Also, the length of each subfield shown may be changed.

The illustrated length field 1210 has the same value as the length field of the L-SIG field of the uplink PPDU transmitted in response to the 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 may be used to indicate the length of the corresponding uplink PPDU.

In addition, the cascade indicator field 1220 indicates whether a cascade operation is performed. The cascade operation means that downlink MU transmission and uplink MU transmission are performed together in the same TXOP. That is, after downlink MU transmission is performed, it means that uplink MU transmission is performed after a preset time (eg, SIFS). During the case cade operation, there may be only one transmitter (eg, AP) performing downlink communication, and a plurality of transmitters (eg, non-AP) performing uplink communication may exist.

The CS request field 1230 indicates whether the state of the radio medium or NAV should be considered in a situation in which the receiving device receiving the corresponding trigger frame transmits the corresponding uplink PPDU.

The HE-SIG-A information field 1240 may include information for controlling the content of the SIG-A field (ie, the HE-SIG-A field) of the uplink PPDU transmitted in response to the corresponding trigger frame.

The CP and LTF type field 1250 may include information on the LTF length and CP length of the uplink PPDU transmitted in response to the corresponding trigger frame. The trigger type field 1060 may indicate a purpose for which the corresponding trigger frame is used, for example, normal triggering, triggering for beamforming, a request for Block ACK/NACK, and the like.

In the present specification, it may be assumed that the trigger type field 1260 of the trigger frame indicates a basic type trigger frame for normal triggering. For example, a basic type trigger frame may be referred to as a basic trigger frame.

13 shows an example of a subfield included in a per user information field. The user information field 1300 of FIG. 13 may be understood as any one of the individual user information fields 1160#1 to 1160#N mentioned in FIG. 11 above. Some of the subfields included in the user information field 1300 of FIG. 13 may be omitted, and other subfields may be added. Also, the length of each subfield shown may be changed.

A User Identifier field 1310 of FIG. 13 indicates an identifier of an STA (ie, a receiving STA) corresponding to per user information, and an example of the identifier is an association identifier (AID) of the receiving STA. It can be all or part of a value.

In addition, an RU Allocation field 1320 may be included. That is, when the receiving STA identified by the user identifier field 1310 transmits the TB PPDU in response to the trigger frame, it transmits the TB PPDU through the RU indicated by the RU allocation field 1320 . In this case, the RU indicated by the RU Allocation field 1320 may be the RU shown in FIGS. 5, 6, and 7 .

The subfield of FIG. 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 is set to '1', and when LDPC coding is applied, the coding type field 1330 can be set to '0'. have.

Also, the subfield of FIG. 13 may include an MCS field 1340 . The MCS field 1340 may indicate an MCS technique applied to a TB PPDU. For example, when BCC coding is applied to the TB PPDU, the coding type field 1330 is set to '1', and when LDPC coding is applied, the coding type field 1330 can be set to '0'. have.

Hereinafter, a UL OFDMA-based random access (UORA) technique will be described.

14 illustrates the technical features of the UORA technique.

The transmitting STA (eg, AP) may allocate 6 RU resources as shown in FIG. 14 through a trigger frame. Specifically, the AP is a first RU resource (AID 0, RU 1), a second RU resource (AID 0, RU 2), a third RU resource (AID 0, RU 3), a fourth RU resource (AID 2045, RU) 4), a fifth RU resource (AID 2045, RU 5), and a sixth RU resource (AID 3, RU 6) may be allocated. Information on AID 0, AID 3, or AID 2045 may be included, for example, in the user identification field 1310 of FIG. 13 . Information on RU 1 to RU 6 may be included in, for example, the RU allocation field 1320 of FIG. 13 . AID=0 may mean a UORA resource for an associated STA, and AID=2045 may mean a UORA resource for an un-associated STA. Accordingly, the first to third RU resources of FIG. 14 may be used as UORA resources for an associated STA, and the fourth to fifth RU resources of FIG. 14 are non-associated for STAs. It may be used as a UORA resource, and the sixth RU resource of FIG. 14 may be used as a resource for a normal UL MU.

In the example of FIG. 14 , the OFDMA random access BackOff (OBO) counter of STA1 is decreased to 0, and STA1 randomly selects the second RU resources (AID 0, RU 2). In addition, since the OBO counter of STA2/3 is greater than 0, uplink resources are not allocated to STA2/3. In addition, in FIG. 14 , STA4 includes its AID (ie, AID=3) in the trigger frame, and thus the resource of RU 6 is allocated without backoff.

Specifically, since STA1 of FIG. 14 is an associated STA, there are a total of three eligible RA RUs for STA1 (RU 1, RU 2, RU 3), and accordingly, STA1 decrements the OBO counter by 3 to increase the OBO counter. became 0. In addition, since STA2 in FIG. 14 is an associated STA, there are a total of three eligible RA RUs for STA2 (RU 1, RU 2, RU 3), and accordingly, STA2 decrements the OBO counter by 3, but the OBO counter is 0. is in a larger state. In addition, since STA3 of FIG. 14 is an un-associated STA, the eligible RA RUs for STA3 are two (RU 4, RU 5) in total, and accordingly, STA3 decrements the OBO counter by 2, but the OBO counter is is greater than 0.

15 shows an example of a channel used/supported/defined in the 2.4 GHz band.

The 2.4 GHz band may be referred to as another name such as a first band (band). Also, the 2.4 GHz band may mean a frequency region in which channels having a center frequency adjacent to 2.4 GHz (eg, channels having a center frequency within 2.4 to 2.5 GHz) are used/supported/defined.

The 2.4 GHz band may contain multiple 20 MHz channels. 20 MHz in the 2.4 GHz band may have multiple channel indices (eg, indices 1 to 14). For example, a center frequency of a 20 MHz channel to which channel index 1 is allocated may be 2.412 GHz, a center frequency of a 20 MHz channel to which channel index 2 is allocated may be 2.417 GHz, and 20 MHz to which channel index N is allocated. The center frequency of the channel may be (2.407 + 0.005*N) GHz. The channel index may be called by various names such as a channel number. Specific values of the channel index and center frequency may be changed.

15 exemplarily shows four channels in the 2.4 GHz band. The illustrated first frequency region 1510 to fourth frequency region 1540 may each include one channel. For example, the first frequency domain 1510 may include channel 1 (a 20 MHz channel having index 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region 1520 may include channel 6 . In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency domain 1530 may include channel 11 . In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency domain 1540 may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

16 shows an example of a channel used/supported/defined within the 5 GHz band.

The 5 GHz band may be referred to as another name such as a second band/band. The 5 GHz band may mean a frequency region in which channels having a center frequency of 5 GHz or more and less than 6 GHz (or less than 5.9 GHz) are used/supported/defined. Alternatively, the 5 GHz band may include a plurality of channels between 4.5 GHz and 5.5 GHz. The specific numerical values shown in FIG. 16 may be changed.

The plurality of channels in the 5 GHz band include UNII (Unlicensed National Information Infrastructure)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include a frequency domain called UNII Mid and UNII-2Extended. UNII-3 may be referred to as UNII-Upper.

A plurality of channels may be configured within the 5 GHz band, and the bandwidth of each channel may be variously configured such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency region/range in UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain/range may be divided into 4 channels through the 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain/range may be divided into two channels through the 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain/range may be divided into one channel through the 160 MHz frequency domain.

17 shows an example of a channel used/supported/defined within the 6 GHz band.

The 6 GHz band may be referred to as another name such as a third band/band. The 6 GHz band may mean a frequency region in which channels having a center frequency of 5.9 GHz or higher are used/supported/defined. The specific numerical values shown in FIG. 17 may be changed.

For example, the 20 MHz channel of FIG. 17 may be defined from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 17 may have an index 1 (or, a channel index, a channel number, etc.), and a center frequency of 5.945 GHz may be allocated. That is, the center frequency of the channel index N may be determined to be (5.940 + 0.005*N) GHz.

Accordingly, the index (or channel number) of the 20 MHz channel of FIG. 17 is 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. In addition, according to the above-mentioned (5.940 + 0.005*N) GHz rule, the index of the 40 MHz channel of FIG. 17 is 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.

Although 20, 40, 80, and 160 MHz channels are illustrated in the example of FIG. 17 , a 240 MHz channel or a 320 MHz channel may be additionally added.

Hereinafter, the PPDU transmitted/received by the STA of the present specification will be described.

18 shows an example of a PPDU used in this specification.

The PPDU of FIG. 18 may be referred to by various names such as an EHT PPDU, a transmission PPDU, a reception PPDU, a first type or an Nth type PPDU. For example, in the present specification, a PPDU or an EHT PPDU may be referred to by various names such as a transmission PPDU, a reception PPDU, a first type or an Nth type PPDU. In addition, the EHT PPU may be used in an EHT system and/or a new WLAN system in which the EHT system is improved.

The PPDU of FIG. 18 may represent some or all of the PPDU types used in the EHT system. For example, the example of FIG. 18 may be used for both a single-user (SU) mode and a multi-user (MU) mode. In other words, the PPDU of FIG. 18 may be a PPDU for one receiving STA or a plurality of receiving STAs. When the PPDU of FIG. 18 is used for a trigger-based (TB) mode, the EHT-SIG of FIG. 18 may be omitted. In other words, the STA that has received the Trigger frame for uplink-MU (UL-MU) communication may transmit a PPDU in which the EHT-SIG is omitted in the example of FIG. 18 .

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

The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields of FIG. 18 is set to 312.5 kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF, and Data fields may be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields is expressed in units of 312.5 kHz, EHT-STF, EHT-LTF, The tone index (or subcarrier index) of the Data field may be displayed in units of 78.125 kHz.

In the PPDU of FIG. 18, L-LTF and L-STF may be the same as the conventional fields.

The L-SIG field of FIG. 18 may include, for example, 24-bit bit information. For example, 24-bit information may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity bit, and a 6-bit Tail bit. For example, the 12-bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, when the PPDU is a non-HT, HT, VHT PPDU or an EHT PPDU, the value of the Length field may be determined as a multiple of 3. For example, when the PPDU is an HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 +2". In other words, for non-HT, HT, VHT PPDUs or for EHT PPDUs, the value of the Length field may be determined as a multiple of 3, and for the HE PPDU, the value of the Length field may be "a multiple of 3 + 1" or "a multiple of 3" +2".

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

The transmitting STA may generate the RL-SIG generated in the same way as the L-SIG. For RL-SIG, BPSK modulation may be applied. The receiving STA may know that the received PPDU is an HE PPDU or an EHT PPDU based on the existence of the RL-SIG.

A U-SIG (Universal SIG) may be inserted after the RL-SIG of FIG. 18 . The U-SIG may be referred to by various names such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, and a first (type) control signal.

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

Through the U-SIG (or U-SIG field), for example, A-bit information (eg, 52 un-coded bits) may be transmitted, and the first symbol of the U-SIG is the first of the total A-bit information. X-bit information (eg, 26 un-coded bits) is transmitted, and the second symbol of U-SIG can transmit the remaining Y-bit information (eg, 26 un-coded bits) of the total A-bit information. have. For example, the transmitting STA may obtain 26 un-coded bits included in each U-SIG symbol. The transmitting STA may generate a 52-coded bit by performing convolutional encoding (ie, BCC encoding) based on a rate of R=1/2, and may perform interleaving on the 52-coded bit. The transmitting STA may generate 52 BPSK symbols allocated to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. One U-SIG symbol may be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, except for DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) excluding pilot tones -21, -7, +7, and +21 tones.

For example, A-bit information (eg, 52 un-coded bits) transmitted by U-SIG includes a CRC field (eg, a 4-bit long field) and a tail field (eg, a 6-bit long field). ) may be included. The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on the remaining 16 bits except for the CRC/tail field in the 26 bits allocated to the first symbol of the U-SIG and the second symbol, and may be generated based on the conventional CRC calculation algorithm. can Also, the tail field may be used to terminate the trellis of the convolutional decoder, and may be set to, for example, 000000.

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

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

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

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

For example, when the EHT PPDU is divided into various types (eg, various types such as EHT PPDU related to SU mode, EHT PPDU related to MU mode, EHT PPDU related to TB mode, EHT PPDU related to Extended Range transmission) , information about the type of the EHT PPDU may be included in the version-dependent bits of the U-SIG.

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

Preamble puncturing may be applied to the PPDU of FIG. 18 . Preamble puncturing refers to applying puncturing to some bands (eg, secondary 20 MHz band) among all bands of the PPDU. For example, when an 80 MHz PPDU is transmitted, the STA may apply puncturing to the secondary 20 MHz band among the 80 MHz band, and transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

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

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

For example, U-SIG and EHT-SIG may include information about preamble puncturing based on the following method. When the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in units of 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG includes information about the 160 MHz bandwidth, and the second field of the first U-SIG includes information about the preamble puncturing applied to the first 80 MHz band (that is, the preamble information about the puncturing pattern). In addition, the first field of the second U-SIG includes information about the 160 MHz bandwidth, and the second field of the second U-SIG includes information about the preamble puncturing applied to the second 80 MHz band (ie, preamble puncture). information about processing patterns). On the other hand, the EHT-SIG subsequent to the first U-SIG may include information on preamble puncturing applied to the second 80 MHz band (that is, information on the preamble puncturing pattern), and in the second U-SIG The successive EHT-SIG may include information about preamble puncturing applied to the first 80 MHz band (ie, information about a preamble puncturing pattern).

Additionally or alternatively, the U-SIG and the EHT-SIG may include information on preamble puncturing based on the following method. The U-SIG may include information on preamble puncturing for all bands (ie, information on preamble puncturing patterns). That is, the EHT-SIG does not include information about the preamble puncturing, and only the U-SIG may include information about the preamble puncturing (ie, information about the preamble puncturing pattern).

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

The EHT-SIG of FIG. 18 may include control information for the receiving STA. The EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 us. Information on the number of symbols used for the EHT-SIG may be included in the U-SIG.

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

As in the example of FIG. 8, the common field of the EHT-SIG and the user-individual field of the EHT-SIG may be individually coded. One user block field included in the user-individual field may contain information for two users, but the last user block field included in the user-individual field is for one user. It is possible to include information. That is, one user block field of the EHT-SIG may include a maximum of two user fields. As in the example of FIG. 9 , each user field may be related to MU-MIMO assignment or may be related to non-MU-MIMO assignment.

As in the example of FIG. 8, the common field of the EHT-SIG may include a CRC bit and a Tail bit, the length of the CRC bit may be determined as 4 bits, and the length of the Tail bit may be determined as 6 bits and set to '000000'. can be set.

As in the example of FIG. 8 , the common field of the EHT-SIG may include RU allocation information. The RU allocation information may refer to information about a location of an RU to which a plurality of users (ie, a plurality of receiving STAs) are allocated. As in Table 1, RU allocation information may be configured in units of 8 bits (or N bits).

An example of Tables 5 to 7 is an example of 8-bit (or N-bit) information for various RU allocation. Indexes displayed in each table can be changed, some entries in Tables 5 to 7 may be omitted, and entries not displayed may be added.

Examples of Tables 5 to 7 relate to information about the location of an RU allocated to a 20 MHz band. For example, 'index 0' of Table 5 may be used in a situation in which nine 26-RUs are individually allocated (eg, a situation in which nine 26-RUs shown in FIG. 5 are individually allocated).

On the other hand, in the EHT system, it is possible to allocate a plurality of RUs to one STA, for example, in the 'index 60' of Table 6, one 26-RU is one user (that is, on the leftmost side of the 20 MHz band) receiving STA), and one 26-RU and one 52-RU on the right side are allocated for another user (ie, the receiving STA), and 5 26-RUs on the right side are allocated individually can be

A mode in which the common field of EHT-SIG is omitted may be supported. The mode in which the common field of EHT-SIG is omitted may be called compressed mode. When compressed mode is used, a plurality of users (ie, a plurality of receiving STAs) of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) based on non-OFDMA. That is, a plurality of users of the EHT PPDU may decode a PPDU (eg, a data field of the PPDU) received through the same frequency band. On the other hand, when the non-compressed mode is used, a plurality of users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) based on OFDMA. That is, a plurality of users of the EHT PPDU may receive the PPDU (eg, a data field of the PPDU) through different frequency bands.

The EHT-SIG may be configured based on various MCS techniques. As described above, information related to the MCS technique applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on the DCM technique. For example, among the N data tones (eg, 52 data tones) allocated for the EHT-SIG, a first modulation scheme is applied to a continuous half tone, and a second modulation scheme is applied to the remaining consecutive half tones. technique can be applied. That is, the transmitting STA modulates specific control information to a first symbol based on the first modulation scheme and allocates to consecutive half tones, modulates the same control information to a second symbol based on the second modulation scheme, and performs the remaining continuous can be allocated to half the tone. As described above, information (eg, 1-bit field) related to whether the DCM technique is applied to the EHT-SIG may be included in the U-SIG.

The EHT-STF of FIG. 18 may be used to improve automatic gain control estimation in a multiple input multiple output (MIMO) environment or an OFDMA environment. The EHT-LTF of FIG. 18 may be used to estimate a channel in a MIMO environment or an OFDMA environment.

The EHT-STF of FIG. 18 may be set to various types. For example, the first type of STF (ie, 1x STF) may be generated based on the first type STF sequence in which non-zero coefficients are disposed at intervals of 16 subcarriers. The STF signal generated based on the first type STF sequence may have a period of 0.8 µs, and the 0.8 µs period signal may be repeated 5 times to become the first type STF having a length of 4 µs. For example, the second type of STF (ie, 2x STF) may be generated based on the second type STF sequence in which non-zero coefficients are disposed at intervals of 8 subcarriers. The STF signal generated based on the second type STF sequence may have a cycle of 1.6 μs, and the cycle signal of 1.6 μs may be repeated 5 times to become a second type EHT-STF having a length of 8 μs. Hereinafter, an example of a sequence (ie, an EHT-STF sequence) for configuring the EHT-STF is presented. The following sequence may be modified in various ways.

The EHT-STF may be configured based on the following M sequence.

M = {-1, -1, -1, 1, 1, 1, -1, 1, 1, 1, -1, 1, 1, -1, 1}

The EHT-STF for the 20 MHz PPDU may be configured based on the following equation. The following example may be a first type (ie, 1x STF) sequence. For example, the first type sequence may be included in an EHT-PPDU rather than a trigger-based (TB) PPDU. In the following Equation, (a:b:c) may mean a section defined as a b tone interval (ie, subcarrier interval) from a tone index (ie, subcarrier index) to c tone index. For example, Equation 2 below may represent a sequence defined at intervals of 16 tones from tone index -112 to index 112. For EHT-STF, subcarrier spacing of 78.125 kHz is applied, so the 16 tone interval may mean that the EHT-STF coefficient (or element) is disposed at an interval of 78.125 * 16 = 1250 kHz. Also, * means multiplication and sqrt() means square root. In addition, j means an imaginary number.

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

EHT-STF(0) = 0

The EHT-STF for the 40 MHz PPDU may be configured based on the following equation. The following example may be a first type (ie, 1x STF) sequence.

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

The EHT-STF for the 80 MHz PPDU may be configured based on the following equation. The following example may be a first type (ie, 1x STF) sequence.

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

The EHT-STF for the 160 MHz PPDU may be configured based on the following equation. The following example may be a first type (ie, 1x STF) sequence.

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

A sequence for the lower 80 MHz among the EHT-STFs for the 80+80 MHz PPDU may be the same as Equation (4). A sequence for the upper 80 MHz among the EHT-STFs for the 80+80 MHz PPDU may be configured based on the following equation.

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

Equations 7 to 11 below relate to an example of a second type (ie, 2x STF) sequence.

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

The EHT-STF for the 40 MHz PPDU may be configured based on the following equation.

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

EHT-STF(-248) = 0

EHT-STF(248) = 0

The EHT-STF for the 80 MHz PPDU may be configured based on the following equation.

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

The EHT-STF for the 160 MHz PPDU may be configured based on the following equation.

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)

EHT-STF(-8)=0, EHT-STF(8)=0,

EHT-STF(-1016)=0, EHT-STF(1016)=0

A sequence for the lower 80 MHz among the EHT-STFs for the 80+80 MHz PPDU may be the same as Equation (9). A sequence for the upper 80 MHz among the EHT-STFs for the 80+80 MHz PPDU may be configured based on the following equation.

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

EHT-STF(-504)=0,

EHT-STF(504)=0

The EHT-LTF may have a first, second, and third type (ie, 1x, 2x, 4x LTF). For example, the first/second/third type LTF may be generated based on an LTF sequence in which non-zero coefficients are disposed at intervals of 4/2/1 subcarriers. The first/second/third type LTF may have a time length of 3.2/6.4/12.8 μs. In addition, GIs of various lengths (eg, 0.8/1/6/3.2 μs) may be applied to the first/second/third type LTF.

Information on the type of STF and/or LTF (including information on GI applied to the LTF) may be included in the SIG A field and/or the SIG B field of FIG. 18 .

The PPDU of FIG. 18 (ie, EHT-PPDU) may be configured based on the examples of FIGS. 5 and 6 .

For example, the EHT PPDU transmitted on the 20 MHz band, that is, the 20 MHz EHT PPDU may be configured based on the RU of FIG. 5 . That is, the location of the RU of the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in FIG. 5 .

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

Since the RU location of FIG. 6 corresponds to 40 MHz, if the pattern of FIG. 6 is repeated twice, a tone-plan for 80 MHz may be determined. That is, the 80 MHz EHT PPDU may be transmitted based on a new tone-plan in which the RU of FIG. 6 is repeated twice instead of the RU of FIG. 7 .

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

The tone-plan for 160/240/320 MHz may be configured in the form of repeating the pattern of FIG. 6 several times.

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

The receiving STA may determine the type of the receiving PPDU as an EHT PPDU based on the following items. For example, 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) the RL-SIG where the L-SIG of the received PPDU is repeated is detected, 3) the L-SIG of the received PPDU is Length When a result of applying "modulo 3" to the field value is detected as 0, the received PPDU may be determined as an EHT PPDU. When it is determined that the received PPDU is an EHT PPDU, the receiving STA determines the type of the EHT PPDU (eg, SU/MU/Trigger-based/Extended Range type) based on bit information included in the symbols after the RL-SIG of FIG. 18 . ) can be detected. In other words, the receiving STA 1) the first symbol after the L-LTF signal, which is BSPK, 2) the RL-SIG that is continuous to the L-SIG field and is the same as the L-SIG, 3) the result of applying "modulo 3" is 0 Based on the L-SIG including the Length field set to , and 4) the 3-bit PHY version identifier (eg, the PHY version identifier having the first value) of the above-described U-SIG, the received PPDU is converted into an EHT PPDU can be judged as

For example, the receiving STA may determine the type of the receiving PPDU as the HE PPDU based on the following items. For example, 1) the first symbol after the L-LTF signal is BPSK, 2) RL-SIG where L-SIG is repeated is detected, and 3) "modulo 3" is applied to the Length value of L-SIG. When the result is detected as "1" or "2", the received PPDU may be determined as an HE PPDU.

For example, the receiving STA may determine the type of the received PPDU as non-HT, HT, and VHT PPDU based on the following items. For example, if 1) the first symbol after the L-LTF signal is BPSK, and 2) RL-SIG in which L-SIG is repeated is not detected, the received PPDU is determined to be non-HT, HT and VHT PPDU. can In addition, even if the receiving STA detects the repetition of the RL-SIG, if the result of applying "modulo 3" to the Length value of the L-SIG is detected as 0, the received PPDU is determined as non-HT, HT and VHT PPDU can be

In the example below, (transmit/receive/uplink/downlink) signals, (transmit/receive/uplink/downlink) frames, (transmit/receive/uplink/downlink) packets, (transmit/receive/uplink/downlink) data units, ( A signal indicated by transmission/reception/uplink/downlink) data, etc. may be a signal transmitted/received based on the PPDU of FIG. 18 . The PPDU of FIG. 18 may be used to transmit and receive various types of frames. For example, the PPDU of FIG. 18 may be used for a control frame. Examples of the control frame may 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, the PPDU of FIG. 18 may be used for a management frame. An example of the management frame may include a Beacon frame, a (Re-)Association Request frame, a (Re-)Association Response frame, a Probe Request frame, and a Probe Response frame. For example, the PPDU of FIG. 18 may be used for a data frame. For example, the PPDU of FIG. 18 may be used to simultaneously transmit at least two or more of a control frame, a management frame, and a data frame.

Each device/STA of the sub-drawings (a)/(b) of FIG. 1 may be modified as shown in FIG. 19 . The transceiver 630 of FIG. 19 may be the same as the

transceivers

113 and 123 of FIG. 1 . The transceiver 630 of FIG. 19 may include a receiver and a transmitter.

The processor 610 of FIG. 19 may be the same as the

processors

111 and 121 of FIG. 1 . Alternatively, the processor 610 of FIG. 19 may be the same as the

processing chips

114 and 124 of FIG. 1 .

The memory 150 of FIG. 19 may be the same as the

memories

112 and 122 of FIG. 1 . Alternatively, the memory 150 of FIG. 19 may be a separate external memory different from the

memories

112 and 122 of FIG. 1 .

Referring to FIG. 19 , the power management module 611 manages 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 result processed by the processor 610 . Keypad 614 receives input to be used by processor 610 . A keypad 614 may be displayed on the display 613 . SIM card 615 may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) used to identify and authenticate subscribers in mobile phone devices, such as mobile phones and computers, and keys associated therewith. .

Referring to FIG. 19 , the speaker 640 may output a sound related result processed by the processor 610 . Microphone 641 may receive sound related input to be used by processor 610 .

20 shows an example of a HE-PPDU.

The illustrated L-STF 2000 may include a short training orthogonal frequency division multiplexing symbol (OFDM). The L-STF 2000 may be used for frame detection, automatic gain control (AGC), diversity detection, and coarse frequency/time synchronization.

The L-LTF 2010 may include a long training orthogonal frequency division multiplexing symbol (OFDM). The L-LTF 2010 may be used for fine frequency/time synchronization and channel prediction.

The L-SIG 2020 may be used to transmit control information. The L-SIG 2020 may include information on a data rate and a data length. Also, the L-SIG 2020 may be repeatedly transmitted. That is, the L-SIG 2020 may be configured in a repeating format (eg, may be referred to as R-LSIG).

The HE-SIG-A 2030 may include control information common to the receiving stations.

Specifically, HE-SIG-A 2030 is, 1) DL/UL indicator, 2) BSS color field that is an identifier of BSS, 3) field indicating the remaining time of the current TXOP section, 4) 20, Bandwidth field indicating whether 40, 80, 160, 80+80 MHz, 5) field indicating MCS technique applied to HE-SIG-B, 6) HE-SIG-B dual subcarrier modulation for MCS ( Dual subcarrier modulation) an indication field for whether modulation is performed, 7) a field indicating the number of symbols used for HE-SIG-B, 8) indicating whether HE-SIG-B is generated over the entire band field, 9) a field indicating the number of symbols of HE-LTF, 10) a field indicating a length of HE-LTF and a CP length, 11) a field indicating whether additional OFDM symbols exist for LDPC coding, 12) It may include information on a field indicating control information on Packet Extension (PE), 13) a field indicating information on CRC field of HE-SIG-A, and the like. This specific field of HE-SIG-A may be added or some may be omitted. In addition, some fields may be added or omitted in other environments where HE-SIG-A is not a multi-user (MU) environment.

Also, HE-SIG-A 2030 may be composed of two parts: HE-SIG-A1 and HE-SIG-A2. HE-SIG-A1 and HE-SIG-A2 included in HE-SIG-A may be defined in the following format structure (field) according to the PPDU. First, the HE-SIG-A field of the HE SU PPDU may be defined as follows.

In addition, the HE-SIG-A field of the HE MU PPDU may be defined as follows.

In addition, the HE-SIG-A field of the HE TB PPDU may be defined as follows.

The HE-SIG-B 2040 may be included only in the case of a PPDU for multiple users (MUs) as described above. Basically, the HE-SIG-A 2050 or the HE-SIG-B 2060 may include resource allocation information (or virtual resource allocation information) for at least one receiving STA.

In the 802.11be (ie, EHT) standard, in order to improve throughput and increase spectrum efficiency, multiple RUs may be allocated to transmit signals. However, only the whole bandwidth was used in the SU PPDU of the 802.11ax standard. Therefore, through the RU allocation of the 802.11ax standard, an indication for multiple RU allocation cannot be performed.

Therefore, in order to efficiently use multiple RUs in SU transmission, an indication for multiple RUs allocated in the EHT standard may be required. In the following specification, a technical feature regarding a multiple RU indication for efficiently transmitting a signal using multiple RU allocation for a single STA may be proposed.

EHT PPDU의 구성Configuration of EHT PPDU

In order to provide a higher data rate than the 802.11ax standard, the EHT standard may be proposed. The EHT standard may support a wide bandwidth (eg, a bandwidth of 320 MHz or more), 16 streams, and/or multi-link (or multi-band) operation. Therefore, to support a transmission method based on the EHT standard, a new frame format may be used. When transmitting a signal through the 2.4/5/6 GHz band using the new frame format, convention Wi-Fi receivers (or STAs) (eg, 802.11n) as well as a receiver (receiver) supported by the EHT standard Receivers according to the /ac/ax standard) may also receive the EHT signal transmitted through the 2.4/5/6 GHz band.

The preamble of the PPDU based on the EHT standard may be set in various ways. Hereinafter, an embodiment in which a preamble of a PPDU based on the EHT standard is configured may be described. Hereinafter, a PPDU based on the EHT standard may be described as an EHT PPDU. However, the EHT PPDU is not limited to the EHT standard. The EHT PPDU may include not only the 802.11be standard (ie, the EHT standard), but also a PPDU based on a new standard obtained by improving/evolving/extending the 802.11be standard.

In the EHT standard, a format for a single user (SU) and a format for a multi user (MU) may be identically configured. Accordingly, the EHT PPDU for the SU and the MU may be referred to as an EHT MU PPDU. Hereinafter, for convenience of description, an EHT MU PPDU may be described as an EHT PPDU.

21 shows an example of an EHT PPDU.

Referring to FIG. 21 , the EHT PPDU 2100 may include an L-part 2110 and an EHT-part 2120 . The EHT PPDU 2100 may be configured in a format to support backward compatibility. In addition, the EHT PPDU 2100 may be transmitted to a single STA (single STA) and/or multiple STAs.

The EHT PPDU 2100 may be configured in a structure in which the L-part 2110 is first transmitted before the EHT-part 2120 for coexistence with the legacy STA (STA according to the 802.11n/ac/ax standard). have. For example, the L-part 2110 may include L-STF, L-LTF, and L-SIG.

According to an embodiment, the EHT part 2120 may include RL-SIG, U-SIG 2121, EHT-SIG 2122, EHT-STF, EHT-LTF and EHT-data fields. For example, the U-SIG 2121 may include a version independent field and a version dependent field. An example of the U-SIG 2121 may be described with reference to FIG. 22 .

22 shows an example of U-SIG.

Referring to FIG. 22 , the U-SIG 2200 may correspond to the U-SIG 2121 of FIG. 21 . The U-SIG 2200 may include a Version independent field 2210 and a Version dependent field 2220 .

According to an embodiment, the version independent field 2210 may include a version identifier of 3 bits indicating the EHT standard and the Wi-Fi version after the EHT standard. In other words, the version independent field 2210 may include 3 bits of information about the EHT standard and the Wi-Fi version after the EHT standard.

According to an embodiment, the version independent field 2210 may further include a 1-bit DL/UL field, a field related to BSS color, and/or a field related to TXOP duration. In other words, the version independent field 2210 may further include 1-bit information on DL/UL, information on BSS color, and/or information on TXOP duration.

According to an embodiment, the version dependent field 2220 may include a field/information about a PPDU format type, a field/information about a bandwidth, and/or a field/information about an MCS.

According to an embodiment, the U-SIG 2200 may consist of two symbols. The two symbols may be jointly encoded. According to an embodiment, the U-SIG 2200 may be configured with 52 data tones and 4 pilot tones for each 20 MHz. In addition, it may be modulated in the same manner as HE-SIG-A of the HE standard. For example, the U-SIG 2200 may be modulated with BPSK and a code rate of 1/2.

Referring back to FIG. 21 , the EHT-SIG 2122 may include a version dependent field that is not included in the U-SIG 2121 . In other words, the EHT-SIG 2122 may include information overflowed from the U-SIG 2121 . For example, the EHT-SIG 2122 may include information dependent on the version of the PPDU. For another example, the EHT-SIG 2122 may include at least some of fields included in HE-SIG-A of the HE specification.

According to an embodiment, the EHT-SIG 2122 may consist of a plurality of OFDM symbols. According to an embodiment, the EHT-SIG 2122 may be modulated with various MCSs. For example, the EHT-SIG 2122 may be modulated based on MCS0 to MCS5.

According to an embodiment, the EHT-SIG 2122 may include a common field and a user specific field. For example, the common field may include information on spatial stream information and information on RU allocation. For example, the user specific field may include at least one user block field including information about the user. The user specific field may include/indicate information on information ID, MCS, and coding used for a specific user or STA. As an example, the user specific field may include at least one user block field.

According to an embodiment, in the EHT standard, SU transmission may be performed using 20/40/80/160/240/320 MHz. At this time, when the STA of the EHT standard (hereinafter, the EHT STA) cannot use the full band width due to the channel condition, it may transmit a signal using a non-continuous bandwidth.

For example, the non-continuous bandwidth may be configured in units of 20 MHz. In order to perform SU transmission using the non-continuous bandwidth configured in units of 20 MHz, the EHT STA (ie, the transmitting STA) may allocate multiple RUs to the receiving STA in various ways, based on the allocated multiple RUs. , SU transmission may be performed. Hereinafter, technical features for the allocation of multiple RUs may be described below.

SU transmission using non-continuous bandwidth can be applied from 80MHz. At this time, the configuration of the RU used for SU transmission consists of a continuous RU of 60/100/120/140/180/200/220/260/280/300 MHz and two non-continuous RUs within the allocated BW. Considering that, it can be configured as follows. In other words, the configuration of the RU used for SU transmission may consist of two non-continuous RUs. For example, a 260 MHz non-continuous RU may be configured with a 20 MHz RU and a 240 MHz RU discontinuous from the 20 MHz RU.

The size of an RU used for SU transmission may be configured as 242, 484, or 996. Multiple RUs may be allocated based on 242 RUs.

Hereinafter, for convenience of description, it may be assumed that P20 (Primary 20 MHz) is 242 RUs that come first in the RU location. The location of P20 is exemplary, and P20 may exist in a different location.

In addition, in order to express the configuration of a non-continuous multiple RU in units of 20 MHz (or units of 242 RUs), the RU allocation position may be expressed as 1. In addition, the configuration of multiple RUs may be expressed in square brackets (ie, []) in units of 80 MHz. For example, multiple RUs at 80 MHz may be expressed as [a b c d]. Each of a, b, c, and d may be set to one of 0 and 1. As an example, multiple RUs at 80 MHz may be expressed as [1 0 0 1]. This may mean that multiple RUs at 80 MHz are configured with first and fourth RUs of 20 MHz. As another example, multiple RUs at 160 MHz may be expressed as [a b c d] [e f g h]. A configuration of multiple RUs may be described based on the above-described expression.

1. 20 MHz case

1-A. 242 (RU)

2. 40 MHz case

2-A. 494 (RU)

3. 80 MHz case

For example, in 80 MHz, multiple RUs may be configured in non-continuous 40 MHz (hereinafter, 3-A). For another example, in 80 MHz, multiple RUs may be configured in non-continuous 60 MHz (hereinafter, 3-B). As another example, in 80 MHz, multiple RUs may be configured in the entire 80 MHz (hereinafter, 3-C).

3-A. Non-continuous 40MHz

3-A-i) 242+242 (RU)

The allocation position of 242 RUs may be expressed as [1 0 1 0] and [1 0 0 1] within 80 MHz. In this case, 1 may indicate allocated 242 RUs and 0 may indicate unassigned 242 RUs. Here, a comma (,) can be used to separate cases. That is, in the above example, the allocation position of 242 RUs may be configured as [1 0 1 0] within 80 MHz or as [1 0 0 1] within 80 MHz. The same may be used in the following.

3-B. Non-continuous 60MHz

3-B-i) 242 + 484 (RU) - [1 0 1 1]

3-B-ii) 484 + 242 (RU) - [1 1 0 1], [1 1 1 0]

3-C. 996 RU

4. 160 MHz case

4-A. 100 MHz case

4-A-i) In case P80 MHz (ie, primary 80 MHz) allocates only P20 and allocates S80 (ie secondary 80 MHz) for transmission

4-A-i)-a. 242+996 - [1 0 0 0] [1 1 1 1]

4-A-ii) In case of allocating P40 (ie, primary 40 MHz) in P80 MHz and allocating non-continuous 60 MHz in S80 for transmission

4-A-ii)-a. 484 + [484+242] - [1 1 0 0] [1 1 0 1], [1 1 0 0] [1 1 1 0]

4-A-ii)-b. 484 + [242+484] - [1 1 0 0] [1 0 1 1], [1 1 0 0] [0 1 1 1]

4-A-iii) In case of allocating non-continuous 60 MHz including P40 in P80 MHz and allocating 40 MHz in S80 for transmission

4-A-iii)-a. 484+242+484 - [1 1 1 0] [1 1 0 0], [1 1 0 1] [1 1 0 0]

4-A-iv) In case of allocating P80 and allocating 20 MHz in S80 for transmission

4-A-iv)-a. 996+242 - [1 1 1 1] [1 0 0 0], [1 1 1 1] [0 1 0 0], [1 1 1 1] [0 0 1 0], [1 1 1 1] [ 0 0 0 1]

4-B. 120MHz case

4-B-i) When P80 allocates non-continuous 60 MHz and S80 allocates non-continuous 60 MHz and transmits

4-B-i)-a. [242+484] [242+484] - [1 0 1 1] [1 0 1 1], [1 0 1 1] [0 1 1 1]

4-B-i)-b. [242+484] [484+242] - [1 0 1 1] [1 1 1 0]

4-B-i)-c. [484+242] [242+484] - [1 1 0 1] [1 0 1 1], [1 1 0 1] [0 1 1 1], [1 1 1 0] [1 0 1 1], [1 1 1 0] [0 1 1 1]

4-B-i)-d. [484+242] [484+242] - [1 1 0 1] [1 1 0 1], [1 1 0 1] [1 1 1 0], [1 1 1 0] [1 1 0 1], [1 1 1 0] [1 1 1 0]

4-B-ii) In case of allocating non-continuous 40 MHz in P80 MHz and allocating S80 for transmission

4-B-ii)-a. 484+996 - [1 0 1 0] [1 1 1 1], [1 0 0 1] [1 1 1 1]

4-B-iii) In case of transmission by allocating P40 MHz and allocating S80 in P80 MHz

4-B-iii)-a. 484+996 - [1 1 0 0][1 1 1 1]

4-B-iv) In case of allocating P80 and transmitting non-continuous 40 MHz in S80

4-B-iv)-a. 996+[242+242] - [1 1 1 1] [1 0 0 1], [1 1 1 1] [1 0 1 0], [1 1 1 1] [1 0 0 1]

4-B-v) When P80 is allocated and 40 MHz is allocated from S80 and transmitted

4-B-v)-a. 996+484 - [1 1 1 1] [1 1 0 0], [1 1 1 1] [0 0 1 1]

4-C. 140 MHz case

4-C-i) In case of allocating non-continuous 60 MHz in P80 MHz and allocating S80 for transmission

4-C-i)-a. [242+484] [996] - [1 0 1 1] [1 1 1 1]

4-C-ii) [484+242] [996] - [1 1 0 1] [1 1 1 1] , [1 1 1 0] [1 1 1 1]

4-D. 996+996

5. 240 MHz

5-A. At 240 MHz, various non-continuous channels may be configured/formed in consideration of the 20 MHz channel. However, in order to reduce the ease of implementation and signaling overhead, an RU configuration including only one non-continuous part may be proposed. This is one embodiment, and RUs in various locations may be configured.

5-B. 160MHz case

5-B-i) Assign P80 and one of the two 80 MHz

5-B-i)-a. 996+996 - [1 1 1 1] [1 1 1 1] [0 0 0 0], [1 1 1 1] [0 0 0 0] [1 1 1 1]

5-C. 180 MHz case

5-C-i) Assign P20 MHz to P80 MHz

5-C-i)-a. 242+996+996 - [1 0 0 0] [1 1 1 1] [1 1 1 1]

5-C-i)-b. 242+242+996+484+242 - [1 0 0 1] [1 1 1 1] [1 1 1 0]

5-C-i)-c. 242+484+996+242 - [1 0 1 1] [1 1 1 1] [1 0 0 0]

5-C-ii) Assign P40 MHz to P80 MHz

5-C-ii)-a. 484+996+484+242 - [1 1 0 0] [1 1 1 1] [1 1 1 0]

5-C-ii)-b. 484+242+996+242 - [1 1 0 1] [1 1 1 1] [1 0 0 0]

5-C-iii) P80 MHz assignment

5-C-iii)-a. 996+242+996 - [1 1 1 1] [1 0 0 0] [1 1 1 1], [1 1 1 1] [0 0 0 1] [1 1 1 1]

5-C-iii)-b. 996+484+484+242 - [1 1 1 1] [1 1 0 0] [1 1 1 0], [1 1 1 1] [0 0 1 1] [1 1 1 0]

5-C-iii)-c. 996+484+242+484 - [1 1 1 1] [1 1 1 0] [1 1 0 0], [1 1 1 1] [1 1 0 1] [1 1 0 0]

5-C-iii)-d. 996+242+484+484 - [1 1 1 1] [0 1 1 1] [1 1 0 0], [1 1 1 1] [1 0 1 1] [1 1 0 0]

5-C-iii)-e. 996+996+242 - [1 1 1 1] [1 1 1 1] [0 1 0 0], [1 1 1 1] [1 1 1 1] [0 0 1 0], [1 1 1 1] [1 1 1 1] [0 0 0 1], [1 1 1 1] [1 1 1 1] [1 0 0 0]

5-D. 200 MHz case

5-D-i) Assign P20 MHz to P80 MHz

5-D-i)-a. 242+242+996+996 - [1 0 0 1] [1 1 1 1] [1 1 1 1]

5-D-i)-b. 242+484+996+484+242 - [1 0 1 1] [1 1 1 1] [1 1 1 0]

5-D-ii) Assign P40 MHz to P80 MHz

5-D-ii)-a. 484+996+996 - [1 1 0 0] [1 1 1 1] [1 1 1 1]

5-D-ii)-b. 484+242+996+484+242 - [1 1 1 0] [1 1 1 1] [1 1 1 0], [1 1 0 1] [1 1 1 1] [1 1 1 0]

5-D-iii) P80MHz assignment

5-D-iii)-a. 996+484+996 - [1 1 1 1] [1 1 0 0] [1 1 1 1], [1 1 1 1] [0 0 1 1][1 1 1 1]

5-D-iii)-b. 996+242+484+484+242 - [1 1 1 1] [1 0 1 1] [1 1 1 0]

5-D-iii)-c. 996+484+242+484+242 - [1 1 1 1] [1 1 1 0] [1 1 1 0]

5-D-iii)-d. 996+996+484 - [1 1 1 1] [1 1 1 1] [1 1 0 0], [1 1 1 1] [1 1 1 1] [0 0 1 1]

5-E. 220 MHz case

5-E-i) Assign P20 MHz to P80 MHz

5-E-i)-a. 242+484+996+996 - [1 0 1 1] [1 1 1 1] [1 1 1 1]

5-E-ii) Assign P40 MHz in P80 MHz

5-E-ii)-a. 484+242+996+996 - [1 1 0 1] [1 1 1 1] [1 1 1 1], [1 1 1 0] [1 1 1 1] [1 1 1 1]

5-E-iii) P80MHz assignment

5-E-iii)-a. 996+242+484+996 - [1 1 1 1] [1 0 1 1] [1 1 1 1]

5-E-iii)-b. 996+484+242+996 - [1 1 1 1] [1 1 0 1] [1 1 1 1], [1 1 1 1] [1 1 1 0] [1 1 1 1]

5-E-iii)-c. 996+996+484+242 - [1 1 1 1] [1 1 1 1] [1 1 0 1], [1 1 1 1] [1 1 1 1] [1 1 1 0]

5-E-iii)-d. 996+996+242+484 - [1 1 1 1] [1 1 1 1] [1 0 1 1]

5-F. 996+996+996

6. 320 MHz case

6-A. 240 MHz

6-A-i) In case of allocating P80 and allocating two out of three 80 MHz, that is, puncturing one 80 MHz

6-A-i)-a. 996+996+996 - [1 1 1 1] [0 0 0 0] [1 1 1 1] [1 1 1 1], [1 1 1 1] [1 1 1 1] [0 0 0 0] [ 1 1 1 1], [1 1 1 1] [1 1 1 1] [1 1 1 1] [0 0 0 0]

6-B. 260 MHz case

6-B-i) Assign P20 MHz to P80 MHz

6-B-i)-a. 242+996+996+996 - [1 0 0 0] [1 1 1 1] [1 1 1 1] [1 1 1 1]

6-B-ii) Assign P40 MHz to P80 MHz

6-B-ii)-a. 484+242+484+996+996 - [1 1 0 0] [0 1 1 1] [1 1 1 1] [1 1 1 1], [1 1 1 0] [0 0 1 1] [1 1 1 1] [1 1 1 1]

6-B-ii)-b. 484+996+996+484+242 - [1 1 0 0] [1 1 1 1] [1 1 1 1] [1 1 1 0]

6-B-iii) P80MHz assignment

6-B-iii)-a. 996+242+996+996 - [1 1 1 1] [1 0 0 0] [1 1 1 1] [1 1 1 1], [1 1 1 1] [0 0 0 1] [1 1 1 1 ] [1 1 1 1]

6-B-iii)-b. 996+484+[242+484]+996 - [1 1 1 1] [1 1 0 0] [0 1 1 1] [1 1 1 1]

6-B-iii)-c. 996+[484+242]+484+996 - [1 1 1 1] [1 1 1 0] [0 0 1 1] [1 1 1 1]

6-B-iii)-d. 996+996+242+996 - [1 1 1 1] [1 1 1 1] [1 0 0 0] [1 1 1 1], [1 1 1 1] [1 1 1 1] [0 0 0 1 ] [1 1 1 1]

6-B-iii)-e. 996+996+484+484+242 - [1 1 1 1] [1 1 1 1] [1 1 0 0] [1 1 1 0], [1 1 1 1] [1 1 1 1] [0 0 1 1] [1 1 1 0]

6-B-iii)-f. 996+996+[242+484]+484 - [1 1 1 1] [1 1 1 1] [1 0 1 1] [1 1 0 0], [1 1 1 1] [1 1 1 1] [ 0 1 1 1] [1 1 0 0]

6-B-iii)-g. 996+996+[484+242]+484 - [1 1 1 1] [1 1 1 1] [1 1 1 0] [0 0 1 1], [1 1 1 1] [1 1 1 1] [ 1 1 0 1] [1 1 0 0]

6-B-iii)-h. 996+996+996+242 - [1 1 1 1] [1 1 1 1] [1 1 1 1] [ 1 0 0 0 ], [1 1 1 1] [1 1 1 1] [1 1 1 1 ] [0 1 0 0], [1 1 1 1] [1 1 1 1] [1 1 1 1] [0 0 1 0], [1 1 1 1] [1 1 1 1] [1 1 1 1 ][0 0 0 1]

6-C. 280 MHz case

6-C-i) Assign P40 MHz to P80 MHz

6-C-i)-a. 484+996+996+996 - [1 1 0 0] [1 1 1 1] [1 1 1 1] [1 1 1 1]

6-C-i)-b. [484+242]+[242+484]+996+996 - [1 1 1 0] [0 1 1 1] [1 1 1 1] [1 1 1 1]

6-C-i)-c. [484+242]+996+996+[484+242] - [1 1 1 0] [1 1 1 1] [1 1 1 1] [1 1 1 0], [1 1 0 1] [1 1 1 1] [1 1 1 1] [1 1 1 0]

6-C-ii) P80 MHz assignment

6-C-ii)-a. 996+484+242+242+484+996 - [1 1 1 1] [1 1 1 0] [0 1 1 1] [1 1 1 1]

6-C-ii)-b. 996+996+484+242+242+484 - [1 1 1 1] [1 1 1 1] [1 1 1 0] [0 1 1 1]

6-C-ii)-c. 996+996+484+242+484+242 - [1 1 1 1] [1 1 1 1] [1 1 0 1] [1 1 1 0]

6-C-ii)-d. 996+996+996+242 - [1 1 1 1] [1 1 1 1] [1 1 1 1] [1 0 0 0], [1 1 1 1] [1 1 1 1] [1 1 1 1 ] [0 1 0 0], [1 1 1 1] [1 1 1 1] [1 1 1 1] [0 0 1 0], [1 1 1 1] [1 1 1 1] [1 1 1 1 ] [0 0 0 1]

6-C-ii)-e. 996+484+996+996 - [1 1 1 1] [1 1 0 0] [1 1 1 1] [1 1 1 1], [1 1 1 1] [0 0 1 1] [1 1 1 1 ] [1 1 1 1]

6-C-ii)-f. 996+996+484+996 - [1 1 1 1] [1 1 1 1] [1 1 0 0] [1 1 1 1], [1 1 1 1] [0 0 1 1] [1 1 1 1 ] [1 1 1 1]

6-C-ii)-g. 996+996+996+484 - [1 1 1 1] [1 1 1 1] [1 1 1 1] [1 1 0 0], [1 1 1 1] [0 0 1 1] [1 1 1 1 ] [1 1 1 1]

6-D. 300 MHz case

6-D-i) Assign P40 MHz to P80 MHz

6-D-i)-a. [484+242]+996+996+996 - [1 1 1 0] [1 1 1 1] [1 1 1 1] [1 1 1 1], [1 1 0 1] [1 1 1 1] [ 1 1 1 1] [1 1 1 1]

6-D-ii) P80 MHz assignment

6-D-ii)-a. 996+[484+242]+996+996 - [1 1 1 1] [1 1 0 1] [1 1 1 1] [1 1 1 1]

6-D-ii)-b. 996+[242+484]+996+996 - [1 1 1 1] [1 0 1 1] [1 1 1 1] [1 1 1 1]

6-D-ii)-c. 996+996+[242+484]+996 - [1 1 1 1] [1 1 1 1] [1 0 1 1] [1 1 1 1]

6-D-ii)-e. 996+996+[484+242]+996 - [1 1 1 1] [1 1 1 1] [1 1 0 1] [1 1 1 1]

6-D-ii)-f. 996+996+996+[242+484] - [1 1 1 1] [1 1 1 1][1 1 1 1] [1 0 1 1]

6-D-ii)-g. 996+996+996+[484+242] - [1 1 1 1] [1 1 1 1] [1 1 1 1] [1 1 0 1]

6-E. 996+996+996+996 - [1 1 1 1] [1 1 1 1] [1 1 1 1] [1 1 1 1]

As in the above example, various BWs and various combinations of RU/preamble puncturing may be used for SU transmission. Accordingly, in order to perform SU transmission as in the above-described example, a technical feature of transmitting the above-described RU combination/preamble puncturing information may be proposed below.

제1 실시 예first embodiment

According to the first embodiment, information on RU combination/preamble puncturing may be transmitted by configuring an allocation/puncturing bit map including combinations of various BW combinations and RU combinations.

A. 7-bit information is required to indicate the number of combinations of various continuous BWs and multiple RUs (consisting of two non-continuous RUs) configured in the above example. Accordingly, the 7-bit table for indicating the combination may be configured as follows.

B. A multiple RU allocation/puncturing table (7 bit table) for SU transmission may be configured as shown in Tables 21 to 29.

In the above-described embodiment, RU allocation/preamble puncturing having only one non-continuous part has been proposed. In order to use the resource more flexibly than in the above-described embodiment, RU combination/preamble puncturing in which the number of non-continuous parts is 2-3 may also be considered. Therefore, in order to use such flexible RU allocation, the RU indication/preamble puncturing bit table may be configured as an 8-bit table. The 8-bit table may be configured similarly to the above-described 7-bit table, and the 8-bit table may indicate an entire RU combination for BW. The 8-bit table may include information on all RU combinations for BW.

1. When the allocation information configured as described above is used, the BW may be composed of 3 bits to indicate 20, 40, 80, 160/80+80, 240/160+80, 160+160/320.

As described above, in order to perform SU transmission using various BW and RU combinations, allocation/puncturing information may be transmitted as follows.

i. The SU-PPDU (or MU PPDU) may be configured to include a user field/EHT-SIG. In this case, allocation information for the above-described RU combination may be included in the user field/EHT-SIG.

i-1. The user field/EHT-SIG may be configured to include RU allocation information like the common field of 11ax HE-SIGB. In addition, the user field/EHT-SIG may include a CRC and a tail bit.

i-2. The user field/EHT-SIG may include user specific information and may include one STA-ID during SU transmission.

i-3. The User field may be located after the EHT-SIGA or after the U-SIG when there is no EHT-SIGA.

i-4. The User field/EHT-SIG is configured in units of 20 MHz/40 MHz and may be transmitted by duplication during wide bandwidth transmission.

i-4-A. User field/EHT-SIG may have different configuration granularity according to transmission BW. For example, user field/EHT-SIG may be configured in units of 20 MHz up to 160 MHz, and user field/EHT-SIG may be configured and transmitted in units of 40 MHz for BW above 240 MHz.

i-4-B. When the user field/EHT-SIG is transmitted using different granularities, the granularity may be indicated through the U-SIG. In this case, 1 bit may be used to indicate the granularity.

ii. According to an embodiment, unlike the above-described example, the RU allocation information may be transmitted while being included in the EHT-SIGA during SU transmission. The EHT-SIGA may be configured with a common control field and an RU allocation bit during SU transmission. In EHT-SIGA, the information is jointly encoded and may include one CRC and a tail bit.

ii-1. EHT-SIGA can be applied with the same modulation and code rate as 11ax HE-SIGA.

iii. In another embodiment, the bit table including the BW and RU allocation/preamble puncturing information may be transmitted through the U-SIG of the EHT-PPDU.

iii-1. Accordingly, all information on M-RU aggregation/preamble puncturing can be indicated during SU transmission using the BW field and the bit table.

iii-1-A. Information on preamble puncturing/allocated occupied BW for the entire band may be indicated using the U-SIG field.

iii-2. The allocation bit map may be transmitted using the BW field of the U-SIG.

iii-2-A. Unlike the above example, all information on M-RU aggregation/preamble puncturing may be indicated during SU transmission using the BW field.

제2 실시 예 second embodiment

According to the second embodiment, the presence or absence of RU allocation per 20 MHz (ie, 242 tone RUs) may be indicated.

A. BW may be composed of 3/4 bits to represent 20,40,80,160/80+80,240/160+80,160+160/320. When a case of non-continuous BW (eg, preamble punctured BW) is included, the BW may be composed of 4 bits.

B. Information on BW may be transmitted through the BW field. Information on M-RU aggregation/preamble puncturing may be transmitted/indicated using allocation/pattern information included in the EHT-SIG/User field.

C. Information on 20 MHz allocated in the BW used by the STA may be individually indicated in units of 20 MHz. In this case, the information may be configured as follows.

C-i. Information on 20 MHz allocated in the BW in units of 80 MHz may be indicated. The information may consist of 4 bits per 80 MHz channel. That is, information on 20 MHz allocated within 80 MHz may be indicated as [x1 x2 x3 x4]. Here, x1 to x4 may be set to 1 or 0. x1 to x4 may be set to 1 when the corresponding 20 MHz channel is allocated. x1 to x4 may be set to 0 when the corresponding 20 MHz channel is not allocated. That is, x1 may indicate whether the first 20 MHz is allocated within the 80 MHz bandwidth or whether preamble puncturing is applied. x2 may indicate whether the second 20 MHz is allocated within the 80 MHz bandwidth or whether preamble puncturing is applied. x3 may indicate whether the third 20 MHz is allocated within the 80 MHz bandwidth or whether preamble puncturing is applied. x4 may indicate whether the fourth 20 MHz is allocated within the 80 MHz bandwidth or whether preamble puncturing is applied.

C-i-1. For example, non-continuous RUs (ie, multiple RUs) may be allocated within 80 MHz. The allocated RU may be 484+242 (third 20MHz channel). In this case, the information may be set to [1 1 1 0] as an indication for the allocated RU.

C-ii. For example, when the BW is less than 80 MHz, it is composed of 4 bits, and when the BW is greater than 80 MHz, the information about 20 MHz allocated in the BW can be composed of N*4 bits. Here, N may mean the number of 80 MHz channels. * can mean multiplication. Accordingly, when the EHT STA (ie, the transmitting STA) transmits a signal (eg, EHT PPDU) using 320 MHz, RU allocation may be indicated using 4*4 = 16 bits.

C-ii-1. As an example, the bit size for the indication of RU allocation may be changed according to the transmission BW.

C-ii-2. As another example, unlike the example of C-ii-1, the EHT STA may individually indicate whether to allocate 20 MHz in units of 80 MHz to indicate RU allocation with the same bit size. In this case, the information for the indication of RU allocation may be transmitted while being included in the version dependent information of the U-SIG. And, the U-SIG may be configured differently in units of 80 MHz.

C-ii-3. As another example from the above-described example, the above-described information on RU allocation/puncturing may be used to indicate puncturing information for 80 MHz. The puncturing information for the 80 MHz may be transmitted by being included in the version independent information of the U-SIG in units of 80 MHz. In addition, puncturing information for the entire BW may be transmitted through the EHT-SIG field.

C-ii-3-A. In this case, the BW field may not include puncturing information.

C-ii-3-B. That is, the U-SIG may include puncturing information for 80 MHz. In addition, puncturing information for the entire BW may be indicated through the EHT-SIG field. In other words, the EHT-SIG field may include puncturing information for the entire BW.

D. According to the above-described embodiment, the EHT STA may individually indicate RU allocation information in units of 20 MHz. Therefore, although the signaling overhead may be slightly large, there is an effect that the EHT STA can indicate the flexible multiple RU combination of the above-described embodiment.

E. According to an embodiment, unlike the above example, allocation bit information may not be variably configured according to BW. The EHT STA may indicate information on the RU allocated to the receiving STA by using allocation bit information of a fixed size for supporting the maximum BW.

E-i. Considering 320 MHz, the allocation bit table may consist of 16 bits. For example, the allocation bit table may be configured as [a1 a2 a3 a4 a5 to a14 a15 a16]. Based on 242 RUs, allocated RUs may be set to 1 and unassigned RUs may be set to 0. The EHT STA may indicate RU allocation information or puncturing information based on the allocation bit table.

F. As described above, in order to perform SU transmission using various BW and RU combinations, RU allocation/puncturing information may be configured and transmitted as follows.

F-i. The SU-PPDU (or MU PPDU) may include a user field/EHT-SIG. In this case, allocation information for the RU combination may be included in the user field/EHT-SIG.

F-i-1. The user field/EHT-SIG may be configured to include RU allocation information like the common field of 11ax HE-SIGB. The user field/EHT-SIG may include a CRC and a tail bit.

F-i-2. The user field/EHT-SIG may include user specific information. In addition, when SU transmission, the user field/EHT-SIG may be configured to include one STA-ID.

F-i-3. The User field may be located after the EHT-SIGA or after the U-SIG when there is no EHT-SIGA.

F-i-4. The User field/EHT-SIG may be configured in units of 20 MHz/40 MHz. The User field/EHT-SIG may be transmitted by duplication during wide bandwidth transmission.

F-i-4-A. User field/EHT-SIG may have different configuration granularity according to transmission BW. For example, user field/EHT-SIG may be configured in units of 20 MHz up to 160 MHz, and user field/EHT-SIG may be configured and transmitted in units of 40 MHz for BW above 240 MHz.

F-i-4-B. When the user field/EHT-SIG is transmitted using different granularities, the granularity may be indicated through the U-SIG. In this case, 1 bit may be used to indicate the granularity.

iii-1. RU allocation information (or information about preamble puncturing) may be configured with 4 bits per 80 MHz. RU allocation information may be transmitted through U-SIG. In this case, the U-SIG may include different information for each 80 MHz.

iii-2. As an example, information on RU allocation/puncturing may be used to indicate puncturing information for 80 MHz. The puncturing information for 80 MHz may be transmitted by being included in version independent information (version independent field) or version dependent information (version dependent field) of the U-SIG in units of 80 MHz. In addition, puncturing information for the entire BW may be transmitted through the EHT-SIG field.

iii-2-A. In this case, the BW field may not include puncturing information.

iii-2-B. That is, the U-SIG may include puncturing information for 80 MHz. In addition, puncturing information for the entire BW may be indicated through the EHT-SIG field. In other words, the EHT-SIG field may include puncturing information for the entire BW.

iii-3. According to an embodiment, unlike the above example, puncturing/RU allocation (RA) information indicated through the U-SIG may be transmitted including information on the entire BW.

iii-3-A. According to the embodiment, since the puncturing/RU allocation (RA) information indicated through the U-SIG includes information on the entire BW, there is an effect that it is not necessary to transmit information on the entire BW through the EHT-SIG. .

제3 실시 예third embodiment

According to the third embodiment, the EHT STA may indicate RU combination information allocated per 80 MHz.

A. According to an embodiment, the EHT STA may indicate information on the RU allocated to the STA in units of 80 MHz during SU transmission. In this case, 80 MHz may be configured with various RUs such as 242, 484, or 996.

23 shows RU allocation at 80 MHz.

Referring to FIG. 23 , RU allocation at 80 MHz may consist of 242, 484, or 996 RUs. That is, 80 MHz may consist of four 242 RUs, two 484 RUs, or one 996 RU.

B. As described above, an RU combination for 80 MHz may be configured as shown in Table 30 in consideration of the RU size constituting 80 MHz.

According to an embodiment, in order to reduce overhead, an RU combination for 80 MHz may be configured as shown in Table 31.

C. Unlike the above-described second embodiment, the EHTS STA may indicate an RU combination using various RU sizes existing within 80 MHz.

D. In order to indicate the RU combination as described above, the EHT STA may indicate information on the allocated RU using 3/4-bit information per 80 MHz. For example, when the BW is greater than 80 MHz, information on the allocated RU may be indicated using information of N*3 / N*4 bits. Here, N may mean the number of 80 MHz channels in the BW.

D-i. Accordingly, in order to indicate information on RU allocation in the channel BW (160/240/320), each allocation bit size may be set to (6 or 8)/ (9 or 12)/ (12 or 16).

For example, when the BW is 80 MHz or less, information on the allocated RU is set to 6 bits (6 bit information), and when the BW exceeds 80 MHz, information on the allocated RU is 8 bits (8 bit information) ) can be set.

For another example, when the BW is 80 MHz or less, information on the allocated RU is set to 9 bits (9 bit information), and when the BW exceeds 80 MHz, information on the allocated RU is 12 bits (12 bits) information) can be set.

For another example, when the BW is 80 MHz or less, information on the allocated RU is set to 12 bits (12 bit information), and when the BW exceeds 80 MHz, information on the allocated RU is 16 bits (16 bits) information) can be set.

D-ii. Unlike the above example, the EHT STA may indicate the RU allocation information configured as described above per 80 MHz. In this case, a fixed bit size (3/4 bit) may be used regardless of BW.

D-iii. The 3/4-bit information may be transmitted through U-SIG per 80 MHz. In this case, the 3 bits of the U-SIG may be set differently.

D-iii-1. The puncturing information may be transmitted through version independent information or version dependent information of the U-SIG.

D-iii-1-A. Information on the allocated RU may include all puncturing information at 80 MHz. Accordingly, information on the allocated RU may be included in version independent information such as BW and transmitted through the U-SIG.

D-iii-1-B. As described above, when puncturing information is indicated in units of 80 MHz, BW may be composed of only 20/40/80/160, 80+80/240, 160+80/320, or 160+160 MHz, which is information on continuous BW. have

D-iii-1-C. As another example, the BW may be configured to include puncturing information.

D-iii-2. For example, information on RU allocation/puncturing may be used to indicate puncturing information for 80 MHz. The puncturing information for 80 MHz may be transmitted by being included in version independent information (version independent field) or version dependent information (version dependent field) of the U-SIG in units of 80 MHz. In addition, puncturing information for the entire BW may be transmitted through the EHT-SIG field.

D-iii-2-A. In this case, the BW field may not include puncturing information.

D-iii-2-B. That is, the U-SIG may include puncturing information for 80 MHz. In addition, puncturing information for the entire BW may be indicated through the EHT-SIG field. In other words, the EHT-SIG field may include puncturing information for the entire BW.

E. According to an embodiment, the EHT STA may indicate information on the allocated RU by indicating puncturing information for each 80 MHz.

E-i. A preamble puncturing pattern at 80 MHz may be configured as shown in Table 32.

E-ii. Accordingly, the EHT STA may indicate/transmit information on preamble puncturing for BW by indicating/transmitting RUs of 242 RUs or more punctured per 80 MHz.

E-iii. As described above, when the preamble puncturing pattern is configured in units of 80 MHz, the EHT STA may indicate/transmit information on preamble puncturing per 80 MHz using 3-bit information. Therefore, there is an effect of reducing overhead.

E-iv. The 3-bit information may be transmitted through U-SIG in units of 80 MHz. In this case, the 3 bits of the U-SIG may be set differently.

E-iv-1. The puncturing information may be transmitted through version independent information or version dependent information of the U-SIG.

E-iv-1-A. The puncturing information may include all puncturing information at 80 MHz. Accordingly, the puncturing information may be transmitted through the U-SIG as version independent information such as BW.

E-iv-1-B. When puncturing information is indicated in units of 80 MHz as described above, the BW may be composed of only 20/40/80/160, 80+80/240, 160+80/320, or 160+160 MHz, which is information on continuous BW have

E-iv-1-C. As another example, the BW may be configured to include puncturing information.

E-V. For example, puncturing information may be used to indicate puncturing information for 80 MHz. The puncturing information for 80 MHz may be transmitted by being included in version independent information (version independent field) or version dependent information (version dependent field) of the U-SIG in units of 80 MHz. In addition, puncturing information for the entire BW may be transmitted through the EHT-SIG field.

E-V-1. In this case, the BW field may not include puncturing information.

E-V-2. That is, the U-SIG may include puncturing information for 80 MHz. In addition, puncturing information for the entire BW may be indicated through the EHT-SIG field. In other words, the EHT-SIG field may include puncturing information for the entire BW.

F, as described above, in order to perform SU transmission using various BW and RU combinations, allocation/puncturing information may be transmitted as follows.

F-i. The EHT STA may transmit a puncturing pattern for 80 MHz in units of 80 MHz through the U-SIG. The EHT STA may indicate puncturing information for all BWs or puncturing information for other 80 MHz through the EHT-SIG for puncturing information for BW greater than 80.

F-i-1. That is, the puncturing information may be configured in two stages.

F-i-1-A. 80MHz puncturing information (U-SIG) + puncturing information for all or other 80 MHz (EHT-SIG)

In other words, the U-SIG may include only puncturing information of an 80 MHz bandwidth. The EHT-SIG may include puncturing information of the entire bandwidth or puncturing information of another 80 MHz bandwidth. For example, when a signal (or PPDU) is transmitted in a 160 MHz bandwidth, the U-SIG of the first 80 MHz bandwidth among 160 MHz may include only puncturing information of the first 80 MHz bandwidth. The EHT-SIG may include puncturing information of the second 80 MHz bandwidth among 160 MHz or may include puncturing information of the entire 160 MHz bandwidth.

F-ii. The SU-PPDU (or MU PPDU) may include a user field/EHT-SIG. In this case, allocation information or puncturing information for the RU combination may be included in the user field/EHT-SIG.

F-ii-1. The user field/EHT-SIG may be configured to include RU allocation information or puncturing information like the common field of 11ax HE-SIGB. The user field/EHT-SIG may include a CRC and a tail bit.

F-ii-2. The user field/EHT-SIG may include user specific information. In addition, when SU transmission, the user field/EHT-SIG may be configured to include one STA-ID.

F-ii-3. The User field may be located after the EHT-SIGA or after the U-SIG when there is no EHT-SIGA.

F-ii-4. The puncturing information may include puncturing information for the entire BW.

F-ii-5. The User field/EHT-SIG may be configured in units of 20 MHz/40 MHz. The User field/EHT-SIG may be transmitted by duplication during wide bandwidth transmission.

F-ii-5-A. User field/EHT-SIG may have different configuration granularity according to transmission BW. For example, user field/EHT-SIG may be configured in units of 20 MHz up to 160 MHz, and user field/EHT-SIG may be configured and transmitted in units of 40 MHz for BW above 240 MHz.

F-ii-5-B. When the user field/EHT-SIG is transmitted using different granularities, the granularity may be indicated through the U-SIG. In this case, 1 bit may be used to indicate the granularity.

F-ii-6. When indicating/transmitting information on M-RU aggregation/preamble puncturing using the above-described embodiment, the BW field of the U-SIG is 20,40,80,160/80+80,240/160+80,160+160/320 MHz It may be composed of 3 bits to represent

F-ii-7. Unlike the above example, the bit table including BW and RU allocation information may be transmitted through the U-SIG of the EHT-PPDU.

F-ii-7-A. For example, U-SIG information may be set differently for every 80 MHz.

F-iii. Unlike the above-described example, the RU allocation information/puncturing information may be transmitted while being included in the EHT-SIGA during SU transmission. The EHT-SIGA may be configured with a common control field and an RU allocation bit/puncturing bit during SU transmission. In EHT-SIGA, the information is jointly encoded and may include one CRC and a tail bit.

F-iii-1. EHT-SIGA can be applied with the same modulation and code rate as 11ax HE-SIGA.

제4 실시 예4th embodiment

According to the fourth embodiment, the EHT STA may indicate/transmit RU allocation/preamble puncturing information using BW and empty allocation information.

A. Similar to the 11ax standard, the EHT STA may indicate non-continuous BW/preamble puncture BW by using the BW field. Detailed allocation information may be indicated using the RU allocation table.

A-i. Allocation for indicating information on M-RU aggregation/preamble puncturing may consist of 8 bits as in the 802.11ax standard, or 3/4/5 bits in consideration of only the allocated combination. Allocation for indicating information on M-RU aggregation/preamble puncturing may be configured differently according to a value of the BW field.

A-ii. For example, in order to indicate the non-continuous BW/preamble puncture BW, the BW field may be configured as follows. Hereinafter, an example of the BW field in SU transmission to support Multi-RU allocation may be described.

A-ii-1. For example, the EHT STA may indicate non-continuous BW/preamble puncture BW based on 20 MHz. The BW field may be configured as shown in Table 33.

A-ii-2. Unlike the above example, considering that 40MHz/80MHz is punctured, the BW field on SU-transmission to support multi-RU allocation may be configured as shown in Tables 34 and 35.

A-ii-3. Unlike the A-ii-2 example described above, the BW may be configured as shown in Table 36 including the puncturing case of the secondary channel and the indication of the primary channel (eg, 40 MHz/80 MHz).

A-ii-4. As in the above example, in order to support a limited RU combination during SU transmission, the BW may be configured with 4 bits. In addition, the above-described examples are only examples, and in order to support more combinations, the BW field may be extended to 5 bits. Accordingly, the EHT STA may perform an indication of various combinations of RUs through the BW field.

A-iii. When the BW for multiple RUs is indicated using the BW field as in the above-described example, the RU allocation information may be configured as follows in order to inform detailed allocation information for the allocated RUs.

A-iii-1. The EHT STA may transmit RU allocation information using the RU allocation 8-bit table defined in the 11ax standard.

A-iii-2. The EHT STA may indicate/transmit information on non-allocated RUs/allocated RUs using an allocation table.

A-iii-2-A. For example, unlike RU allocation for MU transmission, allocation information for SU transmission may be configured and used during SU transmission.

A-iii-2-B. The EHT STA may indicate/transmit information on non-Allocated RUs/allocated RUs using the above-described allocation method.

A-iii-2-B-i. For example, information on RUs/allocated RUs that are not allocated on the basis of 20 MHz per 80 MHz may be indicated. That is, information on non-allocated RUs/allocated RUs may be indicated through the second embodiment.

A-iii-2-B-ii. As another example, information on non-allocated RUs/allocated RUs may be indicated using a table that considers RU combinations per 80 MHz. That is, information on non-allocated RUs/allocated RUs may be indicated through the third embodiment.

A-iii-2-B-iii. Information on non-allocated RUs/allocated RUs may be indicated using an allocation bit map composed of only allocation combinations supported by BW among the combinations listed in the first embodiment. For example, the allocation bit map may consist of 3/4/5 bits.

A-iii-2-B-iii-1. For example, the allocation field according to the above-described BW configuration may be configured as follows.

A-iii-2-B-iii-1-A. Hereinafter, punctured or unassigned 20 MHz may be indicated as 0 in the allocation information. In addition, the allocated 20 MHz may be indicated by 1.

A-iii-2-B-iii-1-B. When the BW field of 1 is used, the allocation information may consist of 5 bits. An example of this may be configured as shown in Table 37.

A-iii-2-B-iii-1-C. When the BW field of 2 is used, Allocation information may be configured as shown in Table 38.

A-iii-2-B-iii-1-D. When the BW field of 3 is used, Allocation information may be configured as shown in Table 39.

B. As described above, in order to perform SU transmission using various BW and RU combinations, RU allocation/puncturing information may be configured and transmitted as follows.

B-i. The SU-PPDU (or MU PPDU) may include a user field/EHT-SIG. In this case, allocation information for the RU combination may be included in the user field/EHT-SIG.

B-i-1. The user field/EHT-SIG may be configured to include RU allocation information like the common field of 11ax HE-SIGB. The user field/EHT-SIG may include a CRC and a tail bit.

B-i-2. The user field/EHT-SIG may include user specific information. In addition, when SU transmission, the user field/EHT-SIG may be configured to include one STA-ID.

B-i-3. The User field may be located after the EHT-SIGA or after the U-SIG when there is no EHT-SIGA.

B-i-4. The User field/EHT-SIG may be configured in units of 20 MHz/40 MHz. The User field/EHT-SIG may be transmitted by duplication during wide bandwidth transmission.

B-i-4-A. User field/EHT-SIG may have different configuration granularity according to transmission BW. For example, user field/EHT-SIG may be configured in units of 20 MHz up to 160 MHz, and user field/EHT-SIG may be configured and transmitted in units of 40 MHz for BW above 240 MHz.

B-i-5. When the user field/EHT-SIG is transmitted using different granularities, the granularity may be indicated through the U-SIG. In this case, 1 bit may be used to indicate the granularity.

B-ii. According to an embodiment, unlike the above-described example, the RU allocation information may be transmitted while being included in the EHT-SIGA during SU transmission. The EHT-SIGA may be configured with a common control field and an RU allocation bit during SU transmission. In EHT-SIGA, the information is jointly encoded and may include one CRC and a tail bit.

C. For EHT-SIGA, the same modulation and code rate as 11ax HE-SIGA can be applied.

제5 실시 예5th embodiment

According to the fifth embodiment, among the various RU combinations proposed in the present specification, some combinations may be allocated during SU transmission as follows. In this case, bits reserved in the RU allocation table of HE-SIGB may be used to indicate the allocation.

A. M-RU combination within each BW

A-i. In the above-described embodiment, the primary 20 is configured as the first 20 MHz. According to an embodiment, allocation may be configured differently according to the location of P20. Allocation according to the embodiment may be configured as shown in Table 40.

Referring to Table 40, 0 in the allocation may mean 242/484/996 RUs that are not allocated. In the allocation, index 15 and index 21 having the same meaning as continuous 160 MHz/continuous 240 MHz may be excluded.

B. A reserved bit of the RU-allocation table may be used for the indication of the M-RU of A. For example, bits for index 224-255 (111x4x3x2x1x0) may be used.

B-i. The RU allocation bit may be transmitted through U-SIG/EHT-SIG.

C. Considering puncturing and continuous BW for the RU combination, the BW field may consist of 6 bits. The BW field and information included in the BW field may be configured as shown in Tables 41 and 42.

Referring to Tables 41 and 42, the BW field may be configured with 5 bits using only some of the above configurations. The BW field may be transmitted through U-SIG.

Since the multiple RU combination proposed in this specification is based on a 20 MHz RU size (ie, 242 RU), the EHT STA may also indicate a preamble puncturing pattern using the allocation information. Therefore, based on the M-RU indication method and the signaling method proposed in this specification, the EHT STA may perform the preamble puncturing indication.

제6 실시 예6th embodiment

According to the sixth embodiment, information on MRU aggregation or preamble puncturing during EHT SU PPDU (or EHT MU PPDU) or non-OFDMA transmission (except the Full bandwidth MU-MIMO) may be indicated as follows.

1. An example of RU allocation or puncturing pattern according to BW may be configured as shown in Table 43.

Referring to Table 43, in consideration of MRU aggregation/puncturing per BW, the maximum number of cases per BW may be 12. Therefore, the MRU aggregation/puncturing indication for each BW may be configured with 4 bits.

Hereinafter, the location of the RU defined/configured according to the BW may be described. A location of an RU configured based on 4-bit information at 80 MHz may be configured as shown in Table 44.

A location of an RU configured based on 4-bit information at 160 MHz may be configured as shown in Table 45.

The location of the RU configured based on 4 bit information at 240 MHz may be configured as shown in Table 46.

The location of the RU configured based on 4 bit information at 320 MHz may be configured as shown in Table 47.

44 to 47 , bit information of a subfield (4 bits) indicating MRU aggregation/puncturing may be set differently according to BW. The subfield indicating the MRU aggregation/puncturing may be included in the U-SIG or the EHT-SIG.

2. Unlike the above example, a subfield may be configured including information on all MRU aggregation/puncturing. In this case, the subfield may include all indications for each BW in the above (ie, 37 cases) and may be composed of 6 bits.

6-bit information for the MRU aggregation/puncturing information may be configured as shown in Table 48.

In the above example, an indication for MRU aggregation/puncturing pattern was configured in consideration of 240 MHz BW. According to an embodiment, unlike the above example, 240 MHz BW may be configured as puncturing for 320 MHz BW. Specifically, the indication may be configured in consideration of the MRU aggregation/puncturing pattern configured for the 240 MHz as the MRU aggregation/puncturing pattern for 320 MHz.

For example, when puncturing for 240 MHz and 3200 MHz BW is configured, the MRU aggregation/puncturing pattern for 320 MHz may be configured with 42 cases as follows. Therefore, the MRU aggregation/puncturing pattern may be composed of 6 bits as follows to support 320 MHz. The location of the RU configured based on 6-bit information at 320 MHz may be configured as shown in Table 49.

Referring to Table 49, as in the example of 1 above, the 6-bit MRU aggregation/puncturing pattern may be transmitted including different information according to the BW.

According to an embodiment, as in the example of 2 above, the EHT STA may indicate for the MRU aggregation/puncturing pattern by configuring one MRU aggregation/puncturing pattern indication including all cases. When 240MHz is configured as a puncturing case for 320MHz, the number of all cases is 46. Therefore, the MRU aggregation/puncturing pattern indication may be configured with 6 bits. The 6-bit MRU aggregation/puncturing pattern indication may be configured as shown in Tables 50 and 51.

According to an embodiment, unlike the above-described example, when 240 MHz is configured/formed by 320 MHz puncturing, two or more holes may be generated in BW. Therefore, in order to prevent 2 hole cases, the MRU aggregation/puncturing pattern for 240 MHz may not be considered. In this case, the MRU aggregation/puncturing pattern indication may be configured with 5 bits except for the indication for 240 mhz in the example of 2 above. The MRU aggregation/puncturing pattern indication composed of the 5-bit may be configured as shown in Table 52.

As described in Example 3 above, the information on the MRU aggregation/puncturing pattern during SU/non-OFDMA transmission may be transmitted through the U-SIG and the EHT-SIG as follows.

A. The EHT STA may transmit a puncturing pattern for 80 MHz in units of 80 MHz through the U-SIG. In order to indicate the puncturing information for the BW greater than 80 MHz, the EHT STA may indicate puncturing information for all or other 80 MHz through the EHT-SIG.

A-1. The puncturing information for 80 MHz included in the U-SIG may be included in version independent information of the U-SIG. For example, the 80MHz puncturing indication bit may consist of 2/3 bits.

A-2. The indication information for the MRU aggregation/puncturing may be transmitted through the EHT-SIG.

A-2-i. Since puncturing information for 80 MHz is transmitted through the U-SIG, MRU aggregation/puncturing information included in the EHT-SIG may be configured without including MRU aggregation/puncturing for 80 MHz.

A-2-ii. In the case of 80 MHz, since puncturing information for 80 MHz is transmitted through the U-SIG, the 80 MHz SU-PPDU (or MU PPDU) may not include the MRU aggregation/puncturing indication field in the EHT-SIG. That is, in the case of 80 MHz, the subfield for MRU aggregation/puncturing indication may not be transmitted in the EHT-SIG.

A-2-iii. In the case of 80 MHz, a subfield of the EHT-SIG indicating MRU aggregation/puncturing may be set to a specific value (or a specific bit index). For example, the subfield of EHT-SIG may be set to 11m11. That is, all bits of the subfield of the EHT-SIG may be set to 1.

B. Unlike the above example, the EHT STA may indicate the entire MRU aggregation/puncturing pattern through the U-SIG.

24 is a flowchart for explaining an operation of a transmitting STA.

Referring to FIG. 24 , in step S2410, the transmitting STA may generate a PPDU. According to an embodiment, the transmitting STA may generate a PPDU including the first signal field and the second signal field. For example, the first signal field may include a U-SIG. For example, the second signal field may include EHT-SIG.

For example, the first signal field and the second signal field may be encoded, respectively. As an example, in the first signal field, two symbols may be jointly encoded. In addition, the first signal field and the second signal field may be modulated, respectively.

According to an embodiment, the PPDU may further include an L-SIG field and a RL-SIG field. For example, the RL-SIG field may be consecutive to the L-SIG field. For example, the first signal field may be consecutive to the RL-SIG field. For example, the second signal field may be continuous to the first signal field.

For example, the transmitting STA may set the value of the length field of the L-SIG field based on the transmission time of the PPDU. As an example, the result of "modulo 3 operation" on the value of the length field of the L-SIG field may be set to 0.

For example, the RL-SIG field may be configured such that the L-SIG field is repeated. As an example, the RL-SIG field includes the same information field as the L-SIG field and may be modulated in the same manner. The L-SIG field and the RL-SIG field may be modulated through BPSK, respectively.

According to an embodiment, the first signal field may include information about a version of the PPDU. Information on the version (version) of the PPDU may be determined based on whether the PPDU is an EHT PPDU.

For example, the information about the version (version) of the PPDU may be composed of 3-bit information. The information on the version of the PPDU may include information indicating that the PPDU is a PPDU (ie, an EHT PPDU) based on the EHT standard. In addition, the information about the version of the PPDU may include information for distinguishing the PPDU according to the 802.11be standard (ie, the EHT standard) or later. In other words, the information on the version of the PPDU may include information for classifying the EHT standard and the PPDU according to the standard determined/generated/established after the EHT standard. That is, the information about the version of the PPDU may include information indicating that the PPDU is an EHT standard or a PPDU after the EHT standard.

According to an embodiment, the type of the PPDU and the version of the PPDU may be used separately. The type of PPDU may be used to distinguish the PPDU according to the EHT standard and the standard before the EHT standard (eg, 802.11n/ac/ax). On the other hand, the version of the PPDU may be used to distinguish the PPDU according to the EHT standard and the standard after the EHT standard. For example, the version of the PPDU may be called variously. For example, the version of the PPDU may be referred to as a PHY version, a Packet version, a Packet identifier, and a Wi-Fi version.

According to an embodiment, the first signal field may further include information on basic service set (BSS) color and information on transmission opportunity (TXOP). For example, the information on the BSS color may be set as various bit information. As an example, the information on the BSS color may be set as 6-bit information. For example, the information about the TXOP may be set to various bit information. As an example, information on TXOP may be set as 7-bit information.

According to an embodiment, the first signal field may include 4-bit information about the preamble puncturing pattern of the 80 MHz bandwidth among the entire bandwidth of the PPDU. Upon receiving the PPDU from the transmitting STA, the receiving STA may identify a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU based on the 4-bit information. The 4-bit information may include first information on whether puncturing is applied in units of 20 MHz among the 80 MHz bandwidth.

The 4-bit information may include first bit information to fourth bit information. The 4-bit information may be configured as [x1 x2 x3 x4]. x1 may mean first bit information. x2 may mean second bit information. x3 may mean third bit information. x4 may mean fourth bit information.

For example, the first bit information of the 4-bit information may include information on whether preamble puncturing is applied to the first 20 MHz bandwidth of the 80 MHz bandwidth. For example, based on whether the first bit information is a first value, it may be determined whether preamble puncturing is applied to the first 20 MHz bandwidth.

In other words, based on the first bit information being a first value (eg, 0), preamble puncturing may be applied to the first 20 MHz bandwidth. Based on the first bit information being the second value (eg, 1), preamble puncturing may not be applied to the first 20 MHz bandwidth.

For example, the second bit information of the 4-bit information may include information on whether preamble puncturing is applied to the second 20 MHz bandwidth of the 80 MHz bandwidth. For example, based on whether the second bit information is the first value, it may be determined whether preamble puncturing is applied to the second 20 MHz bandwidth.

In other words, based on the second bit information being a first value (eg, 0), preamble puncturing may be applied to the second 20 MHz bandwidth. Based on the second bit information being a second value (eg, 1), preamble puncturing may not be applied to the second 20 MHz bandwidth.

For example, the third bit information of the 4-bit information may include information on whether preamble puncturing is applied to the third 20 MHz bandwidth of the 80 MHz bandwidth. For example, based on whether the third bit information is the first value, it may be determined whether preamble puncturing is applied to the third 20 MHz bandwidth.

In other words, based on the third bit information being the first value (eg, 0), preamble puncturing may be applied to the third 20 MHz bandwidth. Based on the third bit information being the second value (eg, 1), preamble puncturing may not be applied to the third 20 MHz bandwidth.

For example, the fourth bit information of the 4 bit information may include information on whether preamble puncturing is applied to the fourth 20 MHz bandwidth among the 80 MHz bandwidth. For example, based on whether the fourth bit information is the first value, it may be determined whether preamble puncturing is applied to the fourth 20 MHz bandwidth.

In other words, based on the fourth bit information being a first value (eg, 0), preamble puncturing may be applied to the fourth 20 MHz bandwidth. Based on the fourth bit information being the second value (eg, 1), preamble puncturing may not be applied to the fourth 20 MHz bandwidth.

According to an embodiment, the second signal field may include second information about the preamble puncturing pattern of the entire bandwidth of the PPDU. For example, the second signal field may include a common field and a user specific field. The second information may be included in the general field.

According to an embodiment, the first signal field may further include a bandwidth field related to the total bandwidth of the PPDU. The first information and/or the second information may not be included in the bandwidth field. In other words, the above-described 4-bit information may be configured as a field independent of the bandwidth field in the first signal field. In addition, the above-described second information may be configured as an independent field within the second signal field.

For example, the second signal field may be configured by being duplicated within the entire bandwidth of the PPDU in units of the first bandwidth. The information about the first bandwidth may be included in the first signal field. Accordingly, the transmitting STA may transmit information about the first bandwidth through the first signal field. In addition, the transmitting STA may configure the PPDU by duplicating the second signal field in the unit of the first bandwidth. For example, the first bandwidth may be set to either 20 MHz or 40 MHz.

In step S2420, the transmitting STA may transmit a PPDU. That is, the transmitting STA may transmit the generated PPDU.

According to an embodiment, each field included in the PPDU may be transmitted through a symbol. For example, the L-SIG field may be transmitted through the first symbol. The RL-SIG field may be transmitted through a second symbol consecutive to the first symbol. The first signal field may be transmitted through a third symbol consecutive to the second symbol. The second signal field may be transmitted through a fourth symbol consecutive to the third symbol.

As an example, the first symbol may consist of one symbol. The second symbol may consist of one symbol. The third symbol may consist of two symbols. Accordingly, the first signal field may be transmitted through two symbols. For example, the fourth symbol may consist of at least one or at least one or more symbols. Accordingly, the second signal field may be transmitted through at least one or more symbols consecutive to two symbols through which the first signal field is transmitted.

25 is a flowchart illustrating an operation of a receiving STA.

Referring to FIG. 25 , in step S2510, a receiving STA may receive a PPDU. According to an embodiment, the transmitting STA may generate a PPDU including the first signal field and the second signal field. For example, the first signal field may include a U-SIG. For example, the second signal field may include EHT-SIG.

According to an embodiment, each field included in the PPDU may be received through a symbol. For example, the L-SIG field may be received through the first symbol. The RL-SIG field may be received through a second symbol consecutive to the first symbol. The first signal field may be received through a third symbol consecutive to the second symbol. The second signal field may be received through a fourth symbol consecutive to the third symbol.

As an example, the first symbol may consist of one symbol. The second symbol may consist of one symbol. The third symbol may consist of two symbols. Accordingly, the first signal field may be received through two symbols. For example, the fourth symbol may consist of at least one or at least one or more symbols. Accordingly, the second signal field may be received through at least one or more consecutive symbols from two symbols in which the first signal field is received.

For example, the value of the length field of the L-SIG field may be set based on the transmission time of the PPDU. As an example, the result of "modulo 3 operation" on the value of the length field of the L-SIG field may be set to 0.

For example, the second signal field may be configured by being duplicated within the entire bandwidth of the PPDU in units of the first bandwidth. The information about the first bandwidth may be included in the first signal field. Accordingly, the receiving STA may obtain/identify information about the first bandwidth through the first signal field. In addition, the receiving STA may identify that the PPDU is duplicated in the first bandwidth unit using the second signal field. For example, the first bandwidth may be set to either 20 MHz or 40 MHz.

In step S2520, the receiving STA may decode the PPDU. According to an embodiment, the receiving STA may decode the PPDU based on the first signal field and the second signal field.

The technical features of the present specification described above may be applied to various devices and methods. For example, the above-described technical features of the present specification may be performed/supported through the apparatus of FIGS. 1 and/or 19 . For example, the technical features of the present specification described above may be applied only to a part of FIGS. 1 and/or 19 . For example, the technical features of the present specification described above are implemented based on the

processing chips

114 and 124 of FIG. 1 , or implemented based on the

processors

111 and 121 and the

memories

112 and 122 of FIG. 1 , or , may be implemented based on the processor 610 and the memory 620 of FIG. 19 . For example, the apparatus of the present specification includes a processor and a memory connected to the processor, wherein the processor transmits a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from a transmitting STA. obtained, wherein the first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU, and the 4-bit information is applied in units of 20 MHz of the 80 MHz bandwidth. first information on whether or not, the second signal field includes second information on a preamble puncturing pattern of the full bandwidth, and based on the first signal field and the second signal field, the It may be configured to decode the PPDU.

The technical features of the present specification may be implemented based on a CRM (computer readable medium). For example, CRM proposed by the present specification obtains a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from a transmitting STA, wherein the first signal field is the entirety of the PPDU. 4 bit information about the preamble puncturing pattern of the 80 MHz bandwidth of the bandwidth, wherein the 4 bit information includes first information on whether puncturing is applied in units of 20 MHz of the 80 MHz bandwidth, the first The 2 signal field includes second information about the preamble puncturing pattern of the entire bandwidth; and decoding the PPDU based on the first signal field and the second signal field. The instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to CRM in the present specification may be the

processors

111 and 121 or the

processing chips

114 and 124 of FIG. 1 , or the processor 610 of FIG. 19 . Meanwhile, the CRM of the present specification may be the

memories

112 and 122 of FIG. 1 , the memory 620 of FIG. 19 , or a separate external memory/storage medium/disk.

The technical features of the present specification described above are applicable to various applications or business models. For example, the above-described technical features may be applied for wireless communication in a device supporting artificial intelligence (AI).

Artificial intelligence refers to a field that studies artificial intelligence or a methodology that can create it, and machine learning refers to a field that defines various problems dealt with in the field of artificial intelligence and studies methodologies to solve them. do. Machine learning is also defined as an algorithm that improves the performance of a certain task through constant experience.

An artificial neural network (ANN) is a model used in machine learning, and may refer to an overall model having problem-solving ability, which is composed of artificial neurons (nodes) that form a network by combining synapses. An artificial neural network may be defined by a connection pattern between neurons of different layers, a learning process that updates model parameters, and an activation function that generates an output value.

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

Model parameters refer to parameters determined through learning, and include the weight of synaptic connections and the bias of neurons. In addition, the hyperparameter refers to a parameter to be set before learning in a machine learning algorithm, and includes a learning rate, the number of iterations, a mini-batch size, an initialization function, and the like.

The purpose of learning the artificial neural network can be seen as determining the model parameters that minimize the loss function. The loss function may be used as an index for determining optimal model parameters in the learning process of the artificial neural network.

Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning according to a learning method.

Supervised learning refers to a method of training an artificial neural network in a state where a label for the training data is given, and the label is the correct answer (or result value) that the artificial neural network should infer when the training data is input to the artificial neural network. can mean Unsupervised learning may refer to a method of training an artificial neural network in a state where no labels are given for training data. Reinforcement learning can refer to a learning method in which an agent defined in an environment learns to select an action or sequence of actions that maximizes the cumulative reward in each state.

Among artificial neural networks, machine learning implemented as a deep neural network (DNN) including a plurality of hidden layers is also called deep learning, and deep learning is a part of machine learning. Hereinafter, machine learning is used in a sense including deep learning.

In addition, the above-described technical features can be applied to the wireless communication of the robot.

A robot can mean a machine that automatically handles or operates a task given by its own capabilities. In particular, a robot having a function of recognizing an environment and performing an operation by self-judgment may be referred to as an intelligent robot.

Robots can be classified into industrial, medical, home, military, etc. depending on the purpose or field of use. The robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving the robot joints. In addition, the movable robot includes a wheel, a brake, a propeller, and the like in the driving unit, and can travel on the ground or fly in the air through the driving unit.

In addition, the above-described technical features may be applied to a device supporting extended reality.

The extended reality is a generic term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology provides only CG images of objects or backgrounds in the real world, AR technology provides virtual CG images on top of images of real objects, and MR technology is a computer that mixes and combines virtual objects in the real world. graphic technology.

MR technology is similar to AR technology in that it shows both real and virtual objects. However, there is a difference in that in AR technology, a virtual object is used in a form that complements a real object, whereas in MR technology, a virtual object and a real object are used with equal characteristics.

XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phone, tablet PC, laptop, desktop, TV, digital signage, etc. can be called

The claims described herein may be combined in various ways. For example, the technical features of the method claims of the present specification may be combined and implemented as an apparatus, and the technical features of the apparatus claims of the present specification may be combined and implemented as a method. In addition, the technical features of the method claim of the present specification and the technical features of the apparatus claim may be combined to be implemented as an apparatus, and the technical features of the method claim of the present specification and the technical features of the apparatus claim may be combined and implemented as a method.

Claims

A method performed in a receiving STA (station) of a wireless local area network (WLAN) system, the method comprising:

Receiving a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from the transmitting STA,

The first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU,

The 4-bit information includes first information on whether puncturing is applied in units of 20 MHz among the 80 MHz bandwidth,

The second signal field includes second information on a preamble puncturing pattern of the entire bandwidth; and

Decoding the PPDU based on the first signal field and the second signal field

Way.
According to claim 1,

The first bit information of the 4-bit information includes information on whether preamble puncturing is applied to the first 20 MHz bandwidth of the 80 MHz bandwidth,

The second bit information of the 4-bit information includes information on whether preamble puncturing is applied to the second 20 MHz bandwidth of the 80 MHz bandwidth,

The third bit information of the 4-bit information includes information on whether preamble puncturing is applied to the third 20 MHz bandwidth of the 80 MHz bandwidth,

The fourth bit information of the 4 bit information includes information on whether preamble puncturing is applied to the fourth 20 MHz bandwidth of the 80 MHz bandwidth

Way.
3. The method of claim 2,

Based on whether the first bit information is a first value, it is determined whether preamble puncturing is applied to the first 20 MHz bandwidth,

Based on whether the second bit information is the first value, it is determined whether preamble puncturing is applied to the second 20 MHz bandwidth,

Whether to apply preamble puncturing to the third 20 MHz bandwidth is determined based on whether the third bit information is the first value,

Whether to apply preamble puncturing to the fourth 20 MHz bandwidth is determined based on whether the fourth bit information is the first value

Way.
According to claim 1,

The second signal field includes a common field and a user specific field.

Way.
5. The method of claim 4,

The second information is included in the general field.

Way.
According to claim 1,

The first signal field is transmitted through 2 symbols

Way.
According to claim 1,

The second signal field is configured by being duplicated within the entire bandwidth in units of a first bandwidth.

Way.
8. The method of claim 7,

The information about the first bandwidth is included in the first signal field.

Way.
According to claim 1,

The first signal field includes a U-SIG and

The second signal field includes EHT-SIG

Way.
According to claim 1,

The first signal field further includes a bandwidth field related to the total bandwidth of the PPDU,

The first information or the second information is not included in the bandwidth field

Way.
A method performed in a transmitting STA (station) of a wireless local area network (WLAN) system, the method comprising:

Generating a physical layer protocol data unit (PPDU) including a first signal field and a second signal field,

The first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU,

The 4-bit information includes first information on whether puncturing is applied in units of 20 MHz among the 80 MHz bandwidth,

The second signal field includes second information on a preamble puncturing pattern of the entire bandwidth; and

Transmitting the PPDU

Way.
In a receiving STA (station) used in a wireless local area network (WLAN) system,

a transceiver for transmitting and receiving radio signals; and

A processor coupled to the transceiver, the processor comprising:

Receiving a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from the transmitting STA,

The first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU,

The 4-bit information includes first information on whether puncturing is applied in units of 20 MHz among the 80 MHz bandwidth,

The second signal field includes second information about the preamble puncturing pattern of the entire bandwidth,

configured to decode the PPDU based on the first signal field and the second signal field

Receiving STA.
13. The method of claim 12,

The first bit information of the 4-bit information includes information on whether preamble puncturing is applied to the first 20 MHz bandwidth of the 80 MHz bandwidth,

The second bit information of the 4-bit information includes information on whether preamble puncturing is applied to the second 20 MHz bandwidth of the 80 MHz bandwidth,

The third bit information of the 4-bit information includes information on whether preamble puncturing is applied to the third 20 MHz bandwidth of the 80 MHz bandwidth,

The fourth bit information of the 4 bit information includes information on whether preamble puncturing is applied to the fourth 20 MHz bandwidth of the 80 MHz bandwidth

Receiving STA.
14. The method of claim 13,

Based on whether the first bit information is a first value, it is determined whether preamble puncturing is applied to the first 20 MHz bandwidth,

Based on whether the second bit information is the first value, it is determined whether preamble puncturing is applied to the second 20 MHz bandwidth,

Whether to apply preamble puncturing to the third 20 MHz bandwidth is determined based on whether the third bit information is the first value,

Whether to apply preamble puncturing to the fourth 20 MHz bandwidth is determined based on whether the fourth bit information is the first value

Receiving STA.
13. The method of claim 12,

The second signal field includes a common field and a user specific field.

Receiving STA.
16. The method of claim 15,

The second information is included in the general field.

Receiving STA.
13. The method of claim 12,

The first signal field further includes a bandwidth field related to the total bandwidth of the PPDU,

The first information or the second information is not included in the bandwidth field

Receiving STA.
In a transmitting STA (station) used in a wireless local area network (WLAN) system,

a transceiver for transmitting and receiving radio signals; and

A processor coupled to the transceiver, the processor comprising:

Generating a physical layer protocol data unit (PPDU) including a first signal field and a second signal field,

The first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU,

The 4-bit information includes first information on whether puncturing is applied in units of 20 MHz among the 80 MHz bandwidth,

The second signal field includes second information about the preamble puncturing pattern of the entire bandwidth,

configured to transmit the PPDU

Transmitting STA.
In at least one computer-readable recording medium comprising an instruction based on being executed by at least one processor,

Obtaining a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from the transmitting STA,

The first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU,

The 4-bit information includes first information on whether puncturing is applied in units of 20 MHz of the 80 MHz bandwidth

The second signal field includes second information on a preamble puncturing pattern of the entire bandwidth; and

decoding the PPDU based on the first signal field and the second signal field;

performing an operation that includes

Device.
A device used in a wireless LAN system, comprising:

processor, and

a memory coupled to the processor;

The processor is

Obtaining a physical layer protocol data unit (PPDU) including a first signal field and a second signal field from the transmitting STA,

The first signal field includes 4-bit information about a preamble puncturing pattern of an 80 MHz bandwidth among the entire bandwidth of the PPDU,

The 4-bit information includes first information on whether puncturing is applied in units of 20 MHz of the 80 MHz bandwidth

The second signal field includes second information about the preamble puncturing pattern of the entire bandwidth,

configured to decode the PPDU based on the first signal field and the second signal field

Device.