Reception of data unit, and detection related to type of received signal

Abstract

The present specification provides a method and a device for receiving an enhanced long range (ELR) PPDU. The reception device determines a preamble type of the PPDU on the basis of a detection failure of an RL-SIG field. If the preamble type is non-HT, the reception device performs parallel processing on fourth and fifth symbols after an L-SIG field. An ELR-MARK field is detected through the parallel processing. When the ELR-MARK field is detected, the reception device performs ELR preamble parsing on the PPDU. The ELR preamble parsing is performed on the basis of information of an ELR-SIG field. The reception device determines whether to filter or decode the PPDU on the basis of the information. Therefore, the ELR PPDU can be accurately identified and communication coverage can be extended without additional signaling overhead.

Description

Detection related to the reception of data units and the type of the received signal

[0001] This specification relates to wireless communication systems, and more specifically, to an improved receiving method in a wireless LAN system and a device supporting the same.

[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 may be expressed as follows.

[0007] For example, in the IEEE 802.11bn system, the newly defined Enhanced Long Range (ELR) PPDU has a different preamble structure from the existing PPDU, but a problem may arise in that the receiving procedure for the receiving STA to accurately identify and properly decode it is not specifically defined. In particular, in ambiguous situations where the detection of the Repeated L-SIG (RL-SIG) field fails or the received signal is determined to be a non-HT preamble, a sophisticated identification mechanism may be required to prevent the receiving end from misidentifying the ELR PPDU or improperly terminating the reception process.

[0008] Additionally, if separate dedicated signaling or control information is added to identify the presence of an ELR PPDU, there may be limitations in that system overhead increases and reception delays occur. Furthermore, if it is not possible to reliably determine in advance whether an ELR PPDU for uplink (UL) transmission has been received, a technical challenge may arise in that it is difficult to achieve the UL coverage extension and transmission reliability required in long-distance or poor channel environments.

[0009] Additionally, or generally, we aim to provide a new reception procedure that can efficiently detect the presence of an ELR-MARK field and verify its validity for a PPDU received by a UHR AP or STA while making full use of the existing L-SIG and RL-SIG structures. Specifically, by performing ELR-MARK detection in parallel with data symbol decoding to rapidly determine whether to parse the ELR preamble without additional signaling overhead, we aim to provide a solution that can maximize the utilization of ELR-based communication and system efficiency in both downlink (DL) and uplink transmissions.

[0010] The technical features of this specification may relate to the reception, decoding, filtering, etc. of a physical protocol data unit (PPDU). For example, the operations of this specification may be performed by an AP, a non-AP STA, etc. For example, the AP may be included in an AP MLD, and the non-AP STA may be included in a non-AP MLD.

[0011] A station (STA) of a wireless LAN system according to one embodiment of the present specification may receive a physical protocol data unit (PPDU). The STA may detect an RL-SIG field, which is a repetition of an L-SIG field. If the detection of the RL-SIG field fails, the STA may determine the preamble type of the PPDU based on the L-SIG field. If the preamble type is non-HT (non-High Throughput), the STA may perform parallel processing to detect an ELR-MARK field. The parallel processing may be performed on the 4th and 5th symbols following the L-SIG field. If the ELR-MARK field is detected by the parallel processing, the STA may perform ELR preamble parsing for the PPDU. The ELR-MARK field may include an orthogonal sequence associated with a basic service set (BSS) color. The above ELR preamble parsing step may include a step of evaluating information contained in the ELR-SIG field. The ELR-SIG field may be followed by UHR-STF and UHR-LTF. The STA may determine whether to filter the corresponding PPDU based on the information contained in the ELR-SIG field. If the information matches, the STA may perform decoding on the ELR-DATA field.

[0012] An example of this specification can achieve various technical effects. An example of such various technical effects is listed below.

[0013] For example, according to the reception procedure of a wireless LAN system proposed in this specification, detection performance and identification accuracy for the Enhanced Long Range (ELR) PPDU, newly defined in the IEEE 802.11bn standard, can be significantly improved. In particular, even in ambiguous situations where RL-SIG field detection fails or the received signal is determined to be in a legacy non-HT format, it is possible for the receiving end to perform reception processing more stably without misidentifying the ELR PPDU through a series of processes that check the ELR-MARK field at a specific symbol location after L-SIG.

[0014] Additionally or generally, by performing decoding of data symbols and parallel processing of the ELR-MARK field, the reception latency can be minimized and resource consumption efficiency can be increased through the technical means described in this specification. Instead of the receiving STA waiting for the entire reception process to determine the type of PPDU, unnecessary computation can be prevented by quickly determining whether it is an ELR using symbols at specific locations, and the effect of improving power efficiency can be expected by filtering out PPDUs that do not apply to it early on based on the STA-ID and uplink / downlink information within the ELR-SIG.

[0015] Additionally or generally, by adopting a method of soliciting ELR transmission via DL PPDU while making full use of existing L-SIG and RL-SIG structures, effective system control may be possible without additional signaling overhead according to the embodiments of this specification. This can contribute to improving overall data throughput by reducing the proportion of control information in a limited wireless resource environment, and can serve as a technical foundation for seamlessly integrating next-generation functions while minimizing mutual interference even in a coexistence environment with existing legacy devices.

[0016] Additionally or generally, by effectively inducing signal transmission utilizing ELR PPDU during uplink (UL) transmission, it may be possible to expand the service coverage and ensure transmission reliability of a wireless LAN system through the configuration disclosed herein. Even in environments with long-distance communication or poor channel conditions, the communication success rate can be increased through dedicated ELR preamble parsing and sequence detection; this can result in resolving dead zones that may occur within the entire Basic Service Set (BSS) and providing stable long-distance data connectivity.

[0017] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

[0018] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0019] Figure 3 is a diagram illustrating a general link setup process.

[0020] FIG. 4 illustrates an example of a multi-link (ML).

[0021] FIG. 5 illustrates a PPDU transmitted / received in an STA of the present specification.

[0022] Figure 6 is a diagram showing the arrangement of resource units (RU) used for a 20 MHz PPDU.

[0023] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0024] Figure 8 is a diagram showing the arrangement of resource units (RU) used for an 80 MHz PPDU.

[0025] Figure 9 shows the operation according to UL-MU.

[0026] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0027] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0028] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0029] Figure 13 shows an example of a MAC frame header.

[0030] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.

[0031] FIG. 15 shows an example of an ELR PPDU of the present specification.

[0032] FIG. 16 is a flowchart illustrating an example of the present specification.

[0033] FIG. 17 is another example of a flowchart illustrating an example of the present specification.

[0034] Figure 18 illustrates the operation / procedure related to the procedure for evaluating the U-SIG for a PPDU.

[0035] Figure 19 is another example of a procedure flowchart related to ELR preamble parsing.

[0036] FIG. 20 shows a part of the procedure flowchart of the present specification.

[0037] Figure 21 is another procedure flowchart illustrating the operation of detecting ELR-MARK in STA.

[0038] Figure 22 shows another example of ELR preamble parsing.

[0039] An example in Fig. 23 illustrates a procedure / operation / step related to UHR preamble parsing.

[0040] FIG. 24 is a flowchart illustrating an example of the present specification.

[0041] 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."

[0042] 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."

[0043] 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."

[0044] 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."

[0045] 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."

[0046] 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."

[0047] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

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

[0049] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0050] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

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

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

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

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

[0055] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.

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

[0057] 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.).

[0058] 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).

[0059] 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.).

[0060] 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).

[0061] 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).

[0062] 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).

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

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

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

[0066] 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).

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

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

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

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

[0071] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0072] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).

[0073] 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).

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

[0075] 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).

[0076] 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).

[0077] 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).

[0078] The bottom of Fig. 2 is a conceptual diagram showing IBSS.

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

[0080] Figure 3 is a diagram illustrating a general link setup process.

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

[0082] 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).

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

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

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

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

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

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

[0089] FIG. 4 illustrates an example of a multi-link (ML).

[0090] 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).

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

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

[0093] 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).

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

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

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

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

[0098] 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).

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

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

[0101] 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).

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

[0103] 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}.

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

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

[0106] 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 μs. 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.

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

[0108] 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".

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

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

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

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

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

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

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

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

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

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

[0119] 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).

[0120] 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).

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

[0122] 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 μs. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.

[0123] 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).

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

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

[0126] 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 are inserted into 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 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

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

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

[0129] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

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

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

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

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

[0134] 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).

[0135] 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).

[0136] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

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

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

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

[0140] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

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

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

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

[0144] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

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

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

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

[0148] The structure and types / subtypes of MAC frames are described below.

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

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

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

[0152] 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).

[0153] 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).

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

[0155] 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).

[0156] FIG. 14 shows a modified example of a transmitting device and / or receiving device of the present specification.

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

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

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

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

[0161] 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).

[0162] ELR PPDU

[0163] This specification proposes various technical features related to the transmission of ELR (extended long range or enhanced long range) PPDUs. The ELR PPDU may be changed to various names. For example, the ELR PPDU may be referred to by various names such as the first, second, TX, RX, ER (extended range), and UHR PPDU. The technical features of this specification are not limited to the name ELR PPDU.

[0164] FIG. 15 illustrates an example of an ELR PPDU of the present specification. For example, side view (a) of FIG. 15 illustrates an example of an ELR PPDU. As illustrated, the ELR PPDU may include L-STF (1505), L-LTF (1510), L-SIG (1515), RL-SIG (1520), U-SIG (1525), ELR-MARK (1530), UHR-STF (1535), UHR-LTF (1540), ELR-SIG (1545), and Data (1550). For example, some fields of FIG. 15 may be omitted. For example, the order of some fields of FIG. 15 may be changed. Each field disclosed in FIG. 15 may be referred to by various names such as signal / bit.

[0165] For example, the value of the number of spatial streams (e.g., Nss) for an ELR PPDU may be limited to 1. Additionally or generally, for example, an ELR PPDU has a fixed bandwidth of 20 MHz and can be used for both downlink and uplink in 2.4 GHz band operation, but only for uplink in 5 GHz and 6 GHz band operation. In other words, an ELR PPDU may consist only of 20 MHz and may not have bandwidths such as 40 / 80 / 160 / 320 MHz.

[0166] For example, the above L-SIG (1515) and / or RL-SIG (1520) may be identical to the L-SIG and RL-SIG described in FIG. 5. For example, the technical features of the L-SIG and RL-SIG described with respect to FIG. 5 may be equally applicable to the above L-SIG (1515) and / or RL-SIG (1520).

[0167] For example, the ELR-MARK (1530) of FIG. 15 may be composed of two OFDM symbols. The ELR-MARK (1530) may include information regarding an identifier (e.g., BSS_COLOR) indicating the BSS color to which the STA transmitting the corresponding PPDU belongs.

[0168] For example, the ELR-MARK field may include an identifier related to a BSS (basic service set) color. For example, the ELR-MARK field may include one of 64 orthogonal sequences corresponding to the BSS color. Alternatively, the ELR-MARK field may indicate a BSS color ID for the intended STA of the ELR PPDU. Alternatively, the ELR-MARK field may include an orthogonal sequence corresponding to the BSS color ID for the intended STA of the ELR PPDU. The orthogonal sequence may be set differently depending on the value of the BSS color ID. For example, in this specification, the ELR-MARK field may be referred to by various expressions such as ELR MARK, ELR MARK symbol, ELR MARK signal, etc.

[0169] For example, an example of this specification may relate to improvements to at least one of the fields of FIG. 15: U-SIG (1525), UHR-LTF (1540), ELR-SIG (1545), and Data (1550). Accordingly, further description of the remaining fields / signals, excluding the four fields / signals (1525, 1540, 1545, 1550), may be omitted below.

[0170] For example, the U-SIG (1525) may have the following features. For example, the U-SIG (1525) of this specification may be composed of a signal / field for an ELR PPDU. For example, a PPDU that is not an ELR PPDU (e.g., UHR MU PPDU or UHR TB PPDU) may also include the U-SIG, but the contents of the U-SIG (1525) of this specification may include different contents.

[0171] For example, the U-SIG (1525) of this specification has a length of 2 symbols, and each symbol may be represented as U-SIG-1 and U-SIG-2. For example, bits B0 to B2 of U-SIG-1 may have various names such as the first information or PHY Version Identifier described above, and may include a value (e.g., a value of 1) that identifies that the PHY version of the PPDU is UHR. For example, the positions of bits B0 to B2 may be changed.

[0172] Additionally or generally, bits B3 through B5 of U-SIG-1 may have various names such as the second information or BW information, and may include information regarding the bandwidth of the ELR PPDU. For example, bits B3 through B5 of U-SIG-1 may have only a value of 0. This is because it is desirable for the bandwidth of the ELR PPDU to be fixed at 20 MHz. For example, the positions of bits B3 through B5 may be changed.

[0173] Additionally or generally, the B6 bit of U-SIG-1 may contain information regarding whether the PPDU is transmitted to UL or DL. For example, the position of the B6 bit may be changed.

[0174] Additionally or generally, bits B7 through B12 of U-SIG-1 may represent the ID of the Basic Service Set (BSS). For example, bits B7 through B12 may include ID information (or BSS color information) of the BSS to which the STA transmitting / receiving the PPDU belongs. For example, the positions of bits B7 through B12 may be changed.

[0175] Additionally or generally, bits B13 through B19 of U-SIG-1 may contain information related to the duration of a TXOP (transmission opportunity). For example, the positions of bits B13 through B19 may be changed.

[0176] Additionally or generally, bits B20 through B24 of U-SIG-1 may all be set to 1, and the bits may be called disregard. For example, the positions of bits B20 through B24 may be changed.

[0177] Additionally or generally, the B25 bit of U-SIG-1 may be set to 1, and the bit may be called Validate. For example, the position of the B25 bit may be changed.

[0178] Additionally or generally, bits B0 to B1 of U-SIG-2 may have various names such as the third information or PPDU Type and Compression Mode. Bits B0 to B1 may always have a value of 3 regardless of whether the associated PPDU is a DL PPDU or a UL PPDU, thereby indicating / identifying that the PPDU is an ELR PPDU. For example, the positions of bits B0 to B1 may be changed.

[0179] Additionally or generally, bits B2 through B12 of U-SIG-2 may be composed of a STA ID. For example, bits B2 through B12 may be composed of some 11 bits (e.g., LSB 11 bits or MSB 11 bits) of the Association ID (AID) of the STA transmitting the PPDU. For example, the positions of bits B2 through B12 may be changed.

[0180] Additionally or generally, bits B13 through B15 of U-SIG-2 may be configured as ELR validate. These three bits may be used to identify the ELR PPDU, and these three bits may all be set to 1 (i.e., these three bits have a value of 7). For example, the positions of bits B13 through B15 may be changed.

[0181] Additionally or generally, bits B16 through B19 of U-SIG-2 may be composed of a CRC.

[0182] Additionally or generally, bits B20 through B25 of U-SIG-2 may be configured as a tail, so that all bits are zero.

[0183] For example, the UHR-LTF (1540) may have the following features. The UHR-LTF (1540) may be divided into a signal for ELR communication and a signal for non-ELR communication.

[0184] For example, the UHR-LTF (1540) may be constructed based on a sequence in which the first LTF sequence is duplicated four times in the frequency domain in 52-tone RU units. For example, the first LTF sequence may have a length of 52. For example, the non-zero elements of the first LTF sequence may be 52 in total. Additionally or alternatively, the UHR-LTF for the ELR communication may be constructed based on a 2x LTF sequence. The 2x LTF sequence may be defined in the range from index -122 to index +122.

[0185] For example, the ELR-SIG (1545) may have the following features. For example, the ELR-SIG (1545) of this specification may have two parts. Each part may be denoted as ELR-SIG-1 and ELR-SIG-2. For example, the B0 bit of ELR-SIG-1 may contain the first ER / ELR-SIG information or ELR Version Identifier described above. For example, the B0 bit of ELR-SIG-1 may contain information for identifying the ELR version, and the ELR Version Identifier included in the ELR PPDU having the technical features described in this specification may have a value of 0. For example, the position of the B0 bit may be changed.

[0186] Additionally or generally, the B1 bit of ELR-SIG-1 may contain a UL / DL field. For example, the bit may contain information regarding whether the ELR PPDU is transmitted as UL / DL. For example, the position of B1 may be changed.

[0187] Additionally or generally, the B2 bit of ELR-SIG-1 may contain an MCS field. For example, the bit may contain information related to MCS information applied to the data field of the ELR PPDU. For example, if the bit is set to a first value (e.g., 0), the bit may indicate that BPSK with a coding rate of 1 / 2 is applied to the data field of the ELR PPDU. For example, if the bit is set to a second value (e.g., 1), the bit may indicate that QPSK with a coding rate of 1 / 2 is applied to the data field of the ELR PPDU. For example, the position of B2 may be changed.

[0188] Additionally or generally, the B3 bit of ELR-SIG-1 may contain a coding (type) field. For example, the bit may contain information related to coding (type) information applied to the data field of the ELR PPDU. For example, if the bit is set to a first value (e.g., 0), the bit may indicate that the BCC technique is applied to the data field of the ELR PPDU. For example, if the bit is set to a second value (e.g., 1), the bit may indicate that the LDPC technique (e.g., LDPC having a word length of 648, 1296, or 1944) is applied to the data field of the ELR PPDU.

[0189] Additionally or generally, bits B4 through B12 of ELR-SIG-1 may contain a length field. For example, the length field may have a length of 9 bits, and the specific bit position may change. For example, the field may contain information regarding the number of symbols in the data field included in the ELR PPDU.

[0190] Additionally or generally, the B13 bit of ELR-SIG-1 may contain information regarding the presence of LDPC extra (OFDM) symbols. For example, such information may include information regarding whether additional OFDM symbols are required for LDPC encoding of the PPDU.

[0191] Additionally or generally, bits B14 through B17 of ELR-SIG-1 may include CRC bits, and bits B18 through B23 of ELR-SIG-1 may include tail bits and have a value of 0.

[0192] Additionally or generally, bits B0 through B10 of ELR-SIG-2 may contain information regarding the STA-ID. For example, the bits may consist of some 11 bits (e.g., LSB 11 bits or MSB 11 bits) of the AID of the STA transmitting the ELR PPDU. For example, the position of the bits may change.

[0193] Additionally or generally, bits B1 through B13 of ELR-SIG-2 may contain disregard fields / information. Each bit of the corresponding 3-bit fields / information may be set to 1.

[0194] Additionally or generally, bits B14 through B17 of ELR-SIG-2 may include CRC bits, and bits B18 through B23 of ELR-SIG-1 may include tail bits and have a value of 0.

[0195] For example, the Data (1550) field may be referred to by various names such as ER / ELR-Data, payload, etc. The Data (1550) field and ELR-SIG (1545) of this specification may be transmitted through four duplicated 52-tone RUs as described below.

[0196] For example, ELR-SIG-1 and ELR-SIG-2 included in ELR-SIG (1545) may each contain information of 24 bits in length (e.g., un-coded bits of 24 bits). BCC encoding at a 1 / 2 code rate may be applied to this information of 24 bits in length (e.g., un-coded bits of 24 bits) to generate coded bits of 48 bits in length. BPSK modulation may be applied to the coded bits to generate 48 BPSK symbols corresponding to ELR-SIG-1 and ELR-SIG-2, respectively. Four pilots are added to these 48 BPSK symbols to generate data corresponding to a total of 52 subcarriers / tones, and this data is included in a 52-tone RU. These 52-tone RUs can be transmitted through 52-tone RUs that are duplicated / repeated four times in the frequency domain (or through four duplicated 52-tone RUs).

[0197] For example, the information contained in Data (1550) can be mapped to a 52-tone RU based on BPSK or QPSK modulation. The 52-tone RU can be transmitted through a 52-tone RU that is duplicated / repeated four times in the frequency domain (or through four duplicated 52-tone RUs).

[0198] The ELR PPDU described above can resolve the signal transmission and reception range difference caused by TX power imbalance between the AP and non-AP STA. When transmitting and receiving signals using such an ELR PPDU, it may be necessary to define procedures and methods for efficient detection and reception of the ELR PPDU.

[0199] Accordingly, the present specification proposes technical features of a method and apparatus for receiving an ELR PPDU.

[0200] In order to successfully receive, detect, interpret, and decode ELR PPDUs in STA, various technical features must be defined. As an example of these various technical features, technical features related to ELR capability are described below.

[0201] In a UHR system, whether transmission and / or reception of ELR PPDU is supported can be determined by the capability of the STA (e.g., AP and / or non-AP STA). For example, the AP and non-AP STA can mutually indicate whether transmission and / or reception of signals using ELR PPDU is supported through the UHR capability.

[0202] Specifically, information regarding whether ELR PPDU is supported or whether ELR transmission is supported can be indicated through the UHR PHY Capabilities Information field. For example, the UHR PHY Capabilities Information field may include an ELR support field or an ELR PPDU field. The names of these fields can be determined in various ways, and in addition to the ELR support field and ELR PPDU field, they may have various names such as an ELR transmission support field / bit / subfield and an ELR reception support field / bit / subfield.

[0203] For example, the above ELR-related field / bit / subfield may have various bit lengths. For example, the above ELR-related field / bit / subfield may have a length of 1 bit. For example, if the value of the corresponding 1 bit is set to a first value (e.g., 1), it may indicate ELR transmission support. For example, if the value of the corresponding 1 bit is set to a second value (e.g., 0), it may indicate that ELR transmission is not supported.

[0204] FIG. 15 illustrates an example of a UHR PHY Capabilities Information field. For example, as shown in side view (b) of FIG. 15, at least one of the multiple subfields within the UHR PHY Capabilities Information field may indicate ELR transmission support. Additionally, or generally, a 1-bit information / subfield / bit indicating ELR reception support may be defined within the UHR PHY Capabilities Information field of FIG. 15.

[0205] A STA (e.g., ELR enable STA) that indicates support for the transmission and / or reception of ELR (or ELR PPDU) through the UHR PHY Capabilities Information field defined as above may perform the following operations to determine whether the received PPDU is an ELR PPDU or a non-ELR PPDU. The device performing the following operations may have various names such as STA, ELR-STA, ELR enable STA, non-AP STA, ELR enable non-AP STA, ELR non-AP STA, AP, ELR-AP, or ELR enable AP.

[0206] The above ELR-STA may utilize some existing procedures and methods for determining whether a received PPDU is an ELR PPDU. In other words, since the following example is an example of a situation where there is a possibility of receiving an ELR PPDU, the STA performing the following operation may indicate that it supports the reception of an ELR PPDU through a 1-bit subfield within the UHR PHY Capabilities Information field before performing the following operation. In other words, the STA performing the following operation transmits a management frame from the peer STA, wherein the management frame includes a UHR PHY Capabilities Information field, and the UHR PHY Capabilities Information field may include a 1-bit subfield indicating that it supports the reception of an ELR PPDU. The following operation may be performed based on the fact that the management frame described above has been transmitted to the peer STA.

[0207] FIG. 16 is a flowchart illustrating an example of the present specification.

[0208] As described, an STA (e.g., ELR-STA) can receive a PPDU (S1610). A specific layer or specific function of the STA can determine whether the PPDU is detected by the STA (S1620). If the PPDU is detected as a result (S1630), a check can be performed to determine whether the L-SIG included in the PPDU is repeated (S1640). In other words, the STA can check whether the L-SIG (1515) of FIG. 15 is repeated within the received PPDU. In other words, the STA can check whether the RL-SIG (1520), which is a repeat of the L-SIG (1515), exists within the received PPDU. For example, the RL-SIG (1520) can be received through the symbol immediately following the L-SIG (1510).

[0209] When a repeat of L-SIG is detected (S1660), the procedure / action marked B is performed, and the procedure / action marked B is described in more detail in FIG. 18.

[0210] If a repeat of L-SIG is not detected (S1670), the procedure / action marked A is performed, and the procedure / action marked A is described in more detail in FIG. 17.

[0211] FIG. 17 is another example of a flowchart illustrating an example of the present specification.

[0212] For example, the STA can determine the type of the preamble of the PPDU based on the SIG field of the received PPDU (e.g., the L-SIG (1515) field of FIG. 15) (S1705). For example, the type of the preamble may include non-HT, HT, VHT, etc. For example, the STA can determine the type of the preamble of the received PPDU based on the structure of at least one SIG field after the L-LTF (e.g., the L-LTF (1510) of FIG. 15). For example, since conventional non-HT PPDU, HT PPDU, and VHT-PPDU have different preamble structures, the STA can determine the type of the preamble based on the structure of the preamble of the received PPDU. For example, a non-HT PPDU has BPSK applied and a SIG with a single symbol length (e.g., L-SIG or non-HT SIG), and includes a Data field immediately following the SIG symbol; a conventional HT PPDU has QBPSK applied and a SIG with two symbol lengths (e.g., HT-SIG1 and HT-SIG2); and a conventional VHT-PPDU has BSPK applied and a SIG with a single symbol length (e.g., L-SIG or non-HT SIG), and has a structure in which the corresponding SIG field satisfies the condition LEN%3==0 and VHT-SIGA1 is located immediately following the corresponding SIG symbol. The STA can detect whether the preamble of the received PPDU has a non-HT, HT, or VHT type based on various conventional techniques (e.g., L-SIG field) (S1705).

[0213] For example, if the type of the preamble is detected as HT (i.e., if the PPDU is detected as 11n PPDU), it may be indicated as S1760, and if the type of the preamble is detected as VHT (i.e., if the PPDU is detected as 11ac PPDU), it may be indicated as S1765.

[0214] Meanwhile, in various operations / procedures of FIG. 17 such as S1720, S1740, and S1775, whether the SIG field (e.g., the L-SIG field (1515) of FIG. 15) is valid or invalid can be determined by various criteria, for example, by whether the parity check for the L-SIG is successful.

[0215] The following describes the case where the repetition check fails as a result of performing the L-SIG repetition check (in other words, the case where L-SIG is valid and RL-SIG is not detected). In other words, the detailed operation / procedure shown in FIG. 17 is described.

[0216] Operations / procedures related to S1760 and S1775:

[0217] In this case, the ELR-STA determines the received PPDU as an 11n PPDU (or HT PPDU) through PPDU classification. However, the corresponding SIG (e.g., HT-SIG) may be determined to be invalid. That is, this case can be expressed as "Detected as 11n but HT-SIG is invalid".

[0218] Operations / procedures related to S1765 and S1775:

[0219] In this case, the ELR-STA determines the received PPDU to be an 11ac PPDU (or VHT PPDU) through PPDU classification. However, the corresponding SIG (e.g., VHT-SIG) may be determined to be invalid. That is, this case can be expressed as "Detected as 11ac but VHT-SIG is invalid".

[0220] For example, in the situations of S1760 to S1775, and / or in the situations of S1765 to S1775, the ELR-STA may not set PHY-RXEND.indication (FormatViolation). Specifically, the ELR-STA may wait for the reception of one OFDM symbol (e.g., 4 μs duration) after receiving an HT-SIG symbol (or VHT-SIG) symbol in order to perform ELR-MARK detection after receiving an ELR-MARK symbol, and then perform ELR-MARK detection based on the two OFDM symbols received at that time. In other words, the ELR-STA may perform the operation of S1780.

[0221] In other words, if the HT-SIG (or VHT-SIG) is invalid, the ELR-STA may perform ELR-MARK detection after receiving up to the point where the ELR-MARK symbol defined in the ELR PPDU is received. If an ELR-MARK is detected, the corresponding PPDU may be identified as an ELR PPDU, and in this case, the ELR PPDU reception procedure may be performed. The above case may correspond to S1790. If an ELR-MARK is not detected, the ELR-STA may set PHY-RXEND.indication (FormatViolation) to stop receiving and decoding PPDUs. The above case may correspond to S1785.

[0222] Additionally, or generally, another operation / procedure shown in FIG. 17 is described.

[0223] Operations / procedures related to S1710, S1715, and S1740:

[0224] An L-SIG may be detected within the received PPDU and determined to be valid. In other words, the ELR-STA can detect the type of the preamble of the received PPDU (S1705). If the ELR-STA detects the type of the preamble as non-HT (S1710), the ELR-STA can evaluate the L-SIG included in the PPDU (S1715). If the L-SIG is determined to be invalid, the operation / procedure of S1720 is performed, and if the L-SIG is determined to be valid, the operation / procedure of S1740 may be performed. As previously described, whether the L-SIG is valid can be determined in various ways; for example, validity can be determined by checking the parity bit included within the L-SIG.

[0225] For example, in the case of S1740, the ELR-STA can perform parallel processing for the 5 symbols following L-SIG for ELR PPDU detection (S1745). In this case, the received PPDU may be an 11a PPDU (or a non-HT PPDU, or an IEEE 802.11a PPDU), or the received PPDU may be an ELR-PPDU. Considering both of these cases is one of the technical features of this specification. Accordingly, the ELR-STA can perform the conventional 11a data processing procedure (or the data field decoding procedure of a non-HT PPDU) for the 5 OFDM symbols following L-SIG, and the ELR-MARK detection processing procedure for the 4th OFDM symbol and the 5th OFDM symbol following L-SIG. As described above, since two processing steps (e.g., 11a data processing and ELR-MARK detection processing) are performed simultaneously, it can be said that ELR-MARK detection processing can be performed based on parallel processing.

[0226] For example, an ELR-STA that performs ELR mark detection based on S1740 may not perform separate reception processing for the three OFDM symbols (e.g., the first OFDM symbol, the second OFDM symbol, and the third OFDM symbol) received after L-SIG, and may perform ELR-Mark detection for the fourth and fifth OFDM symbols received thereafter. In other words, ELR-MARK detection processing based on parallel processing may not be performed for the first / second / third OFDM symbols after L-SIG, but may be performed for the fourth / fifth OFDM symbols after L-SIG.

[0227] For example, an ELR-STA (or an ELR-STA that has performed S1740) that has performed parallel processing for the previously described 11a data processing (or non-HT data processing, or IEEE 802.11a data processing) and ELR mark detection may stop the 11a data processing (or non-HT data processing) and perform ELR PPDU processing if it is detected as an ELR PPDU according to the ELR mark detection result. The ELR PPDU processing may be an operation / procedure according to S1755, and an example of such processing is described in FIG. 19. For example, if it is not detected as an ELR PPDU according to the ELR mark detection result, the ELR-STA may continue the execution of 11a data processing.

[0228] Additionally, or generally, another operation / procedure shown in FIG. 17 is described.

[0229] Operations / procedures related to S1710, S1715, and S1720:

[0230] For example, the ELR-STA may detect the reception of a PPDU via the reception of an L-STF but may not receive a valid SIG field. For instance, this case may be expressed as "SIG field is not valid or not detected." In this case, the procedure / operation of S1725 may be executed. Specifically, for ELR mark detection, the ELR-STA may receive the signal up to the time interval in which the ELR-mark symbol is received, and then perform ELR-MARK detection. Specifically, that is, if the L-SIG is invalid, the ELR-STA may not set PHY_RXEND.indication(CarrierLost) in order to receive the OFDM symbol following the L-SIG.

[0231] Based on S1725, the ELR-STA can perform ELR-MARK detection using the 4th and 5th OFDM symbols among the 5 OFDM symbols received after L-SIG. If the received PPDU is determined to be an ELR PPDU through such ELR-MARK detection, the procedure / operation of S1735 can be performed. An example of the procedure / operation is described in FIG. 19. In other words, if the received PPDU is determined to be an ELR PPDU according to S1725, the ELR-STA can decode the received PPDU by following the ELR PPDU reception procedure. Conversely, if the received PPDU is not determined to be an ELR PPDU according to S1725, the ELR-STA can set PHY_RXEND.indication(CarrierLost) (S1730). Through this, the reception procedure for the received PPDU may not be performed any further.

[0232] Below, specific procedures / operations related to the case where a repeat of L-SIG is detected in FIG. 16 (S1660) are explained with reference to FIG. 18. FIG. 18 describes the operations / procedures related to the procedure for evaluating U-SIG for PPDU.

[0233] For example, the case described below can be described as a case where RL-SIG is detected and L-SIG is valid as a result of performing an L-SIG repetition check, and the related case can be described by an example such as FIG. 18. Alternatively, if a repeat of L-SIG is detected based on the result of the L-SIG repetition check (S1660 or S1805), the ELR-STA can evaluate L-SIG (S1810). If there are no errors in the Rate bit and parity bit included in L-SIG (S1815), the ELR-STA can distinguish whether the received PPDU is an 11ax PPDU (e.g., HE PPDU) or an 11be&11bn PPDU (e.g., EHT PPDU and UHR PPDU) using the length field of L-SIG. This operation can be described as S1820.

[0234] Specifically, in an EHT / UHR PPDU, the LENGTH field is set to a value that satisfies the condition that the remainder is zero when LENGTH is divided by 3. This remainder is used to distinguish an EHT / UHR PPDU from an HE PPDU.

[0235] Accordingly, the operation can distinguish whether the received PPDU is an 11ax PPDU (e.g., HE PPDU) or an 11be&11bn PPDU (e.g., EHT PPDU and UHR PPDU) based on whether the remainder is zero (0) when LENGTH is divided by 3, as in S1820. Based on the relationship below, 11be / bn PPDU and 11ax PPDU can be distinguished.

[0236] LEN%3 == 0 (11be or 11bn) , LEN%3 ≠ 0 (11ax)

[0237] If a received PPDU is determined to be 11ax using the method described above, the ELR-STA does not perform ELR mark detection on the received PPDU. An ELR-PPDU is a PPDU defined in the higher-level wireless LAN standard, 11bn / UHR. Accordingly, for a PPDU detected as an 11ax PPDU, the ELR-STA receives the PPDU by applying the previously defined 11ax PPDU reception procedure. The above case may correspond to a situation where it is not treated as S1825.

[0238] Meanwhile, for cases such as the following, the following actions / procedures may be performed. The following actions / procedures may be related to S1825 and / or S1830.

[0239] 11Be / Bn detected ( LEN%3 = 0) but U-SIG is invalid

[0240] As in the case above, if U-SIG is invalid, it may mean that the CRC check failed after receiving the U-SIG. In this case, since the U-SIG content is invalid, information about the PPDU cannot be identified through the U-SIG information. Therefore, when U-SIG is invalid, the ELR-STA can perform ELR-MARK detection on the subsequent two OFDM symbols without setting PHY_RXEND.indication(FormatViolation), unlike before. The ELR-STA, having performed ELR-MARK detection using the two OFDM symbols following the U-SIG as described above, can perform the reception procedure for the ELR PPDU if the detection result determines that the received PPDU is an ELR PPDU. An example of the reception procedure for an ELR PPDU can be explained in Fig. 19. Conversely, if it is not an ELR PPDU, the ELR-STA sets PHY_RXEND.indication(FormatViolation) or filters out the PPDU.

[0241] In the above example, after determining the packet through the length field, if the received PPDU is determined to be an 11be / bn PPDU, the ELR-STA may not perform the detection procedure for the ER preamble defined in 11be (or may skip the detection procedure) and may only determine the validity of the U-SIG.

[0242] The operations / procedures related to S1835 and / or S1840 are described below.

[0243] 11be / bn detected ( LEN%3 = 0) but U-SIG is valid

[0244] For example, if a PPDU received according to S1825, etc. is detected as an 11Be / Bn PPDU and U-SIG is determined to be valid through S1830 and S1835, the following operation / procedure may be problematic.

[0245] In this case, the ELR-STA can identify the fields / bits (version, BW, TXOP, BSS color, PPDU type and transmission mode, DL / UL, puncturing, etc.) of the received PPDU using information from the U-SIG. When the version Identifier among the fields / bits is zero (specifically, when the PHY version is indicated as EHT), the reception procedure for the PPDU for the previously determined 11be (or EHT) is performed.

[0246] Additionally or generally, when the value of the Version identifier included in the U-SIG is one (1) and the value of the PPDU Type and compression mode subfield included in the U-SIG is three (3), the ELR-STA can perform ELR-Mark detection on the two OFDM symbols after the U-SIG. In other words, S1845 can be performed based on the Version identifier and the Type and compression mode subfield.

[0247] When the value of the above Version identifier is one (1), the value indicates UHR, and when the value of the above Type and compression mode subfield is three (3), the value indicates ELR PPDU (format) among UHR PPDUs. Therefore, when the above conditions are satisfied, it is desirable to perform ELR-Mark detection on the two OFDM symbols after the above U-SIG. Through the above ELR mark detection, the ELR-STA determines whether the received PPDU is an ELR PPDU and information about the BSS that transmitted the received PPDU.

[0248] Additionally or generally, if the identifier has a value of 1 (1) and the PPDU Type and compression mode subfield has a value other than 3 (3), the ELR-STA may not perform ELR mark detection. In this case, the ELR-STA may recognize the received PPDU as a UHR PPDU (or non-ELR PPDU) and decode the PPDU by following the reception procedure.

[0249] Additionally or generally, the operation in the case where the value of the Version identifier included in the above U-SIG is one (1) and the value of the PPDU Type and compression mode subfield included in the above U-SIG is three (3) can be performed as follows. Specifically, when the Version identifier is 1 and the PPDU Type and compression mode subfield is set to 3, the ELR-STA can determine whether to perform a reception procedure for the received ELR PPDU and perform ELR mark detection based on at least one of the validate bits and STA-ID among the contents of the U-SIG. For example, if the STA-ID information / field / subfield / bit included in the U-SIG of the received PPDU does not match (or does not match) the ID of the corresponding ELR-STA, the PPDU may be filtered out without performing ELR-mark detection for the received PPDU. As another example, if the validate bit does not match (or does not match), the reception procedure for the ELR PPDU may be performed by performing ELR-mark detection for the received PPDU. The above operation can be realized through the operations of S1850 to S1865.

[0250] FIG. 19 is a flowchart illustrating a specific example of the ELR PPDU processing described above. In various examples including FIG. 17 and FIG. 18 described above, the ELR-STA can determine whether it is an ELR PPDU through ELR-mark detection, and if it is determined to be an ELR PPDU through ELR mark detection, it can perform ELR PPDU processing. In this specification, the expression "ELR PPDU processing" may be referred to by various names such as ELR preamble parsing, ELR parsing, ELR DATA decoding, and ELR decoding. Specific operations / procedures according to this specification are described below with reference to FIG. 19.

[0251] As in S1905, through ELR mark detection, the ELR-STA can verify information about the BSS that transmitted the received PPDU. In other words, the ELR-MARK (1530) shown in FIG. 15, etc., may include identification information about the BSS of the received PPDU. If the information about the BSS verified through the ELR Mark is different from the associated BSS of the ELR-STA that received the PPDU, the received PPDU may be filtered out and no further reception procedure may be performed (S1910).

[0252] For example, as in S1915, when the result of the ELR-STA’s associated BSS and ELR mark detection is the same (or matches), the ELR-STA can perform a receiving procedure for the ELR-SIG using the ELR-STF (or UHR-STF) and ELR-LTF (or UHR-LTF) received after the ELR-MARK (S1920). More specifically, the ELR-STA can perform receiving / decoding for the ELR-SIG (1545) based on the STF (1535) and / or LTF (1540) shown in FIG. 15, etc.

[0253] Specifically, the ELR-STA can perform a validation check (e.g., CRC check) on ELR-SIG1 (or the first symbol / part of the ELR-SIG field). For example, if the CRC check is successful, it can determine whether to filter out the received PPDU using the various beeps / fields within the previously described ELR-SIG1 (e.g., DL / UL, ELR version identifier bits / fields) (S1935). For example, if filtering out is performed on the PPDU, the ELR-STA can defer PPDU reception or channel access using the length information included in ELR-SIG1 (S1940).

[0254] Additionally or generally, if the corresponding CRC check fails, the PPDU can be filtered out (S1925). In this case, the length field information of the L-SIG / the TXOP information of the U-SIG can be used to wait or power save during the PPDU reception period, or to defer channel access.

[0255] For example, if the PPDU is not filtered out after validation for ELR-SIG1, validation for ELR-SIG2 may be performed (S1945 and S1950). For example, if success for the CRC check is confirmed, ELR-STA may determine whether the received PPDU is a PPDU for the corresponding ELR-STA based on bits / fields / subfields (e.g., STA-ID bits / fields) within ELR-SIG2 (S1960 and S1965). If the received PPDU is a PPDU for ELR-STA, ELR DATA decoding may be performed based on the information of the received ELR-SIG1 and ELR-SIG2 (S1975, S1980).

[0256] In contrast, if the STA-ID bit / field is not for the ELR-STA, the ELR-STA can filter out the PPDU (S1970). In this case, the reception of the PPDU or channel access can be deferred using the length information included in ELR-SIG1.

[0257] Meanwhile, if the preceding CRC check fails, the STA-ID information of ELR-SIG2 cannot be used (S1955). In this case, ELR-STA can filter out the PPDU. In this case, ELR-STA can use the length information included in ELR-SIG1 to wait or power save during the PPDU reception period, or defer channel access.

[0258] FIG. 20 illustrates a part of the procedure flowchart of the present specification. The step of FIG. 20 is performed when certain conditions in FIG. 17 through FIG. 19 are satisfied, and may be related, for example, to an operation where no further PPDU reception or decoding is performed.

[0259] The individual steps, procedures, and actions shown in the examples of the foregoing specification do not all need to be performed. For example, for the effective decoding of an ELR PPDU, some of the steps, procedures, and actions described above may be omitted, and additional steps, procedures, and actions may be inserted between the individual steps, procedures, and actions described above.

[0260] For example, an example of this specification is described once again based on some of the steps / procedures / actions described in FIGS. 16 and 17 described above. The following actions may be identical to the steps / procedures / actions already described through FIGS. 16 to 20.

[0261] Figure 21 is another procedure flowchart illustrating the operation of detecting ELR-MARK in STA.

[0262] As with S2110, the ELR-STA can detect RL-SIG. S2110 may correspond to S1640 of FIG. 16. As previously described, RL-SIG is a repeat of L-SIG. As shown in FIG. 15, etc., the L-SIG is the first symbol after L-LTF, and the RL-SIG is the second symbol after L-LTF. Accordingly, S2110 and / or S1640 may include a step of determining whether the first symbol after the L-LTF symbol and the second symbol after the L-LTF symbol are the same.

[0263] The case where RL-SIG is not detected by S2110 can be described as a "repetition failed" case. When RL-SIG is not detected or a repetition failed is confirmed, as in S2115, the ELR-STA can determine the preamble type of the received PPDU. This process can be described as a process of detecting SIG for non-HT, HT, or VHT, as in S2120. Alternatively, according to S2120, the ELR-STA detects SIG and can determine whether the preamble type of the received PPDU corresponds to a non-HT type, HT type, or VHT type. Accordingly, S2120 can correspond to S1705 of FIG. 17. For example, in the case of a "repetition failed" (e.g., a failure in the L-SIG repetition check), the STA (e.g., ELR STA) can detect the phase rotation of the two symbols following the L-SIG. For example, if Q-BPSK (Quadrature Phase Shift Keying) modulation is detected in both the first and second symbols following L-SIG, the preamble type of the received PPDU may correspond to the HT type. For example, if BPSK (Binary Phase Shift Keying) modulation is detected in the first symbol following L-SIG and Q-BPSK modulation is detected in both of the second symbols following L-SIG, the preamble type of the received PPDU may correspond to the VHT type. For example, such phase rotation as described above may be applied when the rate information / field included within the L-SIG is 6 Mbps. As described above, the step of S2120 is an operation related to L-SIG, and various symbols / information including L-SIG (e.g.It may be performed based on the two symbols following L-SIG, but may not be performed based solely on L-SIG. For example, if it is expressed in this specification that the preamble type is determined based on L-SIG, the operation may be interpreted as various operations related to L-SIG as described above.

[0264] For example, if a Non-HT preamble is determined according to S2110, the ELR-STA can perform data processing suitable for the non-HT preamble. For example, since the non-HT PPDU includes a Data field after L-SIG, the ELR-STA can perform data decoding according to the non-HT specification (or 11a data decoding). Accordingly, S2125 can correspond to S1745 of FIG. 17.

[0265] For example, ELR-STA can perform S2140 based on Parallel Processing together with S2125. Specifically, ELR-STA can perform Parallel Processing on the 4th and 5th symbols after L-SIG according to S2140. In other words, ELR-STA can determine whether ELR-MARK is included in the 4th and 5th symbols after L-SIG according to S2140. In other words, ELR-STA can determine whether ELR-MARK is detected from the 4th and 5th symbols after L-SIG according to S2140. Accordingly, S2140 can correspond to S1745 of FIG. 17.

[0266] For example, ELR-STA may not be detected by ELR-MARK as a result of Parallel Processing according to S2140 (S2145). This case of S2145 may correspond to S1750 in FIG. 17. In this case, ELR-STA may continue non-HT data processing such as in step S2125 (S2150).

[0267] For example, the ELR-STA can detect the ELR-MARK based on the result of Parallel Processing according to S2140 (S2155). This case of S2155 may correspond to S1755 of FIG. 17. In this case, the ELR-STA can perform ELR preamble parsing (S2160), and this ELR preamble parsing may be explained by an example such as FIG. 19 or FIG. 22.

[0268] For example, if an HT preamble is determined according to S2110, the ELR-STA can perform data processing suitable for the HT preamble (S2130), and in this case, the operation of the ELR-STA can be expressed in various ways. For example, the operation performed in S2130 may correspond to at least one of the operations performed in S1770, S1775, and S1780 of FIG. 17.

[0269] For example, if a VHT preamble is determined according to S2110, the ELR-STA can perform data processing suitable for the VHT preamble (S2135), and in this case, the operation of the ELR-STA can be expressed in various ways. For example, the operation performed in S2135 may correspond to at least one of the operations performed in S1770, S1775, and S1780 of FIG. 17.

[0270] FIG. 22 illustrates another example of ELR preamble parsing. Individual steps / actions / procedures of FIG. 19 may be represented in various ways, and some steps / actions / procedures of FIG. 19 may be omitted. An example in FIG. 22 is an example of an example in FIG. 19 represented in a different way.

[0271] As in step S2210, the ELR-STA can receive ELR-SIG-1 (or the first symbol / part of the ELR-SIG-1 or ELR-SIG field). Additionally, the ELR-STA can test the CRC of ELR-SIG-1 through step S2210. This feature of step S2210 can correspond to S1920 in FIG. 19.

[0272] For example, passing the CRC test according to step S2210 can be expressed as S2215.

[0273] As in step S2220, the ELR-STA can evaluate UL / DL information / bits / fields included in ELR-SIG-1 (or the first symbol / part of the ELR-SIG1 or ELR-SIG fields). This feature of step S2220 may correspond to S1935 in FIG. 19. For example, it can be determined whether the UL / DL information / bits / fields included in ELR-SIG-1 are identical to the value intended by the ELR-STA. In other words, it can be determined whether the corresponding PPDU is filtered out based on whether the UL / DL information / bits / fields match (or are identical to) the intended value (S2220).

[0274] For example, the case where the evaluation according to step S2220 is passed can be expressed as S2225. This case can correspond to S1945 in FIG. 19.

[0275] As in step S2230, the ELR-STA can receive ELR-SIG-2 (or the second symbol / part of the ELR-SIG-2 or ELR-SIG field). Additionally, the ELR-STA can test the CRC of ELR-SIG-2 through step S2230. This feature of step S2230 can correspond to S1950 in FIG. 19.

[0276] For example, passing the CRC test according to step S2230 can be expressed as S2235.

[0277] As in step S2240, the ELR-STA can evaluate the STA-ID information / bits / fields included in the ELR-SIG-2. This feature of step S2240 may correspond to S1965 in FIG. 19. For example, it can be determined whether the STA-ID information / bits / fields included in the ELR-SIG-2 are identical to the STA-ID of the ELR-STA. In other words, it can be determined whether the corresponding PPDU is filtered out based on whether the STA-ID information / bits / fields match (or are identical to) an intended value (S2240).

[0278] For example, the case where the evaluation according to step S2240 is passed can be expressed as S2245. This case can correspond to S1975 in FIG. 19.

[0279] If the evaluation according to step S2240 is passed, the ELR-STA can perform data processing on the ELR-PPDU to decode the data fields of the ELR-PPDU (S2250). This case may correspond to S1980 of FIG. 19.

[0280] The procedure described in FIG. 18 can also be expressed in various other ways. For example, the operation / procedure / step of FIG. 18 can also be described based on FIG. 23.

[0281] An example in Fig. 23, like an example in Fig. 18, describes a procedure / operation / step related to UHR preamble parsing.

[0282] For example, the ELR-STA can evaluate the Length information included in the L-SIG included in the received PPDU (S2310). For example, if the condition that the remainder is 0 when dividing the value corresponding to the Length information by 3 is satisfied (or LENGTH mod 3 == 0), the process can proceed to S2310.

[0283] If the evaluation of the Length included in the L-SIG passes, the ELR-STA can receive the U-SIG included in the received PPDU (S2320). As described above, the U-SIG includes a 4-bit CRC, and the ELR-STA can perform a test on the CRC.

[0284] For example, if the test for the CRC of the U-SIG is passed, the ELR-STA can check the 3-bit PHY version ID included in the U-SIG (S2330). As described above, the 3-bit PHY version ID included in the U-SIG indicates the PHY version of the PPDU, and for example, a value of zero (0) indicates EHT and a value of one (1) indicates UHR.

[0285] For example, if the PHY version ID of the bit has a value of 1 (1), the process may proceed to S2340. In S2340, the ELR-STA may determine whether to perform filter-out on the corresponding PPDU based on various bits / fields / information included in the U-SIG. For example, whether to perform filter-out on the corresponding PPDU may be determined based on at least one of various fields included in the U-SIG, such as the BSS color field, UL / DL field, and PPDU Type and compression mode field. More specifically, whether to perform filter-out on the corresponding PPDU may be determined based on whether the aforementioned various fields are identical to the values ​​intended by the ELR-STA.

[0286] For example, if filter-out for the PPDU is not performed in step S2340, the process may proceed to S2350. In S2350, the PPDU type of the received PPDU (e.g., ELR PPDU type, Trigger-based PPDU type, MU PPDU type, etc.) can be determined. For example, based on the value of the PPDU Type and compression mode subfield included in U-SIG being three (3), the PPDU type of the received PPDU can be determined to be an ELR PPDU.

[0287] For example, if the PPDU type is determined to be an ELR PPDU at step S2350, entry into S2360 is possible. In this case, the ELR-STA checks the (ELR) Validate bits included in the U-SIG (S2360), and if the validation performed based on the Validate bits passes, entry into S2370 is possible.

[0288] In S2370, the ELR-STA can determine whether the STA-ID included in the U-SIG is identical to the intended STA-ID (or matches the intended STA-ID). If the STA-ID included in the U-SIG is identical to the intended STA-ID (or matches the intended STA-ID), detection of the ELR-MARK included in the PPDU can be skipped, as in step S2380. The information included in the ELR-MARK is identification information for the BSS; if it is confirmed that the information included in the received UHR-SIG is accurate, there may not be a need to perform additional detection of the ELR-MARK separately. Accordingly, if step S2370 is passed, ELR-MARK detection may be skipped or not performed.

[0289] If ELR-MARK Detection is skipped or not performed, ELR STA can perform normal ELR Preamble parsing (S2390)

[0290] An example of FIG. 23 is an example of a different representation of an example of FIG. 18. For example, S2310 is an example of a different representation of the operation described in S1820 to S1825, etc. of FIG. 18. For example, S2320 is an example of a different representation of the operation described in S1830, etc. of FIG. 18. For example, S2330 and S2340 are examples of different representations of the operation described in S1840, etc. of FIG. 18. For example, S2350 is an example of a different representation of the operation described in S1845, etc. of FIG. 18. For example, S2360 is an example of a different representation of the operation described in S1840, etc. of FIG. 18. For example, S2370 to S2380 may correspond to the operation described in S1850, etc. of FIG. 18. For example, as described in FIG. 18, when the PHY Version identifier is 1 and the PPDU Type and compression mode subfield is set to 3, the ELR-STA can determine whether to perform a reception procedure for the received ELR PPDU and perform ELR mark detection based on at least one of the validate bits and STA-ID among the contents of the U-SIG. This operation of FIG. 18 can be individually represented by S2330 to S2380 of FIG. 23.

[0291] FIG. 24 is a flowchart illustrating an example of the present specification.

[0292] As in S2410, the STA can detect the RL-SIG (repeated L-SIG) field, which is a repeat of the L-SIG (legacy signal) field included in the PPDU (physical protocol data unit). This feature of S2410 may correspond to S2110 and S2115 in FIG. 21, or to S1610 through S1640 in FIG. 16. For example, the PPDU may include an L-LTF (legacy long training field). For example, the L-SIG field may be included in the first symbol after the L-LTF, and the RL-SIG may be included in the second symbol after the L-LTF. For example, the L-SIG field may be indicated as the SIG field.

[0293] Detecting the RL-SIG (repeated L-SIG) field according to S2410 can be implemented in various ways. For example, for S2410, the STA can determine whether the first symbol after the L-LTF and the second symbol after the L-LTF are identical. For example, if it is determined that the first symbol and the second symbol are identical, the detection of the RL-SIG field may be determined to be successful. For example, if it is determined that the first symbol and the second symbol are not identical, the detection of the RL-SIG field may be determined to be a failure.

[0294] As in S2420, based on the failure of detection of the RL-SIG field, the STA can determine the preamble type of the PPDU. This feature of S2420 may correspond to S1650 in FIG. 16 and S1705 in FIG. 17. Alternatively, this feature of S2420 may correspond to S2120 in FIG. 21.

[0295] For example, in S2420, the STA can determine the preamble type of the PPDU as one of non-HT, HT, or VHT. Specifically, the STA can determine the preamble type of the PPDU based on bit information included in the L-SIG of the PPDU.

[0296] As with S2430, based on the fact that the preamble type of the PPDU is non-HT (non-High Throughput), the STA can perform parallel processing on the 4th and 5th symbols after the L-SIG field to detect the Enhanced Long Range Mark (ELR) field. This feature of S2430 corresponds to S2125 and S2140 of FIG. 21, or to S1710, S1715, S1740, and S1745 of FIG. 17. In other words, the STA can decode / process the received PPDU based on the non-HT type, and at the same time detect whether the 4th and 5th symbols after the L-SIG within the received PPDU contain an ELR-MARK field. For example, since detection of the ELR-MARK field is performed simultaneously with decoding / processing based on the non-HT type, it can be said that detection of the ELR-MARK field is performed based on (or by) parallel processing. For example, it is preferable that detection of the ELR-MARK field be performed only for the 4th and 5th symbols after L-SIG. For example, if the PPDU is of the non-HT type, since a data field (e.g., non-HT Data) is located immediately after the L-SIG field, the STA can perform parallel processing for detection of the ELR-MARK field while simultaneously performing decoding / processing for the data field that may be included after L-SIG.

[0297] For example, the ELR-MARK has a length of two symbols as previously described and includes an identifier associated with a BSS (basic service set) color, and the ELR mark field may include one of 64 orthogonal sequences corresponding to the BSS color.

[0298] As in S2440, based on the detection of the ELR-MARK field by the parallel processing, the STA can perform ELR preamble parsing for the PPDU. If the ELR-MARK field is not detected by the parallel processing, the STA can continue the previously described non-HT data processing.

[0299] The features of the above S2440 may correspond to S2155 and S2160 of FIG. 21, or to S1755 of FIG. 17.

[0300] In addition, the ELR preamble parsing of S2440 may include various technical features. For example, some steps illustrated in FIG. 19 may be included in the ELR preamble parsing of S2440. For example, all or part of the steps illustrated in FIG. 22 may be included in the ELR preamble parsing of S2440.

[0301] For example, the ELR preamble parsing of S2440 may include a step of evaluating information contained in the ELR-SIG (Enhanced Long Range signal) field. For example, operations including S2220 and S22440 of FIG. 22 may be included in the ELR preamble parsing. For example, some of the operations of S1935 and S1965 of FIG. 19 may be included in the ELR preamble parsing. Specifically, the ELR preamble parsing may include a step of determining whether to filter out the PPDU based on UL / DL (uplink / downlink) information and STA-ID (station identifier) ​​information contained in the ELR-SIG field. In addition, for example, if the UL / DL (uplink / downlink) information and STA-ID (station identifier) ​​information included in the ELR-SIG field match, the STA can perform decoding / processing of the ELR-DATA field included in the PPDU. In other words, decoding / processing of S1980 of FIG. 19 or S2250 of FIG. 22 can be performed.

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

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

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

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

[0306] 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.).

[0307] 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).

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

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

[0310] 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).

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

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

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

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

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

[0316] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.

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

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

[0319] In addition, the aforementioned technical features can be applied to the wireless communication of robots.

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

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

[0322] In addition, the aforementioned technical features can be applied to devices that support augmented reality.

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

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

[0325] 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. A method performed by a STA (station) of a wireless LAN system, A step of detecting an RL-SIG (repeated L-SIG) field, which is a repeat of the L-SIG (legacy signal) field included in a PPDU (physical protocol data unit); A step of determining the preamble type of the PPDU based on the failure of detection of the RL-SIG field; Based on the fact that the preamble type of the above PPDU is non-HT (non-High Throughput), a step of performing parallel processing on the 4th and 5th symbols after the L-SIG field to detect the ELR (Enhanced Long Range MARK) field; and A step of performing ELR preamble parsing for the PPDU based on the detection of the ELR mark field by the parallel processing above. A method including 2. In paragraph 1, the PPDU includes an L-LTF (legacy long training field), the L-SIG field is included in the first symbol after the L-LTF, and the RL-SIG is included in the second symbol after the L-LTF. method.

3. In paragraph 2, the STA determines whether the first symbol after the L-LTF and the second symbol after the L-LTF are identical, and Based on the fact that the first symbol and the second symbol are identical, the RL-SIG field is detected, method.

4. In Paragraph 1, Based on the fact that the preamble type of the above PPDU is non-HT (non-High Throughput), the above STA detects whether the 4th and 5th symbols after the L-SIG field contain an ELR mark field while decoding the data symbols after the above L-SIG field, method.

5. In Paragraph 1, ELR preamble parsing for the above PPDU is performed when the ELR mark field is included in the 4th and 5th symbols after the L-SIG field by the above parallel processing, method.

6. In Paragraph 1, The above ELR mark field includes an identifier related to the BSS (basic service set) color, and The above ELR mark field includes one of 64 orthogonal sequences corresponding to the above BSS color, method.

7. In Paragraph 1, The above ELR preamble parsing is, It includes a step of evaluating information contained in the ELR-SIG (Enhanced Long Range signal) field included in the above PPDU, and The above ELR-SIG field follows the UHR-STF (ultra-high reliability long short field) and UHR-LTF (ultra-high reliability long training field) included in the above PPDU, method.

8. In Paragraph 7, The above ELR preamble parsing is, The method includes a step of determining whether to filter out the PPDU based on UL / DL (uplink / downlink) information and STA-ID (station identifier) ​​information included in the ELR-SIG field. method.

9. In Paragraph 8, If the UL / DL (uplink / downlink) information and STA-ID (station identifier) ​​information included in the above ELR-SIG field match, the STA performs decoding of the ELR-DATA field included in the above PPDU, and The above ELR-DATA field follows the above ELR-SIG field, method.

10. 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 operations based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, A step of detecting an RL-SIG (repeated L-SIG) field, which is a repeat of the L-SIG (legacy signal) field included in a PPDU (physical protocol data unit); A step of determining the preamble type of the PPDU based on the failure of detection of the RL-SIG field; Based on the fact that the preamble type of the above PPDU is non-HT (non-High Throughput), a step of performing parallel processing on the 4th and 5th symbols after the L-SIG field to detect the ELR (Enhanced Long Range MARK) field; and A step of performing ELR preamble parsing for the PPDU based on the detection of the ELR mark field by the parallel processing above. Performing an operation that includes STA.

11. In Paragraph 10, The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 2 to 9. STA 12. 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, A step of detecting an RL-SIG (repeated L-SIG) field, which is a repeat of the L-SIG (legacy signal) field included in a PPDU (physical protocol data unit); A step of determining the preamble type of the PPDU based on the failure of detection of the RL-SIG field; Based on the fact that the preamble type of the above PPDU is non-HT (non-High Throughput), a step of performing parallel processing on the 4th and 5th symbols after the L-SIG field to detect the ELR (Enhanced Long Range MARK) field; and A step of performing ELR preamble parsing for the PPDU based on the detection of the ELR mark field by the parallel processing above. Performing an operation that includes Recording media.

Images