Signaling for multi-link transmissions

Abstract

The invention relates to signaling for multi-link transmission. In a wireless local area network system, a multi-link device (MLD) may transmit a multi-link element including a link number field and a link presence field indicating whether the link number field is present.

Description

[0001] This application is a divisional application of a patent application filed on August 9, 2022, with an international application date of January 8, 2021, and application number 202180013558.1 (PCT / KR2021 / 000273), and with the invention name “Signaling for multi-link transmission”. Technical Field

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

[0003] Wireless local area networks (WLANs) have been improved in various ways. For example, the IEEE 802.11ax standard proposes an improved communication environment using orthogonal frequency division multiple access (OFDMA) and downlink multi-user multiple input multiple output (DL MU MIMO) technologies.

[0004] This specification proposes technical features that can be used in new communication standards. For example, the new communication standard may be the ultra-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

[0005] Technical Solution

[0006] The method performed by a transmitting device in a wireless local area network (WLAN) system according to various embodiments of the present disclosure may include technical features related to a link setting method for multi-link operation. A transmitting multi-link device (MLD) of a wireless local area network (WLAN) system may generate a multi-link element. The multi-link element may include a multi-link control field and a common information field. The multi-link control field may include a first presence field related to the presence / absence of a link quantity field. The common information field may include a link quantity field based on the first presence field. The transmitting MLD may send a multi-link element.

[0007] Technical Effects

[0008] According to the example of this specification, multilink setting and multilink operation can be realized by sending multilink information including information related to other links. In addition, by indicating whether the multilink information is included in the presence field in the multilink element, the technical effect of reducing signaling overhead can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1An example of a transmitting device and / or a receiving device of this specification is shown.

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

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

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

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

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

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

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

[0017] Fig. 9 An example is shown in which multiple user STAs are assigned to the same RU through the MU-MIMO scheme.

[0018] Fig.10 The operation based on UL-MU is shown.

[0019] Fig.11 An example of a trigger frame is shown.

[0020] Fig.12 An example of a common information field of a trigger frame is shown.

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

[0022] Fig.14 Describe the technical features of the UORA scheme.

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

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

[0025] Fig.17 Shows examples of channels used / supported / defined in the 6 GHz band.

[0026] Fig.18An example of PPDU used in this specification is shown.

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

[0028] Fig. 20 A diagram illustrating an example of channel bonding.

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

[0030] Fig. 22 is a diagram illustrating an embodiment of a multi-link setting process.

[0031] Fig.23 is a diagram illustrating an embodiment of a multilink element.

[0032] Fig.24 is a diagram illustrating an embodiment of a method of instructing an operation link set.

[0033] Fig.25 is a diagram illustrating an embodiment of a method for indicating a link set in a single BA protocol.

[0034] Fig.26 is a diagram illustrating an embodiment of a method of indicating STR capability.

[0035] Fig. 27 is a diagram illustrating an embodiment of a multilink element including TID and link-to-link mapping information.

[0036] Fig.28 is a diagram illustrating an embodiment of a multilink element including TID and link-to-link mapping information.

[0037] Fig.29 is a diagram illustrating an embodiment of a presence field of a multilink element.

[0038] Fig.30 is a diagram illustrating an embodiment of a TID to Link Mapping Presence field.

[0039] Fig.31 is a diagram illustrating an embodiment of a TID to Link Mapping Presence field.

[0040] Fig.32 and Fig.33 is a diagram illustrating an embodiment of a Simultaneous Send and Receive (STR) Capability Present field.

[0041] Fig.34 is a diagram illustrating an embodiment of a presence field for transmitting information of STA.

[0042] Fig.35is a diagram illustrating an embodiment of a link quantity presence field.

[0043] Fig.36 and 37 is a diagram illustrating an embodiment of a TID to link mapping and STR capability field according to the number of links.

[0044] Fig.38 is a diagram illustrating an embodiment of a multilink element.

[0045] Fig.39 It is a diagram illustrating an embodiment of the NR element.

[0046] Fig.40 is a diagram illustrating an embodiment of a method of instructing an operation link.

[0047] Fig.41 is a diagram illustrating an embodiment of a method for indicating a link set in a single BA protocol.

[0048] Fig.42 is a diagram illustrating an embodiment of a method of indicating STR capability.

[0049] Fig.43 is a diagram illustrating an embodiment of reduced neighbor elements.

[0050] Fig.44 It is a diagram illustrating an embodiment of TBTT information.

[0051] Fig.45 is a diagram illustrating an embodiment of the format of the TBTT information field.

[0052] Fig.46 and Fig.47 is a diagram illustrating an embodiment of a process of establishing a multi-link setup with an MLD to which an AP that has performed discovery belongs and a reduced neighbor report (RNR).

[0053] Fig.48 is a flow chart illustrating an embodiment of a method of operating a send MLD.

[0054] Fig.49 is a flow chart illustrating an embodiment of a receive MLD method of operation. DETAILED DESCRIPTION

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

[0056] A slash ( / ) or a comma used in this specification 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".

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

[0058] In addition, in the present 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".

[0059] In addition, the brackets used in this specification may mean "for example". Specifically, when indicated as "control information (EHT-signal)", it may mean that "EHT-signal" is proposed as an example of "control information". In other words, the "control information" of 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 (ie, EHT signal)", it may also mean that "EHT signal" is proposed as an example of "control information".

[0060] Technical features described separately in one drawing of the present specification may be implemented separately or simultaneously.

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

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

[0063] Figure 1 An example of a transmitting device and / or a receiving device of this specification is shown.

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

[0065] For example, the STAs 110 and 120 may function as an AP or a non-AP. That is, the STAs 110 and 120 of the present specification may function as an AP and / or a non-AP.

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

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

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

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

[0070] The transceiver 113 of the first STA performs a signal transmission / reception operation. Specifically, it can transmit / receive IEEE802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

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

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

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

[0074] For example, the operation of a device indicated as an AP in the specification described below 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 the relevant signal may be transmitted or received by 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 TX / RX signal of the AP 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 the relevant signal may be transmitted or received by 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 TX / RX signal of the AP may be stored in the memory 122 of the second STA 120.

[0075] For example, in the specification described below, the operation of the 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 the relevant signal may be transmitted or received by the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, the 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 the relevant signal may be transmitted or received by the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, the 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.

[0076] In the specification described below, 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, a device indicated as (transmitting / receiving) STA, a first STA, a second STA, STA1, STA2, AP, a first AP, a second AP, AP1, AP2, a (transmitting / receiving) terminal, a (transmitting / receiving) device, a (transmitting / receiving) apparatus, a network, etc. (but without a specific number) may refer to Figure 1 For example, in the following example, the operation of various STAs sending / receiving signals (eg, PPDU) may be performed in Figure 1 In addition, in the following examples, various STAs generate TX / RX signals or perform data processing and calculations in advance for TX / RX signals. Figure 1111 and 121 of the processors. For example, examples of operations for generating TX / RX signals or performing data processing and calculation in advance may include: 1) operations for determining / obtaining / configuring / calculating / decoding / encoding bit information of subfields (SIG, STF, LTF, data) included in the PPDU; 2) operations for determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) for subfields (SIG, STF, LTF, data) included in the PPDU; 3) operations for determining / configuring / obtaining specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for 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, etc. 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 the memories 112 and 122.

[0077] 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 the present specification.

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

[0079] 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, repeater, receiving unit, sending unit, receiving STA, sending STA, receiving device, sending device, receiving apparatus and / or sending apparatus described below may mean Figure 1 STAs 110 and 120 shown in sub-figures (a) / (b) of 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-figure (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 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 illustrated in the sub-figures (a) / (b) of FIG. 1 transmits the Figure 1 The technical features of the control signals generated in the processors 111 and 121 illustrated in the sub-figures (a) / (b) of FIG. Alternatively, the technical features of the sending STA sending the control signal can be understood as Figure 1 The technical features of the processing chips 114 and 124 shown in the sub-figure (b) of FIG. 110 and 111 show the control signals to be transmitted to the transceivers 113 and 123 .

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

[0081] Reference Figure 1 As shown in sub-figure (b), software codes 115 and 125 may be included in memories 112 and 122. Software codes 115 and 126 may include instructions for controlling operations of processors 111 and 121. Software codes 115 and 125 may be included as various programming languages.

[0082] Figure 1 The processors 111 and 121 or the processing chips 114 and 124 may include an application specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. The processor may be an application processor (AP). For example, 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). Figure 1 The processors 111 and 121 or the processing chips 114 and 124 may be composed of The SNAPDRAGONTM processor series manufactured by EXYNOSTM processor series manufactured by Processor family manufactured by The HELIOTM processor series manufactured by The ATOMTM processor family manufactured by or enhanced from these processors.

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

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

[0085] Figure 2 The upper part of shows the structure of an infrastructure basic service set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11.

[0086] 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 are successfully synchronized to communicate with each other, are not concepts indicating a specific area. BSS 205 may include one or more STAs 205-1 and 205-2 that may join one AP 230.

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

[0088] The distribution system 210 may implement an extended service set (ESS) 240 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 identification (SSID).

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

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

[0091] Figure 2 The lower part of FIG. 1 shows a conceptual diagram illustrating an IBSS.

[0092] Reference Figure 2 In the lower part, the IBSS is a BSS operating in a self-organizing mode. Since the IBSS does not include an access point (AP), there is no centralized management entity that performs management functions in the center. That is, in the IBSS, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 may be composed of mobile STAs, and access to the DS is not allowed to form a self-contained network.

[0093] Figure 3 Describe the general link establishment process.

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

[0095] Figure 3The network discovery operation including active scanning processing is described. 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 exists around while moving to the 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 a 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 the 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).

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

[0097] After discovering the network, the STA may perform an authentication process in S320. This authentication process may be referred to as a first authentication process to clearly distinguish it from the security establishment operation in the subsequent 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 frame used for the authentication request / response is a management frame.

[0098] The authentication frame may include information about the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust security network (RSN), and limited cycle group.

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

[0100] 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, a mobile domain, a 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 mobile domain, a timeout interval (association recovery time), overlapping BSS scanning parameters, a TIM broadcast response, and a QoS map.

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

[0102] Figure 4 An example of PPDU used in the IEEE standard is described.

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

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

[0105] like Figure 4As shown, the HE-PPDU for multiple users (MU) 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 (ie, 4 or 8 μs).

[0106] The following describes a resource unit (RU) for a PPDU. A RU may include multiple subcarriers (or tones). A RU may be used to send signals to multiple STAs according to OFDMA. In addition, a RU may also be defined as sending a signal to one STA. A RU may be used for an STF, an LTF, a data field, etc.

[0107] Figure 5 The layout of resource units (RU) used in a 20 MHz frequency band will be described.

[0108] like Figure 5 As shown, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to form some fields of the HE-PPDU. For example, resources may be allocated for the HE-STF, HE-LTF, and data fields in the RU shown.

[0109] like Figure 5 As shown in the uppermost part of , 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 bands. Each unit may be allocated to a receiving STA (i.e., a user).

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

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

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

[0113] Similar to using RUs with various sizes Figure 5 ,exist Figure 6 In the example of 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 the guard band in the leftmost band of the 40MHz band, and 11 tones can be used for the guard band in the rightmost band of the 40MHz band.

[0114] like Figure 6 As shown in FIG. 4, 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.

[0115] Figure 7 The layout of RUs used in the 80 MHz frequency band will be described.

[0116] Similar to using RUs with various sizes Figure 5 and Figure 6 ,exist Figure 7 In the example of 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc., 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. may be used. In addition, seven DC tones may be inserted in the center frequency, 12 tones may be used for a guard band in the leftmost band of the 80 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 80 MHz band. In addition, 26-RU corresponding to 13 tones on each side of the left and right sides of the DC band may be used.

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

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

[0119] 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 may allocate 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 through the first RU in one MU PPDU, and may transmit the HE-STF, HE-LTF, and data fields for the second STA through the second RU.

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

[0121] Figure 8 Describe the structure of the HE-SIG-B field.

[0122] 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 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 be applied only to any one of the multiple users.

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

[0124] 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 on a specific frequency band where a specific RU (26-RU / 52-RU / 106-RU) is arranged.

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

[0126] [Table 1]

[0127]

[0128] like Figure 5 As shown in the example of , up to nine 26-RUs can be allocated to a 20MHz 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., 20MHz). 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 may be allocated to the far right, and seven 26-RUs may be allocated to its left.

[0129] The example in Table 1 only shows some RU positions where RU allocation information can be displayed. For example, the RU allocation information may include the example in Table 2 below.

[0130] [Table 2]

[0131]

[0132] "01000y2y1y0" relates to an example in which a 106-RU is allocated to the leftmost side of a 20 MHz channel and five 26-RUs are allocated to the right 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 8 STAs (e.g., user STAs) can be allocated to the 106-RU, and the number of STAs (e.g., user STAs) allocated to the 106-RU is determined based on 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 may be N+1.

[0133] Generally, multiple STAs (eg, user STAs) different from each other may be allocated to multiple RUs. However, multiple STAs (eg, user STAs) may be allocated to one or more RUs having at least a specific size (eg, 106 subcarriers) based on the MU-MIMO scheme.

[0134] 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 can be determined based on the RU allocation information of the common field 820. For example, when the RU allocation information of the common field 820 is "00000000", one user STA can be allocated to each of the nine 26-RUs (e.g., nine user STAs can be allocated). That is, up to 9 user STAs can be allocated to a specific channel through the OFDMA scheme. In other words, up to 9 user STAs can be allocated to a specific channel through a non-MU-MIMO scheme.

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

[0136] Fig. 9 An example of allocating multiple user STAs to the same RU through the MU-MIMO scheme is described.

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

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

[0139] Figure 8 and Fig. 9 The user field shown may be configured based on two formats. That is, the user field related to the MU-MIMO scheme may be configured in a first format, and the user field related to the non-MIMO scheme may be configured in a second format. Fig. 9 In the example of , 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).

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

[0141] For example, the first bit (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. In addition, the second bit (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to the space configuration. Specifically, examples of the second bit (i.e., B11-B14) may be shown in Tables 3 and 4 below.

[0142] [Table 3]

[0143]

[0144] [Table 4]

[0145]

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

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

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

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

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

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

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

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

[0154] Fig.10UL-MU-based operation is 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 a trigger frame 1030. Upon receiving a PPDU including a trigger frame, a trigger-based (TB) PPDU is transmitted after a delay corresponding to SIFS.

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

[0156] Reference Figures 11 to 13 Describes specific features of the trigger frame. Even when UL-MU communication is used, an Orthogonal Frequency Division Multiple Access (OFDMA) scheme or a MU-MIMO scheme may be used, and OFDMA and MU-MIMO schemes may be used simultaneously.

[0157] Fig.11 An example of a trigger frame is shown. Fig.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.

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

[0159] Fig.11 The frame control field 1110 may include information related to the MAC protocol version and additional 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.

[0160] In addition, the RA field 1130 may include address information of the receiving STA of the corresponding trigger frame, and may be optionally omitted. The TA field 1140 may include 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, 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 may be included. 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.

[0161] In addition, preferably including and receiving Fig.11 The number of receiving STAs of 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".

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

[0163] Fig.11 Each of the illustrated per-user information fields 1160#1 to 1160#N may include a plurality of subfields.

[0164] Fig.12 An example illustrating the common information field of a trigger frame. Fig.12 The subfields of may be partially omitted, and additional subfields may be added. In addition, the lengths of the various subfields shown may be changed.

[0165] The length field 1210 shown has the same value as the length field of the L-SIG field of the uplink PPDU sent 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.

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

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

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

[0169] The CP and LTF type field 1250 may include information related to 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, requesting a block ACK / NACK, etc.

[0170] 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 a typical trigger. For example, the basic type of trigger frame can be referred to as a basic trigger frame.

[0171] Fig.13 An example of subfields included in the per-user information field is described. Fig.13 The user information field 1300 may be understood as the above reference Fig.11 Any of the per-user information fields 1160#1 to 1160#N mentioned above. Included in Fig.13 The subfields in the user information field 1300 may be partially omitted, and additional subfields may be added. In addition, the length of each subfield shown may be changed.

[0172] Fig.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 an association identifier (AID) value of the receiving STA.

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

[0174] Fig.13The subfield of 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".

[0175] in addition, Fig.13 The subfield of 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".

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

[0177] Fig.14 Describe the technical features of the UORA scheme.

[0178] The sending STA (e.g., AP) can Fig.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, Fig.13 The information related to RU 1 to RU 6 may be included in, for example, the user identifier field 1310. Fig.13 AID=0 may mean UORA resources for associated STAs, and AID=2045 may mean UORA resources for non-associated STAs. Fig.14 The 1st to 3rd RU resources can be used as UORA resources for associated STAs. Fig.14 The 4th RU resource and the 5th RU resource can be used as UORA resources for non-associated STAs. Fig.14 The 6th RU resources may be used as typical resources for UL MU.

[0179] exist Fig.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. Fig.14 For STA4 in , since the AID of STA4 (eg, AID=3) is included in the trigger frame, resources of RU 6 are allocated without backoff.

[0180] Specifically, due to Fig.14 STA1 is the associated STA, so the total number of qualified RA RUs for STA1 is 3 (RU1, RU 2, and RU 3), so STA1 decrements the OBO counter by 3 to make the OBO counter 0. In addition, since Fig.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, due to Fig.14 STA3 is a non-associated STA, so the total number of eligible RA RUs for STA3 is 2 (RU 4, RU 5), and therefore STA3 decrements the OBO counter by 2, but the OBO counter is greater than 0.

[0181] Fig.15 Illustrate examples of channels used / supported / defined in the 2.4 GHz band.

[0182] The 2.4 GHz band may be referred to by other terms such as a first frequency band. In addition, the 2.4 GHz band may mean a frequency domain that uses / supports / defines channels having center frequencies close to 2.4 GHz (eg, channels having center frequencies within 2.4 to 2.5 GHz).

[0183] 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 as various terms such as channel numbers. The specific values ​​of channel indices and center frequencies may vary.

[0184] Fig.15An example is given of 4 channels within the 2.4 GHz frequency band. Each of the 1st frequency domain 1510 to the 4th frequency domain 1540 shown herein may include one channel. For example, the 1st 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 2nd frequency domain 1520 may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The 3rd frequency domain 1530 may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The 4th frequency domain 1540 may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0185] Fig.16 Illustrate examples of channels used / supported / defined in the 5 GHz band.

[0186] The 5 GHz band may be referred to as other terms such as a second frequency band, etc. The 5 GHz band may mean 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 band may include multiple channels between 4.5 GHz and 5.5 GHz. Fig.16 The specific values ​​shown may be varied.

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

[0188] A plurality of channels may be configured within the 5 GHz frequency band, and the bandwidth of each channel may be set differently, for example, to 20 MHz, 40 MHz, 80 MHz, 160 MHz, etc. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range may be divided into four channels via a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range may be divided into two channels via an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range may be divided into one channel via a 160 MHz frequency domain.

[0189] Fig.17 Illustrate examples of channels used / supported / defined in the 6 GHz band.

[0190] The 6 GHz frequency band may be referred to as 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. Fig.17 The specific values ​​shown may be varied.

[0191] For example, Fig.17 The 20MHz channel can be defined starting from 5.940GHz. Fig.17 Among the 20 MHz channels of the channel, the leftmost channel may have an index of 1 (or a channel index, a 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.

[0192] therefore, Fig.17 The index (or channel number) of the 2MHz channel 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, Fig.17 The index of the 40MHz 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.

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

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

[0195] Fig.18 An example of PPDU used in this specification is described.

[0196] Fig.18The PPDU of the WLAN 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 the present 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.

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

[0198] exist Fig.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 a physical layer.

[0199] You can Fig.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.5kHz, and the subcarrier spacing of the EHT-STF, EHT-LTF and data fields can be determined to be 78.125kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG fields can be expressed in units of 312.5kHz, and the tone index (or subcarrier index) of the EHT-STF, EHT-LTF and data fields can be expressed in units of 78.125kHz.

[0200] exist Fig.18 In the PPDU, the L-LTF and L-STF can be the same as those in the regular fields.

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

[0202] For example, the transmitting STA may apply BCC encoding based on a 1 / 2 coding rate 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 positions other than the pilot subcarriers {subcarrier indexes -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols may be mapped to subcarrier indexes -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 of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The aforementioned signal may be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

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

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

[0205] 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 (e.g., OFDM symbol) used for the U-SIG may have a duration of 4 μs. Each symbol of the U-SIG may be used to send 26 bits of information. For example, each symbol of the U-SIG may be sent / received based on 52 data tones and 4 pilot tones.

[0206] Through U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 uncoded bits) can be transmitted. The first symbol of U-SIG can transmit the first X bits of information of A-bit information (e.g., 26 uncoded bits), and the second symbol of U-SIG can transmit the remaining Y bits of information of A-bit information (e.g., 26 uncoded bits). For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional coding (i.e., BCC coding) 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 assigned to each U-SIG symbol. In addition to DC index 0, one U-SIG symbol can be sent 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, namely, tones -21, -7, +7, +21.

[0207] 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 of the first symbol allocated to 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".

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

[0209] 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, the first value of the 3-bit PHY version identifier may indicate that the TX / RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits an EHT PPDU, the 3-bit PHY version identifier may be set to a first value. In other words, the receiving STA may determine that the RX PPDU is an EHT PPDU based on the PHY version identifier having a first value.

[0210] For example, the version-independent bits of the U-SIG may include a 1-bit UL / DL Flag field. 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.

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

[0212] 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 can be included in the version-related bit of the U-SIG.

[0213] 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 a 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 EHT-LTF / STF; and 7) information related to a field indicating the EHT-LTF length and the CP length.

[0214] Can Fig.18 Preamble puncturing is applied to the PPDU of the primary 20 MHz band. Preamble puncturing implies that puncturing is applied to part of the full band (e.g., the secondary 20 MHz band). For example, when sending an 80 MHz PPDU, the STA may apply puncturing to the secondary 20 MHz band in the 80 MHz band, and may send the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0215] For example, the pattern of the leading perforation can be preconfigured. For example, when the first perforation pattern is applied, perforation can be applied only to the auxiliary 20 MHz band in the 80 MHz band. For example, when the second perforation pattern is applied, perforation 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 perforation pattern is applied, perforation can be applied only to the auxiliary 20 MHz band in the main 80 MHz band included in the 160 MHz band (or the 80+80 MHz band). For example, when the fourth perforation pattern is applied, perforation can be applied to at least one 20 MHz channel that does not belong to the main 40 MHz band in the presence of the main 40 MHz band in the 80 MHz band included in the 160 MHz band (or the 80+80 MHz band).

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

[0217] For example, based on the following method, the U-SIG and the EHT-SIG may include information related to the preamble puncturing. 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 puncturing applied to the first 80 MHz band (i.e., information related to the preamble puncturing 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 puncturing applied to the second 80 MHz band (i.e., information related to the preamble puncturing pattern). Meanwhile, the EHT-SIG continuous with the first U-SIG may include information related to 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 preamble puncturing applied to the first 80 MHz band (i.e., information related to the preamble puncturing pattern).

[0218] Additionally or alternatively, based on the following method, the U-SIG and the EHT-SIG may include information related to preamble puncturing. The U-SIG may include information related to preamble puncturing for all frequency bands (ie, 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 (ie, information related to the preamble puncturing pattern).

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

[0220] Fig.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 for the EHT-SIG may be included in the U-SIG.

[0221] The EHT-SIG may include reference Figure 8 and Fig. 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 may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0222] As in Figure 8 In the example of , the common field of EHT-SIG and the user-specific field of EHT-SIG may be encoded separately. One user block field included in the user-specific field may include information for two users, but the last user block field included in the user-specific field may include information for one user. That is, one user block field of EHT-SIG may include a maximum of two user fields. Fig. 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.

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

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

[0225] The examples of 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, and some entries in Tables 5 to 7 may be omitted, and entries may be added (not shown).

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

[0227] In addition, multiple RUs may be allocated to one STA in the EHT system. For example, with respect to "index 60" of Table 6, one 26-RU may be allocated to the leftmost user (ie, receiving STA) of the 20 MHz band, one 26-RU and one 52-RU may be allocated to the right side thereof, and five 26-RUs may be allocated to the right side thereof separately.

[0228] [Table 5]

[0229]

[0230] [Table 6]

[0231]

[0232] [Table 7]

[0233]

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

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

[0236] Fig.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. Fig.18 The HE-LTF can be used to estimate the channel in a MIMO environment or an OFDMA environment.

[0237] Can be set according to various types Fig.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 may have a period of 0.8 μs, and the periodic signal of 0.8 μs may 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) may 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 may have a period of 1.6 μs, and the periodic signal of 1.6 μs may be repeated 5 times to become a second type of STF with a length of 8 μs. In the following, an example of a sequence for configuring the EHT-STF (i.e., an EHT-STF sequence) is proposed. The following sequence can be modified in various ways.

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

[0239] <Formula 1>

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

[0241] The EHT-STF for a 20MHz PPDU may be configured based on the following formula. The following example may be a first type (ie, 1x STF) sequence. For example, a 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 a duration of b tone intervals (ie, subcarrier intervals) defined from tone index (ie, subcarrier index) 'a' to tone index 'c'. For example, the following formula 2 may represent a sequence of 16 tone intervals defined from tone index -112 to tone index 112. Since a subcarrier spacing of 78.125kHz is applied to EHT-STR, 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.

[0242] <Formula 2>

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

[0244] EHT-STF(0)=0

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

[0246] <Formula 3>

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

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

[0249] <Formula 4>

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

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

[0252] <Formula 5>

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

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

[0255] <Formula 6>

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

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

[0258] <Formula 7>

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

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

[0261] <Formula 8>

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

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

[0264] EHT-STF(248)=0

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

[0266] <Formula 9>

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

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

[0269] <Formula 10>

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

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

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

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

[0274] <Formula 11>

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

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

[0277] EHT-STF(504)=0

[0278] The EHT-LTF may have first, second, and third types (i.e., 1x, 2x, 4x LTF). For example, the first / second / third type LTF may 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 may 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) may be applied to the first / second / third type LTF.

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

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

[0281] For example, based on Figure 5 The RU is used to configure the EHT PPDU sent on the 20MHz band, that is, the 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.

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

[0283] because Figure 6 The RU position corresponds to 40MHz, so it can be Figure 6 The tone plan for 80 MHz is determined when the pattern of is repeated twice. That is, the tone plan for 80 MHz can be determined based on Figure 7 The RU is Figure 6 The RU repeats the new tone schedule twice to send the 80 MHz EHTP PDU.

[0284] 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 the 80 MHz EHT PPDU allocated based on OFDMA can have 23 DC tones. Different from this, the 80 MHz EHT PPDU allocated based on non-OFDMA (i.e., non-OFDMA full bandwidth 80 MHz PPDU) can be configured based on 996-RU and can include 5 DC tones, 12 left guard tones, and 11 right guard tones.

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

[0286] Based on the following method Fig.18 The PPDU is determined (or identified) as an EHT PPDU.

[0287] 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 as 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 Fig.18 The type of the EHT PPDU (e.g., SU / MU / triggered / extended range type) can be detected by using bit information included in the symbol after 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 continuous with the L-SIG field and is the same as the L-SIG; 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).

[0288] For example, 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 is a BPSK symbol; 2) when an RL-SIG in which the L-SIG 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 is "1" or "2", the RX PPDU may be determined as a HEPPDU.

[0289] For example, the receiving STA may determine the type of the RX PPDU as non-HT, HT, and VHT PPDU based on the following aspects. 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, and VHT PPDU. In addition, even if the receiving STA detects RL-SIG repetition, when it is detected that 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, and VHT PPDU.

[0290] 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 Fig.18 PPDU transmission / reception signal. Fig.18 The PPDU can be used to send / receive various types of frames. For example, Fig.18 The PPDU may 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) notification, and trigger frames. For example, Fig.18 The PPDU may 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, Fig.18 The PPDU can be used for data frames. For example, Fig.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.

[0291] Fig.19 An example of a transmission device and / or a reception device of a modification of the present specification is described.

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

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

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

[0295] Reference Fig.19 , the power management module 611 manages the power for the processor 610 and / or the transceiver 630. The battery 612 supplies power to the power management module 611. The display 613 outputs the results processed by the processor 610. The keypad 614 receives input to be used by the processor 610. The keypad 614 may be displayed on the display 613. The 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 telephony devices such as mobile phones and computers.

[0296] Reference Fig.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.

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

[0298] For example, in the IEEE 802.11n system, 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 the IEEE 802.11ac system.

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

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

[0301] Fig. 20 An example of channel bonding is shown. Fig. 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.

[0302] Channel bundling can be performed when the channel adjacent to the main channel is in an idle state. That is, the main 20MHz channel, the auxiliary 20MHz channel, the auxiliary 40MHz channel and the auxiliary 80MHz channel can be bundled sequentially. However, if it is determined that the auxiliary 20MHz channel is in a busy state, channel bundling cannot be performed even if all other auxiliary channels are in an idle state. In addition, when it is determined that the auxiliary 20MHz channel is in an idle state and the auxiliary 40MHz channel is in a busy state, channel bundling can be performed only on the main 20MHz channel and the auxiliary 20MHz channel.

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

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

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

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

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

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

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

[0310] When a STA supports multiple links, the transceiver supporting each link can operate as a logical STA. For example, a STA supporting two links can be expressed as a multi-link device (MLD), which includes a first STA for a first link and a second STA for a second link. For example, an AP supporting two links can be expressed 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 expressed as a non-AP MLD, which includes a first STA for the first link and a second STA for the second link.

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

[0312] MLD (AP MLD and / or non-AP MLD) can send information on the link that the corresponding MLD can support through ML settings. Link information can be configured in various ways. For example, the 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 uplinks / downlinks supported by the MLD (or STA), 3) information about the location / band / resource of the uplink / downlink 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, 5) information about the ACK strategy available or preferred in at least one uplink / downlink, and 6) information about the service identifier (TID) available or preferred in at least one uplink / downlink. The TID is related to the priority of the service 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.

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

[0314] Through ML setting, multiple links available for sending MLD and receiving MLD related to ML communication can be set, and this can be called "enabled links". "Enabled links" can be called differently with various expressions. For example, it can be called various expressions such as first link, second link, transmission link and reception link.

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

[0316] In the standard Extreme High Throughput (EHT) discussed after IEEE802.11ax, HARQ is being considered for introduction. When HARQ is introduced, coverage can be expanded in a low signal-to-noise ratio (SNR) environment, that is, in an environment where the distance between the transmitter and the receiver is long, and higher throughput can be obtained in a high SNR environment.

[0317] The equipment described below can be Figure 1 and / or Fig.19 device, and the PPDU described below may be Fig.18 The device may be an AP or a non-AP STA. The device described below may be an AP multi-link device (MLD) supporting multi-link or a non-AP STA MLD.

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

[0319] In the following, although described in the form of multilink, the frequency band can be configured in various other forms. Although terms such as multiband and / or multilink may be used in this specification, for the convenience of the following description, the following embodiments may be described based on multilink.

[0320] In the following description, MLD refers to a multi-link device. An MLD has one or more subordinate STAs and has a MAC service access point (SAP) connected to an upper link layer (logical link control, LLC). MLD may refer to a physical device or a logical device. In the following, a device may refer to an MLD.

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

[0322] IEEE802.11be can support two types of multi-link operations. For example, simultaneous transmission and reception (STR) and non-STR operations can be considered. For example, STR can be referred to as asynchronous multi-link operation, while non-STR can be referred to as synchronous multi-link operation. Multi-link can include multiple frequency bands. That is, multi-link can mean a link included in several frequency bands, or can mean a plurality of links included in one frequency band.

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

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

[0325] refer to Fig.21 , STA MLD (or AP MLD) may include three STAs, may have three links, and each link may have a primary channel (PCH). In 11be, STA MLD should provide information related to one or more links it has for a single setting. Therefore, a method for indicating the above information may be required. Hereinafter, a method for this and a method using the method will be described.

[0326] The terms (names) in the present disclosure may vary, and the STA may include an AP STA or a non-AP STA.

[0327] Fig. 22 is a diagram illustrating an embodiment of a multi-link setting process.

[0328] refer to Fig. 22 , the AP MLD may provide the non-AP MLD with multi-link information. Based on the multi-link information, the non-AP MLD may request link 1 and link 2 as operating links through link 1, and the AP MLD responds to the request.

[0329] In the present disclosure, a link that transmits multi-link information, such as Link 1, may be referred to as an associated link, and other links may be referred to as non-associated links.

[0330] A method of indicating multilink information transmitted through link 1 may be as follows.

[0331] Information about an associated link such as Link 1 may be sent through an EHT Capability / Operation element similar to the conventional one. For example, because an EHT STA or MLD with a single link currently operates on only one link, a procedure similar to the conventional procedure may be applied to the associated link as the only link.

[0332] A new element can be used to indicate non-associated links such as link 2 and link 3. That is, a new element capable of indicating information related to links other than associated links can be defined. In the present disclosure, this element may be referred to as a multilink element, and is not limited thereto and may be changed.

[0333] A multilink element may indicate information related to one or more links, except for the link through which the multilink element is sent. However, the link through which the multilink element is sent is not necessarily excluded, and information related to the corresponding link may be included as needed. The information that can be included in the multilink element may be as follows, but is not limited thereto. In addition, according to various circumstances, all of the following may be included, or only some of the contents may be included according to the frame type / operation. The following names may change.

[0334] 1) Number of links supported: This indicates the total number of supported links.

[0335] EX) When a bitmap is used and the total number of links is set to "3", the above content can be set to "11" if the associated link is included, and set to "10" if it is not included.

[0336] The number of supported links may mean the number of APs that can simultaneously exchange data frames (and / or management frames) through AP MLD, and the number of non-AP STAs that can simultaneously exchange data frames through non-AP MLD. The technical effect obtained by indicating this value in the multi-link (ML) element will be described separately in the presence field below.

[0337] 2) Link-specific information: This information includes specific information related to each link, and this information can be as follows but is not limited to this.

[0338] 2-1) Link Identifier: An identifier that can distinguish each link. The AP / STA can redefine the identifier for each link, or can use the existing BSSID, BSS color, etc. as the link ID.

[0339] Ex) New identifiers: 0, 1, 2, etc.

[0340] 2-2) Channel information: This information includes channel information for each link, and this information may be as follows but is not limited thereto.

[0341] - Frequency band information: This information includes information related to the frequency band supporting the multi-link operation. Specifically, this information includes an ID capable of distinguishing the frequency band of the EHT operation, a frequency band ID field of the conventional specification, etc., but is not limited thereto.

[0342] Ex 1) Frequency band ID: 0-2.4GHz, 1-5GHz, 2-6GHz, etc.

[0343] Ex 2) Band ID field: 2-2.4GHz, 4-5GHz, 7-6GHz, etc.

[0344] - Primary Channel: This information includes the primary channel number of the corresponding link channel.

[0345] - Channel Width: This information includes the channel bandwidth of the corresponding link channel.

[0346] -CCFS 0: Center frequency of main 80

[0347] -CCFS1: Channel center frequency band of auxiliary 80 or main 160

[0348] To support 240MHz / 320MHz, CCFS2 may be required additionally.

[0349] -CCFS2: Channel center frequency of S80-2 or P240 in case of 240MHz (P320 or S160 in case of 320MHz)

[0350] 2-3) Auxiliary information: This information includes information that can help STA MLD select links, transitions, or operations.

[0351] -BSS load information: This information includes the BSS load information of the link and the BSS load element field of the existing specification.

[0352] -TSF / Beacon Interval: This information includes the timestamp / beacon interval of the link channel

[0353] -TID Mapping: This information includes the TID assigned to the link

[0354] Ex) When the bitmap of TID 0 to TID 7 is used, "00001111" may indicate that TID 4 to TID 7 are mapped to the link.

[0355] - Primary link: This indicates whether the corresponding link is a primary link. Here, the primary link refers to a link on which the main BSS functionality is performed for the purpose of channel access and power saving.

[0356] - Link Status: This includes information about whether each link is currently available for data transmission (up / down).

[0357] Ex) When indicated by link-specific information, it is set to "0" and the STA cannot use the link for current data transmission. It is set to "1" and the STA can use the link for current data transmission

[0358] Ex) When there is no information indication for each link, it can be expressed in the form of a bitmap: in the case of "011", the bitmap indicates that the first link has capability but is not currently used for data transmission.

[0359] 2-4) Capability: It includes the capability-related information of each link

[0360] - Number of Supported Spatial Streams (NSS): It includes the number of spatial streams supported by each link.

[0361] Ex)1 / 2 / 4 / 8 / 16

[0362] - Supported Band Information (SBI): It includes information of bands capable of multi-link operation. Specifically, this can be an ID capable of distinguishing a band in which EHT operates, a band ID field of an existing specification, etc., but is not limited thereto.

[0363] Ex 1) Band ID: "0" for 2.4 GHz, "1" for 5 GHz, "2" for 6 GHz, and so on.

[0364] Ex 2) Band ID field: "2" for 2.4 GHz, "4" for 5 GHz, "7" for 6 GHz, and so on.

[0365] Ex 3) Bitmap: It can be a multiple selection of 2.4 / 5 / 6GHz. For example, "011" can indicate support for 5GHz band and 6GHz band.

[0366] 3) Indication on multi-link operation: It indicates multi-link operation.

[0367] - Simultaneous TX / RX (STR): It indicates the ability to enable simultaneous TX / RX in multiple links, i.e., whether RX in another link is possible while TX in one link

[0368] Ex 1) If the elements are indicated in link indication order, it is possible to indicate whether all link pairs are STR in the form of a bitmap, such as [link 1, link 2], [link 1, link 3].

[0369] For the case where there are N links, 1 bit is used for each pair to indicate whether it is a STR. Each bit indicates whether a pair [first, second] is a STR, ..., whether a pair [first, Nth] is a STR, whether a pair [second, third] is a STR. If it is a STR, the corresponding value is set to "0". If not, the corresponding value is set to "1".

[0370] Ex 2) If the elements are indicated based on the link indication order, whether STR is possible for the pair, i.e., [link 1, link 2], [link 2, link 3] in the sequence, can be indicated in the form of a bitmap. In this way, the relationship between link 1 and link 3 can be known from [link 1, link 2] and [link 2, link 3]. For example, if [link 1, link 2] is STR and [link 2, link 3] is STR, then link 1 and link 3 will be STR.

[0371] For N links, 1 bit can be used to indicate whether each pair is a STR in sequence: STR of the 1st link and the 2nd link, STR of the 2nd link and the 3rd link, ... / If STR, then "1", otherwise "0".

[0372] It can reduce the overhead compared to Ex 1), but the link indication should be in order.

[0373] - Operation link: indicates the link to be operated

[0374] Ex 1) If the elements are indicated in a link indication order, the operation links can be indicated in the form of a bitmap.

[0375] If an associated link and a first non-associated link are selected from three links, "110" may be indicated. Also, if an associated link is not included, "10" may be indicated. For example, when link-specific information is included, only information related to an actual operating link may be included, and in this case, the operating link field may not exist.

[0376] Similar to the example indicating "10", if the association (discovery) link is always regarded as an operation link, the association link related bit can be excluded. That is, among the total three links, only two links can be indicated by the bitmap.

[0377] - Primary link: This indicates whether the corresponding link is a primary link. Here, the primary link refers to a link on which the main BSS functionality is performed for the purpose of channel access and power saving.

[0378] Ex 1) If the elements are indicated in a link indication order, the operation links can be indicated in the form of a bitmap. Among the three links, if the associated link is the main link, if the indication includes the associated link, it can be indicated as "100", and if the indication does not need to include the associated link, it can be indicated as "10".

[0379] Similar to the example indicating "10", if the associated (discovered) link is always regarded as the main link, the associated link related bit can be excluded. That is, among the total three links, only two links can be indicated by the bitmap.

[0380] -TID to Link Mapping: This indicates which TID is mapped to the link

[0381] Ex 1) For TID 0 to TID 7, 8 bits are indicated in the bitmap in the order indicated by each link.

[0382] Ex 2) This is indicated by as many bitmaps as the number of links of one TID.

[0383] Ex 3) TIDs can be grouped to indicate, for example, TIDs mapped to the same AC (e.g., TID 1, 2) can be indicated with 1 bit. That is, mapping can be performed per AC, and two ACs can be indicated with 1 bit to further reduce signaling overhead. That is, there is a trade-off between signaling overhead and granularity.

[0384] Fig.23 is a diagram illustrating an embodiment of a multilink element.

[0385] refer to Fig.23 , the multilink element may include a link number field, a link specific information field, and an indication field about ML operation. The link specific information field may include an ID, channel information, auxiliary information, and capability fields.

[0386] The multilink element can be applied to the following examples.

[0387] Example 1: Example for indicating a link set

[0388] -Multi-link elements can be used when requesting / responding to an operational link and determining the primary link mentioned above.

[0389] -Can be indicated in the form of a bitmap by using the order indicating the links.

[0390] Fig.24 is a diagram illustrating an embodiment of a method of instructing an operation link set.

[0391] refer to Fig.24 , the multilink element includes information related to link 2 and link 3 in order, STA A requests link 1 and link 2 as operating links, and AP 1 responds to the request. In this case, the link set is indicated in the order of link 1 (sending the element), link 2, and link 3 by using a bitmap. Therefore, STA A can request AP by indicating a bitmap of "110", and AP can confirm the bitmap of "110".

[0392] Fig.25 is a diagram illustrating an embodiment of a method for indicating a link set in a single BA protocol.

[0393] refer to Fig.25, the multilink element includes information about link 2 and link 3 in sequence, and STA A is negotiating with the AP to use BA for TID 1 in link 1 and link 2. In this case, the link set can be indicated by using a bitmap in the order of link 1 (sending the element), link 2, and link 3. Therefore, STA A can indicate "110" (i.e., indicating link 1 and link 2) to request the AP using the ADDBA frame, and the AP can confirm success as it is (using the bitmap "110").

[0394] Example 2: Example indicating STR ability

[0395] Fig.26 is a diagram illustrating an embodiment of a method of indicating STR capability.

[0396] refer to Fig.26 , the multi-link element includes information about link 2 and link 3 in sequence, and may indicate the STR capabilities for links 1 / 2 / 3.

[0397] In the first example, the multilink element includes information that link 1 and link 2 operate based on STR, and link 2 and link 3 operate based on STR(1), so information that link 1 and link 3 can also operate based on STR can be included.

[0398] The second example is an example in which the multilink element is indicated for all pairs, and it is assumed that the pair order is set to {link 1 and link 2}, {link 1 and link 3}, and {link 2 and link 3}, and can include information that all pairs operate based on STR (1).

[0399] Example 3: Example indicating TID to link mapping

[0400] Fig. 27 is a diagram illustrating an embodiment of a multilink element including TID and link-to-link mapping information.

[0401] refer to Fig. 27 , the multilink element includes information about Link 2 and Link 3 in sequence, and shows a TID to link mapping using a bitmap starting / considering Link 1 as the associated link.

[0402] The left diagram is an example of a bitmap of links to which each TID is assigned. For example, if TID 0 is indicated as "110", it means that TID 0 is assigned to link 1 and link 2. The right diagram is an example of a bitmap of TIDs assigned to each link, and the link order is the same as indicated in the link specific information. For example, if "001111111" is indicated for link 1, it means that TIDs 2 to 7 are assigned to link 1. Although the methods of the left diagram and the right diagram are different, the signaling overhead is the same.

[0403] Fig.28 is a diagram illustrating an embodiment of a multilink element including TID and link-to-link mapping information.

[0404] refer to Fig.28 , the multilink element includes information about Link 2 and Link 3 in sequence, and shows a TID to link mapping using a bitmap starting / considering Link 1 as the associated link.

[0405] In order to reduce signaling overhead, two TIDs are bundled / grouped for each AC, and when "111" is indicated for TID 1 / 2 (ie, AC_BK), it means that all links are allocated for TID 1 and TID 2.

[0406] Examples of allowing dynamic indications

[0407] The above-mentioned field may be a predefined field, which can be omitted for each AP MLD or non-AP MLD or frame. Alternatively, in the case where this is not defined, it is possible to dynamically determine whether the field exists by using 1 bit in front of the above-mentioned field. In the present disclosure, this field may be referred to as a presence field.

[0408] Fig.29 is a diagram illustrating an embodiment of a presence field of a multilink element.

[0409] refer to Fig.29, shows an example of the integrated structure of the above-mentioned multi-link (ML) element, and the multi-link element is basically composed of public information and link information. The public information includes the public information among the STA in the MLD, and the link information includes specific information for each link (STA / AP) through each STA profile. The existence field can exist for the public information and the link information respectively. The public information can be present in the multi-link control field, and the link information can be present in the per-STA control field included in the per-STA profile. As described above, these existence fields can determine whether to include information according to the type of the multi-link element (the type subfield of the multi-link control field), the purpose and the process. In this way, it is possible to avoid including unnecessary information and have a compact ML IE format suitable for various purposes. Examples in this regard may be as follows.

[0410] Field #1 exists: TID to link mapping

[0411] For example, if the bit preceding the TID to Link Mapping field (ie, the TID to Link Mapping Present field) indicates "1", this field exists, and if "0" indicates this field it does not exist.

[0412] Fig.30 is a diagram illustrating an embodiment of a TID to Link Mapping Presence field.

[0413] refer to Fig.30 , showing the above-mentioned TID to link mapping indication (i.e., Example 3) and the presence field. If the TID to link mapping is located in the common information, the presence or absence may be indicated by the TID to link mapping presence subfield in the multi-link control field. If the value of the presence subfield is "1", the TID to link mapping field is present in the common information field. Basically, TID to link mapping is the default operation and does not require separate signaling, and because all TIDs are defined to be mapped to all links, this presence field may be useful if separate signaling is required.

[0414] Fig.31 is a diagram illustrating an embodiment of a TID to Link Mapping Presence field.

[0415] refer to Fig.31 , an example of the presence of a field is shown when TID to link mapping is indicated in link information instead of common information. Fig.31 refer to Fig.29 Similarly, the presence or absence may be indicated by the TID to Link Mapping Present subfield of the Per-STA Control field. If the value of this subfield is "1", the TID to Link Mapping field is present in the Per-STA profile.

[0416] If the TID to link mapping for all setup links is indicated by a presence field in the common information and implicitly indicated by the order of the link IDs, then the overhead of including sub-element IDs, link IDs, full profiles, etc. in the link information by default may be reduced (e.g., Fig.30 ). However, in each STA profile (e.g., Fig.31 ), only a part of a specific link may be indicated by the link ID, and in this case, the number of links to be indicated may need to be indicated in the common information. In addition, if the TID to link mapping is always carried with other information, the link information that can indicate the information of each link by the link ID may be appropriate in position.

[0417] Existence Field #2: STR Ability

[0418] For example, if "1" is indicated in front of the STR capability, this field exists, and if "0" is indicated, this field does not exist.

[0419] Fig.32 and Fig.33 is a diagram illustrating an embodiment of a Simultaneous Send and Receive (STR) Capability Present field.

[0420] refer to Fig.32 , showing the above-mentioned STR capability indication (simultaneous TX / RX (STR) of Example 2) and the presence field. If the STR capability is located in the common information, the presence or absence may be indicated by the STR capability presence subfield of the multi-link control field. If the value of the presence subfield is "1", the STR capability field may be present in the common information field. If the MLD (e.g., AP MLD) operates all link pairs based on STR by default, separate signaling may not be required. Therefore, if there are link pairs that do not operate based on STR, this presence field may be useful.

[0421] refer to Fig.33 , an example of the presence field is shown when STR capability is indicated in link information rather than public information. Fig.33 refer to Fig.29 . Similarly, the presence or absence can be indicated by the STR capability presence subfield of the per-STA control field. If the value of this subfield is "1", the STR capability field exists in the per-STA profile. In this STR capability, based on the link corresponding to each STA, only the pairs with other links are indicated. For example, if link 2 is the standard for each STA, the STR capabilities of the pairs of link 2 and link 1 and the pairs of link 2 and link 3 are indicated.

[0422] If the STR capability of all links is indicated through a presence field in the common information, and the pairs are implicitly indicated in the order of link ID, sub-element ID, link ID, complete profile included in the link information by default (as indicated in Example 2), the overhead may be reduced. In addition, redundancy may appear in the link information as a whole. (For example, {link #1, link #2} and {link #2, link #1}. However, if this capability is indicated only when there is a link pair that is not based on STR operation (NSTR), it may be difficult to distinguish the pairs in the common information. Therefore, the method of indicating through the presence field in the link information may be appropriate.

[0423] Field #3 exists: Information related to the associated link (i.e., sending STA)

[0424] This may indicate the presence or absence of information related to the above-mentioned associated link, ie, the link (STA) that sent the ML element.

[0425] Because the information related to the STA sending the ML element is included in the management (Mgmt) frame (e.g., beacon, probe response frame) including the multi-link element, most of the information may not be included separately in the ML element. However, if it is not always included in the Mgmt frame (e.g., change sequence, link ID) or the STA requests partial information instead of complete information, it may be included in the ML element. If this information is included in the per-STA profile of the link information, a separate presence field is not required because the link ID is indicated and can already be identified. However, in order to reduce the default overhead of the link information mentioned above, the presence field may be included when included in the common information. In addition, if the above information exists because the presence field has a value of "1", the information related to the sending STA may have a format.

[0426] Fig.34 is a diagram illustrating an embodiment of a presence field for transmitting information of STA.

[0427] refer to Fig.34 , when indicating information related to the transmitting STA in the common information, an example of the existence of the field is shown. The presence or absence may be indicated by the transmitting STA's information existence subfield of the multi-link control field. If the value of the existence subfield is "1", the transmitting STA's information field exists in the common information field. Link ID, change sequence, etc. may be indicated in the transmitting STA's information, and may include additional requested information, but is not limited thereto.

[0428] Field #4 exists: Example indicating information related to the number of links

[0429] This information refers to the number of links supported in 1) mentioned above.

[0430] The number of supported links indicates the number of APs that can simultaneously exchange data frames (and / or management frames) for the AP MLD, and the number of non-AP STAs that can simultaneously exchange data frames (and / or management frames) for the non-AP MLD.

[0431] Depending on the Mgmt frame and its purpose, this information may be present, that is, it may be present when the signaling affected by this information is present in the ML element. In addition, this information may not be present when the signaling affected by this information is not present. Therefore, this presence field may be present.

[0432] Fig.35 is a diagram illustrating an embodiment of a link quantity presence field.

[0433] refer to Fig.35 , when indicating information related to the number of links in the common information, an example of the presence of a field is shown. The presence can be indicated by the link number presence subfield of the multi-link control field. If the value of this subfield is "1", the link number field is present in the common information.

[0434] If information related to all STAs (links) in the MLD is always included, the number of links can be derived from the number of per-STA profiles. However, the presence field may be necessary because there are cases where it is not (for example, when only information about some links is requested, or when information about all STAs is not always included in the case of association). In addition, because it is possible to determine whether to include a field affected by the number of links based on the type of management frame including the ML element and the purpose of the ML element, the link number presence field may be required. For example, in a non-AP MLD, when information related to the links to be received from the AP is not yet known, such as when a probe request frame is sent during an initial scan, as mentioned above, because the signaling of STR capabilities or TID to link mapping affected by the number of links may not be performed, the link number field may not be required. However, if the MLD knows the link information, such as when sending an association request frame, and signaling of STR capabilities or TID to link mapping is required, the link number is necessary. Therefore, the link number can be dynamically indicated by this presence field.

[0435] The signaling affected by the Number of Links field and the effects of this information are as follows.

[0436] TID to link mapping and STR capabilities

[0437] As mentioned in the presence fields #1 and #2 above, the field sizes of the TID to link mapping and STR capability may vary depending on the number of links. That is, if a TID bitmap is used in the TID to link mapping, the number of TID bitmaps varies according to the number of links, and if the STR is indicated according to pairs in the STR capability, the number of pairs varies according to the number of links. Therefore, the number of links can affect the size of these fields.

[0438] Fig.36 and 37 is a diagram illustrating an embodiment of a TID to link mapping and STR capability field according to the number of links.

[0439] refer to Fig.36 and Fig.37 , when the number of links is "3" in both cases, when the TID to link mapping is included in the common information, there are three TID bitmaps (for links #1, #2, #3), and if the STR capability is included in the link information, the number of link pairs becomes "2" (i.e., {link #2, link #1} and {link #2, link #3}). For example, the content and size included in the TID to link mapping field and the STR capability field may be affected according to the number of links. That is, the content and size included in the TID to link mapping field and the STR capability field may be determined based on the number of links.

[0440] Estimated number of unset STAs

[0441] The association request frame includes information about the STA requesting the setup (association) (in each per-STA profile), and the association response frame includes information about the AP that established the setup. That is, it does not include information related to all STAs. Therefore, when re-establishing the setup with the STA that was not set up after the multi-link setup (e.g., link transition / switching), it is possible to know how many STAs that were not set up exist by the previous link number, and use this to request information.

[0442] Fig.38 is a diagram illustrating an embodiment of a multilink element.

[0443] refer to Fig.38 , the multilink element may be included in the association request or association response frame. For example, when the number of links in the ML IE included in the association request frame or the association response frame is indicated as "3" and the number of profiles per STA is "1", it can be seen that the number of STAs that do not indicate information (ie, STAs that do not want to be set) is 1. For reference, it is assumed that information about the STA that sends this MLIE is basically included in the association request or response frame.

[0444] As another example, since non-AP does not indicate channel information, if "1" is indicated in front of the channel information field, this field exists, and if "0" is indicated, it does not exist. Therefore, in addition to the mandatory fields that should exist in all frames, the presence of this field that may or may not exist can be indicated by dynamic indication.

[0445] Fields that can be included in each link except bitmap

[0446] Among the fields mentioned above, a bit value corresponding to each link in the bitmap may be included in each corresponding link field of the link-specific information. Although the relationship between links such as STR capabilities is difficult to classify, whenever information related to each link is provided, a bitmap such as a main link may indicate 1 bit. For example, if the bitmap related to the main link is "100", "0" may be indicated by using 1 bit of information related to link 2 in the link-specific information, and "0" may also be indicated by using 1 bit in link 3.

[0447] Examples of replacing a part of a multilink element or a child element of another element

[0448] Some information of a multilink element can be replaced with other existing elements. However, when using existing elements, there may be fields that are not necessarily needed, which may cause overhead.

[0449] Elements that can be replaced may include 1) a neighbor report element, 2) a reduced neighbor element, and 3) a multi-band element.

[0450] 1. Neighbor Report Elements

[0451] This element can basically indicate channel information by operation class, channel number, etc., and can additionally contain a large amount of information by using optional sub-elements. Currently, the optional sub-elements include the following information.

[0452] [Table 8]

[0453]

[0454]

[0455] In 11ax, HE capabilities / operation elements, BSS payload / HE BSS payload, and SSID are additionally included.

[0456] EHT can also include a lot of information using reserved IDs. Therefore, 1) if the EHT capability / operation element is defined in 11be, all capability and operation related information can be added to the above reserved part, or 2) if only the necessary information for data exchange with other links is entered, it can be added to the above reserved part in the form of "reduced EHT capability / operation element" by only forming the relevant fields. These elements can include information related to the above multi-link elements.

[0457] If a part of a multilink element is replaced with a neighbor report element as described above, it can be configured as follows, but is not limited thereto: Depending on the frame type / operation, a corresponding configuration field may not be included.

[0458] (1) Example of using the Neighbor Report (NR) element to indicate link-specific information

[0459] Fig.39 It is a diagram illustrating an embodiment of the NR element.

[0460] Each NR element indicates whether it is used for multilink (ML), or using Fig.39 The ML indication shown indicates whether it is used for ML in the order of the NR element (eg, "0011", where "1" is used for the NR element in ML). If this ML indication is included in the NR element, it is not necessarily included.

[0461] (2) Fields related to operations between the above links, such as indications regarding multi-link operations, may also be indicated as follows: The following information may be indicated by additionally using new elements in the BSSID information field reserved bits of this element or the above optional sub-elements.

[0462] 1) This can simply indicate whether the link is a link (eg, a selected operational link, a primary link).

[0463] Ex) Set to "1" if the link is selected for multi-link operation, and set to "0" otherwise.

[0464] Ex) If the link is prioritized over the main link for power saving, channel access, etc., it is set to "1", and otherwise it is set to "0".

[0465] 2) If the relationship is expressed in a multi-link operation manner with other links as in Example 2 explained above, it can be expressed in addition to itself.

[0466] Ex) If this neighbor report is for link 2, only the relationship with link 1 and link 3 is indicated. STR is indicated by "1", and non-STR is indicated by "0". The STR relationship between link 1 and link 2 and the STR relationship between link 3 and link 3 are indicated by "11".

[0467] 3) Example indicating whether a neighbor report element is used for multilink

[0468] Ex) It is set to "1" for multilink and set to "0" for legacy.

[0469] Since the above information should also be included in the link that sends these elements, EHT capability / operation elements or new elements should be defined and included.

[0470] If the neighbor report element is used to replace the multilink element as described above, it can be configured as the following example, but is not limited thereto.

[0471] Example 1: Link Selection

[0472] When a corresponding link, such as an operational link or a primary link, is selected for a certain operation / feature, it can be indicated with a bit.

[0473] Fig.40 is a diagram illustrating an embodiment of a method of instructing an operation link.

[0474] refer to Fig.40 , a neighbor element, not a multilink element, includes information related to link 2 and link 3 in order, and STA A requests link 1 and link 2 as operating links, and AP 1 responds to the request. In this case, "1" is indicated in the NR element of the link through which the element is being sent, and thus "1" is indicated for the NR element of link 2.

[0475] Fig.41 is a diagram illustrating an embodiment of a method for indicating a link set in a single BA protocol.

[0476] refer to Fig.41 , the neighbor element replaces the multilink element, includes information related to link 2 and link 3 in sequence, and STA A is negotiating with the AP to use BA for TID 1 in link 1 and link 2. In this case, the link set can be indicated by using a bitmap in the order of link 1 (transmission element), link 2, and link 3. Therefore, the STA A can indicate "110" to request the AP using the ADDBA frame, and the AP can confirm success as it is (using the bitmap "110").

[0477] Example 2: Example indicating STR ability

[0478] Fig.42 is a diagram illustrating an embodiment of a method of indicating STR capability.

[0479] refer to Fig.42 , information about link 2 and information about link 3 are included sequentially using NR elements, and can indicate STR capabilities for links 1 / 2 / 3 ("1" for STR, "0" for non-STR). For links other than itself, STA can indicate for each link in a pair. When indicated by the element for link 1, the first is "01" (link 1 and link 2, link 1 and link 3), thus indicating that link 1 and link 2 do not support STR, and link 1 and link 3 operate based on STR. For the NR element for link 2, it is set to "00", thus indicating that link 2 does not support STR for both link 1 and link 3. Finally, for the NR element for link 3, it is set to "10", thus indicating that link 3 has non-STR with link 2, and has STR with link 2.

[0480] 2. Reduced neighbor elements

[0481] The reduced neighbor element may include information related to several APs. Basically, since each neighbor AP information can include channel information and TBTT information, it can indicate a portion of the multilink element present above.

[0482] Fig.43 is a diagram illustrating an embodiment of reduced neighbor elements.

[0483] refer to Fig.43 , the information of the multi-link element can be indicated by partially modifying the reduced neighbor report element. The TBTT information field is present in the reduced neighbor report element, and through the indication of the TBTT information length field, the TBTT information field can have a field size of up to 255 octets. However, the reduced neighbor report element can be configured to be variable with sub-elements, but if the length is specified in the TBTT information length field and the TBTT information field is used to indicate the ML information, because the length is determined, there can be a problem of difficulty in indicating a variable value according to the number of links. In order to improve this, there may be a method of specifying it in the form of a range or specifying a maximum length value and indicating it therein.

[0484] 1) For traditional or for multi-link

[0485] First, in order to determine whether the information related to each neighbor AP is for legacy or for ML, a reserved bit of the TBTT information header or a TBTT information field may be used.

[0486] 2) EHT capability / operation element or reduced EHT capability / operation element (e.g., the multi-link element mentioned above)

[0487] If the size is determined, the (reduced) capability / operation element mentioned above can also indicate a length that matches the field size, but it is difficult to set the correct length because the relationship between links such as STR capabilities is variable. However, such variable fields are indicated separately, and this is possible if the TBTT information field is used for fixed fields. Next, Fig.44 is an example where the entire field consists of 20 octets.

[0488] Fig.44 It is a diagram illustrating an embodiment of TBTT information.

[0489] refer to Fig.44 , the TBTT information field may include multi-link information. There may be a reserved bit among the 20 octets, the operating link value is set to "1" and the main link value is set to "1", and the neighbor AP information including this field is the link information for ML, and is an example of selecting a link for ML operation and selecting as a main link.

[0490] Fig.45 is a diagram illustrating an embodiment of the format of the TBTT information field.

[0491] Referring to 45, the MLD ID may correspond to 1) for legacy or for multi-link mentioned above, and the link ID and the change sequence may correspond to link specific information. That is, through this field, it is possible to know whether it belongs to MLD and which MLD it belongs to. Basically, this information can be found through multi-link discovery, and the process of establishing multi-link settings with the MLD to which the AP performing discovery belongs is shown below.

[0492] Fig.46 and Fig.47 is a diagram illustrating an embodiment of a process of establishing a multi-link setup with an MLD to which an AP that has performed discovery belongs and a reduced neighbor report (RNR).

[0493] refer to Fig.46 and Fig.47, STA 1 of non-AP MLD can establish multi-link setup with the MLD to which the AP (AP 4) that has performed discovery belongs. Assuming that the ID of the MLD to which the AP that sends the RNR element belongs is "0", STA 1 can determine whether the APs (AP1, AP2, AP3) with MLD ID "0" belong to the same MLD as AP 4 that sends the RNR element. In addition, because each AP is distinguished by the link ID, it is possible to make a request by including the link ID in the association request frame. Another AP may belong to an MLD with the same MLD ID "3", and their link IDs can also be distinguished. At the same time, when performing multi-link setup with the other AP, the association request can be performed by moving to the corresponding channel with information related to the AP of the corresponding MLD ID.

[0494] Fig.48 is a flow chart illustrating an embodiment of a method of operating a send MLD.

[0495] refer to Fig.48 , sending MLD can generate a multilink element (S4810). For example, the multilink element may include a multilink control field, a common information / information field, and a link information / information field. In addition, the multilink control field may include a first existence field related to the existence of the link quantity field, and the common information field may include a link quantity field based on the first existence field.

[0496] For example, the link information field includes a per-STA control field for each station (STA), the per-STA control field includes a second presence field related to the presence / absence of a TID to link mapping field, and the link information field may further include a TID to link mapping field based on the second presence field. The TID link mapping field may include information related to the TID assigned to each link.

[0497] For example, the link information field may include a per-STA control field, the per-STA control field may include a third presence field related to the presence / absence of a simultaneous transmit and receive (STR) capability field, the link information field may further include an STR capability field based on the third presence field, and the STR capability field may include information related to whether each link supports STR.

[0498] For example, the number of links field may include information regarding the number of links through which the transmitting MLD can simultaneously perform physical protocol data unit (PPDU) exchanges.

[0499] For example, a multi-link element may be sent via an associated link, the multi-link control field may further include a fourth presence field related to the presence / absence of an associated link information field, the common information field may further include an associated link information field based on the fourth presence field, and the associated link information field may include a link identifier (ID) subfield and a TID to link mapping field.

[0500] For example, the size of the TID to Link Mapping field may be determined based on the Number of Links field.

[0501] Number of Links Supported: This indicates the total number of links supported.

[0502] Ex) When a bitmap is used and the total number of links is set to "3", the above content can be set to "11" if the associated link is included, and set to "10" if it is not included.

[0503] The number of links supported may mean the number of APs that can simultaneously exchange data frames (and / or management frames) through AP MLD, and the number of non-AP STAs that can simultaneously exchange data frames through non-AP MLD. The technical effect obtained by indicating this value in the multi-link (ML) element will be described separately in the presence field below.

[0504] The multilink element may include a link number field, a link specific information field, and an indication field regarding ML operation. The link specific information field may include an ID, channel information, auxiliary information, and capability fields.

[0505] The multilink element can be applied in the following examples.

[0506] Example 1: Example for indicating a link set

[0507] When requesting / responding to an operation link and determining the above-mentioned main link, a multi-link element can be used.

[0508] It can be indicated in the form of a bitmap by using the order of the indicated links.

[0509] The multilink element includes information about link 2 and link 3 in order, STA A requests link 1 and link 2 as operation links, and AP 1 responds to the request. In this case, the link set can be indicated in the order of link 1 (transmission element), link 2, and link 3 by using a bitmap. Therefore, STA A can request AP by indicating a bitmap of "110", and AP can confirm the bitmap of "110".

[0510] Example 2: Example indicating STR ability

[0511] The multilink element includes information about link 2 and link 3 in sequence and may indicate the STR capabilities of links 1 / 2 / 3.

[0512] In the first example, the multilink element includes information that link 1 and link 2 operate based on STR, and information that link 2 and link 3 operate based on STR(1), so information that links 1 and 3 can also operate based on STR can be included.

[0513] The second example is an example in which the multilink element is indicated for all pairs, and assuming that the pair order is set to {link 1 and link 2}, {link 1 and link 3}, and {link 2 and link 3}, it is possible to include information that all pairs operate based on STR (1).

[0514] Example 3: Example indicating TID to link mapping

[0515] The multilink element includes information about Link 2 and Link 3 in sequence, and shows TID to link mapping using a bitmap starting / considering Link 1 as the associated link.

[0516] The figure on the left is an example of a bitmap of links to which each TID is assigned. For example, if "110" is indicated for TID 0, it means that TID 0 is assigned to link 1 and link 2. The figure on the right is an example of a bitmap of TIDs assigned to each link, and the link order is the same as indicated in the link specific information. For example, if "001111111" is indicated for link 1, it means that TIDs 2 to 7 are assigned to link 1. Although the methods of the left and right figures are different, the signaling overhead is the same.

[0517] The multilink element includes information about Link 2 and Link 3 in sequence, and shows TID to link mapping using a bitmap starting / considering Link 1 as the associated link.

[0518] In order to reduce signaling overhead, two TIDs are bundled / grouped for each AC, and when "111" is indicated for TID 1 / 2 (ie, AC_BK), it means that all links are allocated for TID 1 and TID 2.

[0519] Examples of allowing dynamic indications

[0520] The above-mentioned field may predefine a field that can be omitted for each AP MLD or non-AP MLD or frame. Alternatively, without defining this, it may be dynamically determined whether the field exists by using 1 bit in front of the above-mentioned field. In the present disclosure, this field may be referred to as an existence field.

[0521] The multilink element is basically composed of common information and link information. The common information includes common information among STAs in MLD, and the link information includes specific information for each link (STA / AP) through each STA profile. The existence field can exist for common information and link information respectively. Common information can be present in the multilink control field, and link information can be present in each STA control field included in each STA profile. As mentioned above, these existence fields can determine whether to include information according to the type (type subfield of the multilink control field), purpose and process of the multilink element. In this way, it is possible to avoid including unnecessary information and have a compact ML IE format suitable for various purposes. Examples in this regard may be as follows.

[0522] Field #1 exists: TID to link mapping

[0523] For example, if a preceding bit of the TID to Link Mapping field (ie, the TID to Link Mapping Exists field) indicates '1', this field exists, and if '0' indicates this field, it does not exist.

[0524] If the TID to link mapping is in the common information, the presence or absence may be indicated by the TID to link mapping presence subfield of the multilink control field. If the value of the presence subfield is "1", the TID to link mapping field is present in the common information field. Basically, TID to link mapping is the default operation and does not require separate signaling, and because all TIDs are defined to be mapped to all links, the presence field may be useful if separate signaling is required.

[0525] Similarly, the presence or absence may be indicated by the TID to Link Mapping Present subfield of the Per-STA Control field. If the value of this subfield is "1", the TID to Link Mapping field is present in the Per-STA profile.

[0526] If the TID-to-link mapping for all configured links is indicated by a presence field in the common information and implicitly indicated in the order of the link IDs, it may be possible to reduce the overhead of including sub-element IDs, link IDs, full profiles, etc. in the link information by default (e.g., Fig.30 ). However, in each STA profile (e.g., Fig.31 ), only a part of a specific link may be indicated by the link ID, and in this case, the number of links to be indicated may be required in the common information. In addition, if the TID to link mapping is always carried with other information, the link information capable of indicating the information for each link by the link ID may be appropriate in position.

[0527] Existence Field #2: STR Ability

[0528] For example, if "1" is indicated in front of the STR capability, this field exists, and if "0" is indicated, this field does not exist.

[0529] If the STR capability is in the common information, the presence or absence may be indicated by the STR capability presence subfield of the multi-link control field. If the value of the presence subfield is "1", the STR capability field may be present in the common information field. If the MLD (e.g., AP MLD) operates based on STR for all link pairs by default, separate signaling may not be required. Therefore, if there are link pairs that do not operate based on STR, this presence field may be useful.

[0530] When the STR capability is indicated in the link information instead of the common information, an example of the presence field is shown. Similarly, the presence or absence can be indicated by the STR capability presence subfield of the per-STA control field. If the value of this subfield is "1", the STR capability field is present in the per-STA profile. In this STR capability, based on the link corresponding to each STA, only the pair with other links is indicated. For example, if link 2 is the standard for each STA, the STR capability of the pair of link 2 and link 1 and the pair of link 2 and link 3 are indicated.

[0531] If the STR capability for all links is indicated by a presence field in the common information and is implicitly indicated in the order of link ID, sub-element ID, link ID, full profile that is included in the link information by default (as shown in Example 2), the overhead may be reduced. In addition, in the link information, redundancy may appear when viewed as a whole. (For example, {link #1, link #2} and {link #2, link #1}. However, if this capability is indicated only when there is a non-STR-operated (NSTR) link pair, it may be difficult to distinguish the pairs in the common information. Therefore, the method of indicating by the presence field in the link information may be appropriate.

[0532] Field #3 exists: Information related to the associated link (i.e., sending STA)

[0533] This may indicate the presence or absence of information related to the above-mentioned associated link, ie, the link (STA) that transmits the ML element.

[0534] Because the information related to the STA sending the ML element is included in the management (Mgmt) frame (e.g., beacon, probe response frame) including the multi-link element, most of the information may not be included in the ML element alone. However, if it is not always included in the Mgmt frame (e.g., change sequence, link ID) or the STA requests partial information instead of complete information, it may be included in the ML element. If this information is included in the per-STA profile of the link information, a separate presence field is not required because the link ID is indicated and can already be identified. However, in order to reduce the default overhead of the link information mentioned above, the presence field may be included when included in the common information. In addition, if the above information exists because the presence field has a value of "1", the information related to the sending STA can have one format.

[0535] The presence or absence may be indicated by the information presence subfield of the transmitting STA of the multi-link control field. If the value of the presence subfield is "1", the information field of the transmitting STA exists in the common information field. Link ID, change sequence, etc. may be indicated in the information of the transmitting STA, and may include additional requested information, but is not limited thereto.

[0536] Field #4 exists: Example indicating information related to the number of links

[0537] This information refers to the number of links supported in 1) mentioned above.

[0538] The number of supported links indicates the number of APs that can simultaneously exchange data frames (and / or management frames) for the AP MLD, and the number of non-AP STAs that can simultaneously exchange data frames (and / or management frames) for the non-AP MLD.

[0539] Depending on the Mgmt frame and its purpose, this information may be present, that is, it may be present when the signaling affected by this information is present in the ML element. In addition, this information may not be present when the signaling affected by this information is not present. Therefore, the presence field may be present.

[0540] The presence may be indicated by the Link Quantity subfield of the Multilink Control field. If the value of this subfield is "1", the Link Quantity field is present in the common information.

[0541] If information related to all STAs (links) in the MLD is always included, the number of links can be inferred from the number of per-STA profiles. However, this presence field may be necessary because there are some situations where it may not be (for example, when information about only some links is requested, or when information about all STAs is not always included in the case of association). In addition, because it is possible to determine whether to include a field affected by the number of links based on the type of management frame including the ML element and the purpose of the ML element, the link number presence field may be required. For example, in a non-AP MLD, when information related to the link to be received from the AP is not yet known, such as when a probe request frame is sent during an initial scan, as mentioned above, because signaling for STR capabilities or TID to link mapping affected by the number of links may not be performed, the link number field may not be required. However, if the MLD knows the link information, such as when sending an association request frame, and signaling for STR capabilities or TID to link mapping is required, the link number is necessary. Therefore, the link number can be dynamically indicated by the presence field.

[0542] The signaling affected by the Number of Links field and the effects of this information are as follows.

[0543] TID to link mapping and STR capabilities

[0544] As mentioned in the presence fields #1 and #2 above, the field sizes of TID to link mapping and STR capability may vary depending on the number of links. That is, if a TID bitmap is used in TID to link mapping, the number of TID bitmaps varies according to the number of links, and if STR is indicated in pairs in STR capability, the number of pairs varies according to the number of links. Therefore, the number of links can affect the size of these fields.

[0545] Sending the MLD may send a multi-link element (S4820).

[0546] The transmitting MLD may transmit an RNR element (S4830). For example, the RNR element may include a target beacon transmission time (TBTT) information field, and the TBTT information field may include information about a link through which the RNR element is transmitted.

[0547] The information of the multi-link element can be indicated by partially modifying the reduced neighbor report element. The TBTT information field is present in the reduced neighbor report element, and through the indication of the TBTT information length field, the TBTT information field can have a field size of up to 255 octets. However, the reduced neighbor report element can be configured to be variable with sub-elements, but if the length is specified in the TBTT information length field and the TBTT information field is used to indicate the ML information, because the length is determined, there may be a problem that it is difficult to indicate a variable value according to the number of links. In order to improve this, there may be a method of specifying or specifying a maximum length value in the form of a range and indicating it therein.

[0548] 1) For traditional or for multi-link

[0549] First, in order to determine whether the information associated with each neighbor AP is for legacy or ML, a reserved bit of the TBTT information header or a TBTT information field may be used.

[0550] 2) EHT capability / operation element or reduced EHT capability / operation element (e.g., the multi-link element mentioned above)

[0551] If the size is determined, the (reduced) capability / operation element mentioned above can also indicate a length that matches the field size, but it is difficult to set the correct length because the relationship between links such as STR capabilities is variable. However, such variable fields are indicated separately, and this is possible if the TBTT information field is used for fixed fields.

[0552] The TBTT information field may include multi-link information. There may be a reserved bit among the 20 octets, the operating link value is set to "1" and the main link value is set to "1", and the neighbor AP information including this field is the link information for ML, and is an example of selecting a link for ML operation and selecting as a main link.

[0553] MLD ID can correspond to 1) for legacy or for multi-link mentioned above, and link ID and change sequence can correspond to link specific information. That is, through this field, it can be known whether it belongs to MLD and which MLD it belongs to.

[0554] Fig.49 is a flow chart illustrating an embodiment of a receive MLD method of operation.

[0555] refer to Fig.49, the receiving MLD may receive a multilink element (S4910). For example, the multilink element may include a multilink control field, a common information / information field, and a link information / information field. Also, the multilink control field may include a first presence field associated with the presence of a link quantity field, and the common information field may include a link quantity field based on the first presence field.

[0556] For example, the link information field includes a per-STA control field for each station (STA), the per-STA control field includes a second presence field related to the presence / absence of a TID to link mapping field, and the link information field may further include a TID to link mapping field based on the second presence field. The TID link mapping field may include information related to the TID assigned to each link.

[0557] For example, the link information field may include a per-STA control field, the per-STA control field may include a third presence field related to the presence / absence of a simultaneous transmit and receive (STR) capability field, the link information field may further include an STR capability field based on the third presence field, and the STR capability field may include information related to whether each link supports STR.

[0558] For example, the number of links field may include information regarding the number of links through which the transmitting MLD can simultaneously perform physical protocol data unit (PPDU) exchanges.

[0559] For example, a multi-link element may be sent via an associated link, the multi-link control field may further include a fourth existence field related to the presence / absence of an associated link information field, the common information field may further include an associated link information field based on the fourth existence field, and the associated link information field may include a link identifier (ID) subfield and a change sequence subfield.

[0560] For example, the size of the TID to Link Mapping field may be determined based on the Number of Links field, among others.

[0561] Number of Links Supported: This indicates the total number of links supported.

[0562] Ex) When a bitmap is used and the total number of links is set to "3", the above content can be set to "11" if the associated link is included, and set to "10" if it is not included.

[0563] The number of supported links may mean the number of APs that can simultaneously exchange data frames (and / or management frames) through AP MLD and the number of non-AP STAs that can simultaneously exchange data frames through non-AP MLD. The technical effect obtained by indicating this value in the multi-link (ML) element will be described separately in the presence field below.

[0564] The multilink element may include a link number field, a link specific information field, and an indication field regarding ML operation. The link specific information field may include an ID, channel information, auxiliary information, and capability fields.

[0565] The multilink element can be applied in the following examples.

[0566] Example 1: Example for indicating a link set

[0567] When requesting / responding to an operation link and determining the above-mentioned main link, a multi-link element can be used.

[0568] The order of using the indicated links can be indicated in the form of a bitmap.

[0569] The multilink element includes information about link 2 and link 3 in order, STA A requests link 1 and link 2 as operating links, and AP 1 responds to the request. In this case, a bitmap can be used to indicate a link set in the order of link 1 (transmission element), link 2, and link 3. Therefore, STA A can request AP by indicating a bitmap of "110", and AP can confirm the bitmap of "110".

[0570] Example 2: Example indicating STR ability

[0571] The multilink element includes information about link 2 and link 3 in sequence and may indicate the STR capabilities for links 1 / 2 / 3.

[0572] In the first example, the multilink element includes information that link 1 and link 2 operate based on STR and information that link 2 and link 3 operate based on STR(1), so information that links 1 and 3 can also operate based on STR can be included.

[0573] The second example is an example in which the multilink element is indicated for all pairs, and assuming that the pair order is set to {link 1 and link 2}, {link 1 and link 3}, and {link 2 and link 3}, it is possible to include information that all pairs operate based on STR (1).

[0574] Example 3: Example indicating TID to link mapping

[0575] The multilink element includes information about Link 2 and Link 3 in sequence, and shows TID to link mapping using a bitmap starting / considering Link 1 as the associated link.

[0576] The figure on the left is an example of a bitmap of links to which each TID is assigned. For example, if "110" is indicated for TID 0, it means that TID 0 is assigned to link 1 and link 2. The figure on the right is an example of a bitmap of TIDs assigned to each link, and the link order is the same as indicated in the link specific information. For example, if "001111111" is indicated for link 1, it means that TIDs 2 to 7 are assigned to link 1. Although the methods of the left and right figures are different, the signaling overhead is the same.

[0577] The multilink element includes information about Link 2 and Link 3 in sequence, and shows TID to link mapping using a bitmap starting / considering Link 1 as the associated link.

[0578] In order to reduce signaling overhead, two TIDs are bundled / grouped for each AC, and when "111" is indicated for TID 1 / 2 (ie, AC_BK), it means that all links are allocated for TID 1 and TID 2.

[0579] Examples of allowing dynamic indications

[0580] The above-mentioned field may predefine a field that can be omitted for each AP MLD or non-AP MLD or frame. Alternatively, without defining this, it is possible to dynamically determine whether the field exists by using 1 bit in front of the above-mentioned field. In the present disclosure, this field may be referred to as an existence field.

[0581] The multilink element is basically composed of common information and link information. Common information includes common information among STAs in MLD, and link information includes specific information for each link (STA / AP) through each STA profile. There are fields that can exist for common information and link information respectively. Common information can be present in the multilink control field, and link information can be present in each STA control field included in each STA profile. As mentioned above, these fields can determine whether to include information according to the type (type subfield of the multilink control field), purpose and process of the multilink element. In this way, it is possible to avoid including unnecessary information and have a compact ML IE format suitable for various purposes. Examples in this regard may be as follows.

[0582] Field #1 exists: TID to link mapping

[0583] For example, if a preceding bit of the TID to Link Mapping field (ie, the TID to Link Mapping Exists field) indicates '1', this field exists, and if '0' indicates this field, it does not exist.

[0584] If the TID to link mapping is in the common information, the presence or absence can be indicated by the TID to link mapping presence subfield of the multi-link control field. If the value of the presence subfield is "1", the TID to link mapping field is present in the common information field. Basically, TID to link mapping is the default operation and does not require separate signaling, and because all TIDs are defined to be mapped to all links, the presence field may be useful if separate signaling is required.

[0585] Similarly, the presence or absence may be indicated by the TID to Link Mapping Present subfield of the Per-STA Control field. If the value of this subfield is "1", the TID to Link Mapping field is present in the Per-STA profile.

[0586] If the TID to link mapping for all setup links is indicated by a presence field in the common information and implicitly indicated by the order of the link IDs, it may be possible to reduce the overhead of including sub-element IDs, link IDs, full profiles, etc. in the link information by default (e.g., Fig.30 ). However, in each STA profile (e.g., Fig.31 ), only a part of a specific link may be indicated by the link ID, and in this case, the number of links to be indicated may need to be in the common information. In addition, if the TID to link mapping is always carried with other information, the link information that can indicate the information for each link by the link ID may be appropriate in position.

[0587] Existence Field #2: STR Ability

[0588] For example, if "1" is indicated in front of the STR capability, this field exists, and if "0" is indicated, this field does not exist.

[0589] If the STR capability is in the common information, the presence or absence may be indicated by the STR capability presence subfield of the multi-link control field. If the value of the presence subfield is "1", the STR capability field may be present in the common information field. If the MLD (e.g., AP MLD) operates based on STR for all link pairs by default, separate signaling may not be required. Therefore, if there are link pairs that do not operate based on STR, this presence field may be useful.

[0590] When the STR capability is indicated in the link information instead of the common information, an example of the presence field is shown. Similarly, the presence or absence can be indicated by the STR capability presence subfield of the per-STA control field. If the value of this subfield is "1", the STR capability field is present in the per-STA profile. In this STR capability, based on the link corresponding to each STA, only the pair with other links is indicated. For example, if link 2 is the standard for each STA, the STR capability of the pair of link 2 and link 1 and the pair of link 2 and link 3 are indicated.

[0591] If the STR capability for all links is indicated through the presence field in the common information and the pairs are implicitly indicated in the order of link ID, sub-element ID, link ID, full profile included in the link information by default (as shown in Example 2), the overhead may be reduced. In addition, redundancy may appear in the link information as a whole. (For example, {link #1, link #2} and {link #2, link #1}. However, if this capability is indicated only when there is a link pair that is not based on STR operation (NSTR), it may be difficult to distinguish the pairs in the common information. Therefore, the method of indicating through the presence field in the link information may be appropriate.

[0592] Field #3 exists: Information related to the associated link (i.e., sending STA)

[0593] This may indicate the presence or absence of information related to the above-mentioned associated link, ie, the link (STA) that sent the ML element.

[0594] Because the information related to the STA sending the ML element is included in the management (Mgmt) frame (e.g., beacon, probe response frame) including the multi-link element, most of the information may not be included in the ML element separately. However, if it is not always included in the Mgmt frame (e.g., change sequence, link ID) or the STA requests partial information instead of complete information, it may be included in the ML element. If this information is included in the per-STA profile of the link information, a separate presence field is not required because the link ID is indicated and can already be identified. However, in order to reduce the default overhead of the link information mentioned above, the presence field may be included when included in the common information. In addition, if the above information exists because the presence field has a value of "1", the information related to the sending STA may have one format.

[0595] The presence or absence may be indicated by the information presence subfield of the transmitting STA of the multi-link control field. If the value of the presence subfield is "1", the information field of the transmitting STA exists in the common information field. Link ID, change sequence, etc. may be indicated in the information of the transmitting STA, and may include additional requested information, but is not limited thereto.

[0596] Field #4 exists: Example indicating information related to the number of links

[0597] This information refers to the number of links supported in 1) mentioned above.

[0598] The number of supported links indicates the number of APs that can simultaneously exchange data frames (and / or management frames) for the AP MLD and the number of non-AP STAs that can simultaneously exchange data frames (and / or management frames) for the non-AP MLD.

[0599] Depending on the Mgmt frame and its purpose, this information may be present, that is, it may be present when the signaling affected by this information is present in the ML element. In addition, this information may not be present when the signaling affected by this information is not present. Therefore, the presence field may be present.

[0600] The presence may be indicated by the Link Quantity subfield of the Multilink Control field. If the value of this subfield is "1", the Link Quantity field is present in the common information.

[0601] If information related to all STAs (links) in the MLD is always included, the number of links can be inferred from the number of per-STA profiles. However, this presence field may be necessary because there are some situations where it may not be (for example, when information about only some links is requested, or when information about all STAs is not always included in the case of association). In addition, because it is possible to determine whether to include a field affected by the number of links based on the type of management frame including the ML element and the purpose of the ML element, the link number presence field may be required. For example, in a non-AP MLD, when information related to the link to be received from the AP is not yet known, such as when a probe request frame is sent during an initial scan, as mentioned above, because signaling for STR capabilities or TID to link mapping affected by the number of links may not be performed, the link number field may not be required. However, if the MLD knows the link information, such as when sending an association request frame, and signaling for STR capabilities or TID to link mapping is required, the link number is necessary. Therefore, the link number can be dynamically indicated by the presence field.

[0602] The signaling affected by the Number of Links field and the effects of this information are as follows.

[0603] TID to link mapping and STR capabilities

[0604] As mentioned in the presence fields #1 and #2 above, the field sizes of the TID to link mapping and the STR capability may vary depending on the number of links. That is, if a TID bitmap is used in the TID to link mapping, the number of TID bitmaps varies according to the number of links, and if the STR is indicated in pairs in the STR capability, the number of pairs varies according to the number of links. Therefore, the number of links can affect the size of these fields.

[0605] The receiving MLD may decode the multilink element (S4920).

[0606] The receiving MLD may receive the RNR element (S4930). For example, the RNR element may include a target beacon transmission time (TBTT) information field, and the TBTT information field may include information about the link through which the RNR element is transmitted.

[0607] The information of the multi-link element can be indicated by partially modifying the reduced neighbor report element. The TBTT information field is present in the reduced neighbor report element, and through the indication of the TBTT information length field, the TBTT information field can have a field size of up to 255 octets. However, the reduced neighbor report element can be configured to be variable with sub-elements, but if the length is specified in the TBTT information length field and the TBTT information field is used to indicate the ML information, because the length is determined, there may be a problem that it is difficult to indicate a variable value according to the number of links. In order to improve this, there may be a method of specifying or specifying a maximum length value in the form of a range and indicating it therein.

[0608] 1) For traditional or for multi-link

[0609] First, in order to determine whether the information associated with each neighbor AP is for legacy or ML, a reserved bit of the TBTT information header or a TBTT information field may be used.

[0610] 2) EHT capability / operation element or reduced EHT capability / operation element (e.g., the multi-link element mentioned above)

[0611] If the size is fixed, the (reduced) capability / operation element mentioned above can also indicate a length that matches the field size, but it is difficult to set the correct length because the relationship between links such as STR capabilities is variable. However, such variable fields are indicated separately, and this is possible if the TBTT information field is used for fixed fields.

[0612] The TBTT information field may include multi-link information. There may be a reserved bit among the 20 octets, the operating link value is set to "1" and the main link value is set to "1", and the neighbor AP information including this field is the link information for ML, and is an example of selecting a link for ML operation and selecting as a main link.

[0613] MLD ID can correspond to 1) for legacy or for multi-link mentioned above, and link ID and change sequence can correspond to link specific information. That is, through this field, it can be known whether it belongs to MLD and which MLD it belongs to.

[0614] exist Fig.48 and Fig.49 Some of the detailed steps shown in the examples may not be necessary steps and may be omitted. Fig.48 and 49 In addition to the steps shown in , other steps can be added, and the order of the steps can be changed. Only part of the above steps has its independent technical significance.

[0615] The technical features of the present specification described above can be applied to various devices and methods. Figure 1 and / or Fig.19 For example, the above technical features of this specification may only be applied to Figure 1 and / or Fig.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 may be implemented based on Fig.19 The processor 610 and the memory 620 of the embodiment are implemented. For example, a receiving multi-link device (MLD) in a wireless local area network (WLAN) system may include: 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 process 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.

[0616] 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, which are based on being executed by at least one processor of a receiving multi-link device (MLD) in a wireless local area network system to perform operations, wherein 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 sending MLD; and the first STA sends 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.

[0617] 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 in this specification can be Figure 1 The processor 111 and / or 121 or the processing chip 114 and / or 124, or Fig.19 The processor 610 of this specification can also be Figure 1 Memory 112 and / or 122, Fig.19 memory 620, or a separate external memory / storage medium / disk.

[0618] 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 supporting artificial intelligence (AI).

[0619] Artificial intelligence refers to the field of study regarding artificial intelligence or methods of creating artificial intelligence, while machine learning refers to the field of study regarding methods of defining and solving various problems in the field of artificial intelligence. Machine learning is also defined as algorithms that improve the performance of operations through stable experience of operations.

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

[0621] The 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 neurons. In the 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 a synapse.

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

[0623] 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 learning an artificial neural network.

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

[0625] Supervised learning refers to a method of 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 to the artificial neural network. Unsupervised learning may refer to a method of training an artificial neural network when no labels are given for training data. Reinforcement learning may refer to a training method of an agent defined in a training environment to select actions or action sequences to maximize the cumulative reward in each state.

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

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

[0628] A robot may 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 may be referred to as an intelligent robot.

[0629] Robots can be classified into industrial, medical, household, military robots, etc. according to their uses or fields. Robots can include actuators or drives, which include motors to perform various physical operations (e.g., move 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 through the drive.

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

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

[0632] 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 equal.

[0633] XR technology may be applied to head mounted displays (HMDs), heads 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.

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

Claims

1. A method in a wireless local area network (WLAN) system, the method comprising: generating an association request frame including a multilink element, The multilink element includes a multilink control field, a common information field and a link information field. wherein the multilink control field has a length of two octets, wherein the multi-link control field comprises a first presence field having a length of 1 bit, wherein the first presence field is related to the presence of a subfield in the common information field, wherein the subfield is related to the number of links and has a length of 4 bits, Wherein, the public information field further includes a multi-link device media access control MLD MAC address subfield; and The association request frame is sent.

2. The method according to claim 1, further comprising: A reduced neighbor report RNR element is sent, wherein the RNR element includes a target beacon transmission time TBTT information field, and the TBTT information field includes an AP MLD ID subfield identifying an access point multi-link device AP MLD and a link ID subfield identifying a link of an AP within the AP MLD.

3. The method according to claim 1, wherein: The link information field includes a per-STA control field, wherein the per-STA control field includes a second presence field associated with the presence of a service identifier to link, TID to link, mapping field, wherein the link information field further includes the TID to link mapping field based on the second presence field, The TID-to-link mapping field includes information related to the TID assigned to each link.

4. The method according to claim 1, wherein: The subfield includes information related to the number of links through which the AP MLD can simultaneously perform physical protocol data unit PPDU exchange.

5. The method according to claim 1, wherein: When the subfield related to the number of links exists in the common information field, the first existence field is set to.

6. A device in a wireless local area network system, comprising a transceiver configured to transmit and / or receive wireless signals; and a processor coupled to the transceiver, in, The processor is configured to: generating an association request frame including a multilink element, The multilink element includes a multilink control field, a common information field and a link information field. wherein the multilink control field has a length of two octets, wherein the multi-link control field comprises a first presence field having a length of 1 bit, wherein the first presence field is related to the presence of a subfield in the common information field, wherein the subfield is related to the number of links and has a length of 4 bits, Wherein, the public information field further includes a multi-link device media access control MLD MAC address subfield; and The association request frame is sent.

7. The device according to claim 6, wherein: The processor is further configured to: execute the steps of the method according to any one of claims 2 to 5.

8. A method for use in a wireless local area network (WLAN) system, the method comprising: receiving an association request frame including a multilink element, The multilink element includes a multilink control field, a common information field and a link information field. wherein the multilink control field has a length of two octets, The multi-link control field includes a first presence field of 1 bit in length, wherein the first presence field is related to the presence of a subfield in the common information field, wherein the subfield is related to the number of links and has a length of 4 bits, The public information field further includes a multi-link device media access control MLD MAC address subfield.

9. A device in a wireless local area network system, comprising a transceiver configured to transmit and / or receive wireless signals; and a processor coupled to the transceiver, in, The processor is configured to: receiving an association request frame including a multilink element, The multilink element includes a multilink control field, a common information field and a link information field. wherein the multilink control field has a length of two octets, wherein the multi-link control field comprises a first presence field having a length of 1 bit, wherein the first presence field is related to the presence of a subfield in the common information field, wherein the subfield is related to the number of links and has a length of 4 bits, The public information field further includes a multi-link device media access control MLD MAC address subfield.

10. The device according to claim 13, wherein: The processor is further configured to perform the steps of a method according to any one of claims 2 to 5.

Images