Wireless communication method using multi-link and wireless communication terminal using the same

Abstract

To provide a wireless communication method using a multilink and a wireless communication terminal using the same.SOLUTION: The present invention discloses a channel switching method and device, the method performed by a multi-link device (MLD) comprising a plurality of stations, which respectively operate in a plurality of links, in a wireless communication system. Particularly, the MLD of the present invention may: receive a frame comprising channel switching information for channel switching from a first AP of a primary link from among the plurality of links; and determine whether or not channel switching is to be performed for a station connected to a second AP by means of one subsidiary link, on the basis of the channel switching information.SELECTED DRAWING: Figure 20

Description

[Technical field]

[0001] The present invention relates to a wireless communication method using multilinks and a wireless communication terminal using the same. [Background technology]

[0002] Recently, as the use of mobile devices has become more widespread, wireless LAN technology that can provide them with high-speed wireless Internet services has been attracting attention. Wireless LAN technology is a technology that enables mobile devices such as smartphones, smart pads, laptop PCs, portable multimedia players, embedded devices, etc. to wirelessly connect to the Internet at home, in business, or in specific service areas based on short-distance wireless communication technology.

[0003] Since IEEE (Institute of Electronics Engineers) 802.11 supported early wireless LAN technology using 2.4GHz frequency, it has put into practical use or is currently developing standards for various technologies. First, IEEE 802.11b uses the 2.4GHz frequency band and supports a maximum communication speed of 11Mbps. IEEE 802.11a, which was commercialized after IEEE 802.11b, uses the 5GHz frequency band instead of the 2.4GHz band, reducing the impact of interference compared to the significantly more congested 2.4GHz frequency band, and uses OFDM technology to increase communication speeds to a maximum of 54Mbps. However, IEEE 802.11a has the disadvantage of a shorter communication distance than IEEE 802.11b. IEEE 802.11g, like IEEE 802.11b, uses the 2.4GHz band and achieves a maximum transmission speed of 54Mbps and satisfies backward compatibility, which has attracted considerable attention, but it also has an advantage over IEEE 802.11a in communication distance.

[0004] IEEE 802.11n is a technical standard established to overcome the communication speed limitations that have been pointed out as a weakness of wireless LAN. The purpose of IEEE 802.11n is to increase the speed and reliability of the network and to extend the operating distance of the wireless network. In detail, IEEE 802.11n supports a high throughput (HT) of up to 540Mbps or more in data processing speed, and is based on MIMO (Multiple Inputs and Multiple Outputs) technology that uses multiple antennas on both the transmitting and receiving ends to minimize transmission errors and optimize data speed. This standard also uses a coding method that transmits multiple duplicate copies to increase data reliability.

[0005] As the use of wireless LANs becomes more widespread and applications using them become more diverse, the need for new wireless LAN systems to support data throughput rates (Very High Throughput, VHT) higher than those supported by IEEE 802.11n is emerging. Among them, IEEE 802.11ac supports wide bandwidth (80MHz~160MHz) at 5GHz frequency. Although the IEEE 802.11ac standard is defined only in the 5GHz band, it is expected that initial 11ac chipsets will also support operation in the 2.4GHz band for backward compatibility with existing 2.4GHz band products. Theoretically, this standard allows multi-station wireless LAN speeds of at least 1Gbps and maximum single link speeds of at least 500Mbps. This is done by extending the air interface concepts accepted by 802.11n, such as wider radio frequency bandwidth (up to 160MHz), more MIMO spatial streams (up to 8), multi-user MIMO, and high density modulation (up to 256QAM). Also, there is IEEE 802.11ad, a method of transmitting data using the 60GHz band instead of the conventional 24GHz / 5GHz. IEEE 802.11ad is a transmission standard that uses beamforming technology to provide speeds of up to 7Gbps, and is suitable for streaming large amounts of data and high bitrate videos such as uncompressed HD video. However, the 60GHz frequency band has the disadvantage that it is difficult to pass through obstacles and can only be used between devices in close proximity.

[0006] Meanwhile, the IEEE 802.11ax (High Efficiency WLAN, HEW) standard is being developed and is in the final stages as the WLAN standard after 802.11ac and 802.11ad to provide high-efficiency and high-performance WLAN communication technology in high-density environments where APs and terminals are densely packed. In an 802.11ax-based WLAN environment, it is necessary to provide high-frequency efficient communication indoors / outdoors in the presence of high density stations and APs (Access Points), and various technologies are being developed to realize this.

[0007] In addition, new WLAN standards have begun to be developed to increase maximum transmission speeds to support new multimedia applications such as high-definition video and real-time games. IEEE 802.11be (Extremely High Throughput, EHT), the 7th generation WLAN standard, is currently being developed with the goal of supporting transmission rates of up to 30 Gbps through wider bandwidth in the 2.4 / 5 / 6 GHz bands, increased spatial streams, and multiple AP cooperation. Summary of the Invention [Problem to be solved by the invention]

[0008] An object of one embodiment of the present invention is to provide a wireless communication method using multilinks and a wireless communication terminal using the same.

[0009] Another object of the present invention is to provide a channel change method for a station and an AP using multilink.

[0010] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0011] A multi-link device (MLD) including a plurality of stations each operating on a plurality of links includes a processor, the processor receiving a frame including channel change information for a channel change from a first AP of a primary link among the plurality of links, the plurality of links being composed of one of the primary links and at least one non-primary link, the channel change information being used for a channel change of a second AP for one of the at least one secondary link, and determining whether to change a channel of a station connected to the second AP through the one secondary link based on the channel change information, and a field related to the timing of the channel change of the second AP included in the channel change information is set based on the first AP of the primary link.

[0012] In addition, in the present invention, the field related to the timing of the channel change of the second AP is set based on a target beacon transmission time (TBTT) and a beacon interval (BI) of the primary link to the first AP.

[0013] In addition, in the present invention, the field related to the timing of the channel change of the second AP includes a switch time field indicating the time interval from the time the channel change begins until the first frame is transmitted through the changed channel, and / or a channel switch count field indicating the number of TBTTs remaining until the channel change begins.

[0014] In addition, in the present invention, the switch time field is recognized based on the time when a beacon frame in which the value of the channel switch count field related to the channel change of the second AP is set to "1" or "0" is transmitted among the beacon frames transmitted from the first AP of the main link.

[0015] Also, in the present invention, if the value of the channel switch count field is 1, the channel change begins at the next TBTT of the first AP after the frame is transmitted, and if the value of the channel switch count field is 0, the channel change begins after the frame is transmitted.

[0016] In addition, in the present invention, the channel change information further includes a new channel number field indicating a number of a channel to be changed by the channel change.

[0017] In addition, in the present invention, the channel change information is included in at least one Per-STA profile sub-element included in the frame, and each of the at least one Per-STA profile sub-element includes information regarding other APs included in the same MLD.

[0018] In addition, in the present invention, the first AP and the second AP are non-simultaneous transmission and reception (NSTR) stations that do not support simultaneous transmission and reception within the same MLD.

[0019] Also, in the present invention, the processor performs a channel change of the station based on the channel change information, and receives a frame associated with the completion of the channel change from the first AP or the second AP.

[0020] In addition, in the present invention, when the processor does not change the channel of the station connected to the second AP through the one secondary link based on the channel change information, the processor re-establishes a link with the AP MLD including the first AP and the second AP so that the MLD is connected only to the primary link of the first AP.

[0021] The present invention also provides a method including the steps of: receiving a frame including channel change information for channel change from a first AP of a primary link among the plurality of links, the plurality of links being composed of one of the primary links and at least one non-primary link, and the channel change information being used for a channel change of a second AP for one of the at least one secondary link; and determining whether to perform a channel change of a station connected to the second AP through the one secondary link based on the channel change information, and a field related to timing of the channel change of the second AP included in the channel change information is set based on the first AP of the primary link. Effect of the Invention

[0022] An embodiment of the present invention provides a wireless communication method that efficiently uses multiple links and a wireless communication terminal that uses the same.

[0023] The effects obtained from the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 is a diagram showing a wireless LAN system according to an embodiment of the present invention. [Diagram 2] FIG. 11 is a diagram showing a wireless LAN system according to another embodiment of the present invention. [Diagram 3]FIG. 2 is a diagram showing a configuration of a station according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram showing the configuration of an access point according to an embodiment of the present invention. [Diagram 5] 1 is a diagram illustrating a process in which a STA sets up a link with an AP. [Figure 6] FIG. 1 is a diagram illustrating a CSMA (Carrier Sense Multiple Access) / CA (Collision Avoidance) method used in wireless LAN communication. [Figure 7] 1 shows examples of various standard generation PPDU (PLCP Protocol Data Unit) formats. [Figure 8] 1 illustrates an example of various Extremely High Throughput (EHT) Physical Protocol Data Unit (PPDU) formats and a method for indicating the same according to an embodiment of the present invention. [Figure 9] 1 illustrates a multi-link device according to an embodiment of the present invention. [Figure 10] 1 illustrates a multi-link operation in which transmissions on different links are performed simultaneously according to an embodiment of the present invention. [Figure 11] 1 illustrates an example of the contents of a beacon frame transmitted by an AP in AP MLD and a TBTT (target beacon transmission time) information field format included in an RNR (Reduced Neighbor Report) element according to one embodiment of the present invention. [Figure 12] 13 illustrates yet another example of a TBTT information field format according to an embodiment of the present invention. [Figure 13]13 illustrates an example of a TBTT information length subfield indicating a TBTT information field including an MLD AP TBTT offset subfield according to an embodiment of the present invention. [Figure 14] 1 illustrates an example of a Per-STA Profile subelement format according to an embodiment of the present invention. [Figure 15] 13 illustrates an example of a process in which a non-AP MLD set up with an NSTR (Non-Simultaneous Transmission and Reception) Soft AP MLD updates information on a non-primary link, according to one embodiment of the present invention. [Figure 16] 11 is a flowchart illustrating an example of a procedure in which a non-AP STA MLD associated with an NSTR AP MLD updates parameters of a non-primary link according to an embodiment of the present invention. [Figure 17] 1 illustrates an example of an element format according to an embodiment of the present invention. [Figure 18] 13 illustrates an example of a process in which an NSTR AP MLD sets (defines) a quiet interval for a non-primary according to an embodiment of the present invention. [Figure 19] 13 illustrates an example of a method for an NSTR AP MLD to perform a non-primary channel switch according to an embodiment of the present invention. [Figure 20] 11 is a flowchart illustrating an example of an operation of non-AP MLD according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] The terms used in this specification are selected as general terms that are currently widely used as much as possible in consideration of the functions of the present invention, but this may vary depending on the intentions, customs, or the emergence of new technologies of the engineers in the relevant technical field. In addition, in certain cases, the applicant may arbitrarily select terms, and in such cases, the meanings of the terms will be described in the description of the relevant invention. Therefore, it is clear that the terms used in this specification should be interpreted not simply as terms, but based on the substantial meanings of the terms and the contents of this specification as a whole.

[0026] Throughout the specification, when a certain component is "connected" to another component, this includes not only when it is "directly connected" to another component, but also when it is "electrically connected" with another component in between. Furthermore, when a certain component "includes" a specific component, this means that it may further include the other component, not excluding the other component, unless otherwise specified to the contrary. In addition, limitations such as "greater than" or "less than" based on a specific threshold value may be appropriately replaced with "greater than" or "less than" depending on the embodiment.

[0027] Hereinafter, in the present invention, the terms field and subfield may be used interchangeably.

[0028] FIG. 1 is a diagram showing a wireless LAN system according to an embodiment of the present invention.

[0029] A wireless LAN system includes one or more Basic Service Sets (BSS), which are a set of devices that can successfully synchronize and communicate with each other. Generally, BSSs are classified into infrastructure BSSs and independent BSSs (IBSSs), and Figure 1 shows an infrastructure BSS.

[0030] As shown in FIG. 1, infrastructure BSS BSS1, BSS2 includes one or more stations STA1, STA2, STA3, STA4, STA5, access points AP-1, AP-2 which are stations providing a distribution service, and a distribution system DS which connects multiple access points AP-1, AP-2.

[0031] A station (STA) is any device including a medium access control (MAC) and a physical layer interface for a wireless medium according to the IEEE 802.11 standard, and in a broad sense includes not only non-AP stations but also APs. In this specification, the term "terminal" refers to either a non-AP or an AP, or to both. A station for wireless communication includes a processor and a communication unit, and further includes a user interface unit and a display unit, etc., depending on the embodiment. The processor generates frames to be transmitted through a wireless network, processes frames received through the wireless network, and performs various other processes for controlling the station. The communication unit is functionally connected to the processor and transmits and receives frames through the wireless network for the station. In the present invention, the term "terminal" is used to include a user equipment (UE).

[0032] An access point (AP) is an entity that provides a connection to a distribution system DS via a wireless medium for a station associated therewith. In an infrastructure BSS, communication between non-AP stations is generally performed via the AP, but when a direct link is set up, direct communication is possible between non-AP stations. Meanwhile, in the present invention, AP is used as a concept including a personal BSS coordination point (PCP), but in a broad sense, AP includes all concepts such as a central controller, a base station (BS), a node B, a base transceiver system (BTS), or a site controller. In the present invention, AP is also referred to as a base wireless communication terminal, but in a broad sense, the base wireless communication terminal is used as a term including an AP, a base station, an eNodeB (eNB), and a transmission point TP. In addition, the base wireless communication terminal includes various types of wireless communication terminals that allocate communication medium resources and perform scheduling in communication with a plurality of wireless communication terminals.

[0033] A plurality of infrastructure BSSs are connected to each other via a distribution system DS. In this case, a plurality of BSSs connected to each other via the distribution system is called an Extended Service Set (ESS).

[0034] 2 is a diagram showing an independent BSS, which is a wireless LAN system according to another embodiment of the present invention, in which the same or corresponding parts in the embodiment of FIG. 2 are described in the same manner as in the embodiment of FIG.

[0035] BSS3 shown in Figure 2 is an independent BSS and does not include an AP, so all stations (STA6, STA7) are not connected to an AP. An independent BSS is not allowed to connect to a distribution system and forms a self-contained network. In an independent BSS, each station (STA6, STA7) is directly connected to each other.

[0036] 3 is a block diagram showing a configuration of a station 100 according to an embodiment of the present invention. As shown in the figure, the station 100 according to the embodiment of the present invention includes a processor 110, a communication unit 120, a user interface unit 140, a display unit 150, and a memory 160.

[0037] First, the communication unit 120 transmits and receives wireless signals such as wireless LAN packets, and may be built into or externally provided in the station 100. According to an embodiment, the communication unit 120 may include at least one communication module using different frequency bands. For example, the communication unit 120 may include communication modules of different frequency bands such as 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz. According to an embodiment, the station 100 may include a communication module using a frequency band of 7.125 GHz or more and a communication module using a frequency band of 7.125 GHz or less. Each communication module may perform wireless communication with an AP or an external station based on the wireless LAN standard of the frequency band supported by the communication module. The communication unit 120 may operate only one communication module at a time or operate multiple communication modules simultaneously according to the performance and requirements of the station 100. When the station 100 includes multiple communication modules, each communication module may be provided in an independent form, or multiple modules may be integrated into one chip. In an embodiment of the present invention, the communication unit 120 may represent a radio frequency (RF) communication module that processes RF signals.

[0038] Next, the user interface 140 includes various types of input / output means provided in the station 100. That is, the user interface unit 140 receives user input using various input means, and the processor 110 controls the station 100 based on the received user input. Also, the user interface unit 140 performs output based on a command from the processor 110 using various output means.

[0039] Then, the display unit 150 outputs an image on a display screen. The display unit 150 outputs various display objects such as a user interface based on the contents performed by the processor 110 or a control command of the processor 110. The memory 160 also stores control programs used by the station 100 and various data associated therewith. Such control programs include connection programs required for the station 100 to connect to an AP or an external station.

[0040] The processor 110 of the present invention executes various commands or programs to process data within the station 100. The processor 110 also controls each unit of the station 100 and controls transmission and reception of data between the units. According to an embodiment of the present invention, the processor 110 executes a program for connection to an AP stored in the memory 160 and receives a communication setup message transmitted by the AP. The processor 110 also reads information on the priority conditions of the station 100 included in the communication setup message and requests a connection to the AP based on the information on the priority conditions of the station 100. The processor 110 of the present invention may refer to a main control unit of the station 100, or may refer to a control unit for individually controlling some components of the station 100, for example, the communication unit 120, depending on the embodiment. That is, the processor 110 may be a modem that modulates and demodulates a wireless signal transmitted and received from the communication unit 120, or a modulator and / or demodulator. The processor 110 controls various operations of transmitting and receiving wireless signals of the station 100 according to an embodiment of the present invention. A detailed embodiment of the present invention will be described later.

[0041] The station 100 shown in FIG. 3 is a block diagram according to an embodiment of the present invention, and the separate blocks are used to logically distinguish between elements of the device. Thus, the above-mentioned device elements may be mounted on one chip or multiple chips depending on the design of the device. For example, the processor 110 and the communication unit 120 may be integrated and embodied on one chip, or may be embodied on separate chips. In addition, in an embodiment of the present invention, some components of the station 100, such as the user interface unit 140 and the display unit 150, may be selectively provided in the station 100.

[0042] 4 is a block diagram showing a configuration of an AP 200 according to an embodiment of the present invention. As shown in the figure, the AP 200 according to the embodiment of the present invention includes a processor 210, a communication unit 220, and a memory 260. In FIG. 4, a duplicated description of parts of the configuration of the AP 200 that are the same as or correspond to the configuration of the station 100 in FIG. 3 will be omitted.

[0043] Referring to FIG. 4, the AP 200 according to the present invention includes a communication unit 220 for operating a BSS in at least one frequency band. As described above in the embodiment of FIG. 3, the communication unit 220 of the AP 200 may also include a plurality of communication modules using different frequency bands. That is, the AP 200 according to the embodiment of the present invention may include two or more communication modules using different frequency bands, for example, any of 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz. Preferably, the AP 200 may include a communication module using a frequency band of 7.125 GHz or higher and a communication module using a frequency band of 7.125 GHz or lower. Each communication module may perform wireless communication with a station based on the WLAN standard of the frequency band supported by the communication module. The communication unit 220 may operate only one communication module at a time or operate multiple communication modules simultaneously according to the performance and requirements of the AP 200. In the embodiment of the present invention, the communication unit 220 may represent an RF communication module that processes RF (Radio Frequency) signals.

[0044] Next, the memory 260 stores control programs used in the AP 200 and various data associated therewith. Such control programs include a connection program for managing station connections. Also, the processor 210 controls each unit of the AP 200 and controls transmission and reception of data between the units. According to an embodiment of the present invention, the processor 210 executes a program for connection with a station stored in the memory 260 and transmits a communication setting message to one or more stations. At this time, the communication setting message includes information regarding connection priority conditions of each station. Also, the processor 210 performs connection setting in response to a connection request of a station. According to an embodiment, the processor 210 is a modem or a modulation / demodulation unit that modulates and demodulates wireless signals transmitted and received from the communication unit 220. The processor 210 controls various operations of transmitting and receiving wireless signals of the AP 200 according to an embodiment of the present invention. A detailed embodiment thereof will be described later.

[0045] FIG. 5 is a diagram illustrating a process in which a STA establishes a link with an AP.

[0046] 5, the link between the STA 100 and the AP 200 is set up through three steps: scanning, authentication, and association. First, the scanning step is a step in which the STA 100 acquires connection information of the BSS operated by the AP 200. There are two methods for performing scanning: a passive scanning method in which the STA 100 acquires information using only a beacon message S101 periodically transmitted by the AP 200, and an active scanning method in which the STA 100 transmits a probe request to the AP S103, receives a probe response from the AP S105, and acquires connection information.

[0047] The STA 100 that has successfully received wireless connection information in the scanning step transmits an authentication request (S107a), receives an authentication response from the AP 200 (S107b), and performs an authentication step. After the authentication step is performed, the STA 100 transmits an association request (S109a), receives an association response from the AP 200, and performs an association step (S109b). In this specification, association basically means wireless association, but the present invention is not limited thereto, and association in a broad sense includes both wireless association and wired association.

[0048] Meanwhile, an 802.1X-based authentication step S111 and an IP address acquisition step S113 via DHCP are additionally performed. In Fig. 5, the server 300 is a server that processes 802.1X-based authentication with the STA 100, and may be physically connected to the AP 200 or may exist as a separate server.

[0049] FIG. 6 is a diagram showing a Carrier Sense Multiple Access (CSMA) / Collision Avoidance (CA) method used in wireless LAN communication.

[0050] A terminal performing wireless LAN communication checks whether a channel is occupied by performing carrier sensing before transmitting data. If a wireless signal of a certain strength or more is detected, the channel is determined to be occupied, and the terminal delays access to the channel. This process is called Clear Channel Assessment (CCA), and the level that determines whether the signal is detected is called the CCA threshold. If a wireless signal of a strength greater than the CCA threshold received by a terminal is received by the terminal, the terminal processes the received wireless signal. On the other hand, if no wireless signal is detected from the channel or a wireless signal of a strength less than the CCA threshold is detected, the channel is determined to be idle.

[0051] If the channel is determined to be in an idle state, each terminal having data to transmit performs a backoff procedure after an IFS (Inter Frame Space) according to the status of each terminal, for example, an AIFS (Arbitration IFS) or a PIFS (PCF IFS). In some embodiments, the AIFS is used as a configuration to replace the conventional DIFS (DCF IFS). Each terminal waits while decreasing a slot time of a random number determined for the corresponding terminal during an interval of the idle state of the channel, and a terminal that has exhausted all the slot time attempts to access the corresponding channel. In this manner, a section in which each terminal performs a backoff procedure is called a contention window section. At this time, the random number can be called a backoff counter. That is, an initial value of the backoff counter is set by an integer that is a random number obtained by the terminal. If the terminal detects that the channel is idle during the slot time, the terminal can decrease the backoff counter by 1. Also, if the backoff counter reaches 0, the terminal may be allowed to perform channel access on the corresponding channel. Thus, a terminal may be allowed to transmit if the channel is idle during the AIFS time and the backoff counter slot time.

[0052] If a specific terminal succeeds in accessing the channel, the terminal transmits data through the channel. However, if the terminal attempting access collides with another terminal, the colliding terminals are assigned new random numbers and perform a backoff procedure again. According to one embodiment, the random numbers newly assigned to each terminal are determined within a range (2*CW) twice the range (contention window, CW) of the random numbers previously assigned to the terminal. Meanwhile, each terminal attempts access by performing a backoff procedure again in the next contention window period, and at this time, each terminal performs the backoff procedure from the slot time remaining in the previous contention window period. In this manner, each terminal performing wireless LAN communication can avoid collision with each other on a specific channel.

[0053] <Examples of various PPDU formats>

[0054] FIG 7 shows an example of various standard generation PPDU (PLCP Protocol Data Unit) formats. More specifically, FIG 7(a) shows an example of a legacy PPDU format based on 802.11a / g, FIG 7(b) shows an example of a HE PPDU format based on 802.11ax, and FIG 7(c) shows an example of a non-legacy PPDU (i.e., EHT PPDU) format based on 802.11be. Also, FIG 7(d) shows detailed field configurations of L-SIG and RL-SIG commonly used in the PPDU formats.

[0055] 7(a), the preamble of the legacy PPDU includes a legacy short training field (L-STF), a legacy long training field (L-LTF), and a legacy signal field (L-SIG). In an embodiment of the present invention, the L-STF, L-LTF, and L-SIG may be referred to as a legacy preamble.

[0056] Referring to FIG. 7(b), the preamble of the HE PPDU further includes a RL-SIG (Repeated Legacy Short Training field), a HE-SIG-A (High Efficiency Signal A field), a HE-SIG-B (High Efficiency Signal B field), a HE-STF (High Efficiency Short Training field), and a HE-LTF (High Efficiency Long Training field) in addition to the legacy preamble. In an embodiment of the present invention, the RL-SIG, HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF can be referred to as an HE preamble. The specific configuration of the HE preamble may be modified according to the HE PPDU format. For example, the HE-SIG-B may be used only in the HE MU PPDU format.

[0057] Referring to FIG. 7(c), the preamble of the EHT PPDU further includes a RL-SIG (Repeated Legacy Short Training field), a U-SIG (Universal Signal field), an EHT-SIG-A (Extremely High Throughput Signal A field), an EHT-SIG-A (Extremely High Throughput Signal B field), an EHT-STF (Extremely High Throughput Short Training field), and an EHT-LTF (Extremely High Throughput Long Training field) in addition to the legacy preamble. In an embodiment of the present invention, the RL-SIG, EHT-SIG-A, EHT-SIG-B, EHT-STF, and EHT-LTF can be called an EHT preamble. The specific configuration of the non-legacy preamble may be modified according to the EHT PPDU format. For example, EHT-SIG-A and EHT-SIG-B may be used only in some formats of the EHT PPDU format.

[0058] The L-SIG field included in the preamble of the PPDU is configured with a total of 64 subcarriers by applying 64 FFT OFDM. Of these, 48 subcarriers excluding the guard subcarriers, DC subcarriers, and pilot subcarriers are used for L-SIG data transmission. Since BPSK and Rate=1 / 2 MCS (Modulation and Coding Scheme) are applied to the L-SIG, it can contain a total of 24 bits of information. Figure 7(d) shows the 24-bit information configuration of the L-SIG.

[0059] Referring to FIG. 7(d), the L-SIG includes an L_RATE field and an L_LENGTH field. The L_RATE field is composed of 4 bits and indicates the MCS used for data transmission. Specifically, the L_RATE field indicates one of the transmission speeds of 6 / 9 / 12 / 18 / 24 / 36 / 48 / 54 Mbps, which is a combination of a modulation method such as BPSK / QPSK / 16-QAM / 64-QAM and a code rate such as 1 / 2, 2 / 3, or 3 / 4. The total length of the PPDU can be indicated by combining the information in the L_RATE field and the L_LENGTH field. In the non-legacy PPDU format, the L_RATE field is set to the minimum speed of 6 Mbps.

[0060] The unit of the L_LENGTH field is byte, and a total of 12 bits are allocated so that a maximum of 4095 can be signaled. The length of the corresponding PPDU can be indicated in combination with the L_RATE field. In this case, legacy and non-legacy terminals can interpret the L_LENGTH field in different ways.

[0061] First, a method in which a legacy or non-legacy terminal analyzes the length of the PPDU using the L_LENGTH field is as follows. When the L_RATE field is set to 6 Mbps, 3 bytes (i.e., 24 bits) may be transmitted at 4 us, which is one symbol duration of 64 FFT. Therefore, the number of 64 FFT reference symbols after the L-SIG is obtained by adding 3 bytes corresponding to the SVC field and the Tail field to the L_LENGTH field value and dividing it by 3 bytes, which is the transmission amount of one symbol. The length of the PPDU, i.e., the reception time (RXTIME), is obtained by multiplying the obtained number of symbols by 4 us, which is one symbol duration, and adding 20 us for the transmission of the L-STF, L-LTF, and L-SIG. This can be expressed as the following Equation 1.

[0062]

number

[0063] At this time,

number

[0064]

number

[0065] Here, TXTIME is the total transmission time constituting the PPDU, and is expressed as the following Equation 3. In this case, TX represents the transmission time of X.

[0066]

number

[0067] Referring to the above formula, the length of the PPDU is calculated based on the rounded up value of L_LENGTH / 3. Therefore, for any value of k, three different values ​​of L_LENGTH={3k+1, 3k+2, 3(k+1)} indicate the same PPDU length.

[0068] Referring to FIG. 7(e), the U-SIG (Universal SIG) field remains in the EHT PPDU and the PPDU of the succeeding generation of WLAN, and plays a role in identifying which generation of PPDU it is, including 11be. The U-SIG is two symbols of 64FFT-based OFDM and can transmit a total of 52 bits of information. Of these, 43 bits excluding the CRC / tail 9 bits are roughly divided into a VI (Version Independent) field and a VD (Version Dependent) field.

[0069] The VI bit will maintain the current bit configuration, and even if a subsequent generation PPDU is defined, a current 11be terminal can obtain information about the PPDU from the VI field of the PPDU. To this end, the VI field is composed of PHY version, UL / DL, BSS color, TXOP, and Reserved fields. The PHY version field is 3 bits, and serves to sequentially distinguish 11be and subsequent generation WLAN standards by version. 11be has a value of 000b. The UL / DL field distinguishes whether the corresponding PPDU is an uplink / downlink PPDU. The BSS color means a BSS-specific identifier defined in 11ax, and has a value of 6 bits or more. The TXOP means a transmit opportunity duration that was transmitted in the MAC header, but by adding it to the PHY header, the length of the TXOP containing the corresponding PPDU can be inferred without decoding the MPDU, and has a value of 7 bits or more.

[0070] The VD field may be composed of fields commonly used in any PPDU format, such as PPDU format and BW, which are signaling information useful only for PPDUs of the 11be version, and fields defined differently for each PPDU format. The PPDU format is a division factor that distinguishes EHT SU (Single User), EHT MU (Multiple User), EHT TB (Trigger-based), EHT ER (Extended Range) PPDU, etc. The BW field mainly signals five basic PPDU BW options of 20, 40, 80, 160 (80+80), and 320 (160+160) MHz (BWs that can be expressed in the form of a power of 20*2 can be called basic BWs), and various remaining PPDU BWs formed by preamble puncturing. After being signaled at 320 MHz, some 80 MHz may be signaled in a punctured form. Also, the punctured and modified channel shape may be directly signaled in the BW field, or may be signaled using both the BW field and a field that appears after the BW field (e.g., a field in the EHT-SIG field). If the BW field is 3 bits, a total of 8 BW signalings are possible, so a maximum of 3 puncturing modes can be signaled. If the BW field is 4 bits, a total of 16 BW signalings are possible, so a maximum of 11 puncturing modes can be signaled.

[0071] The fields located after the BW field vary depending on the type and format of the PPDU. The MU PPDU and the SU PPDU may be signaled in the same PPDU format, and a field for distinguishing the MU PPDU from the SU PPDU may be located before the EHT-SIG field, and additional signaling may be performed for this purpose. Both the SU PPDU and the MU PPDU include an EHT-SIG field, but some fields that are not necessary in the SU PPDU may be compressed. In this case, the information of the compressed field may be omitted or may have a reduced size compared to the size of the original field included in the MU PPDU. For example, in the case of the SU PPDU, the common field of the EHT-SIG may be omitted or replaced, or the user-specific field may be replaced or reduced to one, and may have a different configuration.

[0072] Alternatively, the SU PPDU may further include a compression field indicating whether or not it is compressed, and some fields (eg, the RA field, etc.) may be omitted depending on the value of the compression field.

[0073] When a part of the EHT-SIG field of the SU PPDU is compressed, the information included in the compressed field may be signaled together in an uncompressed field (e.g., a common field, etc.). In the case of the MU PPDU, since it is a PPDU format for simultaneous reception by multiple users, the EHT-SIG field must be transmitted after the U-SIG field, and the amount of information signaled may be variable. That is, since multiple MU PPDUs are transmitted to multiple STAs, each STA must recognize the location of the RU to which the MU PPDU is transmitted, the STA to which each RU is assigned, and whether the transmitted MU PPDU was transmitted to itself. Therefore, the AP must transmit the above information in the EHT-SIG field. To this end, the U-SIG field signals information for efficiently transmitting the EHT-SIG field, which may be the number of symbols of the EHT-SIG field and / or MCS, which is a modulation method. The EHT-SIG field may include the size and location information of the RU assigned to each user.

[0074] In the case of a SU PPDU, a STA may be assigned multiple RUs, and the multiple RUs may be contiguous or discontinuous. If the RUs assigned to the STA are not contiguous, the STA can receive the SU PPDU efficiently only by recognizing the RUs punctured in between. Therefore, the AP can transmit the SU PPDU including information on the punctured RUs among the RUs assigned to the STA (e.g., the puncturing pattern of the RUs, etc.). That is, in the case of a SU PPDU, a puncturing mode field including information indicating whether a puncturing mode is applied and the puncturing pattern in a bitmap format, etc., may be included in the EHT-SIG field, and the puncturing mode field may signal the type of discontinuous channels that appear within the bandwidth.

[0075] The form of the signaled discontinuous channel is limited, and indicates the BW and discontinuous channel information of the SU PPDU in combination with the value of the BW field. For example, in the case of a SU PPDU, since it is a PPDU transmitted only to a single UE, the STA can recognize the bandwidth allocated to itself from the BW field included in the PPDU, and can recognize the punctured resources of the allocated bandwidth from the puncturing mode field of the U-SIG field or EHT-SIG field included in the PPDU. In this case, the UE can receive the PPDU in the remaining resource units other than the specific channel of the punctured resource unit. In this case, the multiple RUs allocated to the STA may be configured with different frequency bands or tones.

[0076] The reason why only limited discontinuous channel types are signaled is to reduce the signaling overhead of SU PPDU. Since puncturing may be performed for each 20 MHz subchannel, if puncturing is performed for a BW having multiple 20 MHz subchannels such as 80, 160, and 320 MHz, in the case of 320 MHz, the discontinuous channel type (when only the end 20 MHz is punctured and considered as discontinuous) must be signaled by expressing whether or not the remaining 15 20 MHz subchannels other than the primary channel are used. In this way, using 15 bits to signal discontinuous channel types for single user transmission may result in excessive signaling overhead when considering the low transmission speed of the signaling part.

[0077] The present invention proposes a method for signaling the discontinuous channel type of the SU PPDU, illustrates the discontinuous channel type determined by the proposed method, and proposes a method for signaling the primary 160 MHz and secondary 160 MHz puncturing types in the 320 MHz BW configuration of the SU PPDU.

[0078] In addition, in one embodiment of the present invention, a method is proposed in which the configuration of the PPDU indicated by the preamble puncturing BW value is different depending on the PPDU format signaled in the PPDU format field. Assuming that the BW field is 4 bits, in the case of EHT SU PPDU or TB PPDU, one symbol of EHT-SIG-A is further signaled after U-SIG, or EHT-SIG-A does not need to be signaled from the beginning. Taking this into consideration, it is necessary to completely signal up to 11 puncturing modes using only the BW field of U-SIG. However, in the case of EHT MU PPDU, EHT-SIG-B is further signaled after U-SIG, so up to 11 puncturing modes can be signaled in a different manner from SU PPDU. In the case of EHT ER PPDU, the BW field is set to 1 bit to signal whether the PPDU uses a 20 MHz or 10 MHz band.

[0079] FIG. 7(f) shows the format-specific field configuration of the VD field when the PPDU format field of the U-SIG indicates EHT MU PPDU. In the case of MU PPDU, SIG-B, which is a signaling field for simultaneous reception by multiple users, is required, and SIG-B may be transmitted after U-SIG without a separate SIG-A. For this purpose, U-SIG must signal information for decoding SIG-B. Such fields include SIG-B MCS, SIG-B DCM, Number of SIG-B Symbols, SIG-B Compression, and Number of EHT-LTF Symbols.

[0080] FIG. 8 illustrates an example of various Extremely High Throughput (EHT) Physical Protocol Data Unit (PPDU) formats and a method for indicating the same according to an embodiment of the present invention.

[0081] 8, a PPDU may be composed of a preamble and a data portion, and the format of an EHT PPDU, which is one type, may be distinguished by a U-SIG field included in the preamble. Specifically, whether the format of the PPDU is an EHT PPDU may be indicated based on a PPDU format field included in the U-SIG field.

[0082] 8(a) shows an example of an EHT SU PPDU format for a single STA. The EHT SU PPDU is a PPDU used for single user (SU) transmission between an AP and a single STA, and an EHT-SIG-A field for additional signaling may be located after the U-SIG field.

[0083] 8(b) shows an example of an EHT trigger-based PPDU format, which is an EHT PPDU transmitted based on a trigger frame. The EHT trigger-based PPDU is an EHT PPDU transmitted based on a trigger frame, and is an uplink PPDU used for responding to the trigger frame. Unlike the EHT SU PPDU, the EHT PPDU does not have an EHT-SIG-A field after the U-SIG field.

[0084] 8(c) shows an example of an EHT MU PPDU format, which is an EHT PPDU for multiple users. The EHT MU PPDU is a PPDU used to transmit a PPDU to one or more STAs. In the EHT MU PPDU format, an HE-SIG-B field may be located after the U-SIG field.

[0085] Fig. 8(d) shows an example of an EHT ER SU PPDU format used for single-user transmission with an STA in an extended range. The EHT ER SU PPDU may be used for single-user transmission with a STA in a wider range than the EHT SU PPDU described in Fig. 8(a), and the U-SIG field may be repeatedly positioned on the time axis.

[0086] The EHT MU PPDU described in (c) of FIG. 8 can be used by the AP for downlink transmission to multiple STAs. In this case, the EHT MU PPDU can include scheduling information so that multiple STAs can simultaneously receive the PPDU transmitted from the AP. The EHT MU PPDU can convey AID information of the receiver and / or sender of the PPDU transmitted through the user specific field of the EHT-SIG-B to the STA. Therefore, multiple terminals receiving the EHT MU PPDU can perform spatial reuse based on the AID information of the user specific field included in the preamble of the received PPDU.

[0087] Specifically, the resource unit allocation (RA) field of the HE-SIG-B field included in the HE MU PPDU may include information regarding a resource unit configuration (e.g., a resource unit division form) in a specific bandwidth (e.g., 20 MHz, etc.) on the frequency axis. That is, the RA field may indicate a resource unit configuration divided by a bandwidth for transmitting the HE MU PPDU so that the STA receives the PPDU. Information on the STA allocated (or designated) to each divided resource unit may be included in a user specific field of the EHT-SIG-B and transmitted to the STA. That is, the user specific field may include one or more user fields corresponding to each divided resource unit.

[0088] For example, a user field corresponding to at least one resource unit used for data transmission among the multiple divided resource units may include the AID of a receiver or sender, and a user field corresponding to the remaining resource units not used for data transmission may include a null STA ID that has already been set.

[0089] For ease of explanation, the term frame or MAC frame may be used interchangeably with MPDU in this specification.

[0090] When one wireless communication device communicates using multiple links, the communication efficiency of the wireless communication device can be improved. In this case, the link is a physical path, and may be configured as one wireless medium that can be used to transmit MSDU (MAC service data unit). For example, when the frequency band of any one link is being used by another wireless communication device, the wireless communication device can continue to communicate using another link. In this way, the wireless communication device can effectively use multiple channels. Also, when the wireless communication device simultaneously communicates using multiple links, the overall throughput can be increased. However, the existing wireless LAN is specified on the premise that one wireless communication device uses one link. For this reason, a wireless LAN operation method for using multiple links is required. A wireless communication method of a wireless communication device using multiple links will be described with reference to Figs. 9 to 26. First, a specific form of a wireless communication device using multiple links will be described with reference to Fig. 9.

[0091] FIG. 9 shows a multi-link device according to an embodiment of the present invention.

[0092] For the wireless communication method using the above-mentioned multiple links, a multi-link device (MLD) may be defined. The multi-link device may represent a device having one or more affiliated stations. According to a specific embodiment, the multi-link device may represent a device having two or more affiliated stations. Also, the multi-link device may exchange a multi-link element. The multi-link element includes information on one or more stations or one or more links. The multi-link element may include a multi-link setup element, which will be described later. In this case, the multi-link device may be a logical entity. Specifically, the multi-link device may have multiple affiliated stations. The multi-link device may be called a multi-link logical entity (MLLE) or a multi-link entity (MLE). The multi-link device may have one MAC service access point (SAP) up to a logical link control (LLC). Also, the MLD may have one MAC data service.

[0093] The stations included in the multilink device can operate on multiple links. Also, the stations included in the multilink device can operate on multiple channels. Specifically, the stations included in the multilink device can operate on different links or different channels. For example, the stations included in the multilink device can operate on different channels of 2.4 GHz, 5 GHz, and 6 GHz.

[0094] The operation of the multilink device may be referred to as multilink operation, MLD operation, or multi-band operation. If a station associated with the multilink device is an AP, the multilink device may be referred to as AP MLD. If a station associated with the multilink device is a non-AP station, the multilink device may be referred to as non-AP MLD.

[0095] FIG. 9 shows the operation of communication between non-AP MLD and AP-MLD. Specifically, non-AP MLD and AP-MLD each communicate using three links. AP MLD includes a first AP (AP1), a second AP (AP2), and a third AP (AP3). Non-AP MLD includes a first non-AP STA (non-AP STA1), a second non-AP STA (non-AP STA2), and a third non-AP STA (non-AP STA3). The first AP (AP1) and the first non-AP STA (non-AP STA1) communicate through a first link (Link1). Also, the second AP (AP2) and the second non-AP STA (non-AP STA2) communicate through a second link (Link2). Also, the third AP (AP3) and the third non-AP STA (non-AP STA3) communicate through a third link (Link3).

[0096] The multi-link operation may include a multi-link setup operation. The multi-link setup corresponds to the association operation of the single-link operation described above, and must be preceded for frame exchange in the multi-link. The multi-link device may obtain information required for the multi-link setup from the multi-link setup element. Specifically, the multi-link setup element may include capability information related to the multi-link. In this case, the capability information may include information indicating whether one of the multiple devices included in the multi-link device can transmit and the other devices can receive at the same time. In addition, the capability information may include information regarding links available to each station included in the MLD. In addition, the capability information may include information regarding channels available to each station included in the MLD.

[0097] The multilink setting may be set by negotiation between peer stations. Specifically, the multilink setting may be set by communication between stations without communication with the AP. The multilink setting may be set through any one of the links. For example, even if the first link to the third link are set through the multilink, the multilink setting may be set through the first link.

[0098] Also, a mapping between a traffic identifier (TID) and a link may be set. Specifically, a frame corresponding to a specific TID value may be exchanged only through a link designated in advance. The mapping between a TID and a link may be set on a directional-based basis. For example, when a plurality of links are set between a first multilink device and a second multilink device, the first multilink device may be set to transmit a frame of a first TID to a plurality of first links, and the second multilink device may be set to transmit a frame of a second TID to the first link. Also, a default setting may exist for the mapping between a TID and a link. Specifically, when there is no additional setting in the multilink setting, the multilink device may exchange frames corresponding to a TID in each link according to a default setting. In this case, the default setting may be that all TIDs are exchanged in any one link.

[0099] The TID will be specifically described. The TID is an ID for classifying traffic and data to support QoS (quality of service). The TID may be used and assigned in a layer higher than the MAC layer. The TID may indicate a traffic category (TC) or a traffic stream (TS). The TID may be classified into 16 types. For example, the TID may be designated as one of 0 to 15. The TID value to be used may be designated differently depending on an access policy, a channel access, or a medium access method. For example, when EDCA (enhanced distributed channel access) or HCAF (hybrid coordination function contention based channel access) is used, the TID value may be assigned in the range of 0 to 7. When EDCA is used, the TID may indicate a user priority (UP). In this case, the UP may be designated by the TC or the TS. The UP may be assigned in a layer higher than the MAC. Also, when HCCA (HCF controlled channel access) or SPCA is used, the TID may be assigned a value in the range of 8 to 15. When HCCA or SPCA is used, the TID may indicate a TSID. Also, when HEMM or SEMM is used, the TID may be assigned a value in the range of 8 to 15. When HEMM or SEMM is used, the TID may indicate a TSID.

[0100] UP and AC (access category) may be mapped. AC may be a label for providing QoS in EDCA. AC may be a label for indicating an EDCA parameter set. EDCA parameters or EDCA parameter sets are parameters used in channel contention in EDCA. QoS stations can guarantee QoS using AC. AC may include AC_BK, AC_BE, AC_VI, and AC_VO. AC_BK, AC_BE, AC_VI, and AC_VO may indicate background, best effort, video, and voice, respectively. AC_BK, AC_BE, AC_VI, and AC_VO may be classified into lower ACs. For example, AC_VI may be subdivided into AC_VI primary and AC_VI alternate. AC_VO may be subdivided into AC_VO primary and AC_VO alternate. UP or TID may be mapped to AC. For example, 1, 2, 0, 3, 4, 5, 6, and 7 in UP or TID may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI, AC_VI, AC_VO, and AC_VO, respectively. Also, 1, 2, 0, 3, 4, 5, 6, and 7 in UP or TID may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI alternate, AC_VI primary, AC_VO primary, and AC_VO alternate, respectively. Also, 1, 2, 0, 3, 4, 5, 6, and 7 in UP or TID may have a higher priority in that order. That is, 1 may have a lower priority, and 7 may have a higher priority. Therefore, the priority may be higher in the order of AC_BK, AC_BE, AC_VI, and AC_VO. Also, AC_BK, AC_BE, AC_VI, and AC_VO may correspond to ACI (AC index) 0, 1, 2, and 3, respectively. Due to the characteristics of such a TID, the mapping between a TID and a link may represent the mapping between an AC and a link.Additionally, the mapping between links and ACs can represent the mapping between TIDs and links.

[0101] As described above, a TID may be mapped to each of a plurality of links. The mapping may be a designation of a link through which traffic corresponding to a particular TID or AC may be exchanged. Also, a TID or AC that may be transmitted for each transmission direction within a link may be designated. As described above, there may be a default setting for mapping between a TID and a link. Specifically, if there is no additional setting in the multilink setting, the multilink device may exchange frames corresponding to the TID on each link according to the default setting. In this case, the default setting may be that all TIDs are exchanged on any one link. At any given time, any TID or AC may be mapped to at least one link. Management frames and control frames may be transmitted on all links.

[0102] When a link is mapped to a TID or AC, only data frames corresponding to the TID or AC mapped to the link may be transmitted on the link. Therefore, when a link is mapped to a TID or AC, frames not corresponding to the TID or AC not mapped to the link may not be transmitted on the link. When a link is mapped to a TID or AC, an ACK may also be transmitted based on the link to which the TID or AC is mapped. For example, a Block ACK agreement may be determined based on the mapping between the TID and the link. In yet another specific embodiment, the mapping between the TID and the link may be determined based on the Block ACK agreement. Specifically, a Block ACK agreement may be set for a TID mapped to a specific link.

[0103] The above-mentioned TID-to-link mapping may ensure QoS. Specifically, a high priority AC or TID may be mapped to a link where a relatively small number of stations are in operation or where channel conditions are good. The above-mentioned TID-to-link mapping may also allow stations to stay in a power saving state for a longer period of time.

[0104] FIG. 10 illustrates simultaneous transmission of different links in a multi-link operation according to an embodiment of the present invention.

[0105] Depending on the implementation of the multilink device, simultaneous operation in the multilink may not be supported. For example, the multilink device may support simultaneous transmission in multiple links, simultaneous reception in multiple links, or transmission in one link and reception in another link. Reception or transmission in one link may affect reception or transmission in another link. Specifically, transmission in one link may act as interference in another link. Interference from one link of a multilink device acting on another link may be called internal leakage. The smaller the frequency interval between the links, the larger the internal leakage may be. If the internal leakage is not too large, transmission can be performed in another link when transmission is performed in one link. If the internal leakage is large, transmission cannot be performed in another link when transmission is performed in one link. In this way, the simultaneous operation of the multilink device in multiple links may be called STR (simultaneous transmit and receive, simultaneous transmission and reception). For example, a multilink device may transmit on multiple links simultaneously, transmit on one link while simultaneously receiving on another link, or receive on multiple links simultaneously, all of which may be referred to as STR.

[0106] On the other hand, when STR is not supported due to interference between multiple stations constituting the MLD, the STAs may be expressed as being in a non-STR relationship or NSTR relationship (relationship in which STR is not supported).

[0107] In this case, whether two STAs (STA1 and STA2) in the MLD support STR may depend on the distance between the link pair on which the STAs operate (Link1 on which STA1 operates and Link2 on which STA2 operates).

[0108] Therefore, when an MLD operates each STA in a specific link pair, if an STR is supported between both STAs operated in the specific link pair, the specific link pair may be considered as an STR link pair by the MLD. On the other hand, when an MLD operates each STA in another link pair, if an STR is not supported between both STAs operated in the other link pair, the other link pair may be considered as an NSTR link pair by the MLD.

[0109] In this way, whether STR is supported between STAs of MLDs is determined by whether the link pair on which these STAs operate is an STR link pair or an NSTR link pair. However, as described above, since the characteristics (such as shielding performance) of each MLD may differ from each other, a specific link pair may be considered as a link pair in which STR is supported for a specific MLD and as an NSTR link pair in which STR is not supported for another MLD.

[0110] In one embodiment of the present invention described below, for convenience of explanation, the STAs operated in the STR link pair of the MLD are named (specified) as STR MLD STAs, and the STAs operated in the NSTR link pair of the MLD are named (specified) as NSTR (and non-STR) MLD STAs. That is, in the embodiment described below, when "non-STR MLD STAs" are mentioned, it may be interpreted as referring to one of the two STAs operated in the NSTR link pair of the MLD, and when "STR MLD STAs" are mentioned, it may be interpreted as referring to one of the two STAs operated in the STR link pair of the MLD.

[0111] In addition, the NSTR MLD may include not only an MLD in which the STA of a specific MLD loses reception capability in relation to the presence or absence of STR support described above, but also an MLD in which the hardware configuration of the MLD itself does not support simultaneous transmission / reception.

[0112] In other words, the hardware configuration of a MLD (Multi-link device) may have a configuration that limits the hardware resources that other STAs in the MLD can utilize when a specific STA in the MLD is transmitting or receiving. For example, if a specific MLD has a hardware configuration that supports processing for only one PPDU, when a specific STA in the specific MLD is performing Rx, the specific MLD cannot support Tx and Rx for other STAs in the MLD. Similarly, when a specific STA in the specific MLD is performing Tx, the specific MLD cannot support Tx and Rx for other STAs in the MLD.

[0113] In this way, a device that is an MLD and can operate STAs on two or more links but can support transmission / reception for only one STA at a particular time can be called a multi-link single radio MLD (MLSR MLD). Alternatively, an operation mode in which an MLD supports transmission / reception for only one STA as one type of operation mode can be called an enhanced multi-link single radio (EMLSR) mode. In this case, an MLD operating in EMLSR mode can be a multi-radio MLD or an enhanced single-radio MLD. An enhanced single-radio MLD supports data transmission / reception for only one link at a time, but can refer to a device that supports CCA and low-speed data rate (e.g., encoded at 6 MHz or 24 MHz or less) PPDU transmission / reception for two or more links by having a configuration including separate hardware (such as a low-cost PHY front end).

[0114] Also, as a modification of the EMLSR mode, EMLMR (Enhance Multi-Link Multi-Radio) may be defined in which the MLD supports transmission / reception for each STA, but utilizes part of the RF chain used by a specific STA for transmission / reception for other STAs. EMLMR may have the same transmission / reception restriction characteristics as EMLSR when all of the RF chains used by the specific STA are utilized for transmission / reception for the other STAs. That is, the MLD operating in the EMLMR mode can operate to support only transmission / reception for only one link (STA) at a specific time regardless of whether STR is supported for the link, and this may be understood as an operation similar to that of the MLD operating in the EMLSR mode.

[0115] That is, the links of an MLD operated in EMLSR / EMLMR mode may be considered as an NSTR link pair.

[0116] In this case, the above-mentioned transmission / reception includes transmission / transmission and reception / reception, that is, it has nothing to do with whether or not both links support STR / NSTR.

[0117] For ease of explanation, hereinafter, EMLSR / EMLMR MLD is used to mean an MLD that can only support transmission / reception for one STA at a particular time due to hardware constraints, and an MLD that can support transmission / reception for two or more STAs (processing capability unrelated to STR) but only supports high-speed data frame transmission / reception for one STA at a particular time as a type of operating mode.

[0118] The operation of the STR MLD considering the performance limitations of the NSTR MLD provided by the above-mentioned embodiment of the present invention can be directly used as the operation of the STR MLD for the MLSR MLD. For example, after a STA of the STR MLD transmits to a STA of the multi-link single radio MLD, if the STA determines that the transmission has failed or is expected to fail due to the limited performance of the multi-link single radio MLD STA, the STA can cancel the transmission that is being performed or is about to be performed. In this case, the procedure of checking whether the transmission has failed due to the limited performance of the EMLSR / EMLMR MLD can be similar to the procedure of checking whether a transmission to a STA of the NSTR MLD has failed due to the limited performance of the NSTR MLD STA.

[0119] As mentioned above, the multilink device can support STR or can support it in a limited manner. Specifically, the multilink device can support STR only under certain conditions. For example, if the multilink device operates with a single radio, the multilink device may not be able to perform STR. Also, if the multilink device operates with a single antenna, the multilink device may not be able to perform STR. Also, if an internal leak is detected to be equal to or greater than a pre-specified magnitude, the multilink device may not be able to perform STR.

[0120] A station can exchange information on the STR capability of the station with other stations. Specifically, a station can exchange information on the presence or absence of a restriction on the capability of the station to simultaneously transmit on multiple links or simultaneously receive on multiple links with other stations. Specifically, the information on the presence or absence of a restriction on the capability of transmitting or receiving on multiple links can indicate whether the station transmits on multiple links simultaneously, receives on multiple links simultaneously, or transmits and receives simultaneously. In addition, the information on the presence or absence of a restriction on the capability of transmitting or receiving on multiple links may be information indicated in stages. Specifically, the information on the presence or absence of a restriction on the capability of transmitting or receiving on multiple links may be information indicating a stage indicating the magnitude of the internal leakage. In a specific embodiment, the information indicating a stage indicating the magnitude of the internal leakage may be information indicating a stage indicating the magnitude of interference generated by the internal leakage. In yet another specific embodiment, the information indicating a stage indicating a frequency interval between links that may affect the internal leakage may be information indicating a stage indicating the magnitude of the internal leakage. In addition, the information indicating a stage indicating the magnitude of the internal leakage may be information indicating a relationship between the frequency interval between the links and the magnitude of the internal leakage in stages.

[0121] In FIG. 10, a first station (STA1) and a second station (STA2) are affiliated to one non-AP multilink device. Also, a first AP (AP1) and a second AP (AP2) may be affiliated to one non-AP multilink device. A first link (link1) is established between the first AP (AP1) and the first station (STA1), and a second link (link2) is established between the second AP (AP2) and the second station (STA2). In FIG. 10, the non-AP multilink device may perform STR in a limited manner. When the second station (STA2) transmits through the second link (Link2), the first station (STA1)'s reception through the first link (Link1) may be interrupted by the transmission through the second link (Link2). For example, in the following case, the first station (STA1)'s reception through the first link (Link1) may be interrupted by the transmission through the second link (Link2). The second station (STA2) transmits the first data (Data1) via the second link (Link2), and the first AP (AP1) transmits a response (Ack for Data1) to the first station (STA1). The second station (STA2) transmits the second data (Data2) via the second link (Link2). At this time, the transmission time of the second data (Data2) and the transmission time of the response (Ack for Data1) to the first data (Data1) may overlap. At this time, the transmission to the second station (STA2) via the second link (Link2) may cause interference to the first link (Link1). As a result, the first station (STA1) may not be able to receive the response (Ack for Data1) to the first data (Data1).

[0122] The operation of the multilink device performing channel access will now be described. The multilink operation not specifically described can follow the channel access procedure described in FIG.

[0123] The multilink device may perform channel access independently from a plurality of links. In this case, the channel access may be a back-off based channel access. When the multilink device performs channel access independently from a plurality of links and the back-off counters reach 0 in the plurality of links, the multilink device may start transmission simultaneously from the plurality of links. In a specific embodiment, when any one of the back-off counters of the links of the multilink reaches 0 and a pre-specified condition is satisfied, the multilink device may perform channel access not only for the link whose back-off counter reaches 0 but also for other links whose back-off counters have not reached 0. Specifically, when any one of the back-off counters of the links of the multilink reaches 0, the multilink device may perform energy sensing in other links whose back-off counters have not reached 0. In this case, when energy equal to or greater than a pre-specified magnitude is not detected, the multilink device may perform channel access not only for the link whose back-off counter reaches 0 but also for the link whose energy sensing has been performed. In this way, the multilink device may start transmission simultaneously from the plurality of links. The threshold value used for energy sensing may be smaller than the threshold value used when determining whether to decrease the back-off counter. In addition, when determining whether to decrease the back-off counter, the multilink device can sense any type of signal, not just a WLAN signal. In addition, in the above-mentioned energy sensing, the multilink device can sense any type of signal, not just a WLAN signal. Internal leakage may not be detected as a WLAN signal. In such a case, the multilink device can sense a signal detected due to internal leakage by energy sensing. In addition, as described above, the threshold value used for energy sensing may be smaller than the threshold value used when determining whether to decrease the back-off counter. Therefore, even when transmission is being performed on one link, the multilink device can decrease the back-off counter on the other link.

[0124] Depending on the degree of interference between links used by the multilink apparatus, the multilink apparatus may determine whether stations operating on each link can operate independently. In this case, the degree of interference between links may be the magnitude of interference sensed by other stations of the multilink apparatus when any one station of the multilink apparatus transmits on any one link. When the transmission of a first station of the multilink apparatus on the first link causes interference of a predetermined magnitude or more to a second station of the multilink apparatus operating on the second link, the operation of the second station may be restricted. Specifically, the reception or channel access of the second station may be restricted. When interference occurs, the second station may fail to decode a signal received due to the interference. Also, when interference occurs, the second station may determine that the channel is in use when the second station accesses the channel using backoff.

[0125] In addition, when the transmission of the first station of the multilink device through the first link generates interference of less than a pre-specified magnitude in the second station of the multilink device operating through the second link, the first station and the second station can operate independently. Specifically, when the transmission of the first station of the multilink device through the first link generates interference of less than a pre-specified magnitude in the second station of the multilink device operating through the second link, the first station and the second station can perform channel access independently. In addition, when the transmission of the first station of the multilink device through the first link generates interference of less than a pre-specified magnitude in the second station of the multilink device operating through the second link, the first station and the second station can perform transmission or reception independently. When interference of less than a pre-specified magnitude occurs, the second station can successfully decode the received signal even in the presence of interference. In addition, when interference of less than a pre-specified magnitude occurs, the second station can determine that the channel is idle when the second station accesses the channel using backoff.

[0126] The degree of interference occurring between stations of a multilink device may vary depending on the interval between the frequency bands of the links on which the stations operate as well as the hardware characteristics of the multilink device. For example, the internal interference occurring in a multilink device including a high RF (radio frequency) device may be smaller than the internal interference occurring in a multilink device including a low RF device. Therefore, the degree of interference occurring between stations of a multilink device may be determined based on the characteristics of the multilink device.

[0127] FIG. 10 shows that the magnitude of interference generated varies depending on the interval between the frequency bands of the links and the characteristics of the multilink device. In the embodiment of FIG. 10, the first multilink device (MLD#1) includes a first station (STA1)-1 operating on the first link (Link1) and a second station (STA1)-2 operating on the second link (Link2). The second multilink device (MLD#2) includes a first station (STA2)-1 operating on the first link (Link1) and a second station (STA2)-2 operating on the second link (Link2). The frequency interval between the first link (Link1) and the second link (Link2) in which the first multilink device (MLD#1) operates is the same as the frequency interval between the first link (Link1) and the second link (Link2) in which the second multilink device (MLD#2) operates. However, the magnitude of interference generated varies depending on the difference between the characteristics of the first multilink device (MLD#1) and the characteristics of the second multilink device (MLD#2). Specifically, the magnitude of interference generated in the second multilink device (MLD#2) may be greater than the magnitude of interference generated in the first multilink device (MLD#1). Considering that the magnitude of interference generated may differ depending on the characteristics of the multilink devices and that the presence or absence of STR support may differ depending on the multilink devices, information regarding whether STR is supported or not needs to be exchanged.

[0128] The multilink device may signal whether or not a station included in the multilink device supports STR. Specifically, the AP multilink device and the non-AP multilink device may exchange whether or not an AP included in the AP multilink device supports STR and whether or not an STA included in the non-AP multilink device supports STR. In this embodiment, an element indicating whether or not an STR is supported may be used. The element indicating whether or not an STR is supported may be called an STR support element. The STR support element may indicate whether or not an STR is supported by a station of the multilink device that transmits the STR support element by one bit. Specifically, the STR support element may indicate whether or not an STR is supported by each station included in the multilink device that transmits the STR support element by one bit. In this case, if the station supports STR, the bit value may be 1, and if the station does not support STR, the bit value may be 0. If the multilink device that transmitted the STR support element includes a first station (STA1), a second station (STA2), and a third station (STA3), and the first station (STA1) and the third station (STA3) support STR, and the second station (STA2) does not support STR, the STR support element is 101 1b It is assumed that stations operating in different frequency bands support STR, and the STR support element may omit signaling regarding the presence or absence of STR support between stations operating in different frequency bands. For example, a first station (STA1) operates in a first link of 2.4 GHz, and a second station (STA2) and a third station (STA3) operate in a second link of 5 GHz and a third link of 5 GHz, respectively. In this case, the STR support element may indicate with one bit that STR is supported between the second station (STA2) and the third station (STA3). Also, the STR support element may include only one bit when there are two stations to which the STR support element signals.

[0129] In a specific embodiment, the relationship between a link located at 2.4 GHz and a link located at 5 GHz or 6 GHz among the links of the multi-link device may always be determined as an STR, and therefore, signaling regarding the presence or absence of an STR between the link located at 2.4 GHz and the link located at 5 GHz or 6 GHz may be omitted.

[0130] In the above-mentioned embodiment, the operation of the station of the multilink device may be replaced by the operation of the multilink device. Also, in the above-mentioned embodiment, the operation of the AP may be replaced by the operation of the non-AP station, and the operation of the non-AP station may be replaced by the operation of the AP. Thus, the operation of the AP of the non-STR multilink device may be replaced by the operation of the non-AP station of the non-STR multilink device, and the operation of the non-AP station of the STR multilink device may be replaced by the operation of the AP of the STR multilink device. Also, the operation of the non-AP station of the non-STR multilink device may be replaced by the operation of the AP of the non-STR multilink device, and the operation of the AP of the STR multilink device may be replaced by the operation of the non-AP station of the STR multilink device.

[0131] Each AP included in the AP MLD can transmit a beacon frame on its own link. APs included in the AP MLD can transmit beacon frames for the same purpose and function as APs in conventional Wi-Fi, and may further include information indicating that the AP is an MLD included in the MLD, MLD level information, common information, and basic information of other APs included in the same MLD in the beacon frame. In this case, the basic information of other APs may be included in the TBTT Information field of the RNR element and transmitted in the beacon frame.

[0132] In a beacon frame transmitted by an AP MLD, only common information per MLD may be included in the beacon frame to prevent the size of the beacon frame from becoming too large (beacon bloating) due to information about multiple APs included in the same MLD being included in one beacon frame.

[0133] However, in the NSTR Soft AP MLD, beacon frames can be transmitted only through some of the APs that it operates. As an example, when the NSTR soft AP MLD operates an AP on two separate links and the two links have an NSTR relationship with each other, the NSTR Soft AP MLD can transmit beacon frames only through one of the two links. In this case, the link through which the NSTR Soft AP MLD transmits beacon frames may have the concept of a primary link in the NSTR link pair of the NSTR Soft AP MLD. Meanwhile, the NSTR Soft AP MLD can operate links other than the primary link in the NSTR link pair with the concept of a secondary link, and the secondary link may be a link that does not transmit beacon frames. The reason why the NSTR Soft AP MLD operates one link of the NSTR link pair as the primary link and at least one other link as the secondary link is to prevent problems that may occur when two separate APs are independently operated in the NSTR link pair. Problems that may occur in an AP MLD that operates an NSTR link pair will be described in more detail in conjunction with an embodiment of an operation restriction applied to an NSTR Soft AP MLD and an STA MLD associated with an NSTR Soft AP MLD, which will be described later. That is, a link pair to which NSTR is applied can transmit beacon frames only on the primary link, and cannot transmit beacon frames on the secondary link.

[0134] As described above, since the NSTR Soft AP MLD has a restriction that a beacon frame is transmitted only on the primary link, the NSTR Soft AP MLD may be allowed to include more information (related to APs of other links (non-primary)) in a beacon frame transmitted on the primary link compared to a general AP MLD. This may be a method of configuring a beacon frame devised so that a non-AP MLD that operates a STA on a secondary link can operate the STA on the secondary link based on information of a beacon frame received on the primary link.

[0135] As an example, the primary link AP of the NSTR soft AP MLD may include a Per-STA Profile corresponding to the secondary link AP (of the same NSTR Soft AP MLD) in the Multi-Link element of the beacon frame. In this case, the primary link AP of the NSTR Soft AP MLD may not have a separate constraint when including a Per-STA Profile corresponding to the secondary link AP. The constraint means a condition under which a general AP MLD may include a Per-STA Profile in a beacon frame (such as an AP corresponding to a Per-STA Profile performing (extended) channel switching, channel quieting, etc.).

[0136] FIG. 11 shows an example of the contents of a beacon frame transmitted by an AP in AP MLD according to one embodiment of the present invention and an example of a TBTT (target beacon transmission time) information field format included in an RNR (Reduced Neighbor Report) element.

[0137] Referring to (a) of Figure 11, the beacon frame may include the same parameters and elements in the Legacy IEs as those included in the beacon frame disclosed in conventional Wi-Fi 802.11ax. For example, the legacy IEs of a beacon frame may include elements such as a timestamp field, a beacon interval field indicating the interval at which a beacon is transmitted, TIM, DSSS parameter set, IBSS parameter set, country, channel switch announcement, extended channel switch announcement, wide bandwidth channel switch, transmit power envelope, supported operating classes, IBSS DFS, ERP information, HT capabilities, HT operation, VHT capability, VHT operation, S1G beacon compatibility, short beacon interval, S1G capability, S1G operation, HE capability, HE 6 GHz band capability, HE operation, BSS color change announcement, and spatial reuse parameter set.

[0138] In this case, the setting method and meaning of the fields and elements included in the legacy IEs field are the same as the setting and meaning of the fields and elements of the same names included in the beacon frame disclosed in conventional Wi-Fi up to 802.11ax.

[0139] In addition, the beacon frame may include a Reduced Neighbor Report (RNR) element for indicating information about neighbor APs. The RNR element may be used to inform a station of information about neighbor APs, and the station may receive the beacon frame and recognize the neighbor APs based on the RNR element included in the beacon frame.

[0140] Specifically, the RNR element may include an element ID field, a length field, and a neighbor AP information field. Each of the neighbor AP information fields may include a TBTT information header (2 octets), an operation class (1 octet), a channel number (1 octet), and a TBTT information set (variable length) field. In this case, the RNR element transmitted by the AP included in the AP MLD may include a TBTT information field format as shown in (b) of FIG. 11 in order to indicate basic information for other APs included in the same MLD. Unlike the TBTT information field of the RNR element transmitted by the AP in conventional Wi-Fi 802.11ax, the RNR element transmitted by the AP included in the EHT AP MLD may include an MLD parameter field.

[0141] The MLD parameter field may include an MLD ID, a link ID, and a change sequence subfield, as shown in (c) of FIG. 11. In this case, when the AP MLD indicates other AP information of the same MLD by the specific neighbor AP information field of the RNR element, the MLD ID subfield included in the specific neighbor AP information field can be set to 0. That is, the AP can set the MLD ID subfield to a specific value to inform the station that the neighbor AP information field is an AP included in the same AP MLD, and the station receiving the neighbor AP information field can recognize from the value of the MLD ID subfield that the AP corresponding to the neighbor AP information field is included in the same MLD as the AP that transmitted the neighbor AP information field.

[0142] The link ID subfield may be a subfield in which an index determined by the AP MLD is indicated to indicate a link operated by another AP to be indicated using the neighbor AP information. The change sequence subfield may be a subfield used to indicate information related to an update (e.g., a critical update) related to a link of another AP. For example, when the value of the change sequence subfield is changed, a station receiving the change sequence subfield can recognize that a parameter related to the link of the corresponding AP has been updated, and can request the updated parameter from the AP to update the corresponding parameter. In this case, if the AP MLD is an NSTR AP MLD that does not support simultaneous transmission and reception (e.g., if the AP MLD is an NSTR mobile AP MLD or an NSTR soft AP MLD, i.e., a mobile terminal operates as a soft AP MLD for tethering, etc.), the STA included in the STA MLD can perform a procedure for updating parameters only in a primary link. That is, in order to update parameters of other links (e.g., non-primary links) to other neighboring APs other than the primary link of the AP MLD, frames for parameter update can be transmitted and received only through the primary link.

[0143] Hereinafter, in the present invention, the NSTR AP MLD can be referred to as an NSTR soft AP MLD or an NSTR mobile AP MLD.

[0144] Also, when the AP is an NSTR AP MLD that does not support simultaneous transmission and reception (e.g., when it is an NSTR mobile AP MLD or an NSTR soft AP MLD, i.e., when a mobile terminal operates as a soft AP MLD for tethering, etc.), the NSTR AP MLD can transmit a beacon frame including information indicating that it is an NSTR AP MLD. For example, the NSTR AP MLD can set the value of a specific subfield included in the beacon frame to a specific value (e.g., "0" or "1"), and a non-AP STA MLD that receives a beacon frame can recognize that the AP MLD that transmitted the beacon frame is the NSTR AP MLD. Therefore, the specific subfield for indicating that it is an NSTR AP MLD may be set to a value different from the specific value (e.g., "1" or "0") when not indicating the NSTR AP MLD (e.g., the STR AP MLD or another AP MLD, etc.).

[0145] A specific subfield for indicating that it is an NSTR AP MLD may be indicated together with a capability-related subfield (e.g., MLD level capability) of a beacon frame, or may be included in a neighbor AP information field associated with an AP of a non-primary link of the NSTR AP MLD and transmitted. For example, a specific subfield for indicating that it is an NSTR AP MLD may be encoded and indicated together with a frequency separation for STR / AP MLD type indication, which is a capability-related subfield. That is, the specific subfield may be encoded together with a frequency separation for STA / AP MLD type indication indicating a distance for supporting STR, and indicated in a beacon frame. In this case, when the corresponding indicator indicates the type of AP MLD, it may indicate whether the AP MLD that transmitted the beacon frame is an NSTR AP MLD or not, depending on a set value (for example, it may indicate that it is not an NSTR AP MLD when set to '0', and that it is an NSTR AP MLD when set to '1').

[0146] The method of utilizing the subfield indicating whether or not the AP MLD is an NSTR AP MLD may be a method of explicitly indicating whether or not the AP MLD is an NSTR AP MLD.

[0147] As another example, the NSTR AP MLD may indicate that it is an NSTR AP MLD by an implicit method, rather than directly indicating that it is an NSTR AP MLD by a specific subfield. Specifically, the NSTR AP MLD may indicate that it has an NSTR link pair while indicating that it has two links that it can support, thereby implicitly indicating that it is an NSTR AP MLD. In this case, the NSTR AP MLD may set the Maximum Number Of Simultaneous Links subfield included in the beacon frame to 1 (or a pre-agreed value meaning 2) to indicate that it has two links that it can support. In this case, the NSTR AP MLD may set the NSTR Link Pair Present subfield included in the beacon frame to 1 or 0 to indicate that it has an NSTR link pair.

[0148] The AP MLD can inform the non-AP STA MLD that it is the NSTR AP MLD by an explicit or implicit method by transmitting a beacon frame by the above-mentioned method. The non-AP STA MLD can implicitly or explicitly recognize whether the AP MLD that transmitted the beacon frame is the NSTR AP MLD from the received beacon frame. If the AP MLD that transmitted the beacon frame is the NSTR AP MLD (i.e., if the beacon frame indicates that the AP MLD is the NSTR AP MLD by an explicit or implicit method), the non-AP STA MLD can perform a procedure for association or setup with the NSTR AP MLD only on the link on which the beacon frame was received. That is, the non-AP STA MLD can transmit and receive frames for association or setup with the NSTR AP MLD on the link on which the beacon frame was received (e.g., primary link). For example, frames for association or configuration with an AP connected via a link other than the primary link included in the NSTR AP MLD may be transmitted only via the primary link. In this case, an (ML)(Re) association request frame transmitted by the Non-AP STA MLD may be transmitted via a link other than the primary link (non-primary link).

[0149] At this time, the NSTR AP MLD may not indicate information about the AP of the non-primary link in the RNR element of the beacon frame (transmitted on the primary link) in order to prevent the non-AP STA MLD from attempting a setup procedure on the non-primary link. That is, the beacon frame transmitted by the AP of the NSTR AP MLD may not include / indicate the neighbor AP information field for the AP of the other link (of the same MLD). In this case, the non-AP STA MLD may not attempt to set up the NSTR AP MLD on the non-primary link after receiving the beacon frame because it cannot confirm information about the AP of the non-primary link. At this time, the non-AP STA MLD that receives a beacon frame from the NSTR AP MLD that does not include the neighbor AP information field for the AP of the non-primary link can implicitly recognize that the other AP is the NSTR AP MLD based on the fact that the number of simultaneously supported links of the AP that transmitted the beacon frame is two and information about other APs of the same MLD is not indicated, as described above.

[0150] Meanwhile, in a typical AP MLD, when an (ML) (Re) association request frame is received from a STA (MLD), an (ML) association response frame must be transmitted on the link on which the (ML) association request frame was received. However, in the NSTR AP MLD, a response to an (ML) association request frame received on a non-primary link can be made on the primary link (i.e., an (ML) association response frame can be responded to on the primary link).

[0151] This may be an acceptable operation because the NSTR AP MLD operation of transmitting on a non-primary link is somewhat restricted compared to a general AP, as described above. Furthermore, the NSTR AP MLD has an operation restriction that when a response to a (ML) association response frame is transmitted on a non-primary link, it must also start transmitting on a primary link. This may be an operation restriction considered to prevent the AP of the primary link from entering a BLIND state, as in the other embodiments of the present invention.

[0152] Therefore, when the NSTR AP MLD receives an (ML)(Re) association request frame on a non-primary link, it can respond with an (ML)(Re) association response frame on the primary link, or it can respond with an (ML)(Re) association response frame on both the primary link and the non-primary link at the same time. That is, the STA MLD that sent an (ML)(Re) association request frame on the non-primary link of the NSTR AP MLD knows that the response to the request frame it sent will be on the primary link, and can wait to receive an (ML)(Re) association response frame on the primary link.

[0153] The RNR element transmitted by the AP in the beacon frame may include a specific TBTT information field including the MLD Parameters field. In this case, when the MLD ID of the MLD Parameters field is set to "0", the STA MLD can recognize that the AP corresponding to the neighbor AP information field including the MLD Parameters field is included in the AP MLD that includes the AP that transmitted the beacon frame. That is, the STA MLD can recognize that the neighbor AP information field indicates information about other APs included in the same AP MLD as the AP that transmitted the beacon frame. In this case, the method by which the STA MLD analyzes / obtains this may be the same / similar to the operation that a conventional STA performs after receiving an RNR element.

[0154] However, since the NSTR Soft AP does not transmit a beacon frame through a non-primary link, it may be impossible to indicate information related to the beacon frame of another AP (non-primary link AP) through the RNR element. Furthermore, since the NSTR Soft AP MLD does not transmit a beacon frame through the non-primary link AP, it cannot support information related to the beacon frame when indicating the non-primary link AP basic information through the RNR element. For example, a non-primary link that does not transmit a beacon frame does not have information corresponding to the TBTT information count, TBTT information length, and neighbor AP TBTT offset subfields that should be indicated in the RNR element. Therefore, when the NSTR Soft AP MLD transmits an RNR element through the primary link AP, it may be necessary to set the TBTT-related fields of the neighbor AP information field corresponding to the non-primary link AP to a preset value.

[0155] The neighbor AP TBTT offset subfield of the TBTT information field (see FIG. 11(b)) is a subfield indicating information related to the next TBTT of another AP to be indicated. That is, the neighbor AP TBTT offset subfield included in the neighbor AP information field may include information on the next TBTT of the AP corresponding to the neighbor AP information field. As an example, when AP1 transmitting a beacon frame indicates information on AP2 using the RNR element (by the neighbor AP information field), the neighbor AP TBTT offset subfield corresponding to AP2 indicates how many TUs (Time Units, 1024 us) the next TBTT of AP2 has compared to the previous TBTT of AP1. In this case, the value indicated in the neighbor AP TBTT offset subfield is a value obtained by rounding down the TBTT offset to the nearest integer. That is, when an AP indicates a value of 10 in the neighbor AP TBTT offset subfield of another AP, the next TBTT of the other AP may have a time interval of 10 TUs or more and less than 11 TUs based on the previous TBTT of the AP.

[0156] However, when the AP of the primary link of the NSTR Soft AP MLD sets the neighbor AP TBTT offset subfield (1-octet) corresponding to the AP of the non-primary link, it may need to set it to a preset value (e.g., 254 or 255). This may be because the NSTR Soft AP does not transmit a beacon frame to the non-primary link and is unable to determine a target beacon transmission time (TBTT), which is a scheduled time for transmitting the next beacon frame. That is, the beacon frame transmitted by the NSTR Soft AP MLD on the primary link may need to set the neighbor AP TBTT offset subfield corresponding to the AP of the non-primary link to 254 and / or 255 using the RNR element. In this case, the neighbor AP TBTT offset subfield corresponding to the non-primary link may be present in a TBTT information field including an MLD parameters field in which the MLD ID subfield is set to 0.

[0157] Therefore, when a non-AP STA MLD receives a beacon frame of an NSTR Soft AP MLD and checks a TBTT information field in which the MLD ID subfield is 0 and the TBTT offset subfield is specified as 254 and / or 255 in the specific neighbor AP information field of the RNR element included in the beacon frame, the non-AP STA MLD can recognize that the specific neighbor AP information field is information about an AP (of the NSTR Soft AP MLD) operated on a non-primary link of the NSTR Soft AP MLD. In this way, when a non-AP STA MLD that receives a beacon frame of an NSTR Soft AP MLD checks information about an AP MLD operated on a non-primary link of the NSTR AP MLD, it must not transmit a probe request frame or an ML probe request frame to the NSTR Soft AP MLD on a non-primary link.

[0158] In addition, when the non-AP STA MLD recognizes that the received beacon frame is the beacon frame transmitted by the MLD, and the Neighbor AP TBTT Offset subfield corresponding to another AP of the same MLD as the AP (Reporting AP) that transmitted the beacon frame is indicated as 254 and / or 255, the non-AP STA MLD shall not transmit a probe request frame and an ML probe request frame to the other AP.

[0159] In addition, when the non-AP STA MLD recognizes that the received beacon frame is the beacon frame transmitted by the MLD, and the Neighbor AP TBTT Offset subfield corresponding to another AP of the same MLD as the AP (Reporting AP) that transmitted the beacon frame is indicated as 254 and / or 255, the non-AP STA MLD shall not transmit a probe request frame and an ML probe request frame to the other AP.

[0160] <MLD AP TBTT Offset Indication>

[0161] In one embodiment of the present invention described above, it was mentioned that the beacon frame transmitted by the NSTR Soft AP MLD can indicate the Neighbor AP TBTT Offset subfield corresponding to the AP of the non-primary link with a preset value (254 and / or 255). However, the Neighbor AP TBTT Offset subfield may be indicated as 254 or 255 even if it does not correspond to the AP of the non-primary link of the NSTR Soft AP MLD. As an example, when the TBTT offset of another AP grasped by the AP transmitting the beacon frame is 254 TU or more (254 TU or exceeding 254 TU), the said AP can indicate the Neighbor AP TBTT Offset subfield corresponding to the said other AP as 254 in the beacon frame. Also, when the AP transmitting the beacon frame cannot accurately grasp the TBTT offset of another AP, the said AP can indicate the Neighbor AP TBTT Offset subfield corresponding to the said other AP as 255.

[0162] However, since an AP in an MLD can always recognize the TBTT offsets of other APs in the MLD, it should not indicate (set) 255 when indicating (setting) the neighbor AP TBTT offset subfield corresponding to another AP (in the same MLD) using the RNR element.

[0163] Specifically, the neighbor AP information field included in the RNR element of the beacon frame may include a neighbor AP TBTT offset subfield indicating an offset between the times when the beacon frame is transmitted. In this case, the neighbor AP TBTT offset subfield indicates an offset value between the time when the beacon frame is transmitted and the time when the next beacon frame is transmitted by the AP corresponding to the neighbor AP TBTT offset subfield among the multiple APs included in the AP MLD (NSTR or STR AP MLD). In this case, the neighbor AP TBTT offset subfield cannot be set to a specific value according to a specific condition.

[0164] For example, when the neighbor AP TBTT offset subfield is included in the same AP MLD as the AP that transmitted the beacon frame, the neighbor AP TBTT offset subfield is not set to a specific value (e.g., "255"). In this case, the size of the neighbor AP TBTT offset subfield may be 8 bits, and in this case, the neighbor AP TBTT offset subfield is not set to the maximum value that can be indicated by the neighbor AP TBTT offset subfield (in the case of 8 bits, the values ​​from 0 to 255 are respectively corresponding, so the maximum offset that can be indicated by 8 bits may be 255). However, when the neighbor AP TBTT offset subfield is not included in the same AP MLD as the AP that transmitted the beacon frame (for example, when the AP is a legacy AP), the neighbor AP TBTT offset subfield may be set to a specific value (e.g., "255").

[0165] In a similar embodiment, the neighbor AP TBTT offset subfield may be analyzed so that a value set therein may differ according to a specific condition.

[0166] For example, when the neighbor AP TBTT offset subfield is set to a specific value (eg, '254'), the set value may be analyzed to be different, such as '254' or greater than '254', according to a specific condition.

[0167] Specifically, if an AP corresponding to a neighbor AP information field including a neighbor AP TBTT offset subfield is included in the same AP MLD as the AP that transmitted the beacon frame or in another MLD, and the neighbor AP TBTT offset subfield is set to a specific value (e.g., "254"), the station can interpret the value indicated by the neighbor AP TBTT offset subfield as 254 TUs. However, if the AP is not included in the same AP MLD as the AP that transmitted the beacon frame or in another MLD (e.g., if the AP is a legacy AP or an AP not included in the MLD), and the neighbor AP TBTT offset subfield is set to a specific value (e.g., "254"), the station can interpret the value indicated by the neighbor AP TBTT offset subfield as 254 TUs or more.

[0168] Generally, the reason why a conventional AP transmits TBTT offset information along with basic information about neighboring APs using a beacon frame may be to help a STA receiving a beacon frame quickly obtain basic information about other APs and receive beacon frames from other APs more efficiently using the confirmed TBTT offset information.

[0169] However, the neighbor AP TBTT offset subfield included in the conventional beacon frame is composed of one octet and is designed to indicate only a TBTT offset of up to 254TU. This may be a neighbor AP TBTT offset subfield design that compromises the overhead of the beacon frame and the information that can be indicated by excluding information support regarding the case where a TBTT offset of 254TU or more is present when considering the maximum TBTT offset that other APs may have ((2^16) or (2^16)-1TU when considering the configurable beacon interval).

[0170] However, when the AP MLD indicates information about other APs in the MLD using a beacon frame, an additional MLD AP TBTT offset subfield may be included in the transmission to more accurately notify the TBTT offset of the other APs. The MLD AP TBTT offset subfield may be included in the TBTT information field corresponding to other APs in the same MLD when the AP MLD transmits a beacon frame. In this case, when the neighbor AP TBTT offset subfield and the MLD AP TBTT offset subfield are both indicated in a specific TBTT information field, the neighbor AP TBTT offset subfield may be indicated as a preset value (which may be 254 or 255). The MLD AP TBTT offset subfield is a subfield with a size of 2 octets, and may be used to indicate a TBTT offset value when the TBTT offset between the AP (Reporting AP) that transmits the beacon frame and another AP (Reported AP) in the same MLD exceeds 254TU. Furthermore, the MLD AP TBTT offset subfield may be included in the TBTT information field only when the TBTT offset of another AP in the same MLD exceeds 254 TU when the AP MLD transmits a beacon frame and the existing neighbor AP TBTT offset subfield cannot indicate an accurate TBTT offset.

[0171] When the STA MLD checks the TBTT information field including the MLD AP TBTT offset subfield in the RNR element included in the beacon frame received from a specific AP, the STA can check the TBTT offset of the AP corresponding to the TBTT information field based on the value indicated in the MLD AP TBTT offset subfield. In this case, in order to know whether the TBTT information field included in the beacon frame includes the MLD AP TBTT offset subfield, the STA may check based on the value of the TBTT information length subfield (in the TBTT Information Header (sub) field of each neighbor AP information field) corresponding to each TBTT information field. That is, when the STA recognizes that the TBTT information field includes the MLD AP TBTT offset subfield based on the value of the TBTT Information Length subfield, the STA can check the TBTT offset of the AP corresponding to the TBTT information field based on the value indicated in the MLD AP TBTT offset subfield. In this case, when the MLD AP TBTT offset subfield of a specific TBTT information field indicates 0 or a preset value (or a value less than 254), the STA MLD can confirm the TBTT offset of the AP corresponding to the specific TBTT information field based on the value of the neighbor AP TBTT offset subfield.

[0172] FIG. 12 shows yet another example of a TBTT information field format according to an embodiment of the present invention.

[0173] 12, the TBTT information field may have a configuration including an MLD AP TBTT offset subfield. The MLD AP TBTT offset subfield may be included only in a beacon frame transmitted by an AP of the AP MLD. Also, the MLD AP TBTT offset subfield may be included only in a TBTT information field corresponding to another AP of the same MLD as the AP transmitting the beacon frame.

[0174] As an example, in a beacon frame transmitted by a specific AP of an AP MLD, in order to indicate that the TBTT offset of another AP of the same MLD is 300TU, the TBTT information field corresponding to the other AP may be used as a format including an MLD AP TBTT offset subfield. In this case, the neighbor AP TBTT offset subfield of the TBTT information field corresponding to the other AP may be indicated as 254 or 255, and the MLD AP TBTT offset subfield may be indicated as a value corresponding to 300TU (e.g., 300, 299, or (300-254)). In this case, the above-mentioned MLD AP TBTT offset subfield is an example subfield name, and subfields having the same purpose may be defined with different names.

[0175] FIG. 13 illustrates an example of a TBTT information length subfield indicating a TBTT information field including an MLD AP TBTT offset subfield according to an embodiment of the present invention.

[0176] Referring to FIG. 13, the type of content included in the TBTT information field may be indicated by the TBTT information length subfield. The TBTT information length subfield may be a subfield included in the TBTT information header field in the neighbor AP information field included in the RNR element. That is, the RNR element transmitted in the beacon frame may include a plurality of neighbor AP information fields, and the TBTT information fields included in each neighbor AP information field may have a structure including different amounts and types of content. In this case, since the TBTT information fields included in each neighbor AP information field may include different amounts and types of content, information regarding the content (and format) indicated by each TBTT information field is indicated by the TBTT information header field.

[0177] That is, the STA can parse each neighbor AP information field in the RNR element of the beacon frame received through the AP based on the information indicated in the TBTT information header. At this time, each parsed neighbor AP information field may indicate information on a neighbor AP or another AP of the same MLD. At this time, if the value of the TBTT information length subfield included in the TBTT information header field indicates a content configuration including an MLD AP TBTT offset subfield as shown in FIG. 13, the STA can check the TBTT offset of the AP corresponding to the TBTT information field based on the value indicated in the MLD AP TBTT offset subfield.

[0178] Alternatively, a restriction may be applied such that an AP MLD must manage the TBTT offset between APs it operates so as not to exceed 254 TU or to exceed 255 TU.

[0179] In this case, the AP MLD may need to adjust the beacon interval of the AP it operates on each link and / or the TBTT time (setting) of the BSS operated by each AP so that the TBTT time difference between APs belonging to the MLD does not exceed 254TU or 255TU. In this case, the adjustment of the beacon interval and the TBTT time is an example of a method for changing the TBTT interval of each AP in the MLD, and other implementations may be applied that adjust the TBTT offset so as not to exceed a specific time value (254TU or 255TU). In addition, a method for the AP MLD to prevent the TBTT time difference of each AP it operates from exceeding a specific interval (254TU or 255TU) does not need to be defined separately.

[0180] In this way, when the AP MLD adjusts the TBTT time difference of each AP it operates to 254 TU or less or less than 255 TU, the neighbor AP TBTT offset subfield value transmitted to other APs of the same MLD in the RNR element transmitted by the specific AP in the beacon may indicate only a value of 253 or 254 or less. Furthermore, when the specific AP MLD manages the TBTT time difference of the AP it operates to 254 TU or less or less than 255 TU, the neighbor AP TBTT offset subfield transmitted by the specific AP belonging to the specific AP MLD, which corresponds to other APs belonging to the same AP MLD (the specific AP MLD), may indicate (have) only a value of 254 or less.

[0181] As described above, when the AP MLD maintains the TBTT time difference of each AP operated by the non-AP STA to be equal to or less than 254TU or less than 255TU, the non-AP STA may need to analyze the neighbor AP TBTT offset subfield of the beacon frame received from the AP of the AP MLD in a manner different from the above-mentioned analysis method. In this case, the above-mentioned analysis method may mean an analysis method when the value of the neighbor AP TBTT offset subfield is indicated as 254. That is, the above-mentioned analysis method may analyze that the time interval between the previous TBTT of the Reporting AP and the next TBTT of the Reported AP (transmitted after the previous TBTT) is equal to or greater than 254TU when the value of the neighbor AP TBTT offset subfield is indicated as 254. In this case, the other analysis method may analyze that the time interval between the previous TBTT of the Reporting AP and the next TBTT of the Reported AP (transmitted after the previous TBTT) is equal to or greater than 254TU and less than 255TU when the value of the neighbor AP TBTT offset subfield is indicated as 254. Alternatively, another analysis method may be to analyze that when the value of the neighbor AP TBTT offset subfield is indicated as 254, the time interval between the previous TBTT of the Reporting AP and the next TBTT of the Reported AP (transmitted after the previous TBTT) is 254 TU.

[0182] This is because the TBTT time difference of each AP operated by AP MLD has been adjusted by AP MLD to less than 254 TU or less than 255 TU, so the existing neighbor AP TBTT offset subfield has the meaning of "254 TU or more" and can be an analysis method that reflects the operating characteristics of AP MLD.

[0183] That is, when a non-AP STA receives a neighbor AP TBTT offset subfield for another AP in the same AP MLD via a beacon received from a specific AP in the AP MLD, if the value of the subfield is 254, it can analyze that the TBTT offset of the other AP is 254 TU or (greater than 254 TU and less than 255 TU).

[0184] On the other hand, even when a non-AP STA receives a beacon frame from an AP in AP MLD, if the neighbor AP TBTT offset subfield included in the beacon frame that is not for an AP in the same AP MLD is indicated as 254, i.e., if the neighbor AP TBTT offset subfield for a legacy AP and an AP that is not MLD is indicated as 254, the non-AP STA must interpret that a TBTT offset of 254 TU or more has been indicated.

[0185] In this case, the method for the non-AP MLD to distinguish whether the specific neighbor AP TBTT offset subfield is for another AP of the same AP MLD may be based on information of the MLD Parameters subfield included in the same TBTT information field as the specific neighbor AP TBTT offset subfield. More specifically, if the MLD ID subfield value of the MLD Parameters subfield included in the same TBTT information field as the specific neighbor AP TBTT offset subfield is 0, the non-AP STA can analyze that the specific neighbor AP TBTT offset subfield is an AP of the same MLD as the AP that transmitted the beacon frame.

[0186] That is, when the neighbor AP TBTT offset subfield of the TBTT information field in which the MLD ID subfield value is 0 is indicated as 254, the non-AP STA can analyze that the neighbor AP TBTT offset subfield indicates a TBTT offset of 254 TU or more and less than 255 TU. In this case, the non-AP may further consider whether or not the beacon frame includes an ML element (whether or not the AP that transmitted the beacon frame is MLD) in order to analyze the neighbor AP TBTT offset subfield.

[0187] That is, when the MLD ID subfield value is not 0 (for example, 1 to 255) and the neighbor AP TBTT offset subfield of the TBTT information field indicates 254, the non-AP STA can interpret that the neighbor AP TBTT offset subfield indicates a TBTT offset of 254 TU or more.

[0188] <Non-primary link set-top and management>

[0189] As mentioned above, the NSTR AP MLD cannot transmit beacon frames, probe response frames, or ML (Multi-link) probe response frames on non-primary links. Therefore, a STA MLD that wishes to be connected to the NSTR AP MLD must transmit (ML) probe request frames only on the link on which the NSTR AP MLD transmitted a beacon frame.

[0190] The ML probe request frame transmitted by the STA of the EHT non-AP STA MLD may include EHT Capability information and a Multi-Link element in addition to the information included in the probe request frame transmitted by the conventional HE STA. In this case, the Multi-Link element included in the ML probe request frame can play a role in which the MLD transmitting the ML probe request frame requests additional information on the AP of another link to the AP MLD.

[0191] For example, when a non-AP STA MLD transmits an ML probe request frame, it can request the AP MLD to further respond with complete information or partial information on the AP of another link using the Multi-Link element of the ML probe request frame. That is, it can request the AP MLD to transmit all or part of the parameters related to the link of another AP included in the same AP MLD to the AP receiving the ML probe request frame.

[0192] For example, when all or part of the parameters related to an AP connected via a non-primary link are updated, a station included in the non-AP STA MLD can request the AP connected via a primary link to transmit all or part of the updated parameters related to other APs of the non-primary link.

[0193] In this case, the complete information is requested / responded to mean that the AP of the other link (Reported AP) is requested / responded to with the same level of information as the AP (Reporting AP) that responds with the ML probe response frame, whereas the partial information is requested / responded to mean that only the information on the AP of the other link requested by the STA is responded to.

[0194] When additional information about APs of other links is requested in the ML probe request frame received on a particular link, the AP MLD that sent the beacon frame can respond using an ML probe response frame to not only provide information about the AP of the particular link, but also the requested additional information about the AP of the other link.

[0195] In this case, when the STA MLD transmits an ML probe request frame on a specific link and requests complete information on the AP of another link, the AP MLD must provide information on the AP of the other link at the same level as the information on the AP of the specific link using an ML probe response frame that responds on the specific link. In other words, the STA MLD that receives a response of complete information on the AP of another link on a specific link can obtain the same level of information on the AP of the other link as when it directly receives an ML probe response from the AP of the other link.

[0196] In this case, when the STA MLD transmits an ML probe request frame on a specific link and requests partial information on the AP of another link, the AP MLD can provide only requested information (requested element information) among information on the AP of the other link using an ML probe response frame that responds on the specific link. In other words, the STA MLD that receives partial information on the AP of the other link on a specific link can further obtain only the information that it requested from the AP of the other link. In this case, the STA MLD that requests partial information on the AP of the other link can transmit an ML probe request frame including information indicating further information to be obtained (which may be indicated by the Requested element IDs field) together with the link ID corresponding to the other link. Therefore, when the ML probe request frame received on a specific link includes information indicating information on the other link (Request element IDs field), the AP MLD can further indicate the indicated information on the other link in the ML probe response frame.

[0197] In this case, when transmitting an ML probe request frame on a particular link, the STA MLD can set the Complete Profile subfield (of the Per-STA Control field included in the Multi-Link element) corresponding to the other link to 0 or 1 to indicate whether it is requesting complete information or partial information for the other link.

[0198] In this case, the additional information (Complete and Partial) for the other AP may be transmitted by a Per-STA profile included in a Multi-link element of an ML probe response frame. The Per-STA profile is a field included in the Multi-link element 0 or more than 0, and may include information of other STAs (AP and non-AP STAs) that exist in the same MLD as the STA (AP and non-AP STA) that transmits a frame including the Multi-Link element. In this case, the Per-STA profile has a configuration including a Complete Profile subfield, and complete information (information at the same level as the STA (AP and non-AP) that transmits a frame including the Multi-Link element) of the other STA (AP and non-AP STA) corresponding to (corresponding to) the Per-STA profile in which the Complete Profile subfield is indicated as 1 can be obtained from the Per-STA profile. However, a parameter / element that means the same information as the STA (AP and non-AP) that transmits the Per-STA profile may be omitted according to an inheritance rule. The inheritance rule may mean that if a parameter or element is not specified, the value of the same parameter or element (specified for other STAs (AP and non-AP)) that has already been specified is inherited and utilized to prevent repeated specification of the same parameter or element. That is, if a value of parameter1 is specified for STA1 and a value of parameter1 is not specified for STA2, the inheritance rule may analyze that the value of parameter1 for STA2 is specified to be the same as the value of parameter1 for STA1.

[0199] At this time, the Per-STA profile subelement included in the Multi-link element transmitted by the NSTR AP MLD may have a configuration that does not include a Beacon Interval subfield for indicating the interval at which a beacon is transmitted. That is, when the NSTR AP MLD indicates a Per-STA profile subelement corresponding to an AP of a non-primary link in the Multi-link element, the Beacon Interval Present subfield must be set to 0. This may be because the AP operated in the non-primary link of the NSTR AP MLD does not transmit a beacon frame, and therefore there is no separate period of the beacon frame. That is, even if the Complete Profile subfield (in the Per-STA Control field) is indicated as 1, the Beacon Interval Present subfield of the Per-STA profile subelement corresponding to the AP of a non-primary link of the NSTR AP MLD may be indicated as 0. That is, the beacon interval information for the AP of a non-primary link does not exist even when complete information is indicated.

[0200] Similarly, DTIM information (DTIM Count and DTIM Period information) for a non-primary link AP may not be present even when complete information is indicated. That is, the Per-STA profile corresponding to a non-primary link AP in the NSTR AP MLD may be indicated as 1 in the Complete Profile subfield (in the Per-STA Control field) and 0 in the DTIM Info Present subfield.

[0201] That is, since beacons are not transmitted on non-primary links, even if a non-AP STA MLD requests all information (or all updated information) for other APs of non-primary links through the AP of the primary link of the AP MLD (i.e., completeness is set to '1'), the beacon interval and DTIM information for the AP of the non-primary link may not be present in the ML probe response frame. That is, the beacon interval and DTIM information may not be included in the Per-STA profile subelement for the AP of the non-primary link included in the ML probe response frame.

[0202] In this case, even if all information (or all updated information) for other APs of non-primary links is requested, the AP MLD does not need to include the beacon interval and DTIM information for the APs of non-primary links in the ML probe response frame. Therefore, in this case, the AP MLD can transmit the beacon interval present subfield and the DTIM information present subfield set to a value (e.g., "0") indicating that the respective fields are not included.

[0203] Since the NSTR AP MLD does not transmit a beacon frame to a non-primary link, it does not need to indicate DTIM information and beacon interval information when indicating information about the AP of the non-primary link. That is, the NSTR AP MLD may need to always indicate the DTIM information present subfield of the Per-STA profile (more precisely, the STA Control field) corresponding to the AP of the non-primary link as 0. That is, the NSTR AP MLD may need to always indicate the Beacon Interval Present subfield in the Per-STA profile corresponding to the AP of the non-primary link as 0. Therefore, even if the NSTR AP MLD receives an ML probe request frame requesting complete information from a non-AP STA MLD or receives an (ML)(Re) association request frame, the NSTR AP MLD may need to always indicate the Beacon Interval Present subfield and the DTIM information present subfield in the Per-STA profile corresponding to the AP of the non-primary link as 0.

[0204] Alternatively, since the NSTR AP MLD does not transmit a beacon frame to the non-primary link, it may be necessary to set the subfields of Beacon Interval, DTIM Count, and DTIM Interval to pre-promised values ​​in the Per-STA profile corresponding to the AP of the non-primary link. This may be an operation considered to maintain the same Per-STA profile configuration as a general AP MLD (e.g., STR AP MLD) when the NSTR AP MLD transmits (responds to) complete information for the AP of the non-primary link. That is, the STA MLD requests complete information for a specific link from the AP MLD using an ML probe request frame, etc., and then the complete information for the AP of the specific link is expected to be responded to in the response frame. In this case, if the complete information responded by the NSTR AP MLD has a different Per-STA profile configuration from the complete information responded by the STR AP MLD, the implementation complexity of the process of the STA MLD acquiring information according to the Per-STA profile may increase. Therefore, even if the AP of the non-primary link does not transmit a beacon frame, the NSTR AP MLD can use a Per-STA profile with the same configuration as the Per-STA profile used when the general AP MLD responds with complete information when responding with complete information of the non-primary link. In this case, the Per-STA profile corresponding to the AP of the non-primary link of the NSTR AP MLD may have the Beacon Interval subfield, the DTIM Count subfield, and the DTIM Interval subfield set to preset values, respectively. As an example, when the NSTR AP MLD transmits complete information for the AP of the non-primary link, each bit of the Beacon Interval subfield of the non-primary link can be set to all 0, all 1, or in a predetermined manner.For example, when the NSTR AP MLD transmits complete information for the AP of the non-primary link, it can set each bit of the DTIM Count subfield of the non-primary link to all 0's, all 1's, or a predetermined manner. For example, when the NSTR AP MLD transmits complete information for the AP of the non-primary link, it can set each bit of the DTIM Interval subfield of the non-primary link to all 0's, all 1's, or a predetermined manner.

[0205] Alternatively, since a beacon frame is not transmitted to the non-primary link, the NSTR AP MLD may set the Beacon Interval, DTIM Count, and DTIM Interval subfields in the Per-STA profile corresponding to the AP of the non-primary link to values ​​associated with the beacon frame of the primary link. This may be an operation considered to maintain the same Per-STA profile configuration as described above. In this case, the Beacon Interval subfield, DTIM Count subfield, and DTIM Interval subfield of the Per-STA profile corresponding to the AP of the non-primary link may be set to values ​​associated with the beacon frame transmitted on the primary link, respectively. As an example, when transmitting complete information for the AP of the non-primary link, the NSTR AP MLD may set the Beacon Interval subfield of the non-primary link to a value indicating (meaning) the beacon interval of the primary link. As an example, when transmitting complete information for the AP of the non-primary link, the NSTR AP MLD may set the DTIM Count subfield of the non-primary link to the DTIM Count value of the primary link. As an example, when the NSTR AP MLD transmits complete information for the AP of a non-primary link, it can set the DTIM Interval subfield of the non-primary link to a value indicating (meaning) the DTIM interval of the primary link.

[0206] Alternatively, since the NSTR AP MLD does not transmit a beacon frame to the non-primary link, the Beacon Interval, DTIM Count, and DTIM Interval subfields of the Per-STA profile corresponding to the AP of the non-primary link may be set to values ​​having a specific purpose by the AP MLD. Furthermore, the Beacon Interval subfield of the non-primary link may be set to a value having a specific purpose (virtual beacon interval), for example, a value for calculation. Conventionally, the beacon interval of Wi-Fi literally means a value related to the time interval at which a beacon frame is transmitted, but is also used as a time unit for the operation of various BSSs. For example, a unit such as JointFailureTimeout and QueryFailureTimeout primitives is defined as a beacon interval, and a Listen interval field, a PRAW Start offset subfield, an AID Request Interval field, an AID Switch Count field, an AID Response Interval field, a Minimum Transmission Interval subfield, a Channel Quality Measurement Duration, a Color Switch Countdown (BSS Color Change Announcement element) subfield, etc. indicate an interval / duration using the beacon interval (or TBTT) as a basic unit. As such, since the beacon interval has a meaning of a value related to an interval at which a beacon frame is actually transmitted, and is a value used as a unit for various primitives and fields, it may be necessary to define (indicate, set) a beacon interval for a non-primary link in order to be used as a unit for the above-mentioned primitives / subfields even if a beacon frame is not actually transmitted to the non-primary link.

[0207] That is, even if a beacon frame is not transmitted to the non-primary link, the NSTR AP MLD can indicate the Beacon Interval subfield of the Per-STA profile corresponding to the AP of the non-primary link as a beacon interval value to be used as a time unit of the non-primary link. In this case, the non-AP MLD can recognize (check, calculate) the duration and interval of the above-mentioned primitives and fields (used as a beacon interval unit) based on the value indicated in the Beacon interval subfield of the Per-STA profile corresponding to the AP of the non-primary link. In this case, the DTIM Interval subfield and DTIM Count subfield of the Per-STA profile corresponding to the AP of the non-primary link may also be set according to the BSS operation purpose of the AP MLD, and the non-AP MLD operating the STA on the non-primary link may need to operate based on the set value when operating the STA on the non-primary link.

[0208] Meanwhile, the method of setting subfields related to non-primary link beacons of the NSTR AP MLD described above (Beacon Interval, DTIM Count, DTIM Interval, etc.) may be equally applied to other frames and subfields (transmitted on the primary link or non-primary link) containing information related to non-primary link beacons as well as the Per-STA profile transmitted on the primary link.

[0209] In addition, a non-AP STA MLD that wishes to associate with the NSTR AP MLD may need to use the beacon interval of the primary link of the NSTR AP MLD as the unit of the Listen Interval field transmitted while requesting a setup for the primary link and the non-primary link. That is, a non-AP STA MLD that transmits a Listen Interval field to the NSTR AP MLD must calculate and set the unit of the Listen Interval field as the beacon interval of an AP operating on the primary link of the NSTR AP MLD. In this case, the Listen Interval field may be a field indicating information related to a period (time) at least one STA changes to a wake state in order for a non-AP STA MLD performing Multi-Link (Re)Association to receive a beacon frame. In this case, the Listen Interval field may indicate a value derived when a ListenInterval parameter is indicated in an MLME primitive.

[0210] In this case, when the non-AP STA MLD transmits a Listen interval field to another AP MLD (e.g., STR AP MLD) other than the NSTR AP MLD, it may be necessary to set the unit of the Listen interval field to the maximum value of the beacon interval of the link (AP) on which it is to perform set-top. As an example, when the non-AP STA MLD is to perform multi-link setup with the AP MLD and link 1 or link 2, the non-AP STA MLD may set the unit of the Listen interval field included in the ML association request frame to the larger value of the beacon interval of the link 1 (AP) and the beacon interval of link 2. In other words, if the beacon interval of link 1 is 100 ms and the beacon interval of link 2 is 50 ms, the unit of the Listen interval subfield transmitted by the non-AP STA MLD may be in units of 100 ms.

[0211] Generally, when an AP and a STA complete the setup, the STA can learn and track (update) the operation parameters and element changes of the AP while receiving the beacon frame transmitted by the AP. The beacon frame also plays a role of providing information including the Timestamp field for the STAs in the BSS to achieve time synchronization.

[0212] However, since the NSTR AP MLD does not transmit beacon frames on non-primary links as mentioned above, the STA MLD set up with the NSTR AP MLD may need to perform additional operations to track (update) parameters / elements and maintain time synchronization for the non-primary links.

[0213] According to an embodiment of the present invention, the non-AP STA MLD combined with the NSTR AP MLD can check the change sequence (in the MLD parameter field of the RNR element) of the non-primary link after receiving a beacon frame on the primary link and transmit an ML Probe Request. In this case, the ML probe request frame transmitted by the non-AP STA MLD may be transmitted for the purpose of requesting changed parameters and element information of the non-primary link. In this case, the ML probe request frame may request complete information of the non-primary link by setting the complete profile of the Per-STA profile corresponding to the non-primary link (and the AP of the non-primary link) to 1 and transmitting it. Alternatively, the ML probe request frame transmitted by the STA MLD for the purpose of updating the parameters / elements of the non-primary link may request updated information, not complete / partial information, for the non-primary link.

[0214] In other words, even if multiple links are formed between the non-AP STA MLD and the AP MLD, frames for performing association, reassociation, and / or parameter update procedures may be performed only on the primary link. For example, when the STA recognizes that parameters for the AP of a non-primary link have been updated from a specific field (e.g., change sequence or BSS parameter change count subfield, etc.) indicating whether or not the parameter for the link of another AP included in the neighbor AP information included in the beacon frame is an update, the non-AP STA MLD can request transmission of updated parameters on a primary link other than the non-primary link of the other AP. In other words, the non-AP MLD cannot transmit a frame (e.g., a probe request frame, etc.) for requesting updated parameters on a non-primary link.

[0215] As an example, after setting up with the NSTR AP MLD, the non-AP STA MLD that requests information for updating parameters / elements of the non-primary link can request the changed parameters / elements from the AP of the non-primary link by setting the Updated Profile subfield of the Per-STA profile corresponding to the non-primary link to 1 in the ML probe request frame transmitted on the primary link. When the Updated Profile subfield is indicated as 1 in the Per-STA profile (corresponding to the non-primary link) of the received ML probe request frame, the NSTR AP MLD can respond with an ML probe response frame including information (parameters and elements) of the changed non-primary link.

[0216] In this case, the Per-STA Profile field of the ML Probe Request frame transmitted by the non-AP STA MLD may include an Updated Profile subfield and a Recorded Change Sequence subfield. The Recorded Change Sequence subfield indicates the latest Change Sequence value maintained by the non-AP STA MLD for the non-primary link, and the AP MLD can check / determine the type of Updated Information based on the value indicated by the Recorded Change Sequence subfield.

[0217] As an example, the NSTR AP MLD may change Parameter 1 while increasing the Change Sequence number of the non-primary link from 100 to 101, and may further change Parameter 2 while increasing the Change Sequence number from 101 to 102. In this case, the STA MLD may request updated information of the non-primary link while transmitting an ML probe request frame. In this case, the NSTR AP MLD may respond with an ML probe response frame including both Parameter 1 and Parameter 2 when the non-AP STA MLD indicates that the Recorded Change Sequence subfield is 100, and may respond with an ML probe response frame including only Parameter 2 when the non-AP STA MLD indicates that the Recorded Change Sequence subfield is 101.

[0218] In this case, the Non-AP STA MLD does not use a separate Updated Profile subfield to request an Updated Profile, and may indicate the Complete Profile subfield as 0. That is, the way in which the Non-AP STA MLD requests an Updated Profile may be to set the Complete Profile subfield to 0, and in this case, a separate Updated Profile subfield may not be included in the Per-STA profile.

[0219] FIG. 14 illustrates an example of a Per-STA Profile subelement format according to an embodiment of the present invention.

[0220] Referring to FIG. 14(a), the Per-STA profile sub-element may have a configuration including a STA Control field. The STA Control field (see FIG. 14(b)) indicates information for indicating the type of field included in the STA profile (see FIG. 14(a)) of the Per-STA profile sub-element. In this case, in a specific Per-STA profile sub-element transmitted by another AP MLD other than the NSTR AP MLD, when the Complete Profile sub-field of the STA Control field is indicated as 1, the MAC Address Present sub-field, the Beacon Interval Present sub-field, and the DTIM Information Present sub-field may all need to be indicated as 1. However, as described above, since the NSTR AP MLD does not transmit a beacon frame to a non-primary link, information related to a beacon frame of a non-primary link may not be indicated in the Per-STA profile sub-element corresponding to the non-primary link. That is, even if the Complete Profile subfield of a specific Per-STA profile subelement (corresponding to an AP of a non-primary link) transmitted by the NSTR AP MLD is indicated as 1, the Beacon Interval Present subfield and the DTIM Information Present subfield may be indicated as 0.

[0221] Also, as described in the above embodiment, the non-AP STA MLD that transmits the ML probe request frame to the NSTR AP MLD can request the AP of the primary link for updated information of the AP of the non-primary link by indicating the Updated Profile subfield of the STA Control field (included in the Per-STA profile subelement corresponding to the AP of the non-primary link) as 1. In this case, the non-AP STA MLD can indicate the Recorded Change Sequence value, which is information related to the time when the non-primary link AP information is updated, using the Recorded Change Sequence subfield (see FIG. 14(c)). In this case, the Recorded Change Sequence subfield may be a subfield included in the STA profile. After receiving the ML probe request frame of the non-AP STA MLD received via the primary link, the NSTR AP MLD can determine the information of the AP of the non-primary link that responds to the non-AP STA MLD by comparing the value of the Recorded Change Sequence subfield included in the ML probe request frame with the Change Sequence value of the current AP of the non-primary link.

[0222] FIG. 15 illustrates an example of a process in which a non-AP MLD set up with a Non-Simultaneous Transmission and Reception (NSTR) Soft AP MLD updates information on a non-primary link according to an embodiment of the present invention.

[0223] 15, the NSTR AP MLD may indicate that the parameters of AP2 have been changed by using a beacon frame transmitted by AP1 operating on the primary link, link 1, after changing the parameters of AP2 operating on link 2, which is a non-primary link. In this case, the information that the parameters of AP2 have been changed may be indicated by indicating that the Change Sequence subfield value corresponding to AP2 in the RNR element included in the beacon frame transmitted by AP1 is increased by 1 from the value indicated in the immediately preceding beacon frame.

[0224] Non-AP STA MLD can recognize the fact that the parameters of AP2 have been updated after receiving the beacon frame sent by AP1 through STA1. Non-AP STA MLD can send an ML probe request frame through STA1 to obtain the changed parameter information of AP2.

[0225] The ML probe request frame transmitted by the non-AP STA MLD via STA1 may be configured to include a Per-STA profile sub-element corresponding to AP2 in the ML element, and the Per-STA profile sub-element may include an indicator indicating whether a complete profile or an updated profile is requested.

[0226] After receiving an ML probe request frame from STA1 on the primary link, the NSTR AP MLD can respond to STA1 by including the requested information of AP2 (complete or updated information) in an ML probe response frame.

[0227] The non-AP STA MLD, which receives the requested information about AP2 from the NSTR AP MLD in an ML probe response frame, can complete the parameter update for the non-primary link to which the beacon frame is not transmitted by updating the parameters for AP2.

[0228] <Broadcast ML Probe Response>

[0229] According to an embodiment of the present invention, the NSTR AP MLD may transmit a broadcast ML probe response frame over the primary link when information related to an AP operated over a non-primary link is changed. When the Non-AP STA MLD receives a broadcast ML probe response frame transmitted by the NSTR AP MLD over the primary link, it may need to update information about the non-primary link (AP). In this case, the broadcast ML probe response frame may not be transmitted in response to an ML probe request frame transmitted by a specific STA, but may be an ML probe request frame transmitted by the NSTR AP MLD without a separate request.

[0230] The broadcast ML probe response frame includes a Per-STA profile sub-element corresponding to the AP of the non-primary link, and plays a role of helping the non-AP STA MLD to update changed parameters and elements of the non-primary link. Since the (Recorded) Change Sequence of the non-primary link maintained by each non-AP STA may be different from each other, the broadcast ML probe response frame may include complete information on the AP of the non-primary link. In this case, the broadcast ML probe response frame may be transmitted together with the DTIM beacon frame.

[0231] Therefore, a non-AP STA MLD may need to receive a broadcast ML probe response frame while receiving the next DTIM frame using a beacon frame if the Change Sequence Number corresponding to the AP of the non-primary link is different from the Change Sequence it maintains (recorded).

[0232] In this case, the parameter update procedure of the non-primary link using the above-mentioned broadcast ML probe response frame may be performed using a broadcast ML association response frame. In this case, the method of configuring the Per-STA profile sub-element of the broadcast ML association response frame and the procedure of updating the MLD of the receiving STA are the same as the embodiment of the above-mentioned broadcast ML probe response frame, and detailed description thereof will be omitted.

[0233] FIG. 16 is a flowchart illustrating an example of a procedure in which a non-AP STA MLD associated with an NSTR AP MLD updates parameters of a non-primary link according to an embodiment of the present invention.

[0234] After receiving a beacon frame through the primary link, the non-AP STA MLD checks the Change Sequence (in the MLD Parameter field of the RNR element) of the non-primary link. If the checked Change Sequence value of the non-primary link is different from the Change Sequence value maintained (recorded) by the non-AP STA MLD, the non-AP STA MLD can transmit an ML probe request frame through the primary link. In this case, the ML probe request frame may include a subfield indicating whether to request complete information or updated information for the AP of the non-primary link. In addition, the ML probe request frame requesting updated information may also include a subfield indicating the Change Sequence value maintained (recorded) by the non-AP STA MLD. Thereafter, the non-AP STA MLD that has received a ML probe response frame from the AP MLD updates parameters based on the information of the AP of the non-primary link included in the responded ML probe response frame.

[0235] <Time Sync Management for Non-Primary Links>

[0236] As mentioned above, the beacon frame transmitted by the AP not only transmits various parameters and element information, but also helps the STAs in the BSS to synchronize time. The TimeStamp field included in the beacon frame indicates the TSF (timing synchronization function) timer value at the time when the data symbol containing the first bit of the TimeStamp field appears at the transmit antenna connector, and the STA that receives the TimeStamp field can synchronize its own TSF timer with the AP based on the received TimeStamp field value.

[0237] In this way, the AP and STA can operate while maintaining time synchronization based on the TimeStamp value included in the beacon frame and perform timing-based operations. However, NSTR AP MLD cannot transmit beacon frames on non-primary links, so among STAs in Non-AP STA MLD, STAs that are associated with a non-primary link AP of NSTR AP MLD must use a method other than beacon frames to maintain time synchronization with the AP.

[0238] In order to maintain time synchronization with the AP of the non-primary link of the NSTR AP MLD, the associated non-AP STA may need to use the TimeStamp of the TIM frame transmitted by the AP. Since the TIM frame has a configuration including a TimeStamp field having the same function as a beacon frame, the STA that receives the TIM frame from the AP of the non-primary link of the NSTR AP MLD may need to manage the TFS timer using the TimeStamp field included in the TIM frame. However, since the NSTR AP MLD may be restricted from starting transmission on the non-primary link without occupying the primary link, it may be necessary to transmit a TIM frame on the non-primary link at the same time as transmitting a beacon frame on the primary link. In other words, the non-AP STA MLD associated with the NSTR AP MLD may need to prepare to receive a TIM frame on the non-primary link in accordance with the TBTT of the primary link.

[0239] In yet another embodiment of the present invention, when the AP MLD is an NSTR AP MLD that does not support simultaneous transmission and reception, the same TSF timer may be used in each link for multiple APs included in the NSTR AP MLD, and the TSF timer used at this time may be the TSF timer of the primary link. That is, when the AP MLD is an NSTR AP MLD, a link (non-primary link) for an AP affiliated with the NSTR AP MLD can use the TSF timer of the primary link.

[0240] That is, the non-AP STA MLD combined with the NSTR Soft AP MLD may need to share the TSF timer of the primary link with the non-primary link. In other words, the non-AP STA MLD combined with the NSTR AP MLD does not have a separate TSF timer for the non-primary (NSTR Soft AP MLD reference) link, but can use the TSF timer managed using the primary link. That is, in one aspect of the present invention, the NSTR AP MLD and the non-AP STA MLD combined with the NSTR AP MLD can use an MLD level (MLD unit, MLD common) timer. In this case, for stable operation of the NSTR AP MLD and the non-AP STA MLD combined with the NSTR AP MLD, it may be required to maintain time synchronization between APs of the NSTR AP MLD and / or between STAs of the non-AP STA MLD combined with the NSTR AP MLD to have an error less than a predetermined value. For example, NSTR AP MLD may be required to maintain the timestamp difference (or the difference between timers) maintained between the AP of the primary link and the AP of the non-primary link at or below a pre-promised / configured value. For example, non-AP STA MLD combined with NSTR Soft AP MLD may be required to maintain the timestamp difference maintained between the STA of the primary link and the STA of the non-primary link at or below a pre-promised / configured value.

[0241] In other words, the TSF timer of the primary link may be maintained (or applied or used) the same for all links to APs included or affiliated in the NSTR AP MLD, and the difference between the timestamp or TSF timer of any two APs included or affiliated in the NSTR AP MLD may be limited to within a specific value (e.g., 30 us).

[0242] That is, the TSF timers of all APs included in or affiliated with the NSTR AP MLD may be the same, and the difference or clock drift between timestamps or TSF timers between any two APs (e.g., an AP of a primary link and an AP of a non-primary link) included in or affiliated with the AP MLD or NSTR AP MLD may be limited to within a specific value (e.g., ±30 us), in which case the AP MLD or NSTR AP MLD can modify the timestamps or TSF timers so that the difference or clock drift of the TSF timers is within the specific value.

[0243] In addition, the non-AP STA MLD associated with the NSTR AP MLD may need to receive the next beacon frame transmitted through the primary link when it receives a TIM frame through the non-primary link. More specifically, when the non-AP STA MLD receives a TIM frame through the STA of the non-primary link and the value indicated in the Check Beacon field in the TIM frame action field is different from the Check Beacon value it maintains, it may need to receive the next beacon frame transmitted through the primary link. In this case, the next beacon frame may mean a beacon frame transmitted corresponding to the TBTT of the primary link that exists after the time when the TIM frame is received through the non-primary link. In this case, the meaning of receiving the next beacon frame may be an operation that accompanies (includes) updating parameters of the non-primary link using a Per-STA profile (corresponding to the AP of the non-primary link) included in the beacon frame. In this case, the parameters to be updated may be limited to parameters related to a critical update.

[0244] <Channel Switching and Channel Quieting Procedures for Non-Primary Links>

[0245] As described above, the NSTR AP MLD does not transmit beacon frames on non-primary links, and therefore the BSS operation based on the transmission timing of the beacon frame may be performed in a manner different from the BSS operation of a general AP MLD.

[0246] In conventional Wi-Fi, the operating channel frequency (operating frequency band) of the BSS can be changed by a procedure previously agreed between the AP and the STA. In this case, the conventional ECS (Extended channel switching) operation can be used, or the channel change mechanism newly defined in 11be can be used. When the AP decides to change the operating channel of the BSS, it can transmit a beacon frame, a probe response frame, an Extended Channel Switch Announcement frame, etc., to inform the associated STAs that they can switch to a new channel and operating class while maintaining the association. In this case, the AP transmits an Extended Channel Switch Announce element in a beacon frame, and the Channel Switch Count field of the element indicates information on how many beacon frames are transmitted before a channel switch (operating channel change) is performed. If the AP includes a MAX Channel Switch Time element in a beacon frame together with an Extended Channel Switch Announcement element, the AP must transmit the first beacon frame on the new channel within the Switch Time field (of the Max Channel Switch Time element). That is, the beacon frame transmitted on the new channel must be transmitted at a time interval smaller than the time interval indicated by the Switch Time field relative to the last beacon frame transmitted on the current channel.

[0247] Referring to the channel change operation of the conventional Wi-Fi BSS described above, the AP of the BSS can use a beacon frame transmitted on the current channel to indicate to the STA information on the new channel, information on the time when the channel change is performed, and information related to the time of the first beacon frame transmitted on the new channel. The STA of the BSS can complete the channel change while maintaining association with the AP by moving to the new channel in a time period (time period indicated by the AP) determined based on the channel change related information included in the beacon frame transmitted by the AP. In this way, the channel change procedure of the conventional Wi-Fi BSS is performed in a manner in which information required for channel change (Channel Switch mode, new operating class, new channel number, channel switch count, etc.) is provided by the beacon frame transmitted by the AP, and therefore, in the case of a non-primary link BSS of the NSTR AP MLD in which a beacon frame is not transmitted, a channel change cannot be performed using the conventional channel change procedure.

[0248] In addition, when conventional Wi-Fi sets a quiet interval, information regarding the time period to which the quiet interval applies is indicated by elements (Quiet element, Quiet Channel element) included in the beacon frame transmitted by the AP of the BSS, and similar to the channel change procedure, the non-primary link of the NSTR AP MLD, which does not transmit a beacon frame, cannot use the conventional quieting procedure to set the quiet interval.

[0249] According to an embodiment of the present invention, the NSTR AP MLD can indicate information required for changing the operating channel of the non-primary link (channel switching) and / or information required for setting the quiet interval by a beacon frame transmitted on the primary link. That is, the non-AP STA MLD associated with the NSTR AP MLD can operate based on information obtained by a beacon frame of the primary link to perform channel switching of the non-primary link. That is, the non-AP STA MLD associated with the NSTR AP MLD can obtain information related to the quiet interval of the non-primary link by using a beacon frame of the primary link.

[0250] That is, in the STR AP MLD, APs included in the same AP MLD can periodically transmit beacon frames. In this case, each of these APs can transmit a beacon frame including basic information about the other APs in the beacon frame that it transmits, and the basic information about the other APs may include information related to channel changes of the other APs (e.g., a channel switch announcement element, an extended channel switch announcement element, a max channel switch element), and / or information for setting a quiet interval.

[0251] In this case, the channel switch guide element and the extended channel switch guide element may include a new channel number field indicating the number of the channel to be changed and a channel switch count field.

[0252] The channel switch count field indicates the number of TBTTs until the STA that transmitted the channel switch count field switches to a new channel. If the value of the channel switch count field is set to "1", a channel switch will occur at the next TBTT, and if the value of the channel switch count field is set to "0", a channel switch may occur any time after the channel switch count field is transmitted.

[0253] The channel switch guidance element and the extended channel switch guidance element may be transmitted in channel switch guidance frames, beacon frames, and probe response frames.

[0254] If the operating class is to be changed, the station can send an extended channel switch guide element with a new operating class field indicating the operating class to be changed.

[0255] The maximum channel switch time element may indicate a period during which a beacon may be transmitted on a changed channel from the time when channel switching begins. For example, if a channel change is successful, a station (e.g., an AP STA) that has performed the channel change may transmit a beacon on a new changed channel within the time indicated by the maximum channel switch time element from the time when channel switching begins.

[0256] In this case, the Max Channel Switch Time element may include a switch time field that indicates the interval for transmitting a beacon on the new channel.

[0257] The channel change information for changing the channel of other APs included in the same AP MLD may be transmitted by each AP under the assumption that the APs included in the same AP MLD periodically transmit beacons. However, in APs supporting NSTR, the APs included in the same AP MLD can transmit beacon frames only through the primary link. That is, among the multiple APs included in the same AP MLD, only a specific AP can transmit a beacon through the primary link, and the remaining APs cannot transmit a beacon. Therefore, in this case, even if the AP for the non-primary link does not transmit a beacon frame, the AP of the primary link can transmit the channel change information of the AP for the non-primary link by including it in the beacon frame.

[0258] More specifically, the NSTR AP MLD may need to include a Per-STA profile for the non-primary link AP in the primary link beacon frame (and (ML) probe response frame) when performing a channel change or setting a quiet interval for the non-primary link.

[0259] Fig. 17 shows an example of the format of elements according to an embodiment of the present invention. Fig. 17 shows an example of the format of each element described above.

[0260] Referring to FIG. 17, a (corresponding) Per-STA profile for an AP of a non-primary link may have a configuration including at least one of a Channel Switch Announcement element, an Extended Channel Switch Announcement element, a Max Channel Switch Time element, a Quiet element, and a Quiet Channel element.

[0261] The timing field of the element may need to be set based on the Target Beacon Transmission Time (TBTT) and beacon interval of the primary link.

[0262] Specifically, when an AP included in a general AP MLD transmits channel change information for other APs in a frame, elements for channel change of other APs (e.g., channel switch guide element, extended channel switch guide element, maximum channel switch time element, quiet element, quiet channel element, etc.) may be set and transmitted based on the AP performing the channel change rather than the AP transmitting the channel change information.

[0263] However, in AP MLD supporting NSTR (NSTR AP MLD), only the AP for the primary link transmits a beacon frame, and the AP for the non-primary link does not transmit a beacon frame, so that the channel change information and / or information regarding the quiet interval of the AP for the non-primary link may be set based on the AP of the primary link rather than the AP of the non-primary link.

[0264] Specifically, an AP that configures an AP MLD can transmit a Per-STA Profile including channel change information and / or quiet interval-related information for a non-primary link AP in a primary link using a specific frame (e.g., a beacon frame). In this case, the channel change information and / or quiet interval-related information for a non-primary link AP can be set based on the primary link AP.

[0265] For example, timing fields (e.g., time-related fields including duration-related fields (e.g., Switch Time, Quiet Duration fields, etc.) and point-in-time-related fields (e.g., Channel Switch Count, Quiet Count fields, etc.) included in the channel switch guide element, extended channel switch guide element, Quiet element, and / or Quiet Channel element) must be applied by referring to the most recent TBTT and BI indicated in the corresponding element of the AP operating on the primary link.

[0266] The AP of the primary link of the NSTR AP MLD may need to set the timing fields of the Channel Switch Announcement element, Extended Channel Switch Announcement element, Max Channel Switch Time element, Quiet element, and Quiet Channel element included in the Per-STA profile (included in the beacon frame and (ML) probe response frame) for the AP of the non-primary link based on its own beacon interval and TBTT. In this case, the timing fields are used to collectively refer to time-related fields including duration-related fields (Switch Time, Quiet Duration field, etc.) and time-related fields (Channel Switch Count, Quiet Count field, etc.).

[0267] Therefore, the non-AP MLD combined with the NSTR AP MLD may receive a beacon frame from the AP of the NSTR AP MLD operated in the primary link, obtain information related to a channel change and / or a quiet interval of the non-primary link from the Per-STA profile included in the beacon frame, and analyze the information related to a channel change and / or a quiet interval of the non-primary link based on the TBTT and BI (Beacon interval) of the primary link. In this case, the Per-STA profile refers to a Per-STA profile corresponding to the AP of the non-primary link.

[0268] Meanwhile, the NSTR AP MLD may need to transmit a TIM frame (of the non-primary link) on a new channel within a time period indicated by the Switch Time field (of the Max Channel Switch Time element) after completing a channel change of the non-primary link using a beacon frame of the primary link (after announcing and completing the channel change). That is, the AP of the non-primary link of the NSTR AP MLD may need to transmit a TIM frame on a new channel after performing a channel change. In this case, the AP of the non-primary link may need to transmit a TIM frame on a new channel within a time period indicated by the Switch Time field after a beacon frame with a Channel Switch Count subfield indicated as 1 (or 0) is transmitted on the primary link. In this case, the Channel Switch Count field and the Switch Time field may be included in a Per-STA profile (corresponding to a non-primary AP) included in a beacon frame transmitted on the primary link. In this case, the TIM frame may be replaced with another frame transmitted on a new channel of the primary link or non-primary link. As an example, the NSTR AP MLD may transmit a beacon frame indicating information related to the completion of the channel change in the primary link after completing the channel change of the non-primary link. In this case, the beacon frame may be an additional beacon frame transmitted regardless of the TBTT. In this case, the beacon frame may be a beacon frame having a configuration including complete information for the non-primary link. For example, the beacon frame having a configuration including complete information for the non-primary link may be a beacon frame in which the complete information subfield of the Per-STA profile corresponding to the AP of the non-primary link is set to 1.In this case, the primary link beacon frame transmitted after the channel change of the non-primary link is completed may need to be transmitted within a time period previously agreed upon with the beacon frame transmitted before the channel change is started. In this case, the previously agreed upon time may be a time indicated in a Switch Time field (of a Max Channel Switch Time element). Alternatively, the beacon frame may be a beacon frame including an indication related to the channel change of the non-primary link. As an example, the primary link beacon frame transmitted after the channel change of the non-primary link is completed may have a configuration including a Channel Switch Complete subfield. In this case, the Channel Switch Complete subfield may be a subfield included in an ML element. The specific Switch Complete subfield may be a subfield that is indicated as 1 when the channel change of the AP corresponding to the Per-STA profile including the specific subfield is completed. That is, after completing the channel change of the non-primary link, the AP may need to set the Channel Switch Complete subfield of the Per-STA profile (of the beacon frame) corresponding to the AP of the non-primary link to 1. At this time, the beacon frame related to the channel change may be transmitted (utilized) for the same purpose even if the AP MLD is not the NSTR AP MLD, that is, according to a general AP MLD.

[0269] The non-AP MLD combined with the NSTR AP MLD can perform an operation considering that the channel switching of the non-primary link is completed only when it receives a frame (the TIM frame of the non-primary link, or other frame and / or a beacon frame indicating information related to the completion of the channel switching of the primary link) promised from the AP MLD after performing the channel switching of the non-primary link on the primary link. That is, information on the channel switch for the AP of the non-primary link included in the AP MLD supporting NSTR (e.g., channel change information, etc.) may be transmitted by the AP of the primary link. In this case, the AP of the non-primary link cannot transmit a beacon frame on the changed channel even when the channel switch is completed because it is not the primary link. Therefore, in this case, the AP of the non-primary link can transmit a TIM frame indicating that the channel switch is completed when the channel switch is completed, thereby instructing the station of the non-AP MLD that the channel switch is completed. Alternatively, the primary link AP can send a beacon frame indicating that a channel switch to a non-primary link AP has been completed, thereby instructing non-AP MLD stations that the channel switch has been completed.

[0270] If it is determined that the channel switching is not complete, the non-AP STA MLD may need to consider that the channel switching of the non-primary link has been canceled and operate (return to) the previous channel (before the channel switching occurred).

[0271] Alternatively, the NSTR Soft AP MLD may set a specific subfield of a beacon frame transmitted on a primary link to a specific value while a non-primary link AP (BSS of the AP) is performing channel switching. More specifically, a beacon frame transmitted on a primary link by the NSTR Soft AP MLD may include a subfield that is maintained at 1 or 0 while the non-primary link AP is performing channel switching and is indicated as 0 or 1 during a time period when the non-primary link AP is not performing channel switching. That is, the NSTR Soft AP MLD may need to set the subfield based on whether the non-primary link AP is performing channel switching. In this case, the subfield may be a subfield included in an RNR element or a Per-STA profile corresponding to the non-primary link AP.

[0272] As described above, when the NSTR Soft AP MLD determines the value of the subfield depending on whether the AP of the non-primary link is performing channel switching, the non-AP MLD associated with the NSTR Soft AP MLD can determine whether the channel switching of the non-primary link AP (BSS) is being performed based on the value of the subfield indicated in the beacon frame received on the primary link. That is, the non-AP MLD can recognize that the AP of the non-primary link is performing channel switching by confirming that the subfield corresponding to the AP of the non-primary link is indicated as a specific value (e.g., 1) in the beacon frame received on the primary link. If the non-AP MLD confirms that the subfield corresponding to the AP of the non-primary link is not a specific value in the beacon frame received on the primary link, the non-AP MLD can recognize that the AP of the non-primary link has completed the scheduled channel switching. In this case, the meaning of "completed" may mean that the channel switching operation indicated by the last received (Extended) Channel Switching Announcement element corresponding to the AP of the non-primary link is completed or canceled. When the subfield corresponding to the AP of the non-primary link is indicated as a value other than a specific value (a value other than a value indicated when channel switching is in progress), the Non-AP MLD may consider that the AP of the non-primary link is operating in the operating channel / class indicated in the last received beacon frame (or Probe Response frame). When Non-AP MLD is to transmit a UL PPDU on a non-primary link, it may be necessary to transmit the UL PPDU based on whether the AP of the non-primary link is operating in a channel (class) recognized by itself.For example, Non-AP MLD can transmit a UL PPDU only when the subfield corresponding to an AP of a non-primary link is specified to have a value other than a specific value. On the other hand, when the subfield corresponding to an AP of a non-primary link is specified to have a specific value, Non-AP MLD may consider that the AP of the non-primary link is performing channel switching and may not transmit a UL PPDU.

[0273] As another method, the NSTR Soft AP MLD can maintain the Critical Update Flag of the beacon frame (or the Probe Response frame) at 1 until the non-primary link AP (the BSS of the AP) completes the channel switching. The NSTR Soft AP MLD helps the non-AP MLD to recognize the scheduled channel switching of the non-primary link by including an (Extended) Channel Switching Announcement element corresponding to the non-primary link AP in the beacon frame. In this case, the NSTR Soft AP MLD must set the Critical Update Flag subfield of the beacon frame to 1 when transmitting the (Extended) Channel Switch Announcement element in the beacon frame (transmitted on the primary link). The NSTR Soft AP MLD can make the non-AP MLD recognize the fact that the channel switching of the non-primary link is ongoing by maintaining the value of the Critical Update Flag subfield at 1 until the channel switching of the non-primary link is completed. At this time, the NSTR Soft AP MLD may need to include an (Extended) Channel Switch Announcement element (corresponding to the AP of the non-primary link) in the beacon frame until the AP of the non-primary link completes channel switching. At this time, if the AP of the non-primary link is performing channel switching, the NSTR Soft AP MLD may need to indicate the Channel Switch Count subfield of the Channel Switch Announcement element corresponding to the AP of the non-primary link as 0.At this time, if the AP of the non-primary link is performing channel switching, the NSTR Soft AP MLD may need to indicate the SwitchTime subfield of the Channel Switch Timing element corresponding to the AP of the non-primary link as the time value until the predicted completion of the channel switching. At this time, the NSTR Soft AP MLD does not need to specify the completion time of the channel switching of the non-primary link AP by setting the SwitchTime subfield to a specific value (e.g., 65535).

[0274] As described above, when the NSTR Soft AP MLD maintains the value of the Critical Update Flag subfield to 1 when the AP of the non-primary link is in the channel switching, the non-AP MLD may not transmit a UL PPDU on the non-primary link if the value of the Critical Update subfield is 1. More specifically, the non-AP MLD may not transmit a UL PPDU on the non-primary link if the Critical Update Flag subfield of the beacon (Probe Response) frame received from the NSTR Soft AP MLD is 1 and the Channel Switch Count subfield corresponding to the non-primary link AP is indicated as 0. More specifically, the non-AP MLD may not transmit a UL PPDU on the non-primary link if the Critical Update Flag subfield of the beacon (Probe Response) frame received from the NSTR Soft AP MLD is 1 and the SwitchTime subfield corresponding to the non-primary link AP is indicated as a value other than 0.

[0275] As another method, the NSTR Soft AP MLD can indicate by incrementing the value of the BSS Parameter Change Count subfield corresponding to the non-primary link AP when the non-primary link AP (the BSS of the AP) completes channel switching. In this case, the BSS Parameter Change Count subfield means the BSS Parameters Change Count subfield in the MLD Parameters field of the TBTT Information field corresponding to the non-primary link AP. A general AP MLD increases the value of the BSS Parameters Change Count subfield by 1 only when the parameters of the AP corresponding to the BSS Parameters Change Count subfield are updated, but the NSTR Soft AP MLD can also increase the BSS Parameters Change Count subfield corresponding to the non-primary link AP by 1 when channel switching is completed. This may be understood as an increase in the value of the BSS Parameters Change Count subfield as a method for indicating that the instructed channel switching operation is completed for the non-primary link AP, and when the non-AP MLD determines that the channel switching of the non-primary link AP is scheduled / in progress, if the value of the BSS Parameters Change Count subfield is incremented by 1, the non-AP MLD can determine that the scheduled / in progress channel switching is completed. In this case, the non-AP MLD can transmit a UL PPDU after determining that the scheduled / in progress channel switching is completed. The operation of the non-AP MLD regarding the transmission condition of the UL PPDU is the same as the other channel switching completion indication method described above, and the description thereof will be omitted.

[0276] As another method, the NSTR Soft AP MLD can transmit a frame including a subfield indicating a different value on the primary link when the non-primary link AP (the BSS of the AP) is scheduled to perform channel switching, when the channel switching is being performed, and when the channel switching is completed. In this case, the frame can be a beacon frame. Furthermore, when the channel switching for the non-primary link AP is scheduled, the NSTR Soft AP MLD can indicate an (Extended) Channel Switch Announcement element corresponding to the non-primary link AP and indicate a specific subfield to a specific value (e.g., 1). When the channel switching of the non-primary link AP is started, the NSTR Soft AP MLD can set the specific subfield to a value other than the specific value (e.g., 2) until the channel switching is completed. When the channel switching of the non-primary link AP is completed, the NSTR Soft AP MLD can set the specific subfield to an initial value (e.g., 0). In this way, the NSTR Soft AP MLD sets the value of a specific subfield corresponding to a non-primary link AP to different values ​​when channel switching is scheduled, when channel switching is in progress, and when channel switching is completed (when channel switching is not scheduled), respectively, thereby allowing the Associated non-AP MLD to recognize the progress of channel switching of the non-primary link. The Non-AP MLD can determine whether to transmit a UL PPDU on the non-primary link by checking the specific subfield included in a frame received on the primary link. For example, the Non-AP MLD can transmit a UL PPDU only if the last received specific subfield is an initial value.

[0277] As another method, the non-AP MLD can determine whether the non-primary link AP has completed channel switching based on a primary link beacon frame received after the scheduled channel switching completion time of the non-primary link AP indicated (published) by the NSTR Soft AP MLD.

[0278] Furthermore, the non-AP MLD can determine whether the scheduled channel switching is completed by checking the Operating channel / class information of the non-primary link AP indicated by the beacon frame received on the primary link after the channel switching completion time of the non-primary link AP confirmed from the channel switching related element. In this case, the method of checking the channel switching completion time of the non-primary link AP by the channel switching related element may be to use the value indicated in the SwitchTime subfield of the Channel Switch Timing element. When the non-AP MLD confirms that the same information as the Operating channel / Class scheduled for channel switching is indicated to the non-primary link AP in the beacon frame received after the scheduled channel switching completion time, it can determine that the non-primary link AP has completed the scheduled channel switching and transmit the UL PPDU. That is, when the non-AP MLD receives the first beacon frame (on the primary link) after the scheduled channel switching completion time of the non-primary link, it can transmit the UL PPDU on the non-primary link. In this case, the channel / class in which the non-AP MLD transmits the UL PPDU may be the operating channel / class of the non-primary link AP indicated in the first beacon frame.

[0279] In addition, the NSTR AP MLD may not be able to perform channel switching of a non-primary link. However, when the NSTR AP MLD attempts to perform channel switching of a non-primary link, it can release the non-primary link AP operating on the existing channel and operate as if a new non-primary link AP was added on the new channel.

[0280] In yet another embodiment of the present invention, the NSTR AP MLD may be restricted so that the quiet interval cannot be set in the non-primary link. In this case, if there is a quiet interval defined (set) in the primary link, the quiet interval of the non-primary link may be defined (set) as the same time interval as the quiet interval of the primary link. In other words, when the non-AP STA MLD combined with the NSTR AP MLD recognizes the quiet interval of the primary link, it can be considered that the quiet interval is set for the same time interval in the non-primary link.

[0281] In this way, the quiet element for the non-primary link transmitted in the beacon frame of the primary link may be set (indicated) by the NSTR AP MLD as follows:

[0282] 1. The Quiet Count field may be set to the number of TBTTs of the primary link remaining before the next quiet interval begins on the non-primary link.

[0283] 2. The Quiet Period field may be set to a value (in primary link beacon interval units) related to how many primary link beacon intervals the regular (periodic) quiet interval of the non-primary link defined by the Quiet element begins every (set to 0 if not a regular quiet interval).

[0284] 3. The Quiet Offset field may be set to a time value (in TUs) related to how far the quiet interval of the non-primary link begins from the TBTT of the primary link identified by the Quiet Count subfield.

[0285] The (Extended) Channel Switch Announcement element and Max Channel Switch Time element for the non-primary link transmitted in the beacon frame of the primary link may be set (instructed) by the NSTR AP MLD as follows.

[0286] 1. The Channel Switch Count field (of the Channel Switch Announcement element) may be set to information related to how many TBTTs of the primary link remain before a channel change of the non-primary link begins. If a channel change of the AP of the non-primary link begins in the next TBTT of the primary link, the beacon frame transmitted in this TBTT may have the Channel Switch Count field (associated with the AP of the non-primary link) set to 1 or 0.

[0287] 2. The Switch Time field (of the Max Channel Switch Time element) may be set to a value corresponding to the maximum time difference between the primary beacon frame (beacon frame with the Channel Switch Count field set to 1 or 0 in 1 above) transmitted in the TBTT immediately before the TBTT at which the non-primary link channel change begins and the TIM frame transmitted on the new channel of the non-primary link after the channel change of the non-primary link is completed. As an example, when the beacon interval of the primary link is 100 ms, if the Switch Time field (for the non-primary link AP) is set to 200 ms, the non-primary link AP must transmit a TIM frame on the new channel within 200 ms from the time of transmitting the primary link beacon frame at which it began the channel change.

[0288] Therefore, the non-AP MLD combined with the NSTR AP MLD can obtain information on the quiet interval and channel change time and period of the non-primary link based on the information indicated in the Per-STA profile of the non-primary AP included in the beacon frame, the TBTT of the primary link, and the beacon interval information after receiving the beacon frame on the primary link. At this time, the non-AP MLD can set (recognize, analyze) the start time of the quiet interval of the non-primary link based on the TBTT of the primary link. At this time, the non-AP MLD can recognize / analyze the channel change time of the non-primary link based on the reception time of the beacon frame received on the primary link.

[0289] Conventionally, a Wi-Fi non-AP STA can select whether or not to change channels together with the AP to maintain association when the AP changes channels. However, a non-AP STA MLD associated with an NSTR AP MLD may need to change channels on the non-primary link whenever the NSTR AP MLD changes channels on the non-primary link.

[0290] If a non-AP STA MLD that has performed ML setup with the NSTR AP MLD (i.e., ML setup using primary and non-primary links) decides not to change the channel of the non-primary link, the non-AP STA MLD may need to terminate (cancel or change) the ML setup with the NSTR AP MLD and change to a state set up only on the primary link (by setup or reset after release).

[0291] That is, a station in a non-AP MLD that receives channel change information related to channel switching for a non-primary link AP from a primary link AP included in an AP MLD that supports NSTR can decide whether to switch channels together with the non-primary link AP.

[0292] If a station associated with a non-primary link AP decides to perform channel switching, the station moves to the changed channel and receives a specific frame (e.g., a TIM frame) from the non-primary link AP indicating that channel switching has been completed, or the primary link AP may receive a beacon frame indicating that the non-primary link AP's channel switching has been completed. The non-AP STA that receives the TIM frame or beacon frame recognizes that channel switching has been completed and can transmit and receive frames on the changed channel.

[0293] On the other hand, if a station associated with the AP of a non-primary link decides not to perform channel switching, the non-AP STA that does not perform channel switching can terminate (cancel or change) the multiple link setting with the AP of the non-primary link. In this case, the link setting between the AP of the non-primary link and the non-AP STA is cancelled, so that the AP MLD and the STA MLD only have a single link setting of the primary link.

[0294] If a non-AP STA that has a link established with the primary link AP does not perform channel switching to the primary link AP, the non-AP STA can select whether or not to move to another BSS and establish a link with the AP of the other BSS.

[0295] Meanwhile, the NSTR Soft AP MLD may need to set the time interval for channel switching in the primary link as the quiet interval of the non-primary link BSS. This may be an operation that originates from the restriction that the non-primary link can be occupied only when the NSTR Soft AP MLD and the non-AP STA associated with the NSTR Soft AP MLD occupy the primary link. When the NSTR Soft AP MLD performs channel switching for the AP (BSS) of the primary link, the NSTR Soft AP MLD and the associated non-AP MLD restrict communication not only in the primary link but also in the non-primary link. Therefore, when the NSTR Soft AP MLD performs channel switching for the AP (BSS) of the primary link, it may be necessary to specify the same time interval as the channel switching interval as the quiet interval of the non-primary link AP (BSS). Alternatively, even if the NSTR Soft AP MLD does not separately indicate the quiet interval of the non-primary link, the non-AP MLD associated with the NSTR Soft AP MLD should not transmit UL PPDU on the non-primary link from the start of channel switching of the primary link until the completion of channel switching (when the first beacon frame is received on the new channel of the primary link). In this case, the non-AP MLD can perform an operation of generating a new backoff counter when the backoff counter becomes 0 during the time period in which the UL PPDU is not transmitted on the non-primary link. In this case, the new backoff counter may be the backoff counter generated using the current CW (Contention Window). In this case, the counters related to retransmission (such as Short retry count and Long retry counter) are not changed.

[0296] Similarly, the NSTR Soft AP MLD may need to set the time interval set as the quiet interval in the primary link BSS as the quiet interval of the non-primary link BSS. This may be an operation that originates from the restriction that the non-primary link can be occupied only when the NSTR Soft AP MLD and the non-AP STA associated with the NSTR Soft AP MLD occupy the primary link. When the NSTR Soft AP MLD sets a quiet interval for the AP (BSS) of the primary link, the NSTR Soft AP MLD and the associated non-AP MLD restrict communication not only in the primary link but also in the non-primary link. Therefore, when the NSTR Soft AP MLD instructs (sets) the quiet interval for the AP (BSS) of the primary link, it may need to instruct (set) the same time interval as the channel switching interval as the quiet interval of the non-primary link AP (BSS).

[0297] In this way, the non-AP MLD associated with the NSTR Soft AP MLD may not transmit UL PPDUs on the non-primary link when channel switching is being performed on the primary link or when the quiet interval of the primary link is set. Therefore, the non-AP MLD can perform a power save operation on the non-AP STA operating on the non-primary link when channel switching of the primary link is being performed or when the quiet interval is in progress. This may be a power save operation using that the AP of the non-primary link does not transmit DL PPDUs to the non-primary link when channel switching is in progress on the primary link or when the quiet interval is in progress. In addition, even if the non-AP STA operating on the non-primary link completes a channel access operation (e.g., a backoff operation of EDCA), the non-AP MLD may decide to stop the channel access operation on the non-primary link since the UL PPDU transmission using the non-primary link is restricted. For example, non-AP MLD can suspend the channel access operation and / or CCA operation of non-AP STAs operating on a non-primary link when NSTR Soft AP MLD is performing channel switching or a quiet interval on a primary link. In this case, suspending the channel access operation and / or CCA operation can mean operating in a Doze state in a power save mode.

[0298] Considering that the STA of the Non-AP MLD has performed a power saving operation (specifically, maintaining a Doze state) for the non-AP STA operating on the non-primary link, the NSTR Soft AP MLD can transmit an Assistance frame on the non-primary link when the channel switching / quiet interval of the primary link is completed. At this time, the Assistance frame may be transmitted to induce (help) the non-AP STA of the non-primary link to reset the NAVSyncDelay timer that was started after the non-AP STA switched to Awake. At this time, the Assistance frame may be transmitted at a basic rate. At this time, the Assistance frame may be a frame that is transmitted simultaneously when the beacon frame of the primary link is transmitted. At this time, the NAVSyncDelay timer may mean a timer related to the time when the STA that switched from the Doze state to Awake should perform CCA to set the NAV.

[0299] FIG. 18 illustrates an example of a process in which an NSTR Soft AP MLD sets (defines) a quiet interval for a non-primary according to an embodiment of the present invention.

[0300] Referring to FIG. 18, the NSTR AP MLD operates AP1 and AP2 on the primary link and non-primary link, respectively, and is associated with STA1 and STA2 of the Non-AP STA MLD, respectively.

[0301] In order to set (define) a quiet interval (Quiet interval#1 in FIG. 18) in a non-primary link, the NSTR AP MLD can transmit a beacon frame transmitted via AP1 of the primary link including a Per-STA profile corresponding to AP2. The Per-STA profile corresponding to AP2 includes a Quiet element and indicates information related to the time when the Quiet interval (Quiet interval#1 in FIG. 18) starts in Quiet Count and Quiet Offset fields. When the Quiet element is included in the first beacon frame (Beacon#1 in FIG. 18) of the primary link shown in FIG. 18, the Quiet Count field is set to 2, the Quiet Offset field is set to a value indicating "x" TU (Time Unit, 1024 us), and in the second beacon frame (Beacon#2 in FIG. 18), the Quiet Count field is set to 1.

[0302] The non-AP STA MLD that receives the first and / or second beacon frame on the primary link can recognize that a quiet interval has been set (announced by the AP MLD) on the non-primary link by checking the quiet element included in the Per-STA profile (corresponding to AP2) of the beacon frame, and that the quiet interval (Quiet interval #1 in Figure 18) starts when "x" TUs have elapsed since the TBTT corresponding to the third beacon frame.

[0303] As shown in Fig. 18, the NSTR AP MLD can again include the Per-STA profile corresponding to AP2 in the beacon frame transmitted via AP1 of the primary link in order to further set (define) the next quiet interval (Quiet interval#2 in Fig. 18) in the non-primary link. The sixth beacon frame (Beacon#6 in Fig. 18) of the primary link shown in Fig. 18 has the Quiet Count field set to 2 and the Quiet Offset field set to a value indicating 0TU (Time Unit, 1024 us), and the seventh beacon frame (Beacon#7 in Fig. 18) has the Quiet Count field set to 1.

[0304] A non-AP STA MLD that receives the sixth and / or seventh beacon frame on the primary link can recognize that a quiet interval (Quiet interval #2) is set (announced by the AP MLD) on the non-primary link by checking the Quiet element included in the Per-STA profile (corresponding to AP2) of the beacon frame and that the quiet interval (Quiet interval #2) starts from the TBTT corresponding to the eighth beacon frame.

[0305] At this time, information regarding the length of the quiet interval is indicated by a Quiet Duration field indicated together with the Quiet element.

[0306] FIG. 19 illustrates an example of a method for an NSTR Soft AP MLD to perform a non-primary channel switch according to an embodiment of the present invention.

[0307] Referring to FIG. 19, the NSTR AP MLD operates AP1 and AP2 on the primary link and non-primary link, respectively, and is associated with STA1 and STA2 of the Non-AP STA MLD, respectively.

[0308] In order to change the non-primary link to a new channel, the NSTR AP MLD can transmit a beacon frame transmitted via the primary link AP1 including a Per-STA profile corresponding to AP2 (non-primary link). The Per-STA profile corresponding to AP2 includes an (Extended) Channel Switch Announcement element and a Max Channel Switch Time element, and indicates information related to the time when the channel change starts and the time period during which the TIM frame is transmitted on the new channel after the channel change. When the (Extended) Channel Switch Announcement element is included in the first beacon frame (Beacon#1 in FIG. 19) of the primary link shown in FIG. 19, the Channel Switch Count field is set to 2, and in the second beacon frame (Beacon#2 in FIG. 19), it is set to 1.

[0309] The non-AP STA MLD that receives the first and / or second beacon frame on the primary link can determine that the channel change (to a new channel) of the non-primary link begins after receiving the second beacon frame by checking the (Extended) Channel Switch Announcement element included in the Per-STA profile (corresponding to AP2) of the beacon frame, and that the TIM frame of AP2 on the new channel will be received within 'x' TUs from the time the second beacon frame is received. In this case, the new channel may be a channel corresponding to the value indicated in the New Channel Number field included in the (Extended) Channel Switch Announcement element. In this case, the 'x' TUs may be a time value indicated in the Switch Time field included in the Max Channel Switch Time element included in the Per-STA profile (corresponding to AP2).

[0310] <Operation Restriction of Non-AP STA MLD Combined with NSTR AP MLD>

[0311] NSTR AP MLD is an AP MLD where the primary link and the non-primary link are an NSTR link pair. Therefore, during the process of transmitting a PPDU via the AP of the primary link, the AP of the non-primary link may become in the BLIND state, and conversely, when the AP of the non-primary link performs transmission, the AP of the primary link may become in the BLIND state. In this case, the AP of the NSTR AP MLD that has passed through the BLIND state may need to set the MediumSyncDelay to a preset value.

[0312] MediumSyncDelay is a single timer that is commonly applied to the EDCAF (EDCA Function) of the STA. When MediumSyncDelay is not 0, additional constraints may be applied when the STA acquires a TXOP. At this time, the additional constraints may be: (1) the first transmission attempt to obtain a TXOP must be an RTS frame; (2) only attempts to acquire a TXOP a preset number of times or less (until it decreases to 0) are allowed while MediumSyncDelay is applied; (3) utilize a CCA ED (energy detection) threshold that is more stringent (lower: for example, -72dBm to -62dBm) than when MediumSyncDelay is 0. That is, a STA with a non-zero MediumSyncDelay value has more constraints applied in TXOP acquisition compared to a STA with MediumSyncDelay equal to 0.

[0313] Therefore, in the case of NSTR AP MLD, when the AP passes through the BLIND state, MediumSyncDelay must be applied, and in a situation where the channel access of the AP is restricted, it may be difficult to provide normal service to the STA of the BSS. The NSTR AP MLD can manage transmissions on a non-primary link (a link other than the primary link) in a manner that the primary link does not enter the BLIND state by determining one of the links of the NSTR link pair in which the AP operates as a primary link. As an example, the NSTR AP MLD can manage the primary link not to enter the BLIND state by transmitting on the non-primary link only when transmission on the primary link is in progress. For this purpose, the NSTR AP MLD does not need to respond with the requested response frame even if it receives a frame requesting a response frame through the AP of the non-primary link. That is, the NSTR AP MLD can perform an operation of not responding with a response frame even if it receives a frame requesting a response frame through the AP of the non-primary link. At this time, the reason why the NSTR AP MLD does not respond with a response frame via the AP of the non-primary link may be to prevent the AP of the primary link from entering a BLIND state.

[0314] As described above, the NSTR AP MLD can manage the operation (transmission) of the AP operating on the primary link and / or the non-primary link in order to set up a primary link and prevent the AP of the primary link from being in a BLIND state. Similarly, the non-AP STA MLD combined with the NSTR AP MLD may need to understand the primary link management method of the NSTR AP MLD and operate. For example, when the non-AP STA MLD recognizes that a response frame is not responded to from the NSTR AP MLD on the non-primary link, it may not transmit a frame requesting a response of the response frame on the non-primary link. Also, when the non-AP STA MLD transmits a frame requesting a response of the response frame on the non-primary link and fails to receive a response of the response frame from the NSTR AP MLD, it may not retransmit the frame requesting a response of the response frame. For example, when the non-AP STA MLD transmits an RTS frame to the NSTR AP MLD on the non-primary link and fails to receive a CTS frame response, it may not retransmit the RTS frame. In this case, the Non-AP MLD does not need to attempt transmission to the NSTR AP MLD via the non-primary link until it receives a trigger frame via the non-primary link.

[0315] In addition, even if the non-AP MLD completes the channel access procedure of the non-primary link to perform UL transmission, the non-primary link transmission can be postponed until the channel access procedure is completed on the primary link. In this case, the method by which the non-AP MLD postpones the non-primary link transmission may be to stop the backoff procedure performed by the STA of the non-primary link (more precisely, the EDCAF of the STA) until the backoff procedure performed by the STA of the primary link is completed. In this case, the method by which the non-AP MLD stops the backoff procedure performed by the STA of the non-primary link may be to maintain the backoff counter at 0.

[0316] In the above-mentioned method, the non-AP STA MLD that has completed the channel access procedure in both the primary link and the non-primary link can perform simultaneous transmission (simultaneous UL PPDU transmission) in the primary link and the non-primary link. In this case, the "simultaneous transmission" means that the time when each transmission starts is within a preset time interval. However, if only the channel access procedure in the primary link is completed and the channel access procedure in the non-primary link is not yet completed, the non-AP MLD can start PPDU transmission only in the primary link or can start simultaneous transmission when the channel access procedure in the non-primary link is completed. That is, when transmitting to the NSTR AP MLD, the non-AP MLD can perform transmission using only the primary link or perform simultaneous transmission using the primary link and the non-primary link. However, it is not necessary to allow the non-AP MLD to transmit PPDU to the NSTR AP MLD using only the non-primary link.

[0317] In addition, non-AP MLD may require NSTR AP MLD to synchronize the end points of transmissions on both links when performing UL transmissions using both the primary link and the non-primary link. In this case, synchronizing the end points of transmissions may mean that the transmissions on both links are completed within a preset time interval.

[0318] In addition, the non-AP MLD may need to set whether or not the PPDUs transmitted on both links request a response frame when performing UL transmission using both the primary link and the non-primary link in the NSTR AP MLD. Furthermore, the two UL PPDUs transmitted simultaneously by the non-AP MLD on the primary link and the non-primary link may both request a response frame, or both may need to request a response frame. This may be a restriction that is applied because if a response frame is only responded to on a specific link as a result of the UL transmission performed by the non-AP MLD using both the primary link and the non-primary link, the APs operating on other links of the NSTR AP MLD may be in a BLIND state. However, the NSTR AP MLD may not need to respond to all of the two PPDUs (received on the primary link and the non-primary link, respectively) that have been received simultaneously if only one of them is a PPDU that requests a response frame.

[0319] In addition, the non-AP MLD may need to configure the NSTR AP MLD so that the TXOP of the non-primary link ends at the same time as or earlier than the TXOP of the primary link when transmitting using both the primary link and the non-primary link. In other words, the non-AP MLD may need to configure so that the TXOP of the non-primary link ends at the same time as or earlier than the TXOP of the primary link. However, the non-primary link TXOP of the non-AP STA MLD may be allowed to end later than the TXOP of the primary link by a point within a preset time interval.

[0320] In addition, the non-AP STA MLD can recognize that the NSTR AP MLD has experienced a BLIND state in the AP of a specific link and assist the AP in its operation. Furthermore, when the non-AP STA MLD recognizes that the NSTR AP MLD has transmitted only on one of the primary link and the non-primary link, it can recognize that the AP of the other link that did not transmit must have experienced a BLIND state. In this case, the non-AP STA MLD can assist the AP in releasing (resetting to 0) MediumSyncDelay, considering that the AP experiencing the BLIND state is restricted from channel access due to a non-zero MediumSyncDelay. In this case, the operation performed by the non-AP STA MLD may be an operation using a characteristic that MediumSyncDelay can be released when a PPDU (including a valid MPDU) capable of NAV setting is received.

[0321] As an example, the non-AP STA MLD may transmit an Assist frame (a kind of PPDU) capable of NAV setting to the AP of the NSTR AP MLD that is determined to have a non-zero MediumSyncDelay after passing through the BLIND state. In this case, the Assist frame may mean a frame included in a valid MPDU capable of NAV setting, regardless of the frame format. In this case, the condition for the non-AP STA MLD to transmit an Assist frame to the NSTR AP MLD on a specific link may be limited to when the state of the specific link confirmed by the non-AP STA MLD is in an IDLE state. In this case, another condition for the non-AP STA MLD to transmit an Assist frame to the NSTR AP MLD may be limited to when the non-AP STA MLD is a non-AP STA MLD that is explicitly or implicitly requested (instructed) to transmit an Assist frame from the NSTR AP MLD.

[0322] FIG. 20 is a flowchart showing an example of the operation of non-AP MLD according to an embodiment of the present invention.

[0323] Referring to FIG. 20, an MLD consisting of a plurality of STAs can obtain channel change information for an AP of a non-primary link from an AP of a primary link of an AP MLD.

[0324] Specifically, a multi-link device (MLD) including a plurality of stations each operating on a plurality of links can receive a frame including channel change information for changing a channel from a first AP of a primary link among the plurality of links (S20010).

[0325] The multiple links may be composed of one of the primary links and at least one secondary link (non-primary link), and the channel change information may be used for channel change of the second AP for one of the at least one secondary link.

[0326] Thereafter, the MLD can determine whether to change the channel of the station connected to the second AP through the one secondary link based on the channel change information (S33020).

[0327] In this case, a field related to the timing of the channel change of the second AP included in the channel change information may be set based on the first AP of the primary link.

[0328] The field related to the timing of the channel change of the second AP may be set based on a target beacon transmission time (TBTT) and a beacon interval (BI) of the primary link to the first AP, and the field related to the timing of the channel change of the second AP may include a switch time field indicating the time interval from the start of the channel change until the first frame is transmitted on the changed channel, and / or a channel switch count field indicating the number of TBTTs remaining until the channel change starts.

[0329] The switch time field may be recognized based on the time when a beacon frame is transmitted from the first AP of the main link, in which the value of the channel switch count field related to the channel change of the second AP is set to “1” or “0”.

[0330] If the value of the channel switch count field is 1, the channel change may begin at the first AP's next TBTT after the frame is transmitted, and if the value of the channel switch count field is 0, the channel change may begin after the frame is transmitted.

[0331] The channel change information may further include a new channel number field indicating the number of the channel to be changed by the channel change.

[0332] The channel change information is included in at least one Per-STA profile sub-element included in the frame, and each of the at least one Per-STA profile sub-element may include information regarding other APs included in the same MLD.

[0333] The first and second APs are non-simultaneous transmission and reception (NSTR) stations that do not support simultaneous transmission and reception within the same MLD.

[0334] The MLD may perform a channel change for the station based on the channel change information, and may receive a frame related to the completion of the channel change from the first AP or the second AP.

[0335] When the second AP is an AP that operates on a non-primary link, if a non-AP STA associated with the second AP of the non-primary link decides not to perform channel switching and channel switching is not performed, the non-AP STA that does not perform channel switching can terminate (release or change) the multiple link setup with the second AP of the non-primary link. In this case, since the link setup between the AP of the non-primary link and the non-AP STA is released, only a single link setup of the primary link exists for the AP MLD and the STA MLD. Therefore, the AP MLD and the STA MLD can re-establish the link to operate only on the primary link. That is, the AP MLD and the STA MLD can re-establish the link to operate on a single link.

[0336] If a non-AP STA that has a link established with the first AP of the primary link does not perform channel switching for the first AP operating on the primary link, the non-AP STA of the first AP can select whether or not to move to another BSS and establish a link with an AP of the other BSS.

[0337] The above description of the present invention is for illustrative purposes only, and those skilled in the art will understand that the present invention can be easily modified into other specific forms without changing the technical idea or essential features of the present invention. Therefore, the above-described embodiments should be understood to be illustrative and not restrictive in all respects. For example, each component described as a single type may be implemented in a distributed form, and similarly, each component described as a distributed type may be implemented in a combined form.

[0338] The scope of the present invention is indicated by the claims set forth below rather than by the above detailed description, and all modifications and variations that fall within the meaning and scope of the claims and their equivalent concepts should be construed as being included within the scope of the present invention.

Claims

1. A multi-link device (MLD) including a plurality of stations each operating on a plurality of links, The processor receiving a frame including channel change information for changing a channel from a first AP of a primary link among the plurality of links; The plurality of links are composed of one of the main links and at least one secondary link (non-primary link), The channel change information is used for a channel change of a second AP for one of the at least one secondary link; determining whether to change a channel of a station connected to the second AP through the one secondary link based on the channel change information; A field related to the timing of the channel change of the second AP included in the channel change information is set based on the first AP of the primary link, MLD.

2. 2. The MLD of claim 1, wherein the field related to the timing of the channel change of the second AP is set based on a target beacon transmission time (TBTT) and a beacon interval (BI) of the primary link to the first AP.

3. 2. The MLD of claim 1, wherein the field related to the timing of the channel change of the second AP includes a switch time field indicating a time interval from the start of the channel change until the first frame is transmitted through the changed channel, and / or a channel switch count field indicating the number of TBTTs remaining until the channel change starts.

4. The MLD of claim 3, wherein the switch time field is recognized based on the time when a beacon frame is transmitted from the first AP of the primary link, in which the value of the channel switch count field related to the channel change of the second AP is set to "1" or "0".

5. If the value of the channel switch count field is 1, the channel change begins at the first AP's next TBTT after the frame is transmitted; The MLD of claim 3, wherein if the channel switch count field value is 0, then the channel change begins after the frame is transmitted.

6. 4. The MLD of claim 3, wherein the channel change information further includes a new channel number field indicating a number of a channel to be changed by the channel change.

7. The channel change information is included in at least one Per-STA profile sub-element included in the frame; The MLD of claim 1 , wherein each of the at least one Per-STA profile sub-element includes information regarding other APs included in the same MLD.

8. The MLD of claim 1, wherein the first AP and the second AP are non-simultaneous transmission and reception (NSTR) stations that do not support simultaneous transmission and reception within the same MLD.

9. The processor, The MLD of claim 1 , further comprising: performing a channel change of the station based on the channel change information; and receiving a frame related to the completion of the channel change from the first AP or the second AP.

10. The processor, The MLD of claim 1, further comprising: if the station connected to the second AP through the one secondary link does not change channels based on the channel change information, a link is established again with an AP MLD including the first AP and the second AP so that the MLD is connected only to the primary link of the first AP.

11. A method performed by a multi-link device (MLD) including a plurality of stations operating on a plurality of links in a wireless communication system, the method comprising: receiving a frame including channel change information for changing a channel from a first AP of a primary link among the plurality of links, The plurality of links are composed of one of the main links and at least one secondary link (non-primary link), the channel change information is used for a channel change of a second AP for one of the at least one secondary link; and determining whether to change a channel of a station connected to the second AP through the one secondary link based on the channel change information, a field included in the channel change information related to a timing of a channel change of the second AP is set based on the first AP of the primary link.

12. 12. The method of claim 11, wherein the field related to the timing of the channel change of the second AP is set based on a target beacon transmission time (TBTT) and a beacon interval (BI) of the primary link to the first AP.

13. 12. The method of claim 11, wherein the fields related to the timing of the channel change of the second AP include a switch time field indicating a time interval from the start of the channel change until the first frame is transmitted through the changed channel, and / or a channel switch count field indicating the number of TBTTs remaining until the channel change starts.

14. The method of claim 13, wherein the switch time field is recognized based on a time point when a beacon frame is transmitted from the first AP of the primary link, in which the value of the channel switch count field related to the channel change of the second AP is set to "1" or "0".

15. If the value of the channel switch count field is 1, the channel change begins at the next TBTT of the first AP after the frame is transmitted; 14. The method of claim 13, wherein if the channel switch count field value is zero, then the channel change begins after the frame is transmitted.

16. 14. The method of claim 13, wherein the channel change information further comprises a new channel number field indicating a number of a channel to be changed by the channel change.

17. The channel change information is included in at least one Per-STA profile sub-element included in the frame; The method of claim 11 , wherein each of the at least one Per-STA profile sub-element includes information about other APs included in the same MLD.

18. The method of claim 11, wherein the first AP and the second AP are non-simultaneous transmission and reception (NSTR) stations that do not support simultaneous transmission and reception within the same MLD.

19. performing a channel change of the station based on the channel change information; The method of claim 11 , further comprising receiving a frame from the first AP or the second AP related to the completion of the channel change.

20. The method of claim 11, further comprising: if the station connected to the second AP through the one secondary link does not change channels based on the channel change information, re-establishing a link with an AP MLD including the first AP and the second AP so that the MLD is connected only to the primary link of the first AP.

Images