Method and apparatus for receiving PPDU in wireless LAN system
By configuring different transmission parameters for each resource unit in the wireless LAN system based on channel conditions, the method enhances transmission efficiency and throughput, addressing the inefficiencies of using common parameters across varying channel conditions.
Patent Information
- Application Number
- PCT/KR2024/004803
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-09
- Filing Date
- 2024-04-11
- Publication Date
- 2024-11-14
AI Technical Summary
In wireless LAN systems, the overall transmission efficiency and throughput decrease when signals are transmitted using common transmission parameters across multiple resource units, especially when channel conditions vary due to OBSS (Overlapping Basic Service Sets) and fading.
A method and device for receiving PPDU in a wireless LAN system that allocates two non-continuous resource units (RUs) and configures different transmission parameters, such as MCS and Nss, for each RU based on channel conditions, using a newly defined RU allocation subfield and user field to apply appropriate Modulation and Coding Schemes and spatial streams.
Improves overall transmission efficiency and throughput by adapting transmission parameters to specific channel states within the MRU, enhancing performance compared to using unified parameters.
Smart Images

Figure KR2024004803_14112024_PF_FP_ABST
Abstract
Description
Method and device for receiving PPDU in a wireless LAN system
[0001] The present specification relates to a technique for receiving a PPDU in a wireless LAN system, and more particularly, to a method and device for configuring a signal field for transmitting data by allocating an MRU composed of two non-continuous RUs and applying different transmission parameters, for example, MCS and Nss, to each RU.
[0002] Wireless local area networks (WLANs) have 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.
[0003] This specification proposes technical features that can be utilized in a new communications standard. For example, the new communications standard could be the Extreme High Throughput (EHT) standard, which is currently under discussion. The EHT standard could utilize newly proposed increased bandwidth, an improved PHY layer protocol data unit (PPDU) structure, improved sequences, and the Hybrid Automatic Repeat Request (HARQ) technique. The EHT standard could also be referred to as the IEEE 802.11be standard.
[0004] New wireless LAN standards may allow for an increased number of spatial streams. This may necessitate improvements to signaling techniques within the wireless LAN system to properly utilize these increased spatial streams.
[0005] This specification proposes a method and device for receiving a PPDU in a wireless LAN system.
[0006] An example of this specification proposes a method for receiving a PPDU.
[0007] The present embodiment can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves the 802.11be system and can satisfy backward compatibility with the 802.11be system.
[0008] This embodiment is performed in a receiving STA, and the receiving STA may correspond to at least one STA (station). The transmitting STA may correspond to an AP (access point).
[0009] The present embodiment proposes a method for allocating an MRU composed of two non-continuous RUs and configuring a signal field for transmitting data by applying different transmission parameters, e.g., MCS and Nss, to each RU. In particular, the present embodiment proposes a method for allocating two non-consecutive RUs within an MRU through a new RU allocation subfield in the signal field and configuring one unified user field for each of the two RUs to indicate the MCS and Nss applied to each RU.
[0010] A receiving STA (station) receives a PPDU (Physical layer protocol data unit) from a transmitting STA.
[0011] The receiving STA decodes the PPDU.
[0012] The above PPDU includes first and second signal fields and a data field.
[0013] The first signal field includes information that the data field is transmitted via a Multiple Resource Unit (MRU) composed of a combination of discontinuous first and second Resource Units (RUs).
[0014] The second signal field includes a common field and a user-specific field. The common field includes RU allocation information for the combination of the discontinuous first and second RUs. The RU allocation information is newly defined information based on the value of the Disregard bit (or reserved bit) of the RU allocation subfield, and a detailed description will be provided later.
[0015] The above user-specific field comprises a single user field integrated for the first and second RUs. The single user field may be configured to include different MCS and Nss information for each RU. For example, the single user field comprises information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU.
[0016] Additionally, the one user field may further include information about the first Nss (Number of spatial streams) applied to the first RU, and the second user field may further include information about the second Nss applied to the second RU.
[0017] Based on the channel status of the first and second RUs, the first RU may be transmitted by applying the first MCS and the first Nss, and the second RU may be transmitted by applying the second MCS and the second Nss. The sum of the first and second Nss may not exceed 8 at most.
[0018] In the past, there was a problem that the overall transmission efficiency and throughput were reduced when transmitting a signal by commonly applying transmission parameters to MRUs even when the channel condition of a specific channel within an MRU was poor due to OBSS, fading, etc. Therefore, in this embodiment, a method is proposed to transmit a signal by applying different transmission parameters to each RU by considering the channel condition of an MRU composed of discontinuous RUs. That is, this embodiment proposes a method of configuring a newly defined RU allocation subfield to apply different MCS and Nss to each RU within an MRU and a single integrated user field for discontinuous RUs.
[0019] According to the embodiment proposed in this specification, by transmitting a signal by applying transmission parameters suitable for the channel condition to each RU within an MRU, there is an effect of improving the overall transmission efficiency and throughput compared to applying common (or unified) transmission parameters to the MRU.
[0020] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.
[0021] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).
[0022] Figure 3 is a diagram illustrating a general link setup process.
[0023] Figure 4 illustrates one embodiment of a multi-link (ML).
[0024] Figure 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.
[0025] Figure 6 is a diagram showing the layout of resource units (RUs) used for 20MHz PPDU.
[0026] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.
[0027] Figure 8 is a diagram showing the layout of resource units (RUs) used for 80MHz PPDU.
[0028] Figure 9 shows the operation according to UL-MU.
[0029] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.
[0030] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.
[0031] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.
[0032] Figure 13 shows an example of a header of a MAC frame.
[0033] FIG. 14 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.
[0034] Figure 15 shows an example of an EHT-SIG content channel for 320 MHz OFDMA transmission.
[0035] Figure 16 shows an example of an EHT-SIG content channel for EHT SU transmission.
[0036] Figure 17 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0037] Figure 18 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0038] Figure 19 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0039] Figure 20 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0040] Figure 21 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0041] Figure 22 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0042] Figure 23 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0043] Figure 24 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0044] Figure 25 shows an example of the RU Allocation subfield defined in an 802.11be wireless LAN system.
[0045] Figure 26 shows the layout of 484+242-tone MRUs in 80MHz bandwidth.
[0046] Figure 27 shows the layout of 996+484-tone MRUs in a 160MHz bandwidth.
[0047] Figure 28 shows the layout of 996+484+242-tone MRU in 160MHz bandwidth.
[0048] Figure 29 shows the layout of 2x996+484-tone MRUs in 320MHz bandwidth.
[0049] Figure 30 shows the layout of 3x996-tone MRUs in a 320 MHz bandwidth.
[0050] Figure 31 shows the layout of 3x996+484-tone MRUs in a 320MHz bandwidth.
[0051] Figure 32 illustrates an example of the NDP Announcement frame format.
[0052] Figure 33 illustrates a procedure for an STA to select an optimal subchannel or RU.
[0053] Figure 34 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.
[0054] Figure 35 is a flowchart illustrating the operation of a receiving device according to the present embodiment.
[0055] Figure 36 is a flowchart illustrating a procedure for transmitting a PPDU according to the present embodiment.
[0056] Figure 37 is a flowchart illustrating a procedure for receiving a PPDU according to the present embodiment.
[0057] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”
[0058] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."
[0059] In this specification, “at least one of A and B” can mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” can be interpreted identically to “at least one of A and B.”
[0060] In addition, parentheses used in this specification may mean “for example.” Specifically, when “control information (UHR-Signal field)” is indicated, the “UHR-Signal field” may be suggested as an example of “control information.” In other words, the “control information” in this specification is not limited to the “UHR-Signal field,” and the “UHR-Signal field” may be suggested as an example of “control information.” In addition, even when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be suggested as an example of “control information.”
[0061] Additionally, as used herein, “a / an” can mean “at least one” or “one or more.” Additionally, terms ending in “(s)” can mean “at least one” or “one or more.”
[0062] Additionally, the expressions “based on” or “on the basis of” or “according to” used herein mean “based at least in part on” and not “based solely on.”
[0063] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.
[0064] The following examples of this specification can be applied to various wireless communication systems. For example, the following examples of this specification can be applied to wireless local area network (WLAN) systems. For example, the present specification can be applied to the IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification can be applied to the Ultra High Reliability (UHR) standard or the next-generation wireless LAN standard that enhances IEEE 802.11bn. In addition, the examples of this specification can be applied to mobile communication systems. For example, the examples of this specification can be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on the 3rd Generation Partnership Project (3GPP) standard.
[0065] In order to explain the technical features of this specification, the technical features to which this specification can be applied are described below.
[0066] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.
[0067] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of the present specification may also be referred to by various names such as a mobile terminal, a wireless device, a Wireless Transmit / Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a Mobile Subscriber Unit, or simply a user. The STA (110, 120) of the present specification may also be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) of the present specification may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.
[0068] For example, STA (110, 120) may perform the role of an AP (access point) or a non-AP role. That is, STA (110, 120) of the present specification may perform the functions of an AP and / or a non-AP. In the present specification, AP may also be indicated as an AP STA.
[0069] The STA (110, 120) of this specification can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard). In addition, the STA of this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. In addition, the STA of this specification can support communication for various communication services such as voice calls, video calls, data communications, and autonomous driving (Self-Driving, Autonomous-Driving).
[0070] In this specification, STA (110, 120) may include a medium access control (MAC) and a physical layer interface for a wireless medium that follow the provisions of the IEEE 802.11 standard.
[0071] Based on the sub-drawing (a) of Fig. 1, STA (110, 120) is described as follows.
[0072] The first STA (110) may include a processor (111), a memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.
[0073] The transceiver (113) of the first STA performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).
[0074] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (112) of the AP can store a signal received through the transceiver (113) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).
[0075] For example, the second STA (120) can perform the intended operation of a non-AP STA. For example, the transceiver (123) of the non-AP performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).
[0076] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (122) of the Non-AP STA can store a signal received through the transceiver (123) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).
[0077] For example, in the specification below, the operation of a device indicated as AP may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is an AP, the operation of the device indicated as AP may be controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). In addition, control information related to the operation of the AP or a transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110). In addition, when the second STA (110) is an AP, the operation of the device indicated as an AP is controlled by the processor (121) of the second STA (120), and a related signal can be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signal of the AP can be stored in the memory (122) of the second STA (110).
[0078] For example, in the specification below, the operation of a device indicated as a non-AP (or User-STA) may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is a non-AP, the operation of the device indicated as a non-AP may be controlled by the processor (121) of the second STA (120), and a related signal may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of a device indicated as a non-AP is controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110).
[0079] In the following specification, devices called (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. without specific drawing symbols may also refer to the STA (110, 120) of FIG. 1. For example, in the example below, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. In addition, in the example below, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation that generates a transmission / reception signal or performs data processing or operation in advance for a transmission / reception signal may include 1) an operation of determining / obtaining / configuring / computing / decoding / encoding bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU, 2) an operation of determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 3) an operation of determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (112, 122) of FIG. 1.
[0080] The device / STA of the sub-drawing (a) of the above-described FIG. 1 can be modified as in the sub-drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of the present specification will be described based on the sub-drawing (b) of FIG. 1.
[0081] For example, the transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the transceiver illustrated in sub-drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) illustrated in sub-drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (a) of FIG. 1 described above.
[0082] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, user STA, network, Base Station, Node-B, Access Point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.
[0083] For example, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal being received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1 being acquired by a processor (111, 121) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 being acquired by a processing chip (114, 124) illustrated in sub-drawing (b) of FIG.
[0084] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.
[0085] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or an enhanced processor thereof.
[0086] In this specification, uplink may mean a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packet / signal, etc. may be transmitted through the uplink. In addition, in this specification, downlink may mean a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packet / signal, etc. may be transmitted through the downlink.
[0087] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).
[0088] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.
[0089] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.
[0090] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter, BSS). The BSSs (200, 205) are a collection of APs and STAs, such as an access point (AP) 225 and a station (STA1, 200-1), that have successfully synchronized and can communicate with each other, and are not a concept that designates a specific area. The BSS (205) may also include one or more STAs (205-1, 205-2) that can be associated with one AP (230).
[0091] A BSS may include at least one STA, an AP (225, 230) providing a distribution service, and a distribution system (DS, 210) connecting multiple APs.
[0092] A distributed system (210) can connect multiple BSSs (200, 205) to implement an extended service set (ESS, 240). An ESS (240) can be used as a term to indicate a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) can have the same SSID (service set identification).
[0093] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).
[0094] In a BSS such as the upper part of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network and perform communication between STAs without an AP (225, 230). A network that establishes a network and performs communication between STAs without an AP (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).
[0095] The bottom of Figure 2 is a conceptual diagram showing IBSS.
[0096] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and access to the distributed system is not permitted, forming a self-contained network.
[0097] Figure 3 is a diagram illustrating a general link setup process.
[0098] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning by the STA. That is, for the STA to access the network, it must find a network it can join. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning. Scanning methods include active scanning and passive scanning.
[0099] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover which APs exist in the vicinity while moving between channels and waits for a response. A responder transmits a probe response frame to the STA that transmitted the probe request frame in response to the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In a BSS, the AP transmits the beacon frame, so the AP becomes the responder. In an IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not constant. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.
[0100] Although not shown in the example of FIG. 3, the scanning operation can also be performed in a passive scanning manner. An STA performing scanning based on passive scanning can wait for a beacon frame while moving between channels. A beacon frame is one of the management frames in IEEE 802.11. It announces the presence of a wireless network and is periodically transmitted so that the scanning STA can find the wireless network and participate in the wireless network. In the BSS, the AP periodically transmits the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. An STA that receives a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.
[0101] An STA that discovers a network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and the AP responds by transmitting an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.
[0102] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group.
[0103] An STA can transmit an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.
[0104] A successfully authenticated STA may perform an association process based on step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and the AP transmits an association response frame to the STA in response. For example, the association request frame may include information related to various capabilities, such as a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, and interworking service capabilities. For example, the association response frame may contain information related to various capabilities, status codes, Association ID (AID), supported rates, Enhanced Distributed Channel Access (EDCA) parameter sets, Received Channel Power Indicator (RCPI), Received Signal to Noise Indicator (RSNI), mobility domains, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS maps, etc.
[0105] In step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame.
[0106] Figure 4 illustrates one embodiment of a multi-link (ML).
[0107] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate over a remote link. The MLDs can be categorized into AP MLDs including multiple AP STAs and non-AP MLDs including multiple non-AP STAs. That is, the AP MLD can include affiliated APs (i.e., AP STAs), and the non-AP MLD can include affiliated STAs (i.e., non-AP STAs, or user-STAs).
[0108] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be allocated to the first and second links. The first and second multilinks may be identified through a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the second link may be configured in different bands.
[0109] The AP MLD of FIG. 4 includes three affiliated APs. In the example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In the example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Furthermore, in the example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Furthermore, in the example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.
[0110] In the example of FIG. 4, AP1 may initiate a multi-link setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In the example of FIG. 4, non-AP STA1 may transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the AP illustrated in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the STA (i.e., user-STA or non-AP STA) illustrated in FIG. 1 and / or FIG. 2.
[0111] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.
[0112] Figure 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.
[0113] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) of the present specification can transmit and / or receive the PPDU of FIG. 5. The PPDU described in the present specification may have, for example, the structure of FIG. 5. In addition, the PPDU described in the present specification may be called by various names such as a transmission PPDU, a reception PPDU, a first type PPDU, or an Nth type PPDU, etc. The PPDU described in the present specification can be used in a WLAN system defined according to IEEE 802.11bn and / or a next-generation WLAN system that improves IEEE 802.11bn.
[0114] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of a single-user (SU) mode / type / transmission, a multi-user (MU) mode / type / transmission, and a null data packet (NDP) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the Data field illustrated may be omitted. If the PPDU of FIG. 5 is used for a trigger-based (TB) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU with the UHR-SIG omitted in the example of FIG. 5.
[0115] In FIG. 5, L-STF or UHR-LTF may be called a preamble or physical preamble, and may be generated / transmitted / received / acquired / decoded in the physical layer (included in the transmitting / receiving STA).
[0116] Each block illustrated in Fig. 5 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 5, L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.
[0117] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in FIG. 5 may be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields may be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields may be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields may be expressed in units of 78.125 kHz.
[0118] In the PPDU of Fig. 5, L-LTF and L-STF may be identical to conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).
[0119] The L-SIG field of FIG. 5 may include, for example, 24 bits of bit information. For example, the 24 bits of information may include a 4 bit Rate field, a 1 bit Reserved bit, a 12 bit Length field, a 1 bit Parity bit, and a 6 bit Tail bit. For example, the 12 bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12 bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU or UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is a HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High-Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in an UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.
[0120] For example, (non-AP and AP) STAs can apply BCC encoding based on a code rate of 1 / 2 to the 24 bits of information in the L-SIG field. Then, the transmitting STA can obtain 48 BCC coded bits. BPSK modulation can be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarriers {subcarrier index -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols can be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can additionally map the signal {-1, -1, -1, 1} to the subcarrier indices {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.
[0121] For example, (non-AP and AP) STA can generate RL-SIG, which is generated in the same manner as L-SIG. BPSK modulation can be applied to RL-SIG. Receiving (non-AP and AP) STA can determine whether the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of RL-SIG. In other words, if RL-SIG is present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of HE PPDU, EHT PPDU, or UHR PPDU. In other words, if RL-SIG is not present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.
[0122] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be called by various names such as the first SIG field, the first SIG, the first type SIG, the control signal, the control signal field, the first (type) control signal, the common control field, and the common control signal.
[0123] A U-SIG can contain N bits of information and can include information for identifying the type of EHT PPDU. For example, a U-SIG can be formed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., an OFDM symbol) for a U-SIG can have a duration of 4 microseconds. Each symbol of a U-SIG can be used to transmit 26 bits of information. For example, each symbol of a U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.
[0124] For example, A bit information (e.g., 52 uncoded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bits of information (e.g., 26 uncoded bits) out of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bits of information (e.g., 26 uncoded bits) out of the total A bit information. For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52 coded bits, and perform interleaving on the 52 coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols allocated to each U-SIG symbol. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) excluding the pilot tones -21, -7, +7, and +21.
[0125] For example, A bit information (e.g., 52 uncoded bits) transmitted by U-SIG may include a CRC field (e.g., a 4-bit long field) and a tail field (e.g., a 6-bit long field). The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits excluding the CRC / tail field within the second symbol, and may be generated based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of the convolutional decoder and may be set to, for example, "000000".
[0126] The A bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits can be assigned only to the first symbol of the U-SIG, or the version-independent bits can be assigned to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.
[0127] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.
[0128] In other words, when the (AP / non-AP) STA transmits an EHT PPDU, it can set the 3-bit PHY version identifier to the first value. In other words, the receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is an UHR PPDU based on the PHY version identifier having the second value.
[0129] For example, the version-independent bits of U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field relates to UL communication, and the second value of the UL / DL flag field relates to DL communication.
[0130] For example, the version-independent bits of U-SIG may include information about the length of a transmission opportunity (TXOP) and information about the BSS color ID.
[0131] For example, if a UHR PPDU is classified into various types (e.g., a type related to SU transmission (performed based on UL or DL), a type related to DL transmission, a type related to NDP transmission, a type related to DL non-MU-MIMO, a type related to DL MU-MIMO, a type related to Multi-AP operation, a type related to CBF (Coordinated beamforming), SR (Spatial Reuse), a type related to C-OFDMA (Coordinated OFDMA), a type related to C-TDMA (Coordinated TDMA)), information about the type of the EHT PPDU (e.g., 2-bit or 3-bit information) can be included in the version-dependent bits of the U-SIG.
[0132] For example, a U-SIG may include information about 1) a bandwidth field including information about a bandwidth, 2) a field including information about an MCS technique applied to the UHR-SIG, 3) an indication field including information about whether a dual subcarrier modulation (DCM) technique is applied to the UHR-SIG, 4) a field including information about the number of symbols used for the UHR-SIG, 5) a field including information about whether the UHR-SIG is generated over the entire band, 6) a field including information about the type of UHR-LTF / STF, and 7) a field indicating the length of the UHR-LTF and the CP length.
[0133] Preamble puncturing may be applied to the PPDU of FIG. 5. Preamble puncturing refers to applying puncturing to a portion of the entire bandwidth of the PPDU (e.g., the secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.
[0134] For example, the pattern of preamble puncturing can be preset. For example, when the first puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when the second puncturing pattern is applied, puncturing can be applied only to one of the two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when the third puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, a primary 40 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band) may be present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.
[0135] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.
[0136] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIGs may be individually configured in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may have a first U-SIG configured for the first 80 MHz frequency block and a second U-SIG configured for the second 80 MHz frequency block. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information about a 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern). Meanwhile, the UHR-SIG consecutive to the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern), and the UHR-SIG consecutive to the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about a preamble puncturing pattern).
[0137] Additionally or alternatively, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).
[0138] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding 80 MHz bandwidth can contain different U-SIGs per 80 MHz.
[0139] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted via at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.
[0140] UHR-SIG provides additional signals to the U-SIG field to enable STAs to interpret / decode UHR PPDUs. The UHR-SIG field may contain U-SIG overflow bits that are common to all users. The UHR-SIG field also contains resource allocation information, allowing STAs to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).
[0141] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on RUs (resource units) defined by multiple subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through RUs (resource units) defined by multiple subcarriers / tones.
[0142] FIG. 6 is a diagram illustrating the layout of resource units (RUs) used for a 20 MHz PPDU. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.
[0143] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for a receiving station, i.e., a user.
[0144] Meanwhile, the RU arrangement of FIG. 6 is utilized not only in a situation for multiple users (MUs) but also in a situation for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of FIG. 4, in which case three DC tones can be inserted.
[0145] In the example of Fig. 6, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are proposed. Since the specific sizes of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be represented as N-tone RU, etc. For example, 26-RU may be represented as 26-tone RU.
[0146] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.
[0147] As in the example of Fig. 6 where RUs of various sizes were used, the example of Fig. 7 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.
[0148] Additionally, as illustrated, 484 RUs may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.
[0149] Figure 8 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of resource units (RUs) used in this specification may vary. For example, the layout of resource units (RUs) used in the 80MHz band may vary.
[0150] Figure 9 illustrates an operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) may perform channel access through contending (i.e., backoff operation) and transmit a trigger frame (930). That is, the transmitting STA (e.g., AP) may transmit a PPDU including a trigger frame (930). When a PPDU including a trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.
[0151] TB PPDUs (941, 942) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (930). The ACK frame (950) for the TB PPDU can be implemented in various forms.
[0152] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.
[0153] The 2.4 GHz band may be referred to by other names, such as the first band (band). Furthermore, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency between 2.4 and 2.5 GHz) are used / supported / defined.
[0154] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned channel index N may be (2.407 + 0.005*N) GHz. The channel indices may be referred to by various names, such as channel numbers. The specific numerical values of the channel indices and center frequencies may change.
[0155] Figure 10 exemplarily illustrates four channels within the 2.4 GHz band. The illustrated first frequency region (1010) to fourth frequency region (1040) may each include one channel. For example, the first frequency region (1010) may include channel 1 (a 20 MHz channel having an index of 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency region (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency region (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.
[0156] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.
[0157] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with center frequencies greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 are subject to change.
[0158] Multiple channels within the 5 GHz band include Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency ranges called UNII Mid and UNII-2Extended. UNII-3 may be referred to as UNII-Upper.
[0159] Within the 5 GHz band, multiple channels can be configured, and the bandwidth of each channel can be variously configured, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range can be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range can be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range can be divided into one channel through a 160 MHz frequency domain.
[0160] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.
[0161] The 6 GHz band may also be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, or defined. The specific figures shown in Figure 12 are subject to change.
[0162] For example, the 20 MHz channel of FIG. 12 can be defined from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 can have an index of 1 (or channel index, channel number, etc.), and a center frequency of 5.945 GHz can be assigned. That is, the center frequency of the indexed channel N can be determined as (5.940 + 0.005*N) GHz.
[0163] Accordingly, the indexes (or channel numbers) of the 20 MHz channels of FIG. 12 are 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, It can be 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule mentioned above, the indices of the 40 MHz channels in Fig. 12 can be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.
[0164] Below, the structure and types / subtypes of MAC frames are described.
[0165] Fig. 13 illustrates an example of a header of a MAC frame. As illustrated, the MAC frame may include a frame control field / information of 2 octets in length, a duration field / information of 2 octets in length, a RA (Receiver Address) field / information of 6 octets in length, and a TA (Transmitter Address) field / information of 6 octets in length. As illustrated in Fig. 13, the four fields may be consecutive to each other. The MAC header of Fig. 13 may be modified in various ways, and a new field may be inserted between the four illustrated fields, or at least one of the illustrated fields may be omitted.
[0166] The MAC header illustrated in Fig. 13 may be positioned at the very front of a MAC frame. That is, the MAC frame may include a MAC header as illustrated in Fig. 13 and MAC body fields / information subsequent to the MAC header. The MAC frame including the MAC header of Fig. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) illustrated in Fig. 5.
[0167] The MAC frames included in the data field of the PPDU of this specification can be classified into various types. For example, the MAC frames of this specification can be classified into control frames, management frames, and data frames.
[0168] For example, the management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLAN. For the management frame, the values of the type fields (B3 and B2) in FIG. 13 are set to 00. In addition, the values of the subtype fields (B7, B6, B5, B4) in FIG. 13 are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).
[0169] For example, the control frame includes Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLAN. For the control frame, the value of the type field (B3 and B2) in FIG. 13 is set to 01. Also, the values of the subtype fields (B7, B6, B5, B4) of FIG. 13 are as follows: Trigger (0010), Beamforming Report Poll (0100), NDP Announcement (0101), Control Frame Extension (0110), Control Wrapper (0111), BlockAckReq (1000), BlockAck (1001), PS-Poll (1010), RTS (1011), CTS (1100), Ack (1101), CF-End (1110).
[0170] For example, the data frame includes (QoS) Data, (QoS) Null, etc. defined in conventional WLAN. For the management frame, the value of the type field (B3 and B2) of Fig. 13 is set to 10.
[0171] The MAC frame / signal used in this specification can be identified through the type field / information and subtype field / information described above. For example, “frame” in this specification can mean a MAC frame in which the type bits B3 and B2 bits in the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 bits in the frame control field are set to 0010. Various MAC frames described in this specification are inserted / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDUs).
[0172] FIG. 14 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.
[0173] The devices (e.g., AP STA, non-AP STA) illustrated in FIGS. 1 to 4 may be modified as illustrated in FIG. 14. The transceiver (630) of FIG. 14 may be identical to the transceivers (113, 123) of FIG. 1. The transceiver (630) of FIG. 14 may include a receiver and a transmitter.
[0174] The processor (610) of FIG. 14 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (610) of FIG. 14 may be identical to the processing chip (114, 124) of FIG. 1.
[0175] The memory (150) of FIG. 14 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (150) of FIG. 14 may be a separate external memory different from the memory (112, 122) of FIG. 1.
[0176] Referring to FIG. 14, a power management module (611) manages power to a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.
[0177] Referring to FIG. 14, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related input to be used by the processor (610).
[0178] Below, the EHT-SIG field applicable to this specification is described.
[0179] The EHT-SIG field provides additional signaling to the U-SIG field to enable STAs to interpret the EHT MU PPDU. In an EHT MU PPDU, the EHT-SIG field contains U-SIG overflow bits common to all users. The EHT-SIG field further contains resource allocation information that allows STAs to query the corresponding resources to be used in the EHT modulated field of the PPDU. The integer fields of the EHT-SIG field are transmitted in unsigned binary format (LSB first), where the least significant bit (LSB) is in the lowest bit position.
[0180] The EHT-SIG field of a 20MHz EHT MU PPDU contains one EHT-SIG content channel. For OFDMA transmission and non-OFDMA transmission for multiple users, the EHT-SIG field of a 40MHz or 80MHz EHT MU PPDU contains two EHT-SIG content channels.
[0181] For OFDMA transmissions and non-OFDMA transmissions for multiple users, the EHT-SIG field of an EHT MU PPDU that is 160 MHz or wider contains two EHT-SIG content channels per 80 MHz frequency subblock. When the bandwidth of an EHT MU PPDU for OFDMA transmission is wider than 80 MHz, the EHT-SIG content channels per 80 MHz frequency subblock may carry different information. The EHT-SIG field of an EHT SU transmission or the EHT-SIG field of an EHT sounding NDP contains one EHT-SIG content channel, which is duplicated for each non-punctured 20 MHz subchannel when the EHT PPDU is 40 MHz or wider.
[0182] Figure 15 shows an example of an EHT-SIG content channel for 320 MHz OFDMA transmission.
[0183] Figure 16 shows an example of an EHT-SIG content channel for EHT SU transmission.
[0184] For OFDMA transmission, the common field of the EHT-SIG content channel contains information about resource unit allocation, such as RU allocation to be used in the EHT modulated field of the PPDU, RU allocated to MU-MIMO, and the number of users in the MU-MIMO allocation. The common field consists of one or two common encoding blocks.
[0185] In non-OFDMA transmissions, the common field of the EHT-SIG content channel does not include the RU allocation subfield. For non-OFDMA transmissions, excluding EHT sounding NDP, the common field of the EHT-SIG content channel is encoded together with the first user field, and this encoding block contains the CRC and Tail, which is called the common encoding block.
[0186] The user-specific field combinations of the EHT-SIG content channel contain information on how to decode the payload for all users of the PPDU.
[0187] The common field for the above OFDMA transmission includes an RU Allocation subfield.
[0188] The RU Allocation-A subfield located at B17-B16+9N in the above common field is defined as follows. N RU Allocation-A subfields exist in the EHT-SIG content channel, and N is set to 1 when the bandwidth field of the U-SIG field is 0 or 1, and N is set to 2 when the bandwidth field of the U-SIG field is 2, 3, 4, or 5.
[0189] Each RU Allocation-A subfield of an EHT-SIG content channel corresponding to a 20 MHz frequency subchannel indicates an RU or MRU allocation, including the size of the RU or MRU and its arrangement in the frequency domain.
[0190] Each Allocation-A subfield also indicates the information necessary to calculate the number of users assigned to each of these RUs or MRUs.
[0191] In the above common field, the RU Allocation-B subfield located at B27+9N-B26+9N+9M is defined as follows. When the bandwidth subfield of the U-SIG field indicates a 160MHz, 320MHz-1 or 320MHz-2 EHT MU PPDU, M RU Allocation-B subfields are present in the EHT-SIG content channel. Here, M is equal to 2 or 6 as follows. When the bandwidth field of the U-SIG field is 3, M is set to 2. When the bandwidth field of the U-SIG field is 4 or 5, M is set to 6.
[0192] Each RU Allocation-B subfield of the EHT-SIG content channel corresponding to a 20 MHz frequency subchannel indicates an RU or MRU allocation, including the size of the RU or MRU and its arrangement in the frequency domain. It is used in the EHT modulated field of the EHT MU PPDU in the frequency domain.
[0193] Each RU Allocation-B subfield also indicates the information necessary to calculate the number of users allocated to each of these RUs or MRUs.
[0194] Figures 17 to 25 illustrate examples of RU Allocation subfields defined in an 802.11be wireless LAN system.
[0195] The mapping from the 9-bit RU Allocation subfield to the RU allocation and the number of User fields per RU or MRU contributed to the User Specific field of the same EHT-SIG content channel as the RU Allocation subfield are defined in FIGS. 19 to 27.
[0196] Referring to FIGS. 17 to 25, when the value of the RU Allocation subfield is from 0 to 303, it indicates an allocation pattern of a specific RU or MRU, and when the value of the RU Allocation subfield is from 304 to 511, it is set to Disregard.
[0197] Large size MRUs defined in DL and UL non-OFMDA transmissions are as follows:
[0198] : 484+242-tone MRU, 996+484-tone MRU, 996+484+242-tone MRU, 2×996+484-tone MRU, 3×996-tone MRU, and 3×996+484-tone MRU
[0199] Large size MRU defined in DL and UL OFMDA transmissions is as follows:
[0200] : 484+242-tone MRU, 996+484-tone MRU, 2×996+484-tone MRU, 3×996-tone MRU, and 3×996+484-tone MRU (i.e., 996+484+242-tone MRU is defined only for non-OFDMA transmissions)
[0201] Figure 26 shows the layout of 484+242-tone MRUs in 80MHz bandwidth.
[0202] Referring to FIG. 26, for non-OFDMA 80MHz EHT PPDU, 484+242 tone MRU is defined only when 20MHz subchannel is punctured. 484+242 tone MRU is obtained by combining 484 tone RU and 242 tone RU in non-OFDMA 80MHz EHT PPDU. The data subcarrier of 484+242 tone MRU is composed of the data subcarriers of 484 tone RU and 242 tone RU that make up 484+242 tone MRU. The pilot subcarrier of 484+242 tone MRU is composed of the pilot subcarriers of 484 tone RU and 242 tone RU that make up 484+242 tone MRU. The four 484+242 tone MRUs allowed in a non-OFDMA 80MHz EHT PPDU are shown in Figure 26.
[0203] Figure 27 shows the layout of 996+484-tone MRUs in a 160MHz bandwidth.
[0204] Referring to Figure 27, for non-OFDMA 160MHz EHT PPDU, 996+484 tone MRU is defined only when 40MHz subchannel is punctured. 996+484 tone MRU is obtained by combining 996 tone RU and 484 tone RU in non-OFDMA 160MHz EHT PPDU. The data subcarrier of 996+484 tone MRU is composed of the data subcarriers of 996 tone RU and 484 tone RU that make up 996+484 tone MRU. The pilot subcarrier of 996+484 tone MRU is composed of the pilot subcarriers of 996 tone RU and 484 tone RU that make up 996+484 tone MRU. The four 996+484 tone MRUs allowed in a non-OFDMA 160MHz EHT PPDU are shown in Figure 27.
[0205] Figure 28 shows the layout of 996+484+242-tone MRU in 160MHz bandwidth.
[0206] Referring to Figure 28, for non-OFDMA 160MHz EHT PPDU, 996+484+242 tone MRU is defined only when 20MHz subchannel is punctured. 996+484+242 tone MRU is obtained by combining 996 tone RU, 484 tone RU, and 242 tone RU in non-OFDMA 160MHz EHT PPDU. The data subcarrier of 996+484+242 tone MRU is composed of a set of data subcarriers of 996 tone, 484 tone, and 242 tone RU that constitute 996+484+242 tone MRU. The pilot subcarrier of the 996+484+242-tone MRU is composed of a set of pilot subcarriers of the 996-tone, 484-tone, and 242-tone RUs that make up the 996+484+242-tone MRU. The eight 996+484+242-tone MRUs allowed in a non-OFDMA 160MHz EHT PPDU are shown in Figure 28.
[0207] Figure 29 shows the layout of 2x996+484-tone MRUs in 320MHz bandwidth.
[0208] Referring to FIG. 29, for non-OFDMA 320 MHz EHT PPDU, 2×996+484 tone MRU is defined only when 996-tone RU1 or 996-tone RU4 is punctured and one of the 40 MHz subchannels of the remaining 240 MHz is punctured. 2×996+484 tone MRU is obtained by combining two 996-tone RUs and a 484-tone RU in a non-OFDMA 320 MHz EHT PPDU. The data subcarrier of 2×996+484 tone MRU is formed by combining the data subcarriers of the two 996-tone RUs and the 484-tone RU that constitute 2×996+484 tone MRU. The pilot subcarrier of a 2×996+484 tone MRU is formed by combining the pilot subcarrier of the two 996 tone RUs that make up the 2×996+484 tone MRU and the 484 tone RU. The twelve 2×996+484 tone MRUs allowed in a non-OFDMA 320 MHz EHT PPDU are shown in Figure 29 (2×996+484 tone MRUs allowed in a non-OFDMA 320 MHz EHT PPDU). If any of 2×996+484 tone MRU 1 to 2×996+484 tone MRU 6 is used, the highest 80 MHz frequency subblock in the frequency is punctured. If any of 2×996+484 tone MRU 7 to 2×996+484 tone MRU 12 is used, the lowest 80 MHz frequency subblock in the frequency is punctured.
[0209] Figure 30 shows the layout of 3x996-tone MRUs in a 320 MHz bandwidth.
[0210] Referring to FIG. 30, for non-OFDMA 320MHz EHT PPDU, 3×996-tone MRU is defined only when 80MHz subchannel is punctured. 3×996-tone MRU is obtained by combining three 996-tone RUs in non-OFDMA 320MHz EHT PPDU. The data subcarrier of 3×996-tone MRU is formed by combining the data subcarriers of three 996-tone RUs that constitute 3×996-tone MRU. The pilot subcarrier of 3×996-tone MRU is formed by combining the pilot subcarriers of three 996-tone RUs that constitute 3×996-tone MRU. Four 3×996-tone MRUs allowed in non-OFDMA 320MHz EHT PPDU are shown in FIG. 30.
[0211] Figure 31 shows the layout of 3x996+484-tone MRUs in a 320MHz bandwidth.
[0212] Referring to Fig. 31, for non-OFDMA 320MHz EHT PPDU, 3×996+484 tone MRU is defined only when 40MHz subchannel is punctured. 3×996+484 tone MRU is obtained by combining three 996-tone RUs and 484-tone RUs in non-OFDMA 320MHz EHT PPDU. The data subcarrier of 3×996+484 tone MRU is formed by the union of the data subcarriers of the three 996-tone RUs and the 484-tone RUs that constitute 3×996+484 tone MRU. The pilot subcarrier of 3×996+484 tone MRU is formed by the union of the pilot subcarriers of the three 996-tone RUs and the 484-tone RUs that constitute 3×996+484 tone MRU. The eight 3×996+484 tone MRUs allowed in a non-OFDMA 320MHz EHT PPDU are shown in Figure 31.
[0213] The location of the large size MRU is fixed and defined as follows. Table 1 defines the index of the large size MRU in OFDMA 80MHz PPDU and non-OFDMA 80MHz PPDU.
[0214] MRU typeMRU indexCombinations484+242-tone MRUMRU 1484-tone RU 2 + 242-tone RU 2; [(gap-242-tone RU) - 242-tone RU - 484-tone RU]MRU 2484-tone RU 2 + 242-tone RU 1; [242-tone RU - (gap-242-tone RU) - 484-tone RU]MRU 3484-tone RU 1 + 242-tone RU 4; [484-tone RU - (gap-242-tone RU) - 242-tone RU]MRU 4484-tone RU 1 + 242-tone RU 3; [484-tone RU - 242-tone RU - (gap-242-tone RU)]NOTE 1―gap-242-tone RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242-tone RU indicates that one 20 MHz subchannel corresponding to gap-242-tone RU is punctured and is to help indicate the frequency order of the MRU in an 80 MHz PPDU.NOTE 3―OFDMA transmission, gap-242-tone RU indicates that one 20 MHz subchannel corresponding to gap-242-tone RU is either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within an 80 MHz EHT PPDU.
[0215] Tables 2 to 4 define the indices of large size MRUs in OFDMA 160MHz PPDUs and non-OFDMA 160MHz PPDUs.
[0216] MRU typeMRU indexCombinations484+242-tone MRU (only for OFDMA)MRU 1484-tone RU 2 + 242-tone RU 2; [(gap-242-tone RU) - 242-tone RU -484-tone RU] in lower 80 MHz channelMRU 2484-tone RU 2 + 242-tone RU 1; [242-tone RU - (gap-242-tone RU) - 484-tone RU] in lower 80 MHz channelMRU 3484-tone RU 1 + 242-tone RU 4; [484-tone RU - (gap-242-tone RU) -242-tone RU] in lower 80 MHz channelMRU 4484-tone RU 1 + 242-tone RU 3; [484-tone RU - 242-tone RU - (gap-242-tone RU)] in lower 80 MHz channelMRU 5484-tone RU 4 + 242-tone RU 6; [(gap-242-tone RU) - 242-tone RU -484-tone RU] in upper 80 MHz channelMRU 6484-tone RU 4 + 242-tone RU 5; [242-tone RU - (gap-242-tone RU) -484-tone RU] in upper 80 MHz channelMRU 7484-tone RU 3 + 242-tone RU 8; [484-tone RU - (gap-242-tone RU) - 242-tone RU] in upper 80 MHz channelMRU 8484-tone RU 3 + 242-tone RU 7;[484-tone RU - 242-tone RU - (gap-242-tone RU)] in upper 80 MHz channelNOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484-tone RU are punctured and is to help indicate the frequency order of the MRU in a 160 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 160 MHz EHT PPDU.;
[0217] MRU typeMRU indexCombinations996+484-tone MRUMRU 1996-tone RU 2 + 484-tone RU 2; [(gap-484-tone RU) - 484-tone RU - 996-tone RU]MRU 2996-tone RU 2 + 484-tone RU 1; [484-tone RU - (gap-484-tone RU) - 996-tone RU]MRU 3996-tone RU 1 + 484-tone RU 4; [996-tone RU - (gap-484-tone RU) - 484-tone RU]MRU 4996-tone RU 1 + 484-tone RU 3; [996-tone RU - 484-tone RU - (gap-484-tone RU)]NOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484-tone RU are punctured and is to help indicate the frequency order of the MRU in a 160 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 160 MHz EHT PPDU.
[0218] MRU typeMRU indexCombinations996+484+242-tone MRU (only for non-OFDMA)MRU 1996-tone RU 2 + 484-tone RU 2 + 242-tone RU 2; [(gap-242-tone RU) -242-tone - RU 484-tone RU - 996-tone RU]MRU [242-tone RU - (gap-242-tone RU) - 484-tone RU - 996-tone RU]MRU 3996-tone RU 2 + 484-tone RU 1 + 242-tone RU 4; [484-tone RU - (gap-242-tone RU) - [484-tone RU - 242-tone RU - (gap-242-tone RU) - 996-tone RU]MRU 5996-tone RU 1 + 484-tone RU 4 + 242-tone RU 6; [996-tone RU - (gap-242-tone RU) - 242-tone RU - 484-tone RU]MRU 6996-tone RU 1 + 484-tone RU 4 + 242-tone RU 5; [996-tone RU - 242-tone RU - (gap-242-tone RU) - 484-tone [996-tone RU - 484-tone RU - (gap-242-tone RU) - 242-tone RU]MRU 8996-tone RU 1 + 484-tone RU 3 + 242-tone RU 7;[996-tone RU - 484-tone RU - 242-tone RU - (gap-242-tone RU)]NOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484-tone RU are punctured and is to help indicate the frequency order of the MRU in a 160 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 160 MHz EHT PPDU.;
[0219] 표 5 내지 표 9는 OFDMA 320MHz PPDU 및 non-OFDMA 320MHz PPDU에서 large size MRU의 인덱스를 정의한다.
[0220] MRU typeMRU indexCombinations484+242-tone MRU (only for OFDMA)MRU 1484-tone RU 2 + 242-tone RU 2; [(gap-242-tone RU) - 242-tone RU -484-tone RU] in lower 80 MHz channel in lower 160 MHzMRU 2484-tone RU 2 + 242-tone RU 1; [242-tone RU - (gap-242-tone RU) - 484-tone RU] in lower 80 MHz channel in lower 160 MHzMRU 3484-tone RU 1 + 242-tone RU 4; [484-tone RU - (gap-242-tone RU) - 242-tone RU] in lower 80 MHz channel in lower 160 MHzMRU 4484-tone RU 1 + 242-tone RU 3; [484-tone RU - 242-tone RU - (gap-242-tone RU)] in lower 80 MHz channel in lower 160 MHzMRU 5484-tone RU 4 + 242-tone RU 6; [(gap-242-tone RU) - 242-tone RU - 484-tone RU] in upper 80 MHz channel in lower 160 MHzMRU 6484-tone RU 4 + 242-tone RU 5; [242-tone RU - (gap-242-tone RU) -484-tone RU] in upper 80 MHz channel in lower 160 MHzMRU 7484-tone RU 3 + 242-tone RU 8; [484-tone RU - (gap-242-tone RU) - 242-tone RU] in upper 80 MHz channel in lower 160 MHzMRU 8484-tone RU 3 + 242-tone RU 7;[484-tone RU - 242-tone RU - (gap-242-tone RU)] in upper 80 MHz channel in lower 160 MHzMRU 9484-tone RU 6 + 242-tone RU 10; [(gap-242-tone RU) - 242-tone RU - 484-tone RU] in lower 80 MHz channel in upper 160 MHzMRU 10484-tone RU 6 + 242-tone RU 9; [242-tone RU - (gap-242-tone RU) - 484-tone RU] in lower 80 MHz channel in upper 160 MHzMRU 11484-tone RU 5 + 242-tone RU 12; [484-tone RU - (gap-242-tone RU) - 242-tone RU] in lower 80 MHz channel in upper 160 MHzMRU 12484-tone RU 5 + 242-tone RU 11; [484-tone RU - 242-tone RU - (gap-242-tone RU)] in lower 80 MHz channel in upper 160 MHzMRU 13484-tone RU 8 + 242-tone RU 14; [(gap-242-tone RU) - 242-tone RU - 484-tone RU] in upper 80 MHz channel in upper 160 MHzMRU 14484-tone RU 8 + 242-tone RU 13; [242-tone RU - (gap-242-tone RU) - 484-tone RU] in upper 80 MHz channel in upper 160 MHzMRU 15484-tone RU 7 + 242-tone RU 16;[484-tone RU - (gap-242-tone RU) - 242-tone RU] in upper 80 MHz channel in upper 160 MHzMRU 16484-tone RU 7 + 242-tone RU 15; [484-tone RU - 242-tone RU - (gap-242-tone RU)] in upper 80 MHz channel in upper 160 MHzNOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are punctured and is to help indicate the frequency order of the MRU in a 320 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 320 MHz EHT PPDU.;
[0221] MRU typeMRU indexCombinations996+484-tone MRU (only for OFDMA)MRU 1996-tone RU 2 + 484-tone RU 2; [(gap-484-tone RU) - 484-tone RU - 996-tone RU] in lower 160 MHzMRU 2996-tone RU 2 + 484-tone RU 1; [484-tone RU - (gap-484-tone RU) - 996-tone RU] in lower 160 MHzMRU 3996-tone RU 1 + 484-tone RU 4; [996-tone RU - (gap-484-tone RU) - 484-tone RU] in lower 160 MHzMRU 4996-tone RU 1 + 484-tone RU 3; [996-tone RU - 484-tone RU - (gap-484-tone RU)] in lower 160 MHzMRU 5996-tone RU 4 + 484-tone RU 6; [(gap-484-tone RU) - 484-tone RU - 996-tone RU] in upper 160 MHzMRU 6996-tone RU 4 + 484-tone RU 5; [484-tone RU - (gap-484-tone RU) - 996-tone RU] in upper 160 MHzMRU 7996-tone RU 3 + 484-tone RU 8; [996-tone RU - (gap-484-tone RU) - 484-tone RU] in upper 160 MHzMRU 8996-tone RU 3 + 484-tone RU 7; [996-tone RU - 484-tone RU - (gap-484-tone RU)] in upper 160 MHzNOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are punctured and is to help indicate the frequency order of the MRU in a 320 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 320 MHz EHT PPDU.
[0222] MRU typeMRU indexCombinations2×996+484-tone MRUMRU 1996-tone RU 2 + 996-tone RU 3 + 484-tone RU 2; [(gap-484-tone RU) - 484-tone RU - 996-tone RU - 996-tone RU - (gap-996-tone RU)]MRU 2996-tone RU 2 + 996-tone RU 3 + 484-tone RU 1; [484-tone RU - (gap-484-tone RU) - 996-tone RU - 996-tone RU - (gap-996-tone RU)]MRU 3996-tone RU 1 + 996-tone RU 3 + 484-tone RU 4; [996-tone RU - (gap-484-tone RU) - 484-tone RU - 996-tone RU - (gap-996-tone RU)]MRU 4996-tone RU 1 + 996-tone RU 3 + 484-tone RU 3; [996-tone RU - 484-tone RU - (gap-484-tone RU) - 996-tone RU - (gap-996-tone RU)]MRU 5996-tone RU 1 + 996-tone RU 2 + 484-tone RU 6; [996-tone RU - 996-tone RU - (gap-484-tone RU) - 484-tone RU - (gap-996-tone RU)]MRU 6996-tone RU 1 + 996-tone RU 2 + 484-tone RU 5; [996-tone RU - 996-tone RU - 484-tone RU - (gap-484-tone RU) - (gap-996-tone RU)]MRU 7996-tone RU 3 + 996-tone RU 4 + 484-tone RU 4;[(gap-996-tone RU) - (gap-484-tone RU) - 484-tone RU - 996-tone RU - 996-tone RU]MRU 8996-tone RU 3 + 996-tone RU 4 + 484-tone RU 3; [(gap-996-tone RU) - 484-tone RU - (gap-484-tone RU) - 996-tone RU - 996-tone RU]MRU 9996-tone RU 2 + 996-tone RU 4 + 484-tone RU 6; [(gap-996-tone RU) - 996-tone RU - (gap-484-tone RU) - 484-tone RU - 996-tone RU]MRU 10996-tone RU 2 + 996-tone RU 4 + 484-tone RU 5; [(gap-996-tone RU) - 996-tone RU - 484-tone RU - (gap-484-tone RU) - 996-tone RU]MRU 11996-tone RU 2 + 996-tone RU 3 + 484-tone RU 8; [(gap-996-tone RU) - 996-tone RU - 996-tone RU - (gap-484-tone RU) - 484-tone RU]MRU 12996-tone RU 2 + 996-tone RU 3 + 484-tone RU 7;[(gap-996-tone RU) - 996-tone RU - 996-tone RU - 484-tone RU - (gap-484-tone RU)]NOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are punctured and is to help indicate the frequency order of the MRU in a 320 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 320 MHz EHT PPDU.;
[0223] MRU typeMRU indexCombinations3×996-tone MRUMRU 1996-tone RU 2 + 996-tone RU 3 + 996-tone RU 4; [(gap-996-tone RU) - 996-tone RU - 996-tone RU - 996-tone RU]MRU 2996-tone RU 1 + 996-tone RU 3 + 996-tone RU 4; [996-tone RU - (gap-996-tone RU) - 996-tone RU - 996-tone RU]MRU 3996-tone RU 1 + 996-tone RU 2 + 996-tone RU 4; [996-tone RU - 996-tone RU - (gap-996-tone RU) - 996-tone RU]MRU 4996-tone RU 1 + 996-tone RU 2 + 996-tone RU 3; [996-tone RU - 996-tone RU - 996-tone RU - (gap-996-tone RU)]NOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are punctured and is to help indicate the frequency order of the MRU in a 320 MHz PPDU.NOTE 3―OFDMA transmission, gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission, and is to help indicate the frequency order of the MRU within a 320 MHz EHT PPDU.
[0224] MRU typeMRU indexCombinations3×996+484-tone MRUMRU 1996-tone RU 2 + 996-tone RU 3 + 996-tone RU 4 + 484-tone RU 2; [(gap-484-tone RU) - 484-tone RU - 996-tone RU - 996-tone RU - 996-tone RU]MRU 2996-tone RU 2 + 996-tone RU 3 + 996-tone RU 4 + 484-tone RU 1; [484-tone RU - (gap-484-tone RU) - 996-tone RU - 996-tone RU - 996-tone RU]MRU 3996-tone RU 1 + 996-tone RU 3 + 996-tone RU 4 + 484-tone RU 4; [996-tone RU - (gap-484-tone RU) - 484-tone RU - 996-tone RU - 996-tone RU]MRU 4996-tone RU 1 + 996-tone RU 3 + 996-tone RU 4 + 484-tone RU 3; [996-tone RU - 484-tone RU - (gap-484-tone RU) - 996-tone RU - 996-tone RU]MRU 5996-tone RU 1 + 996-tone RU 2 + 996-tone RU 4 + 484-tone RU 6; [996-tone RU - 996-tone RU - (gap-484-tone RU) - 484-tone RU - 996-tone RU]MRU 6996-tone RU 1 + 996-tone RU 2 + 996-tone RU 4 + 484-tone RU 5; [996-tone RU - 996-tone RU - 484-tone RU - (gap-484-tone RU) - 996-tone RU]MRU 7996-tone RU 1 + 996-tone RU 2 + 996-tone RU 3 + 484-tone RU 8;[996-tone RU - 996-tone RU - 996-tone RU - (gap-484-tone RU) - 484-tone RU]MRU 8996-tone RU 1 + 996-tone RU 2 + 996-tone RU 3 + 484-tone RU 7; [996-tone RU - 996-tone RU - 996-tone RU - 484-tone RU - (gap-484-tone RU)]NOTE 1―RU is not part of an MRU and is used to indicate the size of a gap between or beside RUs that form the MRU.NOTE 2―non-OFDMA transmission, . gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are punctured and is to help indicate the frequency order of the MRU in a 320 MHz PPDU.NOTE 3―OFDMA transmission, . gap-242 / 484 / 996-tone RU indicates that one or more 20 MHz subchannels corresponding to gap-242 / 484 / 996-tone RU are either punctured or unassigned or assigned to other RUs or MRUs for data transmission;
[0225] EHT-SIG content channels have 15 minutes to 16 minutes and 0 minutes to go 패딩(있는 경우)으로 구성된다.
[0226] For DL OFDMA transmission (UL / DL fields in the U-SIG field are set to 0, and PPDU Type And Compression Mode field is set to 0), the number of user fields is indicated by the RU Allocation subfield.
[0227] Each non-final user encoding block consists of two user fields containing information about the two STAs used to decode the payload. The final user encoding block contains information about one or two users, depending on the number of user fields in the EHT-SIG content channel.
[0228] For EHT SU transmissions (UL / DL fields in the U-SIG field are set to 0 or 1, PPDU Type And Compression Mode field is set to 1, and EHT-SIG MCS field and Number of EHT-SIG Symbols field are not set to 0 at the same time) and for DL non-OFDMA transmissions for multiple users (UL / DL fields in the U-SIG field are set to 0 and PPDU Type And Compression Mode field is set to 2), the number of users is indicated by the Number Of Non-OFDMA Users subfield.
[0229] The common fields of the EHT-SIG content channel are encoded together with the first user field of the same content channel. This common encoding block contains the CRC and Tail.
[0230] For non-OFDMA transmissions to multiple users, a user encoding block exists if there is more than one user field in the corresponding content channel.
[0231] There are N user fields in a user encoding block, where: If there is only one user in the end-user encoding block, then N=1, otherwise N=2.
[0232] The format of the user field for non-MU-MIMO allocation and the format of the user field for MU-MIMO allocation are each defined.
[0233] The user fields for non-MU-MIMO allocation include the STA-ID subfield, MCS subfield, Reserved subfield, NSS subfield, Beamformed subfield, and Coding subfield. The user fields for MU-MIMO allocation include the STA-ID subfield, MCS subfield, Coding subfield, and Spatial Configuration subfield.
[0234] Below, the NDPA frame used in the NDP sounding procedure is described.
[0235] Figure 32 illustrates an example of the NDP Announcement frame format.
[0236] The NDP Announcement frame has three variants: the VHT NDP Announcement frame, the HE NDP Announcement frame, and the EHT NDP Announcement frame. Each variant is distinguished by the configuration of the HE subfield and the Ranging subfield within the Sounding Dialog Token field.
[0237] The VHT / HE / EHT NDP Announcement frame contains at least one STA Info field. If the VHT / HE / EHT NDP Announcement frame contains only one STA Info field, the RA field is set to the address of an STA that can provide feedback. If the VHT / HE / EHT NDP Announcement frame contains more than one STA Info field, the RA field is set to the broadcast address.
[0238] The TA field is set to the address of the STA transmitting the VHT / HE / EHT NDP Announcement frame or the bandwidth signaling TA of the STA transmitting the VHT / HE / EHT NDP Announcement frame.
[0239] The Resolution subfield of the Partial BW Info subfield indicates the resolution bandwidth for each bit of the Feedback Bitmap subfield. The Feedback Bitmap subfield indicates the request for each resolution bandwidth from the lowest frequency to the highest frequency, with B1 indicating the lowest resolution bandwidth. Each bit of the Feedback Bitmap subfield is set to 1 if feedback is requested for the corresponding resolution bandwidth.
[0240] The Resolution bit indicates the feedback resolution bandwidth. The Resolution bit is set to 0 to indicate a resolution of 20 MHz when the BW subfield is set to 0 through 3, and is set to 1 to indicate a resolution of 40 MHz when the BW subfield is set to 4. The Feedback Bitmap subfield indicates each resolution bandwidth for which the beamformer requests feedback. Each bit in the Feedback Bitmap subfield is set to 1 if feedback is requested for the corresponding bandwidth, and 0 otherwise.
[0241] If the bandwidth of the EHT NDP Announcement frame is less than 320 MHz, the Resolution bit B0 is set to 0 to indicate a resolution of 20 MHz.
[0242] - When the bandwidth of the EHT NDP Announcement frame is 20 MHz, B1 is set to 1 to indicate a feedback request for a 242-tone RU. B2-B8 are reserved and set to 0.
[0243] - When the bandwidth of the EHT NDP Announcement frame is 40 MHz, B1 and B2 indicate feedback requests for each of the two 242-tone RUs, from low to high frequency. B3-B8 are reserved and set to 0.
[0244] - When the bandwidth of the EHT NDP Announcement frame is 80 MHz, B1 to B4 represent feedback requests for each of the four 242-tone RUs, from low frequency to high frequency. B5 to B8 are reserved and set to 0. If B1 to B4 are all set to 1, it represents a feedback request for the 996-tone RU.
[0245] - When the bandwidth of the EHT NDP Announcement frame is 160 MHz, B1-B8 represent feedback requests for each of the eight 242-tone RUs from low to high frequency. If B1-B4 are all set to 1, it represents a feedback request for the lower 996-tone RU, and if B5-B8 are all set to 1, it represents a feedback request for the upper 996-tone RU.
[0246] When the bandwidth of the EHT NDP Announcement frame is 320 MHz, the Resolution bit B0 is set to 1 to indicate a resolution of 40 MHz. B1 through B8 represent feedback requests for each of the eight 484-tone RUs from low to high frequency. When B1 and B2 are both set to 1, it represents a feedback request for the lowest 996-tone RU, when B3 and B4 are both set to 1, it represents a feedback request for the second-lowest 996-tone RU, when B5 and B6 are both set to 1, it represents a feedback request for the second-highest 996-tone RU, and when B7 and B8 are both set to 1, it represents a feedback request for the highest 996-tone RU.
[0247] The sounding protocol can be described as follows. Since the standardization stage has not yet been finalized, the sounding protocol described below was written for EHT wireless LAN systems, but it can also be applied to UHR wireless LAN systems or next-generation wireless LAN systems.
[0248] Transmit beamforming and Downlink Multi-User-Multi-Input-Multi-Output (DL MU-MIMO) require knowledge of the channel state to compute a steering matrix applied to the transmitted signal to optimize reception at one or more receivers. The EHT STA determines the channel state information using the EHT sounding protocol. The EHT sounding protocol provides an explicit feedback mechanism, defined as EHT non-trigger-based (non-TB) sounding and EHT trigger-based (TB) sounding. Here, the EHT beamformee measures the channel using training signals transmitted by the EHT beamformer (i.e., the EHT sounding NDP) and sends back a transformed estimate of the channel state. The EHT beamformer uses this estimate to derive the steering matrix.
[0249] EHT Beamformer returns an estimate of the channel state from an EHT compressed Beamforming / CQI report contained in one or more EHT Compressed Beamforming / CQI frames. There are three types of EHT compressed Beamforming / CQI reports.
[0250] - SU Feedback: EHT Compression Beamforming / CQI report consists of EHT Compression Beamforming report field.
[0251] - MU Feedback: The EHT Compressed Beamforming / CQI report consists of an EHT Compressed Beamforming report field and an EHT MU Exclusive Beamforming report field.
[0252] - CQI Feedback: EHT Compression Beamforming / CQI Reporting consists of an EHT CQI Reporting field.
[0253] Note that the use of EHT TB sounding does not necessarily imply MU feedback. EHT TB sounding is also used to obtain SU feedback and CQI feedback.
[0254] <Embodiments applicable to this specification>
[0255] In 802.11be, MRU is defined by considering various preamble puncturing patterns and channel conditions in SU / MU transmission to efficiently use wide bandwidth (up to 320MHz). The channel status of each subchannel within a large-size MRU allocated to an STA may be different. In this case, the STA can indicate information about subchannels with good channel conditions when receiving a signal, and the AP can improve overall transmission efficiency by allocating the optimal subchannel or RU to the STA and applying high MCS and high Nss to transmit the signal. In this specification, we propose a method of transmitting a signal by allocating a unified RU or multiple RUs within the BW by considering the optimal subchannel or RU for the STA when transmitting a signal to a non-AP STA / AP.
[0256] Considering backward compatibility, an 802.11be MU-PPDU for transmitting signals to multiple STAs may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG, EHT-STF, EHT-LTF, and Data.
[0257] A U-SIG may contain version independent fields and version dependent fields.
[0258] The version independent field may include a 3-bit version identifier indicating the Wi-Fi version after 802.11be and 802.11be, a 1-bit DL / UL field, BSS color, TXOP duration, etc., and the version dependent field may include information such as PPDU format type, bandwidth, and MCS.
[0259] U-SIG is a jointly encoded two-symbol U-SIG, consisting of 52 data tones and 4 pilot tones every 20MHz. In addition, U-SIG is modulated in the same way as HE-SIG-A of 802.11ax (i.e., modulated with BPSK 1 / 2 code rate).
[0260] EHT-SIG can be divided into common fields and user-specific fields, and can be encoded with variable MCS. The common field can indicate information about the spatial stream and RU being used, and the user-specific field can indicate information ID, MCS, and coding information used for a specific user or STA.
[0261] Additionally, EHT-SIG can be composed of different information in 80MHz units, and within 80MHz, it is composed of two EHT-SIG content channels (EHT-SIG CC1 and EHT-SIG CC2).
[0262] 1. Procedure for selecting the best subchannel (optimal channel) or RU in a non-AP STA in a wireless LAN system
[0263] In UHR or next-generation wireless LAN systems, measurements are made on the best subchannel or RU from the STA perspective in order to transmit signals using the optimal subchannel or RU for each STA.
[0264] - In this case, the size of the subchannel or RU being measured has a minimum size of 242 ton RU / 20MHz. That is, the size of the subchannel or RU for measuring the best subchannel or RU size can be configured as 242 / 484 / 996 ton RU or 20 / 40 / 80MHz.
[0265] - Measurement of the best subchannel or RU for signal transmission can be performed at the request of the AP or during channel sounding.
[0266] When performed by an AP request, it can be performed by a procedure such as that in Fig. 33, for example.
[0267] Figure 33 illustrates a procedure for an STA to select an optimal subchannel or RU.
[0268] As shown in the example in Fig. 33, in order to measure the best subchannel or RU for STA(s), the AP transmits a request frame for measuring this to the STA(s).
[0269] In this case, the request frame is composed of a Best channel measurement request subfield, a BW subfield, a Puncturing information or disallowed subchannel information subfield, and a User info subfield.
[0270] The best channel measurement request subfield can consist of 1 bit and instructs the STA to perform best channel measurement.
[0271] The BW subfield contains information about the BW over which the NDP (Null Data Packet) performing channel measurement is transmitted, and is set to 20 / 40 / 80 / 160 / 320 MHz.
[0272] The Puncturing information or disallowed subchannel information subfield indicates information about available channels within the BSS (Basic Service Set).
[0273] The Best channel measurement information subfield consists of the Subchannel resolution size and the subchannel bitmap, and is structured as follows:
[0274] The above Subchannel resolution size can be configured as 242 / 484 tone RU or 20 / 40MHz.
[0275] For example, the Best channel measurement information subfield may be configured as a 9-bit table (1-bit resolution, 8-bit best channel indication).
[0276] The 8-bit best channel indication is indicated for 80 / 160 / 320MHz and is configured as follows for each BW.
[0277] 1) 80MHz - 4bit (indicated in 242-tone RU units, LSB (Least Significant Bit) or last 4bits are reserved)
[0278] 2) 160MHz - 8bit (indicated in 242-tone RU units) or 484-tone RU units can also be indicated.
[0279] 3) 320MHz - 8bit (indicated in 484-ton RU units / 996-ton RU units), if 996-ton RU is used as the resolution, the LSB or last 4bits are reserved.
[0280] In another embodiment, the Best channel measurement information subfield may be fixed to a specific RU size for each BW. In this embodiment, the Best channel measurement information subfield does not require information indicating the resolution size, and its value is determined according to the BW.
[0281] For example, the resolution size is fixed to 242 ton RU at 80 MHz, 484 ton RU at 160 MHz, and 996 ton RU at 320 MHz. In other words, since it is fixed to a specific size according to BW, separate signaling is not required. The Best channel measurement information subfield includes a Channel bitmap, and the Channel bitmap consists of 4 bits, and each bit represents a subchannel or RU corresponding to the resolution size.
[0282] An STA (or non-AP STA) that receives a request frame transmitted by an AP receives the request frame and, after SIFS, transmits a response frame using the allocated RU. In this case, the response frame transmitted by the STA is composed of AID12 and a status code. The status code indicates success or denial in response to the received request.
[0283] The CTS or CTS-to-self frame can be used as the above response frame.
[0284] Unlike the above, the response frame for the request may be omitted in the procedure of FIG. 33.
[0285] The AP that receives the response frame from the STA(s) transmits the NDP using the BW indicated in the request frame.
[0286] The STA(s) that received the NDP from the AP performs measurements on the subchannel or RU using the channel measurement information included in the request information and selects the best subchannel or RU.
[0287] The AP sends a Trigger frame to the STA to request information about the best subchannel or RU selected by the STA based on the NDP reception.
[0288] An STA that receives a request for information about the best subchannel or RU from an AP transmits information about the selected best subchannel or RU to the AP using the allocated RU.
[0289] 2. How to instruct non-continuous RU combinations to non-AP STAs
[0290] This embodiment describes an MRU allocated for data transmission in a wireless LAN system.
[0291] As in the above-described embodiment, the AP can receive preferred channel or optimal channel information from the non-AP STA and consider the information and channel conditions when transmitting a signal. Therefore, if the SNR for a specific RU size within the MRU defined by the channel condition or interference is very poor from the non-AP STA side, making it difficult to use the existing defined MRU or reducing transmission efficiency, a signal can be transmitted by allocating multiple RUs spaced apart from each other within the BW, and RUs with a size of 242 tones or more can be allocated to one STA as follows.
[0292] Signal transmission through multiple RU allocation can be applied to a BW of 80 MHz or more based on information about the subchannel or large size RU (information about the best subchannel or RU in the previous embodiment).
[0293] The above multiple RU allocation transmission is used in MU (Multi User) transmission or OFDMA transmission.
[0294] The AP can transmit and receive signals by applying different transmission parameters for each RU based on the channel status of each assigned RU. Differently configured transmission parameters can include the Modulation and Coding Scheme (MCS), Number of Spatial Streams (NSS), and coding.
[0295] Considering the resolution size for the above optimal channel measurement, the RU size used for transmission using multiple RUs at 80 / 160 / 320 MHz can be defined as follows.
[0296] BW80MHz160MHz320MHzAllocated RU size242484996
[0297] Considering the allocated RU size in Table 10 above, the RU allocation allocated for multiple RU transmission in a BW of 80 MHz or more can be configured as follows. The RU allocation combination proposed below is not included in the MRU combination defined in 802.11be and is considered to be allocated non-continuously.
[0298] 1) 80MHz - Allocated based on 242 tone RU, and allocated RUs are not consecutive to each other.
[0299] - 242-tone RU+242-tone RU (1x1x / 1xx1 / x1x1)
[0300] - The part marked as 1 above represents the 242 tone RU allocated within 80MHz, and the part marked as x represents the unallocated 242 tone RU.
[0301] 2) 160MHz - allocated based on 484 tone RU.
[0302] - 484-tone RU + 484-tone RU (2 x 2 x / 2 xx 2 / x 2 x 2)
[0303] - The part marked as 2 above represents the 484 tone RU allocated within 160MHz, and the part marked as x represents the unallocated 484 tone RU.
[0304] 3) 320MHz - allocated based on 996 tone RU.
[0305] - 996-tone RU + 996-tone RU (3 x 3 x / 3 xx 3 / x 3 x 3)
[0306] - The part marked as 3 above represents 996 tone RUs allocated within 320MHz, and the part marked as x represents unallocated 996 tone RUs.
[0307] Two methods can be considered to instruct non-AP STAs about the dis-continuously allocated RU combinations as described above, and in each case, information about multiple allocated RUs is transmitted as follows.
[0308] 1) Method of allocating multiple user fields to one STA using the existing defined RU allocation
[0309] A. As before, the RU allocation subfield is individually indicated for each allocated Multiple RU, and in this case, the User field corresponding to each RU allocation is included.
[0310] i. In this case, a user field is configured for each non-continuous RU within the MRU.
[0311] - The user field assigned to each RU has the same AID (Association Identifier), and in this case, it can be configured by setting different MCS, NSS, and coding.
[0312] - User fields can be configured by reusing previously defined user fields and can be configured to include the following information:
[0313] A. Number of allocated RUs (subfield for)
[0314] i. In the First user field, the corresponding information can be set to the 'total number of allocated RUs - 1'. From the user fields following the First user field, the corresponding information can be set to a number counted by -1. In the Last user field, the corresponding information is set to 0 to indicate that it is the last field.
[0315] ii. The subfield for the above (number of allocated RUs) may consist of 1 / 2 bits.
[0316] B. Remaining user field
[0317] i. For example, the Remaining user field indicates the number of allocated remaining user fields excluding the current user field, and may consist of 2 / 3 bits.
[0318] ii. The Remaining user field is set to a number that sequentially counts -1 for each User field. If the information is set to 0, it means that there are no more user fields, and in this case, the STA no longer performs decoding of the user field.
[0319] iii. The above Remaining user field can be set to 1 / 2 bit.
[0320] C. Indicator for whether it is a Last user field
[0321] i. The indicator for whether it is the Last user field is an indicator for whether the allocated user field is the last field and can be composed of 1 bit. If the indicator is set to 0, it indicates that it is not the last user field. In this case, the STA performs decoding of the user field until it finds a user field in which the AID12 is set to be the same as its own AID12. If the indicator is set to 1, it indicates that it is the last allocated user field, meaning that there are no more allocated user fields, and the STA may no longer perform decoding on the user field.
[0322] D. Directive for More user fields
[0323] i. The indicator for the above More user field indicates whether there are more user fields assigned after the corresponding user field.
[0324] ii. The indicator for the above More user field consists of 1 bit. If the indicator is set to 1, it means that there is an additionally allocated user field, and the STA performs decoding until it finds a user field with AID12 set to the same as its own AID12. In this case, the STA performs decoding of the user field until it finds a user field with the same AID and with the indicator set to 0. If the value of the indicator is set to 0, it indicates that there are no more allocated user fields. In this case, the STA no longer performs decoding of the user field.
[0325] 3. When transmitting and receiving signals using non-continuous multiple RUs, UHR-SIG or next-wifi SIG can be configured to include one of the subfields suggested in A, B, C, and D above.
[0326] ii. For example, when transmitting and receiving signals by allocating multiple RUs at 80MHz, if the allocated 242+242 tone RUs are the first and third 20MHz within 80MHz, each 242 tone RU is indicated through RU allocation subfield 1 and RU allocation subfield 3 included in CC1 and CC2 (content channel 1 and content channel 2) of UHR-SIG, respectively, and at this time, two user fields for the corresponding RU allocation subfield 1 and RU allocation subfield 3 are included in UHR-SIG.
[0327] iii. In this case, the RU allocation subfield for the previously defined 242 tone RU can be used, so there is no need to define a new RU allocation subfield.
[0328] 2) As another example, RU allocation can be newly defined for the non-continuous multiple RUs defined above, and this can be used to indicate multiple RU allocation allocated to a non-AP STA.
[0329] A. The indicator for the newly defined non-continuous multiple RUs is defined using the reserved value (or Disregard bits) of the RU allocation subfield (see Figure 25).
[0330] i. As an example, using reserved values, the RU allocation subfield can be defined as follows:
[0331] RU Allocation subfield (B8 B7 B6 B5 B4 B3 B2 B1 B0)123456789Number of entries.........304 (100110000)Block [1st_242, 3rd_242] within the first, second, third, and fourth 80 MHz frequency subblock in increasing frequency order, respectively1305 (100110001)Block[1st_242, 4th_242] within the first, second, third, and fourth 80 MHz frequency subblock in increasing frequency order, respectively1306 (100110010)Block[2nd_242 ,4th_242] within the first, second, third, and fourth 80 MHz frequency subblock in increasing frequency order, respectively1307 (100110011)Block[1st_484, 3rd_484] within the first and second 160 MHz subblock in increasing frequency order, respectively1308 (100110100)Block[1st_484, 4th_484] within the first and second 160 MHz subblock in increasing frequency order, respectively1309 (100110101)Block[2nd_996, 4th_484] within the first and second 160 MHz subblock in increasing frequency order, respectively1310 (100110110)Block[1st_996,3rd_996] within the 320 MHz1311 (100110111)Block[1st_996, 4th_996] within the 320 MHz1312 (100111000)Block[2nd_996, 4th_996] within the 320 MHz1313 -511 (100111001-111111y2y1y0) Disregard,
[0332] ii. The RU allocation subfield allocated for multiple RUs Allocation specified in Table 11 above is one embodiment and may be defined using another reserved value.
[0333] The following signal transmission can be considered to transmit and receive signals by allocating non-continuous multiple RUs.
[0334] The following signaling can be used to indicate that the AP is performing signal transmission using non-continuous multiple RUs when transmitting MUs.
[0335] - For example, the AP indicates that non-continuous multiple RU allocation is used via U-SIG. For example, the validate or disregards bits of U-SIG included in U-SIG 1 or U-SIG2 may be used, or one of the bits B20-B25 of U-SIG1, B2, B8 of U-SIG2 may be used.
[0336] As another example, it may be indicated using the reserved UL / DL subfield = 0 and PPDU Type And Compression Mode value = 3 among the UL / DL subfield and PPDU Type And Compression Mode field combinations included in U-SIG.
[0337] - In other cases, you can use the contents of the common field of UHR-SIG or Next wifi-SIG to give instructions.
[0338] For example, the common field can be configured to include a bit indicating whether non-continuous multiple RUs are supported, and specifically, the support or presence of non-continuous multiple RUs subfield can be configured to include the bit. At this time, the support or presence of non-continuous multiple RUs subfield consists of 1 bit, and when the bit is set to 1, it indicates that non-continuous multiple RUs are supported, and when the bit is set to 0, it indicates that non-continuous multiple RUs are not supported.
[0339] - You can also give instructions using user specific content rather than the common field mentioned above.
[0340] For example, whether or not to transmit Multiple RUs can be indicated through the user field, and the User field can be configured as follows.
[0341] Based on the RU allocation for the Multiple RU allocation defined as above, the User field can be configured as follows.
[0342] - The user field of UHR-SIG or next wi-fi SIG has a unified format regardless of multiple RU transmission or conventional unified RU / MRU transmission. One User field corresponding to the RU allocation subfield can be configured to include different MCS and NSS information for each RU. That is, the User field can be configured as MCS per RU1, MCS per RU2, Nss per RU1, and Nss per RU2.
[0343] At this time, MCS is supported in the same way as before and can be set to 4 bits. Nss can be flexibly set up to a maximum of 8. For example, if Nss of RU1 is 2, Nss of RU2 can be set to 6.
[0344] In other cases, Nss can be flexibly set within the max value, with a maximum of 4 per block, such as MU-MIMO. In this case, information about the Nss can be composed of 2 bits (e.g., 00 01 10 11).
[0345] When allocating a unified RU in the User field configured as above, MCS1 (MCS per RU1) and NSS1 (Nss per RU1) in the user field are set to the same settings as in the previously defined RU, and at this time, MCS2 (MCS per RU2) and NSS2 (Nss per RU2) are reserved.
[0346] 3) As another example, a method of newly defining the RU allocation subfield newly defined in 2) above (see Table 11) and using it to indicate multiple RU allocations allocated to non-AP STAs, but also configuring a user field for each non-continuous RU (or subchannel) within an MRU can be proposed. (Since a user field is configured for each RU, it is composed of multiple user fields.)
[0347] Figure 34 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.
[0348] An example of FIG. 34 may be performed at a transmitting STA or transmitting device (AP and / or non-AP STA).
[0349] Some of the steps (or detailed sub-steps described below) in the example of Fig. 34 may be omitted or changed.
[0350] Through step S3410, the transmitting device (transmitting STA) can obtain information regarding the aforementioned Tone Plan. As described above, the information regarding the Tone Plan includes the size and location of the RU, control information related to the RU, information regarding the frequency band in which the RU is included, information regarding the STA receiving the RU, etc.
[0351] Through step S3420, the transmitting device can configure / generate a PPDU based on the acquired control information. The step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, step S3420 may include a step of configuring an EHT-SIG field including control information regarding a Tone Plan. That is, step S3420 may include a step of configuring a field including control information indicating the size / position of an RU (e.g., an N bitmap) and / or a step of configuring a field including an identifier (e.g., an AID) of an STA receiving the RU.
[0352] Additionally, step S3420 may include a step of generating an STF / LTF sequence to be transmitted through a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.
[0353] Additionally, step S3420 may include a step of generating a data field (i.e., MPDU) to be transmitted via a specific RU.
[0354] The transmitting device can transmit the PPDU configured through step S3420 to the receiving device based on step S3430.
[0355] While performing step S3430, the transmitting device may perform at least one of operations such as CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion.
[0356] A signal / field / sequence configured according to this specification can be transmitted in the form of FIG. 5.
[0357] Figure 35 is a flowchart illustrating the operation of a receiving device according to the present embodiment.
[0358] The above-described PPDU can be received according to an example of FIG. 35.
[0359] An example of FIG. 35 may be performed at a receiving STA or receiving device (AP and / or non-AP STA).
[0360] Some of the steps (or detailed sub-steps described below) in the example of Fig. 35 may be omitted.
[0361] A receiving device (receiving STA) may receive all or part of a PPDU through step S3510. The received signal may have the form of FIG. 5.
[0362] The sub-step of step S3510 can be determined based on step S3430 of Fig. 34. That is, step S3510 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operations, and GI insert operations applied in step S3430.
[0363] At step S3520, the receiving device can decode all or part of the PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.
[0364] More specifically, the receiving device can 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 regarding various Tone Plans (i.e., RUs) described herein can be included in the EHT-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the EHT-SIG.
[0365] In step S3530, the receiving device can decode the remaining portion of the PPDU based on the information about the Tone Plan (i.e., RU) acquired in step S3520. For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about one Plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the Tone Plan (i.e., RU) and acquire the MPDU included in the data field.
[0366] Additionally, the receiving device may perform a processing operation to transmit the decoded data to a higher layer (e.g., MAC layer) through step S3530. Furthermore, if the generation of a signal from the higher layer to the PHY layer is instructed in response to the data transmitted to the higher layer, a subsequent operation may be performed.
[0367] Hereinafter, the above-described embodiment will be described with reference to FIGS. 1 to 35.
[0368] Figure 36 is a flowchart illustrating a procedure for transmitting a PPDU according to the present embodiment.
[0369] An example of FIG. 36 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves on the 802.11be system and can satisfy backward compatibility with the 802.11be system.
[0370] An example of FIG. 36 is performed at a transmitting STA, which may correspond to an access point (AP). The receiving STA of FIG. 36 may correspond to at least one STA (station).
[0371] The present embodiment proposes a method for allocating an MRU composed of two non-continuous RUs and configuring a signal field for transmitting data by applying different transmission parameters, e.g., MCS and Nss, to each RU. In particular, the present embodiment proposes a method for allocating two non-consecutive RUs within an MRU through a new RU allocation subfield in the signal field and configuring one unified user field for each of the two RUs to indicate the MCS and Nss applied to each RU.
[0372] In step S3610, the transmitting STA (station) generates a Physical layer protocol data unit (PPDU).
[0373] In step S3620, the transmitting STA transmits the PPDU to the receiving STA.
[0374] The above PPDU includes first and second signal fields and a data field.
[0375] The first signal field includes information that the data field is transmitted via a Multiple Resource Unit (MRU) composed of a combination of discontinuous first and second Resource Units (RUs).
[0376] The second signal field includes a common field and a user-specific field. The common field includes RU allocation information for the combination of the discontinuous first and second RUs. The RU allocation information is newly defined information based on the value of the Disregard bit (or reserved bit) of the RU allocation subfield, and a detailed description will be provided later.
[0377] The above user-specific field comprises a single user field integrated for the first and second RUs. The single user field may be configured to include different MCS and Nss information for each RU. For example, the single user field comprises information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU.
[0378] Additionally, the one user field may further include information about the first Nss (Number of spatial streams) applied to the first RU, and the second user field may further include information about the second Nss applied to the second RU.
[0379] Based on the channel status of the first and second RUs, the first RU may be transmitted by applying the first MCS and the first Nss, and the second RU may be transmitted by applying the second MCS and the second Nss. The sum of the first and second Nss may not exceed 8 at most.
[0380] In the past, there was a problem that when a signal was transmitted by commonly applying transmission parameters to MRUs even when the channel condition of a specific channel within an MRU was poor due to OBSS, fading, etc., the overall transmission efficiency and throughput decreased. Therefore, in this embodiment, a method is proposed to transmit a signal by applying different transmission parameters to each RU by considering the channel condition of an MRU composed of discontinuous RUs. That is, this embodiment proposes a method of configuring a newly defined RU allocation subfield to apply different MCS and Nss to each RU within an MRU and a single integrated user field for discontinuous RUs. That is, by transmitting a signal by applying transmission parameters suitable for the channel condition to each RU within an MRU, the overall transmission efficiency and throughput can be improved compared to applying common (or unified) transmission parameters to the MRU.
[0381] Furthermore, this embodiment proposes a method for applying transmission parameters within an MRU composed of a combination of non-contiguous RUs, rather than an MRU composed of a combination of RUs defined in 802.11be. This is because the channel conditions of consecutive RUs are considered similar, and thus applying separate transmission parameters is not very beneficial. Non-contiguous RUs can also receive Rx (Receiver) chains in parallel.
[0382] If the bandwidth of the above PPDU is 80 MHz, the 80 MHz may include the first to fourth 242-tone RUs or the first and second 484-tone RUs in order from low to high frequency.
[0383] If the bandwidth of the above PPDU is 160 MHz, the 160 MHz may include the first to fourth 484-tone RUs in order from low frequency to high frequency.
[0384] If the bandwidth of the above PPDU is 320 MHz, the 320 MHz may include the first to fourth 996-tone RUs in order from low frequency to high frequency.
[0385] The RU allocation information may include information about the size and location of resources for the first RU and information about the size and location of resources for the second RU. Specifically, the RU allocation information may indicate information about the size and location of resources for each RU based on the value of the Disregard bit (or the reserved bit) of the existing RU allocation subfield. According to the present embodiment, there is no need to define additional signaling separately for resource allocation for discontinuous RUs within an MRU, so there is an effect that signaling overhead does not increase.
[0386] Resource allocation per RU within MRU according to the value of the above RU allocation information is as follows.
[0387] When the above RU allocation information is set to 304, the MRU may be a 242+242-tone MRU within an 80MHz frequency subblock, the first RU may be the first 242-tone RU, and the second RU may be the third 242-tone RU.
[0388] When the above RU allocation information is set to 305, the MRU may be a 242+242-tone MRU within an 80 MHz frequency subblock, the first RU may be the first 242-tone RU, and the second RU may be the fourth 242-tone RU.
[0389] When the above RU allocation information is set to 306, the MRU may be a 242+242-tone MRU within an 80MHz frequency subblock, the first RU may be the second 242-tone RU, and the second RU may be the fourth 242-tone RU.
[0390] When the above RU allocation information is set to 307, the MRU may be a 484+484-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 484-tone RU, and the second RU may be the third 484-tone RU.
[0391] When the above RU allocation information is set to 308, the MRU may be a 484+484-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 484-tone RU, and the second RU may be the fourth 484-tone RU.
[0392] When the above RU allocation information is set to 309, the MRU may be a 484+484-tone MRU within a 160 MHz frequency subblock, the first RU may be the second 484-tone RU, and the second RU may be the fourth 484-tone RU.
[0393] When the above RU allocation information is set to 310, the MRU may be a 996+996-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 996-tone RU, and the second RU may be the third 996-tone RU.
[0394] When the above RU allocation information is set to 311, the MRU may be a 996+996-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 996-tone RU, and the second RU may be the fourth 996-tone RU.
[0395] When the above RU allocation information is set to 312, the MRU may be a 996+996-tone MRU within a 160 MHz frequency subblock, the first RU may be the second 996-tone RU, and the second RU may be the fourth 996-tone RU.
[0396] The first signal field may be a U-SIG (Universal-Signal), and the second signal field may be a UHR-SIG (Ultra High Reliability-Signal).
[0397] The above one user field may be encoded together with the common field to form a common encoding block. The common encoding block may include U-SIG overflow, the RU allocation information, the first user field, a CRC (Cyclic Redundancy Check), and a Tail.
[0398] As another example, the common field includes RU allocation information for the first and second RUs. The RU allocation information may be configured separately for allocation information for the first RU and allocation information for the second RU, similar to the existing RU allocation subfield.
[0399] At this time, the user-specific field may be configured with different user fields for the first and second RUs. That is, the user-specific field includes a first user field for the first RU and a second user field for the second RU. The first user field includes information about a first MCS applied to the first RU. The second user field includes information about a second MCS applied to the second RU. The first user field may further include information about the first Nss applied to the first RU. The second user field may further include information about the second Nss applied to the second RU. Content or subfields excluding the MCS and Nss in the first and second user fields may be configured identically.
[0400] The first user field may be encoded together with the common field to form a common encoding block. The common encoding block may include a U-SIG overflow, the RU allocation information, the first user field, a CRC (Cyclic Redundancy Check), and a Tail. In the user-specific field, the second user field may be formed as a user encoding block. In this case, the user encoding block may include the second user field, a CRC, and a Tail.
[0401] The combination of the first and second non-consecutive RUs within the above MRU can be obtained by measuring the optimal subchannel or RU at the receiving STA. The measurement of the optimal subchannel or RU at the receiving STA can be performed at the request of the transmitting STA or during channel sounding.
[0402] Specifically, the transmitting STA may transmit a request frame to the receiving STA. The request frame may include a bit requesting the receiving STA to perform measurement for an optimal channel. The request frame may include information about a bandwidth through which a Null Data Packet (NDP) used to perform channel measurement is transmitted, information about available channels (punctured or disallowed channels) within the BSS, information about an optimal channel (resolution size of a subchannel and a bitmap for the subchannel), and information about receiving STAs performing channel measurement (AID and RU allocation information).
[0403] The transmitting STA may receive a response frame to the request frame from the receiving STA. The response frame may include its own AID information and a status code indicating whether the request frame was successful or denied.
[0404] The transmitting STA may transmit the NDP to the receiving STA via the bandwidth allocated by the request frame. The receiving STA, upon receiving the NDP, may perform measurements based on information about the channel included in the request frame to select an optimal subchannel or RU.
[0405] The transmitting STA may transmit a trigger frame to the receiving STA to request information about the optimal subchannel or RU selected by the receiving STA based on the NDP. The receiving STA transmits information about the optimal subchannel or RU to the transmitting STA through the RU allocated by the trigger frame.
[0406] Based on the information about the optimal subchannel or RU acquired through the preceding operation, the transmitting STA can configure a combination of non-consecutive first and second RUs within the one MRU.
[0407] Figure 37 is a flowchart illustrating a procedure for receiving a PPDU according to the present embodiment.
[0408] An example of FIG. 37 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves on the 802.11be system and can satisfy backward compatibility with the 802.11be system.
[0409] An example of FIG. 37 is performed at a receiving STA, which may correspond to at least one STA (station). The transmitting STA of FIG. 37 may correspond to an AP (access point).
[0410] The present embodiment proposes a method for allocating an MRU composed of two non-continuous RUs and configuring a signal field for transmitting data by applying different transmission parameters, e.g., MCS and Nss, to each RU. In particular, the present embodiment proposes a method for allocating two non-consecutive RUs within an MRU through a new RU allocation subfield in the signal field and configuring one unified user field for each of the two RUs to indicate the MCS and Nss applied to each RU.
[0411] In step S3710, the receiving STA (station) receives a PPDU (Physical layer protocol data unit) from the transmitting STA.
[0412] At step S3720, the receiving STA decodes the PPDU.
[0413] The above PPDU includes first and second signal fields and a data field.
[0414] The first signal field includes information that the data field is transmitted via a Multiple Resource Unit (MRU) composed of a combination of discontinuous first and second Resource Units (RUs).
[0415] The second signal field includes a common field and a user-specific field. The common field includes RU allocation information for the combination of the discontinuous first and second RUs. The RU allocation information is newly defined information based on the value of the Disregard bit (or reserved bit) of the RU allocation subfield, and a detailed description will be provided later.
[0416] The above user-specific field comprises a single user field integrated for the first and second RUs. The single user field may be configured to include different MCS and Nss information for each RU. For example, the single user field comprises information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU.
[0417] Additionally, the one user field may further include information about the first Nss (Number of spatial streams) applied to the first RU, and the second user field may further include information about the second Nss applied to the second RU.
[0418] Based on the channel status of the first and second RUs, the first RU may be transmitted by applying the first MCS and the first Nss, and the second RU may be transmitted by applying the second MCS and the second Nss. The sum of the first and second Nss may not exceed 8 at most.
[0419] In the past, there was a problem that when a signal was transmitted by commonly applying transmission parameters to MRUs even when the channel condition of a specific channel within an MRU was poor due to OBSS, fading, etc., the overall transmission efficiency and throughput decreased. Therefore, in this embodiment, a method is proposed to transmit a signal by applying different transmission parameters to each RU by considering the channel condition of an MRU composed of discontinuous RUs. That is, this embodiment proposes a method of configuring a newly defined RU allocation subfield to apply different MCS and Nss to each RU within an MRU and a single integrated user field for discontinuous RUs. That is, by transmitting a signal by applying transmission parameters suitable for the channel condition to each RU within an MRU, the overall transmission efficiency and throughput can be improved compared to applying common (or unified) transmission parameters to the MRU.
[0420] Furthermore, this embodiment proposes a method for applying transmission parameters within an MRU composed of a combination of non-contiguous RUs, rather than an MRU composed of a combination of RUs defined in 802.11be. This is because the channel conditions of consecutive RUs are considered similar, and thus applying separate transmission parameters is not very beneficial. Non-contiguous RUs can also receive Rx (Receiver) chains in parallel.
[0421] If the bandwidth of the above PPDU is 80 MHz, the 80 MHz may include the first to fourth 242-tone RUs or the first and second 484-tone RUs in order from low to high frequency.
[0422] If the bandwidth of the above PPDU is 160 MHz, the 160 MHz may include the first to fourth 484-tone RUs in order from low frequency to high frequency.
[0423] If the bandwidth of the above PPDU is 320 MHz, the 320 MHz may include the first to fourth 996-tone RUs in order from low frequency to high frequency.
[0424] The RU allocation information may include information about the size and location of resources for the first RU and information about the size and location of resources for the second RU. Specifically, the RU allocation information may indicate information about the size and location of resources for each RU based on the value of the Disregard bit (or reserved bit) of the existing RU allocation subfield. According to the present embodiment, there is no need to define additional signaling separately for resource allocation for each RU within an MRU, so there is an effect that signaling overhead does not increase.
[0425] Resource allocation per RU within MRU according to the value of the above RU allocation information is as follows.
[0426] When the above RU allocation information is set to 304, the MRU may be a 242+242-tone MRU within an 80MHz frequency subblock, the first RU may be the first 242-tone RU, and the second RU may be the third 242-tone RU.
[0427] When the above RU allocation information is set to 305, the MRU may be a 242+242-tone MRU within an 80 MHz frequency subblock, the first RU may be the first 242-tone RU, and the second RU may be the fourth 242-tone RU.
[0428] When the above RU allocation information is set to 306, the MRU may be a 242+242-tone MRU within an 80 MHz frequency subblock, the first RU may be the second 242-tone RU, and the second RU may be the fourth 242-tone RU.
[0429] When the above RU allocation information is set to 307, the MRU may be a 484+484-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 484-tone RU, and the second RU may be the third 484-tone RU.
[0430] When the above RU allocation information is set to 308, the MRU may be a 484+484-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 484-tone RU, and the second RU may be the fourth 484-tone RU.
[0431] When the above RU allocation information is set to 309, the MRU may be a 484+484-tone MRU within a 160 MHz frequency subblock, the first RU may be the second 484-tone RU, and the second RU may be the fourth 484-tone RU.
[0432] When the above RU allocation information is set to 310, the MRU may be a 996+996-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 996-tone RU, and the second RU may be the third 996-tone RU.
[0433] When the above RU allocation information is set to 311, the MRU may be a 996+996-tone MRU within a 160 MHz frequency subblock, the first RU may be the first 996-tone RU, and the second RU may be the fourth 996-tone RU.
[0434] When the above RU allocation information is set to 312, the MRU may be a 996+996-tone MRU within a 160 MHz frequency subblock, the first RU may be the second 996-tone RU, and the second RU may be the fourth 996-tone RU.
[0435] The first signal field may be a U-SIG (Universal-Signal), and the second signal field may be a UHR-SIG (Ultra High Reliability-Signal).
[0436] The above one user field may be encoded together with the common field to form a common encoding block. The common encoding block may include U-SIG overflow, the RU allocation information, the first user field, a CRC (Cyclic Redundancy Check), and a Tail.
[0437] As another example, the common field includes RU allocation information for the first and second RUs. The RU allocation information may be configured separately for allocation information for the first RU and allocation information for the second RU, similar to the existing RU allocation subfield.
[0438] At this time, the user-specific field may be configured with different user fields for the first and second RUs. That is, the user-specific field includes a first user field for the first RU and a second user field for the second RU. The first user field includes information about a first MCS applied to the first RU. The second user field includes information about a second MCS applied to the second RU. The first user field may further include information about the first Nss applied to the first RU. The second user field may further include information about the second Nss applied to the second RU. Content or subfields excluding the MCS and Nss in the first and second user fields may be configured identically.
[0439] The first user field may be encoded together with the common field to form a common encoding block. The common encoding block may include a U-SIG overflow, the RU allocation information, the first user field, a CRC (Cyclic Redundancy Check), and a Tail. In the user-specific field, the second user field may be formed as a user encoding block. In this case, the user encoding block may include the second user field, a CRC, and a Tail.
[0440] The combination of the first and second non-consecutive RUs within the above MRU can be obtained by measuring the optimal subchannel or RU at the receiving STA. The measurement of the optimal subchannel or RU at the receiving STA can be performed at the request of the transmitting STA or during channel sounding.
[0441] Specifically, the transmitting STA may transmit a request frame to the receiving STA. The request frame may include a bit requesting the receiving STA to perform measurement for an optimal channel. The request frame may include information about a bandwidth through which a Null Data Packet (NDP) used to perform channel measurement is transmitted, information about available channels (punctured or disallowed channels) within the BSS, information about an optimal channel (resolution size of a subchannel and a bitmap for the subchannel), and information about receiving STAs performing channel measurement (AID and RU allocation information).
[0442] The transmitting STA may receive a response frame to the request frame from the receiving STA. The response frame may include its own AID information and a status code indicating whether the request frame was successful or denied.
[0443] The transmitting STA may transmit the NDP to the receiving STA via the bandwidth allocated by the request frame. The receiving STA, upon receiving the NDP, may perform measurements based on information about the channel included in the request frame to select an optimal subchannel or RU.
[0444] The transmitting STA may transmit a trigger frame to the receiving STA to request information about the optimal subchannel or RU selected by the receiving STA based on the NDP. The receiving STA transmits information about the optimal subchannel or RU to the transmitting STA through the RU allocated by the trigger frame.
[0445] Based on the information about the optimal subchannel or RU acquired through the preceding operation, the transmitting STA can configure a combination of non-consecutive first and second RUs within the one MRU.
[0446] <Device Configuration>
[0447] The technical features of the present specification described above can be applied to various devices and methods. For example, the technical features of the present specification described above can be performed / supported by the devices of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above can be applied only to a part of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above can be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and the memory (112, 122) of FIG. 1, or based on the processor (610) and the memory (620) of FIG. 14. For example, the device of the present specification receives a Physical layer protocol data unit (PPDU) from a transmitting STA (station); and decodes the PPDU.
[0448] The technical features of this specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable recording medium containing instructions that are executed by at least one processor.
[0449] The CRM may store instructions for performing operations including receiving a Physical layer protocol data unit (PPDU) from a transmitting STA (station); and decoding the PPDU. Instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to the CRM of the present specification may be the processor (111, 121) or processing chip (114, 124) of FIG. 1, or the processor (610) of FIG. 14. Meanwhile, the CRM of the present specification may be the memory (112, 122) of FIG. 1, the memory (620) of FIG. 14, or a separate external memory / storage medium / disk, etc.
[0450] The technical features of this specification described above are applicable to various applications and business models. For example, the technical features described above can be applied to wireless communication in devices that support artificial intelligence (AI).
[0451] Artificial intelligence (AI) is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.
[0452] An artificial neural network (ANN) is a model used in machine learning. It can refer to a model with problem-solving capabilities, consisting of artificial neurons (nodes) formed by the connection of synapses to form a network. An ANN can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.
[0453] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network may include synapses connecting neurons. In an artificial neural network, each neuron can output a function value of an activation function based on input signals, weights, and biases received through the synapses.
[0454] Model parameters are parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters are parameters that must be set before learning in machine learning algorithms, including the learning rate, number of iterations, mini-batch size, and initialization function.
[0455] The goal of artificial neural network training can be seen as determining model parameters that minimize a loss function. The loss function can be used as an indicator for determining optimal model parameters during the artificial neural network training process.
[0456] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.
[0457] Supervised learning refers to a method for training an artificial neural network when given labels for the training data. The labels can refer to the correct answer (or output value) that the artificial neural network must infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method for training an artificial neural network when the training data is not given labels. Reinforcement learning can refer to a learning method in which an agent defined within a given environment is trained to select actions or action sequences that maximize the cumulative reward in each state.
[0458] Machine learning implemented with a deep neural network (DNN) containing multiple hidden layers among artificial neural networks is also called deep learning, and deep learning is a subset of machine learning. Hereinafter, the term "machine learning" is used to encompass deep learning.
[0459] Additionally, the above-described technical features can be applied to wireless communication of robots.
[0460] A robot can be defined as a machine that automatically performs or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making independent judgments, and performing actions can be called an intelligent robot.
[0461] Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with actuators or motors, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots incorporate wheels, brakes, and propellers into their actuators, enabling them to move on the ground or fly in the air.
[0462] Additionally, the above-described technical features can be applied to devices that support extended reality.
[0463] Extended reality is a general term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology presents real-world objects and backgrounds as CG images only, AR technology presents virtual CG images over images of real objects, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.
[0464] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.
[0465] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.
[0466] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.
Claims
1. In a wireless LAN system, A step in which a receiving STA (station) receives a PPDU (Physical layer protocol data unit) from a transmitting STA; and The receiving STA includes a step of decoding the PPDU, The above PPDU includes first and second signal fields and a data field, The first signal field includes information that the data field is transmitted via an MRU (Multiple Resource Unit) composed of a combination of discontinuous first and second RUs (Resource Units), The second signal field includes a common field and a user-specific field, The above common field includes RU allocation information for the combination of the discontinuous first and second RUs, The above user specific field comprises a single user field integrated for the first and second RUs, and The above one user field includes information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU. method.
2. In paragraph 1, The RU allocation information includes information about the size and location of resources for the first RU and information about the size and location of resources for the second RU, If the bandwidth of the above PPDU is 80 MHz, the 80 MHz includes the first to fourth 242-tone RUs in order from low frequency to high frequency, If the bandwidth of the above PPDU is 160 MHz, the 160 MHz includes the first to fourth 484-tone RUs in order from low frequency to high frequency, If the bandwidth of the above PPDU is 320 MHz, the 320 MHz includes the first to fourth 996-tone RUs in order from low frequency to high frequency. method.
3. In paragraph 2, If the above RU allocation information is set to 304, The above MRU is a 242+242-tone MRU within an 80MHz frequency subblock, The first RU is the first 242-tone RU, and the second RU is the third 242-tone RU. method.
4. In paragraph 2, If the above RU allocation information is set to 305, The above MRU is a 242+242-tone MRU within an 80MHz frequency subblock, The first RU is the first 242-tone RU, and the second RU is the fourth 242-tone RU. method.
5. In paragraph 2, If the above RU allocation information is set to 306, The above MRU is a 242+242-tone MRU within an 80MHz frequency subblock, The first RU is the second 242-tone RU, and the second RU is the fourth 242-tone RU. method.
6. In paragraph 2, If the above RU allocation information is set to 307, The above MRU is a 484+484-tone MRU within a 160MHz frequency subblock, The first RU is the first 484-tone RU, and the second RU is the third 484-tone RU. method.
7. In paragraph 2, If the above RU allocation information is set to 308, The above MRU is a 484+484-tone MRU within a 160MHz frequency subblock, The first RU is the first 484-tone RU, and the second RU is the fourth 484-tone RU. method.
8. In paragraph 2, If the above RU allocation information is set to 309, The above MRU is a 484+484-tone MRU within a 160MHz frequency subblock, The first RU is the second 484-tone RU, and the second RU is the fourth 484-tone RU. method.
9. In paragraph 2, If the above RU allocation information is set to 310, The above MRU is a 996+996-tone MRU within a 160MHz frequency subblock, The first RU is the first 996-tone RU, and the second RU is the third 996-tone RU. method.
10. In paragraph 2, If the above RU allocation information is set to 311, The above MRU is a 996+996-tone MRU within a 160MHz frequency subblock, The first RU is the first 996-tone RU, and the second RU is the fourth 996-tone RU. method.
11. In paragraph 2, If the above RU allocation information is set to 312, The above MRU is a 996+996-tone MRU within a 160MHz frequency subblock, The first RU is the second 996-tone RU, and the second RU is the fourth 996-tone RU. method.
12. In paragraph 1, The above one user field further includes information about the first Nss (Number of spatial streams) applied to the first RU and information about the second Nss applied to the second RU. method.
13. In paragraph 12, Based on the channel status of the first and second RUs, the first RU is transmitted by applying the first MCS and the first Nss, and the second RU is transmitted by applying the second MCS and the second Nss. The sum of the first and second Nss above does not exceed 8. method.
14. In a wireless LAN system, a receiving STA (station) memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Receive a PPDU (Physical layer protocol data unit) from a transmitting STA; and Decrypt the above PPDU, The first signal field includes information that the data field is transmitted via an MRU (Multiple Resource Unit) composed of a combination of discontinuous first and second RUs (Resource Units), The second signal field includes a common field and a user-specific field, The above common field includes RU allocation information for the combination of the discontinuous first and second RUs, The above user specific field comprises a single user field integrated for the first and second RUs, and The above one user field includes information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU. Receiving STA.
15. In a wireless LAN system, A step in which a transmitting STA (station) generates a PPDU (Physical layer protocol data unit); and The transmitting STA comprises a step of transmitting the PPDU to the receiving STA, The first signal field includes information that the data field is transmitted via an MRU (Multiple Resource Unit) composed of a combination of discontinuous first and second RUs (Resource Units), The second signal field includes a common field and a user-specific field, The above common field includes RU allocation information for the combination of the discontinuous first and second RUs, The above user specific field comprises a single user field integrated for the first and second RUs, and The above one user field includes information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU. method.
16. In paragraph 15, The RU allocation information includes information about the size and location of resources for the first RU and information about the size and location of resources for the second RU, If the bandwidth of the above PPDU is 80 MHz, the 80 MHz includes the first to fourth 242-tone RUs in order from low frequency to high frequency, If the bandwidth of the above PPDU is 160 MHz, the 160 MHz includes the first to fourth 484-tone RUs in order from low frequency to high frequency, If the bandwidth of the above PPDU is 320 MHz, the 320 MHz includes the first to fourth 996-tone RUs in order from low frequency to high frequency. method.
17. In paragraph 16, If the above RU allocation information is set to 304, The above MRU is a 242+242-tone MRU within an 80MHz frequency subblock, The first RU is the first 242-tone RU, and the second RU is the third 242-tone RU. method.
18. In a wireless LAN system, a transmitting STA (station) memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: A step in which a transmitting STA (station) generates a PPDU (Physical layer protocol data unit); and The transmitting STA comprises a step of transmitting the PPDU to the receiving STA, The first signal field includes information that the data field is transmitted via an MRU (Multiple Resource Unit) composed of a combination of discontinuous first and second RUs (Resource Units), The second signal field includes a common field and a user-specific field, The above common field includes RU allocation information for the combination of the discontinuous first and second RUs, The above user specific field comprises a single user field integrated for the first and second RUs, and The above one user field includes information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU. Transmitting STA.
19. At least one computer-readable medium containing instructions based on being executed by at least one processor, A step of receiving a PPDU (Physical layer protocol data unit) from a transmitting STA (station); and Including a step of decrypting the above PPDU, The first signal field includes information that the data field is transmitted via an MRU (Multiple Resource Unit) composed of a combination of discontinuous first and second RUs (Resource Units), The second signal field includes a common field and a user-specific field, The above common field includes RU allocation information for the combination of the discontinuous first and second RUs, The above user specific field comprises a single user field integrated for the first and second RUs, and The above one user field includes information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU. Recording medium.
20. In a wireless LAN system, in the device, memory; and A processor operatively coupled to the memory, the processor comprising: Receives a PPDU (Physical layer protocol data unit) from a transmitting STA (station); and Decrypt the above PPDU, The first signal field includes information that the data field is transmitted via an MRU (Multiple Resource Unit) composed of a combination of discontinuous first and second RUs (Resource Units), The second signal field includes a common field and a user-specific field, The above common field includes RU allocation information for the combination of the discontinuous first and second RUs, The above user specific field comprises a single user field integrated for the first and second RUs, and The above one user field includes information about a first MCS (Modulation and Coding Scheme) applied to the first RU and information about a second MCS applied to the second RU. device.
Citation Information
Patent Citations
Method and device for allocating resource by limiting rus and mrus for sta operating at only 20 mhz in wireless LAN system
WO2022050629A1
Methods and devices for resource unit allocation in wireless local area networks
WO2022199268A1
