METHOD AND DEVICE FOR RECEIVING PPDU ON BASIS OF CONTROL INFORMATION RELATED TO CHANNELIZATION OF 6GHZ BAND IN WIRELESS LAN SYSTEM

Proposed are a method and a device that receive a PPDU on the basis of control information related to channelization of a 6 GHz band in a WLAN system. Specifically, a receiving STA receives the PPDU from a transmitting STA. The receiving STA decodes the PPDU to obtain the control information related to the channelization of the 6 GHz band. The receiving STA decodes a data field of the PPDU on the basis of the control information. The 6 GHz band includes first to seventh 160 MHz channels, first to third 320-1 MHz channels, first to third 320-2 MHz channels, first and second 480-1 MHz channels, or first and second 480-2 MHz channels.

TECHNICAL FIELD

The present specification relates to a technique for receiving PPDU based on control information related to channelization of the 6 GHz band in a wireless LAN system, and more particularly, to a method and apparatus for indicating a definition and a bandwidth of a 480 MHz channel and a 640 MHz channel.

BACKGROUND

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

The present specification proposes a technical feature that can be utilized in a new communication standard. For example, the new communication standard may be an extreme high throughput (EHT) standard which is currently being discussed. The EHT standard may use an increased bandwidth, an enhanced PHY layer protocol data unit (PPDU) structure, an enhanced sequence, a hybrid automatic repeat request (HARQ) scheme, or the like, which is newly proposed. The EHT standard may be called the IEEE 802.11be standard.

In a new WLAN standard, an increased number of spatial streams may be used. In this case, in order to properly use the increased number of spatial streams, a signaling technique in the WLAN system may need to be improved.

SUMMARY

The present specification proposes a method and apparatus for receiving PPDU based on control information related to channelization of a 6 GHz band in a wireless LAN system.

An example of the present specification proposes a method for receiving PPDU based on control information related to channelization of a 6 GHz band.

The present embodiment may be performed in a network environment in which a next generation WLAN system (IEEE 802.11be or EHT WLAN system) is supported. The next generation wireless LAN system is a WLAN system that is enhanced from an 802.11ax system and may, therefore, satisfy backward compatibility with the 802.11ax system.

This embodiment proposes a method of configuring channelization and a method of indicating a bandwidth when supporting a 480 MHz channel and a 640 MHz channel in a 6 GHz band.

A receiving station (STA) receives a Physical Protocol Data Unit (PPDU) from a transmitting STA.

The receiving STA decodes the PPDU and obtains control information related to channelization in a 6 GHz band.

The receiving STA decodes a data field of the PPDU based on the control information.

The channelization configuration of the 6 GHz band is as follows.

The 6 GHz band includes first to seventh 160 MHz channels, first to third 320-1 MHz channels, first to third 320-2 MHz channels, first and second 480-1 MHz channels, or first and second 480-2 MHz channels.

The first to seventh 160 MHz channels are arranged in order from lowest frequency to highest frequency.

The first 320-1 MHz channel includes the first and second 160 MHz channels, the second 320-1 MHz channel includes the third and fourth 160 MHz channels, and the third 320-1 MHz channel includes the fifth and sixth 160 MHz channels.

The first 320-2 MHz channel includes the second and third 160 MHz channels, the second 320-2 MHz channel includes the fourth and fifth 160 MHz channels, and the third 320-2 MHz channel includes the sixth and seventh 160 MHz channels.

The first 480-1 MHz channel includes the first 320-1 MHz channel and the third 160 MHz channel, or includes the first 160 MHz channel and the first 320-2 MHz channel. The second 480-1 MHz channel includes the third 320-1 MHz channel and the fourth 160 MHz channel, or includes the second 320-2 MHz channel and the sixth 160 MHz channel.

The first 480-2 MHz channel includes the first 320-2 MHz channel and the fourth 160 MHz channel, or includes the second 160 MHz channel and the second 320-1 MHz channel. The second 480-2 MHz channel includes the third 320-1 MHz channel and the seventh 160 MHz channel, or includes the fifth 160 MHz channel and the third 320-2 MHz channel.

According to the embodiment proposed in this specification, by defining a bandwidth exceeding 320 MHz within the 6 GHz band, it is possible to improve performance such as overall throughput and latency during single link transmission.

DETAILED DESCRIPTION

In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (EHT-signal)”, it may denote that “EHT-signal” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “EHT-signal”, and “EHT-signal” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., EHT-signal)”, it may also mean that “EHT-signal” is proposed as an example of the “control information”.

Technical features described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.

The following example 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, the present specification may also be applied to the newly proposed EHT standard or IEEE 802.11be standard. In addition, the example of the present specification may also be applied to a new WLAN standard enhanced from the EHT standard or the IEEE 802.11be standard. In addition, the 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) depending on a 3rdgeneration partnership project (3GPP) standard and based on evolution of the LTE. In addition, the example of the present specification may be applied to a communication system of a 5G NR standard based on the 3GPP standard.

Hereinafter, in order to describe a technical feature of the present specification, a technical feature applicable to the present specification will be described.

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

In the example ofFIG.1, various technical features described below may be performed.FIG.1relates to at least one station (STA). For example, STAs110and120of the present specification may also be called in various terms such as a mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, or simply a user. The STAs110and120of the present specification may also be called in various terms such as a network, a base station, a node-B, an access point (AP), a repeater, a router, a relay, or the like. The STAs110and120of the present specification may also be referred to as various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, or the like.

For example, the STAs110and120may serve as an AP or a non-AP. That is, the STAs110and120of the present specification may serve as the AP and/or the non-AP.

The STAs110and120of the present specification may support various communication standards together in addition to the IEEE 802.11 standard. For example, a communication standard (e.g., LTE, LTE-A, 5G NR standard) or the like based on the 3GPP standard may be supported. In addition, the STA of the present specification may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, or the like. In addition, the STA of the present specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving (autonomous-driving), or the like.

The STAs110and120of the present specification may include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a radio medium.

The STAs110and120will be described below with reference to a sub-figure (a) ofFIG.1.

The first STA110may include a processor111, a memory112, and a transceiver113. The illustrated process, memory, and transceiver may be implemented individually as separate chips, or at least two blocks/functions may be implemented through a single chip.

The transceiver113of the first STA performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received.

For example, the first STA110may perform an operation intended by an AP. For example, the processor111of the AP may receive a signal through the transceiver113, process a reception (RX) signal, generate a transmission (TX) signal, and provide control for signal transmission. The memory112of the AP may store a signal (e.g., RX signal) received through the transceiver113, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.

For example, the second STA120may perform an operation intended by a non-AP STA. For example, a transceiver123of a non-AP performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be packet, etc.) may be transmitted/received.

For example, a processor121of the non-AP STA may receive a signal through the transceiver123, process an RX signal, generate a TX signal, and provide control for signal transmission. A memory122of the non-AP STA may store a signal (e.g., RX signal) received through the transceiver123, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.

For example, an operation of a device indicated as an AP in the specification described below may be performed in the first STA110or the second STA120. For example, if the first STA110is the AP, the operation of the device indicated as the AP may be controlled by the processor111of the first STA110, and a related signal may be transmitted or received through the transceiver113controlled by the processor111of the first STA110. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory112of the first STA110. In addition, if the second STA120is the AP, the operation of the device indicated as the AP may be controlled by the processor121of the second STA120, and a related signal may be transmitted or received through the transceiver123controlled by the processor121of the second STA120. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory122of the second STA120.

For example, in the specification described below, an operation of a device indicated as a non-AP (or user-STA) may be performed in the first STA110or the second STA120. For example, if the second STA120is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor121of the second STA120, and a related signal may be transmitted or received through the transceiver123controlled by the processor121of the second STA120. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory122of the second STA120. For example, if the first STA110is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor111of the first STA110, and a related signal may be transmitted or received through the transceiver113controlled by the processor111of the first STA110. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory112of the first STA110.

In the specification described below, a device called a (transmitting/receiving) STA, a first STA, a second STA, a STA1, a STA2, an AP, a first AP, a second AP, an AP1, an AP2, a (transmitting/receiving) terminal, a (transmitting/receiving) device, a (transmitting/receiving) apparatus, a network, or the like may imply the STAs110and120ofFIG.1. For example, a device indicated as, without a specific reference numeral, the (transmitting/receiving) STA, the first STA, the second STA, the STA1, the STA2, the AP, the first AP, the second AP, the AP1, the AP2, the (transmitting/receiving) terminal, the (transmitting/receiving) device, the (transmitting/receiving) apparatus, the network, or the like may imply the STAs110and120ofFIG.1. For example, in the following example, an operation in which various STAs transmit/receive a signal (e.g., a PPDU) may be performed in the transceivers113and123ofFIG.1. In addition, in the following example, an operation in which various STAs generate a TX/RX signal or perform data processing and computation in advance for the TX/RX signal may be performed in the processors111and121ofFIG.1. For example, an example of an operation for generating the TX/RX signal or performing the data processing and computation in advance may include: 1) an operation of determining/obtaining/configuring/computing/decoding/encoding bit information of a sub-field (SIG, STF, LTF, Data) included in a PPDU; 2) an operation of determining/configuring/obtaining a time resource or frequency resource (e.g., a subcarrier resource) or the like used for the sub-field (SIG, STF, LTF, Data) included the PPDU; 3) an operation of determining/configuring/obtaining a specific sequence (e.g., a pilot sequence, an STF/LTF sequence, an extra sequence applied to SIG) or the like used for the sub-field (SIG, STF, LTF, Data) field included in the PPDU; 4) a power control operation and/or power saving operation applied for the STA; and 5) an operation related to determining/obtaining/configuring/decoding/encoding or the like of an ACK signal. In addition, in the following example, a variety of information used by various STAs for determining/obtaining/configuring/computing/decoding/decoding a TX/RX signal (e.g., information related to a field/subfield/control field/parameter/power or the like) may be stored in the memories112and122ofFIG.1.

The aforementioned device/STA of the sub-figure (a) ofFIG.1may be modified as shown in the sub-figure (b) ofFIG.1. Hereinafter, the STAs110and120of the present specification will be described based on the sub-figure (b) ofFIG.1.

For example, the transceivers113and123illustrated in the sub-figure (b) ofFIG.1may perform the same function as the aforementioned transceiver illustrated in the sub-figure (a) ofFIG.1. For example, processing chips114and124illustrated in the sub-figure (b) ofFIG.1may include the processors111and121and the memories112and122. The processors111and121and memories112and122illustrated in the sub-figure (b) ofFIG.1may perform the same function as the aforementioned processors111and121and memories112and122illustrated in the sub-figure (a) ofFIG.1.

A mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, a user, a user STA, a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, a receiving unit, a transmitting unit, a receiving STA, a transmitting STA, a receiving device, a transmitting device, a receiving apparatus, and/or a transmitting apparatus, which are described below, may imply the STAs110and120illustrated in the sub-figure (a)/(b) ofFIG.1, or may imply the processing chips114and124illustrated in the sub-figure (b) ofFIG.1. That is, a technical feature of the present specification may be performed in the STAs110and120illustrated in the sub-figure (a)/(b) ofFIG.1, or may be performed only in the processing chips114and124illustrated in the sub-figure (b) ofFIG.1. For example, a technical feature in which the transmitting STA transmits a control signal may be understood as a technical feature in which a control signal generated in the processors111and121illustrated in the sub-figure (a)/(b) ofFIG.1is transmitted through the transceivers113and123illustrated in the sub-figure (a)/(b) ofFIG.1. Alternatively, the technical feature in which the transmitting STA transmits the control signal may be understood as a technical feature in which the control signal to be transferred to the transceivers113and123is generated in the processing chips114and124illustrated in the sub-figure (b) ofFIG.1.

For example, a technical feature in which the receiving STA receives the control signal may be understood as a technical feature in which the control signal is received by means of the transceivers113and123illustrated in the sub-figure (a) ofFIG.1. Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers113and123illustrated in the sub-figure (a) ofFIG.1is obtained by the processors111and121illustrated in the sub-figure (a) ofFIG.1. Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers113and123illustrated in the sub-figure (b) ofFIG.1is obtained by the processing chips114and124illustrated in the sub-figure (b) ofFIG.1.

Referring to the sub-figure (b) ofFIG.1, software codes115and125may be included in the memories112and122. The software codes115and126may include instructions for controlling an operation of the processors111and121. The software codes115and125may be included as various programming languages.

The processors111and121or processing chips114and124ofFIG.1may include an application-specific integrated circuit (ASIC), other chipsets, a logic circuit and/or a data processing device. The processor may be an application processor (AP). For example, the processors111and121or processing chips114and124ofFIG.1may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, the processors111and121or processing chips114and124ofFIG.1may be SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung@, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or processors enhanced from these processors.

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

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

An upper part ofFIG.2illustrates the structure of an infrastructure basic service set (BSS) of institute of electrical and electronic engineers (IEEE) 802.11.

Referring the upper part ofFIG.2, the wireless LAN system may include one or more infrastructure BSSs200and205(hereinafter, referred to as BSS). The BSSs200and205as a set of an AP and a STA such as an access point (AP)225and a station (STA1)200-1which are successfully synchronized to communicate with each other are not concepts indicating a specific region. The BSS205may include one or more STAs205-1and205-2which may be joined to one AP230.

The BSS may include at least one STA, APs providing a distribution service, and a distribution system (DS)210connecting multiple APs.

The distribution system210may implement an extended service set (ESS)240extended by connecting the multiple BSSs200and205. The ESS240may be used as a term indicating one network configured by connecting one or more APs225or230through the distribution system210. The AP included in one ESS240may have the same service set identification (SSID).

A portal220may serve as a bridge which connects the wireless LAN network (IEEE 802.11) and another network (e.g., 802.X).

In the BSS illustrated in the upper part ofFIG.2, a network between the APs225and230and a network between the APs225and230and the STAs200-1,205-1, and205-2may be implemented. However, the network is configured even between the STAs without the APs225and230to perform communication. A network in which the communication is performed by configuring the network even between the STAs without the APs225and230is defined as an Ad-Hoc network or an independent basic service set (IBSS).

A lower part ofFIG.2illustrates a conceptual view illustrating the IBSS.

Referring to the lower part ofFIG.2, the IBSS is a BSS that operates in an Ad-Hoc mode. Since the IBSS does not include the access point (AP), a centralized management entity that performs a management function at the center does not exist. That is, in the IBSS, STAs250-1,250-2,250-3,255-4, and255-5are managed by a distributed manner. In the IBSS, all STAs250-1,250-2,250-3,255-4, and255-5may be constituted by movable STAs and are not permitted to access the DS to constitute a self-contained network.

FIG.3illustrates a general link setup process.

In S310, a STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, to access a network, the STA needs to discover a participating network. The STA needs to identify a compatible network before participating in a wireless network, and a process of identifying a network present in a particular area is referred to as scanning. Scanning methods include active scanning and passive scanning.

FIG.3illustrates a network discovery operation including an active scanning process. In active scanning, a STA performing scanning transmits a probe request frame and waits for a response to the probe request frame in order to identify which AP is present around while moving to channels. A responder transmits a probe response frame as a response to the probe request frame to the STA having transmitted the probe request frame. Here, the responder may be a STA that transmits the last beacon frame in a BSS of a channel being scanned. In the BSS, since an AP transmits a beacon frame, the AP is the responder. In an IBSS, since STAs in the IBSS transmit a beacon frame in turns, the responder is not fixed. For example, when the STA transmits a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA may store BSS-related information included in the received probe response frame, may move to the next channel (e.g., channel 2), and may perform scanning (e.g., transmits a probe request and receives a probe response via channel 2) by the same method.

Although not shown inFIG.3, scanning may be performed by a passive scanning method. In passive scanning, a STA performing scanning may wait for a beacon frame while moving to channels. A beacon frame is one of management frames in IEEE 802.11 and is periodically transmitted to indicate the presence of a wireless network and to enable the STA performing scanning to find the wireless network and to participate in the wireless network. In a BSS, an AP serves to periodically transmit a beacon frame. In an IBSS, STAs in the IBSS transmit a beacon frame in turns. Upon receiving the beacon frame, the STA performing scanning stores information related to a BSS included in the beacon frame and records beacon frame information in each channel while moving to another channel. The STA having received the beacon frame may store BSS-related information included in the received beacon frame, may move to the next channel, and may perform scanning in the next channel by the same method.

After discovering the network, the STA may perform an authentication process in S320. The authentication process may be referred to as a first authentication process to be clearly distinguished from the following security setup operation in S340. The authentication process in S320may include a process in which the STA transmits an authentication request frame to the AP and the AP transmits an authentication response frame to the STA in response. The authentication frames used for an authentication request/response are management frames.

The authentication frames may include information related to 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.

The STA may transmit the authentication request frame to the AP. The AP may determine whether to allow the authentication of the STA based on the information included in the received authentication request frame. The AP may provide the authentication processing result to the STA via the authentication response frame.

When the STA is successfully authenticated, the STA may perform an association process in S330. The association process includes a process in which the STA transmits an association request frame to the AP and the AP transmits an association response frame to the STA in response. The association request frame may include, for example, information related to various capabilities, a beacon listen interval, a service set identifier (SSID), a supported rate, a supported channel, RSN, a mobility domain, a supported operating class, a traffic indication map (TIM) broadcast request, and an interworking service capability. The association response frame may include, for example, information related to various capabilities, a status code, an association ID (AID), a supported rate, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise indicator (RSNI), a mobility domain, a timeout interval (association comeback time), an overlapping BSS scanning parameter, a TIM broadcast response, and a QoS map.

In S340, the STA may perform a security setup process. The security setup process in S340may include a process of setting up a private key through four-way handshaking, for example, through an extensible authentication protocol over LAN (EAPOL) frame.

FIG.4illustrates an example of a PPDU used in an IEEE standard.

As illustrated, various types of PHY protocol data units (PPDUs) are used in IEEE a/g/n/ac standards. Specifically, an LTF and a STF include a training signal, a SIG-A and a SIG-B include control information for a receiving STA, and a data field includes user data corresponding to a PSDU (MAC PDU/aggregated MAC PDU).

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

As illustrated inFIG.4, the HE-PPDU for multiple users (MUs) may include a legacy-short training field (L-STF), a legacy-long training field (L-LTF), a legacy-signal (L-SIG), a high efficiency-signal A (HE-SIG A), a high efficiency-signal-B (HE-SIG B), a high efficiency-short training field (HE-STF), a high efficiency-long training field (HE-LTF), a data field (alternatively, an MAC payload), and a packet extension (PE) field. The respective fields may be transmitted for illustrated time periods (i.e., 4 or 8 μs).

Hereinafter, a resource unit (RU) used for a PPDU is described. An RU may include a plurality of subcarriers (or tones). An RU may be used to transmit a signal to a plurality of STAs according to OFDMA. Further, an RU may also be defined to transmit a signal to one STA. An RU may be used for an STF, an LTF, a data field, or the like.

FIG.5illustrates a layout of resource units (RUs) used in a band of 20 MHz.

As illustrated inFIG.5, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to form some fields of an HE-PPDU. For example, resources may be allocated in illustrated RUs for an HE-STF, an HE-LTF, and a data field.

As illustrated in the uppermost part ofFIG.5, a 26-unit (i.e., a unit corresponding to 26 tones) may be disposed. Six tones may be used for a guard band in the leftmost band of the 20 MHz band, and five tones may be used for a guard band in the rightmost band of the 20 MHz band. Further, seven DC tones may be inserted in a center band, that is, a DC band, and a 26-unit corresponding to 13 tones on each of the left and right sides of the DC band may be disposed. A 26-unit, a 52-unit, and a 106-unit may be allocated to other bands. Each unit may be allocated for a receiving STA, that is, a user.

The layout of the RUs inFIG.5may be used not only for a multiple users (MUs) but also for a single user (SU), in which case one 242-unit may be used and three DC tones may be inserted as illustrated in the lowermost part ofFIG.5.

AlthoughFIG.5proposes RUs having various sizes, that is, a 26-RU, a 52-RU, a 106-RU, and a 242-RU, specific sizes of RUs may be extended or increased. Therefore, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones).

FIG.6illustrates a layout of RUs used in a band of 40 MHz.

Similarly toFIG.5in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, and the like may be used in an example ofFIG.6. Further, five DC tones may be inserted in a center frequency, 12 tones may be used for a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 40 MHz band.

As illustrated inFIG.6, when the layout of the RUs is used for a single user, a 484-RU may be used. The specific number of RUs may be changed similarly toFIG.5.

FIG.7illustrates a layout of RUs used in a band of 80 MHz.

Similarly toFIG.5andFIG.6in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, a 996-RU, and the like may be used in an example ofFIG.7. Further, seven DC tones may be inserted in the center frequency, 12 tones may be used for a guard band in the leftmost band of the 80 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 80 MHz band. In addition, a 26-RU corresponding to 13 tones on each of the left and right sides of the DC band may be used.

As illustrated inFIG.7, when the layout of the RUs is used for a single user, a 996-RU may be used, in which case five DC tones may be inserted.

The RU described in the present specification may be used in uplink (UL) communication and downlink (DL) communication. For example, when UL-MU communication which is solicited by a trigger frame is performed, a transmitting STA (e.g., an AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA through the trigger frame, and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a 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 PPDU is transmitted to the AP at the same (or overlapped) time period.

For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) may allocate the first RU (e.g., 26/52/106/242-RU. etc.) to the first STA, and may allocate the second RU (e.g., 26/52/106/242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit HE-STF, HE-LTF, and Data fields for the first STA through the first RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and Data fields for the second STA through the second RU.

Information related to a layout of the RU may be signaled through HE-SIG-B.

FIG.8illustrates a structure of an HE-SIG-B field.

As illustrated, an HE-SIG-B field810includes a common field820and a user-specific field830. The common field820may include information commonly applied to all users (i.e., user STAs) which receive SIG-B. The user-specific field830may be called a user-specific control field. When the SIG-B is transferred to a plurality of users, the user-specific field830may be applied only any one of the plurality of users.

As illustrated inFIG.8, the common field820and the user-specific field830may be separately encoded.

The common field820may include RU allocation information of N*8 bits. For example, the RU allocation information may include information related to a location of an RU. For example, when a 20 MHz channel is used as shown inFIG.5, the RU allocation information may include information related to a specific frequency band to which a specific RU (26-RU/52-RU/106-RU) is arranged.

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

As shown the example ofFIG.5up to nine 26-RUs may be allocated to the 20 MHz channel. When the RU allocation information of the common field820is set to “00000000” as shown in Table 1, the nine 26-RUs may be allocated to a corresponding channel (i.e., 20 MHz). In addition, when the RU allocation information of the common field820is set to “00000001” as shown in Table 1, seven 26-RUs and one 52-RU are arranged in a corresponding channel. That is, in the example ofFIG.5, the 52-RU may be allocated to the rightmost side, and the seven 26-RUs may be allocated to the left thereof.

The example of Table 1 shows only some of RU locations capable of displaying 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 a 106-RU is allocated to the leftmost side of the 20 MHz channel, and five 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (e.g., user-STAs) may be allocated to the 106-RU, based on a MU-MIMO scheme. Specifically, up to 8 STAs (e.g., user-STAs) may be allocated to the 106-RU, and the number of STAs (e.g., user-STAs) allocated to the 106-RU is determined based on 3-bit information (y2y1y0). For example, when the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., user-STAs) allocated to the 106-RU based on the MU-MIMO scheme may be N+1.

In general, a plurality of STAs (e.g., user STAs) different from each other may be allocated to a plurality of RUs. However, the plurality of STAs (e.g., user STAs) may be allocated to one or more RUs having at least a specific size (e.g.,106subcarriers), based on the MU-MIMO scheme.

As shown inFIG.8, the user-specific field830may include a plurality of user fields. As described above, the number of STAs (e.g., user STAs) allocated to a specific channel may be determined based on the RU allocation information of the common field820. For example, when the RU allocation information of the common field820is “00000000”, one user STA may be allocated to each of nine 26-RUs (e.g., nine user STAs may be allocated). That is, up to 9 user STAs may be allocated to a specific channel through an OFDMA scheme. In other words, up to 9 user STAs may be allocated to a specific channel through a non-MU-MIMO scheme.

For example, when RU allocation is set to “01000y2y1y0”, a plurality of STAs may be allocated to the 106-RU arranged at the leftmost side through the MU-MIMO scheme, and five user STAs may be allocated to five 26-RUs arranged to the right side thereof through the non-MU MIMO scheme. This case is specified through an example ofFIG.9.

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

For example, when RU allocation is set to “01000010” as shown inFIG.9, a 106-RU may be allocated to the leftmost side of a specific channel, and five 26-RUs may be allocated to the right side thereof. In addition, three user STAs may be allocated to the 106-RU through the MU-MIMO scheme. As a result, since eight user STAs are allocated, the user-specific field830of HE-SIG-B may include eight user fields.

The eight user fields may be expressed in the order shown inFIG.9. In addition, as shown inFIG.8, two user fields may be implemented with one user block field.

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

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

For example, a first bit (i.e., B0-B10) in the user field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of a user STA to which a corresponding user field is allocated. In addition, a second bit (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to a spatial configuration.

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

An MCS, MCS information, an MCS index, an MCS field, or the like used in the present specification may be indicated by an index value. For example, the MCS information may be indicated by an index 0 to an index 11. The MCS information may include information related to a constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information related to a coding rate (e.g., 1/2, 2/3, 3/4, 5/6e, etc.). Information related to a channel coding type (e.g., LCC or LDPC) may be excluded in the MCS information.

In addition, a fourth bit (i.e., B19) in the user field (i.e., 21 bits) may be a reserved field.

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

The aforementioned example relates to the user field of the first format (the format of the MU-MIMO scheme). An example of the user field of the second format (the format of the non-MU-MIMO scheme) is as follows.

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

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

FIG.10illustrates an example of a PPDU used in the present specification.

The PPDU ofFIG.10may be called in various terms such as an EHT PPDU, a TX PPDU, an RX PPDU, a first type or N-th type PPDU, or the like. For example, in the present specification, the PPDU or the EHT PPDU may be called in various terms such as a TX PPDU, a RX PPDU, a first type or N-th type PPDU, or the like. In addition, the EHT PPDU may be used in an EHT system and/or a new WLAN system enhanced from the EHT system.

The PPDU ofFIG.10may indicate the entirety or part of a PPDU type used in the EHT system. For example, the example ofFIG.10may be used for both of a single-user (SU) mode and a multi-user (MU) mode. In other words, the PPDU ofFIG.10may be a PPDU for one receiving STA or a plurality of receiving STAs. When the PPDU ofFIG.10is used for a trigger-based (TB) mode, the EHT-SIG ofFIG.10may be omitted. In other words, an STA which has received a trigger frame for uplink-MU (UL-MU) may transmit the PPDU in which the EHT-SIG is omitted in the example ofFIG.10.

InFIG.10, an L-STF to an EHT-LTF may be called a preamble or a physical preamble, and may be generated/transmitted/received/obtained/decoded in a physical layer.

A subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields ofFIG.10may be determined as 312.5 kHz, and a subcarrier spacing of the EHT-STF, EHT-LTF, and Data fields may be determined as 78.125 kHz. That is, a tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be expressed in unit of 312.5 kHz, and a tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and Data fields may be expressed in unit of 78.125 kHz.

In the PPDU ofFIG.10, the L-LTE and the L-STF may be the same as those in the conventional fields.

The L-SIG field ofFIG.10may include, for example, bit information of 24 bits. For example, the 24-bit information may include a rate field of 4 bits, a reserved bit of 1 bit, a length field of 12 bits, a parity bit of 1 bit, and a tail bit of 6 bits. For example, the length field of 12 bits may include information related to a length or time duration of a PPDU. For example, the length field of 12 bits may be determined based on a type of the PPDU. For example, when the PPDU is a non-HT, HT, VHT PPDU or an EHT PPDU, a 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 the non-HT, HT, VHT PPDI or the EHT PPDU, 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 determined as “a multiple of 3”+1 or “a multiple of 3”+2.

For example, the transmitting STA may apply BCC encoding based on a 1/2 coding rate to the 24-bit information of the L-SIG field. Thereafter, the transmitting STA may obtain a BCC coding bit of 48 bits. BPSK modulation may be applied to the 48-bit coding bit, thereby generating 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to positions except for a pilot subcarrier{subcarrier index −21, −7, +7, +21} and a DC subcarrier{subcarrier index 0}. As a result, the 48 BPSK symbols may be mapped to subcarrier indices −26 to −22, −20 to −8, −6 to −1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map a signal of {−1, −1, −1, 1} to a subcarrier index{−28, −27, +27, +28}. The aforementioned signal may be used for channel estimation on a frequency domain corresponding to {−28, −27, +27, +28}.

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

A universal SIG (U-SIG) may be inserted after the RL-SIG ofFIG.10. The U-SIB may be called in various terms such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, a first (type) control signal, or the like.

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

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

For example, the A-bit information (e.g., 52 un-coded bits) generated by the U-SIG may include a CRC field (e.g., a field having a length of 4 bits) and a tail field (e.g., a field having a length of 6 bits). The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits except for the CRC/tail fields in the second symbol, and may be generated based on the conventional CRC calculation algorithm. In addition, the tail field may be used to terminate trellis of a convolutional decoder, and may be set to, for example, “000000”.

The A-bit information (e.g., 52 un-coded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, the version-independent bits may have a fixed or variable size. 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 of the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be called in various terms such as a first control bit, a second control bit, or the like.

For example, the version-independent bits of the U-SIG may include a PHY version identifier of 3 bits. For example, the PHY version identifier of 3 bits may include information related to a PHY version of a TX/RX PPDU. For example, a first value of the PHY version identifier of 3 bits may indicate that the TX/RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits the EHT PPDU, the PHY version identifier of 3 bits may be set to a first value. In other words, the receiving STA may determine that the RX PPDU is the 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 UL/DL flag field of 1 bit. A first value of the UL/DL flag field of 1 bit 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 related to a TXOP length and information related to a BSS color ID.

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

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

Preamble puncturing may be applied to the PPDU ofFIG.10. The preamble puncturing implies that puncturing is applied to part (e.g., a secondary 20 MHz band) of the full band. For example, when an 80 MHz PPDU is transmitted, an STA may apply puncturing to the secondary 20 MHz band out of the 80 MHz band, and may transmit a PPDU only through a primary 20 MHz band and a secondary 40 MHz band.

For example, a pattern of the preamble puncturing may be configured in advance. For example, when a first puncturing pattern is applied, puncturing may be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when a second puncturing pattern is applied, puncturing may be applied to only any one of two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when a third puncturing pattern is applied, puncturing may be applied to only 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 a fourth puncturing is applied, puncturing may be applied to at least one 20 MHz channel not belonging to a primary 40 MHz band in the presence of the primary 40 MHz band included in the 80 MHaz band within the 160 MHz band (or 80+80 MHz band).

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

For example, the U-SIG and the EHT-SIG may include the information related to the preamble puncturing, based on the following method. When a bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured individually in unit of 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, a first field of the first U-SIG may include information related to a 160 MHz bandwidth, and a second field of the first U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the first 80 MHz band. In addition, a first field of the second U-SIG may include information related to a 160 MHz bandwidth, and a second field of the second U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the second 80 MHz band. Meanwhile, an EHT-SIG contiguous to the first U-SIG may include information related to a preamble puncturing applied to the second 80 MHz band (i.e., information related to a preamble puncturing pattern), and an EHT-SIG contiguous to the second U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the first 80 MHz band.

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

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

The EHT-SIG ofFIG.10may 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 μs. Information related to the number of symbols used for the EHT-SIG may be included in the U-SIG.

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

As in the example ofFIG.8, the common field of the EHT-SIG and the user-specific field of the EHT-SIG may be individually coded. One user block field included in the user-specific field may include information for two users, but a last user block field included in the user-specific field may include information for one user. That is, one user block field of the EHT-SIG may include up to two user fields. As in the example ofFIG.9, each user field may be related to MU-MIMO allocation, or may be related to non-MU-MIMO allocation.

As in the example ofFIG.8, the common field of the EHT-SIG may include a CRC bit and a tail bit. A length of the CRC bit may be determined as 4 bits. A length of the tail bit may be determined as 6 bits, and may be set to ‘000000’.

As in the example ofFIG.8, the common field of the EHT-SIG may include RU allocation information. The RU allocation information may imply information related to a location of an RU to which a plurality of users (i.e., a plurality of receiving STAs) are allocated. The RU allocation information may be configured in unit of 8 bits (or N bits), as in Table 1.

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

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

Information related to a type of STF and/or LTF (information related to a GI applied to LTF is also included) may be included in a SIG-A field and/or SIG-B field or the like ofFIG.10.

A PPDU (e.g., EHT-PPDU) ofFIG.10may be configured based on the example ofFIG.5andFIG.6.

For example, an EHT PPDU transmitted on a20 MHz band, i.e., a20 MHz EHT PPDU, may be configured based on the RU ofFIG.5. That is, a location of an RU of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown inFIG.5.

An EHT PPDU transmitted on a 40 MHz band, i.e., a 40 MHz EHT PPDU, may be configured based on the RU ofFIG.6. That is, a location of an RU of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown inFIG.6.

Since the RU location ofFIG.6corresponds to 40 MHz, atone-plan for 80 MHz may be determined when the pattern ofFIG.6is repeated twice. That is, an 80 MHz EHT PPDU may be transmitted based on a new tone-plan in which not the RU ofFIG.7but the RU ofFIG.6is repeated twice.

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

A tone-plan for 160/240/320 MHz may be configured in such a manner that the pattern ofFIG.6is repeated several times.

The PPDU ofFIG.10may be determined (or identified) as an EHT PPDU based on the following method.

A receiving STA may determine a type of an RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the EHT PPDU: 1) when a first symbol after an L-LTF signal of the RX PPDU is a BPSK symbol; 2) when RL-SIG in which the L-SIG of the RX PPDU is repeated is detected; and 3) when a result of applying “modulo 3” to a value of a length field of the L-SIG of the RX PPDU is detected as “0”. When the RX PPDU is determined as the EHT PPDU, the receiving STA may detect a type of the EHT PPDU (e.g., an SU/MU/Trigger-based/Extended Range type), based on bit information included in a symbol after the RL-SIG ofFIG.10. In other words, the receiving STA may determine the RX PPDU as the EHT PPDU, based on: 1) a first symbol after an L-LTF signal, which is a BPSK symbol; 2) RL-SIG contiguous to the L-SIG field and identical to L-SIG; 3) L-SIG including a length field in which a result of applying “modulo 3” is set to “0”; and 4) a 3-bit PHY version identifier of the aforementioned U-SIG (e.g., a PHY version identifier having a first value).

For example, the receiving STA may determine the type of the RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the HE PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; 2) when RL-SIG in which the L-SIG is repeated is detected; and 3) when a result of applying “modulo 3” to a value of a length field of the L-SIG is detected as “1” or “2”.

For example, the receiving STA may determine the type of the RX PPDU as a non-HT, HT, and VHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; and 2) when RL-SIG in which L-SIG is repeated is not detected. In addition, even if the receiving STA detects that the RL-SIG is repeated, when a result of applying “modulo 3” to the length value of the L-SIG is detected as “0”, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU.

In the following example, a signal represented as a (TX/RX/UL/DL) signal, a (TX/RX/UL/DL) frame, a (TX/RX/UL/DL) packet, a (TX/RX/UL/DL) data unit, (TX/RX/UL/DL) data, or the like may be a signal transmitted/received based on the PPDU ofFIG.10. The PPDU ofFIG.10may be used to transmit/receive frames of various types. For example, the PPDU ofFIG.10may be used for a control frame. An example of the control frame may include a request to send (RTS), a clear to send (CTS), a power save-poll (PS-poll), BlockACKReq, BlockAck, a null data packet (NDP) announcement, and a trigger frame. For example, the PPDU ofFIG.10may 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 ofFIG.10may be used for a data frame. For example, the PPDU ofFIG.10may be used to simultaneously transmit at least two or more of the control frames, the management frame, and the data frame.

FIG.11illustrates an example of a modified transmission device and/or receiving device of the present specification.

Each device/STA of the sub-figure (a)/(b) ofFIG.1may be modified as shown inFIG.11. A transceiver630ofFIG.11may be identical to the transceivers113and123ofFIG.1. The transceiver630ofFIG.11may include a receiver and a transmitter.

A processor610ofFIG.11may be identical to the processors111and121ofFIG.1. Alternatively, the processor610ofFIG.11may be identical to the processing chips114and124ofFIG.1.

A memory620ofFIG.11may be identical to the memories112and122ofFIG.1. Alternatively, the memory620ofFIG.11may be a separate external memory different from the memories112and122ofFIG.1.

Referring toFIG.11, a power management module611manages power for the processor610and/or the transceiver630. A battery612supplies power to the power management module611. A display613outputs a result processed by the processor610. A keypad614receives inputs to be used by the processor610. The keypad614may be displayed on the display613. A SIM card615may be an integrated circuit which is used to securely store an international mobile subscriber identity (IMSI) and its related key, which are used to identify and authenticate subscribers on mobile telephony devices such as mobile phones and computers.

Referring toFIG.11, a speaker640may output a result related to a sound processed by the processor610. A microphone641may receive an input related to a sound to be used by the processor610.

1. Embodiment Applicable to the Present Disclosure

In the wireless LAN 802.11 system, PPDU can be transmitted using a wider bandwidth than the 320 MHz bandwidth of 802.11be to increase peak throughput. To this end, this specification proposes a method of defining a channel wider than a 320 MHz channel and indicating when a specific PPDU is transmitted using the corresponding bandwidth.

FIGS.12to14show channels from 20 MHz to 160 MHz currently used in 802.11be.

FIG.12shows the channelization of the 6 GHz band.

Referring toFIG.12, the 6 GHz band has a total spectrum of 1200 MHz, and the total spectrum may include 59 20 MHz channels, 29 40 MHz channels, 14 80 MHz channels, or 7 160 MHz channels.

FIG.13shows the channelization of the 5 GHz band.

Referring toFIG.13, the 5 GHz band has a total spectrum of 500 MHz (180 MHz without DFS (Dynamic Frequency Selection)), and the total spectrum may include 25 20 MHz channels, 12 40 MHz channels, 6 80 MHz channels, or 2 160 MHz channels.

FIG.14shows the channelization of the 2.4 GHz band.

Referring toFIG.14, the 2.4 GHz band has a total spectrum of 80 MHz, and the total spectrum may include three 20 MHz channels (non-overlapping channels) or one 40 MHz channel.

FIG.15shows channelization and extended channelization of the 6 GHz band of the 802.11be wireless LAN system.

Referring toFIG.15, a 320 MHz channel is generated by combining two 160 MHz channels, and two types of 320 MHz channels (320-1 MHz channel and 320-2 MHz channel) overlap each other. In other words, a 320 MHz channel was defined to maximize utilization within the total spectrum of the 6 GHz band by partially overlapping 320 channels.

EHT (802.11be) supports not only the 160 MHz BW (BandWidth) that was supported up to 802.11ax, but also a wider BW (BandWidth) of 320 MHz. In the existing 20/40/80/160 MHz channelization, overlapping channels did not exist. However, 320 MHz BW includes overlapping channels such as 320-1 MHz and 320-2 MHz inFIG.15. Overlapping channels may or may not exist between the 320-1 MHz channel and the 320-2 MHz channel. for example, inFIG.15, the first 320-1 MHz channel and the first 320-2 MHz channel have overlapping channels of 160 MHz BW, but the first 320-1 MHz channel and the second 320-2 MHz channel do not have overlapping channels. Meanwhile, currently, the 320-1 MHz channel and the 320-2 MHz channel are signaled separately in the BW subfield of the Universal Signal (U-SIG) field of the EHT PPDU. The 320-1 MHz channel and 320-2 MHz channel are channels supported by different BSS (Basic Service Set). For example, the first BSS may support a 320-1 MHz channel, and the second BSS may support a 320-2 MHz channel.

The reason for distinguishing between 320-1 MHz and 320-2 MHz is because if the STA's primary 20 MHz channel is in an area where 320-1 MHz and 320-2 MHz overlap, it must be distinguished whether it is allocated to 320-1 MHz or 320-2 MHz.

In this specification, the 160 MHz channel including the primary channel (i.e., 20 MHz primary channel) is referred to as P160, and the 160 MHz channel without it is referred to as S160.

Additionally, this specification proposes to include a 480 MHz channel and a 640 MHz channel, which are extended channels within the 6 GHz band. Descriptions of the 480 MHz channel and 640 MHz channel will be provided later.

The table below shows the configuration of the U-SIG Version Independent field in the EHT MU PPDU ofFIG.10. The Version Independent field can be used in the format below even in Wi-Fi after 802.11be.

TABLE 3Two partsNumberof U-SIGBitFieldof bitsDescriptionU-SIG-1B0-B2PHY Version Identifier3Differentiate between different PHY clauses.Set to 0 for EHT.Values 1-7 are Validate.B3-B5Bandwidth3Set to 0 for 20 MHz.Set to 1 for 40 MHz.Set to 2 Tor 80 MHz.Set to 3 for 160 MHz.Set to 4 for 320 MHz-1.Set io 5 for 320 MHz-2.Values 6 and 7 are Validate.B6UL/DL1Indicates whether the PPDU is sent in UL orDL. Set to the TXVECTOR parameterUPLINK_FLAG.A value of 1 indicates the PPDU isaddressed to an AP.A value of 0 indicates the PPDU isaddressed to a non-AP STA.B7-B12BSS Color6An identifier of the BSS.Set to the TXVECTOR parameterBSS_COLOR.B13-B19TXOP7If the TXVECTOR parameterTXOP_DURATION is UNSPECIFIED, set to127 to indicate the absence of Jurationinformation.If the TXVECTOR parameterTXOP_DURATION is an integer value, set toa value less than 127 to indicate durationinformation for NAV setting and protection ofthe TXOP as follows:If the TXVECTOR parameter TXOP-DURATION is less than 512, set to2 × floor(TXOP_DURATION/8).Otherwise, set to2 × floor((TXOP_DURATION − 512)/128) + 1.B20-B24Disregard5Set to all 1s and treat as Disregard.B25ValidateSet to 1 and treat as Validate.U-SIG-2B0-B1PPDU Type And2If the UL/DL field is set to 0:Compression ModeA value of 0 indicates a DL OFDMAtransmission.A value of 1 indicates a transmission to asingle user or an EHT sounding NDP.A value of 2 indicates a non-OFDMA DLMU-MIMO transmission.A value of 3 is ValidateIf the UL/DL field is set to 1:A value of 1 indicates a transmission to asingle user or an EHT sounding NDP.Values 2 and 3 are Validate.NOTE-A value of 0 indicates a TBPPDU.For further clarifications on all values ofthis field, refer to Table 9 (Combination ofUL/DL, and PPDU Type And CompressionMode field).B2ValidateSet to 1 and treat as Validate.B3-B7Punctured Channel5If the PPDU Type And Compression ModeInformationfield is set to 1 regardless of the value of theUL/DL field, or the PPDU Type AndCompression Mode field is set to 2 and theUL/DL field is 0:Indicates the puncturing information ofthis non-OFDMA transmission. SeeTable 10 (Definition of the PuncturedChannel Information field in the U-SIGforan EHT MU PPDU asing non-OFDMA transmissions) for thedefinition. Undefined values of this fieldare ValidateIf the PPDU Type And Compression Modefield is set to 0 and the UL/DL field is 0;If the Bandwidth field is set to a valuebetween 2 and 5, which indicates an80 MHz, 160 MHz or 320 MHz PPDU,then B3-B6 is a 4-bit bitmap thatindicates which 20 MHz subchannel ispunctured in the 80 MHz frequencysubblock where U-SIG processing isperformed. The 4-bit bitmap is indexedby the 20 MHz subchannels in ascendingorder with B3 indicating the lowestfrequency 20 MHz subchannel. For cachof the bits B3-B6, a value of 0 indicatesthat the corresponding 20 MHz channelis punctured, and a value of 1 is usedotherwise. The following allowedpunctured patterns (B3-B6) are definedfor an 80 MHz frequency subblock: 111(no puncturing), 0111, 1013, 1101, 1110,0011, 1100, and 1001. Any field valuesother than the allowed punctured patternsare Validate. Field valute may be variedfrom one 80 MHz to the other.If the Bandwidth field is set to 0 or 1,which indicates a 20/40 MHz PPDU,B3-B6 are set to all 1s. Other values areValidate.B7 is set to 1 and Disregard.B8ValidateSet to 1 and treat as Validate.B9-B10EHT-SIG MCS2Indicates the MCS need for modulating theEHT-SIG.Set to 0 for EHT-MCS 0.Set to 1 for HHT-MCS 1.Set to 2 for EHT-MCS 3.Set to 3 for EHT-MCS 15.B11-B15Number Of EHT-SIG5Indicates the number of EHT-SIG symbols.SymbolsSet to a value that is the number of EHT-SIGsymbols minus 1. This value shall be the samein every 80 MHz frequency subblock.B16-B19CRCCRC for bits 0-41 of the U-SIG feld. Bits 0-41 of the U-SIG field correspond to bits 0-25of U-SIG-1 field followed by bits 0-15 of U-SIG-2 field.B20-B25Tail6Used to terminate the trellis of theconvolutional decoder. Set to 0.

In Wi-Fi after 802.11be, PHY Version Identifier can be set to a value other than 0. Additionally, when a bandwidth and channel wider than 320 MHz can be defined and PPDU is transmitted using that bandwidth, it can be indicated using the Validate value (i.e., 6 and 7) of the BW field in Table 3 above, or can be indicated by using an additional 1 bit in the BW field.

Below, this embodiment proposes definitions of channels and bandwidths of 640/480 MHz and a BW indication method for when PPDUs using the corresponding bandwidth are transmitted.1) 640 MHz1.1) 640 MHz channel

FIG.16shows the channelization of the 6 GHz band with a 640 MHz channel defined.

As shown inFIG.16, four 640 MHz channels can be defined by combining two adjacent 320 MHz channels. This has the highest flexibility in using 640 MHz and can increase the usefulness of the 640 MHz channel.

i) Four values can be used to eliminate ambiguity when indicating bandwidth in a PPDU using the corresponding channel. Or ii) when indicating bandwidth, two values can be used by distinguishing whether it is a combination within 320-1 MHz or a combination within 320-2 MHz, or one value can be used without distinction. In case ii), there may be ambiguity in the indication of the channel being used.

Alternatively, only some of the 640 MHz channels inFIG.16can be defined.

For example, in this embodiment, only 640-1 and 640-3, whose overlapping portion is only 320 MHz, can be defined, or only 640-2 and 640-4 can be defined. This is a method that combines two adjacent 320 MHz channels in 320-1 or 320-2. When indicating bandwidth in a PPDU using the channel, two values can be used to eliminate ambiguity, or one value can be used without distinction. In the latter case, there may be ambiguity in the indication of the channel being used.

As another example, only 640-1 and 640-4 can be defined, which has the advantage that the adjacent portion of the two 640 MHz channels is minimized, so that 640 MHz can be used with minimal puncturing when both adjacent BSSs use the 640 MHz channel. When indicating bandwidth in a PPDU using the channel, two values can be used to eliminate ambiguity, or one value can be used without distinction. In the latter case, there may be ambiguity in the indication of the channel being used.

As another example, 640 MHz signaling can be minimized by defining only one channel among the four 640 MHz channels inFIG.16. This may not be desirable from a usability perspective. In this case, bandwidth can be indicated using one value.

A 640 MHz channel can only be defined in the 6 GHz band.1.2) 640 MHz bandwidth

Contiguous 640 MHz can be supported using the channel defined in 1.1), and non-contiguous 320+320 MHz can be supported using two non-contiguous 320 MHz.

When indicating bandwidth in a PPDU using the channel, two values can be used to distinguish whether the 320 MHz channel located at a low frequency or the primary 320 MHz channel is 320-1 or 320-2, or one value can be used without distinction. Everything can be instructed. In the latter case, there may be ambiguity in the indication of the channel being used. Even in the former case, there may still be ambiguity because the OBSS (Overlapping Basic Service Set) STA cannot determine the location of the channel.

Or, to simplify BW signaling, only the combination at 320-1 or 320-2 can be considered in non-contiguous 320+320, which is as follows.320-1(1)+320-1(3), 320-2(1)+320-2(3)

When indicating bandwidth in a PPDU using the channel, two values can be used to distinguish whether it is a combination of 320-1 or 320-2, or both values can be indicated using one value without distinction. In the latter case, there may be ambiguity in the indication of the channel being used.

Alternatively, this embodiment may define only one of the above two 320-1(1)+320-1(3) and 320-2(1)+320-2(3). This can be used to minimize signaling. In other words, in this case, bandwidth can be indicated using one value.

Additionally, non-contiguous 320+160+160 MHz can be supported using one non-contiguous 320 MHz and two non-contiguous 160 MHz. Two values can be used to distinguish whether the 320 MHz channel is 320-1 or 320-2, or both can be indicated using one value without distinction. In the latter case, there may be ambiguity in the indication of the channel being used. Even in the former case, there may still be ambiguity because the OBSS STA cannot determine the location of the channel.

Alternatively, only one of 320-1+160+160 MHz or 320-2+160+160 can be supported. In this case, all values can be indicated using one value, but there may be ambiguity in the indication of the channel being used.

Alternatively, non-contiguous 160+160+160+160 MHz can be supported using four non-contiguous 160 MHz. In this case, all values can be indicated using one value, but there may be ambiguity in the indication of the channel being used.

640 MHz bandwidth can only be defined in the 6 GHz band.

Additionally, in the non-contiguous 320+160+160 MHz or non-contiguous 160+160+160+160 MHz bandwidth proposed above, the 160 MHz channel can be a 160 MHz channel within the 5 GHz band as well as the 6 GHz band.2) 480 MHz2.1) 480 MHz channel

FIG.17shows the channelization of the 6 GHz band with a 480 MHz channel defined.

As shown inFIG.17, five 480 MHz channels can be defined by combining adjacent 160 MHz and 320 MHz channels. This provides the highest flexibility in using 480 MHz and can increase the usefulness of the 480 MHz channel.

i) When indicating bandwidth in a PPDU using the channel, three values can be used to eliminate ambiguity (480-1and480-4have no overlap and can be indicated with one value. Similarly,480-2and480-5also have no overlap and can be indicated with one value.). Or ii) when considered as a combination of 320 MHz and the immediately adjacent 160 MHz. Two values can be used to determine whether the 320 MHz channel is 320-1 or 320-2, or one value can be used to indicate both. In the two cases of ii), there may be ambiguity in the indication of the channel to be used.

Alternatively, only some of the 480 MHz channels above can be defined.

For example, this embodiment can define only 480-1, 480-3, and 480-5, or only 480-2 and 480-4, whose overlapping portion is only 160 MHz. This is a method that combines the 320 MHz channels within 320-1 or 320-2 and the 160 MHz channel immediately adjacent to it. (Or, it is a method that combines the 320 MHz channels within 320-1 or 320-2 and the adjacent 160 MHz channel.) In each case, bandwidth can be indicated using 3/2 (or 2/3) values, and all can be indicated using 1 value without distinction. In the latter two cases, there may be ambiguity in the indication of the channel being used.

As another example, 480 MHz signaling can be reduced by excluding 480-3. Two values can be used to eliminate ambiguity when indicating bandwidth in a PPDU using the channel (480-1 and 480-4 have no overlap and can be indicated with one value. Similarly, 480-2 and 480-5 also have no overlap and can be indicated with one value.) Alternatively, in this embodiment, when indicating bandwidth, all can be indicated using one value without distinction. In the latter case, there may be ambiguity in the indication of the channel being used.

As another example, only 480-1 and 480-4 or only 480-2 and 480-5 can be defined, which minimizes 480 MHz signaling because there is no overlap between the two 480 MHz channels. In other words, in this case, bandwidth can be indicated using one value.

As another example, only one channel among the five 480 MHz channels above can be defined, but this may not be desirable in terms of usability. In this case, bandwidth can be indicated using one value.

The 480 MHz channel can only be defined in the 6 GHz band.2.2) 480 MHz bandwidth

Using the channel defined in 2.1), contiguous 480 MHz can be supported and non-contiguous 320+160 MHz can also be supported.

Non-contiguous 320+160 MHz may be a combination of one 320 MHz channel in the 6 GHz band and one non-adjacent 160 MHz channel. This can be good from a usability perspective. When indicating bandwidth in a PPDU using the channel, two values can be used to distinguish whether the 320 MHz channel is 320-1 or 320-2, or both values can be indicated using one value without distinction. In the latter case, there may be ambiguity in the indication of the channel being used. Even in the former case, there may still be ambiguity because the OBSS STA cannot determine the location of the channel.

Alternatively, non-contiguous 320+160 MHz may be a combination of a 320 MHz channel corresponding to 320-1 in the 6 GHz band and one non-adjacent 160 MHz channel. Alternatively, non-contiguous 320+160 MHz may be a combination of a 320 MHz channel corresponding to 320-2 in the 6 GHz band and one non-adjacent 160 MHz channel. This can simplify signaling. In this case, bandwidth can be indicated using one value. However, since the OBSS STA cannot determine the location of the channel, there may still be ambiguity.

Alternatively, non-contiguous 160+160+160 MHz can be supported using three non-contiguous 160 MHz. In this case, all values can be indicated using one value, but there may be ambiguity in the indication of the channel being used.

The above 480 MHz bandwidth can only be defined in the 6 GHz band.

Additionally, in the non-contiguous 320+160 MHz or non-contiguous 160+160+160 MHz bandwidth proposed above, the 160 MHz channel can be a 160 MHz channel within the 5 GHz band as well as the 6 GHz band.3) Bandwidth indicator

Considering the number of values used when indicating the bandwidth suggested in 1) and 2) above, this embodiment can indicate 480/640 MHz bandwidth in various ways by using only the Validate value in the BW field of the Version independent field or by additionally using 1 bit.3.1) When both 480 MHz and 640 MHz bandwidth are used

The most desirable method is to indicate 480 MHz bandwidth (including non-contiguous) using the value 6 in the BW field of the Version independent field, and 640 MHz bandwidth (including non-contiguous) using value 7. In this case, in order to eliminate ambiguity, it may be desirable to indicate using one value among the various channel and bandwidth methods of 1) and 2), but it is not limited to this.

Or, if bandwidth is indicated using multiple values, by additionally using one bit of B20-25in the U-SIG-1 field in Table 3 above (BW field+1 additional bit, total 4 bits), values from 0 to 15 can be used. Starting from the case where the value of BW field+additional 1 bit is 6, indicators for 480 MHz bandwidth and 640 bandwidth can be additionally defined in order. In this case, the non-contiguous case and the contiguous case can be indicated with the same value or different values.

For example, 480 MHz and 640 MHz bandwidth can be indicated as follows using a total of 4 bits (BW field+1 additional bit (B20)).

If the value of the 4 bits is 6, 480-1 is indicated, if the value of the 4 bits is 7, 480-2 is indicated, if the value of the 4 bits is 8, 640-1 is indicated, if the value of the 4 bits is 9, 640-2 is indicated, and if the value of the 4 bits is 10 to 15, it is set to Validate.3.2) 480 MHz is a special case of 640 MHz (for example, a case where a 160 MHz channel is punctured at 640 MHz)

Considering the number of values used to indicate bandwidth, it may be desirable to consider 480 MHz as a special case of 640 MHz. At this time, puncturing from 640 MHz to 160 MHz can be indicated in the Version dependent field of U-SIG or another signaling field.

The preferred method is to indicate 640 MHz bandwidth using two values (6,7) or one value (6). In this case, in order to eliminate ambiguity, it may be desirable to define a method without ambiguity by using two or one value when indicating bandwidth among the various 640 MHz channel and bandwidth methods in 1), but it is not limited to this. In this case, the non-contiguous case and the contiguous case can be indicated with the same value. Alternatively, one value can be used to indicate a contiguous 640 MHz channel and the other value can be used to indicate a non-contiguous 640 MHz channel.

For example, 640 MHz bandwidth can be indicated using the BW field (existing 3 bits) as follows.

If the value of the 3 bits is 6, 640-1 can be indicated, and if the value of the 3 bits is 7, 640-2 can be indicated. At this time, 160 MHz puncturing in a 640 MHz bandwidth may be puncturing for the first or last 160 MHz, accordingly, it can be determined whether it is 480-1 (when the last 160 MHz is punctured) or 480-2 (when the first 160 MHz is punctured).

Alternatively, if bandwidth is indicated using more than two values, one bit of B20-25in the U-SIG field can be additionally used, and values from 0 to 15 can be used. BW field+additional 1 bit can additionally define an indicator of 640 bandwidth, starting with a value of 6. In this case, the non-contiguous case and the contiguous case can be indicated with the same value or different values.

If the non-contiguous case and the contiguous case are indicated with the same value, 1 bit may be additionally used to distinguish them, and this may be one bit among B20-25in the U-SIG field.

Or, in all of the above cases, the non-contiguous situation may not be considered, as in 802.11be. However, if 480 MHz is a case of 160 MHz puncturing of 640 MHz, the non-contiguous situation of 480 MHz within 640 MHz can be considered.

Alternatively, if this embodiment does not define a 640 MHz channel and only defines a 480 MHz channel, the 480 MHz bandwidth can be indicated using the BW field (existing 3 bits) as follows.

If the value of the 3 bits is 6, 480-1 can be indicated, and if the value of the 3 bits is 7, 480-2 can be indicated.

FIG.18is a flowchart illustrating the operation of the transmitting apparatus/device according to the present embodiment.

The example ofFIG.18may be performed by a transmitting device (AP and/or non-AP STA).

Some of each step (or detailed sub-step to be described later) of the example ofFIG.18may be skipped/omitted.

Through step S1810, the transmitting device (transmitting STA) may obtain information about the above-described tone plan. As described above, the information about the tone plan includes the size and location of the RU, control information related to the RU, information about a frequency band including the RU, information about an STA receiving the RU, and the like.

Through step S1820, the transmitting device may construct/generate a PPDU based on the acquired control information. Configuring/generating the PPDU may include configuring/generating each field of the PPDU. That is, step S1820includes configuring the EHT-SIG field including control information about the tone plan. That is, step S1820includes configuring a field including control information (e.g., N bitmap) indicating the size/position of the RU; and/or configuring a field including an identifier of an STA receiving the RU (e.g., AID).

Also, step S1820may include generating an STF/LTF sequence transmitted through a specific RU. The STF/LTF sequence may be generated based on a preset STF generation sequence/LTF generation sequence.

Also, step S1820may include generating a data field (i.e., MPDU) transmitted through a specific RU.

The transmitting device may transmit the PPDU constructed through step S1820to the receiving device based on step S1830.

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

A signal/field/sequence constructed according to the present specification may be transmitted in the form ofFIG.10.

FIG.19is a flowchart illustrating the operation of the receiving apparatus/device according to the present embodiment.

The aforementioned PPDU may be received according to the example ofFIG.19.

The example ofFIG.19may be performed by a receiving apparatus/device (AP and/or non-AP STA).

Some of each step (or detailed sub-step to be described later) of the example ofFIG.19may be skipped/omitted.

The receiving device (receiving STA) may receive all or part of the PPDU through step S1910. The received signal may be in the form ofFIG.10.

A sub-step of step S1910may be determined based on step S1830ofFIG.18. That is, in step S1910, an operation of restoring the result of the CSD, Spatial Mapping, IDFT/IFFT operation, and GI insertion operation applied in step S1930may be performed.

In step S1920, the receiving device may perform decoding on all/part of the PPDU. Also, the receiving device may obtain control information related to atone plan (i.e., RU) from the decoded PPDU.

More specifically, the receiving device may decode the L-SIG and EHT-SIG of the PPDU based on the legacy STF/LTF and obtain information included in the L-SIG and EHT SIG fields. Information on various tone plans (i.e., RUs) described in this specification may be included in the EHT-SIG, and the receiving STA may obtain information on the tone plan (i.e., RU) through the EHT-SIG.

In step S1930, the receiving device may decode the remaining part of the PPDU based on information about the tone plan (i.e., RU) acquired through step S1920. For example, the receiving STA may decode the STF/LTF field of the PPDU based on information about one plan (i.e., RU). In addition, the receiving STA may decode the data field of the PPDU based on information about the tone plan (i.e., RU) and obtain the MPDU included in the data field.

In addition, the receiving device may perform a processing operation of transferring the data decoded through step S1930to a higher layer (e.g., MAC layer). In addition, when generation of a signal is instructed from the upper layer to the PHY layer in response to data transmitted to the upper layer, a subsequent operation may be performed.

Hereinafter, the above-described embodiment will be described with reference toFIG.1toFIG.19.

FIG.20is a flow diagram illustrating a procedure in which a transmitting generates a PPDU based on control information related to channelization in the 6 GHz band according to this embodiment.

The example ofFIG.20may be performed in a network environment in which a next generation WLAN system (IEEE 802.11be or EHT WLAN system) is supported. The next generation wireless LAN system is a WLAN system that is enhanced from an 802.11ax system and may, therefore, satisfy backward compatibility with the 802.11ax system.

The example ofFIG.20is performed in a transmitting STA, and the transmitting STA may correspond to an access point (AP) STA. The receiving STA may correspond to a non-AP STA.

This embodiment proposes a method of configuring channelization and a method of indicating a bandwidth when supporting a 480 MHz channel and a 640 MHz channel in a 6 GHz band.

In step S2010, a transmitting station (STA) obtains control information related to channelization in a 6 GHz band.

In step S2020, the transmitting STA generates a Physical Protocol Data Unit (PPDU) based on the control information.

In step S2030, the transmitting STA transmits the PPDU to a receiving STA.

The channelization configuration of the 6 GHz band is as follows.

The 6 GHz band includes first to seventh 160 MHz channels, first to third 320-1 MHz channels, first to third 320-2 MHz channels, first and second 480-1 MHz channels, or first and second 480-2 MHz channels.

The first to seventh 160 MHz channels are arranged in order from lowest frequency to highest frequency.

The first 320-1 MHz channel includes the first and second 160 MHz channels, the second 320-1 MHz channel includes the third and fourth 160 MHz channels, and the third 320-1 MHz channel includes the fifth and sixth 160 MHz channels.

The first 320-2 MHz channel includes the second and third 160 MHz channels, the second 320-2 MHz channel includes the fourth and fifth 160 MHz channels, and the third 320-2 MHz channel includes the sixth and seventh 160 MHz channels.

The first 480-1 MHz channel includes the first 320-1 MHz channel and the third 160 MHz channel, or includes the first 160 MHz channel and the first 320-2 MHz channel. The second 480-1 MHz channel includes the third 320-1 MHz channel and the fourth 160 MHz channel, or includes the second 320-2 MHz channel and the sixth 160 MHz channel.

The first 480-2 MHz channel includes the first 320-2 MHz channel and the fourth 160 MHz channel, or includes the second 160 MHz channel and the second 320-1 MHz channel. The second 480-2 MHz channel includes the third 320-1 MHz channel and the seventh 160 MHz channel, or includes the fifth 160 MHz channel and the third 320-2 MHz channel.

The PPDU may include a control field and the data field. The control field may include a Bandwidth (BW) field. The BW field may consist of 3 bits.

When the channelization configuration of the 6 GHz band is defined only up to 480 MHz, the method of indicating the bandwidth of the PPDU is as follows.

Based on/If the value of the BW field being/is 6, the bandwidth of the PPDU is 480-1 MHz. Based on/If the value of the BW field being/is 7, the bandwidth of the PPDU is 480-2 MHz. In this case, a bandwidth of 480 MHz may be indicated using only the existing BW field (3 bits).

The 6 GHz band may further include a 640-1 MHz channel and a 640-2 MHz channel. The 640-1 MHz channel may include the first and second 320-1 MHz channel, and the 640-2 MHz channel may include the second and third 320-2 MHz channels.

When the channelization configuration of the 6 GHz band is also defined as 480 MHz and 640 MHz, the method of indicating the bandwidth of the PPDU is as follows.

The control field may further include 1 bit. The 1 bit may be one of a Disregard field or a Validate field (for example, B20).

Based on/If a value of the 3 bits and the 1 bit being/is 6, the bandwidth of the PPDU is 480-1 MHz. Based on/If the value of the 3 bits and the 1 bit being/is 7, the bandwidth of the PPDU is 480-2 MHz. Based on/If the value of the 3 bits and the 1 bit being/is 8, the bandwidth of the PPDU is 640-1 MHz. Based on/If the value of the 3 bits and the 1 bit being/is 9, the bandwidth of the PPDU is 640-2 MHz.

The control field may further include a puncturing field.

Based on/If a value of the BW field being/is 6, the bandwidth of the PPDU is 640-1 MHz. Based on/If a value of the puncturing field being/is 0, a last 160 MHz of the 640-1 MHz is punctured. Based on/If the value of the puncturing field being/is 1, a first 160 MHz of the 640-1 MHz is punctured.

Based on/If the value of the BW field being/is 7, the bandwidth of the PPDU is 640-2 MHz. Based on/If the value of the puncturing field being/is 0, a last 160 MHz of the 640-2 MHz is punctured. Based on/If the value of the puncturing field being/is 1, a first 160 MHz of the 640-2 MHz is punctured.

In this case, only 640 MHz is indicated using the BW field, but the puncturing field can be used to indicate a bandwidth of 480 MHz with 160 MHz punctured from 640 MHz.

The reason for distinguishing between the 320-1 MHz channel (or 480-1 MHz channel, 640-1 MHz channel) and the 320-2 MHz channel (or 480-2 MHz channel, 640-2 MHz channel) is that it is necessary to distinguish which channel it is assigned to when the primary 20 MHz channel of the receiving STA is in an area overlapping the 320-1 MHz channel (or 480-1 MHz channel, 640-1 MHz channel) and the 320-2 MHz channel (or 480-2 MHz channel, 640-2 MHz channel).

FIG.21is a flow diagram illustrating a procedure in which a receiving STA receives a PPDU based on control information related to channelization in the 6 GHz band according to this embodiment.

The example ofFIG.21may be performed in a network environment in which a next generation WLAN system (IEEE 802.11be or EHT WLAN system) is supported. The next generation wireless LAN system is a WLAN system that is enhanced from an 802.11ax system and may, therefore, satisfy backward compatibility with the 802.11ax system.

The example ofFIG.21is performed in a receiving STA, and the receiving STA may correspond to non-access point (a non-AP) STA. The transmitting STA may correspond to an AP STA.

This embodiment proposes a method of configuring channelization and a method of indicating a bandwidth when supporting a 480 MHz channel and a 640 MHz channel in a 6 GHz band.

In step S2110, a receiving station (STA) receives a Physical Protocol Data Unit (PPDU) from a transmitting STA.

In step S2120, the receiving STA decodes the PPDU and obtains control information related to channelization in a 6 GHz band.

In step S2130, the receiving STA decodes a data field of the PPDU based on the control information.

The channelization configuration of the 6 GHz band is as follows.

The 6 GHz band includes first to seventh 160 MHz channels, first to third 320-1 MHz channels, first to third 320-2 MHz channels, first and second 480-1 MHz channels, or first and second 480-2 MHz channels.

The first to seventh 160 MHz channels are arranged in order from lowest frequency to highest frequency.

The first 320-1 MHz channel includes the first and second 160 MHz channels, the second 320-1 MHz channel includes the third and fourth 160 MHz channels, and the third 320-1 MHz channel includes the fifth and sixth 160 MHz channels.

The first 320-2 MHz channel includes the second and third 160 MHz channels, the second 320-2 MHz channel includes the fourth and fifth 160 MHz channels, and the third 320-2 MHz channel includes the sixth and seventh 160 MHz channels.

The first 480-1 MHz channel includes the first 320-1 MHz channel and the third 160 MHz channel, or includes the first 160 MHz channel and the first 320-2 MHz channel. The second 480-1 MHz channel includes the third 320-1 MHz channel and the fourth 160 MHz channel, or includes the second 320-2 MHz channel and the sixth 160 MHz channel.

The first 480-2 MHz channel includes the first 320-2 MHz channel and the fourth 160 MHz channel, or includes the second 160 MHz channel and the second 320-1 MHz channel. The second 480-2 MHz channel includes the third 320-1 MHz channel and the seventh 160 MHz channel, or includes the fifth 160 MHz channel and the third 320-2 MHz channel.

The PPDU may include a control field and the data field. The control field may include a Bandwidth (BW) field. The BW field may consist of 3 bits.

When the channelization configuration of the 6 GHz band is defined only up to 480 MHz, the method of indicating the bandwidth of the PPDU is as follows.

Based on/If the value of the BW field being/is 6, the bandwidth of the PPDU is 480-1 MHz. Based on/If the value of the BW field being/is 7, the bandwidth of the PPDU is 480-2 MHz. In this case, a bandwidth of 480 MHz may be indicated using only the existing BW field (3 bits).

The 6 GHz band may further include a 640-1 MHz channel and a 640-2 MHz channel. The 640-1 MHz channel may include the first and second 320-1 MHz channel, and the 640-2 MHz channel may include the second and third 320-2 MHz channels.

When the channelization configuration of the 6 GHz band is also defined as 480 MHz and 640 MHz, the method of indicating the bandwidth of the PPDU is as follows.

The control field may further include 1 bit. The 1 bit may be one of a Disregard field or a Validate field (for example, B20).

Based on/If a value of the 3 bits and the 1 bit being/is 6, the bandwidth of the PPDU is 480-1 MHz. Based on/If the value of the 3 bits and the 1 bit being/is 7, the bandwidth of the PPDU is 480-2 MHz. Based on/If the value of the 3 bits and the 1 bit being/is 8, the bandwidth of the PPDU is 640-1 MHz. Based on/If the value of the 3 bits and the 1 bit being/is 9, the bandwidth of the PPDU is 640-2 MHz.

The control field may further include a puncturing field.

Based on/If a value of the BW field being/is 6, the bandwidth of the PPDU is 640-1 MHz. Based on/If a value of the puncturing field being/is 0, a last 160 MHz of the 640-1 MHz is punctured. Based on/If the value of the puncturing field being/is 1, a first 160 MHz of the 640-1 MHz is punctured.

Based on/If the value of the BW field being/is 7, the bandwidth of the PPDU is 640-2 MHz. Based on/If the value of the puncturing field being/is 0, a last 160 MHz of the 640-2 MHz is punctured. Based on/If the value of the puncturing field being/is 1, a first 160 MHz of the 640-2 MHz is punctured.

In this case, only 640 MHz is indicated using the BW field, but the puncturing field can be used to indicate a bandwidth of 480 MHz with 160 MHz punctured from 640 MHz.

The reason for distinguishing between the 320-1 MHz channel (or 480-1 MHz channel, 640-1 MHz channel) and the 320-2 MHz channel (or 480-2 MHz channel, 640-2 MHz channel) is that it is necessary to distinguish which channel it is assigned to when the primary 20 MHz channel of the receiving STA is in an area overlapping the 320-1 MHz channel (or 480-1 MHz channel, 640-1 MHz channel) and the 320-2 MHz channel (or 480-2 MHz channel, 640-2 MHz channel).

2. Device Configuration

The technical features of the present disclosure may be applied to various devices and methods. For example, the technical features of the present disclosure may be performed/supported through the device(s) ofFIG.1and/orFIG.11. For example, the technical features of the present disclosure may be applied to only part ofFIG.1and/orFIG.11. For example, the technical features of the present disclosure may be implemented based on the processing chip(s)114and124ofFIG.1, or implemented based on the processor(s)111and121and the memory(s)112and122, or implemented based on the processor610and the memory620ofFIG.11. For example, the device according to the present disclosure receives a Physical Protocol Data Unit (PPDU) from a transmitting station (STA); obtains control information related to channelization in a 6 GHz band by decoding the PPDU; and decodes a data field of the PPDU based on the control information.

The technical features of the present disclosure may be implemented based on a computer readable medium (CRM). For example, a CRM according to the present disclosure is at least one computer readable medium including instructions designed to be executed by at least one processor.

The CRM may store instructions that perform operations including receiving a Physical Protocol Data Unit (PPDU) from a transmitting station (STA); obtaining control information related to channelization in a 6 GHz band by decoding the PPDU; and decoding a data field of the PPDU based on the control information. At least one processor may execute the instructions stored in the CRM according to the present disclosure. At least one processor related to the CRM of the present disclosure may be the processor111,121ofFIG.1, the processing chip114,124ofFIG.1, or the processor610ofFIG.11. Meanwhile, the CRM of the present disclosure may be the memory112,122ofFIG.1, the memory620ofFIG.11, or a separate external memory/storage medium/disk.

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

The claims recited in the present specification may be combined in a variety of ways. For example, the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method. In addition, the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method.