Pilot for interference mitigation
The integration of an IM pilot in the PPDU structure addresses interference measurement challenges in wireless LAN systems, enhancing transmission reliability and throughput by improving channel estimation and interference mitigation.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- LG ELECTRONICS INC
- Filing Date
- 2025-12-19
- Publication Date
- 2026-07-02
AI Technical Summary
Existing wireless LAN systems face challenges in accurately measuring and correcting interference in Overlapping BSS and AP-dense environments, leading to performance degradation in signal transmission and reception.
Incorporation of an Interference Measurement (IM) pilot within the PPDU structure, optimized for various bandwidths (80/160/320 MHz) and accounting for preamble puncturing, to enhance interference measurement capabilities and improve channel estimation.
The IM pilot enables precise interference measurement, enhancing data demodulation performance and link stability, particularly in multi-user and long-distance transmissions, thereby improving PPDU transmission reliability and throughput.
Smart Images

Figure KR2025022316_02072026_PF_FP_ABST
Abstract
Description
Pilot for interference mitigation
[0001] This specification relates to wireless LAN systems, and more specifically, to an operation and apparatus for a pilot signal that eliminates interference related to data in a wireless LAN system.
[0002] Wireless local area networks (WLANs) have been improved in various ways. For example, the Extreme High Throughput (EHT) standard can utilize newly proposed increased bandwidth, an improved PPDU (PHY layer protocol data unit) structure, improved sequencing, and the Hybrid Automatic Repeat Request (HARQ) technique. The EHT standard can be referred to as the IEEE 802.11be standard.
[0003] To support high throughput and high data rates, the EHT standard may use wide bandwidth (e.g., 160 / 320 MHz), 16 streams, and / or multi-link (or multi-band) operation.
[0004] In the EHT standard, wide bandwidth (e.g., 160 / 240 / 320 MHz) can be used for high throughput. In addition, preamble puncturing and multiple RU transmission can be used to efficiently utilize bandwidth.
[0005] WLAN systems can be further improved through the Ultra High Reliability (UHR) standard. The UHR system may be referred to as the IEEE 802.11bn standard. The UHR system aims to support ultra-high reliability during signal transmission to STAs. To achieve this, various technologies are being considered for high throughput, low latency, and extended range support.
[0006] One of the various purposes of this specification is to address the problem of signal transmission and reception performance degradation caused by interference in OBSS (Overlapping BSS) environments and AP-dense environments. In conventional technology, it is difficult to sufficiently measure or correct for various interference effects occurring in the time / frequency domain using only existing pilots included in the data field, and there was a limitation in that performance degradation was prominent in multi-user environments or long-distance transmission environments.
[0007] Accordingly, this specification defines an IM (Interference Measurement) pilot for precisely identifying channel and interference characteristics during the signal transmission and reception process, and proposes a method of including said IM pilot in a PPDU along with data for transmission. For example, one of the various examples in this specification is to configure a bandwidth-specific IM pilot tone plan that can be used in various resource structures, such as 80 MHz, 160 MHz, 320 MHz PPDU transmission or 80 MHz PPDU transmission with preamble puncturing applied, thereby enabling the receiver to accurately measure the effects of interference.
[0008] Accordingly, the example of this specification aims to establish a foundation for next-generation high-reliability and high-efficiency transmission by enhancing interference measurement capabilities across the entire PPDU structure transmitted in a WLAN system. In other words, it aims to provide a more stable and high-quality communication link through the acquisition of interference information based on IM pilot.
[0009] One of the various examples of this specification defines an Interference Measurement (IM) pilot and proposes a method of including the said IM pilot in a PPDU along with data for transmission.
[0010] The PPDU of this specification may have various bandwidths. For example, one of the various examples of this specification proposes a bandwidth-specific IM pilot tone plan that can be used in various resource structures, such as 80 MHz, 160 MHz, 320 MHz PPDU transmission or 80 MHz PPDU transmission with preamble puncturing applied.
[0011] Depending on the bandwidth of various PPDUs, the IM pilot may have various subcarrier index intervals such as 6, 9, 10, and 11. For example, it is desirable that the IM pilot does not overlap with the conventional CFO pilot. For example, it is desirable that the IM pilot have a zero value, zero power, or zero energy. For example, the IM pilot can be configured by considering the positions of the existing CFO pilot along with the positions of the conventional guard tones and DC tones.
[0012] According to the present specification, since an IM pilot is included and transmitted during the PPDU transmission and reception process, the receiving end can more precisely measure the level of interference occurring in OBSS and AP-dense environments. In particular, the proposed IM pilot tone plan is optimized for each bandwidth (80 / 160 / 320 MHz) and whether preamble puncturing is applied, thereby significantly improving the accuracy of interference measurement in various real-world environments.
[0013] Since the measured interference information is directly utilized in the receiver's channel estimation, compensation, and interference mitigation processes, signal recovery that is more robust against interference than existing pilot-based methods is possible. As a result, data demodulation performance and link stability are significantly improved, even in multi-user transmissions, long-distance links, and high-interference sections.
[0014] Therefore, applying the IM pilot structure of this specification to a WLAN system improves PPDU transmission reliability and throughput, and enables more consistent performance even in actual densely deployed AP environments. This contributes to meeting the high-quality / low-latency communication requirements demanded in next-generation WLAN standard environments.
[0015] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.
[0016] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).
[0017] Figure 3 is a diagram illustrating a general link setup process.
[0018] FIG. 4 illustrates an example of a multi-link (ML).
[0019] FIG. 5 illustrates a PPDU transmitted / received in an STA of the present specification.
[0020] Figure 6 is a diagram showing the arrangement of resource units (RU) used for a 20 MHz PPDU.
[0021] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.
[0022] Figure 8 is a diagram showing the arrangement of resource units (RU) used for an 80 MHz PPDU.
[0023] Figure 9 shows the operation according to UL-MU.
[0024] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.
[0025] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.
[0026] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.
[0027] Figure 13 shows an example of a MAC frame header.
[0028] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.
[0029] Figure 15 shows an example of a tone plan related to an 80 MHz subchannel to which preamble puncturing is applied.
[0030] FIG. 16 is a flowchart of the procedure related to the technical features of the present specification.
[0031] FIG. 17 is another example of a flowchart of a procedure related to the technical features of the present specification.
[0032] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."
[0033] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."
[0034] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."
[0035] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (UHR-Signal field)," the "UHR-Signal field" may be proposed as an example of "control information." In other words, the "control information" of this specification is not limited to the "UHR-Signal field," and the "UHR-Signal field" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (UHR-Signal field)," the "UHR-Signal field" may be proposed as an example of "control information."
[0036] Additionally, "a / an" as used in this specification may mean "at least one" or "one or more." Also, terms ending in "(s)" may mean "at least one" or "one or more."
[0037] Additionally, the expressions "based on," "on the basis of," or "according to" as used in this specification mean "based at least in part on" and do not mean "based only on one."
[0038] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.
[0039] The following examples of this specification may be applied to various wireless communication systems. For example, the following examples of this specification may be applied to wireless local area network (WLAN) systems. For example, this specification may be applied to IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification may be applied to Ultra High Reliability (UHR) standards or next-generation wireless LAN standards that enhance IEEE 802.11bn. In addition, the examples of this specification may be applied to mobile communication systems. For example, they may be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on 3GPP (3rd Generation Partnership Project) standards.
[0040] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.
[0041] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.
[0042] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of this specification may also be referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. The STA (110, 120) of this specification may also be referred to by various names such as network, base station, Node-B, Access Point (AP), repeater, router, relay, etc. The STA (110, 120) of this specification may also be referred to by various names such as receiving apparatus, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.
[0043] For example, the STA (110, 120) can perform the role of an access point (AP) or a non-AP. That is, the STA (110, 120) of this specification can perform the functions of an AP and / or a non-AP. In this specification, an AP may also be indicated as an AP STA.
[0044] The STA (110, 120) of this specification may support various communication standards other than the IEEE 802.11 standard. For example, it may support communication standards according to 3GPP standards (e.g., LTE, LTE-A, 5G NR standards). In addition, the STA of this specification may be implemented in various devices such as mobile phones, vehicles, and personal computers. Furthermore, the STA of this specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving.
[0045] In this specification, the STA (110, 120) may include a medium access control (MAC) that complies with the provisions of the IEEE 802.11 standard and a physical layer interface for the wireless medium.
[0046] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.
[0047] The first STA (110) may include a processor (111), memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.
[0048] The transceiver (113) of the first STA performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).
[0049] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmitted signal, and perform control for transmitting the signal. The memory (112) of the AP can store the signal received through the transceiver (113) (e.g., received signal) and the signal to be transmitted through the transceiver (e.g., transmitted signal).
[0050] For example, the second STA (120) can perform the intended operation of a Non-AP STA. For example, the non-AP transceiver (123) performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).
[0051] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmitted signal, and perform control for transmitting the signal. The memory (122) of the Non-AP STA can store the signal received through the transceiver (123) (e.g., received signal) and the signal to be transmitted through the transceiver (e.g., transmitted signal).
[0052] For example, the operation of the device indicated as AP in the following specification may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (111) of the first STA (110), and related signals may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). Additionally, control information related to the operation of the AP or the transmission / reception signals of the AP may be stored in the memory (112) of the first STA (110). Additionally, if the second STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signals of the AP can be stored in the memory (122) of the second STA (110).
[0053] For example, the operation of a device indicated as non-AP (or User-STA) in the following specification may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is non-AP, the operation of the device indicated as non-AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signals of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of the device marked as non-AP is controlled by the processor (111) of the first STA (110), and the related signal can be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signal of the AP can be stored in the memory (112) of the first STA (110).
[0054] In the following specification, a device referred to as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, a device indicated without specific drawing symbols as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may also refer to the STA (110, 120) of FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. Additionally, in the following example, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation to generate a transmission / reception signal or to perform data processing or operations in advance for a transmission / reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of sub-fields (SIG, STF, LTF, Data) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 4) a power control operation and / or power saving operation applied to the STA; and 5) an operation related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (112, 122) of FIG. 1.
[0055] The device / STA of the aforementioned supplementary drawing (a) of FIG. 1 can be modified as shown in supplementary drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of this specification will be described based on supplementary drawing (b) of FIG. 1.
[0056] For example, the transceiver (113, 123) shown in side drawing (b) of FIG. 1 can perform the same function as the transceiver shown in side drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) shown in side drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) shown in side drawing (b) of FIG. 1 can perform the same function as the processor (111, 121) and the memory (112, 122) shown in side drawing (a) of FIG. 1 described above.
[0057] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, User STA, network, Base Station, Node-B, AP (Access Point), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or the processing chip (114, 124) shown in side drawing (b) of FIG. 1. That is, the technical features of the present specification may be performed in the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or only in the processing chip (114, 124) shown in side drawing (b) of FIG. 1. For example, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal generated in the processor (111, 121) shown in side drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) shown in side drawings (a) / (b) of FIG. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal to be transmitted from the processing chip (114, 124) shown in side drawing (b) of FIG. 1 is generated to the transceiver (113, 123).
[0058] For example, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal being received by the transceiver (113, 123) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceiver (113, 123) shown in side view (a) of FIG. 1 being acquired by the processor (111, 121) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceiver (113, 123) shown in side view (b) of FIG. 1 being acquired by the processing chip (114, 124) shown in side view (b) of FIG. 1.
[0059] Referring to side view (b) of FIG. 1, software code (115, 125) may be included in memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.
[0060] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or a processor enhanced therefrom.
[0061] In this specification, an uplink may refer to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted through the uplink. Additionally, in this specification, a downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted through the downlink.
[0062] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).
[0063] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).
[0064] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter BSS). The BSS (200, 205) is a set of APs and STAs, such as an AP (access point, 225) and STA1 (Station, 200-1), that can communicate with each other by successfully synchronizing, and is not a concept referring to a specific area. The BSS (205) may include one or more STAs (205-1, 205-2) that can be combined with one AP (230).
[0065] The BSS may include at least one STA, an AP (225, 230) that provides a distribution service, and a distribution system (DS, 210) that connects multiple APs.
[0066] A distributed system (210) can implement an extended service set (ESS, 240) by connecting multiple BSSs (200, 205). The term ESS (240) may be used to denote a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) may have the same service set identification (SSID).
[0067] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) with another network (e.g., 802.X).
[0068] In a BSS like the one at the top of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network between STAs and perform communication without APs (225, 230). A network that establishes a network between STAs and performs communication without APs (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).
[0069] The bottom of Fig. 2 is a conceptual diagram showing IBSS.
[0070] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity that performs management functions centrally. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and since access to the distributed system is not allowed, they form a self-contained network.
[0071] Figure 3 is a diagram illustrating a general link setup process.
[0072] In the described S310 step, the STA can perform a network discovery operation. The network discovery operation may include the STA's scanning operation. That is, in order for the STA to access a network, it must find a network it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.
[0073] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels and transmits a probe request frame to search for nearby APs, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame, whereas in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store the BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (e.g., transmitting and receiving probe requests / responses on channel 2).
[0074] Although not shown in the example of Fig. 3, scanning operations may also be performed using a passive scanning method. An STA performing scanning based on passive scanning can wait for a beacon frame while switching between channels. A beacon frame is one of the management frames in IEEE 802.11, which announces the presence of a wireless network and is periodically transmitted to allow a scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS take turns transmitting beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. An STA that has received a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner.
[0075] The STA that discovered the network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described later. The authentication process of S320 may include the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.
[0076] The authentication frame may include information regarding the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), Finite Cyclic Group, etc.
[0077] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.
[0078] A successfully authenticated STA may perform an association process based on step S330. The association process includes the STA sending an association request frame to the AP, and in response, the AP sending an association response frame to the STA. For example, the association request frame may include information regarding various capabilities, beacon listen interval, service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, Traffic Indication Map Broadcast request, interworking service capabilities, etc. For example, a connection response frame may include information related to various capabilities, status code, AID (Association ID), support rate, EDCA (Enhanced Distributed Channel Access) parameter set, RCPI (Received Channel Power Indicator), RSNI (Received Signal to Noise Indicator), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS map, etc.
[0079] Subsequently, in step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame.
[0080] FIG. 4 illustrates an example of a multi-link (ML).
[0081] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate through a multi-link. The MLDs can be classified into an AP MLD containing multiple AP STAs and a non-AP MLD containing multiple non-AP STAs. That is, the AP MLD may include affiliated APs (e.g., AP STAs), and the non-AP MLD may include affiliated STAs (e.g., non-AP STAs, or user-STAs).
[0082] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be assigned to the first and second links. The first and second multilinks may be identified by a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the link may be configured in different bands.
[0083] The AP MLD of FIG. 4 includes three affiliated APs. In one example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In one example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Additionally, in one example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Additionally, in one example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.
[0084] In one example of FIG. 4, AP1 can initiate a multilink setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In one example of FIG. 4, non-AP STA1 can transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) shown in FIG. 4 may be the same as the AP shown in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) shown in FIG. 4 may be the same as the STA shown in FIG. 1 and / or FIG. 2 (e.g., user-STA or non-AP STA).
[0085] 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.
[0086] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.
[0087] The STAs of this specification (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) can transmit and / or receive the PPDU of FIG. 5. The PPDU described in this specification may have the structure of FIG. 5, for example. Additionally, the PPDU described in this specification, the Ultra High Reliability (UHR) PPDU, may be referred to by various names such as transmit PPDU, receive PPDU, first type or N type PPDU. The PPDU described in this specification may be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that improve upon IEEE 802.11bn.
[0088] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of SU (single-user) mode / type / transmission, MU (multi-user) mode / type / transmission, and NDP (null data packet) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the illustrated Data field may be omitted. If the PPDU of FIG. 5 is used for TB (Trigger-based) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that receives a Trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU in which the UHR-SIG is omitted in the example of FIG. 5.
[0089] In FIG. 5, L-STF to UHR-LTF can be called a preamble or physical preamble and can be generated / transmitted / received / acquired / decoded at the physical layer (included in the transmitting / receiving STA).
[0090] Each block illustrated in FIG. 5 may be referred to as a field / subfield / signal, etc. As illustrated in FIG. 5, the names of these fields / subfields / signals may be L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.
[0091] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in Fig. 5 can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be displayed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be displayed in units of 78.125 kHz.
[0092] The PPDU of Fig. 5, L-LTF and L-STF, may be the same as conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).
[0093] The L-SIG field of FIG. 5 may contain, for example, 24 bits of bit information. For example, the 24 bits of information may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity bit, and a 6-bit Tail bit. For example, the 12-bit Length field may contain information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU, or a UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is an HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, or EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in a UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.
[0094] For example, a (non-AP and AP) STA can apply BCC encoding based on a code rate of 1 / 2 to 24 bits of information in the L-SIG field. Subsequently, the transmitting STA can obtain 48 bits of BCC encoding. BPSK modulation can be applied to the 48 bits of encoding to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarrier {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. Consequently, the 48 BPSK symbols can be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can additionally map the signal of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.
[0095] For example, the (non-AP and AP) STA can generate an RL-SIG that is identical to the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine that the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the HE PPDU, EHT PPDU, or UHR PPDU if the RL-SIG is present. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the non-HT PPDU, HT PPDU, or VHT PPDU if the RL-SIG is not present. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.
[0096] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be referred to by various names such as the first SIG field, first SIG, first type SIG, control signal, control signal field, first (type) control signal, common control field, and common control signal.
[0097] U-SIG may contain N bits of information and may contain information to identify the type of EHT PPDU. For example, U-SIG may be constructed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol for U-SIG (e.g., OFDM symbol) may have a duration of 4 us. Each symbol of U-SIG may be used to transmit 26 bits of information. For example, each symbol of U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.
[0098] For example, A bit information (e.g., 52 un-coded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bit information (e.g., 26 un-coded bits) of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bit information (e.g., 26 un-coded bits) of the total A bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can generate 52-coded bits by performing convolutional encoding (e.g., BCC encoding) based on a rate of R=1 / 2 and can perform interleaving on the 52-coded bits. The transmitting STA can generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers), excluding the pilot tones -21, -7, +7, and +21.
[0099] For example, A bit information (e.g., 52 un-coded bits) transmitted by U-SIG may include a CRC field (e.g., a field of 4 bits) and a tail field (e.g., a field of 6 bits). The CRC field and the tail field may be transmitted through a second symbol of U-SIG. The CRC field may be generated based on 26 bits assigned to the first symbol of U-SIG and the remaining 16 bits within the second symbol excluding the CRC / tail field, and may be generated based on a conventional CRC calculation algorithm. Additionally, the tail field may be used to terminate the trellis of a convolutional decoder and may be set, for example, to "000000".
[0100] A bit information (e.g., 52 un-coded bits) transmitted by U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.
[0101] For example, the version-independent bits of U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value of the 3-bit PHY version identifier (e.g., a value of 000) may indicate that the transmitted and received PPDU is an EHT PPDU. Additionally, a second value of the 3-bit PHY version identifier (e.g., a value of 001) may indicate that the transmitted and received PPDU is a UHR PPDU.
[0102] In other words, when an (AP / non-AP) STA transmits an EHT PPDU, it can set a 3-bit PHY version identifier to a first value. In other words, a receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is a UHR PPDU based on the PHY version identifier having the second value.
[0103] For example, the version-independent bits of U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.
[0104] For example, the version-independent bits of U-SIG may include information regarding the length of the TXOP and information regarding the BSS color ID.
[0105] For example, if the UHR PPDU is classified into various types (e.g., type related to SU transmission (performed based on UL or DL), type related to DL transmission, type related to NDP transmission, type related to DL non-MU-MIMO, type related to DL MU-MIMO, type related to Multi-AP operation, type related to CBF (Coordinated beamforming) and SR (Spatial Reuse), type related to C-OFDMA (Coordinated OFDMA), type related to C-TDMA (Coordinated TDMA)), information regarding the type of the EHT PPDU (e.g., 2-bit or 3-bit information) may be included in the version-dependent bits of the U-SIG.
[0106] For example, U-SIG may include information regarding 1) a bandwidth field containing information about the bandwidth, 2) a field containing information about the Modulation and Coding Scheme (MCS) technique applied to UHR-SIG, 3) an indication field containing information about whether the dual subcarrier modulation (DCM) technique is applied to UHR-SIG, 4) a field containing information about the number of symbols used for UHR-SIG, 5) a field containing information about whether UHR-SIG is generated across the entire band, 6) a field containing information about the type of UHR-LTF / STF, and 7) a field indicating the length of UHR-LTF and CP length.
[0107] Preamble puncturing may be applied to the PPDU of Fig. 5. Preamble puncturing means applying puncturing to a portion of the total band of the PPDU (e.g., a secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band within the 80 MHz band and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.
[0108] For example, the pattern of preamble puncturing can be pre-set. For example, when a first puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band within an 80 MHz band. For example, when a second puncturing pattern is applied, puncturing may be applied only to one of two secondary 20 MHz bands included in a secondary 40 MHz band within an 80 MHz band. For example, when a third puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band included in a primary 80 MHz band within a 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, within the 160 MHz band (or 80+80 MHz band), the primary 40 MHz band included in the primary 80 MHz band is present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.
[0109] 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.
[0110] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured individually in 80 MHz units. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (e.g., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information regarding a 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (e.g., information regarding a preamble puncturing pattern). Meanwhile, the UHR-SIG following the first U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (e.g., information regarding a preamble puncturing pattern), and the UHR-SIG following the second U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (e.g., information regarding a preamble puncturing pattern).
[0111] Additionally or generally, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. U-SIG may include information regarding preamble puncturing for all bands (e.g., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (e.g., information regarding preamble puncturing patterns).
[0112] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth may contain different U-SIGs.
[0113] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.
[0114] UHR-SIG provides additional signals to the U-SIG field, enabling the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that apply commonly to all users. Additionally, the UHR-SIG field contains resource allocation information, making it possible for the STA to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (e.g., UHR modulated fields of an UHR PPDU).
[0115] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on a RU (resource unit) defined by a plurality of subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through a RU (resource unit) defined by a plurality of subcarriers / tones.
[0116] FIG. 6 is a diagram showing the arrangement of resource units (RUs) used for a 20 MHz PPDU. That is, UHR-LTF, UHR-STF and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.
[0117] As shown at the top of FIG. 6, 26 units (e.g., units corresponding to 26 tones) may be arranged. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Additionally, seven DC tones may be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on the left and right sides of the DC band. Furthermore, 26, 52, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.
[0118] Meanwhile, the RU arrangement of Fig. 6 is utilized not only for situations involving multiple users (MU) but also for situations involving a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of Fig. 4, and in this case, three DC tones can be inserted.
[0119] In the example of FIG. 6, various sizes of RUs, namely 26-RU, 52-RU, 106-RU, 242-RU, etc., are proposed. Since the specific size of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (e.g., the number of corresponding tones). In this specification, N-RU may be indicated as N-tone RU, etc. For example, 26-RU may be indicated as 26-tone RU.
[0120] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.
[0121] Just as various sizes of RUs were used in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may also be used in the example of FIG. 7. Additionally, 5 DC tones may be inserted at the center frequency, 12 tones may be used as guard bands in the leftmost band of the 40 MHz band, and 11 tones may be used as guard bands in the rightmost band of the 40 MHz band.
[0122] In addition, as described, 484-RU may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.
[0123] FIG. 8 is a diagram showing the arrangement of resource units (RUs) used for an 80 MHz PPDU. The arrangement of resource units (RUs) used in this specification may be varied. For example, the arrangement of resource units (RUs) used in the 80 MHz band may be varied.
[0124] FIG. 9 illustrates the operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can acquire a TXOP (925) by performing channel access through contending (e.g., Backoff operation) and transmit a Trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU containing the Trigger frame (930). When the PPDU containing the Trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.
[0125] TB PPDUs (941, 942) are transmitted at the same time and may be transmitted from multiple STAs (e.g., User STAs) with an AID indicated within a Trigger frame (930). An ACK frame (950) for a TB PPDU may be implemented in various forms. For example, an ACK frame (950) for a TB PPDU may be implemented in the form of a BA (block ACK).
[0126] In FIG. 9, the transmission(s) of the Trigger Frame (930), TB PPDU (941, 942) and / or ACK Frame (950) can be performed within TXOP (925).
[0127] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.
[0128] The 2.4 GHz band may be referred to by other names, such as the first band (band). Additionally, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency located between 2.4 and 2.5 GHz) are used / supported / defined.
[0129] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz channels within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned to channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned to channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned to channel index N may be (2.407 + 0.005*N) GHz. Channel indices may be referred to by various names, such as channel numbers. The specific numerical values of channel indices and center frequencies may change.
[0130] FIG. 10 illustrates four channels within a 2.4 GHz band as an example. The illustrated first frequency range (1010) to fourth frequency range (1040) may each include one channel. For example, the first frequency range (1010) may include channel 1 (a 20 MHz channel having index 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency range (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency range (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency range (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.
[0131] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.
[0132] The 5 GHz band may be referred to by other names such as the second band / band. The 5 GHz band may refer to a frequency range in which channels with a center frequency of 5 GHz or higher and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 may be changed.
[0133] Multiple channels within the 5 GHz band include UNII (Unlicensed National Information Infrastructure)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency regions referred to as UNII Mid and UNII-2 Extended. UNII-3 may be referred to as UNII-Upper.
[0134] Multiple channels may be configured within the 5 GHz band, and the bandwidth of each channel may be varied, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency range within UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency range may be divided into four channels through a 40 MHz frequency range. The 5170 MHz to 5330 MHz frequency range may be divided into two channels through an 80 MHz frequency range. Alternatively, the 5170 MHz to 5330 MHz frequency range may be divided into one channel through a 160 MHz frequency range.
[0135] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.
[0136] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with a center frequency of 5.9 GHz or higher are used / supported / defined. The specific figures shown in FIG. 12 are subject to change.
[0137] For example, the 20 MHz channel of FIG. 12 can be defined starting from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 may have index 1 (or channel index, channel number, etc.), and the center frequency may be assigned as 5.945 GHz. That is, the center frequency of the index N channel may be determined as (5.940 + 0.005*N) GHz.
[0138] Accordingly, the indices (or channel numbers) of the 20 MHz channel in FIG. 12 are 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, It may be 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule described above, the index of the 40 MHz channel of FIG. 12 may be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.
[0139] The structure and types / subtypes of MAC frames are described below.
[0140] FIG. 13 shows an example of a MAC frame header. As illustrated, the MAC frame may include a frame control field / information of 2 octets, a duration field / information of 2 octets, a Receiver Address (RA) field / information of 6 octets, and a Transmitter Address (TA) field / information of 6 octets. As illustrated in FIG. 13, the four fields may be consecutive. The MAC header of FIG. 13 may be modified in various ways, and a new field may be inserted between the four illustrated fields, or at least one of the illustrated fields may be omitted.
[0141] The MAC header shown in FIG. 13 may be located at the very beginning of the MAC frame. That is, the MAC frame may include a MAC header such as that in FIG. 13 and a MAC body field / information following the MAC header. The MAC frame containing the MAC header of FIG. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) shown in FIG. 5.
[0142] MAC frames included in the data fields of the PPDU of this specification may be classified into various types. For example, MAC frames of this specification may be classified into control frames, management frames, and data frames.
[0143] For example, a management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLANs. For the management frame, the values of the type fields (B3 and B2) in FIG. 13 are set to 00. Additionally, the values of the subtype fields (B7, B6, B5, B4) in FIG. 13 are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).
[0144] For example, the control frame includes the Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLANs. For the control frame, the values of the type fields (B3 and B2) in FIG. 13 are set to 01. Also, the values of the subtype fields (B7, B6, B5, B4) of FIG. 13 are as follows: Trigger(0010), Beamforming Report Poll(0100), NDP Announcement(0101), Control Frame Extension(0110), Control Wrapper(0111), BlockAckReq(1000), BlockAck(1001), PS-Poll(1010), RTS(1011), CTS(1100), Ack(1101), CF-End(1110).
[0145] For example, the data frame includes (QoS) Data, (QoS) Null, etc., defined in conventional WLANs. For the management frame, the value of the type field (B3 and B2) in FIG. 13 is set to 10.
[0146] MAC frames / signals used in this specification can be identified through the type field / information and subtype field / information described above. For example, a "trigger frame" in this specification may refer to a MAC frame in which the type bits B3 and B2 within the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 within the frame control field are set to 0010. Various MAC frames described in this specification are inserted into / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDU).
[0147] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.
[0148] The device illustrated in FIGS. 1 to 4 (e.g., AP STA, non-AP STA) can be modified as in FIG. 14. The transceiver (630) in FIG. 14 may be identical to the transceiver (113, 123) in FIG. 1. The transceiver (630) in FIG. 14 may include a receiver and a transmitter.
[0149] The processor (610) of FIG. 14 may be the same as the processor (111, 121) of FIG. 1. Or, the processor (610) of FIG. 14 may be the same as the processing chip (114, 124) of FIG. 1.
[0150] 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.
[0151] Referring to FIG. 14, a power management module (611) manages power for a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.
[0152] Referring to FIG. 14, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related inputs to be used by the processor (610).
[0153] Pilots that mitigate interference in a wireless LAN system are described below. In this specification, the interference mitigation pilots may be expressed by various terms such as IM (interference mitigation) pilot, IM pilot tone, IM pilot signal, first / second pilot, first / second pilot tone / signal, first / second zero value pilot (tone / signal), first / second zero power pilot (tone / signal), or first / second zero energy pilot (tone / signal). For convenience of explanation, the relevant technical features are described below based on IM pilot(s), but the terms may be replaced with various other terms.
[0154] Interference Mitigation (IM)
[0155] In 11bn / UHR, interference mitigation can be defined to prevent signal reception performance degradation caused by OBSS or interference from other STAs during transmission and reception between an AP and a non-AP STA. To eliminate the effects of such interference, it is necessary to define pilot tone(s) for measuring interference. This specification proposes a method for allocating interference mitigation pilot tone(s) to measure interference when transmitting and receiving wireless LAN signals through subchannels of various sizes.
[0156] Various studies are being conducted on interference mitigation pilot tone(s). The relevant details are introduced below.
[0157] For example, IM pilot(s) in this specification may refer to pilot signals interlaced with the data subcarriers / tones. Through IM pilot(s), a multi-antenna receiver can continuously observe and track interference signals in the time-frequency domain. A transmitting STA can enable a receiving STA to estimate the statistical characteristics of interference signals by inserting IM pilot(s) into the data field. For example, the receiving STA can calculate an interference covariance matrix based on the IM pilot(s) and then apply interference mitigation techniques such as receive beamforming.
[0158] For example, IM pilot(s) can suppress interference on a receiving STA regardless of the bandwidth of the interference. However, the number of Rx antennas required for interference cancellation may need to be greater than the existing N_SS (number of transmitted spatial streams), which can increase the hardware requirements of the receiving STA.
[0159] Meanwhile, the number and density of IM pilot(s) can be critical factors for accurately estimating the interference covariance matrix. For example, theoretically, the number of measurements, i.e., the number of IM pilot(s), must be greater than the number of Rx antennas for the matrix to be estimated in its inverse form, and as the number of Rx antennas increases, the required number of IM pilots may also increase. Due to these characteristics, it is difficult to use low-density pilots, such as CFO (Carrier Frequency Offset) pilots, for IM purposes, and problems may arise where it is difficult to spatially arrange the required number of pilots when the RU size is small.
[0160] In addition, IM pilot(s) must be positioned so that they are appropriately 'sampled' within the coherence bandwidth of the interference signal. Even when interference is confined to a narrow band, accurate covariance estimation is possible only if the area where interference fluctuations exist is observed sufficiently densely; therefore, the distribution of IM pilots in the time-frequency domain needs to be adjusted to suit the characteristics of the interference. Ultimately, IM pilot(s)-based interference mitigation technology is a technique in which the number, density, placement, and weighting models of pilots are organically combined to determine the accuracy of interference estimation by the receiving STA. The technology proposed in this specification can provide specific structures and procedures for improving interference suppression performance in wireless systems by practically utilizing such IM pilots.
[0161] This specification may propose IM pilot tone plans for various bandwidths / communications. For example, this specification may present an 80 MHz IM pilot tone plan, a 160 MHz IM pilot tone plan, and a 320 MHz IM pilot tone plan. For example, the pilot tone plans of this specification may be applied when preamble puncturing is not applied. Additionally or generally, the pilot tone plans of this specification may be designed with preamble puncturing in mind.
[0162] 80 MHz IM pilot tone plan for UHR transmission
[0163] In the following example, an 80 MHz IM pilot tone plan may be proposed. For instance, it may be assumed that the 996 tone RU size is basically the same as the 80 MHz RU tone plan defined in IEEE 802.11be (or EHT system), and that guard tone(s), null tone(s), DC tone(s), and CFO pilot tone(s) have the same number and location as the existing ones.
[0164] For example, FIG. 8 shows an 80 MHz RU location to which the IM pilot tone plan of the present specification is applied.
[0165] As shown in Fig. 8, when transmitting IM pilot(s) in UHR (or IEEE 802.11bn system), the range of data tone may be [-500: -3, 3: 500]. In this case, the index of the CFO pilot tone(s) may be {-468, -400, -334, -266, -226, -158, -92, -24, 24, 92, 158, 226, 266, 334, 400, 468}.
[0166] For example, IM pilot(s) for measuring interference and performing interference mitigation during signal transmission and reception using an 80 MHz PPDU can be defined and evenly distributed within the available tones of 80 MHz. In this case, the IM pilot tone(s) can be defined so as not to overlap with the existing pilots of the 80 MHz / 996 tone RU.
[0167] For example, IM pilot tone(s) can be set to have the same power value or have zero power, zero value, and zero energy. For instance, IM pilot tone(s) are different from the pilots defined for CFO tracking on the Data tone (e.g., CFO pilots) and do not have the same tone location. For instance, IM pilot tone(s) do not overlap with Guard and DC tones.
[0168] For example, IM pilot(s) may exist at intervals of 4 or 5 tones within the available tones. However, if the density of IM pilot(s) increases, the problem of pilot overhead may arise. In other words, since IM pilot(s) are transmitted through the tone or carrier of the data field, pilot overhead increases when many IM pilots are defined and inserted for Interference Mitigation (IM). This results in a disadvantage where the number of tones available for data transmission is reduced, leading to a decrease in data throughput.
[0169] Case 1: 80 MHz IM pilot tone plan with 9-tone interval
[0170] For example, IM pilot tone(s) may not overlap with CFO pilot tone(s) defined in the 80 MHz data tone. For example, IM pilot tone(s) may be defined within the data tone range [-500:-3, 3:500]. For example, IM pilot tone(s) may be designed to be mirror-symmetric within the above tone range. Alternatively, mirror symmetry may not be maintained. In this specification, mirror-symmetric means a structure in which, centered around a specific reference index (e.g., index zero (0)), there exists a tone or resource element corresponding to a positive index that is of the same size and has the opposite sign to a tone or resource element placed at a negative index. For example, if one pilot tone is placed at index minus 3, one pilot tone is also placed at index plus 3, so that the entire pilot tone is configured to have left-right symmetry centered around the reference point (e.g., index zero).
[0171] Case1-1: No mirror symmetric case with 9-tone interval
[0172] A tone plan for an IM pilot can be defined as follows, and as an example, it can be defined using one of the above tone plans.
[0173] For example, the indices of IM pilot(s) may be [-498:9:492]. For example, [a:b:c] as expressed herein means that a is the lowest index, c is the highest index, and b is the interval applied to the index. Alternatively, this may mean that individual tones of the IM pilot are assigned for every b subcarrier index from the a subcarrier index to the c subcarrier index. Data tones or CFO pilots, etc., may be assigned to the remaining indices not indicated above.
[0174] Additionally or generally, the index of the IM pilot(s) can be [-492:9:498].
[0175] Based on the example above, a total of 111 IM pilots are defined within the data tone range, and IM pilots can be defined using fixed tone locations in 9-tone increments. Accordingly, this offers the advantage of easy implementation. However, since the intervals between the left guard, right guard, and IM pilot tone(s) differ, errors may occur regarding interference measured in terms of low or high frequencies.
[0176] Case 1-2: Mirror symmetric case with 9-tone interval
[0177] For example, IM pilot(s) are defined using mirror symmetry, and IM pilot(s) defined at low frequency (or negative tone index) centered on DC tone(s) can be similarly defined at high frequency (or positive tone index) using mirror symmetry. In this case, the tone plan for the IM pilot can be defined, for example, using one of the defined tone plans above.
[0178] For example, the indices of IM pilot(s) can be [-498:9:-3] and [3:9:498].
[0179] For example, since a tone adjacent to a DC tone(s) is allocated for the IM pilot, the interference measurement performance using that tone location may be degraded due to the influence of interference caused by the DC tone(s).
[0180] Additionally or generally, the indices of IM pilot(s) may be [-497:9:-11] and [11:9:497].
[0181] Additionally or generally, the indices of the IM pilot(s) may be [-493:9:-7] and [7:9:493]. The above case may be called the first option.
[0182] Additionally or generally, the indices of IM pilot(s) may be [-492:9:-6] and [6:9:492]. The above cases may be referred to as the second option.
[0183] The tone plans of the first and second options above can reduce the influence of guard and DC by allocating IM pilots at intervals of a specific tone (an interval of (7,4) for the first option and an interval of (8,3) for the second option), taking into account the effects of interference caused by guard and DC. In the example above, since IM pilots are allocated to even tones in the same way as the CFO pilot of the second option, there is an advantage in reusing existing implementation methods.
[0184] As shown above, since mirror symmetry is used, it has the advantage of being easy to implement and requiring minimal memory for tone allocation.
[0185] Case 2: IM pilot(s) with 10-tone interval
[0186] Below, IM pilot(s) are defined at intervals of 10 ton units and can be defined using fixed tone locations.
[0187] For example, IM pilot tone(s) are defined within the data tone range [-500:-3, 3:500], and can be defined using mirror symmetry within the tone range or without using mirror symmetry.
[0188] Case 2-1: No mirror symmetric case with 10-tone interval
[0189] A tone plan for an IM pilot can be defined as follows, and as an example, it can be defined using one of the defined tone plans.
[0190] For example, the index of IM pilot(s) can be [-497:10:493].
[0191] For example, the index of IM pilot(s) can be [-493:10:497].
[0192] For example, the index of IM pilot(s) can be [-495:10:-495].
[0193] For example, the above tone plan defines 100 IM pilots, and the tone of the assigned IM pilot is separated from the Guard and DC by a certain tone, which has the advantage of reducing the influence of the Guard and DC.
[0194] The tone plan [-495:10:-495] described above can reduce interference from guards by assigning IM pilots at equal intervals (e.g., 5-tone intervals) from the left guard and right guard, and can also measure interference at equal intervals by assigning IM pilots at uniform intervals within the data range.
[0195] Case 2-2: Mirror symmetric case with 10-tone interval
[0196] The tone plan for the IM pilot can be defined as follows.
[0197] For example, the indices of the IM pilot(s) could be [-499:10:-9] and [9:10:499]. The above example sets a greater tone interval between IM pilot tones close to the DC tone than between the intervals from the guard tone(s) in order to reduce the influence of the DC tone(s).
[0198] For example, the indices of the IM pilot(s) can be [-495:10:-5] and [5:10:495]. The above example is an instance where more tone intervals are set between IM pilot tones close to the Guard tone(s) than between them from the DC tone(s) in order to reduce the effect of interference from the Guard tone(s).
[0199] Additionally or generally, considering the influence from both guard tone(s) and DC tone(s), the following Option 1 and Option 2 may be proposed.
[0200] Option 1: [-497:10:-7] [ 7:10:497]
[0201] Option 2: [-491:10:-11] [11:10:491]
[0202] For example, to reduce the impact on DC and guard and further reduce the overhead for IM pilot, an IM pilot tone plan such as Option 2 can be defined.
[0203] Case 3: IM pilot(s) with 11-tone interval
[0204] An example of using fixed tone locations at intervals of 11 tones is proposed below.
[0205] In the following example, since the pilot tone interval is 11 tones, there is an advantage in further reducing pilot overhead compared to the previously described intervals of 9 or 10 tones. In this case, the IM pilot tone(s) can be defined within the data tone range [-500:-3, 3:500]. Additionally, mirror symmetry may or may not be used.
[0206] Case 3-1: No mirror symmetric case with 11-tone interval
[0207] The tone plan for the IM pilot can be defined as follows.
[0208] For example, the index of IM pilot(s) can be [-498:11:492].
[0209] For example, the index of IM pilot(s) can be [-492:11:498].
[0210] According to the two examples above, a total of 91 IM pilot tone(s) can be located within the data tone range.
[0211] Case 3-2: Mirror symmetric case with 11-tone interval
[0212] The tone plan for the IM pilot can be defined as follows.
[0213] For example, the indices of IM pilot(s) can be [-496:11:-12] and [12:11:496].
[0214] For example, the indices of IM pilot(s) can be [-494:11:-10] and [10:11:494]. In the above example, similar intervals of 6 from Guard tone(s) and 7 from DC tone(s) can be assigned.
[0215] For example, the indices of the IM pilot(s) may be [-492:11:-8] and [8:11:492]. In the above example, to reduce the effect of interference caused by the Guard tone(s), the interval between the Guard and the IM pilot (e.g., 8-tone) was considered larger than the interval with the DC tones (e.g., 5-tone).
[0216] The IM pilot tone plan defined as above can reduce interference caused by the influence of the left / right Guard tone and DC tone by assigning IM pilot tone(s) from the left / right Guard tone(s) and DC tone(s) to a tone separated by a specific interval.
[0217] Case 4: 80 MHz IM pilot tone plan with 6-tone interval
[0218] Considering the overhead for IM pilot tone(s), IM pilot tone(s) can be assigned in 6-tone intervals within the available tone range. For example, to avoid overlap with CFO pilot tone(s), IM pilot tone(s) assignment can be defined in 6-tone intervals within the available tone range, from -243, the lowest tone index where assignment begins, to DC tone(s). Additionally, mirror symmetry may be applied.
[0219] In this case, the index of the IM pilot(s) can be [-499:6:-7, 7:6:499]. When the above example is used, a total of 166 tones from the existing available data tone range can be used as IM pilot tone(s). The above example can reduce the impact of IM pilot overhead compared to examples where 4-tone and 5-tone are applied.
[0220] The above example can be modified in various ways. For instance, IM pilot tone(s) can be assigned at a certain distance from guard tone(s) and DC tone(s) to avoid overlap with CFO pilot tone(s). For instance, by shifting the lowest tone index by 3 tones, IM pilot tone(s) can be assigned at intervals of 6 tones from tone index -497 to tone index -7. In this case as well, mirror symmetry can be applied.
[0221] In this case, the index of the IM pilot(s) can be [-497:6:-5, 5:6:497]. When the above example is used, the IM pilot can be assigned starting from a tone that is a certain distance away from the guard tone(s) and DC tone(s). This reduces the impact of signal interference entering the IM pilot tone(s) from the guard tone(s) or DC tone(s). Through this, IM measurement and IM performance via the IM pilot tone(s) can be improved.
[0222] The above example can be modified in various ways. For instance, IM pilot tone(s) can be assigned at a certain distance from guard tone(s) and DC tone(s) to avoid overlap with CFO pilot tone(s). For instance, IM pilot tone(s) can be assigned at intervals of 6 tones from tone index -495 to DC tone(s). In this case, mirror symmetry can also be applied. In this case, the total number of tones assigned as IM pilot tone(s) can be 166.
[0223] In this case, the index of the IM pilot(s) can be [-495:6:-3, 3:6:495]. When the above example is used, by assigning the IM pilot tone(s) close to the DC tone(s), the signal can be robust against signal distortion near the DC tone.
[0224] Examples of Cases 1 through 4 proposed above can be applied to 80 MHz at 160 MHz and 320 MHz (PPDU). Additionally, for BWs of 80 MHz or less, IM pilots can be defined using IM pilot tone(s) defined in the frequency part corresponding to 20 / 40 MHz or puncturing BW. For example, in the case of 20 MHz, it can be defined using the IM pilot assigned to one of the four 242-tone RUs existing within 80 MHz. For example, it can be defined using the IM pilot tone plan for the first or second 242-tone RU. For example, in the case of 40 MHz, an IM pilot tone plan defined for the part corresponding to 40 MHz in terms of low frequency within 80 MHz, or for the part including DC, corresponding to 40 MHz, can be used. For example, when using lower 40 MHz, IM pilot tone(s) allocated to the 1st 484-tone RU within 80 MHz can be used. As another example, when using DC-inclusive 40 MHz, IM pilot tone(s) allocated to the 242-tone RU within the second and third can be used. For example, in the case of a BW of 80 MHz or less, IM pilot tone(s) can be defined using an IM pilot tone plan defined for a single 242-tone RU within 80 MHz.
[0225] 160 MHz IM pilot tone plan for UHR transmission
[0226] In the following example, a 160 MHz IM pilot tone plan may be proposed. For instance, it may be assumed that the 996 tone RU size is basically the same as the 160 MHz RU tone plan defined in IEEE 802.11be (or EHT system), and that guard tone(s), null tone(s), DC tone(s), and CFO pilot tone(s) have the same number and location as the existing ones.
[0227] The 160 MHz RU location may be based on a structure in which the 80 MHz RU location shown in FIG. 8 is repeated twice. In a situation where the structure of FIG. 8 is repeated, the range of data tones for IM pilot(s) transmission may be [-1012: -515, -509: -12, 12: 509, 515: 1012]. In this case, the index of the CFO pilot tone may be {-980, -912, -846, -778, -732, -664, -598, -530, -494, -426, -360, -292, -246, -178, -112, -44, 44, 112, 178, 246, 292, 360, 426, 494, 530, 598, 664, 732, 778, 846, 912, 980}.
[0228] For example, IM pilot(s) for measuring interference and performing interference mitigation during signal transmission and reception using a 160 MHz PPDU can be defined and evenly distributed within available tones within 160 MHz. In this case, the IM pilot tones can be defined so as not to overlap with existing pilots (e.g., CFO pilots) of the 160 MHz channel / band or 2x996 tone RU.
[0229] At this time, the above IM pilot can be defined as follows when transmitting a 160MHz PPDU.
[0230] Case 5: 160 MHz IM pilot tone plan with 6-tone interval
[0231] For example, to reduce the overhead for IM pilot tone(s), IM pilot tone(s) can be allocated at intervals of 6 tones within the available tone range and can be defined as follows. In this case, the allocated IM pilot tone(s) can be defined so as not to overlap with existing defined pilot tones.
[0232] For example, IM pilot tone(s) can be assigned within the available tone range without overlapping with CFO pilot tone(s). IM pilot tone(s) can be assigned in 6-tone intervals from the lower tone index -1011 to the DC tone(s). In this case, tone indices that overlap with the null carrier existing in the middle of 996 RU can be excluded. Additionally, assignments for positive tones can be performed based on mirror symmetry.
[0233] For example, the index of IM pilot(s) is [-1011:6:-15, 15:6:1011], but ±513 may be excluded. Alternatively, the above case can be expressed as the index of IM pilot(s) being [-1011:6:-519, -507:6:-15, 15:6:507, 519:6:1011].
[0234] As another example, in order to allocate IM pilot tone(s) close to DC tone(s), the IM pilot tone plan defined above can be defined with a tone shift. In this case, the tone shift considered can be defined by taking into account a 2-tone shift relative to the tone plan defined above. For example, an IM pilot tone plan defined in 6-tone increments considering a tone shift is as follows.
[0235] Specifically, the index of IM pilot(s) is [-1009:6:-13 , 13:6:1009], but ±511 may be excluded. Alternatively, the index of IM pilot(s) can be expressed as [-1009:6:-517, -505:6:-13 , 13:6:505, 517:6:1009].
[0236] In the case of allocating IM pilot tones as described above, a total of 332 tones can be allocated as IM pilot tones from the existing available data tone range. Compared to 4-tone intervals and 5-tone intervals, the above example can reduce overhead caused by IM pilots.
[0237] The above example can be modified in various ways. For instance, IM pilot tones can be defined in units of 6 tones, and the IM pilot tones can be defined so that the null subcarrier existing in tone 996 RU does not overlap with each other. Specifically, after applying a 5-tone shift, IM pilot tone assignments can be defined at 6-tone intervals from tone index -1007 to tone index -17. Additionally, mirror symmetry can be applied.
[0238] For example, the index of the IM pilot(s) can be [-1007:6:-17, 17:7:1007]. In this case, it can be spaced 5 tones away from the guard tone(s) and DC tone(s). This reduces the effect of signal interference from the guard tone(s) or DC tone(s).
[0239] The above example can be modified in various ways. For example, IM pilot tone(s) can be defined so as not to overlap with CFO pilot tone(s) and to have a symmetric position within the 996 tone RU centered on the null subcarrier present in the 996 tone RU.
[0240] For example, IM pilot tone assignments can be defined at intervals of 6 tones from tone index -1011 to the null subcarrier. In this case, after the null subcarrier, tones symmetric to the IM pilot tone relative to the null subcarrier can be assigned as IM pilot tone(s). As defined above, after assigning IM pilot tones, the assignment of positive tones can be defined by applying mirror symmetry. According to the above example, the total number of IM pilot tones can be 166.
[0241] Based on the example above, the index of IM pilot(s) can be [-1011:6: -519, -505:6:-13, 13:6:505, 519:6: 1011].
[0242] The above example can be modified in various ways. For instance, IM pilot tone(s) can be assigned to a tone spaced at a certain distance from Guard tone(s) and DC tone(s) so that they are not affected by the guard and DC tones.
[0243] Based on the above example, the index of IM pilot(s) can be [-1009:6: -517, -507:6:-15, 15:6:507, 517:6:1009].
[0244] The above example can be modified in various ways. For example, to measure interference entering the middle of a 996 tone RU in detail and remove the corresponding line, an IM pilot can be assigned near the null subcarrier of the 996 tone RU. Based on the above example, the indices of the IM pilot(s) can be [-1007:6: -515, -509:6:-17, 17:6:509, 515:6: 1007].
[0245] As described above, if IM pilot tones are defined at 6-tone intervals within the available tone range, approximately 16 to 17% of the data tones can be allocated as IM pilot tones. In this case, the overhead of IM pilot tones can be reduced compared to determining IM pilot tones based on 4-tone intervals.
[0246] 320 MHz IM pilot tone plan for UHR transmission
[0247] In the following example, a 320 MHz IM pilot tone plan may be proposed. For instance, a 996 tone RU size, which is basically the same as the 320 MHz RU tone plan defined in IEEE 802.11be (or EHT system), and guard tone(s), null tone(s), DC tone(s), and CFO pilot tone(s) with the same number and location as the existing ones may be assumed.
[0248] The 320 MHz RU location may be based on a structure in which the 80 MHz RU location shown in FIG. 8 is repeated four times. In a situation where the structure of FIG. 8 is repeated, the range of data tones for IM pilot(s) transmission may be [-2036: -1539, -1533: -1036, -1012: -515, -509: -12, 12: 509, 515:1012, 1036:1533, 1539:2036]. In this case, the index of the CFO pilot tone is {-2004, -1936, -1870, -1802, -1756, -1688, -1622, -1554, -1518, -1450, -1384, -1316, -1270, -1202, -1136, -1068, -980, -912, -846, -778, -732, -664, -598, -530, -494, -426, -360, -292, -246, -178, -112, -44, 44, 112, 178, 246, 292, 360, 426, 494, 530, 598, 664, 732, It can be equal to 778, 846, 912, 980, 1068, 1136, 1202, 1270, 1316, 1384, 1450, 1518, 1554, 1622, 1688, 1756, 1802, 1870, 1936, 2004}.
[0249] For example, IM pilot(s) for measuring interference and performing interference mitigation during signal transmission and reception using a 320 MHz PPDU can be defined and evenly distributed within the available tones within 320 MHz. In this case, the IM pilot tones can be defined so as not to overlap with existing pilots (e.g., CFO pilots) of the 320 MHz channel / band or 4x996 tone RU.
[0250] Case 6: 320 MHz IM pilot tone plan with 6-tone interval
[0251] For example, to reduce the overhead for IM pilot tone(s), IM pilot tone(s) can be allocated at intervals of 6 tones within the available tone range and can be defined as follows. In this case, the allocated IM pilot tone(s) can be defined so as not to overlap with existing defined pilot tones.
[0252] Case 6-1: 320 MHz IM pilot tone plan with 6-tone interval
[0253] For example, IM pilot tone(s) can be assigned within the available tone range without overlapping with CFO pilot tone(s). IM pilot tone(s) can be assigned in 6-tone intervals from the lower tone index -2035 to the DC tone(s). In this case, tone indices that overlap with null carrier / tones existing before the DC tone(s) (e.g., between 996 tones, within 996 tones) may be excluded. After a negative tone index is assigned, assignments for positive tones can be defined by applying mirror symmetry.
[0254] According to the example above, the negative indices of the IM pilot tone(s) can be determined as [-2035:6: -1543], [-1531:6: -1039], [-1009:6: -517], and [-505:6: -13]. The positive indices of the IM pilot tone(s) can be determined based on mirror symmetry.
[0255] The above example can be modified in various ways. For example, the negative index of the IM pilot tone(s) can be like Example 1 below. The positive index of the IM pilot tone(s) can be determined based on mirror symmetry.
[0256] Example 1: [-2033:6: -1541], [-1529:6:-1037], [-1007:6:-515], [-509:6:-17]
[0257] The above example can be modified in various ways. For example, the negative index of the IM pilot tone(s) can be as in Example 2 below. The positive index of the IM pilot tone(s) can be determined based on mirror symmetry.
[0258] Example 2: [-2031:6: -1539], [-1533:6:-1041], [-1011:6:-519], [-507:6:-15]
[0259] Case 6-2: 320 MHz IM pilot tone plan with 6-tone interval
[0260] The IM pilot tone plan for 320 MHz may vary. For example, the IM pilot tone plan is defined for a 996-tone RU, and the defined IM pilot tone plan can be applied identically regardless of the position of the 996 tone. In this case, an IM pilot tone may not be assigned to a tone index that overlaps with a null carrier / tone existing within the 996-tone RU.
[0261] Specifically, the tone index is -2035 and can be defined in units of 6 tones starting from the low tone index. In this case, an IM pilot tone may not be assigned to a tone index that overlaps with a null carrier / tone existing within the 996-tone RU.
[0262] In this case, the frequency index of the IM pilot tone according to each 996 tone-RU may be as follows.
[0263] 1st 996-tone RU index = [-2035:6: -1543], [-1531:6:-1039]
[0264] 2nd 996-tone RU index = [-1011:6: -519], [-507:6:-15]
[0265] 3rd 996-tone RU index = [13:6: 505], [517:6:1009]
[0266] 4th 996-tone RU index = [1037:6:1529], [1541:6: 2033]
[0267] The above example can be modified in various ways. For example, IM pilot tones can be defined in increments of 6 tones starting from tone index -2033. In this case, IM pilot tones may not be assigned to tone indices that overlap with null carrier / tones existing within the 996-tone RU.
[0268] In this case, the frequency index of the IM pilot tone according to each 996 tone-RU may be as follows.
[0269] 1st 996-tone RU index = [-2033:6: -1541], [-1529:6:-1035]
[0270] 2nd 996-tone RU index = [-1009:6: -517], [-505:6:-13]
[0271] 3rd 996-tone RU index = [15:6: 507], [519:6:1011]
[0272] 4th 996-tone RU index = [1039:6:1531], [1543:6: 2035]
[0273] The above example can be modified in various ways. For instance, to avoid the null carrier / tone and IM pilot overlapping within a 996-tone RU, the IM pilot tone(s) can be defined as follows.
[0274] 1st 996-tone RU index = [-2031:6: -1539], [-1533:6:-1041]
[0275] 2nd 996-tone RU index = [-1007:6: -515], [-509:6:-17]
[0276] 3rd 996-tone RU index = [17:6:509], [515:6:1007]
[0277] 4th 996-tone RU index = [1041:6:1533], [1539:6:2031]
[0278] Case 6-3: 320 MHz IM pilot tone plan with 6-tone interval
[0279] The following example relates to an IM pilot tone plan that has a symmetric position within 996 tone RUs without overlapping with the CFO pilot. Specifically, after assigning IM pilot tone indices for frequency subcarriers / tones, mirror symmetry can be applied to define the assignment of high frequency tones for null carriers / tones.
[0280] For example, the assignment of IM pilot tones can be defined at intervals of 6 tones from tone indices -2035, -1011, 13, and 1037 to the null subcarrier. After the null subcarrier / tone, a tone symmetric to the already assigned IM pilot tone relative to the null subcarrier / tone can be assigned as the IM pilot tone. After assigning the IM pilot tone as above, the assignment of high frequency tones after the null subcarrier / tone can be defined by applying mirror symmetry.
[0281] Based on the above principles, the frequency index of the IM pilot tone for each 996 tone-RU may be as follows.
[0282] 1st 996-tone RU index = [-2035:6: -1543], [-1529:6:-1035]
[0283] 2nd 996-tone RU index = [-1011:6: -519], [-505:6:-13]
[0284] 3rd 996-tone RU index = [13:6: 505], [519:6:1011]
[0285] 4th 996-tone RU index = [1037:6:1529], [1543:6: 2035]
[0286] The above example can be modified in various ways. For instance, the IM pilot(s) can be changed to be positioned closer to the null carrier / tone. In this case, the frequency index of the IM pilot tone for each 996 tone-RU can be as follows.
[0287] 1st 996-tone RU index = [-2033:6: -1541], [-1531:6:-1039]
[0288] 2nd 996-tone RU index = [-1009:6: -517], [-507:6:-15]
[0289] 3rd 996-tone RU index = [15:6: 507], [517:6:1009]
[0290] 4th 996-tone RU index = [1039:6:1531], [1541:6: 2033]
[0291] IM pilot tone plan for punctured 80 MHz
[0292] The following example proposes an example of an IM pilot tone plan for a PPDU to which preamble puncturing is applied.
[0293] Figure 15 shows an example of a tone plan related to an 80 MHz subchannel to which preamble puncturing is applied.
[0294] The following example proposes an IM pilot tone plan for 80 MHz, i.e., punctured 80 MHz, to which preamble puncturing is applied. For example, the following example may be based on guard / null / DC tone / pilot tone(s) of the same number and position as the tone plan shown in FIG. 15.
[0295] Based on an example of FIG. 15, the range of data tones for IM pilot(s) transmission may be [-500: -12, 12: 500]. For example, the indices of CFO pilot tone(s) applied in the example of FIG. 15 may be {-494, -468, -426, -400, -360, -334, -292, -266}, {-246, -220, -178, -152, -112, -86, -44, -18}, {18, 44, 86, 112, 152, 178, 220, 246}, {266, 292, 334, 360, 400, 426, 468, 494}.
[0296] IM pilots for measuring interference and performing interference mitigation during signal transmission and reception using a punctured 80 MHz subchannel or a punctured 80 MHz PPDU can be defined by being evenly distributed within the available tones in punctured 80 MHz. In this case, IM pilot tone(s) can be defined so as not to overlap with the CFO pilots of the punctured 80 MHz or 484+242-tone MRU.
[0297] Case 7: Tone plan for punctured 80 MHz
[0298] For example, IM pilot(s) can be defined as follows for punctured 80 MHz PPDU transmission. Specifically, the tone plan for a punctured 80 MHz or 484+242-tone MRU can be the same as the tone plan for an 80 MHz OFDMA. For example, IM pilot tone(s) can be evenly allocated to the available tones for the 242-tone RUs of an 80 MHz OFDMA. In this case, IM pilot tone(s) are evenly allocated from the low frequency tone to DC within the available tone range, and positive tones may be allocated by applying mirror symmetry. For example, if an IM pilot tone overlaps with a null subcarrier located between the 242-tone RUs, that tone may not be allocated as an IM pilot tone. In other words, a fixed IM pilot tone is allocated for the entire 80 MHz, and IM pilot tone(s) included in the punctured 242-tone RU or 20 MHz subchannel may be excluded, and only IM pilot tone(s) corresponding to the non-punctured portion may be used.
[0299] Case 7-1: Tone plan with 4-tone interval for punctured 80 MHz
[0300] Below, an example of a tone plan is proposed for a case where IM pilot(s) are allocated at intervals of 4 tones within an 80 MHz available tone range.
[0301] Case 7-1-1: Tone plan with 4-tone interval for punctured 80 MHz
[0302] For example, IM pilot tones can be assigned evenly at intervals of 4 tones from tone index -499 to DC tone(s). Additionally, mirror symmetry may be applied. In this case, the frequency indices of the IM pilot tone(s) may be [-499: 4:-259, -251:4:-15, 15:4:251, 259:4:499]. When the above example is used, IM pilot(s) may not be assigned to the ±255 index, which is a tone index that overlaps with the null sucarrier.
[0303] In the IM pilot tone plan defined above, IM pilot(s) may not be assigned to a 20 MHz subchannel or a 242-tone RU to which Preamble puncturing is applied. In other words, among the proposed IM pilot tone(s), tone(s) corresponding to a punctured 20 MHz subchannel or a punctured 242-tone RU may be excluded. For example, if the first 20 MHz subchannel is punctured in terms of low frequency, or if [punctured 242-tone RU, Second 242-tone RU, Second 484-tone RU] is used, the IM pilot may be transmitted using the remaining tone plan excluding the tone defined in the first 20 MHz. In this case, the frequency index of the IM pilot may be [-251:4:-15, 15:4:251, 259:4:499]. The above example may be applicable in various cases. For example, depending on the location of the punctured 20 MHz subchannel (or the location of the punctured 242-tone RU), the punctured 20 MHz subchannel (or the punctured 242-tone RU) may be excluded and IM pilot(s) may be assigned at 4-tone intervals.
[0304] As described above, by defining and using a fixed IM piliot tone plan regardless of preamble punctuing, implementation can be made easier and complexity reduced.
[0305] Case 7-1-2: Tone plan with 4-tone interval for punctured 80 MHz
[0306] The above example can be modified in various ways. For example, IM pilot tone(s) can be assigned closer to DC tone(s). For instance, they can be assigned evenly at intervals of 4 tones from tone index -497 to tone index -13, which is close to DC tone(s). In this case, IM pilot tone(s) are not assigned to ±257, which overlaps with the null subcarrier. Mirror symmetry can be applied to the above example. In this case, the frequency indices of the IM pilot tone(s) can be [-497:4:-261, -253:4:-13, 13:4:253, 261:4:497]. Using the above IM pilot tone plan, when puncturing is applied at 80 MHz, IM pilot tone(s) corresponding to the punctured 20 MHz subchannel (or punctured 242-tone RU) can be excluded.
[0307] Case 7-2: Tone plan with 6-tone interval for punctured 80 MHz
[0308] Case 7-1 described above can be modified in various ways. For example, to reduce data tone loss or to reduce IM pilot tone overhead, IM pilot tone allocation can be assigned at 6-tone intervals within the available tone range so as not to overlap with existing pilot tones.
[0309] Case 7-2-1: Tone plan with 6-tone interval for punctured 80 MHz
[0310] For example, IM pilot tones can be allocated evenly at intervals of 6 tones from tone index -499 to the DC tone. Additionally, mirror symmetry can be applied. In this case, the frequency indices of the IM pilot tone(s) can be [-499:6:-13, 13:6:499]. As described above, since there are no tones overlapping with the null subcarrier when allocating IM pilot tones, IM pilots can be allocated evenly over 80 MHz. According to the above example, IM pilot overhead can be reduced by using 164 tones for IM pilot allocation compared to Case 7-1 described earlier. Consequently, approximately 16.94% of the available tones can be used for IM pilot allocation.
[0311] Case 7-2-2: Tone plan with 6-tone interval for punctured 80 MHz
[0312] For example, various examples can be proposed by shifting the index of an example in Case 7-2-1. For example, various examples can be applied in which the lowest tone index defined in Case 7-2-1 is shifted by 2 or 4.
[0313] For example, in the case of a 2-tone shift, IM pilot tones can be evenly distributed at 6-tone intervals from tone index -497 to DC tone(s). In this case, tone index -257, which overlaps with the null subcarrier, can be excluded. Mirror symmetry may be applied to this example.
[0314] In this case, the frequency index of the IM pilot tone(s) may be [-497:6:-17, 17:6:497], and the ±257 index in the above example may be excluded. Alternatively, the frequency index of the IM pilot tone(s) may be [-497:6:-263, -251:6: -17, 17:6:251, 263:6: 479].
[0315] For example, in the case of a 4-tone shift, IM pilot tones can be evenly distributed at 6-tone intervals from tone index -495 to DC tone(s). In this case, tone index -255, which overlaps with the null subcarrier, can be excluded. Mirror symmetry may be applied to this example.
[0316] In this case, the frequency index of the IM pilot tone(s) may be [-495:6:-15 15:6:495], and the ±255 index in the above example may be excluded. Alternatively, the frequency index of the IM pilot tone(s) may be [-495:6:-261, -249:6: -15, 15:6:249, 261:6:495].
[0317] Case 8: Tone plan for 242-tone RUs
[0318] For example, the IM pilot tone can be defined in units of 242-tone RUs, as defined in the 80 MHz tone plan. In this case, the first 242-tone RU and the fourth 242-tone RU, and the second 242-tone RU and the third 242-tone RU are paired with each other so that the same IM pilot tone plan can be applied. That is, the IM pilot tone plan for the first 242-tone RU and the second 242-tone RU is configured differently, and the IM pilot tone for the third 242-tone RU and the fourth 242-tone RU can be defined by applying mirror symmetry.
[0319] Case 8-1: Tone plan for 242-tone RUs
[0320] For example, IM pilot tones can be allocated in units of 4 tones within the available tones. In this case, the IM pilot tone plan defined for each 242-tone RU can be defined as follows.
[0321] First, for the 1st 242-tone RU and the 4th 242-tone RU, an IM pilot tone plan can be defined using one of the following two tone plans.
[0322] Tone plan_1 = [-499:4:-259], [259:4:499]
[0323] Tone plan_2 = [-497:4:-261], [261:4:497]
[0324] And for the 2nd 242-tone RU and 3rd 242-tone RU, an IM pilot tone plan can be defined using one of the following two tone plans.
[0325] Tone plan_3 = [-253:4:-13], [13:4:253]
[0326] Tone plan_4 = [-251:4:-15], [15:4:251]
[0327] The IM pilot tone plan for 80 MHz can be composed of a combination of the tone plans defined above. For example, the IM pilot tone plan for 80 MHz can be defined through a combination of the defined tone plan_1 and tone plan_3, or tone plan_2 and tone plan_4. For example, if puncturing is applied to 80 MHz, the IM pilot tone(s) corresponding to the punctured 20 MHz subchannel (or 242-tone RU) can be excluded.
[0328] The combination of the above tone plan is an example and can be defined through various combinations. Additionally, different IM pilot tone plans can be applied to each 242-tone RU using the IM pilot tone plans defined for the above-defined 242-tone RU.
[0329] Case 8-2: Tone plan for 242-tone RUs
[0330] Case 8-1 is an example based on a 4-tone interval, but IM pilot tone(s) of a 6-tone interval can be proposed below.
[0331] First, for the 1st 242-tone RU and the 4th 242-tone RU, an IM pilot tone plan can be defined using one of the following three tone plans.
[0332] Tone plan_1 = [-499:6:-259], [259:6:499]
[0333] Tone plan_2 = [-497:6:-263], [263:6:497]
[0334] Tone plan_3 = [-495:6:-261], [261:6:495]
[0335] And for the 2nd 242-tone RU and 3rd 242-tone RU, an IM pilot tone plan can be defined using one of the following three tone plans.
[0336] Tone plan_4 = [-253:6:-13], [13:6:253]
[0337] Tone plan_5 = [-251:6:-17], [17:6:251]
[0338] Tone plan_6 = [-249:6:-15], [15:6:249]
[0339] The IM pilot tone plan for 80 MHz can be composed of a combination of the tone plans defined above. For example, the combination of the tone plans can be defined as follows.
[0340] IndexCombined tone plan1Tone plan_1+ Tone plan_52Tone plan_1+ Tone plan_63Tone plan_2+ Tone plan_44Tone plan_2+ Tone plan_65Tone plan_3+ Tone plan_46Tone plan_3+ Tone plan_5
[0341] The above combination is an example, and an IM pilot tone plan for 80 MHz can be configured through various combinations using the defined tone plan. An IM pilot tone plan for 80 MHz is defined through the combination defined as above, and if puncturing is applied to 80 MHz, the IM pilot tone corresponding to the punctured 20 MHz or 242-tone RU can be excluded.
[0342] The combination of the above tone plan is an example and can be defined through various combinations. Additionally, different IM pilot tone plans can be applied to each 242-tone RU using the IM pilot tone plans defined for the above-defined 242-tone RU.
[0343] FIG. 16 is a flowchart of the procedure related to the technical features of the present specification.
[0344] The operation of FIG. 16 can be performed by various devices. For example, the operation of FIG. 16 can be performed by a non-AP STA, an AP, etc., and can be performed by a non-AP MLD including at least one non-AP STA or an AP MLD including at least one AP.
[0345] As in S1610, the STA can generate a PPDU. For example, the PPDU of S1610 may be a UHR-PPDU disclosed in FIG. 5 or a PPDU of a new format that further improves FIG. 5. For example, the PPDU of S1610 may include a data field.
[0346] For example, the PPDU of S1610 may have various bandwidths. For example, to configure an IM pilot according to the pilot tone described in Case 1, Case 2, Case 3, Case 4, Case 7, and Case 8 described above, a PPDU with a bandwidth of 80 MHz may be generated. Additionally or generally, to configure an IM pilot according to the pilot tone described in Case 5, a PPDU with a bandwidth of 160 MHz may be generated. Additionally or generally, to configure an IM pilot according to the pilot tone described in Case 6, a PPDU with a bandwidth of 320 MHz may be generated.
[0347] For example, coding based on the Low-density Parity Check Code (LDPC) may be applied to the data field of the above PPDU. For example, the above data field may include an Interference Mitigation (IM) pilot with zero energy.
[0348] For example, the IM pilot may include an IM (interference mitigation) pilot based on various tone plans presented in Case 1 to Case 8. For example, an IM pilot may be included based on [-495:10:-495]. In other words, it may be included at intervals of 10 subcarrier indices from the first subcarrier index to the second subcarrier index, and at intervals of 10 subcarrier indices from the third subcarrier index to the fourth subcarrier index, wherein the first subcarrier index is -495, the second subcarrier index is -5, the third subcarrier index is 5, and the second subcarrier index is 495.
[0349] The IM pilot based on [-495:10:-495] is one of the various examples of this specification, and the technical features of this specification are not limited to a single formula. For example, the subcarrier index interval of 10 can be changed to various values such as 9, 11, 6, etc., based on the various tone plans presented in Cases 1 through 8 described above. Also, the lowest subcarrier index or the highest subcarrier index can be changed in various ways. For example, the subcarrier index described in this specification is defined / indicated based on a subcarrier frequency spacing of 78.125 kHz.
[0350] For example, the above IM pilot may have zero energy, zero power, or zero value, etc. In contrast, the above data field may additionally include a CFO pilot. The above CFO pilot may have non-zero energy, non-zero power, or non-zero value, etc. For example, the subcarrier index of the above CFO pilot may be determined according to the bandwidth of the PPDU. As previously explained, the subcarrier index of the above CFO pilot is {-468, -400, -334, -266, -226, -158, -92, -24, 24, 92, 158, 226, 266, 334, 400, 468} or {-980, -912, -846, -778, -732, -664, -598, -530, -494, -426, -360, -292, -246, -178, -112, -44, 44, 112, 178, 246, 292, 360, 426, 494, 530, 598, 664, 732, 778, 846, 912, 980}or, {-2004, -1936, -1870, -1802, -1756, -1688, -1622, -1554, -1518, -1450, -1384, -1316, -1270, -1202, -1136, -1068, -980, -912, -846, -778, -732, -664, -598, -530, -494, -426, -360, -292, -246, -178, -112, -44, 44, 112, 178, 246, 292, 360, 426, 494, 530, 598, 664, It can be 732, 778, 846, 912, 980, 1068, 1136, 1202, 1270, 1316, 1384, 1450, 1518, 1554, 1622, 1688, 1756, 1802, 1870, 1936, 2004}.
[0351] Preamble puncturing may or may not be applied to the above PPDU. For example, depending on whether preamble puncturing is considered or applied, any one of the various tone plans described in Case 1 to Case 8 may be applied.
[0352] As with S1620, the STA can transmit PPDU.
[0353] The steps of FIG. 16 can be varied, additional steps may be inserted in the middle of each step, a preliminary step may be performed before the illustrated step, or a post-step may be performed after the illustrated step. For example, before performing step S1610, the STA may determine various parameters (e.g., bandwidth) for PPDU configuration and, based on this, configure various signal fields (e.g., U-SIG field) of the related PPDU.
[0354] FIG. 17 is a flowchart of the procedure related to the technical features of the present specification.
[0355] The operation of FIG. 17 can be performed by various devices. For example, the operation of FIG. 16 can be performed by a non-AP STA, an AP, etc., and can be performed by a non-AP MLD including at least one non-AP STA or an AP MLD including at least one AP.
[0356] As in step S1710, the STA can receive the PPDU.
[0357] Additionally, as in step S1720, the STA can interpret the PPDU. Step S1720 may include the step of decoding a data field included in the PPDU or obtaining information included in the data field.
[0358] For example, the PPDUs of steps S1710 and S1720 may include data fields. For example, the PPDUs of steps S1710 and S1720 may be the same as the PPDUs of steps S1610 and S1620. Accordingly, the pilot applied to the example of FIG. 17 may be the same as the pilot applied to the example of FIG. 16.
[0359] The steps of FIG. 17 may be varied, and additional steps may be inserted in the middle of each step, a preliminary step may be performed before the illustrated step, or a post-step may be performed after the illustrated step. For example, after step S1710 is performed, the STA may confirm the presence of an IM pilot based on the data field and / or signal field of the PPDU, etc., and perform operations related to interference mitigation based on the IM pilot. The STA may obtain information contained in the data tone in the data field where interference mitigation has been performed and decode the data field based on this.
[0360] The technical features of this specification may be performed by various devices. The device of this specification may be the device described in FIG. 1 / 14. The device of this specification may include at least one processor; and at least one computer memory that is operabably connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor.
[0361] For example, the processor may be the processor described in FIG. 1 and / or FIG. 14. That is, as described above, the processor of this specification may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). The processor includes computers having various architectures, such as single / multi-processor architectures and sequential (Von Neumann) / parallel architectures, as well as specialized circuits such as FPGAs, ASICs, signal processing units, and other devices. For example, the processor of this specification may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or a processor enhanced therefrom.
[0362] For example, the above instructions may refer to computer program instructions executed by the at least one processor. The above (computer program) instructions provide logic and / or routines that enable the technical features of the present specification to be performed by the processor. By reading the at least one memory, the at least one processor can load and execute the computer program.
[0363] The computer program(s) defined by the above instruction may arrive at the device of this specification (e.g., STA) through an appropriate delivery mechanism. The delivery mechanism may be, for example, a computer-readable storage medium, a computer program product, a memory device, a recording medium such as a CD-ROM or DVD, or a manufactured product that tangibly embodies the computer program. The delivery mechanism may be a signal configured to reliably transmit the computer program via a wireless or electrical connection.
[0364] The above (computer program) instructions may include software or firmware for a programmable processor (e.g., programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array, or programmable logic device, etc.).
[0365] For example, the memory described above may be the memory described in FIG. 1 and / or FIG. 14. That is, as described above, the memory of the present specification may store control information related to the operation of the STA of the present specification or information regarding signals transmitted and received by the STA (e.g., PPDU containing a management / control / data frame).
[0366] The technical features of this specification may be implemented in at least one computer-readable medium (CRM). The CRM includes instructions based on execution by at least one processor described above. Instructions stored in the CRM may be the computer program instructions described above.
[0367] The device of the present specification may further include a transceiver. The transceiver may be operabably connectable to the memory / processor, etc. The transceiver may be the transceiver illustrated in FIG. 1 and / or FIG. 14.
[0368] The technical features of the present specification described above are applicable to various applications or business models. For example, the technical features described above may be applied for wireless communication in devices supporting Artificial Intelligence (AI).
[0369] Artificial intelligence refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems addressed within the field of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.
[0370] An Artificial Neural Network (ANN) is a model used in machine learning that can refer to any model capable of problem-solving, composed of artificial neurons (nodes) that form a network through the connection of synapses. An artificial neural network can be defined by connection patterns between neurons in different layers, a learning process that updates model parameters, and an activation function that generates output values.
[0371] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer may include one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron may output a function value of an activation function for input signals, weights, and biases input through the synapses.
[0372] Model parameters refer to parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters, on the other hand, refer to parameters that must be set prior to training in a machine learning algorithm, including the learning rate, number of iterations, mini-batch size, and initialization function.
[0373] The objective of training an artificial neural network can be viewed as determining model parameters that minimize the loss function. The loss function can be used as an indicator to determine optimal model parameters during the training process of an artificial neural network.
[0374] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.
[0375] Supervised learning refers to a method of training an artificial neural network with labels provided for the training data; a label can refer to the correct answer (or result) that the neural network must infer when the training data is input. Unsupervised learning refers to a method of training an artificial neural network without labels provided for the training data. Reinforcement learning refers to a learning method in which an agent defined within an environment is trained to select an action or sequence of actions that maximizes the cumulative reward in each state.
[0376] Machine learning implemented using a Deep Neural Network (DNN) that includes multiple hidden layers among artificial neural networks is also called Deep Learning, and Deep Learning is a part of Machine Learning. Hereinafter, Machine Learning is used in a sense that includes Deep Learning.
[0377] In addition, the aforementioned technical features can be applied to the wireless communication of robots.
[0378] A robot can refer to a machine that automatically processes or operates a given task based on its own capabilities. In particular, a robot that has the ability to perceive its environment, make decisions on its own, and perform actions can be called an intelligent robot.
[0379] Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, and propellers in their drive units, enabling them to drive on the ground or fly in the air.
[0380] In addition, the aforementioned technical features can be applied to devices that support augmented reality.
[0381] Extended Reality is a collective term for Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on real-world images, and MR technology is a computer graphics technology that mixes and combines virtual objects with the real world.
[0382] MR technology is similar to AR technology in that it displays real-world objects and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual objects and real-world objects are used as equals in MR technology.
[0383] XR technology can be applied to HMDs (Head-Mount Displays), HUDs (Head-Up Displays), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.
Claims
1. Generate a PPDU (Physical Protocol Data Unit) containing data fields, The bandwidth of the above PPDU is 80 MHz, and The above data field is subjected to LDPC (Low-density parity check code), and The above data field includes an IM (interference mitigation) pilot having zero energy, and The above IM pilot is, Included from the first subcarrier index to the second subcarrier index at intervals of 10 subcarrier indices, It is included from the 3rd subcarrier index to the 4th subcarrier index at intervals of 10 subcarrier indices, and The first subcarrier index is -495, and the second subcarrier index is -5, and Step in which the third subcarrier index is 5 and the fourth subcarrier index is 495; and The step of transmitting the above PPDU A method including 2. In paragraph 1, including a pilot having non-zero energy, The subcarrier index of the above non-zero energy pilot is {-468, -400, -334, -266, -226, -158, -92, -24, 24, 92, 158, 226, 266, 334, 400, 468}. method.
3. In paragraph 2, the pilot having non-zero energy is a CFO (Carrier Frequency Offset) pilot. method.
4. The method of claim 1, wherein the data field comprises one 996-ton RU (resource unit).
5. In paragraph 1, preamble puncturing is not applied to the PPDU method.
6. In paragraph 1, the data field comprises five DC (direct current) tones method.
7. In paragraph 1, the PPDU further comprises a U-SIG (universal signal) field containing information regarding the 80 MHz bandwidth. method.
8. The above IM pilot includes, based on 78.125 kHz subcarrier spacing method.
9. Regarding STA(station), At least one processor; and It includes at least one computer memory that is operablely connectable to the at least one processor and stores instructions that perform an operation based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, Generate a PPDU (Physical Protocol Data Unit) containing data fields, The bandwidth of the above PPDU is 80 MHz, and The above data field is subjected to LDPC (Low-density parity check code), and The above data field includes an IM (interference mitigation) pilot having zero energy, and The above IM pilot is, Included from the first subcarrier index to the second subcarrier index at intervals of 10 subcarrier indices, It is packed from the 3rd subcarrier index to the 4th subcarrier index at intervals of 10 subcarrier indices, and The first subcarrier index is -495, and the second subcarrier index is -5, and Step in which the third subcarrier index is 5 and the fourth subcarrier index is 495; and The step of transmitting the above PPDU Performing an operation that includes STA.
10. In Paragraph 9 The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 1 to 8. STA.
11. Receive a PPDU (Physical Protocol Data Unit) containing a data field, The bandwidth of the above PPDU is 80 MHz, and The above data field is subjected to LDPC (Low-density parity check code), and The above data field includes an IM (interference mitigation) pilot having zero energy, and The above IM pilot is, Included from the first subcarrier index to the second subcarrier index at intervals of 10 subcarrier indices, It is included from the 3rd subcarrier index to the 4th subcarrier index at intervals of 10 subcarrier indices, and The first subcarrier index is -495, and the second subcarrier index is -5, and Step in which the third subcarrier index is 5 and the fourth subcarrier index is 495; and Step of interpreting the above PPDU A method including 12. In Paragraph 11 The STA (station) receiving the above PPDU performs an operation related to any one of claims 1 to 8. method.
13. Regarding STA(station), At least one processor; and It includes at least one computer memory that is operablely connectable to the at least one processor and stores instructions that perform an operation based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, Receive a PPDU (Physical Protocol Data Unit) containing a data field, The bandwidth of the above PPDU is 80 MHz, and The above data field is subjected to LDPC (Low-density parity check code), and The above data field includes an IM (interference mitigation) pilot having zero energy, and The above IM pilot is, Included from the first subcarrier index to the second subcarrier index at intervals of 10 subcarrier indices, It is included from the 3rd subcarrier index to the 4th subcarrier index at intervals of 10 subcarrier indices, and The first subcarrier index is -495, and the second subcarrier index is -5, and Step in which the third subcarrier index is 5 and the fourth subcarrier index is 495; and Step of interpreting the above PPDU Performing an operation that includes STA.
14. In Paragraph 13 The above STA performs an operation related to any one of claims 1 to 8. method.
15. In a wireless local area network (WLAN) system, at least one computer-readable medium comprising an instruction based on execution by at least one processor, Generate a PPDU (Physical Protocol Data Unit) containing data fields, The bandwidth of the above PPDU is 80 MHz, and The above data field is subjected to LDPC (Low-density parity check code), and The above data field includes an IM (interference mitigation) pilot having zero energy, and The above IM pilot is, Included from the first subcarrier index to the second subcarrier index at intervals of 10 subcarrier indices, It is included from the 3rd subcarrier index to the 4th subcarrier index at intervals of 10 subcarrier indices, and The first subcarrier index is -495, and the second subcarrier index is -5, and Step in which the third subcarrier index is 5 and the fourth subcarrier index is 495; and The step of transmitting the above PPDU Performing an operation that includes Recording media.