Link settings for multi-link operation

Abstract

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

Description

Technical Field

[0001] The present specification relates to a link setting method for multi-link operation in a wireless local area network (WLAN) system. Background Art

[0002] Wireless network technology may include various types of wireless local area networks (WLANs). WLANs employ widely used network protocols and can be used to interconnect nearby devices. 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 wireless protocol family. 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 downlink multi-user multiple input multiple output (DL MU MIMO) schemes.

[0003] This specification proposes technical features that can be used in new communication standards. For example, the new communication standard may be the Extreme High Throughput (EHT) standard currently under discussion. The EHT standard may 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 may be referred to as the IEEE 802.11be standard. Summary of the Invention

[0004] Technical Solution

[0005] According to various embodiments of the present disclosure, a method performed by a transmitting device in a wireless local area network (WLAN) system may 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, wherein the receiving MLD device includes a first station (STA) and a second STA, the first STA operating on a first link and the second STA operating on a second link. The first STA may receive multi-link information including information related to the first link and the second link from the transmitting MLD. The first STA may send multi-link address information to the transmitting MLD. The multi-link address information may include a media access control (MAC) address of the second STA.

[0006] Technical Effects

[0007] According to the examples of this specification, after multilink setup, relevant information can be transmitted to enable signal transmission / reception between established links. During the multilink setup phase, inter-link capability information is exchanged, and information regarding which link to use for multilink operation is exchanged. However, a method for starting signal transmission / reception between links performing multilink operation has not yet been defined.

[0008] According to an example of the present specification, the STA performing multi-link setting may 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.

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

[0010] Figure 1 This shows an example of a transmitting device and / or a receiving device in this specification.

[0011] Figure 2 is a conceptual view showing the structure of a wireless local area network (WLAN).

[0012] Figure 3 Shows the general link establishment process.

[0013] Figure 4 An example of PPDU used in the IEEE standard is shown.

[0014] Figure 5 The layout of resource units (RUs) used in a 20 MHz frequency band is shown.

[0015] Figure 6 The layout of RUs used in the 40 MHz frequency band is shown.

[0016] Figure 7 The layout of RUs used in the 80 MHz frequency band is shown.

[0017] Figure 8 The structure of the HE-SIG-B field is shown.

[0018] Figure 9 This example shows an example of allocating multiple user STAs to the same RU through the MU-MIMO scheme.

[0019] Figure 10 The operation based on UL-MU is shown.

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

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

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

[0023] Figure 14 Describe the technical features of the UORA solution.

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

[0025] Figure 16 Shows an example of channels used / supported / defined in the 5 GHz band.

[0026] Figure 17 Shown are examples of channels used / supported / defined in the 6 GHz band.

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

[0028] Figure 19 An example of a modified transmission device and / or reception device of the present specification is shown.

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

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

[0031] Figure 22 is a diagram illustrating an embodiment of the STR capability of multiple links.

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

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

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

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

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

[0037] Figure 29 is a diagram illustrating an embodiment of an ML IE.

[0038] Figure 30 is a diagram illustrating an embodiment of an ML IE.

[0039] Figure 31 is a diagram illustrating an embodiment of a method for transmitting an initial frame in a non-associated link.

[0040] Figure 32 It is a diagram showing an embodiment of A-1.

[0041] Figure 33 It is a diagram showing an embodiment of Figure A-3.

[0042] Figure 34 It is a diagram illustrating an embodiment of the A-4 method and the B-1 method.

[0043] Figure 35 is a diagram illustrating an embodiment of a multi-link setting method.

[0044] Figure 36 is a diagram illustrating an embodiment of operations related to link capabilities.

[0045] Figure 37 、 Figure 38 and Figure 39 is a diagram illustrating an embodiment of a link negotiation method.

[0046] Figure 40 is a diagram illustrating an embodiment of a receive MLD operation.

[0047] Figure 41 is a diagram illustrating an embodiment of a send MLD operation. DETAILED DESCRIPTION

[0048] In this specification, "A or B" may mean "only A," "only B," or "both A and B." In other words, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B, or C" may mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0049] As used herein, a slash ( / ) or a comma may represent "and / or." For example, "A / B" may represent "A and / or B." Thus, "A / B" may represent "only A," "only B," or "both A and B." For example, "A, B, C" may represent "A, B, or C."

[0050] In this specification, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, in this specification, the expression "at least one of A or B" or "at least one of A and / or B" may be interpreted as "at least one of A and B".

[0051] In addition, in this specification, "at least one of A, B, and C" may 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" may mean "at least one of A, B, and C."

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

[0053] Technical features described separately in one drawing of this specification may be implemented separately or simultaneously.

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

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

[0056] Figure 1 This shows an example of a transmitting device and / or a receiving device in this specification.

[0057] exist Figure 1 In the example, various technical features described below can be performed. Figure 1At least one station (STA) is involved. For example, the STAs 110 and 120 in this specification may also be referred to by various terms such as mobile terminals, wireless devices, wireless transmit / receive units (WTRUs), user equipment (UEs), mobile stations (MSs), mobile subscriber units, or simply users. The STAs 110 and 120 in this specification may also be referred to by various terms such as networks, base stations, Node Bs, access points (APs), repeaters, routers, and relays. The STAs 110 and 120 in this specification may also be referred to by various names such as receiving devices, transmitting devices, receiving STAs, transmitting STAs, receiving devices, and transmitting devices.

[0058] For example, the STAs 110 and 120 may function as APs or non-APs. That is, the STAs 110 and 120 of this specification may function as APs and / or non-APs.

[0059] In addition to the IEEE 802.11 standard, the STAs 110 and 120 of this specification can support various communication standards. For example, communication standards based on 3GPP standards (e.g., LTE, LTE-A, 5G NR standards) can be supported. In addition, the STAs of this specification can be implemented as various devices such as mobile phones, vehicles, and personal computers. In addition, the STAs of this specification can support communication for various communication services such as voice calls, video calls, data communications, and self-driving (autonomous driving).

[0060] The STAs 110 and 120 of the present specification may include a medium access control (MAC) compliant with the IEEE 802.11 standard and a physical layer interface for a radio medium.

[0061] The following will refer to Figure 1 STAs 110 and 120 are described in sub-figure (a) of FIG.

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

[0063] The transceiver 113 of the first STA performs signal transmission / reception operations, and specifically, can transmit / receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0064] For example, the first STA 110 may perform operations expected by the AP. For example, the AP's processor 111 may receive signals via the transceiver 113, process the received (RX) signals, generate transmitted (TX) signals, and provide control over signal transmission. The AP's memory 112 may store signals received via the transceiver 113 (e.g., RX signals) and may store signals to be transmitted via the transceiver (e.g., TX signals).

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

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

[0067] For example, the operation of a device indicated as an AP in the following description may be performed in the first STA 110 or the second STA 120. For example, if the first STA 110 is an AP, the operation of the device indicated as the AP may be controlled by the processor 111 of the first STA 110, and related signals may 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 AP or the AP's TX / RX signals may be stored in the memory 112 of the first STA 110. In addition, if the second STA 120 is an AP, the operation of the device indicated as the AP may be controlled by the processor 121 of the second STA 120, and related signals may 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 AP or the AP's TX / RX signals may be stored in the memory 122 of the second STA 120.

[0068] For example, in the following description, the operation of a device indicated as a non-AP (or user STA) may 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 the non-AP may be controlled by the processor 121 of the second STA 120, and related signals may 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 may be stored in the memory 122 of the second STA 120. For example, if the first STA 110 is a non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 111 of the first STA 110, and related signals may 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 may be stored in the memory 112 of the first STA 110.

[0069] In the following description, devices referred to as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to Figure 1 For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. (but without specific reference numerals) may refer to Figure 1 For example, in the following example, the operations of various STAs transmitting / receiving signals (eg, PPDU) may be performed in Figure 1 In addition, in the following examples, the operations of various STAs generating TX / RX signals or performing data processing and calculations in advance for TX / RX signals can be performed in Figure 111 and 121. For example, examples of operations for generating TX / RX signals or performing data processing and calculation in advance may include: 1) determining / obtaining / configuring / calculating / decoding / encoding bit information of subfields (SIG, STF, LTF, data) included in the PPDU; 2) determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) for the subfields (SIG, STF, LTF, data) included in the PPDU; 3) determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an additional sequence applied to the SIG) for the subfields (SIG, STF, LTF, data) included in the PPDU; 4) power control operations and / or power saving operations applied to STAs; and 5) operations related to determining / obtaining / configuring / decoding / encoding of ACK signals. In addition, 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 / encode TX / RX signals may be stored in Figure 1 in memories 112 and 122 .

[0070] Figure 1 The aforementioned device / STA of sub-graph (a) can be as follows Figure 1 In the following, we will modify the Figure 1 Sub-figure (b) of FIG. 1 is used to describe STA 110 and STA 120 of this specification.

[0071] For example, Figure 1 The transceivers 113 and 123 shown in the sub-diagram (b) can perform the same Figure 1 The same functions as the aforementioned transceiver shown in sub-figure (a) of FIG. 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 the sub-diagram (b) of FIG. Figure 1 The aforementioned processors 111 and 121 and memories 112 and 122 shown in sub-Figure (a) have the same functions.

[0072] The mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, user, user STA, network, base station, Node B, access point (AP), repeater, router, relay, receiving unit, transmitting unit, receiving STA, transmitting STA, receiving device, transmitting device, receiving apparatus and / or transmitting apparatus described below may mean Figure 1 STAs 110 and 120 shown in sub-figures (a) / (b) of FIG. 110 and 120, or may mean Figure 1 The processing chips 114 and 124 shown in the sub-figure (b) of FIG. In other words, the technical features of this specification can be Figure 1 The STA 110 and 120 shown in the sub-figures (a) / (b) of FIG. 110 and 120 may be executed only in Figure 1 The processing chips 114 and 124 shown in the sub-figure (b) of FIG. Figure 1 For example, the technical feature of sending a control signal from a STA can be understood as the transceiver 113 and 123 shown in the sub-figure (a) / (b) of FIG. Figure 1 The transceiver 113 shown in the sub-figures (a) / (b) of FIG. Figure 1 Alternatively, the technical feature of the control signal generated by the processors 111 and 121 illustrated in the sub-figures (a) / (b) of FIG. 1 may be understood as the technical feature of the control signal generated by the processors 111 and 121. Figure 1 The technical features of the processing chips 114 and 124 shown in sub-figure (b) of FIG. 10 are those for generating control signals to be transmitted to the transceivers 113 and 123 .

[0073] For example, the technical feature of receiving the control signal by the receiving STA can be understood as Figure 1 Alternatively, the technical feature of the receiving STA receiving the control signal can be understood as the technical feature of the receiving STA receiving the control signal through Figure 1 The processors 111 and 121 shown in the sub-diagram (a) of Figure 1 Alternatively, the technical feature of the receiving STA receiving the control signal can be understood as the technical feature of the control signal received by the transceiver 113 and 123 shown in the sub-figure (a) of FIG. Figure 1 The processing chips 114 and 124 shown in the sub-graph (b) of FIG. Figure 1 Technical characteristics of the control signals received in transceivers 113 and 123 shown in sub-figure (b).

[0074] Reference Figure 1 , software codes 115 and 125 may be included in memories 112 and 122. The software codes 115 and 126 may include instructions for controlling operations of the processors 111 and 121. The software codes 115 and 125 may be included as various programming languages.

[0075] Figure 1 The processors 111 and 121 or the 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 1 The processors 111 and 121 or the processing chips 114 and 124 may include at least one of the following: a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, Figure 1 The processors 111 and 121 or the processing chips 114 and 124 may be composed of SNAPDRAGONTM processor series manufactured by EXYNOSTM processor series manufactured by Processor family manufactured by HELIOTM processor series manufactured by The ATOMTM processor series manufactured by or enhanced from these processors.

[0076] In this specification, the uplink may refer to a link for communication from a non-AP STA to an SP STA, and uplink PPDUs / packets / signals, etc. may be transmitted through the uplink. In addition, in this specification, the downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted through the downlink.

[0077] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0078] Figure 2 The upper portion of shows the structure of an infrastructure Basic Service Set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11.

[0079] Reference Figure 2 The wireless LAN system may include one or more infrastructure BSSs 200 and 205 (hereinafter referred to as BSSs). BSSs 200 and 205, which are a collection of APs and STAs (e.g., access point (AP) 225 and station (STA1) 200-1) that have successfully synchronized to communicate with each other, do not represent a specific area. BSS 205 may include one or more STAs 205-1 and 205-2 that can join one AP 230.

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

[0081] The distribution system 210 may implement an extended service set (ESS) 240 that is extended by connecting a plurality of BSSs 200 and 205. The ESS 240 may be used as a term indicating one network configured by connecting one or more APs 225 or 230 via the distribution system 210. APs included in one ESS 240 may have the same service set identifier (SSID).

[0082] The portal 220 may serve as a bridge connecting a wireless LAN network (IEEE 802.11) and another network (eg, 802.X).

[0083] exist Figure 2 In the BSS shown in the upper portion of FIG, a network between APs 225 and 230 and a network between APs 225 and 230 and STAs 200-1, 205-1, and 205-2 can be implemented. However, a network can be configured between STAs to perform communication even without APs 225 and 230. A network that performs communication by configuring a network between STAs even without APs 225 and 230 is defined as an ad hoc network or an independent basic service set (IBSS).

[0084] Figure 2 The lower part of FIG shows a conceptual diagram showing an IBSS.

[0085] Reference Figure 2 The IBSS is a BSS operating in self-organizing mode. Because the IBSS does not include an access point (AP), there is no centralized management entity that performs management functions. 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 mobile STAs and are not allowed to access the DS, forming a self-contained network.

[0086] Figure 3 The figure shows the general link establishment process.

[0087] In S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation by the STA. That is, in order to access a network, the STA needs to discover participating networks. Before joining a wireless network, the STA needs to identify compatible networks. The process of identifying networks in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0088] Figure 3The diagram shows a network discovery operation including 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 AP is 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 may be the STA that sent the last beacon frame in the BSS of the channel being scanned. In the BSS, since the AP sends the beacon frame, the AP is the responder. In the IBSS, since the STAs in the IBSS take turns sending beacon frames, the responder is not fixed. For example, when a STA sends a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA may store the BSS-related information included in the received probe response frame, may move to the next channel (e.g., channel 2), and may perform scanning by the same method (e.g., sending a probe request and receiving a probe response via channel 2).

[0089] although Figure 3 Not shown in the figure, scanning can be performed by a passive scanning method. 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 sent to indicate the existence of a wireless network and enable the STA performing the scan to find the wireless network and join the wireless network. In the BSS, the AP is used to periodically send beacon frames. In the IBSS, the STAs in the IBSS take turns sending beacon frames. Upon receiving the beacon frame, the STA performing the scan stores information about the BSS included in the beacon frame and records beacon frame information in each channel while moving to another channel. The STA that receives 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.

[0090] After discovering the network, the STA may perform an authentication process in S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the subsequent security establishment operation in S340. The authentication process in S320 may 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 frames used for authentication requests / responses are management frames.

[0091] The authentication frame may 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 limited round-robin group.

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

[0093] When the STA is successfully authenticated, the STA may perform an association process in S330. The association process includes a process in which the STA sends an association request frame to the AP and the AP sends an association response frame to the STA in response. For example, the association request frame may include information about various capabilities, a beacon listening interval, a service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operation category, a traffic indication map (TIM) broadcast request, and interworking service capabilities. For example, the association response frame may include information about various capabilities, a status code, an association ID (AID), supported rates, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise ratio indicator (RSNI), a mobility domain, a timeout interval (association recovery time), overlapping BSS scan parameters, a TIM broadcast response, and a QoS map.

[0094] In S340, the STA may perform a security establishment process. The security establishment process in S340 may include a process of establishing a private key through a four-way handshake (eg, through an Extensible Authentication Protocol over LAN (EAPOL) frame).

[0095] Figure 4 An example of a PPDU used in the IEEE standard is shown.

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

[0097] Figure 4 An example of HE PPDU according to IEEE 802.11ax is also included. Figure 4 The HE PPDU is an exemplary PPDU for multiple users. The HE-SIG-B may be included only in the PPDU for multiple users and may be omitted in the PPDU for a single user.

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

[0099] The following describes a resource unit (RU) used for a PPDU. A RU can include multiple subcarriers (or tones). A RU can be used to transmit signals to multiple STAs using OFDMA. Furthermore, a RU can be defined as transmitting signals to a single STA. A RU can be used for the STF, LTF, data field, and more.

[0100] Figure 5 The figure shows the layout of resource units (RUs) used in a 20 MHz frequency band.

[0101] like Figure 5 As shown, 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, HE-LTF, and data fields in the RU shown.

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

[0103] Figure 5 The layout of the RU in can be used not only for multiple users (MU) but also for single users (SU), in which case one 242 unit can be used and three DC tones can be inserted, as shown in FIG. Figure 5 As shown at the bottom.

[0104] although Figure 5 RUs of various sizes are proposed, namely, 26-RU, 52-RU, 106-RU, and 242-RU, but RUs of a particular size may be expanded or increased. Therefore, the present embodiment is not limited to a particular size of each RU (ie, the number of corresponding tones).

[0105] Figure 6 The figure shows the layout of RUs used in the 40 MHz frequency band.

[0106] Similar to using RUs with various sizes Figure 5 ,exist Figure 6 In the example, 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.

[0107] like Figure 6 As shown, when the RU layout is used for a single user, 484-RU can be used. The specific number of RUs can be similar to Figure 5 Change.

[0108] Figure 7 The figure shows the layout of RUs used in the 80 MHz frequency band.

[0109] Similar to using RUs with various sizes Figure 5 and Figure 6 ,exist Figure 7 Examples of the 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, and the like can be used. Furthermore, seven DC tones can be inserted into 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. Furthermore, a 26-RU can be used, corresponding to 13 tones on each side of the DC band.

[0110] like Figure 7 As shown, when the RU layout is for a single user, a 996-RU can be used, in which case five DC tones can be inserted.

[0111] 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, the transmitting STA (e.g., AP) can allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA through the trigger frame, and can allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. Thereafter, the first STA can send a first triggered-based PPDU based on the first RU, and the second STA can send a second triggered-based PPDU based on the second RU. The first / second triggered-based PPDUs are sent to the AP in the same (or overlapping) time period.

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

[0113] Information about the layout of RUs may be signaled via HE-SIG-B.

[0114] Figure 8 The structure of the HE-SIG-B field is shown.

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

[0116] like Figure 8 As shown, the common field 820 and the user-specific field 830 may be encoded separately.

[0117] The common field 820 may include N*8 bits of RU allocation information. For example, the RU allocation information may include information related to the location of the RU. For example, when Figure 5 When a 20 MHz channel is used as shown, the RU allocation information may include information about a specific frequency band where a specific RU (26-RU / 52-RU / 106-RU) is arranged.

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

[0119] [Table 1]

[0120]

[0121] like Figure 5As shown in the example of , up to nine 26-RUs can be allocated to a 20 MHz channel. When the RU allocation information of the common field 820 is set to "00000000" as shown in Table 1, nine 26-RUs can be allocated to the corresponding channel (i.e., 20 MHz). In addition, when the RU allocation information of the common field 820 is set to "00000001" as shown in Table 1, seven 26-RUs and one 52-RU are arranged in the corresponding channel. That is, in Figure 5 In the example of , a 52-RU can be allocated to the far right, and seven 26-RUs can be allocated to its left.

[0122] The example in Table 1 shows only some RU positions where RU allocation information can be displayed.

[0123] For example, the RU allocation information may include the example in Table 2 below.

[0124] [Table 2]

[0125]

[0126] "01000y2y1y0" refers 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 thereof. In this case, multiple STAs (e.g., user STAs) can be allocated to the 106-RU based on the MU-MIMO scheme. Specifically, up to eight 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 the 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.

[0127] Typically, multiple STAs (e.g., user STAs) that are different from each other can be assigned to multiple RUs. However, multiple STAs (e.g., user STAs) can be assigned to one or more RUs of at least a specific size (e.g., 106 subcarriers) based on the MU-MIMO scheme.

[0128] like Figure 8As shown, the user-specific field 830 may include multiple user fields. As described above, the number of STAs (e.g., user STAs) assigned to a specific channel may 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 may be assigned to each of the nine 26-RUs (e.g., nine user STAs may be assigned). That is, up to nine user STAs may be assigned to a specific channel through the OFDMA scheme. In other words, up to nine user STAs may be assigned to a specific channel through a non-MU-MIMO scheme.

[0129] For example, when RU allocation is set to "01000y2y1y0", multiple STAs can be allocated to the 106-RU arranged on the leftmost side by the MU-MIMO scheme, and five user STAs can be allocated to the five 26-RUs arranged on its right side by the non-MU MIMO scheme. Figure 9 .

[0130] Figure 9 This figure illustrates an example of allocating multiple user STAs to the same RU through the MU-MIMO scheme.

[0131] For example, when Figure 9 When the RU allocation is set to "01000010," a 106-RU can be allocated to the leftmost side of a specific channel, and five 26-RUs can be allocated to its right. Furthermore, three user STAs can be allocated to the 106-RU using the MU-MIMO scheme. Consequently, since eight user STAs are allocated, the user-specific field 830 of the HE-SIG-B can include eight user fields.

[0132] Eight user fields can be pressed Figure 9 In addition, Figure 8 As shown, two user fields can be implemented using one user block field.

[0133] Figure 8 and Figure 9 The user field shown can be configured based on two formats. That is, the user field related to the MU-MIMO scheme can be configured in a first format, and the user field related to the non-MIMO scheme can be configured in a second format. Figure 9 For example, User Field 1 to User Field 3 may be based on the first format, and User Field 4 to User Field 8 may be based on the second format. The first format or the second format may include bit information of the same length (eg, 21 bits).

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

[0135] For example, the first bits (i.e., B0-B10) in the user field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of the user STA that allocates the corresponding user field. Furthermore, the second bits (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to the spatial configuration. Specifically, examples of the second bits (i.e., B11-B14) may be shown in Tables 3 and 4 below.

[0136] [Table 3]

[0137]

[0138] [Table 4]

[0139]

[0140] As shown in Table 3 and / or Table 4, the second bits (e.g., B11-B14) may include information related to the number of spatial streams allocated to multiple user STAs allocated based on the MU-MIMO scheme. Figure 9 When three user STAs are allocated to 106-RU based on the MU-MIMO scheme, N_user is set to "3". Therefore, the values ​​of N_STS[1], N_STS[2], and N_STS[3] can be determined as shown in Table 3. For example, when the value of the second bit (B11-B14) is "0011", it can be set to N_STS[1]=4, N_STS[2]=1, N_STS[3]=1. That is, in Figure 9 In the example of , four spatial streams may be allocated to user field 1, one spatial stream may be allocated to user field 1, and one spatial stream may be allocated to user field 3.

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

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

[0143] MCS, MCS information, MCS index, MCS field, etc. used in this specification may be indicated by an index value. For example, MCS information may be indicated by indexes 0 to 11. MCS information may include information related to constellation modulation types (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information related to coding rates (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6e, etc.). Information related to channel coding types (e.g., LCC or LDPC) may not be included in the MCS information.

[0144] In addition, the fourth bit (ie, B19) in the user field (ie, 21 bits) may be a reserved field.

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

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

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

[0148] Figure 10UL-MU-based operations are shown. As shown, a transmitting STA (e.g., an AP) may perform channel access through contention (e.g., a backoff operation) and may transmit a trigger frame 1030. That is, the transmitting STA may 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 SIFS.

[0149] The TB PPDUs 1041 and 1042 may be transmitted at the same time period and may be transmitted from a plurality of STAs (eg, user STAs) having the AID indicated in the trigger frame 1030. The ACK frame 1050 for the TB PPDU may be implemented in various forms.

[0150] Reference Figures 11 to 13 Describes the specific characteristics of the trigger frame. Even when using UL-MU communication, either the Orthogonal Frequency Division Multiple Access (OFDMA) scheme or the MU-MIMO scheme may be used, and both OFDMA and MU-MIMO schemes may be used simultaneously.

[0151] Figure 11 An example of a trigger frame is shown. Figure 11 The trigger frame allocates resources for uplink multi-user (MU) transmission and may be sent, for example, from an AP. The trigger frame may be configured by a MAC frame and may be included in a PPDU.

[0152] Figure 11 The various fields shown may be partially omitted, and another field may be added. In addition, the length of each field may be changed to be different from that shown in the figure.

[0153] Figure 11 The frame control field 1110 may include information related to the MAC protocol version and additional control information. The duration field 1120 may include time information configured by the NAV or information related to an identifier (eg, AID) of the STA.

[0154] In addition, the RA field 1130 may include the address information of the receiving STA of the corresponding trigger frame and may optionally be omitted. The TA field 1140 may include the address information of the STA (e.g., AP) that sends the corresponding trigger frame. The public information field 1150 includes public control information applied to the receiving STA that receives the corresponding trigger frame. For example, it may include a field indicating the length of the L-SIG field of the uplink PPDU sent in response to the corresponding trigger frame or information for controlling the content of the SIG-A field (i.e., HE-SIG-A field) of the uplink PPDU sent in response to the corresponding trigger frame. In addition, as public control information, information related to the length of the CP of the uplink PPDU sent in response to the corresponding trigger frame or information related to the length of the LTF field may be included.

[0155] In addition, it is preferred to include Figure 11 The number of STAs receiving the trigger frame corresponds to the per-user information fields 1160 # 1 to 1160 # N. The per-user information field may also be referred to as an “allocation field”.

[0156] in addition, Figure 11 The trigger frame may include a padding field 1170 and a frame check sequence field 1180.

[0157] Figure 11 Each of the illustrated per-user information fields 1160#1 through 1160#N may include a plurality of subfields.

[0158] Figure 12 An example of the common information field of a trigger frame is shown. Figure 12 The subfields of the FIFO may be partially omitted, and additional subfields may be added. In addition, the length of each subfield shown may be changed.

[0159] The length field 1210 shown has the same value as the length field of the L-SIG field of the uplink PPDU transmitted in response to the corresponding trigger frame, and the length field of the L-SIG field of the uplink PPDU indicates the 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.

[0160] In addition, the tandem identifier field 1220 indicates whether tandem operation is performed. Tandem operation means that downlink MU transmission and uplink MU transmission are performed together in the same TXOP. In other words, it means that downlink MU transmission is performed, and then uplink MU transmission is performed after a preset time (e.g., SIFS). During tandem operation, only one transmitting device (e.g., an AP) can perform downlink communication, and multiple transmitting devices (e.g., non-APs) can perform uplink communication.

[0161] The CS request field 1230 indicates whether a wireless medium status or NAV, etc. must be considered in case that a reception device that has received a corresponding trigger frame transmits a corresponding uplink PPDU.

[0162] The HE-SIG-A information field 1240 may include information for controlling the content of the SIG-A field (ie, HE-SIG-A field) of the uplink PPDU in response to the corresponding trigger frame.

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

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

[0165] 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 the above reference Figure 11 Any of the mentioned per-user information fields 1160#1 to 1160#N. Included in Figure 13 The subfields in the user information field 1300 may be partially omitted, and additional subfields may be added. In addition, the lengths of the various subfields shown may be changed.

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

[0167] In addition, the RU allocation field 1320 may be included. That is, when the receiving STA identified by the user identifier field 1310 transmits a 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 may be Figure 5 、 Figure 6 and Figure 7 RU shown.

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

[0169] in addition, Figure 13 The subfields of the 1340 may include an MCS field 1340. The MCS field 1340 may indicate the MCS scheme applied to the TB PPDU. For example, when BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to "1", and when LDPC coding is applied, the coding type field 1330 may be set to "0".

[0170] Hereinafter, a UL OFDMA-based random access (UORA) scheme will be described.

[0171] Figure 14 Describe the technical features of the UORA solution.

[0172] The sending STA (e.g., AP) can Figure 14 Specifically, the AP may allocate the first RU resource (AID 0, RU 1), the second RU resource (AID 0, RU 2), the third RU resource (AID 0, RU 3), the fourth RU resource (AID 2045, RU 4), ​​the fifth RU resource (AID 2045, RU 5), and the sixth RU resource (AID 3, RU 6). Information related to AID 0, AID 3, or AID 2045 may be included in, for example, Figure 13 The information related to RU1 to RU6 may be included in the user identifier field 1310. Figure 13 RU allocation field 1320. AID=0 may mean UORA resources for associated STAs, and AID=2045 may mean UORA resources for non-associated STAs. Figure 14 The 1st to 3rd RU resources can be used as UORA resources for associated STAs. Figure 14 The 4th RU resource and the 5th RU resource can be used as UORA resources for non-associated STAs. Figure 14 The 6th RU resources may be used as typical resources for UL MU.

[0173] exist Figure 14In the example, STA1's OFDMA random access backoff (OBO) is reduced to 0, and STA1 randomly selects the second RU resource (AID 0, RU 2). In addition, since STA2 / 3's OBO counter is greater than 0, no uplink resources are allocated to STA2 / 3. Figure 14 For STA4 in FIG, since the AID of STA4 (eg, AID=3) is included in the trigger frame, resources of RU 6 are allocated without backoff.

[0174] Specifically, due to Figure 14 STA1 is the associated STA, so the total number of eligible RA RUs for STA1 is 3 (RU1, RU2 and RU3), so STA1 decrements the OBO counter by 3 to make the OBO counter 0. In addition, since Figure 14 STA2 is the associated STA, so the total number of eligible RA RUs for STA2 is 3 (RU 1, RU 2 and RU 3), so STA2 decrements the OBO counter by 3, but the OBO counter is greater than 0. In addition, since Figure 14 STA3 is a non-associated STA, so the total number of eligible RA RUs for STA3 is 2 (RU 4, RU 5), so STA3 decrements the OBO counter by 2, but the OBO counter is greater than 0.

[0175] Figure 15 An example of channels used / supported / defined in the 2.4 GHz frequency band is shown.

[0176] The 2.4 GHz band may be referred to as other terms such as a first frequency band. Additionally, the 2.4 GHz band may refer to a frequency domain that uses / supports / defines channels with center frequencies close to 2.4 GHz (eg, channels with center frequencies within 2.4 to 2.5 GHz).

[0177] Multiple 20 MHz channels may be included in the 2.4 GHz band. 20 MHz within 2.4 GHz may have multiple channel indices (e.g., index 1 to index 14). For example, the center frequency of a 20 MHz channel assigned with channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned with channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned with channel index N may be (2.407+0.005*N) GHz. Channel indices may be referred to by various terms such as channel numbers. The specific values ​​of channel indices and center frequencies may vary.

[0178] Figure 15An example is given of four channels within the 2.4 GHz frequency band. Each of the first frequency domain 1510 to the fourth frequency domain 1540 shown herein may include one channel. For example, the first frequency domain 1510 may include channel 1 (a 20 MHz channel with index 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency domain 1520 may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency domain 1530 may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency domain 1540 may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0179] Figure 16 An example of channels used / supported / defined in the 5 GHz frequency band is shown.

[0180] The 5 GHz frequency band may be referred to by other terms such as a second frequency band. The 5 GHz frequency band may refer to a frequency domain that uses / supports / defines channels with a center frequency greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz). Alternatively, the 5 GHz frequency band may include multiple channels between 4.5 GHz and 5.5 GHz. Figure 16 The specific values ​​shown may vary.

[0181] 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 called UNII Mid and UNII-2 Extended. UNII-3 can be referred to as UNII Upper.

[0182] Multiple channels can be configured within the 5 GHz frequency band, and the bandwidth of each channel can be set to various values, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range can be divided into four channels using a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range can be divided into two channels using an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range can be divided into one channel using a 160 MHz frequency domain.

[0183] Figure 17 An example of channels used / supported / defined in the 6 GHz frequency band is shown.

[0184] The 6 GHz frequency band may be referred to by other terms such as a third frequency band, etc. The 6 GHz frequency band may mean a frequency domain that uses / supports / defines channels having a center frequency greater than or equal to 5.9 GHz. Figure 17 The specific values ​​shown may be changed.

[0185] For example, Figure 17 The 20MHz channel can be defined starting from 5.940GHz. Figure 17 Among the 20 MHz channels, the leftmost channel may have an index of 1 (or channel index, channel number, etc.), and 5.945 GHz may be assigned as the center frequency. That is, the center frequency of the channel of index N may be determined to be (5.940+0.005*N) GHz.

[0186] therefore, Figure 17 The indices (or channel numbers) of the 2 MHz channels 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 17 The indices of the 40 MHz channels 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.

[0187] Despite Figure 17 20, 40, 80, and 160 MHz channels are illustrated in the example of FIG, but a 240 MHz channel or a 320 MHz channel may be additionally added.

[0188] Hereinafter, the PPDU transmitted / received in the STA of this specification will be described.

[0189] Figure 18 This figure shows an example of a PPDU used in this specification.

[0190] Figure 18The PPDU of the present invention may be referred to by various terms such as EHT PPDU, TX PPDU, RX PPDU, first type or Nth type PPDU, etc. For example, in this specification, PPDU or EHT PPDU may be referred to by various terms such as TX PPDU, RX PPDU, first type or Nth type PPDU, etc. In addition, the EHT PPDU may be used in the EHT system and / or a new WLAN system enhanced from the EHT system.

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

[0192] exist Figure 18 In the physical layer, L-STF to EHT-LTF may be referred to as a preamble or a physical preamble and may be generated / sent / received / obtained / decoded in the physical layer.

[0193] You can Figure 18 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.

[0194] exist Figure 18 In the PPDU of the IEEE 802.11a PPDU, the L-LTF and L-STF can be the same as those in the regular fields.

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

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

[0197] The transmitting STA can generate the RL-SIG 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 whether the RX PPDU is a HE PPDU or an EHT PPDU.

[0198] Universal SIG (U-SIG) can be inserted in Figure 18 The U-SIG can be referred to by various terms such as first SIG field, first SIG, first type SIG, control signal, control signal field, first (type) control signal, etc.

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

[0200] Through the U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 uncoded bits) can be transmitted. The first symbol of the U-SIG can transmit the first X bits of information of the A-bit information (e.g., 26 uncoded bits), and the second symbol of the U-SIG can transmit the remaining Y bits of information of the A-bit information (e.g., 26 uncoded bits). For example, the transmitting STA can obtain the 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52 coded bits, and 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. Except for DC index 0, one U-SIG symbol can be transmitted based on 65 tones (subcarriers) from subcarrier index -28 to subcarrier index +28. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) excluding the pilot tones, ie, tones -21, -7, +7, +21.

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

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

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

[0204] For example, the version-independent bits of the U-SIG may include a 1-bit UL / DL Flag field, wherein a first value of the 1-bit UL / DL Flag field is associated with UL communication, and a second value of the UL / DL Flag field is associated with DL communication.

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

[0206] For example, when the EHT PPDU is divided into various types (for example, various types such as EHT PPDU related to SU mode, EHT PPDU related to MU mode, EHT PPDU related to TB mode, EHT PPDU related to extended range transmission, etc.), information related to the type of the EHT PPDU may be included in the version-related bit of the U-SIG.

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

[0208] Can Figure 18 Preamble puncturing is applied to the PPDU. Preamble puncturing implies that puncturing is applied to a portion of the full band (e.g., the secondary 20 MHz band). For example, when transmitting an 80 MHz PPDU, the STA may apply puncturing to the secondary 20 MHz band within the 80 MHz band and may transmit the PPDU only over the primary 20 MHz band and the secondary 40 MHz band.

[0209] For example, the pattern of the preamble puncture can be preconfigured. For example, when the first puncture pattern is applied, puncture can be applied only to the auxiliary 20 MHz band within the 80 MHz band. For example, when the second puncture pattern is applied, puncture can be applied only to any one of the two auxiliary 20 MHz bands in the auxiliary 40 MHz band included in the 80 MHz band. For example, when the third puncture pattern is applied, puncture can be applied only to the auxiliary 20 MHz band in the main 80 MHz band included in the 160 MHz band (or 80+80 MHz band). For example, when the fourth puncture pattern is applied, puncture can be applied to at least one 20 MHz channel that does not belong to the main 40 MHz band in the 80 MHz band included in the 160 MHz band (or 80+80 MHz band) when the main 40 MHz band exists.

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

[0211] For example, based on the following method, the U-SIG and the EHT-SIG may include information related to the preamble puncture. When the bandwidth of the PPDU exceeds 80 MHz, the U-SIG can be configured separately in units of 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG may include information related to the 160 MHz bandwidth, and the second field of the first U-SIG may include information related to the preamble puncture applied to the first 80 MHz band (i.e., information related to the preamble puncture pattern). In addition, the first field of the second U-SIG may include information related to the 160 MHz bandwidth, and the second field of the second U-SIG may include information related to the preamble puncture applied to the second 80 MHz band (i.e., information related to the preamble puncture pattern). At the same time, the EHT-SIG continuous with the first U-SIG may 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 with the second U-SIG may include information related to the preamble puncturing applied to the first 80 MHz band (i.e., information related to the preamble puncturing pattern).

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

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

[0214] Figure 18 The EHT-SIG in the U-SIG may include control information for receiving STAs. The EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 μs. Information related to the number of symbols used for the EHT-SIG may be included in the U-SIG.

[0215] The EHT-SIG may include reference Figure 8 and Figure 9For example, the EHT-SIG may include the following: Figure 8 The common field and the user-specific field in the example of . The common field of EHT-SIG can be omitted, and the number of user-specific fields can be determined based on the number of users.

[0216] As in Figure 8 In the example of , the common field of EHT-SIG and the user-specific field of EHT-SIG can be encoded separately. One user block field included in the user-specific field can include information for two users, but the last user block field included in the user-specific field can include information for one user. That is, one user block field of EHT-SIG can include a maximum of two user fields. Figure 9 In the example of , each user field may be associated with a MU-MIMO allocation or may be associated with a non-MU-MIMO allocation.

[0217] As in Figure 8 In the example of , the common field of the EHT-SIG may include a CRC bit and a tail bit. The length of the CRC bit may be determined to be 4 bits. The length of the tail bit may be determined to be 6 bits and may be set to "000000".

[0218] As in Figure 8 In the example of , the common field of the EHT-SIG may include RU allocation information. The RU allocation information may indicate information related to the positions of the RUs to which multiple users (i.e., multiple receiving STAs) are allocated. The RU allocation information may be configured in units of 8 bits (or N bits), as shown in Table 1.

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

[0220] The examples of Tables 5 to 7 relate to information related to the location of RUs allocated to the 20 MHz band. For example, "index 0" of Table 5 may be in the case of individually allocating nine 26-RUs (e.g., Figure 5 Nine 26-RU cases shown in the figure were used.

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

[0222] [Table 5]

[0223]

[0224] [Table 6]

[0225]

[0226] [Table 7]

[0227]

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

[0229] 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 the DCM scheme. For example, among the N data tones (e.g., 52 data tones) allocated for the EHT-SIG, a first modulation scheme can be applied to 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 use the first modulation scheme to modulate specific control information using the first symbol and allocate it to half of the continuous tones, and can use the second modulation scheme to modulate the same control information using the second symbol and allocate it to the remaining half of the continuous tones. As described above, information (e.g., a 1-bit field) about whether the DCM scheme is applied to the EHT-SIG can be included in the U-SIG.

[0230] Figure 18 The HE-STF can be used to improve automatic gain control estimation in a multiple-input multiple-output (MIMO) environment or an OFDMA environment. Figure 18 The HE-LTF can be used to estimate the channel in a MIMO environment or an OFDMA environment.

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

[0232] The EHT-STF may be configured based on the following sequence M.

[0233] <Formula 1>

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

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

[0236] <Formula 2>

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

[0238] EHT-STF(0)=0

[0239] The EHT-STF for a 40 MHz PPDU may be configured based on the following equation: The following example may be a first type (ie, 1x STF) sequence.

[0240] <Formula 3>

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

[0242] The EHT-STF for 80 MHz PPDU may be configured based on the following equation: The following example may be a first type (ie, 1x STF) sequence.

[0243] <Formula 4>

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

[0245] The EHT-STF for 160 MHz PPDU may be configured based on the following equation: The following example may be a first type (ie, 1x STF) sequence.

[0246] <Formula 5>

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

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

[0249] <Formula 6>

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

[0251] The following Equations 7 to 11 are related to an example of the second type (ie, 2x STF) sequence.

[0252] <Formula 7>

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

[0254] The EHT-STF for 40 MHz PPDU may be configured based on the following formula.

[0255] <Formula 8>

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

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

[0258] EHT-STF(248)=0

[0259] The EHT-STF for 80 MHz PPDU may be configured based on the following formula.

[0260] <Formula 9>

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

[0262] The EHT-STF for 160 MHz PPDU may be configured based on the following equation.

[0263] <Formula 10>

[0264] 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)

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

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

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

[0268] <Formula 11>

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

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

[0271] EHT-STF(504)=0

[0272] 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, GIs of various lengths (e.g., 0.8 / 1 / 6 / 3.2 μs) can be applied to the first / second / third type LTF.

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

[0274] Can be based on Figure 5 and Figure 6 Example to configure Figure 18 PPDU (e.g., EHT-PPDU).

[0275] For example, based on Figure 5 The RU of the UE is configured to send an EHT PPDU on the 20MHz band, i.e., a 20MHz EHT PPDU. Figure 5 The positions of RUs that determine the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU are shown in FIG.

[0276] Can be based on Figure 6 The RU of the 40MHz band is configured to send an EHT PPDU, i.e., a 40MHz EHT PPDU. Figure 6 The positions of RUs that determine the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU are shown in FIG.

[0277] because Figure 6 The RU position corresponds to 40MHz, so it can be Figure 6 The tone plan for 80MHz is determined when the pattern of Figure 7 RU but Figure 6 The RU repeats the new tone twice and plans to send an 80MHz EHTP PDU.

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

[0279] Can Figure 6 The pattern is repeated several times in such a way that the tone plans for 160 / 240 / 320MHz are configured.

[0280] The following method can be used to Figure 18 The PPDU is determined (or identified) as an EHT PPDU.

[0281] The receiving STA may determine the type of the RX PPDU as an EHT PPDU based on the following aspects. 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 in which the L-SIG of the RX PPDU is repeated is detected; and 3) when it is detected that the result of applying "modulo 3" to the value of the length field of the L-SIG of the RX PPDU is "0", the RX PPDU may be determined to be an EHT PPDU. When the RX PPDU is determined to be an EHT PPDU, the receiving STA may determine the type of the RX PPDU as an EHT PPDU based on Figure 18 The type of the EHT PPDU (e.g., SU / MU / triggered-based / extended range type) can be detected based on the bit information included in the symbol following the RL-SIG of the RX PPDU. In other words, the receiving STA can determine that the RX PPDU is an EHT PPDU based on the following: 1) the first symbol after the L-LTF signal, which is a BPSK symbol; 2) the RL-SIG that is consecutive to and identical to the L-SIG field; 3) the L-SIG including the length field, in which the result of applying "modulo 3" is set to "0"; and 4) the 3-bit PHY version identifier of the aforementioned U-SIG (e.g., a PHY version identifier having a first value).

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

[0283] For example, the receiving STA may determine the type of the RX PPDU as non-HT, HT, or VHT PPDU based on the following factors. 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 may be determined as non-HT, HT, or VHT PPDU. Furthermore, even if the receiving STA detects repeated RL-SIGs, if the result of applying "modulo 3" to the length value of the L-SIG is "0," the RX PPDU may be determined as non-HT, HT, or VHT PPDU.

[0284] In the following examples, signals represented as (TX / RX / UL / DL) signals, (TX / RX / UL / DL) frames, (TX / RX / UL / DL) packets, (TX / RX / UL / DL) data units, (TX / RX / UL / DL) data, etc. may be based on Figure 18 PPDU transmission / reception signal. Figure 18 The PPDU can be used to send / receive various types of frames. For example, Figure 18 The PPDU can be used for control frames. Examples of control frames may include Request to Send (RTS), Clear to Send (CTS), Power Save Poll (PS-poll), BlockACKReq, BlockAck, Null Data Packet (NDP) notifications, and trigger frames. For example, Figure 18 The PPDU can be used for management frames. Examples of management frames may include beacon frames, (re)association request frames, (re)association response frames, probe request frames, and probe response frames. For example, Figure 18 The PPDU can be used for data frames. For example, Figure 18 The PPDU may be used to simultaneously transmit at least two or more of a control frame, a management frame, and a data frame.

[0285] Figure 19 Illustrated are examples of modified transmitting devices and / or receiving devices of the present specification.

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

[0287] Figure 19 The processor 610 can be used with Figure 1 The processors 111 and 121 are the same. Alternatively, Figure 19 The processor 610 can be used with Figure 1 The processing chips 114 and 124 are the same.

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

[0289] Reference Figure 19 , power management module 611 manages power for processor 610 and / or transceiver 630. Battery 612 supplies power to power management module 611. Display 613 outputs results processed by processor 610. Keypad 614 receives input to be used by processor 610. Keypad 614 may be displayed on display 613. SIM card 615 may be an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and its associated keys, which are used to identify and authenticate users on mobile phone devices (e.g., mobile phones and computers).

[0290] Reference Figure 19 , the speaker 640 may output a result related to the sound processed by the processor 610. The microphone 641 may receive an input related to the sound to be used by the processor 610.

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

[0292] For example, in IEEE 802.11n systems, 40 MHz channel bonding can be performed by combining two 20 MHz channels. In addition, 40 / 80 / 160 MHz channel bonding can be performed in IEEE 802.11ac systems.

[0293] For example, a 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 during the channel bonding process. The backoff count value can be selected as a random value and decremented during the backoff interval. Generally speaking, when the backoff count value reaches 0, the STA may attempt to access the channel.

[0294] During the backoff interval, when the P20 channel is determined to be idle and the backoff count value of the P20 channel reaches 0, the STA performing channel bonding determines whether the S20 channel remains idle for a certain period of time (e.g., the Point Coordination Function Interframe Space (PIFS)). If the S20 channel is idle, the STA can bond the P20 and S20 channels. That is, the STA can transmit a signal (PPDU) over a 40 MHz channel (i.e., a 40 MHz bonded channel) that includes the P20 and S20 channels.

[0295] Figure 20 An example of channel bonding is shown. Figure 20 As shown in , the primary 20 MHz channel and the secondary 20 MHz channel can be combined into 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.

[0296] Channel bundling can be performed when the channels adjacent to the primary channel are in an idle state. That is, the primary 20 MHz channel, the secondary 20 MHz channel, the secondary 40 MHz channel, and the secondary 80 MHz channel can be bundled sequentially. However, if it is determined that the secondary 20 MHz channel is in a busy state, channel bundling cannot 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 bundling can be performed only on the primary 20 MHz channel and the secondary 20 MHz channel.

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

[0298] For example, in Figure 20In the example of , if the primary 20 MHz channel, the secondary 40 MHz channel, and the secondary 80 MHz channel are all in an idle state, but the secondary 20 MHz channel is in a busy state, bundling to the secondary 40 MHz channel and the secondary 80 MHz channel may not be possible. In this case, the STA can configure a 160 MHz PPDU and can perform preamble puncturing on the preamble sent 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 send a signal through the channel in the idle state. In other words, the STA can perform preamble puncturing on some frequency bands of the PPDU. Information about preamble puncturing (e.g., information about the 20 / 40 / 80 MHz channels / bands to which puncturing is applied) can be included in the signal field (e.g., HE-SIG-A, U-SIG, EHT-SIG) of the PPDU.

[0299] Hereinafter, technical features of multi-link (ML) supported by the STA of the present disclosure will be described.

[0300] The STA (AP and / or non-AP STA) of the present disclosure may support multi-link (ML) communication. ML communication may refer to communication that supports multiple links. Links related to ML communication may include Figure 15 The channels of the 2.4GHz band shown in Figure 16 The 5 GHz band shown in Figure 17 6 GHz frequency band (e.g., 20 / 40 / 80 / 160 / 240 / 320 MHz channels) shown in .

[0301] Multiple links for ML communication can be configured in various ways. For example, the multiple links supported by a STA for ML communication may include 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 supported by a STA for ML communication may include 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). Furthermore, at least one of the multiple links supported by a STA for ML communication may be a channel to which preamble puncturing is applied.

[0302] The STA may perform ML settings to perform ML communication. ML settings may be performed based on management frames or control frames such as beacons, probe requests / responses, association requests / responses, etc. For example, information about ML settings may be included in element fields included in beacons, probe requests / responses, association requests / responses, etc.

[0303] When ML setup is complete, an enabled link for ML communication may be determined. The STA may perform frame exchange via at least one of the multiple links determined as enabled links. For example, the enabled link may be used for at least one of management frames, control frames, and data frames.

[0304] When a STA supports multiple links, the transceiver supporting each link can operate as a single logical STA. For example, a STA supporting two links can be represented as a multi-link device (MLD), which includes a first STA for the first link and a second STA for the second link. For example, an AP supporting two links can be represented as an APMLD, which includes a first AP for the first link and a second AP for the second link. In addition, a non-AP supporting two links can be represented as a non-AP MLD, which includes a first STA for the first link and a second STA for the second link.

[0305] In the following, more specific features related to the ML setting will be described.

[0306] MLD (AP MLD and / or non-AP MLD) can send information on the links that the corresponding MLD can support through ML settings. Link information can be configured in various ways. For example, information about the link may include at least one of the following: 1) information about whether the MLD (or STA) supports simultaneous RX / TX operation, 2) information about the number / upper limit of uplink / downlink links supported by the MLD (or STA), 3) information about the location / frequency band / resource of the uplink / downlink links supported by the MLD (or STA), 4) information about the frame type (management, control, data, etc.) available or preferred in at least one uplink / downlink link, 5) information about the ACK policy available or preferred in at least one uplink / downlink link, and 6) information about the traffic identifier (TID) available or preferred in at least one uplink / downlink link. The TID is related to the priority of the 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 may be defined.

[0307] For example, it may be preset that all TIDs are mapped for uplink / downlink communication. Specifically, if all TIDs are used for ML communication, and if the mapping between uplink / downlink communication and TIDs is negotiated through additional ML settings, the negotiated TIDs may be used for ML communication.

[0308] Through ML settings, multiple links available for transmitting and receiving MLDs related to ML communication can be set, and these can be referred to as "enabled links." "Enabled links" can be referred to in various ways. For example, they can be referred to as various expressions such as first link, second link, transmission link, and reception link.

[0309] After the ML setup is complete, the MLD can update the ML setup. For example, when it is necessary to update information about a link, the MLD can send information about the new link. The information about the new link can be sent based on at least one of a management frame, a control frame, and a data frame.

[0310] In Extreme High Throughput (EHT), a standard being discussed after IEEE 802.11ax, the introduction of HARQ is being considered. The introduction of HARQ can extend coverage in low signal-to-noise ratio (SNR) environments, i.e., environments with long distances between the transmitter and receiver, and achieve higher throughput in high SNR environments.

[0311] The equipment described below can be Figure 1 and / or Figure 19 device, and the PPDU described below may be Figure 18 PPDU. The device can be an AP or a non-AP STA. The device described below can be an AP Multi-Link Device (MLD) that supports multi-link or a non-AP STA MLD.

[0312] In Extreme High Throughput (EHT), 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. Figure 21 As shown in , multi-link transmission can be classified into two types.

[0313] In the following, although the description is made 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 may be used in this specification, for the convenience of the following description, the following embodiments may be described based on multi-link.

[0314] In the following description, MLD refers to a multi-link device. An MLD has one or more attached STAs and a MAC service access point (SAP) that connects to a higher link layer (Logical Link Control, LLC). MLD can refer to a physical device or a logical device. Hereinafter, a device can refer to an MLD.

[0315] In the following description, a transmitting device and a receiving device may be referred to as an MLD. A first link of a transmitting / receiving device may be a terminal (e.g., a STA or AP) that transmits / receives signals via the first link included in the transmitting / receiving device. A second link of a transmitting / receiving device may be a terminal (e.g., a STA or AP) that transmits / receives signals via the second link included in the transmitting / receiving device.

[0316] IEEE 802.11be can support two types of multilink operations. For example, simultaneous transmit and receive (STR) and non-STR operations can be considered. For example, STR can be referred to as asynchronous multilink operation, while non-STR can be referred to as synchronous multilink operation. Multilink can include multiple frequency bands. In other words, multilink can refer to links included in multiple frequency bands, or it can refer to multiple links included in one frequency band.

[0317] EHT (11be) considers multi-link technology, where multi-link can include multiple frequency bands. That is, multi-link can represent links of several frequency bands, and can also represent several multi-links within one frequency band. Two types of multi-link operations can be considered. Consider asynchronous operation with simultaneous TX / RX enabled on multiple links and synchronous operation without simultaneous TX / RX enabled. Hereinafter, the ability to simultaneously receive and transmit in multiple links may be referred to as STR (simultaneous transmit and receive), an STA with STR capability may be referred to as an STR multi-link device (MLD), and an STA without STR capability may be referred to as a non-STRMLD.

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

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

[0320] The terms (names) in this specification may vary, and STA may include an AP STA or a non-AP STA.

[0321] The multi-link operation for the overall active links may vary depending on the STR capabilities of the linkset selected by the AP / STA MLD.

[0322] Figure 22 is a diagram illustrating an embodiment of the STR capability of multiple links.

[0323] refer to Figure 22, Link 1 and Link 2 of the STA MLD on the left have a non-STR relationship, that is, a link set that cannot perform transmission and reception on multiple links simultaneously, 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 may have to operate as non-STR due to Link 2.

[0324] Figure 22 In the right STA MLD, links 1 and 2 have a non-STR relationship, and links 3 and 4 also have a non-STR relationship. However, since links 2 and 3 are in a STR relationship, non-STR can be considered in links 1 / 2 and links 3 / 4, respectively.

[0325] An MLD may have a set of links that have non-STR relationships, which are referred to as non-STR linksets in this specification. The basic process (A) is as follows.

[0326] 1) AP MLD provides link information to STA MLD.

[0327] 2) STA MLD requests link operation.

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

[0329] Here, STA MLD does not necessarily need to request a link to operate, which includes the link currently performing the current negotiation. That is, it can flexibly request a link based on capabilities. This situation will be handled later in this specification.

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

[0331] Methods for requesting / responding to LinkSet and / or STR capabilities in steps 2) and 3)

[0332] If the order is determined as 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 for each link.

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

[0334] Figure 23 is a diagram illustrating an embodiment of link information.

[0335] refer to Figure 23 , the link information can be expressed using 3 bits. For example, if the STA requests link 2 and link 3, the link information can indicate "011".

[0336] Figure 24 is a diagram illustrating an embodiment of link information.

[0337] refer to Figure 24 , if the order is determined, it is possible to indicate in sequence whether each link set is in the STR based on the form of a bitmap, such as [link 1, link 2], [link 1, link 3]... Next, the requested or selected link set can be indicated in the form of a bitmap.

[0338] Ex) 1 bit indicates whether all link sets consisting of N links are in the STR: 1 bit can be used to indicate 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, whether each link set is in the STR can be indicated by 1 bit of information. If it is in the STR, the value of the 1 bit of information is 1, and if it is not in the STR, its value is 0.

[0339] Ex) Link Request / Select '1': Select / request link, Link Request / Select '0': Do not select / request link

[0340] For example, in Figure 23 and Figure 24 In the example, if link 2 and link 3 are in a non-STA, whether they are in the STR can be indicated by a 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, and the third bit indicates whether the link set of [link 2, link 3] is in the STR. Therefore, the value of "110" can include information that only the third link set of [link 2, link 3] is in a non-STR), and if the STA requests link 2 and link 3, it can be expressed as "011". Therefore, the total indication bitmap may be "110011".

[0341] In addition, in another method, it is possible to indicate whether a link set is requested or selected and whether each link set is in the STR. The same number of bits as in the above method can be used, and "101001" can be configured to indicate the same example. That is, the last 2 bits "01" indicate a 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.

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

[0343] refer to Figure 25 , the AP MLD has four links, and link information can be announced through beacon frames or probe response frames. Link information may include information related to AP / link capabilities, channel information, and non-STR link sets. For example, links 1 and 2, as well as links 3 and 4, may each be a non-STR link set. The non-AP MLD has three 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, and 4 as links to operate on link 4, and the AP MLD responds, enabling the non-AP MLD to 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 may not be requested.

[0344] In the above process (A), when three link pairs are configured as {STA 1 <-> AP 4}, {STA 2 <-> AP 3}, and {STA 3 <-> AP 2} in a multi-link setup, STA 2 and STA 3 may not have yet performed an initial frame exchange with the APs. In this case, a method is needed to enable STA 2 and STA 3 to perform frame exchanges with AP 2 and AP 3, respectively, on the corresponding links. This method includes, but is not limited to, the following features.

[0345] That is, a method of allowing a STA that is set to perform a multi-link operation but does not directly perform link setup to start transmitting and receiving signals can be classified into a method in the multi-link setup step and a method after the multi-link setup. Among the links to be set, the link through which the association request / response frame is transmitted can be called an associated link, and the other setup links can be called non-associated links. For example, if the setup link is Figure 25 If there are links 2, 3, and 4 in the STA, link 4 becomes an associated link, and links 2 and 3 become non-associated links. However, this is just a term, and the STA and AP of the non-associated link may be in a state where association has already been performed.

[0346] 1) Methods in the multi-link setup steps

[0347] 2) MAC Address Signaling: A STA (i.e., an associated link STA) sending a management frame (e.g., probe request / response frames, beacon frames, association request / response frames) can send the MAC address of another STA (i.e., an unassociated link STA) belonging to the same MLD to which the STA belongs. This MAC address is recognized by the STA to enable frame exchange in the unassociated link. The method of including the MAC address may be as follows, but is not limited thereto.

[0348] A. New element or field definition : It is possible to define new elements or fields to be included in the management frame. Basically, the MLD per-STA MAC address field can be defined as follows.

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

[0350] refer to Figure 26 Because a link ID that can distinguish each AP can exist, AP MLD can indicate the MAC addresses of STAs (i.e., APs) operating in non-associated links in the order of their link IDs. If a STA ID that can distinguish each STA can be defined, non-AP MLD can also indicate MAC addresses in the order of their STA IDs. In addition, the link ID or STA ID can be included in front of each MAC address for clear indication.

[0351] For example, a STA that sends a management frame may not indicate the MAC addresses of all STAs that belong to the same MLD as the STA. Figure 25 , STA 1 may not send the MAC address of STA 2. In this case, the number of STAs (or the number of links (in the case of AP)) may be additionally indicated.

[0352] Because if it is not MLD, the corresponding field may not be included, so the replacement field, Figure 26 The MLD address field presented in the element can be included in the element.

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

[0354] B. Included in multi-link elements : The MAC address of a STA operating in a non-associated link may be included in the common information or per-STA information field of the ML IE (Information Element).

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

[0356] The order, names, and sizes of the fields of the multilink element format may vary, and additional fields may be present. Figure 28 , common information may include information common to STAs in MLD, and specific information about each STA may be included in a per-STA profile.

[0357] Figure 29 is a diagram illustrating an embodiment of an ML IE.

[0358] refer to Figure 29 , Figure 26 The MLD per-STA MAC address field can be included in the public information, such as Figure 29 If the MAC address field is present in the common information and the MAC address should always be included in the ML IE, then a per-STA profile may not be needed. However, because each MAC address is different for each STA, a per-STA profile may be semantically appropriate.

[0359] Figure 30 is a diagram illustrating an embodiment of an ML IE.

[0360] refer to Figure 30 , the MAC address field may be included in the link information field. The per-STA information may include a MAC address field or element for each STA.

[0361] 2) Method after multi-link setting

[0362] 2-1) Initial frame transmission in non-associated links

[0363] To trigger a frame exchange, an initial frame can be sent on an unassociated link. When a transmitter sends an 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 gains channel access on an unassociated link can send a frame. For example, a STA that receives an initial frame can determine the MAC address of the corresponding transmitter STA through the TA (transmitter address) in the initial frame.

[0364] The initial request frame may be defined as a new frame, but an existing QoS data frame, QoS null frame, etc. may be used. The frame transmitted as the initial request frame may include information related to the transmitter MLD and / or information related to the receiver MLD to facilitate notification that operation on the corresponding link is possible after multi-link setup.

[0365] Figure 31 is a diagram illustrating an embodiment of a method for transmitting an initial frame in a non-associated link.

[0366] A. Address setting: MLD MAC address can be set in the initial frame.

[0367] A-1) The receiver's MLD MAC address is set in the Receiver Address (RA) field: During the multi-link setup process, the MLD MAC address of each other can be known by including the ML IE in the Association Request / Response frame. Therefore, by including the MLD's MLD MAC address in the RA, it can be notified that operation is possible on the current link. In addition, to notify that it is the MLD that has performed multi-link setup, the Source Address (SA) can include the MLD MAC address of the transmitter MLD.

[0368] Figure 32 It is a diagram showing an embodiment of A-1.

[0369] refer to Figure 32 , when STA 2 sends an initial request frame in link 3, TA may be set to the MAC address of STA 2, RA may be set to the AP MLD MAC address, and SA may be set to the MAC address of the non-AP MLD.

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

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

[0372] Figure 33 It is a diagram showing an embodiment of Figure A-3.

[0373] refer to Figure 33 , when STA 2 sends an initial request frame in link 3, TA may be set to the MAC address of STA 2, RA may be set to the broadcast address, SA may be set to the MAC address of the non-AP MLD, and DA may be set to the APMLD MAC address.

[0374] A-4) The MLD MAC address of the transmitter MLD and / or the receiver MLD may be included in a control field (eg, an A control field of a QoS null / data frame) in a MAC frame body or a MAC header included in the initial frame.

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

[0376] B-1) The MLD MAC addresses of the transmitter and receiver set in the address fields presented in A-1), A-2), A-3), and A-4) can be replaced with MLD IDs that can distinguish the MLDs. For example, when replacing in method A-4), the MLD IDs of the transmitter MLD and / or receiver MLD can be included in the MAC frame body included in the initial frame or in the control field in the MAC header (e.g., the A control field of the QoS null / data frame). When the MLD ID is included in the address field, the number of remaining bits may increase because the field size is much smaller than the MLD MAC address.

[0377] Figure 34 It is a diagram illustrating an embodiment of the A-4 method and the B-1 method.

[0378] refer to Figure 34 , when STA 2 sends an initial request frame in link 3, the A control field of the initial request frame may include the ID of the non-AP MLD of STA 2 as a transmitter, and include the ID of the AP MLD of AP 4 as a receiver.

[0379] 2-2) Definition of additional rules: A non-AP STA may not transmit a frame until a beacon is received in a 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 other APs can be known during the multi-link setup process. For example, in Figure 34 In the example, STA 2 and STA 3 may not send frames until they receive beacons from AP 3 and AP 2, respectively.

[0380] Upon receiving the link information, the STA MLD may send a request (or initiate) frame in each link, such as an association. That is, the STA MLD may exchange additional frames in each link it wishes to operate.

[0381] Figure 35 is a diagram illustrating an embodiment of a multi-link setting method.

[0382] refer to Figure 35 , after receiving the information of links 1 to 4, the STA MLD can request the settings of links 2, 3, and 4, which are the links to be operated, and the AP MLD can respond. A setup request / response can be sent for each link.

[0383] For example, although a certain linkset is a STR possible linkset for an AP MLD, it may be a non-STR linkset for a STAMLD. Therefore, a STA MLD may send information related to STR-related capabilities when requesting a link.

[0384] Figure 36 is a diagram illustrating an embodiment of operations related to link capabilities.

[0385] refer to Figure 36 , when using links 3 and 4, AP MLD should operate based on non-STR, and other sets can operate in STR. In addition, STA 1 of STA MLD can discover AP MLD through link 4. Here, which link STA 1 and STA 2 of STA MLD request and whether the link is capable of STR may affect MLD link selection.

[0386] AP MLD can accept the requested link, change the link, or reject it based on the STA MLD's requested link and whether the link is STR-capable. In particular, depending on whether AP MLD is accepted, performance using multiple links may degrade. For example, the AP may accept STA MLDs in non-STR links on links 1 and 2. However, performance may be lower than when all links are STR-based.

[0387] Based on the above scenario, an example of a negotiation process related to the STR capabilities of the AP MLD and STA MLD and the requested link may be as follows.

[0388] When STA When MLD selects links 3 and 4 that are not in STR

[0389] Figure 37 is a diagram illustrating an embodiment of a link negotiation method.

[0390] refer to Figure 37 , STA MLD may request link 3 and link 4, and this link set may be a non-STR set for STA MLD. AP MLD may respond to STA MLD by selecting link 3 and link 4 as is.

[0391] When STA When MLD selects links 3 and 4 in STR

[0392] Figure 38 is a diagram illustrating an embodiment of a link negotiation method.

[0393] refer to Figure 38 STA MLD can request links 3 and 4, and this link set can be a link set that can perform STR for STA MLD. If AP MLD selects links 3 and 4 as is, the performance of STA MLD may be degraded. Therefore, AP MLD can respond to STA MLD by selecting links 2 and 3 as the link set.

[0394] In addition, if the STA MLD does not support link 2 due to a problem such as a frequency band, the AP MLD may select only link 3 and respond thereto.

[0395] When STR When MLD selects links 2 and 3 that are not in STR

[0396] Figure 39 is a diagram illustrating an embodiment of a link negotiation method.

[0397] refer to Figure 39 , STA MLD can request link 2 and link 3, and this link set can be a non-STR set for STA MLD. Therefore, AP MLD can respond to STA MLD by modifying / selecting link 3 and link 4 to prevent performance degradation.

[0398] Figure 40 is a diagram illustrating an embodiment of a receive MLD operation.

[0399] refer to Figure 40 , the receiving MLD may include a first STA and a second STA.

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

[0401] The receiving MLD may receive multilink information (S4010). For example, the first STA may receive multilink information including information related to the first link and the second link from the transmitting MLD. For example, the multilink information may include information related to whether the first link and the second link are a simultaneous transmit and receive (STR) link set or a non-STR link set.

[0402] For example, the MLD transmission includes the third STA and the fourth STA, and the multi-link information may include information that the first STA communicates with the third STA and the second STA communicates with the fourth STA.

[0403] The receiving MLD may send multi-link address information (S4020).For example, the first STA may send multi-link address information to the sending MLD, and the multi-link address information may include a media access control (MAC) address of the second STA.

[0404] For example, the received MLD further includes a third STA operating on a third link, the multi-link information further includes information related to the third link, and the multi-link address information may further include a MAC address of the third STA.

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

[0406] For example, the MAC address of the second STA and the MAC address of the third STA may be included in the multilink address information in the order of STA identifiers (IDs) of the second STA and the third STA.

[0407] For example, a STA (i.e., an associated link STA) sending a management frame (e.g., a probe request / response frame, a beacon frame, or an association request / response frame) can send the MAC address of a STA belonging to the same MLD as the STA (i.e., an unassociated link STA). This MAC address is recognized by the STA to enable frame exchange in the unassociated link. The method of including the MAC address may be as follows, but is not limited thereto.

[0408] A. New element or field definition : It is possible to define new elements or fields to be included in the management frame. Basically, the MLD per-STA MAC address field can be defined as follows.

[0409] For example, since there can be a link ID that can distinguish each AP, AP MLD can indicate the MAC addresses of STAs (i.e., APs) operating in non-associated links in the order of their link IDs. If a STA ID that can distinguish each STA can be defined, non-AP MLD can also indicate MAC addresses in the order of their STA IDs. In addition, the link ID or STA ID can be included in front of each MAC address for clear indication.

[0410] For example, a STA that sends a management frame may not indicate the MAC addresses of all STAs that belong to the same MLD as the STA. Figure 25 , STA 1 may not send the MAC address of STA 2. In this case, the number of STAs (or the number of links (in the case of AP)) may be additionally indicated.

[0411] For example, since the corresponding fields may not be included in the non-MLD case, Figure 26 The MLD address fields presented in MLD_ADDR may be included in an element instead of a field.

[0412] B. Included in multi-link elements : The MAC address of a STA operating in a non-associated link may be included in the common information or per-STA information field of the ML IE (Information Element).

[0413] For example, the order, name, and size of the fields of the format of the multilink element may be changed and may exist as additional fields. Common information may include information common to STAs in MLD, and specific information about each STA may be included in a per-STA profile.

[0414] For example, Figure 26 The MLD per-STA MAC address field can be included as Figure 29 . If the MAC address field is present in the common information and the MAC address should always be included in the ML IE, then a per-STA profile may not be needed. However, because each MAC address is different for each STA, a per-STA profile may be semantically appropriate.

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

[0416] The receiving MLD may send data (S4030). For example, each STA in the receiving MLD in which multiple links are set may send data through its own link.

[0417] Figure 41 is a diagram illustrating an embodiment of a send MLD operation.

[0418] refer to Figure 41 , the receiving MLD may include a first STA and a second STA.

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

[0420] The transmitting MLD may transmit multilink information (S4110). For example, the first STA may transmit multilink information including information related to the first link and the second link to the receiving MLD. For example, the multilink information may include information related to whether the first link and the second link are simultaneous transmit and receive (STR) link sets or non-STR link sets.

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

[0422] The transmitting MLD may receive multi-link address information (S4120). For example, the first STA may receive multi-link address information from the third STA receiving the MLD, where the multi-link address information may include a media access control (MAC) address of the fourth STA receiving the MLD. For example, the receiving MLD may include the third STA and the fourth STA. For example, the third STA may operate on the first link, and the fourth STA may operate on the second link.

[0423] For example, the sending MLD further includes a fifth STA, the fifth STA operates in the third link, the multi-link information further includes information related to the third link, and the multi-link address information further may include a MAC address of the fifth STA.

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

[0425] For example, the MAC address of the fourth STA and the MAC address of the fifth STA may be included in the multilink address information in the order of STA identifiers (IDs) of the second STA and the third STA.

[0426] For example, a STA (i.e., an associated link STA) sending a management frame (e.g., probe request / response frame, beacon frame, association request / response frame) can send the MAC address of a STA (i.e., an unassociated link STA) belonging to the same MLD as the STA. This MAC address is recognized by the STA to enable frame exchange in the unassociated link. The method of including the MAC address may be as follows, but is not limited thereto.

[0427] A. New element or field definition : It is possible to define new elements or fields included in the management frame. Basically, the MLD per-STA MAC address field can be defined as follows.

[0428] For example, since there can be a link ID that can distinguish each AP, AP MLD can indicate the MAC addresses of STAs (i.e., APs) operating in non-associated links in the order of their link IDs. If a STA ID that can distinguish each STA can be defined, non-AP MLD can also indicate MAC addresses in the order of their STA IDs. In addition, the link ID or STA ID can be included in front of each MAC address for clear indication.

[0429] For example, a STA that sends a management frame may not indicate the MAC addresses of all STAs that belong to the same MLD as the STA. Figure 25, STA 1 may not send the MAC address of STA 2. In this case, the number of STAs (or the number of links (in the case of AP)) may be additionally indicated.

[0430] For example, since the corresponding fields may not be included in the non-MLD case, Figure 26 The MLD address fields presented in MLD_ADDR may be included in an element instead of a field.

[0431] B. Included in multi-link elements : The MAC address of a STA operating in a non-associated link may be included in the common information or per-STA information field of the ML IE (Information Element).

[0432] For example, the order, name, and size of the fields of the format of the multilink element may be changed and may exist as additional fields. Common information may include information common to STAs in MLD, and specific information about each STA may be included in a per-STA profile.

[0433] For example, Figure 26 The MLD per-STA MAC address field can be included in the public information, such as Figure 29 If the MAC address field is present in the common information and the MAC address should always be included in the ML IE, then a per-STA profile may not be needed. However, because each MAC address is different for each STA, a per-STA profile may be semantically appropriate.

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

[0435] The transmitting MLD may receive data (S4130). For example, each STA in which the transmitting MLD is configured with multiple links may receive data through its own link.

[0436] Figure 40 and Figure 41 Some of the detailed steps shown in the examples may not be necessary and can be omitted. Figure 40 and Figure 41 In addition to the steps shown in FIG, other steps may be added, and the order of the steps may be changed. Some of the steps described above may have their own technical significance.

[0437] The technical features of the present specification can be applied to various devices and methods. Figure 1 Device and / or Figure 19 For example, the above technical features of this specification can only be applied to Figure 1 and / or Figure 19 For example, the technical features of the above-mentioned specification are based on Figure 1 The processing chip 114 and / or 124 is implemented, or based on Figure 1 The processor 111 and / or 121 and the memory 112 and / or 122 can be implemented, or can be based on Figure 19 The processor 610 and the memory 620 are implemented as follows. For example, a receiving multi-link device (MLD) in a wireless local area network (WLAN) system includes: wherein the receiving MLD includes 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 includes: a memory; and a processor operably coupled to the memory, wherein the processor is configured to: receive multi-link information including information related to the first link and the second link from the transmitting MLD via the first STA; and send multi-link address information to the transmitting MLD via the first STA, wherein the multi-link address information includes a media access control (MAC) address of the second STA.

[0438] The technical features of this specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed in this specification can store instructions that are executed by at least one processor of a receiving multi-link device (MLD) in a wireless local area network system to perform the following operations: 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 receives multi-link information including information related to the first link and the second link from the transmitting MLD; and the first STA sends multi-link address information to the transmitting MLD, wherein the multi-link address information includes the media access control (MAC) address of the second STA.

[0439] The instructions stored in the CRM of this specification can be executed by at least one processor. The at least one processor associated with the CRM of this specification can be Figure 1 Processor 111 and / or 121 or processing chip 114 and / or 124, or Figure 19 The processor 610 of this specification can be Figure 1 Memory 112 and / or 122, Figure 19 memory 620, or a separate external memory / storage medium / disk.

[0440] The above technical features of this specification are applicable to various applications or business models. For example, the above technical features can be applied to wireless communications of devices that support artificial intelligence (AI).

[0441] Artificial intelligence refers to the field of study concerning artificial intelligence or methods for creating it, while machine learning refers to the field of study concerning methods for defining and solving various problems within the field of artificial intelligence. Machine learning is also defined as algorithms that improve operational performance through consistent operational experience.

[0442] An artificial neural network (ANN) is a model used in machine learning and can refer to an overall problem-solving model that includes artificial neurons (nodes) that form a network by combining synapses. An artificial neural network can be defined by the connection pattern between neurons in different layers, the learning process that updates the model parameters, and the activation function that generates the output value.

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

[0444] Model parameters are those determined by learning and include the weights of synaptic connections and the biases of neurons. Hyperparameters are those set in a machine learning algorithm before learning and include the learning rate, number of iterations, mini-batch size, and initialization function.

[0445] Learning an artificial neural network can be aimed at determining model parameters for minimizing a loss function. The loss function can be used as an index for determining the optimized model parameters during the learning of the artificial neural network.

[0446] Machine learning can be categorized into supervised learning, unsupervised learning, and reinforcement learning.

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

[0448] Machine learning implemented using a deep neural network (DNN) including multiple hidden layers in an artificial neural network is called deep learning, and deep learning is a part of machine learning. Hereinafter, machine learning is explained as including deep learning.

[0449] The above technical features can be applied to wireless communication of robots.

[0450] A robot can refer to a machine that automatically processes or operates a given task with its own capabilities. Specifically, a robot that has the function of recognizing the environment and autonomously making judgments to perform operations can be called an intelligent robot.

[0451] Robots can be classified into industrial, medical, household, military, etc. according to their use or field. Robots can include actuators or drives, which include motors to perform various physical operations (for example, moving robot joints). In addition, mobile robots can include wheels, brakes, propellers, etc. in the drive to travel on the ground or fly in the air.

[0452] The above technical features can be applied to devices that support extended reality.

[0453] Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphics technology that presents real-world objects and backgrounds solely within CG images. AR technology is a computer graphics technology that presents virtual CG images over images of real objects. MR technology is a computer graphics technology that presents virtual objects that are mixed and combined with the real world.

[0454] 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, while in MR technology, virtual objects and real objects are used as equals.

[0455] XR technology can be applied to head-mounted displays (HMDs), head-up displays (HUDs), mobile phones, tablet PCs, laptop computers, desktop computers, TVs, digital signage, etc. Devices to which XR technology is applied may be referred to as XR devices.

[0456] The claims recited in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to implement a device, and the technical features of the device claims in this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to implement a method.

Claims

1. A method in a wireless local area network (WLAN) system, the method comprising: Receiving, by a first station STA of a receiving multi-link device MLD, an association request frame including multi-link information from a transmitting MLD, wherein the receiving MLD includes the first 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 multi-link information includes information related to the first link and the second link, wherein the multi-link information further includes information related to the first link and the second link being a non-simultaneous transmitting and receiving non-STR link set; as well as The first STA of the receiving MLD sends an association response frame including multi-link address information to the sending MLD, wherein the multi-link address information includes a media access control MAC address of the second STA.

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

3. The method according to claim 2, wherein: The MAC address of the second STA and the MAC address of the third STA are included in the multi-link address information in the order of link identifiers IDs of links in which the second STA and the third STA operate.

4. The method according to claim 2, wherein: The MAC address of the second STA and the MAC address of the third STA are included in the multilink address information in the order of STAIDs of the second STA and the third STA.

5. The method according to claim 1, wherein The sending MLD includes a third STA and a fourth STA, and The multi-link information further includes information about communication between the first STA and the third STA and information about communication between the second STA and the fourth STA.

6. A receiving multi-link device (MLD) in a wireless local area network (WLAN) system, comprising: First stop: STA; and Second STA, wherein the first STA operates on a first link, and the second STA operates on a second link; The first STA is configured as follows: receiving, from the transmitting MLD, an association request frame including multilink information including information related to the first link and the second link, wherein the multilink information further includes information related to the first link and the second link being a non-simultaneous transmitting and receiving non-STR link set; and An association request frame including multi-link address information is sent to the sending MLD, wherein the multi-link address information includes a media access control MAC address of the second STA.

7. A method in a wireless local area network (WLAN) system, the method comprising: An association request frame including multi-link information is sent by a first station STA sending a multi-link device MLD to a third STA receiving the MLD, wherein the sending MLD includes the first 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 multi-link information includes information related to the first link and the second link, and wherein the multi-link information further includes information related to the first link and the second link being a non-simultaneous transmitting and receiving non-STR link set; as well as The first STA that sends the MLD receives an association response frame including multi-link address information from the third STA that receives the MLD, wherein the multi-link address information includes a media access control MAC address of the fourth STA that receives the MLD.

8. A multi-link transmitting device (MLD) in a wireless local area network (WLAN) system, comprising: First stop: STA; and Second STA, The first STA operates on a first link and the second STA operates on a second link; wherein the first STA is configured to: Sending an association request frame including multilink information including information related to the first link and the second link to a third STA receiving the MLD, wherein the multilink information further includes information related to the first link and the second link being a non-STR link set for non-simultaneous transmission and reception; and An association response frame including multi-link address information is received from the third STA receiving the MLD, wherein the multi-link address information includes a media access control (MAC) address of the fourth STA receiving the MLD.

Images