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

Abstract

To provide a wireless communication method using a multi-link and a wireless communication terminal using the same.SOLUTION: The AP multi-link device includes a transceiver and a processor. The processor is configured to determine whether to perform transmission for a non-AP multi-link device in a second link based on whether the non-AP multi-link device is performing transmission in a first link, when performing transmission in the second link to the non-AP multi-link device operating in the first link and the second link, the first link and the second link being non-simultaneoustransmitandreceive (STR) links in which transmission is not supported in the other link when reception is performed in any one link.SELECTED DRAWING: Figure 9

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 popularity of mobile devices has increased, wireless LAN technology, which can provide them with high-speed wireless Internet services, has been gaining attention. Wireless LAN technology is a technology that uses short-range wireless communication technology to enable mobile devices such as smartphones, smart pads, laptop PCs, portable multimedia players, embedded devices, etc. to connect to the Internet wirelessly at home, in business, or in specific service areas.

[0003] Since supporting early wireless LAN technology using the 2.4 GHz frequency band, IEEE (Institute of Electronics Engineers) 802.11 has since implemented or is currently developing various other technology standards. IEEE 802.11b uses the 2.4 GHz frequency band and supports a maximum communication speed of 11 Mbps. IEEE 802.11a, which was commercialized after IEEE 802.11b, uses the 5 GHz frequency band instead of the 2.4 GHz band, reducing the impact of interference compared to the significantly more congested 2.4 GHz frequency band, and uses OFDM technology to improve communication speeds to a maximum of 54 Mbps. 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 has attracted considerable attention for its backward compatibility, but it also has an advantage over IEEE 802.11a in terms of communication distance.

[0004] IEEE 802.11n is a technical standard established to overcome the communication speed limitations that have been identified as a weakness of wireless LANs. IEEE 802.11n aims to increase network speed and reliability and extend the operating distance of wireless networks. Specifically, IEEE 802.11n supports high throughput (HT) of up to 540 Mbps and is based on MIMO (Multiple Inputs and Multiple Outputs) technology, which 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 WLAN adoption continues to grow and applications become more diverse, the need for new WLAN systems is emerging to support data throughput rates (Very High Throughput, VHT) higher than those supported by IEEE 802.11n. Among these, IEEE 802.11ac supports wide bandwidth (80MHz-160MHz) in the 5GHz frequency band. While the IEEE 802.11ac standard is defined only in the 5GHz band, initial 802.11ac chipsets are expected to support operation in the 2.4GHz band as well for backward compatibility with existing 2.4GHz products. Theoretically, this standard enables multi-station WLAN speeds of at least 1Gbps and maximum single-link speeds of at least 500Mbps. This is achieved by expanding the air interface concepts adopted in 802.11n, including wider radio frequency bandwidth (up to 160MHz), more MIMO spatial streams (up to 8), multi-user MIMO, and denser modulation (up to 256QAM). Additionally, 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, making it suitable for streaming large amounts of data and high-bitrate video, such as uncompressed HD video. However, the 60GHz frequency band has the disadvantage of being 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 nearing completion as the successor to 802.11ac and 802.11ad in order 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, high-frequency-efficient communication must be provided both indoors and outdoors in the presence of a high density of stations and APs (Access Points), and various technologies are being developed to achieve this.

[0007] Additionally, development of a new WLAN standard has begun to increase maximum transmission speeds to support new multimedia applications such as high-definition video and real-time gaming. IEEE 802.11be (Extremely High Throughput, EHT), the seventh generation WLAN standard, is currently being developed with the goal of supporting transmission rates of up to 30Gbps in the 2.4 / 5 / 6GHz bands through wider bandwidth, increased spatial streams, and multi-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. [Means for solving the problem]

[0009] According to an embodiment of the present invention, an AP multilink device includes a transceiver unit and a processor. When transmitting to a non-AP multilink device operating over a first link and a second link, the first and second links being non-STR (simultaneous transmit and receive) links that do not support simultaneous reception by the non-AP multilink device over one link and transmission by the non-AP multilink device over the other link, the processor can determine whether to transmit to the non-AP multilink device over the second link based on whether the non-AP multilink device is transmitting over the first link.

[0010] The processor may not transmit to the non-AP multilink device on the second link if the non-AP multilink device is transmitting on the first link.

[0011] When the non-STR multi-link device is transmitting on the first link, the processor can transmit on the second link to another device other than the non-AP multi-link device instead of transmitting to the non-AP multi-link device.

[0012] When transmitting to a device other than the non-AP multilink device on the second link, the processor can transmit traffic having the same priority as or higher priority than the traffic transmitted to the non-AP multilink device.

[0013] The processor can maintain the value of a contention window (CW) used for channel access for transmission to the non-AP multilink device in the second link and use it for channel access for transmission to the other device. In the channel access procedure for the AP multilink device, the multilink device obtains a random number within the CW and sets it as an initial value of a backoff counter, decrements the backoff counter by 1 when the channel is detected as idle during a slot time, and performs transmission when the backoff counter reaches 0.

[0014] The processor may perform transmissions whose ends are synchronized between the first link and the second link. In this case, the transmissions whose ends are synchronized between the first link and the second link may end with a time difference within a pre-specified time interval. The processor may receive a transmission subsequent to the synchronized transmission from at least one of the first link and the second link. In this case, an interval between the subsequent transmission and the synchronized transmission transmitted on the link on which the subsequent transmission was transmitted may be the sum of a single-interval-frame (SIFS) and a time within the pre-specified time interval.

[0015] In the channel access procedure of the AP multilink device, the AP multilink device may obtain a random number within a CW and set it as an initial value of a backoff counter, decrement the backoff counter by 1 if the channel is detected as idle during a slot time, and perform transmission when the backoff counter reaches 0. When the channel access procedure is completed on the first link, the processor may perform transmission on the first link and the second link if the channel of the second link is idle for a first predetermined time.

[0016] The processor may, upon completion of a channel access procedure on the first link, begin transmission on the first link and the second link within a second predetermined time difference if the channel of the second link is idle for a predetermined time.

[0017] A non-AP multilink device according to an embodiment of the present invention includes a transceiver unit and a processor. The non-AP multilink device operates on a first link and a second link, which are non-STR (simultaneous transmit and receive) links that do not support simultaneous reception by the non-AP multilink device on one link and transmission by the non-AP multilink device on the other link. The processor is capable of not transmitting on the second link while transmission is being performed on the first link, and of starting an RTS / CTS (request to send / clear to send) frame exchange on the second link after transmission on the first link is completed.

[0018] The processor can receive transmissions whose ends are synchronized on the first link and the second link. In this case, the transmissions whose ends are synchronized on the first link and the second link may end with a time difference within a pre-specified time interval. The processor can transmit a transmission subsequent to the synchronized transmission on at least one of the first link and the second link. In this case, the interval between the subsequent transmission and the synchronized transmission transmitted on the link on which the subsequent transmission was transmitted may be the sum of a single-interval-frame (SIFS) and a time within the pre-specified time interval.

[0019] When the frequency band of one of the links is changed, information regarding whether STR is supported can be transmitted.

[0020] In the channel access procedure of the non-AP multilink device, the non-AP multilink device obtains a random number within a contention window (CW) and sets it as the initial value of a backoff counter, decrements the backoff counter by 1 if the channel is detected as idle during a slot time, and performs transmission when the backoff counter reaches 0. The processor can maintain the value of the backoff counter for the unused transmission as 0.

[0021] In the channel access procedure of the non-AP multilink device, the non-AP multilink device may obtain a random number within a CW and set it as an initial value of a backoff counter, decrement the backoff counter by 1 if the channel is detected as idle during a slot time, and perform transmission when the backoff counter reaches 0. In this case, when the channel access procedure is completed on the first link, the processor may perform transmission on the first link and the second link if the channel of the second link is idle for a first predetermined time.

[0022] The processor may, upon completion of a channel access procedure on the first link, begin transmission on the first link and the second link within a second predetermined time difference if the channel of the second link is idle for a predetermined time.

[0023] An operating method of an AP multilink device according to one embodiment of the present invention includes, when transmitting on the second link to a non-AP multilink device operating on a first link and a second link, which are non-STR (simultaneous transmit and receive) links in which transmission is not supported on the other link when reception is performed on either link, determining whether to transmit to the non-AP multilink device on the second link based on whether the non-AP multilink device is transmitting on the first link.

[0024] The step of determining whether to transmit to the non-AP multilink device on the second link based on whether transmission is in progress on the first link may include a step of not transmitting to the non-AP multilink device on the second link if the non-AP multilink device is transmitting on the first link.

[0025] The operating method may further include a step of transmitting to another device other than the non-AP multilink device on the second link instead of transmitting to the non-AP multilink device if the non-STR multilink device is transmitting on the first link.

[0026] The step of transmitting to a device other than the non-AP multilink device may further include the step of transmitting traffic having the same priority or higher priority as the traffic transmitted to the non-AP multilink device when transmitting to a device other than the non-AP multilink device on the second link.

[0027] The operating method may further include maintaining a contention window (CW) value used for channel access for transmission to the non-AP multilink device in the second link and using it for channel access for transmission to the other device. In the channel access procedure of the AP multilink device, the multilink device may obtain a random number within the CW and set it as an initial value of a backoff counter, decrement the backoff counter by 1 if the channel is detected as idle during a slot time, and perform transmission when the backoff counter reaches 0.

[0028] The operating method includes performing transmissions in which the end of transmission is synchronized between the first link and the second link, and the transmissions in which the end of transmission is synchronized between the first link and the second link are terminated with a time difference within a predetermined time period; and

[0029] The method may further include receiving a transmission subsequent to the synchronized transmission from at least one of the first link and the second link, wherein the interval between the subsequent transmission and the synchronized transmission transmitted on the link on which the subsequent transmission was transmitted is the sum of a single interval per frame (SIFS) and a time within a pre-specified time interval.

[0030] In the channel access procedure of the AP multilink device, the AP multilink device may obtain a random number within a contention window (CW) and set it as an initial value of a backoff counter, decrement the backoff counter by 1 if the channel is detected as idle during a slot time, and perform transmission when the backoff counter reaches 0. The operating method may further include, upon completion of the channel access procedure in the first link, performing transmission in the first link and the second link if the channel of the second link is idle for a first predetermined time.

[0031] The operating method may further include starting transmission on the first link and the second link within a second predetermined time difference if the channel of the second link is idle for a predetermined time after the channel access procedure is completed on the first link. [Effects of the Invention]

[0032] An embodiment of the present invention provides a wireless communication method that efficiently uses multilinks and a wireless communication terminal that uses the same. [Brief explanation of the drawings]

[0033] [Figure 1] 1 is a diagram showing a wireless LAN system according to an embodiment of the present invention. [Figure 2] FIG. 10 is a diagram showing a wireless LAN system according to another embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing the configuration of a station according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram illustrating a configuration of an access point according to an embodiment of the present invention. [Figure 5] 1 is a diagram illustrating a process in which a STA establishes 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(a)] 1 illustrates various Extremely High Throughput (EHT) Physical Protocol Data Unit (PPDU) formats and methods for indicating the same according to an embodiment of the present invention. [Figure 8(b)] 1 illustrates an example of various EHT PPDU formats and methods for indicating the same according to an embodiment of the present invention. [Figure 8(c)]1 illustrates an example of various EHT PPDU formats and methods for indicating the same according to an embodiment of the present invention. [Figure 8(d)] 1 illustrates an example of various EHT PPDU formats and methods for indicating the same according to an embodiment of the present invention. [Figure 9] 1 shows a multi-link device according to an embodiment of the present invention; [Figure 10] 1 illustrates simultaneous transmission of different links in a multi-link operation according to an embodiment of the present invention. [Figure 11] 10 illustrates the operation of a multi-link device when a link is changed according to one embodiment of the present invention. [Figure 12] 10 shows that, according to one embodiment of the present invention, when any one station in a non-STR multilink device is receiving, other stations in the non-STR multilink device are prohibited from accessing the channel. [Figure 13] 10 shows an operation of canceling channel access prohibition when it is confirmed that the intended recipient of a PPDU received by a station in a non-STR multilink device is not a station according to an embodiment of the present invention. [Figure 14] 10 shows a station according to an embodiment of the present invention accessing a channel after channel access prohibition is lifted. [Figure 15(a)] 10 illustrates an operation of a station transmitting after channel access prohibition is lifted according to an embodiment of the present invention. [Figure 15(b)] 10 illustrates an operation of a station transmitting after channel access prohibition is lifted according to an embodiment of the present invention. [Figure 16] 10 illustrates transmissions based on the state of stations in a non-STR multilink device according to an embodiment of the present invention. [Figure 17(a)] This shows the situation where interference or collision between links may occur. [Figure 17(b)] This shows the situation where interference or collision between links may occur. [Figure 18(a)]10 illustrates an operation in which an STR multilink device stops transmission to a non-STR multilink device according to an embodiment of the present invention. [Figure 18(b)] 10 illustrates an operation in which an STR multilink device stops transmission to a non-STR multilink device according to an embodiment of the present invention. [Figure 19] 10 shows how the STR multilink device processes the value of CW when it recognizes a transmission collision between links according to an embodiment of the present invention. [Figure 20(a)] 10 illustrates an operation of an STR multilink device accessing a channel again after halting transmission to a non-STR multilink device according to an embodiment of the present invention. [Figure 20(b)] 10 illustrates an operation of an STR multilink device accessing a channel again after halting transmission to a non-STR multilink device according to an embodiment of the present invention. [Figure 20(c)] 10 illustrates an operation of an STR multilink device accessing a channel again after halting transmission to a non-STR multilink device according to an embodiment of the present invention. [Figure 21] 10 illustrates an operation in which an STR multilink device transmits a CTS-to-Self frame before transmitting to a non-STR multilink device according to an embodiment of the present invention. [Figure 22] 1 illustrates that multiple APs included in an STR multilink device transmit to multiple stations included in one non-STR multilink device according to an embodiment of the present invention. [Figure 23] According to an embodiment of the present invention, multiple APs included in an STR multilink device perform multiple transmissions with synchronized end of transmission to multiple stations included in one non-STR multilink device. [Figure 24] 1 illustrates multilink devices exchanging RTS / CTS frames according to an embodiment of the present invention. [Figure 25] 25 illustrates a hidden node problem that occurs in the RTS / CTS frame exchange procedure according to the embodiment described in FIG. 24. [Figure 26]1 illustrates multilink devices exchanging RTS / CTS frames according to an embodiment of the present invention. [Figure 27] 10 shows that a multi-link device transmits a response to a control frame exceptionally even when channel access is prohibited according to an embodiment of the present invention. [Figure 28] Indicates that a transmission for a station on a non-STR multilink device should be retransmitted. [Figure 29] 10 shows that the control frame is transmitted on a link on which a station that is not prohibited from channel access operates, rather than on a link on which a station that is prohibited from channel access operates, according to an embodiment of the present invention. [Figure 30] 10 illustrates a multi-link device sending an ACK according to an embodiment of the present invention. [Figure 31(a)] 10 shows an element field indicating information regarding support for receiving or transmitting a sink PPDU according to an embodiment of the present invention. [Figure 31(b)] 10 shows an element field indicating information regarding support for receiving or transmitting a sink PPDU according to an embodiment of the present invention. [Figure 32] 1 illustrates a non-STR multi-link device operating in inter-link TXOP power save mode according to an embodiment of the present invention. [Figure 33] 10 illustrates that a station in a non-STR multilink device enters a power saving state while waiting to receive a sync PPDU according to an embodiment of the present invention. [Figure 34] 10 illustrates a state in which a station in a non-STR multilink device enters a power saving state while waiting to receive a sync PPDU according to yet another embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0034] The terms used in this specification are generally used as widely as possible, taking into consideration the functions of the present invention. However, these may vary depending on the intentions of engineers in the relevant technical field, customs, or the emergence of new technologies. In addition, in certain cases, the applicant may have arbitrarily selected terms, and in such cases, the meanings thereof will be described in the relevant description of the invention. Therefore, it is made clear that the terms used in this specification should be interpreted not simply as names of terms, but based on the substantive meanings of the terms and the overall content of this specification.

[0035] Throughout this specification, when a component is referred to as being "connected" to another component, this includes not only when the component is "directly connected" to another component, but also when the component is "electrically connected" to another component via another component in between. Furthermore, when a component is referred to as "comprising" a specific component, this does not mean that the component may exclude the other component, but may further include the other component, unless otherwise specified. In addition, limitations such as "greater than" or "less than" based on a specific critical value may be appropriately substituted with "exceeds" or "less than," respectively, depending on the embodiment.

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

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

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

[0039] As shown in FIG. 1, infrastructure BSSs BSS1 and BSS2 include one or more stations STA1, STA2, STA3, STA4, and STA5, access points AP-1 and AP-2 that are stations providing distribution services, and a distribution system DS that connects multiple access points AP-1 and AP-2.

[0040] A station (STA) is any device that includes a medium access control (MAC) and a physical layer interface for a wireless medium according to the IEEE 802.11 standard. In a broad sense, the term "station" encompasses not only non-AP stations but also APs. In this specification, the term "terminal" refers to either a non-AP or an AP, or both. A station for wireless communication includes a processor and a communication unit, and may further include a user interface and a display unit, depending on the embodiment. The processor generates frames to be transmitted over a wireless network, processes frames received over 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 over the wireless network for the station. In this specification, the term "terminal" encompasses user equipment (UE).

[0041] An access point (AP) is an entity that provides a connection to a distribution system (DS) via a wireless medium for associated stations. In an infrastructure BSS, communication between non-AP stations is generally performed via the AP. However, if a direct link is established, direct communication is also possible between non-AP stations. Meanwhile, in the present invention, the term AP is used as a concept including a personal BSS coordination point (PCP), but in a broader sense, it also includes 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, an AP is also referred to as a base wireless communication terminal, but in a broader sense, the term 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 for communication with multiple wireless communication terminals.

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

[0043] 2 is a diagram showing an independent BSS, which is a wireless LAN system according to another embodiment of the present invention. In the embodiment of FIG. 2, the same or corresponding parts as those in the embodiment of FIG. 1 will not be described again.

[0044] BSS3 shown in Figure 2 is an independent BSS and does not include an AP, so none of the stations (STA6, STA7) are 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.

[0045] 3 is a block diagram showing the configuration of a station 100 according to an embodiment of the present invention. As shown, 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.

[0046] First, the communication unit 120 transmits and receives wireless signals such as WLAN packets and may be incorporated into or external to 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 using 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 above 7.125 GHz and a communication module using a frequency band below 7.125 GHz. Each communication module may perform wireless communication with an AP or an external station based on the WLAN standard of the frequency band supported by the communication module. The communication unit 120 may operate only one communication module at a time or multiple communication modules simultaneously, depending on the performance and requirements of the station 100. When the station 100 includes multiple communication modules, each communication module may be provided independently, or multiple modules may be integrated into a single chip. In the embodiment of the present invention, the communication unit 120 may represent a radio frequency (RF) communication module that processes RF signals.

[0047] 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 instructions from the processor 110 using various output means.

[0048] Next, 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 processed by the processor 110 or the control commands of the processor 110. The memory 160 also stores control programs and various data used by the station 100. The control programs include a connection program required for the station 100 to connect to an AP or an external station.

[0049] 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 the transmission and reception of data between the units. According to an embodiment of the present invention, the processor 110 executes a program for connection with an AP stored in the memory 160 and receives a communication setup message transmitted by the AP. The processor 110 also reads information about the station 100's preferences contained in the communication setup message and requests connection to the AP based on the information about the station 100's preferences. The processor 110 of the present invention may refer to a main control unit of the station 100, or, depending on the embodiment, may refer to a control unit for individually controlling some components of the station 100, such as the communication unit 120. That is, the processor 110 may be a modem that modulates and demodulates wireless signals transmitted and received by the communication unit 120, or a modulator and / or demodulator. The processor 110 controls various operations for transmitting and receiving wireless signals in the station 100 according to an embodiment of the present invention. A detailed embodiment of this will be described later.

[0050] The station 100 shown in FIG. 3 is a block diagram according to an embodiment of the present invention, and the separate blocks indicate the logically separated elements of the device. Therefore, the above-described device elements may be mounted on a single chip or multiple chips depending on the device design. For example, the processor 110 and the communication unit 120 may be integrated into a single chip or may be mounted on separate chips. Furthermore, in embodiments 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.

[0051] 4 is a block diagram showing the configuration of an AP 200 according to an embodiment of the present invention. As shown, 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, duplicated descriptions 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.

[0052] 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 multiple 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, 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz. Preferably, the AP 200 may include a communication module using a frequency band above 7.125 GHz and a communication module using a frequency band below 7.125 GHz. 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 multiple communication modules simultaneously, depending on the performance and requirements of the AP 200. In the embodiment of the present invention, the communication unit 220 may represent an RF (Radio Frequency) communication module that processes RF signals.

[0053] The memory 260 stores control programs used by the AP 200 and various data associated therewith. These control programs include a connection program that manages station connections. The processor 210 also controls each unit of the AP 200 and controls data transmission and reception between the units. According to an embodiment of the present invention, the processor 210 executes a program for connecting with a station stored in the memory 260 and transmits a communication setup message to one or more stations. The communication setup message includes information regarding connection preferences for each station. The processor 210 also performs connection setup in response to a station connection request. According to an embodiment, the processor 210 is a modem or a modulator / demodulator that modulates and demodulates wireless signals transmitted and received by the communication unit 220. The processor 210 controls various operations for transmitting and receiving wireless signals by the AP 200 according to an embodiment of the present invention. A detailed embodiment of this will be described later.

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

[0055] 5, a link between the STA 100 and the AP 200 is established through three steps: scanning, authentication, and association. First, the scanning step is a step in which the STA 100 acquires connection information for the BSS operated by the AP 200. There are two scanning methods: 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.

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

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

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

[0059] A terminal performing WLAN communication performs carrier sensing to check whether a channel is occupied before transmitting data. If a wireless signal above a certain strength 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 or not a signal is detected is called the CCA threshold. If a wireless signal above the CCA threshold is received by the terminal and the terminal is the receiver, the terminal processes the received wireless signal. On the other hand, if no wireless signal is detected from the channel or a wireless signal with a strength below the CCA threshold is detected, the channel is determined to be idle.

[0060] If the channel is determined to be idle, each terminal having data to transmit performs a backoff procedure after an Inter Frame Space (IFS), such as an Arbitration IFS (AIFS) or a PCF IFS (PIFS), depending on the status of each terminal. In some embodiments, the AIFS is used as a configuration replacing the conventional DCF IFS (DIFS). Each terminal waits while decrementing a slot time equal to a random number determined for the corresponding terminal during the idle interval of the channel, and a terminal that has exhausted all of its slot time attempts to access the corresponding channel. The period during which each terminal performs the backoff procedure is called a contention window period. In this case, the random number can be called a backoff counter. That is, the initial value of the backoff counter is set by an integer, which is a random number obtained by the terminal. If the terminal detects that the channel is idle during the slot time, the terminal can decrement the backoff counter by 1. If the backoff counter reaches 0, the terminal may be allowed to perform channel access on the corresponding channel. Therefore, if the channel is idle during the AIFS time and the backoff counter slot time, the terminal may be allowed to transmit.

[0061] If a specific terminal successfully accesses the channel, it transmits data over 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 new random numbers assigned to each terminal are determined within a range (2*CW) twice the range of the random numbers previously assigned to the terminal (contention window, CW). Meanwhile, each terminal attempts access by performing a backoff procedure again in the next contention window period. At this time, each terminal performs the backoff procedure from the slot time remaining in the previous contention window period. In this way, terminals communicating over a wireless LAN can avoid collisions with each other on a specific channel.

[0062] <Examples of various PPDU formats>

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

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

[0065] Referring to FIG. 7(b), the preamble of the HE PPDU further includes a Repeated Legacy Short Training field (RL-SIG), a High Efficiency Signal A field (HE-SIG-A), a High Efficiency Signal B field (HE-SIG-B), a High Efficiency Short Training field (HE-STF), and a High Efficiency Long Training field (HE-LTF) 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 vary depending on the HE PPDU format. For example, HE-SIG-B may be used only in the HE MU PPDU format.

[0066] Referring to FIG. 7(c), the preamble of the EHT PPDU further includes a Repeated Legacy Short Training field (RL-SIG), a Universal Signal field (U-SIG), an Extremely High Throughput Signal A field (EHT-SIG-A), an Extremely High Throughput Signal B field (EHT-SIG-A), an Extremely High Throughput Short Training field (EHT-STF), and an Extremely High Throughput Long Training field (EHT-LTF) 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 may be referred to as an EHT preamble. The specific configuration of the non-legacy preamble may vary depending on the EHT PPDU format. For example, EHT-SIG-A and EHT-SIG-B may be used only in some EHT PPDU formats.

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

[0068] 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 rates of 6, 9, 12, 18, 24, 36, 48, or 54 Mbps, which is a combination of a modulation scheme such as BPSK, QPSK, 16-QAM, or 64-QAM and a code rate such as 1 / 2, 2 / 3, or 3 / 4. The combined information in the L_RATE and L_LENGTH fields indicates the total length of the PPDU. In a non-legacy PPDU format, the L_RATE field is set to the minimum rate of 6 Mbps.

[0069] The unit of the L_LENGTH field is byte, and a total of 12 bits are allocated, allowing signaling up to 4095. In combination with the L_RATE field, the length of the PPDU can be indicated. In this case, legacy and non-legacy terminals can interpret the L_LENGTH field in different ways.

[0070] First, a legacy or non-legacy terminal analyzes the length of the PPDU using the L_LENGTH field 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 the duration of one symbol of the 64FFT. Therefore, by adding 3 bytes corresponding to the SVC field and the Tail field to the L_LENGTH field value and dividing this by 3 bytes, which is the transmission amount of one symbol, the number of reference symbols for the 64FFT after the L-SIG is obtained. The obtained number of symbols is multiplied by 4 us, which is the duration of one symbol, and then 20 us, which is required to transmit the L-STF, L-LTF, and L-SIG, is added to obtain the length of the PPDU, i.e., the reception time (RXTIME). This can be expressed mathematically as shown in Equation 1 below.

[0071]

number

[0072] At this time,

[0073]

number

[0074] represents the smallest natural number greater than or equal to x. Since the maximum value of the L_LENGTH field is 4095, the length of the PPDU may be set to a maximum of 5.484 ms. A non-legacy terminal transmitting the PPDU must set the L_LENGTH field as shown in Equation 2 below.

[0075]

number

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

[0077]

number

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

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

[0080] The VI bit will maintain its current bit configuration, so even if a subsequent generation PPDU is defined, current 11be UEs can obtain information about the PPDU from the VI field of the PPDU. To this end, the VI field consists of the PHY version, UL / DL, BSS color, TXOP, and Reserved fields. The PHY version field is 3 bits long and serves to sequentially distinguish between 11be and subsequent generations of WLAN standards. 11be has a value of 000b. The UL / DL field identifies whether the PPDU is an uplink or downlink PPDU. The BSS color represents a BSS identifier defined in 11ax and has a value of 6 or more bits. The TXOP represents the transmit opportunity duration (Transmit Opportunity Duration) transmitted in the MAC header. By adding it to the PHY header, the length of the TXOP containing the PPDU can be inferred without decoding the MPDU, and has a value of 7 or more bits.

[0081] The VD field, which is signaling information useful only for 11be version PPDUs, may consist of fields commonly used in any PPDU format, such as the PPDU format and BW, as well as fields defined differently for each PPDU format. The PPDU format is a separator that distinguishes between EHT SU (Single User), EHT MU (Multiple User), EHT TB (Trigger-based), and EHT ER (Extended Range) PPDUs. The BW field broadly signals five basic PPDU BW options: 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), as well as various remaining PPDU BWs formed by preamble puncturing. After signaling at 320 MHz, a portion of 80 MHz may be punctured. In addition, the punctured and modified channel shape may be signaled directly in the BW field, or may be signaled using both the BW field and a field that appears after the BW field (for example, 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.

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

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

[0084] When a portion 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). In the case of an 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 sent to it. 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 in the EHT-SIG field and / or the MCS, which is the modulation method. The EHT-SIG field may include information on the size and location of the RU assigned to each user.

[0085] In the case of an 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 efficiently receive the SU PPDU only by recognizing punctured RUs in between. Therefore, the AP can transmit the SU PPDU including information on punctured RUs among the RUs assigned to the STA (e.g., puncturing pattern of the RUs). That is, in the case of an 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 can signal the type of discontinuous channels appearing within the bandwidth.

[0086] The type of 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, since the SU PPDU is a PPDU transmitted only to a single UE, the STA can recognize its allocated bandwidth from the BW field included in the PPDU and can recognize punctured resources within 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 excluding specific channels of the punctured resource units. In this case, multiple RUs allocated to the STA may be configured with different frequency bands or tones.

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

[0088] This invention proposes a method for signaling the discontinuous channel type of an SU PPDU and illustrates the discontinuous channel type determined by the proposed method. It also proposes a method for signaling the primary 160 MHz and secondary 160 MHz puncturing types in a 320 MHz BW configuration of an SU PPDU. The discontinuous channel types allowed when the above discontinuous channel type definition method is applied and a method for signaling the discontinuous channel type with 3 bits are shown in Figures 17 to 19.

[0089] In addition, one embodiment of the present invention proposes a method of varying the PPDU configuration indicated by the preamble puncturing BW value depending on the PPDU format signaled in the PPDU format field. Assuming that the BW field is 4 bits, in the case of an EHT SU PPDU or TB PPDU, an EHT-SIG-A symbol can be further signaled after the U-SIG, or no EHT-SIG-A can be signaled at all. Taking this into consideration, up to 11 puncturing modes must be fully signaled using only the BW field of the U-SIG. However, in the case of an EHT MU PPDU, an EHT-SIG-B symbol is further signaled after the U-SIG, so up to 11 puncturing modes can be signaled in a different manner than in the case of an SU PPDU. In the case of an EHT ER PPDU, the BW field can be set to 1 bit to signal whether the PPDU uses a 20 MHz or 10 MHz bandwidth. Detailed puncturing patterns for each PPDU type will be described in detail below with reference to FIGS. 11 and 12.

[0090] Figure 7(f) shows the format-specific field configuration of the VD field when the PPDU format field of the U-SIG indicates an EHT MU PPDU. For an MU PPDU, SIG-B, a signaling field for simultaneous reception by multiple users, is required. SIG-B may be transmitted after the U-SIG without a separate SIG-A. For this purpose, the U-SIG must signal information for decoding SIG-B. These fields include the SIG-B MCS, SIG-B DCM, number of SIG-B symbols, SIG-B compression, and number of EHT-LTF symbols.

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

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

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

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

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

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

[0097] The EHT MU PPDU described in (c) of Figure 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 transmitted PPDU to the STA through the user specific field of the EHT-SIG-B. 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.

[0098] Specifically, the resource unit allocation (RA) field of the HE-SIG-B field included in the HE MU PPDU may include information regarding the configuration of resource units (e.g., the division type of resource units) in a specific bandwidth (e.g., 20 MHz) on the frequency axis. That is, the RA field may indicate the configuration of resource units divided by the bandwidth for transmitting the HE MU PPDU so that the STA can receive the PPDU. Information about 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.

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

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

[0101] When a single wireless communication device communicates using multiple links, the communication efficiency of the wireless communication device can be improved. In this case, a link is a physical path and may be configured as a single wireless medium that can be used to transmit an MSDU (MAC service data unit). For example, when the frequency band of one link is being used by another wireless communication device, the wireless communication device can continue communication using another link. In this way, the wireless communication device can effectively use multiple channels. Furthermore, when a wireless communication device simultaneously communicates using multiple links, the overall throughput can be improved. However, existing wireless LANs are specified on the assumption that one wireless communication device uses one link. Therefore, a wireless LAN operation method for using multiple links is needed. A wireless communication method for a wireless communication device using multiple links will be described with reference to FIGS. 9 to 26. First, a specific embodiment of a wireless communication device using multiple links will be described with reference to FIG. 9.

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

[0103] A multi-link device (MLD) may be defined for the wireless communication method using multiple links described above. The multi-link device may represent a device having one or more affiliated stations. Depending on a specific embodiment, the multi-link device may represent a device having two or more affiliated stations. The multi-link device may also exchange multi-link elements. The multi-link element includes information about 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 referred to as a multi-link logical entity (MLLE) or a multi-link entity (MLE). The multi-link device may have one medium access control service access point (SAP) up to a logical link control (LLC). The MLD may also have one MAC data service.

[0104] Multiple stations included in a multilink device can operate on multiple links. Also, multiple stations included in a multilink device can operate on multiple channels. Specifically, multiple stations included in a multilink device can operate on different links or different channels. For example, multiple stations included in a multilink device can operate on different channels, such as 2.4 GHz, 5 GHz, and 6 GHz.

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

[0106] 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 via a first link (Link1). The second AP (AP2) and the second non-AP STA (non-AP STA2) communicate via a second link (Link2). The third AP (AP3) and the third non-AP STA (non-AP STA3) communicate via a third link (Link3).

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

[0108] Multilink configuration may be established through negotiation between peer stations. Specifically, multilink configuration may be established through communication between stations without communication with an AP. Multilink configuration may also be established through any one of the links. For example, even if the first to third links are established through multilink, multilink configuration may be established through the first link.

[0109] In addition, a mapping between a traffic identifier (TID) and a link may be configured. Specifically, frames corresponding to a specific TID value may be exchanged only through a pre-specified link. The mapping between a TID and a link may be configured on a directional basis. For example, when multiple links are configured between a first multilink device and a second multilink device, the first multilink device may be configured to transmit frames of the first TID to the multiple first links, and the second multilink device may be configured to transmit frames of the second TID to the first link. In addition, a default setting may exist for the mapping between TIDs and links. Specifically, if no additional settings are configured in the multilink configuration, the multilink device may exchange frames corresponding to TIDs on each link according to a default setting. In this case, the default setting may be that all TIDs are exchanged on any one link.

[0110] The TID will be described in detail. The TID is an ID for classifying traffic and data to support quality of service (QoS). 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). There may be 16 distinct TIDs. For example, the TID may be designated as any one of 0 to 15. Different TID values ​​may be designated depending on an access policy, a channel access method, or a medium access method. For example, when enhanced distributed channel access (EDCA) or hybrid coordination function contention-based channel access (HCAF) is used, the TID may be assigned a value ranging from 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. Furthermore, 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. Furthermore, 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.

[0111] 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 EDCA channel contention. 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-level ACs. For example, AC_VI may be further subdivided into AC_VI primary and AC_VI alternate. AC_VO may be further subdivided into AC_VO primary and AC_VO alternate. UP or TID may be mapped to an 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 decreasing priority in that order. That is, 1 may have a lower priority, and 7 may have a higher priority. Therefore, the order of priority may be AC_BK, AC_BE, AC_VI, and AC_VO. Also, AC_BK, AC_BE, AC_VI, and AC_VO can correspond to ACI (AC index) 0, 1, 2, and 3, respectively. Due to the characteristics of TID, the mapping between TID and link can represent the mapping between AC and link.The mapping between links and ACs can also represent the mapping between TIDs and links.

[0112] As described above, a TID may be mapped to each of multiple links. The mapping may specify the links through which traffic corresponding to a specific TID or AC can be exchanged. Furthermore, the TID or AC that can be transmitted for each transmission direction within a link may be specified. As described above, a default setting may exist for the mapping between TIDs and links. Specifically, if no additional settings are configured in the multilink configuration, 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.

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

[0114] The above-described 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 active or where channel conditions are good. The above-described TID-to-link mapping may also allow stations to remain in a power-saving state for a longer period of time.

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

[0116] Depending on the implementation of the multi-link device, simultaneous operation of the multi-links may not be supported. For example, a multi-link device may support simultaneous transmission on multiple links, simultaneous reception on multiple links, or transmission on one link while receiving on another link. Reception or transmission on one link may affect reception or transmission on another link. Specifically, transmission on one link may interfere with other links. Interference from one link of a multi-link device affecting other links may be called internal leakage. The smaller the frequency spacing between links, the greater the internal leakage. If the internal leakage is not too large, transmission on one link can occur when transmission on another link. If the internal leakage is large, transmission on one link cannot occur when transmission on another link. This simultaneous operation of the multi-link device on multiple links may be called STR (simultaneous transmit and receive, simultaneous transmission and reception). For example, a multilink device transmitting on multiple links simultaneously, transmitting on one link while receiving on another link, or receiving on multiple links simultaneously can be referred to as STR.

[0117] As mentioned above, a multilink device can support STR, or can support it with limitations. Specifically, a 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 greater than a predetermined magnitude, the multilink device may not be able to perform STR.

[0118] A station can exchange information about its STR capability with other stations. Specifically, a station can exchange information about whether or not the station has limitations on its ability to simultaneously transmit or receive on multiple links. Specifically, the information about whether or not the station has limitations on its ability to transmit or receive on multiple links can indicate whether or not the station will transmit or receive on multiple links simultaneously, or whether or not transmission and reception are simultaneous. Furthermore, the information about whether or not the station has limitations on its ability to transmit or receive on multiple links can be information indicated in stages. Specifically, the information about whether or not the station has limitations on its ability to transmit or receive on multiple links can be information indicating a stage indicating the magnitude of internal leakage. In a specific embodiment, the information indicating a stage indicating the magnitude of internal leakage can be information indicating a stage indicating the magnitude of interference caused by internal leakage. In yet another specific embodiment, the information indicating a stage indicating the frequency spacing between links that may affect internal leakage can be information indicating a stage indicating the relationship between the frequency spacing between links and the magnitude of internal leakage.

[0119] In FIG. 10, a first station (STA1) and a second station (STA2) are affiliated with one non-AP multilink device. A first AP (AP1) and a second AP (AP2) may also be affiliated with 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 can perform limited STR. When the second station (STA2) transmits on the second link (Link2), the first station (STA1)'s reception on the first link (Link1) may be interrupted by the transmission on the second link (Link2). For example, in the following case, the first station (STA1)'s reception on the first link (Link1) may be interrupted by the transmission on the second link (Link2). The second station (STA2) transmits the first data (Data1) over 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) over the second link (Link2). At this time, the transmission of the second data (Data2) and the transmission of the response (Ack for Data1) to the first data (Data1) may overlap. In this case, the transmission to the second station (STA2) over the second link (Link2) may cause interference to the first link (Link1). As a result, the first station (STA1) may not receive the response (Ack for Data1) to the first data (Data1).

[0120] The operation of the multilink device for channel access will be described below. The multilink operation without a specific description can follow the channel access procedure described in FIG.

[0121] A multilink device can perform channel access independently from multiple links. In this case, the channel access may be backoff-based channel access. When a multilink device performs channel access independently from multiple links and the backoff counters for multiple links reach zero, the multilink device can start transmission simultaneously from multiple links. In a specific embodiment, when one of the backoff counters for multiple links reaches zero and a predetermined condition is met, the multilink device can perform channel access not only for the link whose backoff counter has reached zero but also for other links whose backoff counters have not reached zero. Specifically, when one of the backoff counters for multiple links reaches zero, the multilink device can perform energy sensing on other links whose backoff counters have not reached zero. In this case, if energy greater than or equal to a predetermined value is not detected, the multilink device can perform channel access not only for the link whose backoff counter has reached zero but also for the link for which energy sensing has been performed. This allows the multilink device to start transmission simultaneously from multiple links. The threshold used for energy sensing may be smaller than the threshold used for determining whether to decrement the backoff counter. Furthermore, when determining whether to decrement the backoff counter, the multilink device can sense any type of signal, not just a WLAN signal. Furthermore, in the energy sensing described above, 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 detect signals detected due to internal leakage through energy sensing. Furthermore, as described above, the threshold used for energy sensing may be smaller than the threshold used when determining whether to decrement the backoff counter. Therefore, even while transmission is occurring on one link, the multilink device can decrement the backoff counter on another link.

[0122] Depending on the degree of interference between links used by the multilink device, the multilink device 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 perceived by other stations in the multilink device when one station in the multilink device transmits on one of the links. If transmission on the first link of a first station in the multilink device causes interference of a predetermined magnitude or greater to a second station in the multilink device operating on the second link, the operation of the second station may be restricted. Specifically, reception or channel access of the second station may be restricted. If interference occurs, the second station may fail to decode a received signal due to the interference. Furthermore, if interference occurs, the second station may determine that the channel is in use when accessing the channel using backoff.

[0123] Furthermore, if the transmission of a first station in the multilink device through the first link causes interference of less than a predetermined magnitude to a second station in the multilink device operating through the second link, the first station and the second station can operate independently. Specifically, if the transmission of a first station in the multilink device through the first link causes interference of less than a predetermined magnitude to a second station in the multilink device operating through the second link, the first station and the second station can independently access the channel. Also, if the transmission of a first station in the multilink device through the first link causes interference of less than a predetermined magnitude to a second station in the multilink device operating through the second link, the first station and the second station can independently transmit or receive. If interference of less than a predetermined magnitude occurs, the second station can successfully decode the received signal even in the presence of interference. Also, if interference of less than a predetermined magnitude occurs, the second station can determine that the channel is idle when accessing the channel using backoff.

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

[0125] FIG. 10 shows how the magnitude of interference varies depending on the spacing between link frequency bands and the characteristics of the multilink devices. In the example of FIG. 10, a first multilink device (MLD#1) includes a first station (STA1)-1 operating on a first link (Link1) and a second station (STA1)-2 operating on a second link (Link2). A second multilink device (MLD#2) includes a first station (STA2)-1 operating on a first link (Link1) and a second station (STA2)-2 operating on a second link (Link2). The frequency spacing between the first link (Link1) and the second link (Link2) on which the first multilink device (MLD#1) operates is the same as the frequency spacing between the first link (Link1) and the second link (Link2) on which the second multilink device (MLD#2) operates. However, the magnitude of interference varies depending on the difference between the characteristics of the first multilink device (MLD#1) and 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.

[0126] A multilink device can signal whether or not a station included in the multilink device supports STR. Specifically, an AP multilink device and a non-AP multilink device can exchange whether or not an AP included in the AP multilink device supports STR with whether or not a STA included in the non-AP multilink device supports STR. In this embodiment, an element indicating whether or not STR support is available may be used. The element indicating whether or not STR support is available may be referred to as an STR support element. The STR support element may indicate, with one bit, whether or not a station in the multilink device that transmitted the STR support element supports STR. Specifically, the STR support element may indicate, with one bit, whether or not each station included in the multilink device that transmitted the STR support element supports STR. In this case, if a station supports STR, the bit value may be 1, and if a 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 The STR Support element may include a field having the following information: Stations operating in different frequency bands are assumed to 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 on a first link of 2.4 GHz, and a second station (STA2) and a third station (STA3) operate on 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). Alternatively, the STR Support element may include only one bit if the STR Support element signals two stations.

[0127] 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 a multi-link device may always be determined as STR, and therefore, signaling regarding the presence or absence of STR between a link located at 2.4 GHz and a link located at 5 GHz or 6 GHz may be omitted.

[0128] FIG. 11 shows the operation of the multilink device when a link is changed according to one embodiment of the present invention.

[0129] When the frequency band of a link is changed, the STR assistance element may be exchanged. As described above, whether a station supports STR may vary depending on the distance between the frequency bands of the link, and whether a station supports STR may change when the frequency band of the link is changed. When the frequency band of the link is changed, at least one of a change in the center frequency of the link, a change in the bandwidth of the frequency band, and a 20 MHz primary channel may be included. The AP and the station may exchange the STR assistance element through a request and a response. In another specific embodiment, when the frequency band of the link is changed, the STR assistance element may be exchanged without a separate request. Furthermore, in the above embodiment, when the frequency band of the link is changed, the operating channel of the station may be changed.

[0130] If a station in a non-AP multilink device cannot perform STR, the station in the non-AP multilink device can request a link change from the AP. Specifically, the station in the non-AP multilink device can request at least one of a change in center frequency, a change in frequency band bandwidth, and a change in 20 MHz primary channel. The link change request may be transmitted to the AP through a link for which a change is requested. In yet another specific embodiment, the link change request may be transmitted to the AP through a link for which a change is not requested. In this case, the link change request may include information indicating the link for which a change is requested. The information indicating the link may be a number identifying the link. In this embodiment, the link change may be a change in an operating channel within a frequency band. The link change may also include information regarding a method for changing the link. Specifically, the link change request may indicate whether the center frequency of the link should be moved to a frequency higher than the current center frequency or a frequency lower than the current center frequency. In yet another specific embodiment, the link change request may implicitly indicate a change to a frequency band away from an adjacent link. The link change request may also indicate a reduction in link bandwidth. The link change request may also indicate a change in the location of the primary channel. Specifically, the link change request may indicate a change in the location of the primary channel to a channel in a lower frequency band or a channel in a higher frequency band than the location of the current primary channel. The AP that receives the link change request may change the link in response to the link change request. In a specific embodiment, the AP that receives the link change request may ignore the link change request.

[0131] In the embodiment of Figure 11, the second station (STA2) and the third station (STA3) of the non-AP multilink device are in a state where they cannot support STR. The non-AP multilink device requests the AP multilink device to change the third link (Link3). Upon receiving the link change request, the AP multilink device changes the operating link of the third AP (AP3). At this time, the third station (STA3) operating on the changed third link (Link3) can send a change request to the third AP (AP3). In yet another specific embodiment, a station not operating on the third link (Link3) can send a change request to the AP that does not operate on the third link (Link3).

[0132] When an AP changes a link, the AP may broadcast information about the link change using a beacon frame. In this case, the information about the link change may include information about the link frequency. The information about the link frequency may include at least one of a change in the link center frequency, operating bandwidth, and primary channel. The information about the link change may also include information about the time of the link change. The link change may also be completed when a beacon including information about the link change is transmitted.

[0133] In Figure 11, the link on which the third station (STA3) operates is changed, and the third station (STA3) and the second station (STA2) can support STR. As described above, the non-AP multilink device can send an STR support element to the AP multilink device to signal whether or not it supports the changed STR.

[0134] The above-mentioned link change may not be allowed, or even if a link change occurs, STR may not be supported. Also, as in the embodiment of FIG. 11, an AP multilink device may support STR, but a non-AP multilink device may not support STR. This is because a relatively high-RF device is generally used in an AP multilink device, and a relatively low-RF device is generally used in a non-AP multilink device. Therefore, a method is needed to enable efficient communication between multilink devices even when one of the multilink devices does not support STR. In this case, STR can represent simultaneous transmission and reception. This will be described with reference to FIG. 12.

[0135] FIG. 12 shows that when any one station in a non-STR multilink device is receiving, other stations in the non-STR multilink device are prohibited from accessing the channel according to one embodiment of the present invention.

[0136] When transmission is performed on one link of a non-STR multilink device and reception is performed on another link of the non-STR multilink device, reception and transmission of the non-STR multilink device may fail. To solve this problem, when reception is performed on one link of the non-STR multilink device, channel access may be prohibited on the other links of the non-STR multilink device. Specifically, when reception is performed on one link of the non-STR multilink device, channel access backoff may be prohibited on the other links of the non-STR multilink device. This prevents transmission from starting on the other links of the non-STR multilink device when reception is performed on one link of the non-STR multilink device. In a specific embodiment, when reception begins on one link of the non-STR multilink device, channel access backoff may be prohibited on the other links of the non-STR multilink device. This may be set by a specific bit in memory, such as a channel access prohibition flag. Whether channel access is prohibited may be shared by memory within the multilink device. This embodiment allows channel access prohibition to be implemented without a separate frame exchange. For ease of explanation, unless otherwise specified, channel access prohibition as used herein refers to prohibiting channel access or transmission in order to protect the transmission or reception of non-STR multilink devices.

[0137] When channel access is prohibited, stations operating on the link where channel access is prohibited cannot perform a backoff procedure regardless of the NAV and CCA results. Furthermore, when channel access is prohibited, stations operating on the link where channel access is prohibited cannot transmit regardless of the NAV and CCA results. However, even if channel access is prohibited, stations operating on the link where channel access is prohibited can receive. Furthermore, the prohibition of channel access on the second link due to reception performed on the first link may be lifted when reception on the first link is completed. Specifically, the prohibition of channel access on the second link due to reception performed on the first link may be lifted when reception on the first link is completed. In yet another specific embodiment, the prohibition of channel access on the second link due to reception performed on the first link may be lifted when an ACK is transmitted after reception on the first link is completed. Specifically, the prohibition of channel access on the second link due to reception performed on the first link may be lifted when an ACK is transmitted after reception on the first link is completed. In yet another specific embodiment, channel access prohibition on the second link due to reception on the first link may be lifted when ACK transmission is completed after reception on the first link is completed. Also, immediately after the channel access prohibition is lifted, the station may immediately decrement the backoff counter without additional sensing. Here, additional sensing may refer to sensing performed during a DCF Interframe Space (DIFS). In yet another specific embodiment, if the channel is idle for a pre-specified time immediately before the channel access prohibition is lifted, the station may immediately decrement the backoff counter without additional sensing. Here, the pre-specified time may be any one of a PCF Interframe Space (PIFS), a DIFS, a Short Interframe Space (SIFS), and an Arbitration Interframe Space (AIFS).

[0138] In the embodiment of FIG. 12, a non-STR multi-link device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). When the second station (STA2) transmits on the second link (Link2) while the first station (STA1) receives, intra-device interference occurs. As described above, while the first station (STA1) operating on the first link (Link1) receives, the second station (STA2) is prohibited from accessing the channel on the second link (Link2). After the first station (STA1) completes reception on the first link (Link1), the channel access prohibition is lifted. Immediately after the channel access prohibition is lifted, the second station (STA2) can decrement its backoff counter value by 1, from 3 to 2, without additional sensing.

[0139] For convenience of illustration, in Fig. 12, Rx and Tx are represented by a single block (Tx solid line, Rx dotted line), and this single block may be understood to represent an operation including Tx / Ack reception and Rx / Ack transmission even if a separate Ack block is not shown. This may be equally applied to the drawings described later.

[0140] If a station determines that it is not the intended recipient of a PPDU it receives, it may discontinue receiving the PPDU. In such cases, the channel access unblocking operation of the multilink device becomes an issue. In this specification, the intended recipient is used synonymously with the destination station.

[0141] FIG. 13 shows an operation of canceling channel access prohibition when it is confirmed that the intended recipient of a PPDU received by a station in a non-STR multilink device is not a station according to an embodiment of the present invention.

[0142] If the station determines that it is not the intended recipient of the received PPDU, it can lift the channel access prohibition. The station can determine whether it is the intended recipient of the PPDU based on information indicating the recipient address in the signaling field of the PPDU. In this case, the information indicating the recipient address in the signaling field of the PPDU may be the value of the STA-ID field in the EHT-SIG field. Specifically, the station can determine whether the STA-ID field in the EHT-SIG field indicates the station. The station can also determine whether it is the intended recipient of the PPDU based on the value of the RA field in the MAC frame included in the PPDU. Specifically, the station can determine whether the RA field in the MAC frame included in the PPDU indicates the station. In FIG. 13, the non-STR multi-link device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The first station (STA1) receives a PPDU. The first station (STA1) determines that it is not the intended recipient of the received PPDU and stops receiving the PPDU. At this time, the first station (STA1) can lift the channel access prohibition for the second station (STA2). Even if the channel access prohibition for the second station (STA2) is lifted, the channel access of the second station (STA2) may be delayed depending on the NAV set for the second station (STA2).

[0143] As shown in Figure 13, even if channel access prohibition is lifted, stations included in a non-STR multilink device often do not have a channel access opportunity compared to stations not included in the multilink device or stations included in the STR multilink device. Therefore, a method for compensating for channel access opportunities for stations included in a non-STR multilink device is needed to ensure fair competition with other stations. For example, immediately after channel access prohibition is lifted, a station whose channel access prohibition has been lifted may be allowed to decrement its backoff counter by more than 2. This will be described with reference to Figure 14.

[0144] FIG. 14 shows a station according to an embodiment of the present invention accessing a channel after channel access prohibition is lifted.

[0145] A station whose channel access prohibition has been lifted can decrement its backoff counter by 2 or more immediately after the channel access prohibition is lifted. This is to ensure fairness in channel access opportunities with other stations, since other stations have performed backoff procedures while the station's channel access was prohibited.

[0146] In yet another specific embodiment, a station whose channel access is prohibited can perform a channel access procedure to decrement the CCA (CSMA) and backoff counter while its channel access is prohibited. In FIG. 14, a non-STR multi-link device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). In FIG. 14, the second station (STA2) is prohibited from channel access while the first station (STA1) is receiving. In FIG. 14(a), while the second station (STA2) is prohibited from channel access, the second station (STA2) can perform a channel access procedure to decrement the CCA (CSMA) and backoff counter. In FIG. 14(a), while the second station (STA2) is prohibited from channel access, the second station (STA2) decrements its backoff counter because the channel of the second link (Link2) is idle.

[0147] In addition, a station whose channel access is prohibited can delay transmission without starting transmission even if its backoff counter reaches 0 while channel access is prohibited. In this case, the station can maintain the backoff counter value at 0. Furthermore, even if the station delays transmission, the station can maintain the CW value as it is. This is different from the station doubling the CW value because the channel it accesses is busy. This is because the reason for delaying transmission is not because the channel is determined to be busy. In Figure 14(b), while channel access of the second station (STA2) is prohibited, the second station (STA2) can perform a channel access procedure to decrement the CCA (CSMA) and backoff counter. In Figure 14(b), while channel access of the second station (STA2) is prohibited, the channel of the second link (Link2) is idle, so the second station (STA2) decrements the backoff counter. While the second station (STA2) is prohibited from accessing the channel, the backoff counter of the second station (STA2) reaches 0. The second station (STA2) delays transmission and resumes transmission after the channel access prohibition is lifted.

[0148] As described above, the channel access prohibition can include prohibiting a second station from transmitting when a first station in a non-STR multilink device is transmitting, and can also include prohibiting a second station from transmitting when a first station in a non-STR multilink device is receiving.

[0149] In the embodiment illustrated in Figure 14(b), if multiple stations are prohibited from channel access, there is a high possibility that the channel access prohibitions of multiple stations will be lifted simultaneously, causing multiple stations to attempt transmission simultaneously. Therefore, a method is needed to reduce the probability of transmission collisions. This will be explained in Figure 15.

[0150] FIG. 15 shows an operation of a station according to an embodiment of the present invention to transmit after channel access prohibition is lifted.

[0151] As described above, among multiple links operated by a non-STR multilink device, transmission may be performed on a first link and transmission may be prohibited on a second link. When the transmission on the first link is completed, transmission on the second link may begin by exchanging RTS / CTS frames. Therefore, when transmission is performed on a first link among multiple links operated by a non-STR multilink device, the non-STR multilink device may begin exchanging RTS / CTS frames on the second link. After the channel access prohibition of a station whose transmission has been delayed due to channel access prohibition is lifted, the station may begin exchanging RTS / CTS (request to send / clear to send) frames before starting the delayed transmission. At this time, if the station is unable to receive a CTS frame, it may be unable to start the delayed transmission. In the embodiment of FIG. 15(a), a station whose transmission has been delayed due to channel access prohibition transmits an RTS frame before starting the delayed transmission. The station begins the delayed transmission after receiving a CTS frame in response to the RTS frame.

[0152] In yet another specific embodiment, after a station whose transmission was delayed due to channel access prohibition is released, the station can transmit a frame including only a portion of the delayed transmission. In this case, after the station receives a response, e.g., an ACK, to the frame including only a portion of the delayed transmission, the station can transmit the remaining portion of the delayed transmission. If the station does not receive a response to the frame including only a portion of the delayed transmission, the station may not transmit the remaining portion of the delayed transmission. In this manner, the station initiates an RTS / CTS exchange or transmits only a portion of the delayed transmission after channel access prohibition is released because the collision probability of transmission after channel access prohibition is higher than that of general transmission. Therefore, the above-described embodiment may be mandatory for transmissions performed after channel access prohibition is released. In existing WLAN operations, the RTS / CTS frame is used to solve the hidden node problem and can be used based on the size of the transmission data. In the above-described embodiment, the RTS / CTS frame is used to prevent transmission collisions with stations attempting delayed transmissions to protect the transmission or reception of non-STR multilink devices.

[0153] As described above, when one station in a non-STR multilink device receives, transmissions by other stations in the non-STR multilink device may be restricted. Furthermore, when one station in a non-STR multilink device transmits, other stations in the non-STR multilink device may have difficulty accurately sensing the channel status of the link on which the station operates. Specifically, when a first station in a non-STR multilink device transmits, a second station in the non-STR multilink device may always determine that the channel status of the link on which the second station operates is busy. Therefore, even when the channel of the link on which the second station operates is idle, the second station may determine that the channel is busy due to intra-device interference. In this way, when a station that cannot determine the channel status due to intra-device interference or when one station in the non-STR multilink device is continuing to transmit is said to be in a blind state to other stations in the non-STR multilink device. Due to the above-described situation, a station in a blind state may have difficulty performing a backoff procedure and attempting transmission. In addition, due to the above-mentioned circumstances, it may be difficult for blind stations to start receiving or successfully decode the PPDU. Therefore, a transmission method that takes blind stations into consideration is required. This will be explained in FIG. 16.

[0154] FIG. 16 illustrates transmissions based on the state of stations in a non-STR multilink system according to an embodiment of the present invention.

[0155] A station attempting to transmit to a station in a non-STR multilink device can determine whether to transmit based on whether the station in the non-STR multilink device is in a blind state. In this case, the station attempting to transmit to a station in a non-STR multilink device may be a station included in the STR multilink device. Alternatively, the station attempting to transmit to a station in a non-STR multilink device may be an AP included in the AP multilink device, and the non-STR multilink device may be a non-AP multilink device. A station attempting to transmit to a station in a non-STR multilink device can determine whether the station in the non-STR multilink device is in a blind state. The station attempting to transmit can determine whether other stations in the multilink device in which the station is included are transmitting to the non-STR multilink device. If other stations in the multilink device in which the station is included are receiving from the non-STR multilink device, the station can determine that the station in the non-STR multilink device receiving the station's transmission is in a blind state. In the embodiment of FIG. 16, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The second station (STA2) is transmitting to the second AP (AP2). Therefore, the second AP (AP2) can inform the first AP (AP1) that it is receiving from the second station (STA2). Specifically, the second AP (AP2) can inform the first AP (AP1) that the second station (STA2) is the subject of transmission to the second AP (AP2). In yet another specific embodiment, the second AP (AP2) can inform the first AP (AP1) that the second station (STA2) is currently transmitting.At this time, the first AP (AP1) can determine based on the notification that the first station (STA1) is in a blind state.

[0156] A station does not need to transmit to a station in a blind state because, even if a station transmits to a station in a blind state, there is a high possibility that the station in the blind state will not be able to acknowledge reception or will not be able to decode the PPDU. In this case, the station can cancel transmission to the station in the blind state and transmit to another station.

[0157] When an STR multilink device transmits to a non-STR multilink device, the STR multilink device can transmit to the non-STR multilink device over multiple links. Specifically, when the STR multilink device transmits to the non-STR multilink device over a first link, the STR multilink device can begin transmitting to the non-STR multilink device over a second link. In this case, the STR multilink device can determine the length of the transmission over the second link based on the transmission to the non-STR multilink device. Specifically, the STR multilink device can determine the length of the transmission over the second link to the non-STR multilink device based on the length of the transmission over the first link to the non-STR multilink device. In a specific embodiment, the STR multilink device can simultaneously complete transmission over the first and second links. This is to prevent transmission to one of the stations in the non-STR multilink device from completing first, and to prevent transmission to another station in the non-STR multilink device from occurring while one of the stations in the non-STR multilink device is transmitting a response to the transmission, e.g., an ACK. The above-described embodiment allows multiple stations in the non-STR multilink device to simultaneously transmit responses to transmissions to multiple stations.

[0158] An STR multilink device cannot determine the status of stations included in non-STR multilink devices in real time. Therefore, even if an STR multilink device operates according to the embodiment described in FIG. 16, interference or transmission collisions may occur between links on which the non-STR multilink device operates. For example, in the embodiment of FIG. 16, the first AP (AP1) may begin transmitting to the first station (STA1) before recognizing that the second station (STA2) is transmitting to the second AP (AP2). In this way, the probability of inter-link interference or collisions may be greater than the probability of intra-link interference or transmission collisions. This is described in more detail in FIG. 17.

[0159] FIG. 17 shows a situation in which interference or collision between links may occur.

[0160] When a second station in a non-STR station multilink device starts transmitting to a second AP in the STR AP multilink device at the same time as a first AP in the STR AP multilink device starts transmitting to a first station in the non-STR station multilink device, a transmission collision between the links can occur. This is shown in Figure 17(a). As mentioned above, this can occur because the STR multilink device cannot determine the status of the stations included in the non-STR station multilink device in real time.

[0161] Furthermore, even if the transmission of the second station of the non-STR station multilink device to the second AP of the STR AP multilink device begins before the transmission of the first AP of the STR AP multilink device to the first station of the non-STR station multilink device, a transmission collision may occur between the links. This is shown in FIG. 17(b). This is because it may take time for the second AP (AP2) to inform the first AP (AP1) that the second station (STA2) is transmitting. As such, since a transmission collision may occur even between stations that begin transmitting at different times, the probability of inter-device interference or transmission collision may be greater than the probability of intra-link interference or transmission collision. Furthermore, the longer the time it takes for the AP of the STR multilink device to identify the sender of the PPDU it receives, the greater the probability of inter-link interference or transmission collision. Therefore, a method to resolve this issue is needed. When one station of the STR multilink device is receiving, other stations of the STR multilink device may not be allowed to access the channel. However, if channel access is prohibited in this way, the purpose of implementing the STR function may be lost. Therefore, a method of operation that does not inhibit channel access for STR multilink devices is required, which is illustrated in FIG.

[0162] FIG. 18 illustrates an operation in which an STR multilink device stops transmission to a non-STR multilink device according to one embodiment of the present invention.

[0163] If a station in an STR multilink device determines that a station in the non-STR multilink device is in a blind state while transmitting to a station in a non-STR multilink device, the STR multilink device can suspend transmission to the station in the blind state. Specifically, the STR multilink device can determine whether a station in the non-STR multilink device is in a blind state based on a value indicated as an STA(AID)-ID in the signaling field of a received PPDU or a TA (transmitting address) field of a MAC frame included in the received PPDU. In this case, the STA-ID may be a value indicating the station transmitting the UL PPDU in an UL PPDU. In a specific embodiment, the STR multilink device can determine that a second station included in the non-STR multilink device is in a blind state if a value indicated as an STA(AID)-ID in the signaling field of a received PPDU indicates a first station included in the non-STR multilink device. In addition, if the TA field of the MAC frame included in the received PPDU indicates a first station included in a non-STR multilink device, the STR multilink device can determine that a second station included in the non-STR multilink device is in a blind state. First, the operation of the station after transmission cancellation will be described.

[0164] If a TXOP set for a station in a non-STR multilink device remains, the station that canceled transmission to the station in the non-STR multilink device can attempt transmission to stations other than the station in the non-STR multilink device. In this case, the station that canceled transmission to the station in the non-STR multilink device can transmit to stations other than the station in the non-STR multilink device without a separate backoff procedure. In a specific embodiment, if the channel is detected as idle for a pre-designated time period without a separate backoff procedure after canceling transmission to the station in the non-STR multilink device, the station that canceled transmission to the station in the non-STR multilink device can transmit to stations other than the station in the non-STR multilink device. In this case, the pre-designated time period may be any one of SIFS, PDIF, and DIFS.

[0165] When a station that has canceled a transmission to a station in a non-STR multilink device transmits to a station other than the station in the non-STR multilink device, the station that canceled the transmission to the station in the non-STR multilink device can transmit traffic with the same priority as the traffic of the canceled transmission or traffic with a higher priority. This is because transmitting traffic with a lower priority than the priority of the traffic used when accessing the channel for the canceled transmission would not be fair. In the above-mentioned embodiment, the station in the STR multilink device may be an AP.

[0166] A station that cancels transmission to a station in a non-STR multilink device can reset the TXOP it set. Specifically, a station that cancels transmission to a station in a non-STR multilink device can send a CF-End frame after canceling transmission, allowing other stations operating on the link scheduled for transmission to use the link.

[0167] In FIG. 18, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The second station (STA2) is transmitting to the second AP (AP2). While transmitting to the first station (STA1), the first AP (AP1) determines that the first station (STA1) is in a blind state. Therefore, the first AP (AP1) suspends transmission to the first station (STA1). In FIG. 18(a), after suspending transmission to the first station (STA1), the first AP (AP1) transmits to stations other than the first station (STA1), as in the previously described embodiment. In FIG. 18(b), after suspending transmission to the first station (STA1), the first AP (AP1) transmits a CF-END frame as in the embodiment described below.

[0168] When a station suspends transmission, it may not transmit the next fragment after transmitting the fragment that was in transmission. In yet another specific embodiment, the station may immediately stop transmitting the packet that was in transmission.

[0169] In the above-described embodiment, when the STR multilink device suspends transmission to a station of a non-STR multilink device in a blind state and transmits to a station other than the station of the non-STR multilink device in a blind state, it is necessary to notify the other station that transmission to the other station is possible for stable reception. A method for this will be described. For convenience of explanation, the other station other than the station of the non-STR multilink device in a blind state will be referred to as the other station.

[0170] A station in an STR multilink device can insert the address of another station into a MAC frame. Specifically, the station in the STR multilink device can insert the address of the intended recipient of the MAC frame into the RA (receiving address) of the MAC frame and the address of the other station into a separate field. In yet another specific embodiment, the station in the device can insert the address of the other station into an EHT-SIG. Specifically, the station in the STR multilink device can insert the address of the intended recipient of the PPDU and the address of the other station into the User field of the signaling field of the PPDU. In this case, the address of the other station can be inserted after the address of the intended recipient of the PPDU in the User field of the signaling field of the PPDU.

[0171] In yet another specific embodiment, a station may monitor for reception of a PPDU for a predetermined time even after determining that the station is not the intended recipient of the received PPDU. Specifically, the station may monitor for continued reception of a PPDU for a predetermined time even after determining that the station is not the intended recipient of the received PPDU. This allows the station to determine whether PPDU transmission should be stopped and transmission to the station should begin. In this embodiment, if it is determined that PPDU transmission will continue for the predetermined time, the station may enter a doze state. If it is determined that PPDU transmission will not continue for the predetermined time, the station may remain in a wake-up state. At this time, if a new PPDU is received by the station, the station may decode the PPDU.

[0172] In yet another specific embodiment, a station transmitting a PPDU may insert information into the PPDU signaling that the transmission of the PPDU may be interrupted. The information signaling that the transmission of the PPDU may be interrupted may be a 1-bit subfield. For example, if the value of the subfield signaling that the transmission of the PPDU may be interrupted is 1, a station receiving the PPDU may determine that the transmission of the PPDU may be interrupted before the time indicated by the Length field of the signaling field of the PPDU and the Duration field of the MAC frame. If the station determines that the transmission of the PPDU may be interrupted before the time indicated by the Length field of the signaling field of the PPDU and the Duration field of the MAC frame, the station may postpone entering a power-saving state. Alternatively, a station transmitting a PPDU may insert information signaling that the transmission may be interrupted into a reserved field of the PPDU.

[0173] In this way, unnecessary channel occupation due to transmission cancellation or transmission interruption can be prevented.

[0174] When transmission is interrupted or postponed due to a transmission collision between links, the CW value used for channel access may be doubled, as in the case of a general transmission failure. When transmission is interrupted or postponed due to a transmission collision between links, unlike the case of a general channel access failure or transmission failure, the CW value used for channel access does not need to be doubled. That is, the station can maintain the CW value used for channel access as it is. Doubling the CW value increases the range of possible backoff counter values ​​and reduces the probability of transmission collision. This need can be reduced if the station can clearly recognize transmission collision between links. Also, when transmission is interrupted or postponed due to a transmission collision between links, doubling the CW value by the station may delay the transmission. However, when inter-link transmission collision and intra-link collision occur simultaneously, the station needs to double the CW value. This is described in FIG. 19.

[0175] FIG. 19 shows how the STR multilink device processes the value of CW when it recognizes a transmission collision between links according to an embodiment of the present invention.

[0176] When a station cancels a transmission due to a transmission performed in a non-STR multilink device, as in the above-described embodiment, the station can sense the channel state after canceling the transmission. If the channel is detected as not idle, the station can double the CW value. In this case, the doubling can be performed according to the embodiment described in FIG. 6. Alternatively, if the channel is detected as idle, the station can maintain the CW value. This embodiment is used to treat the channel as idle differently from a successful transmission because the probability of a transmission collision within the link is low even when the channel is detected as idle. In yet another specific embodiment, if the channel is detected as idle, the station can set the CW value to the minimum CW value (CW_min) of the traffic. This embodiment is used to treat the channel as idle the same as a successful transmission because the probability of a transmission collision within the link is low when the channel is detected as idle. The above-described embodiment can be applied to the CW of the AC of the traffic included in the canceled transmission.

[0177] In addition, when a station cancels transmission according to the above-described embodiment, the station may not increment the Retry Counter, which may include at least one of a long retry counter and a short retry counter.

[0178] In the above embodiments, canceling a transmission may include at least one of pausing the transmission and / or delaying the transmission before commencing the transmission.

[0179] If a station sends a CTS-to-Self frame before attempting to transmit and then cancels transmission, the station does not need to initiate an RTS / CTS frame exchange before attempting transmission after canceling transmission because the NAV has already been set by the CTS-to-Self frame. Also, if a station cancels transmission and still has a TXOP when it attempts to transmit again, the station can attempt transmission without a backoff procedure.

[0180] In FIG. 19, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The second station (STA2) is transmitting to the second AP (AP2). While transmitting to the first station (STA1), the first AP (AP1) determines that the first station (STA1) is in a blind state. Therefore, the first AP (AP1) suspends transmission to the first station (STA1). In FIG. 19(a), the first AP (AP1) determines that the channel for the first link (Link1) is idle. At this time, there are no remaining TXOPs, so the first AP (AP1) accesses the channel using the backoff procedure. In Figure 19(b), the first AP (AP1) determines that the channel of the first link (Link1) is not idle. At this time, since there is a TXOP remaining, the first AP (AP1) attempts to transmit without a backoff procedure.

[0181] In the above-described embodiment, if the channel is detected as idle for a pre-specified time interval without a separate backoff procedure after canceling a transmission to a station in a non-STR multilink device, the station that canceled the transmission to the station in the non-STR multilink device can transmit to a station other than the station in the non-STR multilink device. In this case, the duration of the pre-specified time interval can be an issue. A station that receives a PPDU of a canceled transmission may fail to decode the PPDU. In this case, if the channel is detected as idle for an extended interframe space (EIFS), the station that fails to decode the PPDU can initiate a backoff procedure. Therefore, an issue arises as to whether the pre-specified time interval should be set to be longer than or equal to the EIFS. This will be described with reference to FIG. 20.

[0182] FIG. 20 illustrates an operation in which an STR multilink device performs channel access again after halting transmission to a non-STR multilink device according to an embodiment of the present invention.

[0183] As shown in Figure 20(a), the pre-specified time interval may be DIFS. This takes into consideration that a station in an STR multilink device acquires a channel access opportunity through a contention procedure and loses the acquired channel access opportunity due to transmission collision between links. In other words, since a station in an STR multilink device acquires a channel access opportunity through a contention procedure, it is given priority over other stations attempting channel access. When EDCA is applied, DIFS may be replaced with AIFS [AC].

[0184] In yet another specific embodiment, as shown in Figure 20(b), the pre-specified time interval may be EIFS, which is in consideration of the fact that the STR multilink device can assume that it has already used up its transmission opportunities and of fairness with other stations.

[0185] In another specific embodiment, as shown in FIG. 20(c), when the signaling field of the PPDU signals that transmission may be interrupted, the pre-specified time interval may be DIFS. Also, when a station receiving a PPDU detects that transmission of the PPDU has been interrupted, the station can detect whether the channel is idle using DIFS instead of EIFS. In this case, if the channel is detected as idle using DIFS, the station can initiate a backoff procedure. This embodiment can improve the performance of the entire network and ensure fairness between stations. When EDCA is applied, DIFS can be replaced with AIFS [AC].

[0186] As described above, the STR multilink device can recognize that a transmission collision between links may occur. Specifically, when a first station in the STR multilink device completes a backoff procedure, a second station in the STR multilink device may be receiving a PPDU. If the second station fails to complete decoding of the signaling field of the PPDU, the first station may not recognize that a transmission collision between links has occurred, but may determine that it is possible. In this case, the first station may insert information indicating that transmission may be interrupted into the PPDU to be transmitted, as described above. Furthermore, the NSTR multilink device may transmit a CTS-to-Self frame before transmitting to a non-STR multilink device for stable and efficient transmission. This will be described with reference to FIG. 21.

[0187] FIG. 21 illustrates an operation in which an STR multilink device transmits a CTS-to-Self frame before transmitting to a non-STR multilink device according to an embodiment of the present invention.

[0188] A station in an STR multilink device can transmit a CTS-to-Self frame before transmitting to a non-STR multilink device. Specifically, if a second station in an STR multilink device attempts to transmit to a non-STR multilink device while a first station in the STR multilink device is receiving, the second station in the STR multilink device can transmit a CTS-to-Self frame before transmitting to the non-STR multilink device. This allows the second station to reserve a TXOP for transmission to the non-STR multilink device. Furthermore, before transmitting to the non-STR multilink device, the second station can determine whether a transmission for the first station is being transmitted from the non-STR multilink device. The second station can determine the destination station of a transmission based on whether a transmission for the first station is being transmitted from the non-STR multilink device. Specifically, if a transmission for the first station is not being transmitted from the non-STR multilink device, the second station can transmit to the non-STR multilink device. When a transmission for a first station is being sent from the non-STR multilink device, a second station may transmit to a station not included in the non-STR multilink device. For example, if the first station plans to transmit a SU-PPDU for a station in the non-STR multilink device, a MU-PPDU containing data for a station in the non-STR multilink device, or a PPDU containing a trigger frame that triggers a transmission for a station in the non-STR multilink device, the first station may cancel the planned transmission. In this case, the first station may attempt to transmit a SU-PPDU for a station other than a station in the non-STR multilink device, a MU-PPDU containing no data for a station in the non-STR multilink device, or a PPDU containing a trigger frame that does not trigger a transmission for a station in the non-STR multilink device.In this case, the first station can begin transmission after a time greater than SIFS from the time it transmits the CTS-to-Self frame. Specifically, the first station can begin transmission PIFS after transmitting the CTS-to-Self frame. The station that transmitted the CTS-to-Self frame must begin transmission SIFS after transmitting the CTS-to-Self frame. As in the above-described embodiment, when canceling a planned transmission and attempting a new transmission, processing time is required from the STR multilink device, such as generating a new MPDU to be transmitted. For this reason, exceptions to the regulations regarding the time interval between a CTS-to-Self frame and a transmission may be applied. In such an embodiment, the second station cannot transmit beyond the TXOP obtained by the CTS-to-Self frame.

[0189] In Figure 21, the STR multi-link device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The second AP (AP2) receives and schedules a transmission to a station in the non-STR multi-link device, so the first AP (AP1) transmits a CTS-to-Self frame before the scheduled transmission. As described above, the first AP (AP1) determines the destination station for transmission based on the determination of the station that transmitted the PPDU received by the second AP (AP2). In addition, the first AP (AP1) transmits after SIFS or PIFS from the time of transmitting the CTS-to-Self frame.

[0190] The second station can initiate the RTS / CTS frame exchange procedure by sending an RTS frame instead of a CTS-to-Self frame. This allows the second station to achieve a similar effect to sending a CTS-to-Self frame. In the case of an RTS / CTS frame exchange, the second station can acquire the TXOP only if the destination station is not blinded.

[0191] FIG. 22 illustrates a case in which multiple APs included in an STR multilink device transmit to multiple stations included in one non-STR multilink device according to an embodiment of the present invention.

[0192] Multiple stations included in one non-STR multilink device can receive simultaneously. This is because simultaneous reception by multiple stations causes relatively little interference. Figure 22 shows multiple stations included in one non-STR multilink device receiving simultaneously. In this case, to ensure stable operation of the non-STR multilink device, multiple APs included in the STR multilink device can perform multiple transmissions to multiple stations included in one non-STR multilink device, with the end of transmissions synchronized. This is described in Figure 23.

[0193] FIG. 23 shows an embodiment of the present invention in which multiple APs included in an STR multilink device perform multiple transmissions with synchronized end of transmission to multiple stations included in a single non-STR multilink device.

[0194] In non-STR links, when a multilink device transmits on one link, the multilink device can simplify the channel access procedure for transmissions on other links. Specifically, when a first station in the multilink device completes a backoff channel access procedure on the first link, if the channel is idle for a pre-specified time period in the link of a second station in the STR multilink device, the second station in the STR multilink device can begin transmission on the second link.

[0195] In a specific embodiment, when one station in an STR multilink device transmits to one station in a non-STR multilink device, the channel access procedure for other stations in the STR multilink device can be simplified. Specifically, when a first station in the STR multilink device completes a backoff channel access procedure for transmission to the first station in the non-STR multilink device, if the channel is idle for a pre-specified time period within the link of the second station in the STR multilink device, the second station in the STR multilink device can begin transmission to the second station in the non-STR multilink device. In this case, the pre-specified time period may be a PIFS. This operation may be applied when the first and second stations in the STR multilink device transmit to stations included in a single non-STR multilink device. In this embodiment, the first and second stations can begin transmission within a pre-specified time period. The pre-specified time period may be a slot time.

[0196] Furthermore, when a first station and a second station in an STR multilink device transmit to a station included in a single non-STR multilink device, the end of transmission of the first station and the second station may be synchronized. In this case, the synchronization of the end of transmission of the first station and the second station may mean that the transmission of the first station and the transmission of the second station end with a difference within a first pre-specified time interval. The first pre-specified time interval may mean within a slot boundary or a symbol boundary.

[0197] Multiple stations in a non-STR multilink device that receive synchronized transmission ends can simultaneously transmit subsequent transmissions, e.g., responses. In this case, the responses can include an ACK. In conventional WLANs, subsequent transmissions are transmitted SIFS after reception. However, transmitting subsequent transmissions with a slight time difference between multiple transmissions that ended with a slight time difference can be more complex to implement than transmitting subsequent transmissions simultaneously. Therefore, as described above, multiple stations in a non-STR multilink device that receive synchronized transmission ends can simultaneously transmit subsequent transmissions. In this case, the interval between subsequent transmissions following at least one of the multiple transmissions whose transmission ends are synchronized may be the sum of SIFS and a time within a pre-specified time interval. Specifically, the transmission following the first transmission among the multiple transmissions whose transmission ends are synchronized may be transmitted at an interval that is the sum of SIFS and a time within a pre-specified time interval. In this case, the pre-specified time interval may be one of a slot time or a symbol length. Furthermore, the difference within a predetermined time interval may be the difference between the end of the last transmission among a plurality of transmissions whose end is synchronized and the first transmission among a plurality of transmissions whose end is synchronized.

[0198] In yet another specific embodiment, when multiple transmissions end with a time difference within a first pre-specified time interval, multiple stations receiving the transmission can transmit synchronized subsequent transmissions. The multiple subsequent transmissions with synchronized transmission ends can represent multiple subsequent transmissions transmitted with a time difference within a second pre-specified time interval. The difference within the second pre-specified time interval can be the difference between the end of the last completed transmission among the synchronized transmissions and the earliest completed transmission among the synchronized transmission ends. In this case, the second pre-specified time interval can be smaller than the first pre-specified time interval. A PPDU with synchronized transmission ends can be referred to as a sync PPDU.

[0199] In Figure 23, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The first AP (AP1) and the second AP (AP2) synchronize the end of transmissions to the first station (STA1) and the second station (STA2), respectively. That is, after the first station (STA1) finishes transmission, the second station (STA2) finishes transmission within a time period pre-specified by the first station (STA1). The first station (STA1) and the second station (STA2) simultaneously send ACKs. At this time, the first station (STA1) transmits an ACK after the difference between the end of transmission to the first station (STA1) (SIFS) and the end of transmission to the first station (STA1) and the end of transmission to the second station (STA2).

[0200] This embodiment may be applied to transmissions for which the ACK policy is not set to No ACK. Specifically, it may also be applied when the ACK policy is not immediate. In a specific embodiment, when multiple stations in a multilink device receive transmissions whose end of transmission is synchronized, the multiple stations in the multilink device can simultaneously receive ACK requests and simultaneously transmit ACKs in response to the ACK requests. Multiple stations in a multilink device that receive transmissions for which the ACK policy is set to a value other than No ACK within a predetermined time period can simultaneously begin ACKs.

[0201] When non-STR multilink devices are present, they must be taken into consideration when transmitting RTS / CTS frames and CTS-to-Self frames to set TXOPs, as will be explained in Figures 24 to 29.

[0202] FIG. 24 shows multilink devices exchanging RTS / CTS frames according to an embodiment of the present invention.

[0203] Even when a non-STR multilink device exists, the RTS / CTS frame exchange procedure can follow the procedure defined in the existing WLAN. The RTS / CTS frame can be used to set the NAV of a station operating on another link. Specifically, a station that receives an RTS / CTS frame can transmit it to another station operating on a link other than the one it operates on and included in the multilink device in which it is included.

[0204] However, as in the previous embodiment, channel access or transmission may be restricted when a non-STR multilink device is present, which may prevent RTS / CTS transmission as shown in Figure 24. That is, a station planning to transmit to a first station in a non-STR multilink device may not attempt to exchange RTS / CTS frames if a second station in the non-STR multilink device is receiving.

[0205] In FIG. 24, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). When the first AP (AP1) transmits an RTS frame to the first station (STA1), channel access for the second station (STA2) is prohibited. The second AP (AP2) determines that channel access for the second station (STA2) is prohibited. Therefore, the second AP (AP2) does not attempt to exchange RTS / CTS frames with the second station (STA2). In this embodiment, a hidden node problem may occur, as will be described in FIG. 25.

[0206] FIG. 25 illustrates a hidden node problem that occurs in the RTS / CTS frame exchange procedure according to the embodiment described in FIG.

[0207] As described above, a station transmitting to a station in a non-STR multilink device may transmit without being able to exchange CTS / RTS. In this case, because a TXOP is not set for the other station, the other station may attempt to transmit, resulting in the station in the non-STR multilink device failing to transmit or receive. In the example of FIG. 25, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). Due to the first AP (AP1) transmitting to the first station (STA1), the second AP (AP2) was unable to send an RTS frame before transmitting. Therefore, a TXOP for the second AP (AP2) transmission is not set for the station operating on the second link (Link2). Therefore, when the second AP (AP2) transmits to the second station (STA2), a station in another BSS (OBSS STA) transmits on the second link (Link 2). As a result, the second station (STA2) fails to receive the transmission from the second AP (AP2). To solve this hidden node problem, the following embodiment may be applied.

[0208] In a specific embodiment, if any station in a non-STR multilink device is receiving, the station may not be allowed to transmit to any station in the non-STR multilink device. In yet another specific embodiment, if a station transmits to a first station in a non-STR multilink device and a second station in the non-STR multilink device is receiving, the station may transmit simultaneously with its transmission to the second station. If a station transmits to a first station in a non-STR multilink device and a second station in the non-STR multilink device is receiving, the station may synchronize the end of its transmission to the first station with the end of its transmission to the second station. Specifically, if a station transmits to a first station in a non-STR multilink device and a second station in the non-STR multilink device is receiving, the station may end its transmission to the first station simultaneously with its transmission to the second station. In such an embodiment, transmission to the second station may be performed by another station in the multilink device, including the station.

[0209] FIG. 26 shows multilink devices exchanging RTS / CTS frames according to an embodiment of the present invention.

[0210] In yet another embodiment of the present invention, if a first station in a multilink device continues transmitting to a third station in a non-STR multilink device, and a second station in the multilink device attempts to transmit an RTS frame to a fourth station in the non-STR multilink device, the first station may end its transmission to the third station before the fourth station attempts to transmit the RTS frame. This allows the fourth station to transmit a CTS frame to the second station. This allows TXOP tentative setup for frame exchange between the second and fourth stations. However, it may be difficult for the first station to end its transmission before the fourth station attempts to transmit the RTS frame.

[0211] In yet another embodiment of the present invention, if a second station in the multilink device attempts to transmit an RTS frame to a fourth station in the non-STR multilink device while a first station in the multilink device continues transmitting to a third station in the non-STR multilink device, the second station can transmit the RTS frame to the fourth station to coincide with the end of the first station's transmission to the third station. To do this, the second station can insert padding into the RTS frame. In this case, the RTS frame may have an RTS frame format that allows for flexible adjustment of the transmission length. For convenience of explanation, this RTS frame format is referred to as an ML (multilink)-RTS frame. The ML-RTS frame may include a pad field for padding. For example, the format of the ML-RTS frame may be the same as the RTS frame format shown in FIG. 26. In addition, the first station can insert padding into the transmission to the third station to coincide with the end of the RTS frame.

[0212] In the embodiment of Figure 26, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on the first link (Link1) and a second station (STA2) operating on the second link (Link2). The second AP (AP2) transmits an ML-RTS frame to the second STA (STA2) in synchronization with the end of the first AP's (AP1) transmission to the first station (STA1). Thereafter, when the first station (STA1) transmits an ACK to the first AP (AP1), the second station (STA2) transmits an ACK to the second AP (AP2). As a result, a TXOP for frame exchange between the second AP (AP2) and the second station (STA2) is established in the station operating on the second link channel.

[0213] In yet another specific embodiment, another frame for setting NAV may be substituted for the RTS / CTS frame. In the above-described embodiment, an ACK request frame may be transmitted instead of the RTS frame. The ACK request frame may include duration information related to the transmission end point. In addition, a frame including an ACK transmitted in response to the ACK request may also include duration information. In this case, the duration information of the frame including the ACK may be set according to the duration information of the ACK request frame.

[0214] Although the above-described embodiment has been described for RTS / CTS frame exchange, it may also be used for control frame exchange other than RTS / CTS frames. In this case, the control frame exchange may include the exchange of PS-Poll frames and response frames to PS-Poll.

[0215] FIG. 27 shows that a multilink device transmits a response to a control frame exceptionally even when channel access is prohibited according to an embodiment of the present invention.

[0216] As described in the above embodiment, when a non-STR multilink device is present, channel access of some stations may be prohibited. Even if channel access of a station is prohibited, the station can still send a response to a control frame. Specifically, even if channel access of a station is prohibited, the station can still send a CTS frame in response to an RTS frame.

[0217] In this way, when a response to a control frame is transmitted as an exception to channel access denial, the following embodiment may be applied: A first station transmits a response to a control frame as an exception to channel access denial. When the first station transmits the response to the control frame, a third station transmits to a second station included in the multilink device including the first station. In this case, the third station can retransmit to the first station. The third station can predict that the transmission to the second station will fail.

[0218] In the example of FIG. 27, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on the first link (Link1) and a second station (STA2) operating on the second link (Link2). The first AP (AP) transmits to the first station (STA1). The second AP (AP2) transmits an RTS frame to the second station (STA2). Because the first station (STA1) receives, channel access for the second station (STA2) is prohibited. However, the second station (STA2) transmits a CTS frame to the second AP (AP2) as an exception to the channel access prohibition. The first AP (AP1) can determine that the first AP's (AP1's) transmission is likely to fail due to the second station's (STA2's) CTS frame transmission. Therefore, the first AP (AP1) retransmits to the first station (STA1). The retransmission method is described in more detail in FIG.

[0219] FIG. 28 shows the retransmission of a transmission to a station of a non-STR multilink device.

[0220] In the retransmission described in FIG. 27, only some of the packets included in the initial transmission may be retransmitted. Specifically, the station performing the retransmission may retransmit only some of the packets included in the initial transmission. The station performing the retransmission may determine some of the packets included in the initial transmission to be retransmitted based on the time interval in which the station performing the retransmission received the CTS frame. Specifically, the station performing the retransmission may determine, among the packets included in the initial transmission, packets transmitted in a time interval including the time interval in which the station performing the retransmission received the CTS frame as the packets to be retransmitted. In this case, the station performing the retransmission may retransmit packets transmitted in a time interval including the time interval in which the station performing the retransmission received the CTS frame based on the propagation delay. In yet another specific embodiment, the station performing the retransmission may retransmit all of the packets included in the initial transmission.

[0221] In addition, a station performing a retransmission can perform the retransmission before receiving an ACK for the transmission. In this case, after performing the retransmission, the station performing the retransmission can receive a Block ACK indicating whether the initial transmission and the retransmission were received. Therefore, the station performing the retransmission can perform the retransmission before a SIFS after the initial transmission. In yet another specific embodiment, a station that fails to receive a control frame transmitted as an exception to channel access prohibition can wait to receive a retransmission without transmitting an ACK.

[0222] 28, the first AP (AP1) retransmits the fourth and fifth packets, taking into account the interval during which the second AP (AP2) receives the CTS frame and the transmission delay. After the retransmission, the first AP (AP1) receives an ACK indicating whether the retransmission was received or not.

[0223] FIG. 29 shows that a control frame is transmitted on a link on which a station that is not prohibited from channel access operates, rather than on a link on which a station that is prohibited from channel access operates, according to an embodiment of the present invention.

[0224] As in the embodiment described in FIG. 26, the end of transmission for multiple stations in a non-STR multilink device may be synchronized. However, this may require adjusting an already generated MPDU or generating an MPDU again, which is difficult to implement. Therefore, the multilink device may transmit a control frame over a link in which a station in which channel access is not prohibited operates, rather than a link in which a station in which channel access is prohibited operates. Specifically, the multilink device may transmit a control frame over a link in which a station in the non-STR multilink device is currently receiving from the multilink device. In this case, the control frame may be an RTS frame.

[0225] In the embodiment of FIG. 29, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The first AP (AP1) transmits to the first station (STA1). Even if the second AP (AP2) successfully completes the backoff procedure, the second AP (AP2) cannot transmit to the second station (STA2) because the first station (STA1) is receiving a transmission from the first AP (AP1). At this time, the second AP (AP2) requests the first AP (AP1) to transmit an RTS frame with the second station (STA2) as the recipient. In this case, the first AP (AP1) may include an RTS frame for which the second station (STA2) is the recipient in the transmission currently being performed by the first AP (AP1). In yet another specific embodiment, after the first AP (AP1) finishes the transmission currently being performed by the first AP (AP1), the first AP (AP1) may transmit an RTS frame for which the second station (STA2) is the recipient via the first link (Link1) SIFS after the transmission. The first station (STA1) receives the RTS frame for which the second station (STA2) is the recipient and transmits the received RTS frame to the second station (STA2). The second station (STA2) performs CCA in the PIFS. If the channel is idle in the PIFS, the second station (STA2) transmits a CTS-to-Self frame. The first AP (AP1) may suspend transmission to the first station (STA1) during a time period in which the second station (STA2) is expected to transmit a response to the RTS frame. Also, while the second station (STA2) is transmitting a response to the RTS frame, the first station (STA1) can transmit an ACK for the received transmission. In yet another specific embodiment, while the second station (STA2) is transmitting a response to the RTS frame, the first station (STA1) can also transmit a response to the RTS frame.29 is provided to facilitate understanding of the explanation, and may also be used to transmit control frames other than RTS frames and CTS-to-Self frames. Also, time intervals other than PIFS may be used.

[0226] FIG. 30 shows a multi-link device sending an ACK according to an embodiment of the present invention.

[0227] A station in a multilink device can request a link for transmitting an ACK to a station in a non-STR multilink device. Specifically, a station in a multilink device can request that an ACK be transmitted over a link other than the link on which the transmission was made. In the example of FIG. 28, a first AP (AP1) in the STR multilink device transmits (Tx(#2)) to a first station (STA1) in a non-STR multilink device. At this time, the first AP (AP1) requests that an ACK for the transmission (Tx(#2)) be transmitted over the second link (Link2). This is because the first AP (AP1)'s transmission (Tx(#2)) to the second station (STA2) from the second AP (AP2) is completed before the first AP (AP1)'s transmission (Tx(#2)) to the second station (STA2) is completed, making it difficult to transmit an ACK for the first AP (AP1)'s transmission (Tx(#2)).

[0228] In addition, for such ACK transmission, the station can set an implicit BAR and ACK policy so as not to send an immediate response to the transmission. In yet another specific embodiment, the station can set the ACK policy for the transmission to BlockAckReq. However, in order to send a Block ACK, a BlockAckReq must be sent, which may result in channel access overhead and transmission delays. Therefore, a new ACK policy for multilink devices is needed.

[0229] A station in a multilink device can transmit both an ACK for a transmission received by the station and an ACK for a transmission received by another station included in the same multilink device. This type of ACK transmission can be called ML (multilink)-ACK. An ACK policy, ML-ACK, can also be configured. In the embodiment of FIG. 30, the first AP (AP1) configures the ACK policy for transmission (Tx(#2)) as ML-ACK. After receiving transmission (Tx(#2)), the first station (STA1) does not transmit an ACK to the first AP (AP1). After completing reception of the transmission from the second AP (AP2), the second station (STA2) transmits to the second AP (AP2) both an ACK for the transmission from the first AP (AP1) and an ACK for the transmission from the second AP (AP2). The non-STR multilink device may include a third station (STA3) in addition to the first station (STA1) and the second station (STA2), and the STR multilink device may include a third AP (AP3) in addition to the first AP (AP1) and the second AP (AP2). In this case, the ACK policy for transmissions from the second AP (AP2) to the second station (STA2) may also be set to ML-ACK. If transmissions from the third AP (AP3) to the third station (STA3) are completed later than transmissions from the second AP (AP2) to the second station (STA3), the third station (STA1) may transmit ACKs for transmissions from the first AP (AP1) to the first station (STA1), ACKs for transmissions from the second AP (AP2) to the second station (STA2), and ACKs for transmissions from the third AP (AP3) to the third station (STA3).

[0230] This embodiment can prevent interference between links that may occur due to ACK transmissions even if transmissions to stations in non-STR multilink devices are not completed simultaneously. In the above-described embodiment, the ACK policy may be set to BlockAck instead of ML-ACK. In yet another specific embodiment, the ACK policy may be set to NoAck instead of ML-ACK.

[0231] As a multilink device transmits traffic, the number of links that acquire transmission opportunities may increase. In this case, the multilink device may transmit traffic that was intended to be transmitted on a link that acquired a transmission opportunity earlier on a link that acquired a transmission opportunity later. In this case, the NAV set on the link where the multilink device acquired a transmission opportunity earlier may be set higher than the NAV required to transmit the traffic. If the NAV set on the link where the multilink device acquired a transmission opportunity earlier is higher than the NAV required to transmit the traffic, the multilink device can reset the NAV by transmitting a CF-END frame after completing transmission on the link that acquired a transmission opportunity earlier.

[0232] The above-mentioned reception of the Sync PPDU and signaling related to the reception of the Sync PPDU will be described with reference to FIGS.

[0233] In order for a first station in a non-STR multilink device to receive the Sync PPDU, it must determine whether a second station in a non-STR relationship with the first station has begun receiving the Sync PPDU. Furthermore, the first station must continuously perform preamble detection (PD). Considering that the first station receiving the Sync PPDU is denied channel access due to the reception activity of another station in the non-STR multilink device, this behavior of the first station may be unreasonable. Therefore, the first station can enter a power-saving state within pre-specified conditions. The Sync PPDU may be transmitted within an existing TXOP. Therefore, the performance gain obtained by receiving the Sync PPDU may be determined by the length of the remaining TXOP. Therefore, the first station can determine whether to give up receiving the Sync PPDU based on the length of the Sync PPDU. If the first station gives up receiving the Sync PPDU, the first station can enter a power-saving state. This power-saving operation can be referred to as inter-link TXOP power save (PS). A station that entered the power saving state in the inter-link TXOP PS can wake up from the power saving state to receive frames periodically transmitted from the AP, such as a beacon frame, a TIM frame, and a DTIM frame. Also, when the TXOP ends, for example, when a CF-END frame is transmitted, a station that entered the power saving state in the inter-link TXOP PS can wake up from the power saving state.

[0234] The above-mentioned TXOP may be changed to a period indicated by the length field of the signaling field of the PPDU and the duration field of the MAC frame. Specifically, in the above-mentioned embodiment, the station can determine the time occupied by the PPDU based on the period indicated by the length field and the duration field of the MAC frame.

[0235] A non-AP multilink device can signal to an AP multilink device information regarding whether it supports receiving a sink PPDU and the conditions for supporting the sink PPDU. Furthermore, an AP multilink device can signal to a non-AP multilink device whether it supports transmitting a sink PPDU. Here, the multilink device can signal whether it supports a sink PPDU for each multilink device. For example, an AP multilink device can signal whether it supports transmitting a sink PPDU for each AP multilink device. In yet another specific embodiment, a multilink device can signal whether it supports a sink PPDU for each station. Specifically, an AP multilink device can signal whether it supports transmitting a sink PPDU for each AP included in the AP multilink device. For example, an AP multilink device including a first AP, a second AP, and a third AP can indicate that the first AP supports transmitting a sink PPDU and that the second and third APs do not support transmitting a sink PPDU.

[0236] If an AP multilink device associated with a non-AP multilink device signals that it does not support sync PPDU transmission, a station in the non-AP multilink device can enter the inter-link PS power-saving state described above while another station in the non-AP multilink device is receiving. This is because the AP multilink device associated with the non-AP multilink device cannot transmit a sync PPDU. In this case, the station in the non-AP multilink device can determine the length of time to maintain the power-saving state based on the length of the PPDU received by the other station in the non-AP multilink device.

[0237] Whether the sync PPDU transmission or reception is supported may be determined based on hardware performance as well as operational policies. Therefore, whether the sync PPDU transmission or reception is supported may be signaled based on information on the operating mode as well as performance information. A method for signaling whether the sync PPDU transmission or reception is supported will be described in detail with reference to FIG. 31.

[0238] FIG. 31 shows an element field indicating information regarding support for receiving or transmitting a sink PPDU according to an embodiment of the present invention.

[0239] As described above, information indicating whether Sync PPDU transmission is supported may be included in an element indicating station capabilities. For ease of explanation, the element indicating station capabilities is called a Capability element. In addition, the field of the Capability element containing information indicating whether Sync PPDU transmission is supported is called a Supporting Sync PPDU Tx subfield. In this case, the Capability element may be a Multi-Link element indicating multi-link related capabilities. In addition, the Capability element may be an EHT Capability element indicating EHT-related capabilities. Figure 31(a) shows an example of a Capability element.

[0240] If the value of the Supporting Sync PPDU Tx subfield is 1, it may indicate that the station or multilink device indicated by the Supporting Sync PPDU Tx subfield supports sync PPDU transmission. If the value of the Supporting Sync PPDU Tx subfield is 0, it may indicate that the station or multilink device indicated by the Supporting Sync PPDU Tx subfield does not support sync PPDU transmission. Also, when a station not included in the multilink device transmits a Capability element, the Supporting Sync PPDU Tx subfield may signal information that is not unrelated to whether sync PPDU transmission is supported or may be used as a reserved field.

[0241] As described above, information indicating whether or not a station supports sync PPDU reception may be included in an element indicating station operation-related information. For ease of explanation, an element indicating station operation-related information is referred to as an Operation element. Furthermore, a field in the Operation element for information indicating whether or not a station supports sync PPDU reception is referred to as a Supporting Sync PPDU Rx Disable subfield. Figure 31(b) shows an example of an Operation element. When the Supporting Sync PPDU Rx Disabled subfield has a value of 1, it may indicate that the station does not want to receive a sync PPDU. Specifically, when the Supporting Sync PPDU Rx Disabled subfield has a value of 1, the Supporting Sync PPDU Rx Disabled subfield may indicate that the station transmitting the Supporting Sync PPDU Rx Disabled subfield does not want to wait for a sync PPDU to be received. In a multilink device that sets the Supporting Sync PPDU Rx Disabled subfield to 1, the second station of the multilink device does not need to perform PD and CCA while the first station of the multilink device is receiving. An AP multilink device connected to a multilink device that transmitted the Supporting Sync PPDU Rx Disabled subfield does not simultaneously transmit PPDUs to multiple stations of the multilink device that transmitted the Supporting Sync PPDU Rx Disabled subfield. The PPDU may be an SU PPDU, Full BW MU PPDU, or OFDMA MU PPDU transmitted in any one of non-HT PPDU, HT PPDU, VHT PPDU, HE PPDU, and EHT PPDU formats. In this case, the AP multilink device must not transmit a response, for example, a frame requesting an immediate response.The frame requesting a response may include at least one of an RTS, a Multi-User RTS (MU-RTS), a trigger frame, and a Block Ack Request (BAR).

[0242] The Operation element may also include information related to the minimum length of a sync PPDU that can be received by the station or multilink device that transmitted the Operation element. In this case, a subfield indicating information related to the minimum length of a sync PPDU is referred to as a Remaining TXOP Threshold subfield. The Remaining TXOP Threshold subfield may indicate time. The Remaining TXOP Threshold subfield may also be indicated in us, ms, or symbol units. A multilink device connected to the multilink device that transmitted the Remaining TXOP Threshold subfield may not be allowed to transmit a sync PPDU that is shorter than the length indicated by the Remaining TXOP Threshold subfield to the multilink device or station that transmitted the Remaining TXOP Threshold subfield.

[0243] Furthermore, if the Remaining TXOP Threshold subfield is set to a pre-specified value, it may indicate that the multilink device or station that transmitted the Remaining TXOP Threshold subfield does not support receiving Sync PPDUs. The pre-specified value may be a value indicating a time greater than the maximum time that the Remaining TXOP Threshold subfield can indicate. In yet another specific embodiment, the pre-specified value may be 0. When such an embodiment is applied, the Sync PPDU Rx Disable subfield may be omitted from the Operation element.

[0244] Also, in the above-mentioned embodiment, it has been described that the Sync PPDU Rx Disable subfield and the Remaining TXOP Threshold subfield can be signaled by the Operation element. The Sync PPDU Rx Disable subfield and the Remaining TXOP Threshold subfield can be signaled by an element other than the Operation element or by signaling information. Figures 32 to 34 describe an embodiment in which the inter-link TXOP power save mode is performed by the signaling described in Figure 31.

[0245] FIG. 32 illustrates an inter-link TXOP power save mode operation in a non-STR multi-link device according to an embodiment of the present invention.

[0246] When a non-STR multilink device signals that it does not support sync PPDU reception, a second station in the non-STR multilink device can enter a power-save state while a first station in the non-STR multilink device is receiving. In this case, the second station can maintain the power-save state until the end of the TXOP indicated in the PPDU received by the first station. As described above, the second station can wake up from the power-save state before the end of the TXOP indicated in the PPDU received by the first station. As described above, the frame periodically transmitted from the AP can include at least one of a beacon frame, a TIM frame, and a DTIM frame.

[0247] The second station may maintain a power-saving state even after the end of the TXOP indicated by the PPDU received by the first station. Specifically, the second station may determine whether to maintain a power-saving state even after the end of the TXOP indicated by the PPDU received by the first station, based on information received from the AP to which the second station is connected. In this case, the information received from the AP to which the second station is connected may be NAV-related information. Also, the information received from the AP to which the second station is connected may be operation information of the AP to which the first station is connected. If the NAV set by the second AP of the AP multilink device currently transmitting to the second station of the non-AP multilink device has not yet expired, the first AP of the AP multilink device may transmit information regarding the expected end of the first AP's transmission or reception and the expected expiration of the NAV to the first station of the non-AP multilink device that signaled that it does not wish to receive a sync PPDU. If the NAV set by the second AP of the AP multilink device currently transmitting to the second station of the non-AP multilink device has not expired, the second AP may transmit or receive a PPDU from any one of the stations.If the NAV set by the second AP of the AP multilink device currently transmitting to the second station of the non-AP multilink device has not expired, the NAV may be set in the second AP by a PPDU not transmitted by the second station.

[0248] In the embodiment of Figure 32, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on the first link (Link1) and a second station (STA2) operating on the second link (Link2). The non-STR non-AP multilink device signals that it does not wish to receive a sync PPDU. The first AP (AP1) transmits to the first station (STA1). At this time, the second station (STA2) maintains a power saving state until the end of the TXOP indicated in the PPDU transmitted by the first AP (AP1) to the first station (STA1).

[0249] FIG. 33 illustrates a non-STR multilink device station entering a power saving state while waiting to receive a sync PPDU according to an embodiment of the present invention.

[0250] A first station in a non-STR multilink device can enter a power-saving state for an inter-link TXOP if the remaining duration of the TXOP indicated in the PPDU being received by the first station in the non-STR multilink device is equal to or shorter than the duration indicated in the Remaining TXOP Threshold subfield transmitted by the non-STR multilink device. Before entering the power-saving state, a second station can receive a sync PPDU transmitted to the second station if the remaining duration of the TXOP indicated in the PPDU being received by the first station is greater than the duration indicated in the Remaining TXOP Threshold subfield transmitted by the non-STR multilink device. To do so, the second station can perform PD to determine whether the intended recipient of the received PPDU is the second station. Specifically, the second station can determine whether the AID indicated in the signaling field of the PPDU or the RA of the MAC frame included in the PPDU indicates the second station.

[0251] In the embodiment of Figure 33, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The non-STR non-AP multilink device signals its desire to receive a sync PPDU. At this time, the non-STR non-AP multilink device also signals "a," the minimum TXOP length required to receive the sync PPDU. The first AP (AP1) transmits to the first station (STA1), and the second station (STA2) waits to receive the sync PPDU. If the TXOP of the PPDU transmitted by the first AP (AP1) to the first station (STA1) is equal to or shorter than "a," the second station (STA2) enters the inter-link TXOP power-save state.

[0252] FIG. 34 illustrates a station in a non-STR multilink device entering a power saving state while waiting to receive a sync PPDU according to yet another embodiment of the present invention.

[0253] If a station in a non-STR multilink device detects a PPDU other than a Sync PPDU from a BSS operated by an AP connected to the station in the non-STR multilink device while waiting to receive a Sync PPDU, the station in the non-STR multilink device can enter the inter-link TXOP power-saving state. In this case, the station can determine that a PPDU that is not the intended recipient of the station is not a Sync PPDU. Also, if a station detects a PPDU other than a Sync PPDU from a BSS operated by an AP connected to the station in the non-STR multilink device even if the minimum TXOP signaled by the station remains, the station in the non-STR multilink device can enter the inter-link TXOP power-saving state.

[0254] In the embodiment of FIG. 34, the STR AP multilink device includes a first AP (AP1) operating on a first link (Link1) and a second AP (AP2) operating on a second link (Link2). The non-STR non-AP multilink device includes a first station (STA1) operating on a first link (Link1) and a second station (STA2) operating on a second link (Link2). The non-STR non-AP multilink device signals its desire to receive a sync PPDU. At this time, the non-STR non-AP multilink device also signals the minimum TXOP length "a" required to receive the sync PPDU. The first AP (AP1) transmits to the first station (STA1), and the second station (STA2) waits to receive the sync PPDU. The second station (STA2) detects that a PPDU other than the sync PPDU is being transmitted from the BSS to which the second station belongs. Although the TXOP of the PPDU sent by the first AP (AP1) to the first station (STA1) is larger than 'a', the second station (STA2) enters the inter-link TXOP power saving state.

[0255] Although the present invention has been described above with reference to wireless LAN communication, the present invention is not limited thereto and may be equally applied to other communication systems such as cellular communication. Furthermore, although the method, apparatus, and system of the present invention have been described in relation to specific embodiments, some or all of the components and operations of the present invention may be implemented using a computer system having a general-purpose hardware architecture.

[0256] The features, structures, effects, etc. described in the above embodiments are included in at least one embodiment of the present invention, and are not necessarily limited to one embodiment. Furthermore, the features, structures, effects, etc. exemplified in each embodiment can be combined or modified in other embodiments by a person skilled in the art to which the embodiment belongs. Therefore, content related to such combinations and modifications should be interpreted as being included within the scope of the present invention.

[0257] The above description has focused on the embodiments, but these are merely illustrative and do not limit the present invention. Those skilled in the art will understand that various modifications and applications not exemplified above are possible within the scope of the essential characteristics of the present invention. For example, each component specifically illustrated in the embodiments can be modified and implemented. Differences related to such modifications and applications should be construed as being included within the scope of the present invention as defined by the appended claims. [Explanation of symbols]

[0258] 100 Stations 110 processors 120 Communications Department 140 User Interface Section 150 display units 160 memory 200 AP 210 processors 220 Communications Department 260 memory 300 servers

Claims

1. An AP multilink device, a transceiver; and a processor; The processor: determining whether to transmit to the non-AP multilink device on the second link based on whether the non-AP multilink device transmits on the first link when transmitting to the non-AP multilink device on the second link, wherein the non-AP multilink device operates on the first and second links corresponding to non-simultaneous transmit and receive (STR) links in which the non-AP multilink device's transmission on one of the first and second links is limited to protect the non-AP multilink device's transmission or reception on the other of the first and second links; configured to: In a channel access procedure for the second link, the processor: Obtaining a random number within a contention window (CW); setting the random number as an initial value of a backoff counter for the second link; decrementing the backoff counter by one if the channel is sensed idle during a slot time, and if the backoff counter is not zero, transmission of the AP multilink device on the second link is not permitted; If the backoff counter is 0, the non-AP multilink device does not transmit on the second link while transmitting on the first link; maintaining a value of 0 for the backoff counter, a value of the CW, and a value of a retry counter in the channel access procedure after the non-transmission, wherein the value of the CW is adjusted based on whether channel access for traffic is successful; further configured to: AP multilink device.

2. The AP multilink device of claim 1, wherein the processor is configured to transmit to a device other than the non-AP multilink device, instead of transmitting to the non-AP multilink device on the second link while the non-AP multilink device is transmitting on the first link.

3. The AP multilink device of claim 2, wherein the processor is configured to transmit traffic having the same or higher priority as the traffic of the transmission to the non-AP multilink device when transmitting to the other device other than the non-AP multilink device on the second link.

4. The processor: performing synchronized transmissions on the first link and the second link, the synchronized transmissions ending at different times within a pre-specified first time interval; receiving a transmission subsequent to the synchronized transmission on at least one of the first link and the second link, wherein the interval between the subsequent transmission and the synchronized transmission on the link on which the subsequent transmission occurred is a short inter-frame space (SIFS) plus a time within the pre-specified first time interval; The AP multilink device according to claim 1 , configured to perform the following:

5. The AP multilink device of claim 1 , wherein the processor is configured to transmit on the first link and the second link when the backoff counter is 0 and the channel of the first link is idle.

6. 6. The AP multilink device of claim 5, wherein the processor is configured to start transmission on the first link and the second link within a predetermined second time difference when the backoff counter is 0 and the channel of the first link is idle.

7. A non-AP multilink device, a transceiver; and a processor; the non-AP multi-link device is configured to operate on the first link and the second link corresponding to a non-simultaneous transmit and receive (STR) link in which transmission of the non-AP multi-link device on one of the first link and the second link is limited to protect transmission or reception of the non-AP multi-link device on the other of the first link and the second link; In a channel access procedure for the second link, the processor: Obtaining a random number within a contention window (CW); setting the random number as an initial value of a backoff counter for the second link; decrementing the backoff counter by one if the channel is sensed idle during a slot time, and if the backoff counter is not zero, transmission of the non-AP multilink device on the second link is not permitted; If the backoff counter is 0, the non-AP multilink device does not transmit on the second link while receiving on the first link; maintaining a value of 0 for the backoff counter, a value of the CW, and a value of a retry counter in the channel access procedure after the non-transmission, wherein the value of the CW is adjusted based on whether channel access for traffic is successful; configured to: Non-AP multi-link device.

8. The processor: receiving synchronized transmissions on the first link and the second link, wherein the synchronized transmissions end on the first link and the second link at a time difference within a pre-specified first time interval; performing a transmission subsequent to the synchronized transmission on at least one of the first link and the second link, wherein an interval between the subsequent transmission and the synchronized transmission performed on the link on which the subsequent transmission was performed is a sum of a short inter-frame space (SIFS) and the pre-specified first time interval; 8. The non-AP multilink device according to claim 7, configured to perform the following:

9. 8. The non-AP multi-link device of claim 7, wherein the processor is configured to transmit information regarding whether STR is supported when a frequency band of either the first link or the second link is changed.

10. 8. The non-AP multi-link device of claim 7, wherein the processor is configured to transmit on the first link and the second link when the backoff counter is 0 and the channel of the first link is idle for a pre-specified second time interval.

11. 1. A method of operating an AP multilink device, comprising: When transmitting to the non-AP multilink device operating on the first link and the second link, the non-AP multilink device operating on the first link and the second link corresponds to a non-simultaneous transmit and receive (STR) link in which transmission of the non-AP multilink device on one of the first link and the second link is limited to protect transmission or reception of the non-AP multilink device on the other of the first link and the second link, determining whether to transmit to the non-AP multilink device on the second link based on whether the non-AP multilink device transmits on the first link. The method includes, in a channel access procedure on the second link, obtaining a random number within a contention window (CW); setting the random number as an initial value of a backoff counter for the second link; decrementing the backoff counter by one if the channel is sensed idle during a slot time, and if the backoff counter is not zero, transmission of the AP multilink device on the second link is not permitted; If the backoff counter is 0, the non-AP multilink device does not transmit on the second link while transmitting on the first link; maintaining the backoff counter value of 0, the CW value, and the retry counter value in the channel access procedure after the non-transmission, wherein the CW is adjusted based on whether channel access for traffic is successful; A method comprising:

12. The method of claim 11, further comprising: while the non-AP multilink device is transmitting on the first link, the transmission to the non-AP multilink device is not performed on the second link, but instead transmission is performed to another device other than the non-AP multilink device.

13. The method of claim 12, wherein transmitting to another device other than the non-AP multilink device further includes transmitting traffic having the same or higher priority as the traffic of the transmission to the non-AP multilink device when the transmission to the other device other than the non-AP multilink device is performed on the second link.

14. performing synchronized transmission on the first link and the second link, the synchronized transmission ending on the first link and the second link at a time difference within a pre-specified first time interval; receiving a transmission subsequent to the synchronized transmission from at least one of the first link and the second link, wherein an interval between the subsequent transmission and the synchronized transmission made on the link on which the subsequent transmission was made is a sum of a short inter-frame space (SIFS) and the pre-specified first time interval; The method of claim 11 , comprising:

15. A method of operating a non-AP multilink device, comprising: The non-AP multilink device is configured to operate on the first link and the second link corresponding to a non-simultaneous transmit and receive (STR) link in which transmission of the non-AP multilink device on one of the first link and the second link is restricted to protect transmission or reception of the non-AP multilink device on the other of the first link and the second link, and the method includes, in a channel access procedure on the second link, Obtaining a random number within a contention window (CW); setting the random number as an initial value of a backoff counter for the second link; decrementing the backoff counter by one if the channel is sensed idle during a slot time, and if the backoff counter is not zero, transmission of the non-AP multilink device on the second link is not permitted; If the backoff counter is 0, the non-AP multilink device does not transmit on the second link while receiving on the first link; maintaining a value of 0 for the backoff counter, a value of the CW, and a value of a retry counter in the channel access procedure after the non-transmission, wherein the value of the CW is adjusted based on whether channel access for traffic is successful; A method comprising:

Images