Link setting for multi-link operation

Abstract

The invention provides a link setting for multi-link operation. In a wireless local area network (LAN) system, an STA of a multilink device (MLD) may transmit, in a link setting step, MAC addresses of other STAs included in the same MLD as the STA.

Description

[0001] This application is a divisional application of patent application No. 202080094947.7 (PCT / KR2020 / 017243), filed on July 28, 2022, with the title of "Link Setup for Multi-Link Operation", and a filing date of November 30, 2020. TECHNICAL FIELD

[0002] The present specification relates to a link setup method for multi-link operation in a wireless local area network (WLAN) system. BACKGROUND

[0003] Wireless network technology can include various types of wireless local area networks (WLANs). WLANs employ widely used network protocols and can be used to interconnect devices that are in proximity together. The various technical features described herein can be applied to any communication standard, such as WiFi, or more generally, any one of the IEEE 802.11 family of wireless protocols. Wireless local area networks (WLANs) have been enhanced in various ways. For example, the IEEE 802.11ax standard has proposed an enhanced communication environment by using orthogonal frequency division multiple access (OFDMA) and a downlink multi-user multiple-input multiple-output (DL MU MIMO) scheme.

[0004] The present specification proposes technical features that can be used in a new communication standard. For example, the new communication standard can be an Extremely High Throughput (EHT) standard that is currently under discussion. The EHT standard can use newly proposed increased bandwidth, enhanced PHY layer protocol data unit (PPDU) structure, enhanced sequence, hybrid automatic repeat request (HARQ) scheme, etc. The EHT standard can be referred to as the IEEE 802.11be standard. SUMMARY

[0005] TECHNICAL SOLUTION

[0006] The method performed by a transmitting device in a wireless local area network (WLAN) system according to various embodiments of the present disclosure can include technical features related to a link setup method for multi-link operation. A method performed by a receiving multi-link device (MLD) in a wireless local area network (WLAN) system is proposed, where the receiving MLD device includes a first station (STA) and a second STA, the first STA operates on a first link, and the second STA operates on a second link. The first STA can receive, from a transmitting MLD, multi-link information including information related to the first link and the second link. The first STA can transmit, to the transmitting MLD, multi-link address information. The multi-link address information can include a media access control (MAC) address of the second STA.

[0007] TECHNICAL EFFECT

[0008] According to the example of the present specification, after the multi-link setup, relevant information can be transmitted so that signals can be transmitted / received between the established links. In the multi-link setup phase, inter-link capability information is exchanged and information about which link to use for multi-link operation is exchanged, but a method of how to start signal transmission / reception in the link in which multi-link operation is performed has not been defined.

[0009] According to the example of the present specification, the STA performing the multi-link setup can transmit MAC address information of the STA performing the multi-link operation among other STAs included in the same MLD as the STA, and thus the counterpart can exchange signals with the STA.

[0010] According to the example of the present specification, the STA not performing the multi-link setup can directly transmit an initial frame. By including the MLD MAC address, the initial frame can notify that it is a STA of an MLD that has performed the multi-link setup. BRIEF DESCRIPTION OF DRAWINGS

[0011] Figure 1 Examples of a transmitting apparatus and / or a receiving apparatus of the present specification are illustrated.

[0012] Figure 2 is a conceptual view illustrating a structure of a wireless local area network (WLAN).

[0013] Figure 3 A general link setup procedure is illustrated.

[0014] Figure 4 An example of a PPDU used in IEEE standards is illustrated.

[0015] Figure 5 A layout of a resource unit (RU) used in a 20 MHz frequency band is illustrated.

[0016] Figure 6 A layout of an RU used in a 40 MHz frequency band is illustrated.

[0017] Figure 7 A layout of an RU used in an 80 MHz frequency band is illustrated.

[0018] Figure 8 A structure of an HE-SIG-B field is illustrated.

[0019] Figure 9 An example of allocating multiple user STAs to the same RU through a MU-MIMO scheme is illustrated.

[0020] Figure 10 An UL-MU based operation is illustrated.

[0021] Figure 11An example of a trigger frame is shown.

[0022] Figure 12 An example of a common information field of a trigger frame is shown.

[0023] Figure 13 An example of subfields included in a per-user information field is shown.

[0024] Figure 14 Technical features describing UORA schemes are described.

[0025] Figure 15 An example of channels used / supported / defined within the 2.4 GHz band is shown.

[0026] Figure 16 An example of channels used / supported / defined within the 5 GHz band is shown.

[0027] Figure 17 An example of channels used / supported / defined within the 6 GHz band is shown.

[0028] Figure 18 An example of a PPDU used in this specification is shown.

[0029] Figure 19 An example of a modified transmitting device and / or receiving device of this specification is shown.

[0030] Figure 20 An example of channel bonding is shown.

[0031] Figure 21 is a diagram illustrating an embodiment of a device supporting multi-link.

[0032] Figure 22 is a diagram illustrating an embodiment of STR capability of multi-link.

[0033] Figure 23 and Figure 24 is a diagram illustrating an embodiment of link information.

[0034] Figure 25 is an example of multi-link setup of the above basic procedure (A).

[0035] Figure 26 is a diagram illustrating an embodiment of MLD per STA MAC address field.

[0036] Figure 27 is a diagram illustrating an embodiment of MLD per STA MAC address element.

[0037] Figure 28 is a diagram illustrating an embodiment of multi-link element.

[0038] Figure 29FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0039] Figure 30 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0040] Figure 31 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0041] Figure 32 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0042] Figure 33 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0043] Figure 34 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0044] Figure 35 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0045] Figure 36 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0046] Figure 37 Figure 38 Figure 39 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0047] Figure 40 FIG. 1 is a diagram illustrating an embodiment of an ML IE.

[0048] Figure 41 FIG. 1 is a diagram illustrating an embodiment of an ML IE. DETAILED DESCRIPTION

[0049] In this specification, “A or B” can mean “only A”, “only B”, or “both A and B”. In other words, in this specification, “A or B” can be interpreted as “A and / or B”. For example, in this specification, “A, B, or C” can mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”.

[0050] A slash ( / ) or a comma used in this specification can mean “and / or”. For example, “A / B” can mean “A and / or B”. Thus, “A / B” can mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” can mean “A, B, or C”.

[0051] ​​In the present specification, "at least one of A and B" can mean "only A", "only B", or "both A and B". In addition, in the present specification, the expression "at least one of A or B" or "at least one of A and / or B" can be interpreted as "at least one of A and B".

[0052] In addition, in the present specification, "at least one of A, B, and C" can mean "only A", "only B", "only C", or "any combination of A, B, and C". In addition, "at least one of A, B, or C" or "at least one of A, B, and / or C" can mean "at least one of A, B, and C".

[0053] In addition, the brackets used in the present specification can mean "for example". Specifically, when indicated as "control information (EHT-signal)", it can mean that the "EHT-signal" is proposed as an example of the "control information". In other words, the "control information" of the present specification is not limited to the "EHT-signal", and the "EHT-signal" can be proposed as an example of the "control information". In addition, when indicated as "control information (i.e., EHT-signal)", it can also mean that the "EHT-signal" is proposed as an example of the "control information".

[0054] The technical features described in one drawing of the present specification can be implemented alone, or can be implemented simultaneously.

[0055] The following examples of the present specification can be applied to various wireless communication systems. For example, the following examples of the present specification can be applied to a wireless local area network (WLAN) system. For example, the present specification can be applied to IEEE 802.11a / g / n / ac standards or IEEE 802.11 ax standards. In addition, the present specification can also be applied to newly proposed EHT standards or IEEE 802.11 be standards. Furthermore, the examples of the present specification can also be applied to new WLAN standards enhanced from the EHT standards or the IEEE 802.11 be standards. In addition, the examples of the present specification can be applied to mobile communication systems. For example, it can be applied to mobile communication systems based on Long Term Evolution (LTE) depending on the 3rd Generation Partnership Project (3GPP) standards and evolution based on LTE. In addition, the examples of the present specification can be applied to communication systems based on the 5G NR standards of the 3GPP standards.

[0056] Hereinafter, in order to describe the technical features of the present specification, technical features applicable to the present specification will be described.

[0057] Figure 1 Examples of a transmitting apparatus and / or a receiving apparatus of the present specification are illustrated.

[0058] In Figure 1In the example of FIG. 1, various technical features described below can be implemented. Figure 1 A station (STA) is involved. For example, the STAs 110 and 120 of the present specification can also be referred to as various terms such as a mobile terminal, a wireless device, a wireless transmit / receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, or simply a user. The STAs 110 and 120 of the present specification can also be referred to as various terms such as a network, a base station, a node B, an access point (AP), a transponder, a router, a repeater, etc. The STAs 110 and 120 of the present specification can also be referred to as various names such as a reception apparatus, a transmission apparatus, a reception STA, a transmission STA, a reception device, a transmission device, etc.

[0059] For example, the STAs 110 and 120 can be used as an AP or a non-AP. That is, the STAs 110 and 120 of the present specification can be used as an AP and / or a non-AP.

[0060] In addition to the IEEE 802.11 standard, the STAs 110 and 120 of the present specification can support various communication standards together. For example, a communication standard based on a 3GPP standard (e.g., an LTE, an LTE-A, a 5G NR standard), etc. can be supported. In addition, the STAs of the present specification can be implemented as various devices such as a mobile phone, a vehicle, a personal computer, etc. In addition, the STAs of the present specification can support communication for various communication services such as a voice call, a video call, data communication, and self-driving (autonomous driving), etc.

[0061] The STAs 110 and 120 of the present specification can include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a radio medium.

[0062] Hereinafter, the STAs 110 and 120 will be described with reference to Figure 1 subfigure (a) of FIG. 1.

[0063] The first STA 110 can include a processor 111, a memory 112, and a transceiver 113. The illustrated processing, memory, and transceiver can be implemented as separate chips, or at least two blocks / functions can be implemented through a single chip.

[0064] The transceiver 113 of the first STA performs a signal transmission / reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.) can be transmitted / received.

[0065] For example, the first STA 110 can perform operations expected by the AP. For example, the processor 111 of the AP can receive a signal through the transceiver 113, process a received (RX) signal, generate a transmission (TX) signal, and provide control for signal transmission. The memory 112 of the AP can store a signal received through the transceiver 113 (e.g., an RX signal), and can store a signal to be transmitted through the transceiver (e.g., a TX signal).

[0066] For example, the second STA 120 can perform operations expected by the non-AP STA. For example, the transceiver 123 of the non-AP performs signal transmission / reception operations. Specifically, IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be packets, etc.) can be transmitted / received.

[0067] For example, the processor 121 of the non-AP STA can receive a signal through the transceiver 123, process an RX signal, generate a TX signal, and provide control for signal transmission. The memory 122 of the non-AP STA can store a signal received through the transceiver 123 (e.g., an RX signal), and can store a signal to be transmitted through the transceiver (e.g., a TX signal).

[0068] For example, operations of a device indicated as an AP in the specification described below can be performed in the first STA 110 or the second STA 120. For example, if the first STA 110 is an AP, operations of a device indicated as an AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operations of the AP or TX / RX signals of the AP can be stored in the memory 112 of the first STA 110. In addition, if the second STA 120 is an AP, operations of a device indicated as an AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operations of the AP or TX / RX signals of the AP can be stored in the memory 122 of the second STA 120.

[0069] For example, in the specification described below, the operation of the device indicated as a non-AP (or user STA) can be performed in the first STA 110 or the second STA 120. For example, if the second STA 120 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 121 of the second STA 120, and the relevant signal can be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the non-AP or the TX / RX signal of the non-AP can 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 indicated as a non-AP can be controlled by the processor 111 of the first STA 110, and the relevant signal can be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the non-AP or the TX / RX signal of the non-AP can be stored in the memory 112 of the first STA 110.

[0070] In the specification described below, a device referred to as a (transmitting / receiving) STA, a first STA, a second STA, STA1, STA2, an AP, a first AP, a second AP, AP1, AP2, a (transmitting / receiving) terminal, a (transmitting / receiving) device, a (transmitting / receiving) apparatus, a network, etc. can mean a STA 110 and 120 of Figure 1 In the specification described below, a device referred to as a (transmitting / receiving) STA, a first STA, a second STA, STA1, STA2, an AP, a first AP, a second AP, AP1, AP2, a (transmitting / receiving) terminal, a (transmitting / receiving) device, a (transmitting / receiving) apparatus, a network, etc. can mean a STA 110 and 120 of Figure 1 In the specification described below, a device referred to as a (transmitting / receiving) STA, a first STA, a second STA, STA1, STA2, an AP, a first AP, a second AP, AP1, AP2, a (transmitting / receiving) terminal, a (transmitting / receiving) device, a (transmitting / receiving) apparatus, a network, etc. can mean a STA 110 and 120 of Figure 1 In the specification described below, a device referred to as a (transmitting / receiving) STA, a first STA, a second STA, STA1, STA2, an AP, a first AP, a second AP, AP1, AP2, a (transmitting / receiving) terminal, a (transmitting / receiving) device, a (transmitting / receiving) apparatus, a network, etc. can mean a STA 110 and 120 of Figure 1The operations are executed in processors 111 and 121. Examples of operations for generating TX / RX signals or pre-performing data processing and calculations may include: 1) operations to determine / obtain / configure / calculate / decode / encode bit information of subfields (SIG, STF, LTF, data) included in the PPDU; 2) operations to determine / configure / obtain time resources or frequency resources (e.g., subcarrier resources) for the subfields (SIG, STF, LTF, data) included in the PPDU; 3) operations to determine / configure / obtain specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for the subfields (SIG, STF, LTF, data) included in the PPDU; 4) power control operations and / or power-saving operations applied to the STA; and 5) operations related to the determination / obtaining / configuration / decoding / encoding of the ACK signal. Additionally, in the following examples, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs to determine / obtain / configure / calculate / decode / decode the TX / RX signal may be stored in the STA's memory. Figure 1 In memory 112 and 122.

[0071] Figure 1 The aforementioned device / STA in subgraph (a) can be as follows Figure 1 The subgraph (b) is modified as shown below. In the following text, the modifications will be based on... Figure 1 The sub-diagram (b) is used to describe STA 110 and STA120 in this specification.

[0072] For example, Figure 1 The transceivers 113 and 123 shown in subgraph (b) can perform operations with Figure 1 The transceiver shown in sub-diagram (a) has the same function as the aforementioned transceiver. For example, Figure 1 The processing chips 114 and 124 shown in sub-figure (b) may include processors 111 and 121 and memories 112 and 122. Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (b) can perform operations related to Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (a) have the same functions.

[0073] The mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, user, subscriber STA, network, base station, node B, access point (AP), repeater, router, relay, receiving unit, transmitting unit, receiving STA, transmitting STA, receiving device, transmitting device, receiving apparatus and / or transmitting apparatus described below may meanFigure 1 The STA 110 and 120 shown in subgraphs (a) / (b) may mean, or Figure 1 The processing chips 114 and 124 are shown in sub-figure (b). That is to say, the technical features of this specification can be found in... Figure 1 It can be performed in STA 110 and 120 as shown in subgraphs (a) / (b), or it can be performed only in Figure 1 The processing chips 114 and 124 shown in sub-diagram (b) are executed Figure 1 Transceivers 113 and 123 are shown in sub-diagrams (a) and (b). For example, the technical features of transmitting control signals by a STA can be understood as being achieved through... Figure 1 The transceiver 113 shown in sub-diagrams (a) / (b) transmits in Figure 1 The technical features of the control signals generated in processors 111 and 121 are illustrated in sub-figures (a) and (b). Alternatively, the technical features of the STA transmitting control signals can be understood as follows: Figure 1 The technical features of generating control signals to be transmitted to transceivers 113 and 123 in processing chips 114 and 124 are shown in sub-figure (b).

[0074] For example, the technical characteristics of receiving STA control signals can be understood as through... Figure 1 The technical features of transceivers 113 and 123 receiving control signals are shown in sub-figure (a). Alternatively, the technical features of receiving STA control signals can be understood as being achieved through... Figure 2 Processors 111 and 121 shown in subgraph (a) obtain Figure 2 The technical features of the control signals received in transceivers 113 and 123 shown in sub-figure (a) are illustrated. Alternatively, the technical features of receiving control signals by the STA can be understood as being achieved through... Figure 2 The processing chips 114 and 124 shown in sub-figure (b) obtain Figure 2 Technical features of the control signals received in transceivers 113 and 123 as shown in sub-figure (b).

[0075] Reference Figure 2 Subgraph (b), software codes 115 and 125 can be included in memories 112 and 122. Software codes 115 and 126 can include instructions for controlling the operation of processors 111 and 121. Software codes 115 and 125 can be included in various programming languages.

[0076] Figure 2 The processors 111 and 121 or processing chips 114 and 124 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example,Figure 3 The processors 111 and 121 or processing chips 114 and 124 of the electronic device 100 can include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, Figure 3 The processors 111 and 121 or processing chips 114 and 124 of the electronic device 100 can be a SNAPDRAGON™ processor series manufactured by Qualcomm®, an EXYNOS™ processor series manufactured by Samsung®, an A series manufactured by Apple®, a HELIO™ processor series manufactured by MediaTek®, an ATOM™ processor series manufactured by Intel®, or a processor enhanced from these processors.

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

[0078] Figure 3 is a conceptual diagram showing a structure of a wireless local area network (WLAN).

[0079] Figure 4 The upper portion of shows a structure of an Institute of Electrical and Electronics Engineers (IEEE) 802.11 infrastructure basic service set (BSS).

[0080] Referring to the upper portion of Figure 4 The BSSs 200 and 205, which are a set of APs and STAs (e.g., an access point (AP) 225 and a station (STAl) 200-1) that successfully synchronize to communicate with each other, are not a concept indicating a specific area. The BSS 205 can include one or more STAs 205-1 and 205-2 that can join one AP 230.

[0081] The BSS can include at least one STA, an AP providing a distributed service, and a distribution system (DS) 210 connecting a plurality of APs.

[0082] Distributed system 210 can implement an Extended Service Set (ESS) 240 that is expanded by connecting multiple BSSs 200 and 205. ESS 240 can be used as a term to refer to a network configured by connecting one or more APs 225 or 230 via distributed system 210. APs included in an ESS 240 can have the same Service Set Identifier (SSID).

[0083] Portal 220 can be used as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0084] exist Figure 4 The BSS shown at the top allows for networking between APs 225 and 230, as well as between APs 225 and 230 and STAs 200-1, 205-1, and 205-2. However, it also allows for networking between STAs to perform communication even without APs 225 and 230. Networks that enable communication between STAs by configuring networks even without APs 225 and 230 are defined as self-organizing networks or Independent Basic Service Sets (IBSS).

[0085] Figure 4 The lower part shows a conceptual diagram illustrating the IBSS.

[0086] Reference Figure 5 The lower part of the IBSS is a BSS that operates in a self-organizing mode. Since the IBSS does not include access points (APs), there is no centralized management entity performing management functions at the center. That is, in the IBSS, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 can be composed of mobile STAs, and access to DS to form a self-contained network is not permitted.

[0087] Figure 5 The diagram illustrates the typical link establishment process.

[0088] In S310, the STA can perform network discovery operations. Network discovery operations can include scanning operations by the STA. That is, in order to access a network, the STA needs to discover participating networks. The process of identifying compatible networks before joining a wireless network and identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0089] Figure 5The network discovery operation includes an active scanning process. In active scanning, the STA performing the scan sends a probe request frame and waits for a response to the probe request frame in order to identify which APs are present around while moving to a channel. The responder sends a probe response frame to the STA that has sent the probe request frame as a response to the probe request frame. Here, the responder can be the STA that has sent the last beacon frame in the BSS of the channel being scanned. In a BSS, the AP is the responder since the AP sends the beacon frame. In an IBSS, the responder is not fixed since the STAs in the IBSS take turns sending the beacon frame. For example, when a STA sends a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA can store the BSS-related information included in the received probe response frame, can move to the next channel (e.g., channel 2), and can perform scanning by the same method (e.g., sending a probe request via channel 2 and receiving a probe response).

[0090] Although Figure 5 Scanning can be performed by a passive scanning method, which is not shown in FIG. 3. In passive scanning, the STA performing the scan can wait for a beacon frame while moving to a channel. The beacon frame is one of the management frames in IEEE 802.11 and is periodically transmitted to indicate the presence of a wireless network and enable the STA performing the scan to find and join the wireless network. In a BSS, the AP is used to periodically transmit the beacon frame. In an IBSS, the STAs in the IBSS take turns transmitting the beacon frame. Upon receiving the beacon frame, the STA performing the scan stores information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. The STA that has received the beacon frame can store the BSS-related information included in the received beacon frame, can move to the next channel, and can perform scanning in the next channel by the same method.

[0091] After discovering the network, the STA can perform an authentication process in S320. The authentication process can be referred to as a first authentication process to clearly distinguish from a security setup operation in S340 later. The authentication process in S320 can include a process in which the STA sends an authentication request frame to the AP and the AP sends an authentication response frame to the STA in response. The authentication frame for authentication request / response is a management frame.

[0092] The authentication frame can include information about an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), and a finite cyclic group.

[0093] The STA can send an authentication request frame to the AP. The AP can determine whether to allow authentication of the STA based on information included in the received authentication request frame. The AP can provide the STA with the authentication process result via an authentication response frame.

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

[0095] In S340, the STA can perform security establishment processing. The security establishment processing in S340 can include processing in which a private key is established through a four-way handshake (e.g., through an extensible authentication protocol over LAN (EAPOL) frame).

[0096] Figure 5 An example of a PPDU used in IEEE standards is illustrated.

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

[0098] Figure 5 An example of an HE PPDU according to IEEE 802.11ax is also included. According to The HE PPDU of Figure 6 The HE PPDU is an exemplary PPDU for multiple users. The HE-SIG-B can be included only in a PPDU for multiple users, and the HE-SIG-B can be omitted in a PPDU for a single user.

[0099] As Figure 5As illustrated, the HE-PPDU for multiple users (MU) can include a legacy short training field (L-STF), a legacy long training field (L-LTF), a legacy signal (L-SIG), a high efficiency signal A (HE-SIG A), a high efficiency signal B (HE-SIGB), a high efficiency short training field (HE-STF), a high efficiency long training field (HE-LTF), a data field (alternatively, a MAC payload), and a packet extension (PE) field. Each field can be transmitted within the illustrated time period (i.e., 4 or 8 μs).

[0100] Hereinafter, a resource unit (RU) for a PPDU is described. The RU can include a plurality of subcarriers (or tones). The RU can be used to transmit a signal to a plurality of STAs according to OFDMA. In addition, the RU can also be defined to transmit a signal to one STA. The RU can be used for an STF, an LTF, a data field, etc.

[0101] Figure 6 A layout of a resource unit (RU) used in a 20 MHz frequency band is illustrated.

[0102] As Figure 6 illustrated, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) can be used to form some fields of the HE-PPDU. For example, resources can be allocated for the HE-STF, the HE-LTF, and the data field in the illustrated RUs.

[0103] As Figure 5 illustrated in the uppermost part, 26 units (i.e., units corresponding to 26 tones) can be provided. Six tones can be used for a guard band in the leftmost frequency band of the 20 MHz frequency band, and five tones can be used for a guard band in the rightmost frequency band of the 20 MHz frequency band. In addition, seven DC tones can be inserted in a center frequency band (i.e., a DC frequency band), and 26 units corresponding to 13 tones in each of the left and right sides of the DC frequency band can be provided. 26 units, 52 units, and 106 units can be allocated to other frequency bands. Each unit can be allocated to a receiving STA (i.e., a user).

[0104] Figure 7 The layout of the RUs in Figure 5 illustrated in the lowermost part.

[0105] Although Figure 6RUs of various sizes, i.e., 26-RU, 52-RU, 106-RU, and 242-RU, are proposed, but a specific size of RU can be extended or added. Accordingly, the present embodiment is not limited to each RU of a specific size (i.e., the number of corresponding tones).

[0106] Figure 7 A layout of RUs used in a 40 MHz band is illustrated.

[0107] Similarly to using RUs of various sizes Figure 7 , in the example of Figure 8 , 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. can be used. In addition, five DC tones can be inserted in the center frequency, 12 tones can be used for a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used for a guard band in the rightmost band of the 40 MHz band.

[0108] As Figure 8 indicated, when the layout of RUs is used for a single user, 484-RU can be used. The specific number of RUs can be changed similarly to Figure 5 .

[0109] Figure 5 A layout of RUs used in an 80 MHz band is illustrated.

[0110] Similarly to using RUs of various sizes Figure 5 and Figure 8 , in the example of Figure 9 , 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. can be used. In addition, seven DC tones can be inserted in the center frequency, 12 tones can be used for a guard band in the leftmost band of the 80 MHz band, and 11 tones can be used for a guard band in the rightmost band of the 80 MHz band. In addition, 26-RU corresponding to 13 tones of each of the left and right sides of the DC band can be used.

[0111] As Figure 9 indicated, when the layout of RUs is used for a single user, 996-RU can be used, in which case five DC tones can be inserted.

[0112] The RUs described in this specification can be used in uplink (UL) communication and downlink (DL) communication. For example, when performing UL-MU communication requested by a trigger frame, a transmitting STA (e.g., an AP) can allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and can allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA through the trigger frame. Thereafter, the first STA can transmit a first trigger-based PPDU based on the first RU, and the second STA can transmit a second trigger-based PPDU based on the second RU. The first / second trigger-based PPDUs are transmitted to the AP at the same (or overlapping) time period.

[0113] For example, when configuring a DL MU PPDU, a transmitting STA (e.g., an AP) can allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and can allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA. That is, the transmitting STA (e.g., an AP) can transmit an HE-STF, an HE-LTF, and a data field for the first STA through a first RU in one MU PPDU, and can transmit an HE-STF, an HE-LTF, and a data field for the second STA through a second RU.

[0114] Information about the layout of the RUs can be signaled through the HE-SIG-B.

[0115] Figure 9 The structure of the HE-SIG-B field is illustrated.

[0116] As illustrated, the HE-SIG-B field 810 includes a common field 820 and a user-specific field 830. The common field 820 can include information commonly applied to all users (i.e., user STAs) receiving the SIG-B. The user-specific field 830 can be referred to as a user-specific control field. When the SIG-B is transmitted to a plurality of users, the user-specific field 830 can be applied only to any one of the plurality of users.

[0117] As Figure 9 illustrated, the common field 820 and the user-specific field 830 can be separately encoded.

[0118] The common field 820 can include N*8-bit RU allocation information. For example, the RU allocation information can include information about the location of the RUs. For example, when a 20 MHz channel is used as Figure 8 illustrated, the RU allocation information can include information about a specific frequency band in which a specific RU (26-RU / 52-RU / 106-RU) is disposed.

[0119] An example of a case where RU allocation information consists of 8 bits is as follows.

[0120] [Table 1]

[0121]

[0122] As shown in the example of Figure 8 As shown in the example of Figure 9 In the example of

[0123] The example of Table 1 shows only some RU positions capable of displaying RU allocation information.

[0124] For example, the RU allocation information can include the example of the following Table 2.

[0125] [Table 2]

[0126]

[0127] "01000y2y1y0" relates to an example in which a 106-RU is allocated to the leftmost side of a 20 MHz channel, and five 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (e.g., user STAs) can be allocated to the 106-RU based on a MU-MIMO scheme. Specifically, up to 8 STAs (e.g., user STAs) can be allocated to the 106-RU, and the number of STAs (e.g., user STAs) allocated to the 106-RU is determined based on 3-bit information (y2y1y0). For example, when the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., user STAs) allocated to the 106-RU based on the MU-MIMO scheme can be N+1.

[0128] Generally, a plurality of STAs (e.g., user STAs) different from each other can be allocated to a plurality of RUs. However, a plurality of STAs (e.g., user STAs) can be allocated to one or more RUs having at least a certain size (e.g., 106 subcarriers) based on a MU-MIMO scheme.

[0129] As shown in the example of Figure 9As shown, the user-specific field 830 can include a plurality of user fields. As described above, the number of STAs (e.g., user STAs) allocated to a specific channel can be determined based on the RU allocation information of the common field 820. For example, when the RU allocation information of the common field 820 is "00000000", one user STA can be allocated to each of the nine 26-RUs (e.g., nine user STAs can be allocated). That is, up to 9 user STAs can be allocated to a specific channel through an OFDMA scheme. In other words, up to 9 user STAs can be allocated to a specific channel through a non-MU-MIMO scheme.

[0130] For example, when the RU allocation is set to "01000y2y1y0", a plurality of STAs can be allocated to the 106-RU arranged at the leftmost side through an MU-MIMO scheme, and five user STAs can be allocated to the five 26-RUs arranged at the right side thereof through a non-MU MIMO scheme. This case is illustrated by an example of Figure 9 .

[0131] Figure 9 An example of allocating a plurality of user STAs to the same RU through an MU-MIMO scheme is illustrated.

[0132] For example, when the RU allocation as Figure 10 shown is set to "01000010", the 106-RU can be allocated to the leftmost side of a specific channel, and the five 26-RUs can be allocated to the right side thereof. In addition, three user STAs can be allocated to the 106-RU through an MU-MIMO scheme. As a result, since eight user STAs are allocated, the user-specific field 830 of the HE-SIG-B can include eight user fields.

[0133] The eight user fields can be represented in the order as Figures 11 to 13 shown. In addition, as shown in Figure 11 , two user fields can be implemented with one user block field.

[0134] Figure 11 The user fields as Figure 11 shown can be configured based on two formats. That is, the user fields related to an MU-MIMO scheme can be configured in a first format, and the user fields related to a non-MU-MIMO scheme can be configured in a second format. Referring to an example of Figure 11 , user field 1 to user field 3 can be based on the first format, and user field 4 to user field 8 can be based on the second format. The first format or the second format can include bit information of the same length (e.g., 21 bits).

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

[0136] For example, the first bits (i.e., B0-B10) in the user field (i.e., 21 bits) can include identification information (e.g., STA-ID, partial AID, etc.) of the user STA to which the corresponding user field is allocated. In addition, the second bits (i.e., B11-B14) in the user field (i.e., 21 bits) can include information related to spatial configuration. Specifically, examples of the second bits (i.e., B11-B14) can be as shown in Table 3 and Table 4 below.

[0137] [Table 3]

[0138]

[0139] [Table 4]

[0140]

[0141] As shown in Table 3 and / or Table 4, the second bits (e.g., B11-B14) can include information related to the number of spatial streams allocated to the plurality of user STAs allocated based on the MU-MIMO scheme. For example, when three user STAs are allocated based on the MU-MIMO scheme as shown in Figure 11 STS[1]=4, N_STS[2]=1, and N_STS[3]=1. That is, in the example of Figure 11 four spatial streams can be allocated to the user field 1, one spatial stream can be allocated to the user field 1, and one spatial stream can be allocated to the user field 3.

[0142] As shown in the examples of Table 3 and / or Table 4, the information related to the number of spatial streams for the user STA (i.e., the second bits, B11-B14) can consist of 4 bits. In addition, the information related to the number of spatial streams for the user STA (i.e., the second bits, B11-B14) can support up to eight spatial streams. In addition, the information related to the number of spatial streams for the user STA (i.e., the second bits, B11-B14) can support up to four spatial streams for one user STA.

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

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

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

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

[0147] The above-described example relates to the user field of the first format (format of the MU-MIMO scheme). An example of the user field of the second format (format of the non-MU-MIMO scheme) is as follows.

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

[0149] Figure 11UL-MU based operation is shown. As shown, a transmitting STA (e.g., an AP) can perform channel access by contention (e.g., backoff operation), and can transmit a trigger frame 1030. That is, the transmitting STA can transmit a PPDU including the trigger frame 1030. Upon receiving the PPDU including the trigger frame, a trigger-based (TB) PPDU is transmitted after a delay corresponding to a SIFS.

[0150] The TB PPDUs 1041 and 1042 can be transmitted at the same time period, and can be transmitted from a plurality of STAs (e.g., user STAs) having AIDs indicated in the trigger frame 1030. ACK frames 1050 for the TB PPDUs can be implemented in various forms.

[0151] Referring to Figure 12 Specific features of the trigger frame are described. Even if UL-MU communication is used, an orthogonal frequency division multiple access (OFDMA) scheme or a MU MIMO scheme can be used, and the OFDMA and MU-MIMO schemes can be used at the same time.

[0152] Figure 12 An example of the trigger frame is shown. Figure 13 The trigger frame allocates resources for uplink multi-user (MU) transmission, and can be transmitted, for example, from an AP. The trigger frame can be configured by a MAC frame, and can be included in a PPDU.

[0153] Figure 13 The various fields shown can be omitted in part, and another field can be added. In addition, the lengths of the various fields can be changed to be different from those shown in the drawing.

[0154] Figure 11 The frame control field 1110 of the trigger frame can include information about a MAC protocol version and additional additional control information. The duration field 1120 can include time information of a NAV configuration or information about an identifier (e.g., an AID) of a STA.

[0155] In addition, the RA field 1130 can include address information of a receiving STA of the corresponding trigger frame, and can be omitted, optionally. The TA field 1140 can include address information of a STA (e.g., an AP) that transmits the corresponding trigger frame. The common information field 1150 includes common control information applied to a receiving STA that receives the corresponding trigger frame. For example, a field indicating a length of an L-SIG field of an uplink PPDU transmitted in response to the corresponding trigger frame or information for controlling contents of a SIG-A field (i.e., a HE-SIG-A field) of the uplink PPDU transmitted in response to the corresponding trigger frame can be included. In addition, as the common control information, information about a length of a CP of the uplink PPDU transmitted in response to the corresponding trigger frame or information about a length of an LTF field can be included.

[0156] In addition, the trigger frame preferably includes a per-user information field 1160#1 to 1160#N corresponding to the number of receiving STAs of the trigger frame. Figure 13 The per-user information field can also be referred to as an "allocation field".

[0157] In addition, Figure 13 The trigger frame can include a padding field 1170 and a frame check sequence field 1180.

[0158] Figure 5 Each of the per-user information fields 1160#1 to 1160#N illustrated can include a plurality of subfields.

[0159] Figure 6 An example of a common information field of a trigger frame is illustrated. Figure 7 The subfields can be partially omitted, and additional subfields can be added. In addition, lengths of the respective subfields illustrated can vary.

[0160] The length field 1210 illustrated has the same value as a length field of an L-SIG field of an uplink PPDU transmitted in response to the corresponding trigger frame, and the length field of the L-SIG field of the uplink PPDU indicates a length of the uplink PPDU. As a result, the length field 1210 of the trigger frame can be used to indicate the length of the corresponding uplink PPDU.

[0161] In addition, the concatenation identifier field 1220 indicates whether a concatenation operation is performed. The concatenation operation means that a downlink MU transmission and an uplink MU transmission are performed together in the same TXOP. That is, it means that a downlink MU transmission is performed, and thereafter an uplink MU transmission is performed after a preset time (e.g., SIFS). During the concatenation operation, only one transmitting device (e.g., an AP) can perform downlink communication, and a plurality of transmitting devices (e.g., non-APs) can perform uplink communication.

[0162] The CS request field 1230 indicates whether or not the state of the wireless medium or the NAV, etc. must be considered in case the receiving device of the corresponding trigger frame transmits the corresponding uplink PPDU.

[0163] The HE-SIG-A information field 1240 can include information for controlling the contents of the SIG-A field (i.e., the HE-SIG-A field) of the uplink PPDU in response to the corresponding trigger frame.

[0164] The CP and LTF type field 1250 can include information on the CP length and the LTF length of the uplink PPDU transmitted in response to the corresponding trigger frame. The trigger type field 1260 can indicate the purpose of using the corresponding trigger frame, such as a typical trigger, a trigger for beamforming, a request for a block ACK / NACK, etc.

[0165] It can be assumed that the trigger type field 1260 of the trigger frame in the present specification indicates a basic type of trigger frame for a typical trigger. For example, the basic type of trigger frame can be referred to as a basic trigger frame.

[0166] Figure 13 An example of subfields included in the per-user information field is illustrated. Figure 13 The user information field 1300 can be understood as any one of the per-user information fields 1160#1 to 1160#N mentioned above with reference to Figure 14 The subfields included in the user information field 1300 of Figure 14 may be partially omitted, and additional subfields can be added. In addition, the length of each of the illustrated subfields can be changed.

[0167] Figure 13 The user identifier field 1310 indicates an identifier of the STA (i.e., the receiving STA) corresponding to the per-user information. An example of the identifier can be all or part of the association identifier (AID) value of the receiving STA.

[0168] In addition, the RU allocation field 1320 can be included. That is, when the receiving STA identified through the user identifier field 1310 transmits the TB PPDU in response to the trigger frame, the TB PPDU is transmitted through the RU indicated by the RU allocation field 1320. In this case, the RU indicated by the RU allocation field 1320 can be Figure 13 、 Figure 14 and Figure 14 the RU illustrated in

[0169] Figure 14The subfield can include a coding type field 1330. The coding type field 1330 can indicate the coding type of the TB PPDU. For example, when BCC encoding is applied to the TB PPDU, the coding type field 1330 can be set to "1", and when LDPC encoding is applied, the coding type field 1330 can be set to "0".

[0170] in addition, Figure 14 The subfields may include the MCS field 1340. The MCS field 1340 can indicate the MCS scheme applied to the TB PPDU. For example, when BCC encoding is applied to the TB PPDU, the encoding type field 1330 can be set to "1", and when LDPC encoding is applied, the encoding type field 1330 can be set to "0".

[0171] The following describes a random access (UORA) scheme based on UL OFDMA.

[0172] Figure 14 Describe the technical features of the UORA scheme.

[0173] Sending a STA (e.g., an AP) can be done via, for example... Figure 14 The trigger frame shown is used to allocate six RU resources. Specifically, the AP can allocate RU resources 1 (AID 0, RU 1), RU resources 2 (AID 0, RU 2), RU resources 3 (AID 0, RU 3), RU resources 4 (AID 2045, RU 4), ​​RU resources 5 (AID 2045, RU 5), and RU resources 6 (AID 3, RU 6). Information related to AID 0, AID 3, or AID 2045 can be included in, for example... Figure 14 The user identifier field 1310. Information related to RU1 through RU6 may be included in, for example... Figure 14 In the RU allocation field 1320, AID=0 can indicate a UORA resource used for an associated STA, and AID=2045 can indicate a UORA resource used for a non-associated STA. Therefore, Figure 15 The first through third RU resources can be used as UORA resources for associated STAs. Figure 15 The 4th RU resource and the 5th RU resource can be used as UORA resources for non-associated STAs. Figure 16 The 6th RU resource can be used as a typical resource for UL MU.

[0174] exist Figure 16In an example of FIG. 10, the OBO of STA1 is reduced to 0, and STA1 randomly selects the 2nd RU resource (AID 0, RU 2). Also, since the OBO counters of STA2 / 3 are greater than 0, no uplink resource is allocated to STA2 / 3. Also, regarding Figure 17 STA4 in FIG. 10, since the AID (e.g., AID=3) of STA4 is included in the trigger frame, the resource of RU 6 is allocated without backoff.

[0175] Specifically, since Figure 17 STA1 of FIG. 10 is an associated STA, the total number of eligible RA RUs for STA1 is 3 (RU1, RU 2, and RU 3), and thus STA1 reduces the OBO counter by 3 so that the OBO counter becomes 0. Also, since Figure 17 STA2 of FIG. 10 is an associated STA, the total number of eligible RA RUs for STA2 is 3 (RU1, RU 2, and RU 3), and thus STA2 reduces the OBO counter by 3, but the OBO counter is greater than 0. Also, since Figure 17 STA3 of FIG. 10 is a non-associated STA, the total number of eligible RA RUs for STA3 is 2 (RU 4, RU 5), and thus STA3 reduces the OBO counter by 2, but the OBO counter is greater than 0.

[0176] Figure 17 An example of channels that are used / supported / defined within a 2.4 GHz band is illustrated.

[0177] The 2.4 GHz band can be referred to as other terms such as a first band. Also, the 2.4 GHz band can mean a frequency domain that uses / supports / defines channels (e.g., channels whose center frequencies are located within 2.4 to 2.5 GHz) whose center frequencies are close to 2.4 GHz.

[0178] A plurality of 20 MHz channels can be included in the 2.4 GHz band. The 20 MHz within 2.4 GHz can have a plurality of channel indices (e.g., index 1 to index 14). For example, the center frequency of the 20 MHz channel allocated with channel index 1 can be 2.412 GHz, the center frequency of the 20 MHz channel allocated with channel index 2 can be 2.417 GHz, and the center frequency of the 20 MHz channel allocated with channel index N can be (2.407+0.005*N) GHz. The channel index can be referred to as various terms such as a channel number. The specific values of the channel index and the center frequency can vary.

[0179] Figure 17Four channels within the 2.4 GHz band are illustrated by way of example. Each of the first through fourth frequency domains 1510-1540 shown herein can include one channel. For example, the first frequency domain 1510 can include channel 1 (a 20 MHz channel with index 1). In this case, the center frequency of channel 1 can be set to 2412 MHz. The second frequency domain 1520 can include channel 6. In this case, the center frequency of channel 6 can be set to 2437 MHz. The third frequency domain 1530 can include channel 11. In this case, the center frequency of channel 11 can be set to 2462 MHz. The fourth frequency domain 1540 can include channel 14. In this case, the center frequency of channel 14 can be set to 2484 MHz.

[0180] Figure 17 An example of channels used / supported / defined within the 5 GHz band is illustrated.

[0181] The 5 GHz band can be referred to by other terms such as a second frequency band, etc. The 5 GHz band can mean a frequency domain using / supporting / defining channels with center frequencies greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz). Alternatively, the 5 GHz band can include multiple channels between 4.5 GHz and 5.5 GHz. Figure 18 The specific values shown can vary.

[0182] Multiple channels within the 5 GHz band include Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 can be referred to as UNII Low. UNII-2 can include frequency domains referred to as UNII Mid and UNII-2 Extended. UNII-3 can be referred to as UNII-Upper.

[0183] Multiple channels can be configured within the 5 GHz band, and the bandwidth of each channel can be set differently, e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, etc. For example, the 5170-5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170-5330 MHz frequency domain / range can be divided into four channels by a 40 MHz frequency domain. The 5170-5330 MHz frequency domain / range can be divided into two channels by an 80 MHz frequency domain. Alternatively, the 5170-5330 MHz frequency domain / range can be divided into one channel by a 160 MHz frequency domain.

[0184] Figure 18An example of a channel illustrated to be used / supported / defined in the 6 GHz band.

[0185] The 6 GHz band can be referred to as other terms such as a third band. The 6 GHz band can mean a frequency domain in which a channel with a center frequency greater than or equal to 5.9 GHz is used / supported / defined. Figure 18 The specific numerical values illustrated can be changed.

[0186] For example, Figure 18 A 20 MHz channel of the 6 GHz band can be defined from 5.940 GHz. Specifically, among the 20 MHz channels of the 6 GHz band, Figure 18 Among the 20 MHz channels of the 6 GHz band, the leftmost channel can have an index 1 (or channel index, channel number, or the like), and 5.945 GHz can be assigned as the center frequency. That is, the center frequency of the channel of index N can be determined as (5.940 + 0.005*N) GHz.

[0187] Therefore, Figure 18 The index (or channel number) of the 2 MHz channel of the 6 GHz band can be 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. In addition, according to the above (5.940 + 0.005*N) GHz rule, Figure 18 The index of the 40 MHz channel of the 6 GHz band can be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.

[0188] Although 20, 40, 80, and 160 MHz channels are illustrated in the example of the 6 GHz band, Figure 18 240 MHz channels or 320 MHz channels can be additionally added.

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

[0190] Figure 18 An example of a PPDU used in the present specification is illustrated.

[0191] Figure 18The PPDU can be referred to using various terms such as EHT PPDU, TX PPDU, RX PPDU, Type 1 or Type N PPDU, etc. For example, in this specification, PPDU or EHT PPDU can be referred to using various terms such as TX PPDU, RX PPDU, Type 1 or Type N PPDU, etc. Furthermore, EHT PPDUs can be used in EHT systems and / or new WLAN systems enhanced from EHT systems.

[0192] Figure 18 The PPDU can indicate all or part of the PPDU types used in the EHT system. For example, Figure 18 The example can be used for both single-user (SU) and multi-user (MU) modes. In other words, Figure 18 The PPDU can be used for one or more receiving STAs. When Figure 8 When using trigger-based (TB) mode, the PPDU can be omitted. Figure 9 The EHT-SIG. In other words, a STA that has received a trigger frame for the uplink MU (UL-MU) can send a signal in... Figure 8 The PPDU for EHT-SIG is omitted in the example.

[0193] exist Figure 8 In the process, L-STF to EHT-LTF can be referred to as a preamble or physical preamble, and can be generated / sent / received / acquired / decoded in the physical layer.

[0194] Can Figure 9 The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields is determined to be 312.5 kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF, and data fields can be determined to be 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields can be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and data fields can be expressed in units of 78.125 kHz.

[0195] exist Figure 8 In the PPDU, L-LTF and L-STF can be the same as those in the regular fields.

[0196] Figure 8The L-SIG field of the L-SIG can include, for example, 24 bits of bit information. For example, the 24 bits of bit information can include 4 bits of a rate field, 1 bit of a reserved bit, 12 bits of a length field, 1 bit of a parity bit, and 6 bits of a tail bit. For example, the 12 bits of the length field can include information related to a length or duration of the PPDU. For example, the 12 bits of the length field can be determined based on a type of the PPDU. For example, when the PPDU is a non-HT, HT, VHT PPDU, or an EHT PPDU, a value of the length field can be determined as a multiple of 3. For example, when the PPDU is a HE PPDU, the length field can be determined as “multiple of 3”+1 or “multiple of 3”+2. In other words, for a non-HT, HT, VHT PPDU, or an EHT PPDU, a value of the length field can be determined as a multiple of 3, and for a HE PPDU, a value of the length field can be determined as “multiple of 3”+1 or “multiple of 3”+2.

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

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

[0199] A universal SIG (U-SIG) can be inserted after the RL-SIG of Figure 5 The U-SIG can be called in various terms such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, a first (type) control signal, etc.

[0200] The U-SIG can include N bits of information, and can include information to identify a type of EHT PPDU. For example, the U-SIG can be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG can have a duration of 4 µs. Each symbol of the U-SIG can be used to transmit 26 bits of information. For example, each symbol of the U-SIG can be transmitted / received based on 52 data tones and 4 pilot tones.

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

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

[0203] The A-bit information (e.g., 52 uncoded bits) sent by the U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the version-independent bits can have a fixed or variable size. For example, the version-independent bits can be allocated to only the first symbol of the U-SIG, or the version-independent bits can be allocated to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be referred to in various terms such as first control bits, second control bits, and the like.

[0204] For example, the version-independent bits of the U-SIG can include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier can include information related to the PHY version of the TX / RX PPDU. For example, a first value of the 3-bit PHY version identifier can indicate that the TX / RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits an EHT PPDU, the 3-bit PHY version identifier can be set to the first value. In other words, the receiving STA can determine that the RX PPDU is an EHT PPDU based on the PHY version identifier having the first value.

[0205] For example, the version-independent bits of the U-SIG can include a 1-bit UL / DL flag field. A first value of the 1-bit UL / DL flag field is related to UL communication, and a second value of the UL / DL flag field is related to DL communication.

[0206] For example, the version-independent bits of the U-SIG can include information related to TXOP length and information related to BSS color ID.

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

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

[0209] Preamble puncturing can be applied to the PPDU of Figure 18 The preamble puncturing implies that the puncturing is applied to a portion of the full band (e.g., a secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA can apply the puncturing to a secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU through only the primary 20 MHz band and the secondary 40 MHz band.

[0210] For example, a pattern of the preamble puncturing can be pre-configured. For example, when a first puncturing pattern is applied, the puncturing can be applied only to a secondary 20 MHz band within an 80 MHz band. For example, when a second puncturing pattern is applied, the puncturing can be applied only to any one of two secondary 20 MHz bands included in a secondary 40 MHz band within the 80 MHz band. For example, when a third puncturing pattern is applied, the puncturing can be applied only to a secondary 20 MHz band included in a primary 80 MHz band within a 160 MHz band (or an 80+80 MHz band). For example, when a fourth puncturing pattern is applied, the puncturing can be applied to at least one 20 MHz channel not belonging to a primary 40 MHz band in the presence of the primary 40 MHz band included in the 80 MHz band within the 160 MHz band (or the 80+80 MHz band).

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

[0212] For example, based on the following method, the U-SIG and the EHT-SIG can include information related to the preamble puncturing. The U-SIG can be separately configured in units of 80 MHz when the bandwidth of the PPDU exceeds 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU can include a first U-SIG for a first 80 MHz frequency band and a second U-SIG for a second 80 MHz frequency band. In this case, a first field of the first U-SIG can include information related to the 160 MHz bandwidth, and a second field of the first U-SIG can include information related to the preamble puncturing applied to the first 80 MHz frequency band (i.e., information related to the preamble puncturing pattern). In addition, a first field of the second U-SIG can include information related to the 160 MHz bandwidth, and a second field of the second U-SIG can include information related to the preamble puncturing applied to the second 80 MHz frequency band (i.e., information related to the preamble puncturing pattern). Meanwhile, the EHT-SIG continuous to the first U-SIG can include information related to the preamble puncturing applied to the second 80 MHz band (i.e., information related to the preamble puncturing pattern), and the EHT-SIG continuous to the second U-SIG can include information related to the preamble puncturing applied to the first 80 MHz frequency band (i.e., information related to the preamble puncturing pattern).

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

[0214] The U-SIG can be configured in units of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG can be duplicated. That is, four identical U-SIGs can be included in the 80 MHz PPDU. The PPDU exceeding the 80 MHz bandwidth can include different U-SIGs.

[0215] Figure 18 The EHT-SIG in the PPDU can include control information for the reception STA. The EHT-SIG can be transmitted through at least one symbol, and one symbol can have a length of 4 µs. Information related to the number of symbols for the EHT-SIG can be included in the U-SIG.

[0216] The EHT-SIG can include a reference Figure 18 and Figure 18Technical features of the described HE-SIG-B. For example, the EHT-SIG can include common fields and user-specific fields as in the examples of Figure 5 The common fields of the EHT-SIG can be omitted, and the number of user-specific fields can be determined based on the number of users.

[0217] As in the examples of Figure 6 The common fields of the EHT-SIG and the user-specific fields of the EHT-SIG can be separately encoded. One user block field included in the user-specific fields can include information for two users, but the last user block field included in the user-specific fields can include information for one user. That is, one user block field of the EHT-SIG can include at most two user fields. As in the examples of Figure 18 Each user field can be related to a MU-MIMO allocation, or can be related to a non-MU-MIMO allocation.

[0218] As in the examples of Figure 5 The common fields of the EHT-SIG can include CRC bits and tail bits. The length of the CRC bits can be determined as 4 bits. The length of the tail bits can be determined as 6 bits, and can be set to "000000".

[0219] As in the examples of Figure 5 The common fields of the EHT-SIG can include RU allocation information. The RU allocation information can imply information related to the positions of RUs to which a plurality of users (i.e., a plurality of receiving STAs) are allocated. The RU allocation information can be configured in units of 8 bits (or N bits) as shown in Table 1.

[0220] The examples of Tables 5 to 7 are examples of 8-bit (or N-bit) information for various RU allocations. The indices shown in each table can be modified, and some entries in Tables 5 to 7 can be omitted, and entries (not shown) can be added.

[0221] The examples of Tables 5 to 7 relate to information related to the positions of RUs allocated to a 20 MHz band. For example, "Index 0" of Table 5 can be used in the case where nine 26-RUs are separately allocated (e.g., in the case where the nine 26-RUs shown in Table 5 are separately allocated). Figure 6

[0222] ​In addition, multiple RUs can be allocated to one STA in the EHT system. For example, with respect to "Index 60" of Table 6, one 26-RU can be allocated to the leftmost one user (i.e., receiving STA) of the 20 MHz band, one 26-RU and one 52-RU can be allocated to the right thereof, and five 26-RUs can be individually allocated to the right thereof.

[0223] [Table 5]

[0224]

[0225] [Table 6]

[0226]

[0227] [Table 7]

[0228]

[0229] A mode in which the common field of the EHT-SIG is omitted can be supported. The mode in which the common field of the EHT-SIG is omitted can be referred to as a compressed mode. When the compressed mode is used, multiple users (i.e., multiple receiving STAs) can decode the PPDU (e.g., data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU can decode the PPDU (e.g., data field of the PPDU) received through the same frequency band. In addition, when the non-compressed mode is used, multiple users of the EHT PPDU can decode the PPDU (e.g., data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU can receive the PPDU (e.g., data field of the PPDU) through different frequency bands.

[0230] The EHT-SIG can be configured based on various MCS schemes. As described above, information related to the MCS scheme applied to the EHT-SIG can be included in the U-SIG. The EHT-SIG can be configured based on a DCM scheme. For example, among N data tones (e.g., 52 data tones) allocated for the EHT-SIG, a first modulation scheme can be applied to one half of the continuous tones, and a second modulation scheme can be applied to the remaining half of the continuous tones. That is, the transmitting STA can modulate and allocate specific control information to one half of the continuous tones using a first modulation scheme through a first symbol, and can modulate and allocate the same control information to the remaining half of the continuous tones using a second modulation scheme through a second symbol. As described above, information (e.g., 1-bit field) about whether to apply the DCM scheme to the EHT-SIG can be included in the U-SIG.

[0231] Figure 6 HE-STF can be used to improve automatic gain control estimation in multiple-input multiple-output (MIMO) or OFDMA environments. Figure 6 HE-LTF can be used to estimate channels in MIMO or OFDMA environments.

[0232] It can be set according to various types. Figure 6 EHT-STF. For example, a first-type STF (e.g., 1x STF) can be generated based on a first-type STF sequence in which non-zero coefficients are arranged at intervals of 16 subcarriers. The STF signal generated based on the first-type STF sequence can have a period of 0.8 μs, and the 0.8 μs periodic signal can be repeated 5 times to become a first-type STF with a length of 4 μs. For example, a second-type STF (e.g., 2x STF) can be generated based on a second-type STF sequence in which non-zero coefficients are arranged at intervals of 8 subcarriers. The STF signal generated based on the second-type STF sequence can have a period of 1.6 μs, and the 1.6 μs periodic signal can be repeated 5 times to become a second-type STF with a length of 8 μs. Examples of sequences for configuring EHT-STF (i.e., EHT-STF sequences) are presented below. The following sequences can be modified in various ways.

[0233] EHT-STF can be configured based on the following sequence M.

[0234] <Formula 1>

[0235] M = {–1, –1, –1, 1, 1, 1, –1, 1, 1, 1, –1, 1, 1, –1, 1}

[0236] The EHT-STF for a 20 MHz PPDU can be configured based on the following formula. The following example could be a Type I (i.e., 1x STF) sequence. For example, a Type I sequence could be included in an EHT-PPDU instead of a trigger-based (TB) PPDU. In the following formula, (a:b:c) can imply the duration of b tone intervals (i.e., subcarrier intervals) defined from tone index (i.e., subcarrier index) 'a' to tone index 'c'. For example, Equation 2 can represent a sequence of 16 tone intervals defined from tone index -112 to tone index 112. Since a subcarrier interval of 78.125 kHz is applied to the EHT-STR, 16 tone intervals can imply that the EHT-STF coefficients (or elements) are arranged at intervals of 78.125 * 16 = 1250 kHz. Additionally, * implies multiplication, and sqrt() implies square root. Furthermore, j implies an imaginary number.

[0237] <Formula 2>

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

[0239] EHT-STF(0) = 0

[0240] The EHT-STF for a 40 MHz PPDU can be configured based on the following formula. The following example can be a first type (i.e., lx STF) sequence.

[0241] <Formula 3>

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

[0243] The EHT-STF for an 80 MHz PPDU can be configured based on the following formula. The following example can be a first type (i.e., lx STF) sequence.

[0244] <Formula 4>

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

[0246] The EHT-STF for a 160 MHz PPDU can be configured based on the following formula. The following example can be a first type (i.e., lx STF) sequence.

[0247] <Formula 5>

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

[0249] In the EHT-STF for an 80+80 MHz PPDU, the sequence for the lower 80 MHz can be the same as Formula 4. In the EHT-STF for an 80+80 MHz PPDU, the sequence for the upper 80 MHz can be configured based on the following formula.

[0250] <Formula 6>

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

[0252] The following Equations 7-11 are related to examples of the second type (i.e., 2x STF) sequence.

[0253] < Equation 7 >

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

[0255] The EHT-STF for a 40 MHz PPDU can be configured based on the following equation.

[0256] < Equation 8 >

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

[0258] EHT-STF(-248) = 0

[0259] EHT-STF(248) = 0

[0260] The EHT-STF for an 80 MHz PPDU can be configured based on the following equation.

[0261] < Equation 9 >

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

[0263] The EHT-STF for a 160 MHz PPDU can be configured based on the following equation.

[0264] < Equation 10 >

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

[0266] EHT-STF(-8) = 0, EHT-STF(8) = 0,

[0267] EHT-STF(-1016) = 0, EHT-STF(1016) = 0

[0268] In the EHT-STF for 80+80 MHz PPDU, the sequence for the lower 80 MHz can be the same as Equation 9. In the EHT-STF for 80+80 MHz PPDU, the sequence for the upper 80 MHz can be configured based on the following equation.

[0269] < Equation 11 >

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

[0271] EHT-STF(-504) = 0,

[0272] EHT-STF(504) = 0

[0273] The EHT-LTF can have first, second, and third types (i.e., 1x, 2x, 4x LTF). For example, the first / second / third type LTF can be generated based on an LTF sequence in which non-zero coefficients are arranged at intervals of 4 / 2 / 1 subcarriers. The first / second / third type LTF can have a time length of 3.2 / 6.4 / 12.8 µs. In addition, the first / second / third type LTF can have a GI having various lengths (e.g., 0.8 / 1 / 6 / 3.2 µs) applied thereto.

[0274] Information related to the type of STF and / or LTF (also including information related to the GI applied to the LTF) can be included in the SIG-A field and / or the SIG-B field of the Figure 7 , etc.

[0275] The PPDU (e.g., EHT-PPDU) of Figure 6 and Figure 6 may be configured based on an example. Figure 6 For example, the EHT PPDU transmitted on a 20 MHz band, i.e., 20 MHz EHT PPDU, can be configured based on the RU of

[0276] . That is, the position of the RU of the EHT-STF, the EHT-LTF, and the data field included in the EHT PPDU can be determined as shown in Figure 18 Figure 18 The EHT PPDU transmitted on a 40 MHz band, i.e., 40 MHz EHT PPDU, can be configured based on the RU of

[0277] Figure 18 Figure 18 ​​​The diagram shows the locations of the EHT-STF, EHT-LTF, and RU fields included in the EHT PPDU.

[0278] because Figure 18 The RU position corresponds to 40 MHz, so it can be used. Figure 18 The tone plan for 80MHz is determined by repeating the pattern twice. In other words, it can be based on the fact that it is not... Figure 18 RU instead Figure 18 The RU repeats the new tone twice, which is planned to be sent to an 80 MHz EHTPPDU.

[0279] when Figure 19 When the pattern repeats twice, 23 tones can be configured in the DC region (i.e., 11 guard tones + 12 guard tones). That is, the tone scheme for an 80 MHz EHTPPDU allocated based on OFDMA can have 23 DC tones. In contrast, an 80 MHz EHTPPDU allocated based on non-OFDMA (i.e., a non-OFDMA full-bandwidth 80 MHz PPDU) can be configured based on the 996-RU and can include 5 DC tones, 12 left guard tones, and 11 right guard tones.

[0280] Able to Figure 1 The pattern is repeated several times in this way for the tone scheme of 160 / 240 / 320 MHz.

[0281] The following methods can be used to... Figure 19 The PPDU was identified (or recognized) as an EHT PPDU.

[0282] The receiving STA can determine the type of an RX PPDU as an EHT PPDU based on the following: for example, 1) when the first symbol after the L-LTF signal of the RX PPDU is a BPSK symbol; 2) when an RL-SIG is detected where the L-SIG of the RX PPDU is repeated; and 3) when the result of applying "modulo 3" to the value of the length field of the L-SIG of the RX PPDU is "0". When the RX PPDU is determined to be an EHT PPDU, the receiving STA can further determine its type based on the following: Figure 19the bits included in the symbol after the RL-SIG of the EHT PPDU to detect the type of the EHT PPDU (e.g., SU / MU / trigger-based / extended range type). In other words, the receiving STA can determine the RX PPDU as an EHT PPDU based on 1) the first symbol after the L-LTF signal, which is a BPSK symbol, 2) the RL-SIG contiguous to and identical to the L-SIG, 3) the L-SIG including the length field in which the result of applying "mod 3" is set to "0", and 4) the 3-bit PHY version identifier of the preceding U-SIG (e.g., the PHY version identifier with the first value).

[0283] For example, the receiving STA can determine the type of the RX PPDU as an EHT PPDU based on the following. For example, 1) when the first symbol after the L-LTF signal is a BPSK symbol, 2) when the RL-SIG in which the L-SIG is repeated is detected, and 3) when the result of applying "mod 3" to the value of the length field of the L-SIG is "1" or "2" is detected, the RX PPDU can be determined as an HE PPDU.

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

[0285] In the following examples, a signal denoted as a (TX / RX / UL / DL) signal, (TX / RX / UL / DL) frame, (TX / RX / UL / DL) packet, (TX / RX / UL / DL) data unit, (TX / RX / UL / DL) data, etc. can be a signal transmitted / received based on a PPDU. Figure 1 A PPDU. Figure 19 A PPDU can be used to transmit / receive various types of frames. For example, Figure 19 A PPDU can be used for control frames. Examples of control frames can include a request to send (RTS), a clear to send (CTS), a power save poll (PS-poll), a BlockACKReq, a BlockAck, a null data packet (NDP) announcement, and a trigger frame. For example, Figure 1PPDUs can be used for management frames. Examples of management frames can include beacon frames, (re)association request frames, (re)association response frames, probe request frames, and probe response frames. For example, Figure 19 PPDUs can be used in data frames. For example, Figure 1 A PPDU can be used to simultaneously transmit at least two or more of control frames, management frames, and data frames.

[0286] Figure 19 Examples of modified transmitting and / or receiving devices are shown in this specification.

[0287] Figure 1 Each device / STA in subgraphs (a) / (b) can be modified as follows Figure 19 As shown. Figure 1 The transceiver 630 can be used with Figure 19 The transceivers 113 and 123 are the same. Figure 19 The transceiver 630 may include a receiver and a transmitter.

[0288] Figure 20 The processor 610 can be with Figure 20 The processors 111 and 121 are the same. Alternatively, Figure 20 The processor 610 can be with Figure 15 The processing chips 114 and 124 are the same.

[0289] Figure 16 The memory 620 can be with Figure 17 The memories 112 and 122 are the same. Alternatively, Figure 1 The memory 620 can be with Figure 19 The memories 112 and 122 are different separate external memories.

[0290] Reference Figure 18 The power management module 611 manages the power supplied to the processor 610 and / or transceiver 630. The battery 612 supplies power to the power management module 611. The display 613 outputs the results processed by the processor 610. The keypad 614 receives inputs to be used by the processor 610. The keypad 614 can be displayed on the display 613. The SIM card 615 can be an integrated circuit for securely storing the International Mobile Subscriber Identity (IMSI) and its associated keys, used for identifying and authenticating users on mobile phone devices (e.g., mobile phones and computers).

[0291] Reference Figure 21 The speaker 640 can output results related to the sound processed by the processor 610. The microphone 641 can receive input related to the sound to be used by the processor 610.

[0292] Hereinafter, technical features of channel bonding supported by the STA of the disclosure will be described.

[0293] For example, in the IEEE 802.11n system, 40 MHz channel bonding can be performed by combining two 20 MHz channels. Also, 40 / 80 / 160 MHz channel bonding can be performed in the IEEE 802.11ac system.

[0294] For example, the STA can perform channel bonding on a primary 20 MHz channel (P20 channel) and a secondary 20 MHz channel (S20 channel). A backoff count / counter can be used in the channel bonding process. The backoff count value can be picked as a random value and decremented during a backoff interval. Generally, when the backoff count value becomes 0, the STA can attempt to access the channel.

[0295] During the backoff interval, when it is determined that the P20 channel is in an idle state and the backoff count value of the P20 channel becomes 0, the STA performing channel bonding determines whether the S20 channel remains in an idle state for a certain period of time (e.g., a point coordination function interframe space (PIFS)). If the S20 channel is in an idle state, the STA can perform bonding on the P20 channel and the S20 channel. That is, the STA can transmit a signal (PPDU) through a 40 MHz channel (i.e., a 40 MHz bonded channel) including the P20 channel and the S20 channel.

[0296] Figure 21 An example of channel bonding is shown. As shown in Figure 21 As shown in FIG. 1, a primary 20 MHz channel and a secondary 20 MHz channel can be composed of a 40 MHz channel (primary 40 MHz channel) through channel bonding. That is, the bonded 40 MHz channel can include the primary 20 MHz channel and the secondary 20 MHz channel.

[0297] Channel bonding can be performed when a channel adjacent to a primary channel is in an idle state. That is, a primary 20 MHz channel, a secondary 20 MHz channel, a secondary 40 MHz channel, and a secondary 80 MHz channel can be sequentially bonded. However, if it is determined that the secondary 20 MHz channel is in a busy state, channel bonding can not be performed even if all other secondary channels are in an idle state. In addition, when it is determined that the secondary 20 MHz channel is in an idle state and the secondary 40 MHz channel is in a busy state, channel bonding can be performed only on the primary 20 MHz channel and the secondary 20 MHz channel.

[0298] Hereinafter, preamble puncturing supported by the STA in the disclosure will be described.

[0299] For example, in Figure 22In the example of FIG. 1, if the primary 20 MHz channel, the secondary 40 MHz channel, and the secondary 80 MHz channel are in an idle state, but the secondary 20 MHz channel is in a busy state, it can not be possible to bundle to the secondary 40 MHz channel and the secondary 80 MHz channel. In this case, the STA can configure a 160 MHz PPDU, and can perform preamble puncturing on a preamble transmitted through the secondary 20 MHz channel (e.g., L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF, EHT-SIG, EHT-STF, EHT-LTF, etc.) so that the STA can transmit a signal through the channels in an idle state. In other words, the STA can perform preamble puncturing on some frequency bands of the PPDU. Information about the preamble puncturing (e.g., information about the 20 / 40 / 80 MHz channel / frequency band to which puncturing is applied) can be included in a signal field (e.g., HE-SIG-A, U-SIG, EHT-SIG) of the PPDU.

[0300] Hereinafter, technical features of Multi-Link (ML) supported by the STA of the disclosure will be described.

[0301] The STA (AP and / or non-AP STA) of the disclosure can support Multi-Link (ML) communication. The ML communication can refer to communication supporting multiple links. The links related to the ML communication can include Figure 22 channels of the 2.4 GHz band as shown in FIG. 2, Figure 22 the 5 GHz band as shown in FIG. 3, and Figure 23 the 6 GHz band (e.g., 20 / 40 / 80 / 160 / 240 / 320 MHz channel) as shown in FIG. 4.

[0302] The multiple links for the ML communication can be set in various ways. For example, the multiple links for the ML communication supported by one STA can be multiple channels in the 2.4 GHz band, multiple channels in the 5 GHz band, and multiple channels in the 6 GHz band. Alternatively, the multiple links for the ML communication supported by one STA can be a combination of at least one channel in the 2.4 GHz band (or the 5 GHz / 6 GHz band) and at least one channel in the 5 GHz band (or the 2.4 GHz / 6 GHz band). Meanwhile, at least one of the multiple links for the ML communication supported by one STA can be a channel to which preamble puncturing is applied.

[0303] The STA can perform ML setup to perform ML communication. The ML setup can be performed based on a management frame or a control frame such as a beacon, a probe request / response, an association request / response. For example, information about the ML setup can be included in an element field included in the beacon, the probe request / response, the association request / response, etc.

[0304] When the ML setup is completed, an enabled link for ML communication can be determined. The STA can perform a frame exchange through at least one of the multiple links determined as the enabled link. For example, the enabled link can be used for at least one of a management frame, a control frame, and a data frame.

[0305] When one STA supports multiple links, transceivers supporting each link can operate as one logical STA. For example, one STA supporting two links can be expressed as one multi-link device (MLD) including a first STA for a first link and a second STA for a second link. For example, one AP supporting two links can be expressed as one AP MLD including a first AP for a first link and a second AP for a second link. Further, one non-AP supporting two links can be expressed as one non-AP MLD including a first STA for a first link and a second STA for a second link.

[0306] Hereinafter, more specific features related to the ML setup will be described.

[0307] An MLD (an AP MLD and / or a non-AP MLD) can transmit information on a link that the corresponding MLD can support through ML setting. The link information can be configured in various ways. For example, the information on the link can include at least one of 1) information on whether the MLD (or STA) supports simultaneous RX / TX operation, 2) information on the number / upper limit of uplink / downlink that the MLD (or STA) supports, 3) information on the location / band / resource of the uplink / downlink that the MLD (or STA) supports, 4) information on the frame type (management, control, data, etc.) that is available or preferred in at least one uplink / downlink, 5) information on the ACK policy that is available or preferred in at least one uplink / downlink, and 6) information on the traffic identifier (TID) that is available or preferred in at least one uplink / downlink. The TID is related to the priority of traffic data, and is expressed as eight types of values according to the conventional wireless LAN standard. That is, eight TID values corresponding to four access categories (ACs) (AC_Background (AC_BK), AC_Best Effort (AC_BE), AC_Video (AC_VI), AC_Voice (AC_VO)) according to the conventional WLAN standard can be defined.

[0308] For example, it can be preset that all TIDs are mapped for uplink / downlink links. Specifically, if not negotiated through ML setting, if all TIDs are used for ML communication, and if the mapping between the uplink / downlink link and the TID is negotiated through additional ML setting, the negotiated TID can be used for ML communication.

[0309] Through ML setting, a plurality of links available to a transmitting MLD and a receiving MLD in relation to ML communication can be set, and this can be referred to as an "enabled link". The "enabled link" can be referred to differently with various expressions. For example, it can be referred to as various expressions such as a first link, a second link, a transmission link, and a reception link.

[0310] After ML setting is completed, the MLD can update the ML setting. For example, when it is necessary to update the information on the link, the MLD can transmit information on a new link. The information on the new link can be transmitted based on at least one of a management frame, a control frame, and a data frame.

[0311] In the standard Extremely High Throughput (EHT) discussed after IEEE 802.11ax, the introduction of HARQ is being considered. When HARQ is introduced, it is possible to expand the coverage in a low signal-to-noise ratio (SNR) environment, i.e., in an environment in which the distance between the transmitting end and the receiving end is long, and a higher throughput can be obtained in a high SNR environment.

[0312] The apparatus described below can be Figure 23 and / or Figure 24 an apparatus, and the PPDU described below can be Figure 24 a PPDU. The apparatus can be an AP or a non-AP STA. The apparatus described below can be an AP multi-link device (MLD) or a non-AP STA MLD supporting multi-link.

[0313] In Extremely High Throughput (EHT), which is a standard discussed after 802.11ax, a multi-link environment using one or more frequency bands is being considered. When a device supports multi-link or multi-link, the device can use one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 60 GHz, etc.) simultaneously or alternately. As shown in Figure 23 Multi-link transmission can be classified into two types.

[0314] Hereinafter, although described in the form of multi-link, the frequency band can be configured in various other forms. Although terms such as multi-band and / or multi-link can be used in the present specification, for convenience of the following description, the following embodiments can be described based on multi-link.

[0315] In the following specification, MLD refers to a multi-link device. The MLD has one or more affiliated STAs and has one MAC service access point (SAP) connected to a higher link layer (logical link control, LLC). The MLD can mean a physical device or a logical device. Hereinafter, the device can mean the MLD.

[0316] In the following specification, the transmitting device and the receiving device can refer to the MLD. The first link of the receiving / transmitting device can be a terminal (e.g., STA or AP) that performs signal transmission / reception through the first link included in the receiving / transmitting device. The second link of the receiving / transmitting device can be a terminal (e.g., STA or AP) that performs signal transmission / reception through the second link included in the receiving / transmitting device.

[0317] IEEE 802.11be can support two types of multi-link operation. For example, simultaneous transmit and receive (STR) and non-STR operation can be considered. For example, STR can be referred to as asynchronous multi-link operation, and non-STR can be referred to as synchronous multi-link operation. The multi-link can include a multi-band. That is, the multi-link can mean a link included in a plurality of frequency bands, or can mean a plurality of links included in one frequency band.

[0318] EHT (11be) considers a multi-link technology, where a multi-link can include multiple frequency bands. That is, a multi-link can represent a link of several frequency bands, and can also represent several multi-links within one frequency band. Two types of multi-link operation can be considered. Asynchronous operation enabling simultaneous TX / RX on multiple links and synchronous operation not enabling simultaneous TX / RX are considered. Hereinafter, the capability of being able to simultaneously receive and transmit in multiple links can be referred to as STR (Simultaneous Transmit and Receive), a STA having the STR capability can be referred to as an STR multi-link device (MLD), and a STA not having the STR capability can be referred to as a non-STR MLD.

[0319] Figure 24 is a diagram illustrating an embodiment of a device supporting a multi-link.

[0320] Referring to Figure 25 , a STA MLD (or an AP MLD) can include three STAs, can have three links, and each link can have a primary channel (PCH). The presence or absence of the STR capability of the AP MLD and the STA MLD can vary depending on the channel of each link. The STR capability needs to be negotiated. That is, the STR capability of the AP MLD can vary based on the link channel configured by the AP MLD, and the multi-link operation of the two MLDS can vary depending on the capability of the STA MLD and the link selected by each STA of the STA MLD. Hereinafter, operation negotiation (e.g., multi-link setup) between the AP MLD and the STA MLD based on the STR capability will be described.

[0321] The term (name) in this specification can vary, and the STA can include an AP STA or a non-AP STA.

[0322] The multi-link operation for the entire active link can vary depending on the STR capability that the link set selected by the AP / STA MLD has.

[0323] Figure 25 is a diagram illustrating an embodiment of the STR capability of a multi-link.

[0324] Referring to Figure 25 , link 1 and link 2 of the left side STA MLD have a non-STR relationship, i.e., a link set that cannot perform transmission and reception simultaneously on multiple links, and link 2 and link 3 also have a non-STR relationship. Here, even if link 1 and link 3 are STR, link 1, link 2, and link 3 can have to operate as non-STR due to link 2.

[0325] A. New element or field definitionThe link 1 and link 2 of the right side STA MLD of FIG. 1 have a non-STR relationship, and the link 3 and link 4 also have a non-STR relationship. However, because the link 2 and link 3 are an STR relationship, the non-STR can be considered in the link 1 / 2 and link 3 / 4, respectively.

[0326] An MLD can have a link set with a non-STR relationship, which is referred to as a non-STR link set in this specification. The basic procedure (A) is as follows.

[0327] 1) The AP MLD provides link information to the STA MLD.

[0328] 2) The STA MLD requests a link operation.

[0329] 3) The AP MLD responds by determining the link on which the STA MLD will operate based on the request.

[0330] Here, the STA MLD does not necessarily need to request a link to operate, which includes the link on which the current negotiation is currently being performed. That is, the link can be flexibly requested based on the capability. This case will be handled later in this specification.

[0331] Here, the AP MLD does not necessarily select all the links requested by the STA MLD. If all the requested links are always selected, it can operate according to the capability, but the performance can be significantly reduced.

[0332] Method of requesting / response link set and / or STR capability in 2) and 3) steps

[0333] If the order is determined to be announced by the link information from the AP and the non-STR link set is known to the STA, it can be expressed as a bitmap of each link.

[0334] Ex) '1': selected or requested link; '0': not selected / requested link

[0335] Figure 26 is a diagram illustrating an embodiment of link information.

[0336] Referring to Figure 26 , the link information can be expressed in 3 bits. For example, if the STA requests link 2 and link 3, the link information can indicate "011".

[0337] Figure 25 is a diagram illustrating an embodiment of link information.

[0338] Referring to Figure 26If the order is determined, each link set whether in the STR can be indicated in the form of bitmap in turn, such as [link 1, link 2], [link 1, link 3]…. Next, the requested or selected link set can be indicated in the form of bitmap.

[0339] Ex) 1 bit indicates whether all link sets consisting of N links are in the STR: 1 bit can be used to indicate each of the following: whether link 1 and link 2 are in the STR, …, whether link 1 and link N are in the STR, whether link 2 and link 3 are in the STR, …, whether link N-1 and link N are in the STR. For example, 1 bit of information can indicate whether each link set is in the STR, if it is in the STR, the value of 1 bit of information is 1, and if it is not in the STR, its value is 0.

[0340] Ex) Link request / selection '1': selected / requested link, link request / selection '0': not selected / requested link

[0341] For example, in Figure 27 and B. Included in the Multi-Link element , if link 2 and link 3 are in the non-STA, whether in the STR can be represented with the value of "110" (i.e., the first bit indicates whether the link set of [link 1, link 2] is in the STR, the second bit indicates whether the link set of [link 1, link 3] is in the STR, the third bit indicates whether the link set of [link 2, link 3] is in the STR, and therefore the value of "110" can include the information that only the third link set of [link 2, link 3] is in the non-STR), and if the STA requests link 2 and link 3, it can be expressed as "011". Therefore, the total indication bitmap can be "110011".

[0342] In addition, in another method, whether the link set is requested or selected and whether each link set is in the STR can be indicated. The same number of bits as the above method can be used, and "101001" can be configured to indicate the same example. That is, the last 2 bits of "01" indicate the non-STR link set, and it can be seen that the STA requests link 2 and link 3. For example, the first 2 bits "10" indicate that [link 1, link 2] is in the STR and is not requested, the second 2 bits "10" indicate that [link 1, link 3] is in the STR and is not requested, and the third 2 bits "01" indicate that [link 2, link 3] is in the non-STR and is requested.

[0343] Figure 28 is an example of multi-link setting of the above basic process (A).

[0344] Referring to Figure 28, the AP MLD has 4 links, and the link information can be announced through a beacon frame or a probe response frame. The link information can include information about AP / link capabilities, channel information, and non-STR link set. For example, link 1 and link 2 and link 3 and link 4 can each be a non-STR link set. The non-AP MLD has 3 STAs, each of which can be connected to a link, and the AP MLD can be discovered through link 4. The non-AP MLD can request links 2, 3, 4 as links for operation through link 4, and the AP MLD responds so that the non-AP MLD can operate on links 2, 3, and 4 based on this request. For example, if the STA MLD does not have the capability to operate on link 4, link 4 can not be requested.

[0345] In the above procedure (A), when three link pairs are configured as {STA 1 <-> AP 4}, {STA 2 <-> AP 3}, {STA 3 <-> AP 2} in a multi-link setup, STA 2 and STA 3 can not have performed an initial frame exchange with the APs. In this case, a method of enabling STA 2 and STA 3 to perform frame exchanges with AP 2 and AP 3, respectively, in the corresponding links is required. The method includes the following features, but is not limited thereto.

[0346] That is, a method of allowing an STA set to perform a multi-link operation but not directly performing a link setup to start transmitting and receiving signals can be classified into a method in a multi-link setup step and a method after the multi-link setup. Among the links to be set, a link through which an association request / response frame is transmitted can be referred to as an association link, and the other set links can be referred to as non-association links. For example, if the set links are link 2, 3, and 4 in Figure 29 link 4 becomes an association link, and links 2, 3 become non-association links. However, this is only a term, and the STA and the AP of the non-association link can be in a state in which association has been performed.

[0347] 1) Method in a multi-link setup step

[0348] 2) MAC address signaling: An STA (i.e., an STA of an association link) that transmits a management frame (e.g., a probe request / response frame, a beacon frame, an association request / response frame) can transmit a MAC address of another STA (i.e., an STA of a non-association link) belonging to the same MLD to which the STA belongs. This MAC address is identified by the STA to operate in a non-association link to enable frame exchange. The method of including the MAC address can be as follows, but is not limited thereto.

[0349] Figure 29: A new element or field included in the management frame can be defined. Basically, the MLD per STA MAC address field can be defined as follows.

[0350] Figure 26 is a diagram illustrating an embodiment of the MLD per STA MAC address field.

[0351] Referring to Figure 29 , since there can be a link ID capable of distinguishing each AP, the AP MLD can indicate the MAC address of the STA (i.e., the AP) operating in the unassociated link in the order of the link ID. If a STA ID capable of distinguishing each STA can be defined, the non-AP MLD can also indicate the MAC address in the order of the STA ID. In addition, the link ID or the STA ID can be included in front of each MAC address in order to clearly indicate.

[0352] For example, the STA transmitting the management frame can not indicate the MAC address of all STAs belonging to the same MLD as the STA. For example, in Figure 30 , STA 1 can not transmit the MAC address of STA 2. In this case, the number of STAs (or the number of links (in the case of an AP)) can be additionally indicated.

[0353] Since the corresponding field can not be included if it is not an MLD, the alternative field, Figure 30 The MLD address field presented in

[0354] Figure 31 is a diagram illustrating an embodiment of the MLD per STA MAC address element.

[0355] Figure 32 : The MAC address of the STA operating in the unassociated link can be included in the common information or the per STA information field of the ML IE (information element).

[0356] Figure 32 is a diagram illustrating an embodiment of the multi-link element.

[0357] The order, name, and size of the fields of the format of the multi-link element can change, and additional fields can exist. Referring to Figure 33 , the common information can include information common to the STAs in the MLD, and specific information about each STA can be included in the per STA profile.

[0358] Figure 33 is a diagram illustrating an embodiment of the ML IE.

[0359] Referring to Figure 34 , Figure 34The MLD per STA MAC address field can be included in the common information, as shown in Figure 34 If the MAC address field is present in the common information and the MAC address should always be included in the ML IE, the per STA profile can not be needed. However, because each MAC address of each STA is different, the per STA profile can be semantically appropriate.

[0360] Figure 35 is a diagram illustrating an embodiment of the ML IE.

[0361] Referring to Figure 35 , the MAC address field can be included in the link information field. The per STA information can include the MAC address field or element of each STA.

[0362] 2) Method after multi-link setup

[0363] 2-1) Initial frame transmission in unassociated link

[0364] To trigger the frame exchange, an initial frame can be sent on the unassociated link. When the transmitter sends the initial request frame, the receiver can respond with an initial response frame (e.g., ACK). The transmitter can be an AP or a non-AP. For example, after multi-link setup, the STA that first obtains the channel access opportunity in the unassociated link can send. For example, the STA that receives the initial frame can know the MAC address of the corresponding transmitter STA through the TA (transmitter address) of the initial frame.

[0365] The initiation request frame can be defined as a new frame, but existing QoS data frames, QoS null frames, etc. can be used. The frame sent as the initial request frame can include information related to the transmitter MLD and / or information related to the receiver MLD in order to inform that operation on the corresponding link after multi-link setup is possible.

[0366] Figure 36 is a diagram illustrating an embodiment of a method for sending an initial frame in an unassociated link.

[0367] A. Address setup: The MLD MAC address can be set in the initial frame.

[0368] A-1) Set the receiver's MLD MAC address in the receiver address (RA) field: During the multi-link setup procedure, the MLD MAC addresses of each other can be known by including the ML IE in the association request / response frame, and thus, by including the MLD MAC address of the MLD in the RA, it can be informed that operation in the current link is possible. In addition, in order to inform that it is an MLD that has performed multi-link setup, the source address (SA) can include the MLD MAC address of the transmitter MLD.

[0369] Figure 36 is a diagram illustrating an embodiment of A-1.

[0370] Referring to When the STA MLD selects Link 3 and Link 4 in non-STR When STA 2 transmits the initial request frame in link 3, TA can be set to the MAC address of STA 2, RA can be set to the AP MLD MAC address, and SA can be set to the MAC address of the non-AP MLD.

[0371] A-2) Setting a broadcast address in RA: The receiver can know the address of the sender through TA, but it is difficult to accurately distinguish whether it is an MLD that has performed multi-link setup.

[0372] A-3) Setting a broadcast address in RA and setting the MLD MAC address of the receiver in the destination address (DA): This method has the same purpose as A-1), but the address setting method can be different. In addition, in order to inform the MLD that multi-link setup has been performed, the source address (SA) can include the MLD MAC address of the transmitter MLD.

[0373] Figure 37 is a diagram illustrating an embodiment of A-3.

[0374] Referring to Figure 37 When STA 2 transmits the initial request frame in link 3, TA can be set to the MAC address of STA 2, RA can be set to the broadcast address, SA can be set to the MAC address of the non-AP MLD, and DA can be set to the AP MLD MAC address.

[0375] A-4) The MLD MAC address of the transmitter MLD and / or the receiver MLD can be included in the control field (e.g., the A control field of the QoS null / data frame) in the MAC frame body or the MAC header included in the initial frame.

[0376] B. MLD ID Setting: The MLD ID can be set in the initial frame.

[0377] B-1) The MLD MAC addresses of the transmitter and the receiver set in the address fields presented in A-1), A-2), A-3), and A-4) can be replaced with the MLD ID capable of distinguishing the MLD. For example, when replaced in the A-4) method, the MLD ID of the transmitter MLD and / or the receiver MLD can be included in the control field (e.g., the A control field of the QoS null / data frame) in the MAC frame body or the MAC header included in the initial frame. In the case of including the MLD ID in the address field, since the field size is much smaller than the MLD MAC address, the number of remaining bits can be increased.

[0378] When the STA MLD selects Link 3 and Link 4 in STR is a diagram illustrating an embodiment of the A-4 method and the B-1 method.

[0379] Reference Figure 38 When the STA 2 transmits the initial request frame in the link 3, the A control field of the initial request frame can include the ID of the non-AP MLD of the STA 2 as the transmitter, and include the ID of the AP MLD of the AP 4 as the receiver.

[0380] 2-2) Definition of additional rule: The non-AP STA can not transmit a frame until a beacon is received in the non-associated link. In other words, it waits for the beacon to be heard. Basically, this rule can be applied because the TBTT (Target Beacon Transmission Time) information of the other APs can be known during the multi-link setup procedure. For example, in Figure 38 , the STA 2 and the STA 3 can not transmit a frame until they receive a beacon from the AP 3 and the AP 2, respectively.

[0381] Upon receiving the link information, the STA MLD can transmit (or initiate) a frame in each link as association. That is, the STA MLD can exchange additional frames in each link in which it wants to operate.

[0382] When the STR MLD selects Link 2 and Link 3 in non-STR is a diagram illustrating an embodiment of the multi-link setup method.

[0383] Reference Figure 39 , the STA MLD can request the setup of the links 2, 3, and 4 after receiving the information of the links 1 to 4, which are the links to be operated, and the AP MLD can respond. The setup request / response can be transmitted for each link.

[0384] For example, although a certain link set is a STR possible link set for the AP MLD, it can be a non-STR link set for the STA MLD. Accordingly, the STA MLD can transmit information related to the STR-related capability when requesting the link.

[0385] Figure 39 is a diagram illustrating an embodiment of the operation related to the link capability.

[0386] Reference Figure 40 When the links 3 and 4 are used, the AP MLD should be based on the non-STA operation, and the other set can operate in the STR. In addition, the STA 1 of the STA MLD can discover the AP MLD through the link 4. Here, which link the STA 1 and the STA 2 of the STA MLD request and whether the link can have the STR capability can affect the MLD to select the link.

[0387] The AP MLD can accept the requested link, change the link, or reject based on the request link by the STA MLD and whether the link has STR capability. In particular, there can be a case where the performance using multi-link can be degraded depending on whether the AP MLD accepts. For example, the STA MLD is in non-STR in Link 1 and Link 2, but the AP can accept it. However, the performance can be lower than when all of them are based on STR operation.

[0388] Based on the above scenario, an example of a negotiation procedure related to the STR capability of the AP MLD and the STA MLD and the requested link can be as follows.

[0389] Figure 40

[0390] A. New element or field definition FIG. is a diagram illustrating an embodiment of a link negotiation method.

[0391] Referring to Figure 25 , the STA MLD can request Link 3 and Link 4, and this link set can be a non-STR set for the STA MLD. The AP MLD can respond to the STA MLD by selecting Link 3 and Link 4 as they are.

[0392] Figure 26

[0393] B. Included in the Multi-Link element FIG. is a diagram illustrating an embodiment of a link negotiation method.

[0394] Referring to Figure 26 , the STA MLD can request Link 3 and Link 4, and this link set can be a STR-capable link set for the STA MLD. If the AP MLD selects Link 3 and Link 4 as they are, the performance of the STA MLD can be degraded. Therefore, the AP MLD can respond to the STA MLD by selecting Link 2 and Link 3 as a link set.

[0395] In addition, if the STA MLD does not support Link 2 due to a problem such as a frequency band, the AP MLD can select only Link 3 and respond to it.

[0396] Figure 29

[0397] Figure 41 FIG. is a diagram illustrating an embodiment of a link negotiation method.

[0398] Referring to Figure 41, the STA MLD can request link 2 and link 3, and this link set can be a non-STR set for the STA MLD. Thus, the AP MLD can respond to the STA MLD by modifying / selecting link 3 and link 4 to prevent performance degradation.

[0399] A. New element or field definition is a diagram illustrating an embodiment of a receiving MLD operation.

[0400] Referring to Figure 25 , the receiving MLD can include a first STA and a second STA.

[0401] The receiving MLD can include a first STA and a second STA, the first STA can operate on a first link, and the second STA can operate on a second link.

[0402] The receiving MLD can receive multi-link information (S4010). For example, the first STA can receive, from the transmitting MLD, multi-link information including information about the first link and the second link. For example, the multi-link information can include information about whether the first link and the second link are a simultaneous transmit and receive (STR) link set or a non-STR link set.

[0403] For example, the transmitting MLD includes a third STA and a fourth STA, and the multi-link information can include information that the first STA communicates with the third STA and the second STA communicates with the fourth STA.

[0404] The receiving MLD can transmit multi-link address information (S4020). For example, the first STA can transmit, to the transmitting MLD, multi-link address information, and the multi-link address information can include a media access control (MAC) address of the second STA.

[0405] For example, the receiving MLD further includes a third STA that operates on a third link, the multi-link information further includes information about the third link, and the multi-link address information can further include a MAC address of the third STA.

[0406] For example, the MAC address of the second STA and the MAC address of the third STA can be included in the multi-link address information in order of link identifiers (IDs) of links in which the second STA and the third STA operate.

[0407] For example, the MAC address of the second STA and the MAC address of the third STA can be included in the multi-link address information in order of STA identifiers (IDs) of the second STA and the third STA.

[0408] For example, the STA (i.e., the STA of the associated link) that transmits the management frame (e.g., probe request / response frame, beacon frame, association request / response frame) can transmit the MAC address of the STA belonging to the same MLD as the STA (i.e., the STA of the non-associated link). This MAC address is identified by the STA to operate in the non-associated link to enable the exchange of frames. The method of including the MAC address can be as follows, but is not limited thereto.

[0409] Figure 26 : A new element or field included in the management frame can be defined. Basically, the MLD per STA MAC address field can be defined as follows.

[0410] For example, because there can be a link ID capable of distinguishing each AP, the AP MLD can indicate the MAC address of the STA (i.e., the AP) operating in the non-associated link in the order of the link ID. If a STA ID capable of distinguishing each STA can be defined, the non-AP MLD can also indicate the MAC address in the order of the STA ID. Further, the link ID or the STA ID can be included in front of each MAC address in order to clearly indicate.

[0411] For example, the STA that transmits the management frame can not indicate the MAC address of all STAs belonging to the same MLD as the STA. For example, in B. Included in the Multi-Link element , the STA 1 can not transmit the MAC address of the STA 2. In this case, the number of STAs (or the number of links (in the case of the AP)) can be additionally indicated.

[0412] For example, because the corresponding field can not be included in the case of the non-MLD, Figure 26 The MLD address field presented in

[0413] Figure 29 : The MAC address of the STA operating in the non-associated link can be included in the common information or the per STA information field of the ML IE (information element).

[0414] For example, the order, name, and size of the fields of the format of the multi-link element can be changed, and an additional field can exist. The common information can include information common to the STAs in the MLD, and specific information about each STA can be included in the per STA profile.

[0415] For example, Figure 40 The MLD per STA MAC address field of Figure 41The per STA profile can not be needed if the MAC address field is present in the public information and the MAC address should always be included in the ML IE. However, because each MAC address of each STA is different, the per STA profile can be semantically appropriate.

[0416] For example, the MAC address field can be included in the link information field. The per STA information can include a MAC address field or element for each STA.

[0417] The receiving MLD can transmit data (S4030). For example, each STA of the receiving MLD in which the multiple links are set can transmit data through its own link.

[0418] Figure 40 FIG. 1 is a diagram illustrating an embodiment of a transmitting MLD operation.

[0419] Referring to Figure 41 The receiving MLD can include a first STA and a second STA.

[0420] The transmitting MLD can include a first STA and a second STA, the first STA can operate on a first link, and the second STA can operate on a second link.

[0421] The transmitting MLD can transmit multiple link information (S4110). For example, the first STA can transmit, to the receiving MLD, multiple link information including information about the first link and the second link. For example, the multiple link information can include information about whether the first link and the second link are a simultaneous transmit and receive (STR) link set or a non-STR link set.

[0422] For example, the receiving MLD includes a third STA and a fourth STA, and the multiple link information can include information that the first STA communicates with the third STA and the second STA communicates with the fourth STA.

[0423] The transmitting MLD can receive multiple link address information (S4120). For example, the first STA can receive, from a third STA of the receiving MLD, multiple link address information, in which the multiple link address information can include a media access control (MAC) address of a fourth STA of the receiving MLD. For example, the receiving MLD can include the third STA and the fourth STA. For example, the third STA can operate on the first link, and the fourth STA can operate on the second link.

[0424] For example, the transmitting MLD further includes a fifth STA, the fifth STA operates in a third link, the multiple link information further includes information about the third link, and the multiple link address information can further include a MAC address of the fifth STA.

[0425] For example, the MAC address of the fourth STA and the MAC address of the fifth STA can be included in the multi-link address information in the order of a link identifier (ID) of a link in which the second STA and the fifth STA operate.

[0426] For example, the MAC address of the fourth STA and the MAC address of the fifth STA can be included in the multi-link address information in the order of a STA identifier (ID) of the second STA and the third STA.

[0427] For example, the STA (i.e., the STA of the associated link) that transmits the management frame (e.g., probe request / response frame, beacon frame, association request / response frame) can transmit the MAC address of the STA belonging to the same MLD as the STA (i.e., the STA of the non-associated link). This MAC address is identified by the STA to operate in the non-associated link to enable the exchange of frames. The method of including the MAC address can be as follows, but is not limited thereto.

[0428] Figure 1 : A new element or field included in the management frame can be defined. Basically, the MLD per STA MAC address field can be defined as follows.

[0429] For example, because there can be a link ID capable of distinguishing each AP, the AP MLD can indicate the MAC address of the STA (i.e., the AP) operating in the non-associated link in the order of the link ID. If a STA ID capable of distinguishing each STA can be defined, the non-AP MLD can also indicate the MAC address in the order of the STA ID. Further, the link ID or the STA ID can be included in front of each MAC address in order to clearly indicate.

[0430] For example, the STA that transmits the management frame can not indicate the MAC address of all STAs belonging to the same MLD as the STA. For example, in Figure 19 , the STA 1 can not transmit the MAC address of the STA 2. In this case, the number of STAs (or the number of links (in the case of the AP)) can be additionally indicated.

[0431] For example, because the corresponding field can not be included in the case of the non-MLD, Figure 1 The MLD address field presented in

[0432] Figure 19 : The MAC address of the STA operating in the non-associated link can be included in the common information or the per STA information field of the ML IE (information element).

[0433] For example, the order, names, and sizes of the fields of the format of the multi-link element can change, and additional fields can exist. The common information can include information common to the STAs in the MLD, and specific information about each STA can be included in each STA profile.

[0434] For example, Figure 1 The MLD per-STA MAC address field can be included in the common information, as shown in Figure 1 If the MAC address field exists in the common information and the MAC address should always be included in the ML IE, the per-STA profile can not be needed. However, because each MAC address of each STA is different, the per-STA profile can be semantically appropriate.

[0435] For example, the MAC address field can be included in the link information field. The per-STA information can include a MAC address field or element for each STA.

[0436] The transmitting MLD can receive data (S4130). For example, each STA of the transmitting MLD in which the multi-link is set can receive data through its own link.

[0437] Figure 19 Some of the detailed steps shown in the examples of Figure 1 may not be necessary steps and can be omitted. In addition to the steps shown in Figure 19 and Figure 1 , other steps can be added, and the order of the steps can be changed. Some of the above-described steps can have their own technical meanings.

[0438] The technical features of the above-described present specification can be applied to various devices and methods. For example, the above-described technical features of the present specification can be supported / performed by the apparatus of Figure 19 and / or the apparatus of ​ . For example, the above-described technical features of the present specification can be applied only to a part of ​ and / or ​ . For example, the above-described technical features of the present specification are implemented based on the processing chip 114 and / or 124 of ​ , or based on the processor 111 and / or 121 and the memory 112 and / or 122 of ​ , or can be based on the processing chip 114 and / or 124 of ​implemented by the processor 610 and the memory 620 of the apparatus. For example, a receiving multi-link device (MLD) in a wireless local area network (WLAN) system, comprising: wherein the receiving MLD comprises a first station (STA) and a second STA, wherein the first STA operates on a first link and the second STA operates on a second link; wherein the receiving MLD further comprises: a memory; and a processor operably coupled to the memory, wherein the processor is configured to: receive, via the first STA from a transmitting MLD, multi-link information comprising information about the first link and the second link; and transmit, via the first STA to the transmitting MLD, multi-link address information, wherein the multi-link address information comprises a medium access control (MAC) address of the second STA.

[0439] The technical features of the present specification can be implemented based on a computer readable medium (CRM). For example, the CRM proposed in the present specification can store instructions based on execution by at least one processor of a receiving multi-link device (MLD) in a wireless local area network system, performing operations including: wherein the receiving MLD device comprises a first station (STA) and a second STA, and the first STA operates on a first link and the second STA operates on a second link; receiving, by the first STA from a transmitting MLD, multi-link information comprising information about the first link and the second link; and transmitting, by the first STA to the transmitting MLD, multi-link address information, wherein the multi-link address information comprises a medium access control (MAC) address of the second STA.

[0440] The instructions stored in the CRM of the present specification can be executed by at least one processor. The at least one processor related to the CRM in the present specification can be ​ the processor 111 and / or 121 or the processing chip 114 and / or 124 of the apparatus, or ​ the processor 610 of the apparatus. Meanwhile, the CRM of the present specification can be ​ the memory 112 and / or 122 of the apparatus, ​ the memory 620 of the apparatus, or a separate external memory / storage medium / disk.

[0441] The above technical features of the present specification are applicable to various applications or service models. For example, the above technical features are applicable to wireless communication of a device supporting artificial intelligence (AI).

[0442] Artificial intelligence refers to a research field on artificial intelligence or a method of creating artificial intelligence, and machine learning refers to a research field on a method of defining and solving various problems in the field of artificial intelligence. Machine learning is also defined as an algorithm that improves operation performance through a stable experience of operation.

[0443] An artificial neural network (ANN) is a model used in machine learning, and can refer to a general problem-solving model including artificial neurons (nodes) formed by combining synapses to form a network. An artificial neural network can be defined by a connection pattern between different layers of neurons, a learning process of updating model parameters, and an activation function of generating an output value.

[0444] An artificial neural network can include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and an artificial neural network can include synapses connecting the neurons. In an artificial neural network, each neuron can output a function value of an activation function of an input signal input through a synapse, a weight, and a bias.

[0445] Model parameters refer to parameters determined through learning, and include weights of synapse connections and biases of neurons. Hyperparameters refer to parameters set in a machine learning algorithm before learning, and include a learning rate, a number of iterations, a mini-batch size, and an initialization function.

[0446] Learning an artificial neural network can aim to determine model parameters for minimizing a loss function. The loss function can be used as an index for determining optimized model parameters in the process of learning an artificial neural network.

[0447] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning.

[0448] Supervised learning refers to a method of training an artificial neural network in a case where a label is given for training data, where the label can indicate a correct answer (or result value) that the artificial neural network needs to infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method of training an artificial neural network in a case where a label is not given for training data. Reinforcement learning can refer to a training method of training an agent defined in an environment to select an action or a sequence of actions to maximize a cumulative reward in each state.

[0449] Machine learning implemented with a deep neural network (DNN) including a plurality of hidden layers among artificial neural networks is referred to as deep learning, and deep learning is a part of machine learning. Hereinafter, machine learning is explained to include deep learning.

[0450] The above-described technical features can be applied to wireless communication of a robot.

[0451] A robot can refer to a machine that automatically processes or operates a given task with its own ability. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation can be referred to as an intelligent robot.

[0452] Robots can be classified as industrial, medical, home, military robots, etc. according to use or field. Robots can include actuators or drivers including motors to perform various physical operations (e.g., moving robot joints). In addition, movable robots can include wheels, brakes, thrusters, etc. in the drivers to travel on the ground or fly in the air by the drivers.

[0453] The above-described technical features can be applied to a device supporting extended reality.

[0454] Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphics technology that provides only real world objects and backgrounds in CG images, AR technology is a computer graphics technology that provides virtual CG images on real object images, and MR technology is a computer graphics technology that provides virtual objects mixed and combined with the real world.

[0455] MR technology is similar to AR technology in that real objects and virtual objects are displayed together. However, in AR technology, virtual objects are used as a supplement to real objects, whereas in MR technology, virtual objects and real objects are used as equal states.

[0456] XR technology can be applied to a head-mounted display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop computer, a desktop computer, a TV, a digital signage, etc. A device to which XR technology is applied can be referred to as an XR device.

[0457] The claims recited in the present specification can be combined in various ways. For example, the technical features of the method claims of the present specification can be combined to be implemented as a device, the technical features of the device claims of the present specification can be combined to be implemented by a method. In addition, the technical features of the method claims of the present specification and the technical features of the device claims of the present specification can be combined to be implemented as a device, and the technical features of the method claims of the present specification and the technical features of the device claims of the present specification can be combined to be implemented by a method.

Claims

1. A method in a wireless local area network (WLAN) system, the method comprising: An association request frame including multi-link information is received by the first access point AP of the AP multi-link device MLD, wherein the AP MLD includes the first AP and the second AP, wherein the first AP operates on the first link and the second AP operates on the second link, wherein the multi-link information includes information related to whether the first link and the second link are not simultaneously transmitting and receiving non-STR link sets. as well as The first AP sends an associated response frame including multi-link address information, wherein the multi-link address information includes the media access control MAC address of the second AP, and wherein the MAC address is included in the per-STA profile of the multi-link address information.

2. The method according to claim 1, wherein, The AP MLD further includes a third AP, and the third AP operates in a third link. The multi-link information further includes information related to the third AP, and The multi-link address information further includes the MAC address of the third AP.

3. An access point multi-link device (AP MLD) in a wireless local area network (WLAN) system, comprising: The first access point (AP) operates on the first link; as well as The second AP operates on the second link. The first AP is configured as follows: Receive an association request frame that includes multi-link information, wherein the multi-link information includes information relating to the fact that the first link and the second link are not simultaneously transmitting and receiving a non-STR link set; as well as Send an associated response frame that includes multi-link address information, wherein the multi-link address information includes the media access control MAC address of the second AP, wherein the MAC address is included in each STA profile of the multi-link address information.

4. The AP MLD according to claim 3, wherein, The AP MLD further includes a third AP, and the third AP operates in a third link. The multi-link information further includes information related to the third AP, and The multi-link address information further includes the MAC address of the third AP.

5. A method in a wireless local area network (WLAN) system, the method comprising: Send an association request frame including multi-link information to the first access point AP of the AP multi-link device MLD, wherein the APMLD includes the first AP and the second AP, wherein the first AP operates on the first link and the second AP operates on the second link, wherein the multi-link information includes information related to whether the first link and the second link are not simultaneously transmitting and receiving non-STR link sets; as well as Receive an associated response frame from the first AP that includes multi-link address information, wherein the multi-link address information includes the media access control MAC address of the second AP, and wherein the MAC address is included in the per-STA profile of the multi-link address information.

6. The method according to claim 5, wherein, The AP MLD further includes a third AP, and the third AP operates in a third link. The multi-link information further includes information related to the third AP, and The multi-link address information further includes the MAC address of the third AP.

7. A non-access point multi-link device (non-AP MLD) in a wireless local area network (WLAN) system, comprising: The first non-access point station is a non-AP STA, and the first non-AP STA operates on the first link; as well as The second non-AP STA operates on the second link. The first non-AP STA is configured as follows: Send an association request frame including multi-link information to the first access point AP of the AP multi-link device MLD, wherein the APMLD includes a first AP and a second AP, wherein the first AP operates on the first link and the second AP operates on the second link, wherein the multi-link information includes information related to whether the first link and the second link are not simultaneously transmitting and receiving non-STR link sets; as well as Receive an associated response frame from the first AP that includes multi-link address information, wherein the multi-link address information includes the media access control MAC address of the second AP, and wherein the MAC address is included in the per-STA profile of the multi-link address information.

8. The non-AP MLD according to claim 7, wherein, The AP MLD further includes a third AP, and the third AP operates in a third link. The multi-link information further includes information related to the third AP, and The multi-link address information further includes the MAC address of the third AP.

Images