Wireless communication method using multiple links and wireless communication terminal using the method
By introducing a non-simultaneous transmit and receive (STR) link management mechanism into multi-link devices, the problems of low communication efficiency and severe interference in high-density environments are solved, achieving more efficient wireless communication and reducing transmission conflicts and interference.
Patent Information
- Application Number
- CN202611249748.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2020-07-14
- Filing Date
- 2021-05-04
- Publication Date
- 2026-11-17
AI Technical Summary
Existing wireless communication technologies suffer from low communication efficiency and severe interference in high-density environments, especially in simultaneous transmit and receive (STR) links between multiple devices, where it is difficult to effectively manage channel access and transmission synchronization, leading to transmission conflicts and interference.
By introducing a non-simultaneous transmit and receive (STR) link management mechanism in multi-link devices, the processor determines whether to perform transmission in different links, maintains the contention window (CW) for channel access and synchronizes the transmission end, and uses backoff counters and random number mechanisms to manage channel access, ensuring the priority and synchronization of transmission.
It improves the communication efficiency of multi-link devices, reduces transmission conflicts and interference, and enables more efficient wireless communication, especially providing high-frequency and efficient communication in high-density environments.
Smart Images

Figure CN123124118A_ABST
Abstract
Description
[0001] This application is a divisional application of patent application No. 202180032922.9 (International Application No. PCT / KR2021 / 005629), filed on November 3, 2022, with an international application date of May 4, 2021, entitled "A wireless communication method using multiple links and a wireless communication terminal using the method". Technical Field
[0002] This invention relates to a wireless communication method using multiple links and a wireless communication terminal using the method. Background Technology
[0003] In recent years, with the expansion of mobile device supply, wireless LAN technology, which can provide fast wireless internet services to mobile devices, has gained attention. Wireless LAN technology allows mobile devices, including smartphones, tablets, laptops, portable multimedia players, embedded devices, and more, to wirelessly access the internet in their homes, offices, or specific service areas based on short-range wireless communication technology.
[0004] Since using the 2.4 GHz frequency to support initial wireless LAN technology, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 has commercialized or developed various technical standards. First, IEEE 802.11b, using the 2.4 GHz band, supported a maximum communication speed of 11 Mbps. Compared to the significantly congested 2.4 GHz band, IEEE 802.11a, commercialized after IEEE 802.11b, used the 5 GHz band instead of 2.4 GHz to reduce interference and increased the communication speed to a maximum of 54 Mbps through the use of OFDM technology. However, a drawback of IEEE 802.11a is its shorter communication range compared to IEEE 802.11b. Furthermore, similar to IEEE 802.11b, IEEE 802.11g, using the 2.4 GHz band to achieve a maximum communication speed of 54 Mbps and satisfying backward compatibility, has attracted significant attention and, furthermore, outperforms IEEE 802.11a in terms of communication range.
[0005] Furthermore, IEEE 802.11n has been developed as a technical standard to overcome the limitations of communication speed, a weakness identified in wireless LANs. IEEE 802.11n aims to improve network speed and reliability and extend the operating range of wireless networks. More specifically, IEEE 802.11n supports high throughput (HT), with data processing speeds of up to 540 Mbps or higher, and further, it is based on multiple-input multiple-output (MIMO) technology, where multiple antennas are used on both sides of the transmitting and receiving units to minimize transmission errors and optimize data speed. Additionally, the standard can use a compilation scheme that transmits multiple superimposed copies to increase data reliability.
[0006] With the activation of the wireless LAN supply, and further, with the diversification of applications using wireless LAN, the need for new wireless LAN systems supporting higher throughput (Very High Throughput (VHT)) than those supported by IEEE 802.11n has gained attention. Among these, IEEE 802.11ac supports wide bandwidth (80 to 160 MHz) in the 5 GHz frequency band. The IEEE 802.11ac standard is defined only in the 5 GHz band, but initial 11ac chipsets even support operation in the 2.4 GHz band for backward compatibility with existing 2.4 GHz band products. Theoretically, according to this standard, wireless LAN speeds of up to 1 Gbps can be enabled for multiple stations, and a maximum single-link speed of up to 500 Mbps can be achieved. This is achieved through concepts that expand the wireless interface accepted by 802.11n, such as wider wireless frequency bandwidth (up to 160 MHz), more MIMO spatial streams (up to 8), multi-user MIMO, and high-density modulation (up to 256 QAM). Furthermore, IEEE 802.11ad has been offered as a solution for transmitting data using the 60 GHz band instead of the existing 2.4 GHz / 5 GHz band. IEEE 802.11ad is a transmission standard that provides speeds up to 7 Gbps using beamforming technology and is suitable for high bit-rate motion streaming, such as large-scale data or uncompressed HD video. However, its drawback is that the 60 GHz band is difficult to penetrate obstacles, limiting its use to devices operating in close proximity.
[0007] As a wireless LAN standard following 802.11ac and 802.11ad, the IEEE 802.11ax (High-Efficiency WLAN, HEW) standard is nearing completion, designed to provide efficient and high-performance wireless LAN communication in high-density environments where access points (APs) and terminals are concentrated. In 802.11ax-based wireless LAN environments, where high-density stations and access points (APs) are present, high-frequency efficiency communication should be provided indoors / outdoors, and various technologies have been developed to achieve this.
[0008] To support new multimedia applications, such as high-definition video and real-time gaming, new wireless LAN standards are being developed to increase maximum transmission rates. IEEE 802.11be (Extreme High Throughput, EHT), the 7th generation wireless LAN standard, is under development with the aim of supporting transmission rates up to 30Gbps in the 2.4 / 5 / 6 GHz band through wider bandwidth, increased spatial streaming, and multi-AP collaboration. Summary of the Invention
[0009] Technical issues
[0010] Embodiments of the present invention provide a wireless communication method using multiple links and a wireless communication terminal using the method.
[0011] Technical solution
[0012] An AP multilink device according to an embodiment of the present disclosure includes a transceiver and a processor. The processor may be configured to: when a transmission to a non-AP multilink device operating in both the first and second links is performed in a second link, determine whether to perform a transmission to the non-AP multilink device in the second link based on whether the non-AP multilink device is performing a transmission in the first link, wherein the first and second links correspond to simultaneously transmit and receive (STR) links that do not simultaneously support reception of the non-AP multilink device in one link and transmission of the non-AP multilink device in the other link.
[0013] The processor can be configured to: when the non-AP multi-link device performs a transmission in the first link, not perform a transmission to the non-AP multi-link device in the second link.
[0014] The processor can be configured to perform a transmission to a different device than the non-AP multilink device in the second link, instead of the non-AP multilink device, when the non-STR multilink device is performing a transmission in the first link.
[0015] The processor can be configured to send a service with a priority equal to or higher than that of the service to the non-AP multi-link device when performing a transmission to a device different from the non-AP multi-link device in the second link.
[0016] The processor can be configured to: maintain a contention window (CW) value for channel access for transmissions to the non-AP multilink device in the second link, and use the CW value for channel access for transmissions to the different devices. The multilink device can be configured to: during the channel access process of the AP multilink device, acquire a random number within the CW, configure the random number as the initial value of a backoff counter, decrement the backoff counter by 1 when channel idleness is detected during a time slot, and execute transmission when the backoff counter reaches 0.
[0017] The processor can be configured to perform a transmission synchronized at its transmission endpoint in both the first and second links. In this case, the transmission synchronized at its transmission endpoint may terminate in both the first and second links with a time difference within a predetermined time interval. The processor is configured to receive a subsequent transmission in at least one of the first and second links. In this case, the interval between the subsequent transmission and the synchronized transmission performed in the link in which the subsequent transmission was performed may be the sum of SIFS and the predetermined time interval.
[0018] The AP multi-link device can be configured to: during the channel access process of the AP multi-link device, acquire a random number within the CW, configure the random number as the initial value of a backoff counter, decrement the backoff counter by 1 when channel idleness is detected during the time slot, and execute transmission when the backoff counter reaches 0. The processor can be configured to: if the channel of the second link is idle for a first predetermined time when the channel access process is completed in the first link, then execute transmission in both the first and second links.
[0019] The processor can be configured to: if the channel of the second link is idle for a predetermined time when the channel access process is completed in the first link, then transmission will begin in the first link and the second link at the difference of a second predetermined time.
[0020] A non-AP multi-link device according to an embodiment of the present disclosure may include: a transceiver; and a processor. The non-AP multi-link device may be configured to operate in a first link and a second link corresponding to a Non-Simultaneous Transmit and Receive (STR) link, wherein the STR links do not simultaneously support reception by the non-AP multi-link device in one link and transmission by the non-AP multi-link device in the other link. The processor may be configured to: when transmission is performed in the first link, not perform transmission in the second link, and after the transmission is completed in the first link, initiate a Request to Send / Clear Transmit (RTS / CTS) frame exchange in the second link.
[0021] The processor is configured to receive transmissions synchronized at its transmission endpoint in both the first and second links. The synchronized transmissions at its transmission endpoint may terminate in both the first and second links with a time difference within a predetermined time interval. The processor may be configured to perform subsequent transmissions of the synchronized transmission in at least one of the first and second links. The interval between the subsequent transmission and the synchronized transmission performed in the link in which the subsequent transmission is performed may be the sum of SIFS and the predetermined time interval.
[0022] When the frequency band of one of the multiple links changes, information about whether STR is supported is sent.
[0023] The non-AP multi-link device can be configured to: during the channel access process of the non-AP multi-link device, acquire a random number within a contention window (CW), configure the random number as the initial value of a backoff counter, decrement the backoff counter by 1 when channel idleness is detected during a time slot, and execute a transmission when the backoff counter reaches 0. The processor can be configured to maintain the value of the backoff counter for transmissions that are not executed at 0.
[0024] The non-AP multi-link device can be configured to: during the channel access process of the non-AP multi-link device, acquire a random number within a contention window (CW), configure the random number as the initial value of a backoff counter, decrement the backoff counter by 1 when channel idleness is detected during a time slot, and execute transmission when the backoff counter reaches 0. At this time, the processor can be configured to execute transmission in both the first and second links if the channel of the second link is idle for a first predetermined time when the channel access process is completed in the first link.
[0025] If the channel on the second link is idle for a predetermined time when the channel access process is completed on the first link, the processor can be configured to start transmission on the first link and the second link at the difference of a second predetermined time.
[0026] A method of operating an AP multilink device according to an embodiment of the present disclosure includes: when a transmission to a non-AP multilink device operating in a first link and the second link is performed in a second link, determining whether to perform a transmission to the non-AP multilink device in the second link based on whether the non-AP multilink device performs a transmission in the first link, wherein the first link and the second link correspond to non-simultaneous transmit and receive (STR) links that do not simultaneously support reception of the non-AP multilink device in one link and transmission of the non-AP multilink device in the other link.
[0027] Determining whether to perform a transmission to the non-AP multi-link device in the second link based on whether a transmission is being performed in the first link may include: when the non-AP multi-link device is performing a transmission in the first link, not performing a transmission to the non-AP multi-link device in the second link.
[0028] The method may further include: when the non-STR multilink device performs a transmission in the first link, performing a transmission in the second link to a device different from the non-AP multilink device, instead of a transmission to the non-AP multilink device.
[0029] The transmission to a device different from the non-AP multi-link device may further include: when the transmission to a device different from the non-AP multi-link device is performed in the second link, sending a service with a priority equal to or higher than that of the transmission to the non-AP multi-link device.
[0030] The method may further include: maintaining a contention window (CW) value for channel access for transmissions to the non-AP multilink device in the second link, and using the CW value for channel access for transmissions to the different devices. The multilink device may be configured to: during the channel access process of the AP multilink device, acquire a random number within the CW, configure the random number as the initial value of a backoff counter, decrement the backoff counter by 1 when channel idleness is detected during a time slot, and perform transmission when the backoff counter reaches 0.
[0031] The method may further include: performing a transmission synchronized at its transmission end in the first link and the second link, wherein the transmission synchronized at its transmission end terminates in the first link and the second link with a time difference within a predetermined time interval, and
[0032] A subsequent transmission is received from at least one of the first link and the second link, wherein the interval between the subsequent transmission and the synchronous transmission performed in the link in which the subsequent transmission is performed is the sum of SIFS and the predetermined time interval.
[0033] The AP multi-link device can be configured to: during the channel access process of the AP multi-link device, acquire a random number within the CW, configure the random number as the initial value of a backoff counter, decrement the backoff counter by 1 when channel idleness is detected during the time slot, and perform transmission when the backoff counter reaches 0. The method may further include: if the channel of the second link is idle for a first predetermined time when the channel access process is completed in the first link, then perform transmission in both the first link and the second link.
[0034] The method may further include: if the channel of the second link is idle for a predetermined time when the channel access process is completed in the first link, then transmission begins in the first link and the second link with a difference of a second predetermined time.
[0035] Beneficial effects
[0036] Embodiments of the present invention provide a wireless communication method for efficiently using multiple links and a wireless communication terminal using the method. Attached Figure Description
[0037] Figure 1 The illustration shows a wireless LAN system according to an embodiment of the present invention.
[0038] Figure 2 The illustration shows a wireless LAN system according to another embodiment of the present invention.
[0039] Figure 3 The illustration shows the configuration of a station according to an embodiment of the present invention.
[0040] Figure 4 The diagram illustrates the configuration of an access point according to an embodiment of the present invention.
[0041] Figure 5 This diagram illustrates the process of setting up a link between a STA and an AP.
[0042] Figure 6The diagram illustrates the Carrier Sense Multiple Access (CSMA) / Collision Avoidance (CA) method used in wireless LAN communication.
[0043] Figure 7 The diagram illustrates an example of the format of the PLCP Protocol Data Unit (PPDU) used in each of the various standard generations.
[0044] Figure 8 The illustrations depict various Extremely High Throughput (EHT) Physical Protocol Data Unit (PPDU) formats according to embodiments of the present invention, as well as examples of methods for indicating such formats.
[0045] Figure 9 The illustration shows a multi-link device according to an embodiment of the present disclosure.
[0046] Figure 10 The illustration shows simultaneous transmission of different links in a multi-link operation according to an embodiment of the present disclosure.
[0047] Figure 11 The illustration shows the operation of a multi-link device according to an embodiment of the present disclosure when a link changes.
[0048] Figure 12 The illustration shows an embodiment of the present disclosure where channel access is blocked for another station of a non-STR multilink device when one station of the non-STR multilink device is receiving data.
[0049] Figure 13 The illustration shows the operation of releasing channel access prohibition when it is identified that the intended receiver of the PPDU received by a station of a non-STR multilink device is not that station.
[0050] Figure 14 The illustration shows a channel access being performed by the station after the channel access ban has been released, according to an embodiment of the present disclosure.
[0051] Figure 15 The illustration shows the operation of a station performing a transmission after the channel access ban is released, according to an embodiment of the present disclosure.
[0052] Figure 16 The illustration shows a transmission performed based on the state of a station within a non-STR multilink device according to an embodiment of the present disclosure.
[0053] Figure 17 The diagram illustrates situations where interference or collisions may occur between links.
[0054] Figure 18 The illustration shows the operation of an STR multilink device stopping transmission to a non-STR multilink device according to an embodiment of the present disclosure.
[0055] Figure 19The illustration shows the processing of the CW value when the STR multilink device identifies a transmission conflict between links, according to an embodiment of the present disclosure.
[0056] Figure 20 The illustration shows an STR multilink device according to an embodiment of the present disclosure stopping transmission to a non-STR multilink device and then re-performing channel access.
[0057] Figure 21 The illustration shows the operation of an STR multilink device sending a CTS-to-Self frame before transmission to a non-STR multilink device according to an embodiment of the present disclosure.
[0058] Figure 22 The illustration depicts a transmission performed by multiple APs included in an STR multilink device to multiple stations included in a non-STR multilink device, according to an embodiment of the present disclosure.
[0059] Figure 23 The illustration depicts multiple transmissions performed by multiple APs included in an STR multilink device to multiple stations included in a non-STR multilink device, according to an embodiment of the present disclosure, with the transmission ends of the multiple transmissions being synchronized.
[0060] Figure 24 The illustration shows the exchange of RTS / CTS frames by a multi-link device according to an embodiment of the present disclosure.
[0061] Figure 25 The diagram illustrates the reference. Figure 24 The hidden node problem that occurs during RTS / CTS frame switching in embodiments of this disclosure is described.
[0062] Figure 26 The illustration shows RTS / CTS frame switching performed by a multi-link device according to an embodiment of the present disclosure.
[0063] Figure 27 The illustration shows an embodiment of the present disclosure in which a multi-link device exceptionally sends a response to a control frame even when channel access is prohibited.
[0064] Figure 28 The diagram illustrates the retransmission of data to a station that is not part of the STR multilink device.
[0065] Figure 29 The illustration shows the transmission of control frames according to an embodiment of the present disclosure via a link in which a channel access is not prohibited for operation, rather than a link in which a channel access is prohibited for operation.
[0066] Figure 30 The illustration shows an ACK being sent by a multi-link device according to an embodiment of the present disclosure.
[0067] Figure 31 The illustration shows element fields indicating information supporting synchronous PPDU reception or transmission according to embodiments of the present disclosure.
[0068] Figure 32 The illustration shows an inter-link TXOP power saving mode operation performed by a non-STR multi-link device according to an embodiment of the present disclosure.
[0069] Figure 33 The illustration shows a station of a non-STR multilink device according to an embodiment of the present disclosure receiving a synchronization PPDU and entering a sleep state.
[0070] Figure 34 The illustration shows a station of a non-STR multilink device according to another embodiment of the present disclosure receiving a synchronization PPDU and entering a sleep state. Detailed Implementation
[0071] In consideration of the functionality of this invention, the terminology used in this specification employs currently widely used and common terms; however, the terminology may change according to the intent, habits, and emergence of new technologies of those skilled in the art. Furthermore, in certain cases, there are terms arbitrarily chosen by the applicant, and in such cases, their meaning will be described in the corresponding descriptive section of the invention. Therefore, it should be understood that the terminology used in this specification should be analyzed not only based on the name of the term, but also on its substantive meaning and the content of the entire specification.
[0072] Throughout this specification and the following claims, when an element is described as being “coupled” to another element, that element may be “directly coupled” to the other element or “electrically coupled” to the other element via a third element. Furthermore, unless expressly stated otherwise, the word “comprising” will be understood to implicitly include the stated element but does not exclude any other element. Additionally, limitations based on specific thresholds, such as “or more” or “or less”, may be appropriately replaced by “greater than” or “less than”, respectively.
[0073] In this invention, fields and subfields can be used interchangeably.
[0074] Figure 1 The illustration shows a wireless LAN system according to an embodiment of the present invention.
[0075] Figure 1 This diagram illustrates a wireless LAN system according to an embodiment of the present invention. The wireless LAN system includes one or more Basic Service Sets (BSSs), and a BSS represents a set of devices that have successfully synchronized with each other to communicate. Typically, a BSS can be divided into a Infrastructure BSS and Independent BSSs (IBSSs), and Figure 1 The diagram shows the basic structure BSS between them.
[0076] like Figure 1 As shown, the infrastructure BSS (BSS1 and BSS2) includes one or more stations STA1, STA2, STA3, STA4 and STA5, access points AP-1 and AP-2 as stations providing distributed services, and a distributed system (DS) connecting multiple access points AP-1 and AP-2.
[0077] A station (STA) is a predetermined device comprising a Media Access Control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for wireless media, and broadly includes both non-access point (non-AP) stations and access point (AP) stations. Furthermore, in this specification, the term "terminal" may be used to refer to a non-AP STA, or an AP, or both. A station for wireless communication includes a processor and a communication unit, and according to embodiments, may further include a user interface unit and a display unit. The processor can generate frames to be transmitted via a wireless network, or process frames to be received via a wireless network, and further performs various processes for controlling the station. Additionally, the communication unit is functionally connected to the processor and transmits and receives frames via the wireless network for the station. According to the invention, "terminal" can be used as a term including user equipment (UE).
[0078] An access point (AP) is an entity that provides access to a distributed system (DS) via wireless media used by its associated stations. In an infrastructure BSS, communication between non-AP stations is generally performed via the AP, but direct communication between non-AP stations is even permitted when a direct link is configured. In this invention, AP is used as a concept encompassing a Personal BSS Coordination Point (PCP), and broadly can include concepts including a central controller, base station (BS), node B, base transceiver system (BTS), and station controller. In this invention, AP can also be referred to as a base station wireless communication terminal. The term base station wireless communication terminal can be used broadly to include AP, base station, eNB (i.e., e-node B), and transport point (TP). Furthermore, a base station wireless communication terminal can include various types of wireless communication terminals that allocate media resources and perform scheduling of communication with multiple wireless communication terminals.
[0079] Multiple infrastructure BSSs can be interconnected via a distributed system (DS). In this case, the multiple BSSs connected via the distributed system are called an extended service set (ESS).
[0080] Figure 2 The illustration shows a standalone BSS according to another embodiment of the present invention, which is a wireless LAN system. Figure 2 In the embodiments, with Figure 1 Same or corresponding Figure 1 Repeated descriptions of certain embodiments will be omitted.
[0081] Because in Figure 2 The BSS3 shown in the diagram is an independent BSS and does not include the AP. All stations STA6 and STA7 are not connected to the AP. Independent BSSs are not allowed to access distributed systems and form self-contained networks. Within an independent BSS, the corresponding stations STA6 and STA7 can be directly interconnected.
[0082] Figure 3 This is a block diagram illustrating the configuration of station 100 according to an embodiment of the present invention. (As shown in...) Figure 3 As shown in the figure, the station 100 according to an embodiment of the present invention may include a processor 110, a communication unit 120, a user interface unit 140, a display unit 150, and a memory 160.
[0083] First, the communication unit 120 transmits and receives wireless signals, such as wireless LAN packets, and can be embedded in the station 100 or provided as a peripheral. According to embodiments, 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 with different frequency bands (such as 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz). According to embodiments, the station 100 may include communication modules using frequency bands of 7.125 GHz or higher, and communication modules using frequency bands of 7.125 GHz or lower. Each communication module can perform wireless communication with an AP or external station according to the wireless LAN standard of the frequency band supported by the respective 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 implemented by an independent component, or multiple modules may be integrated into a single chip. In embodiments of the invention, the communication unit 120 may represent a radio frequency (RF) communication module for processing RF signals.
[0084] Secondly, the user interface unit 140 includes various types of input / output devices provided in the station 100. That is, the user interface unit 140 can receive user input using various input devices, and the processor 110 can control the station 100 based on the received user input. Furthermore, the user interface unit 140 can execute outputs based on commands from the processor 110 using various output devices.
[0085] Next, the display unit 150 outputs an image on the display screen. The display unit 150 can output various display objects based on control commands from the processor 110, such as content executed by the processor 110 or a user interface. Furthermore, the memory 160 stores the control program and various result data used in the station 100. The control program may include the access program required for the station 100 to connect to the AP or an external station.
[0086] The processor 110 of the present invention can execute various commands or programs and process data in the station 100. Furthermore, the processor 110 can control various units of the station 100 and control data transmission / reception within the units. According to an embodiment of the present invention, the processor 110 can execute a program for accessing an AP stored in the memory 160 and receive communication configuration messages sent by the AP. Furthermore, the processor 110 can read information about the priority conditions of the station 100 included in the communication configuration messages and request access to the AP based on the information about the priority conditions of the station 100. The processor 110 of the present invention can represent the main control unit of the station 100, and according to an embodiment, the processor 110 can represent a control unit for individually controlling certain components of the station 100 (e.g., communication unit 120, etc.). That is, the processor 110 can be a modem or modulator / demodulator for modulating wireless signals transmitted to the communication unit 120 and demodulating wireless signals received from the communication unit 120. The processor 110 controls various operations of wireless signal transmission / reception of the station 100 according to an embodiment of the present invention. Detailed embodiments thereof will be described below.
[0087] exist Figure 3 The station 100 illustrated in the diagram is a block diagram according to an embodiment of the present invention, where the separate blocks are illustrated as logically distinct device elements. Therefore, the device elements can be installed on a single chip or multiple chips depending on the device design. For example, the processor 110 and the communication unit 120 can be implemented as a single chip or as separate chips. Furthermore, in embodiments of the present invention, certain 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.
[0088] Figure 4 This is a block diagram illustrating the configuration of AP 200 according to an embodiment of the present invention. (As shown in...) Figure 4 As illustrated in the figure, the AP 200 according to an embodiment of the present invention may include a processor 210, a communication unit 220, and a memory 260. Figure 4 In the AP200 components, and... Figure 2 The components of station 100 are the same or correspond to Figure 2 Repeated descriptions of parts of station 100 will be omitted.
[0089] refer to Figure 4 The AP 200 according to the invention includes a communication unit 220 that operates a BSS in at least one frequency band. (As in...) Figure 3 As described in the embodiments, the communication unit 220 of AP 200 may also include multiple communication modules using different frequency bands. That is, AP 200 according to embodiments of the present invention may together include two or more communication modules in different frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz). Preferably, AP 200 may include communication modules using frequency bands of 7.125 GHz or higher, and communication modules using frequency bands of 7.125 GHz or lower. Each communication module may perform wireless communication with the station according to the wireless LAN standard of the frequency band supported by the respective communication module. Communication unit 220 may operate one communication module at a time, or operate multiple communication modules simultaneously, depending on the performance and requirements of AP 200. In embodiments of the present invention, communication unit 220 may represent a radio frequency (RF) communication module for processing RF signals.
[0090] Next, memory 260 stores the control program and various result data used in AP 200. The control program may include an access program for managing station access. Furthermore, processor 210 can control the various units of AP 200 and control data transmission / reception within the units. According to an embodiment of the invention, processor 210 can execute the program for access stations stored in memory 260 and send communication configuration messages for one or more stations. In this case, the communication configuration message may include information about access priority conditions for each station. Furthermore, processor 210 performs access configuration according to the access request of a station. According to an embodiment, processor 210 may be a modem or modulator / demodulator for modulating wireless signals transmitted to communication unit 220 and demodulating wireless signals received from communication unit 220. Processor 210 controls various operations, such as wireless signal transmission / reception of AP 200, according to embodiments of the invention. Detailed embodiments thereof will be described below.
[0091] Figure 5 This is a diagram illustrating the process of setting up a link between a STA and an AP.
[0092] refer to Figure 5In a broad sense, the link between STA 100 and AP 200 is set up through three steps: scanning, authentication, and association. First, the scanning step is where STA 100 obtains access information from the BSS operated by AP 200. Methods for performing the scan include a passive scanning method, in which AP 200 obtains information by periodically sending beacon messages (S101), and an active scanning method, in which STA 100 sends a probe request to AP (S103) and obtains access information by receiving a probe response from AP (S105).
[0093] STA 100, having successfully received wireless access information during the scanning step, performs an authentication step by sending an authentication request (S107a) and receiving an authentication response from AP 200 (S107b). After performing the authentication step, STA 100 performs an association step by sending an association request (S109a) and receiving an association response from AP 200 (S109b). In this specification, association primarily refers to wireless association; however, the invention is not limited thereto, and association can broadly include both wireless and wired associations.
[0094] Meanwhile, the 802.1X-based authentication step (S111) and the IP address acquisition step via DHCP (S113) can be performed separately. Figure 5 In this context, authentication server 300 is the server that handles 802.1X-based authentication for STA 100, and can exist in a physical association with AP 200 or as a standalone server.
[0095] Figure 6 This is a diagram illustrating the Carrier Sensing Multiple Access (CSMA) / Collision Avoidance (CA) method used in wireless LAN communication.
[0096] Terminals performing wireless LAN communication check channel busy by performing carrier sensing before transmitting data. When a wireless signal of predetermined strength or greater is sensed, the corresponding channel is determined to be busy, and the terminal delays access to that channel. This process is called Clear Channel Assessment (CCA), and the level at which a corresponding signal is sensed is called the CCA threshold. When a terminal receives a wireless signal with a CCA threshold or higher that indicates it is the receiving terminal, the terminal processes the received wireless signal. Conversely, when no wireless signal is detected in the corresponding channel, or a wireless signal with a strength less than the CCA threshold is detected, the channel is determined to be idle.
[0097] When the channel is determined to be idle, each terminal with data to transmit performs a backoff procedure after an inter-frame interval (IFS) period, the duration of which depends on the specific terminal, such as an Arbitrated IFS (AIFS), PCF IFS (PIFS), etc. According to this embodiment, AIFS can be used as a component to replace the existing DCF IFS (DIFS). During the idle period of the channel, each terminal waits while decreasing the slot time by a random number determined by the corresponding terminal, and the terminal that has completely exhausted the slot time attempts to access the corresponding channel. Thus, the interval during which each terminal performs the backoff procedure is called the contention window interval. In this case, the random number is called a backoff counter. That is, the initial value of the backoff counter can be set as an integer, which is the random number obtained by the UE. If the UE detects that the channel is idle during the slot time, the UE can decrement the backoff counter by 1. Furthermore, if the backoff counter reaches 0, the UE can be allowed to perform channel access in the corresponding channel. Therefore, if the channel is idle during the AIFS time and the slot time of the backoff counter, the UE can be allowed to transmit.
[0098] When a specific terminal successfully accesses the channel, the corresponding terminal can transmit data through the channel. However, when a terminal attempting to access the channel conflicts with another terminal, the conflicting terminals are each assigned a new random number to re-execute the backoff process. According to an embodiment, this can be done within the range (2... Within the range (CW), a new random number is determined for each terminal, within which (2... The contention window (CW) is twice the range of random numbers previously assigned to the respective terminals. Simultaneously, each terminal attempts access by performing a backoff procedure again in the next contention window interval, and in this case, each terminal begins the backoff procedure from the remaining time slot of the previous contention window interval. In this way, individual terminals performing wireless LAN communication can avoid mutual collisions on specific channels.
[0099] <Examples of various PPDU formats>
[0100] Figure 7 The illustration shows an example of the format of the PLCP Protocol Data Unit (PPDU) used in each of the various standard generations. More specifically, Figure 7 The illustration in (a) is based on an embodiment of the conventional PPDU format of 802.11a / g. Figure 7 The illustration in (b) is based on an embodiment using the 802.11ax HE PPDU format, and Figure 7 (c) illustrates an embodiment based on a non-traditional PPDU (i.e., EHTPPDU) of 802.11be. Figure 7(d) shows the detailed field configuration of RL-SIG and L-SIG, which are commonly used in the PPDU format.
[0101] refer to Figure 7 (a) The preamble of a conventional PPDU includes a conventional short training field (L-STF), a conventional long training field (L-LTF), and a conventional signal field (L-SIG). In embodiments of the present invention, L-STF, L-LTF, and L-SIG may be referred to as conventional preambles.
[0102] refer to Figure 7 (b) The HE PPDU preamble also includes, in a conventional preamble, a repeated conventional 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 embodiments of the present invention, RL-SIG, HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF may be referred to as HE preambles. The detailed configuration of the HE preamble can be modified according to the HE PPDU format. For example, HE-SIG-B may only be used in the HE MU PPDU format.
[0103] refer to Figure 7 (c) The EHT PPDU also includes, in its conventional preamble, a repeated conventional short training field (RL-SIG), a universal signal field (U-SIG), and a very high throughput signal A field (EHT-SIG-A), a very high throughput signal B field (EHT-SIG-B), a very high throughput short training field (EHT-STF), and a very high throughput long training field (EHT-LTF). In embodiments of the present invention, RL-SIG, EHT-SIG-A, EHT-SIG-B, EHT-STF, and EHT-LTF may be referred to as EHT preambles. The specific configuration of non-conventional preambles can be modified according to the EHT PPDU format. For example, EHT-SIG-A and EHT-SIG-B may be used only in a portion of the EHTPPDU format.
[0104] 64-FFT OFDM is applied to the L-SIG field included in the preamble of the PPDU, and the L-SIG field comprises a total of 64 subcarriers. Of these 64 subcarriers, 48 subcarriers other than the guard subcarrier, DC subcarrier, and pilot subcarrier are used for L-SIG data transmission. BPSK and a modulation and coding scheme (MCS) with a code rate of 1 / 2 are applied to the L-SIG, so the L-SIG can include a total of 24 bits of information. Figure 7 (d) shows the configuration of the 24-bit information of L-SIG.
[0105] refer to Figure 7 (d) L-SIG includes the L_RATE and L_LENGTH fields. The L_RATE field consists of 4 bits and indicates the MCS used for data transmission. Specifically, the L_RATE field indicates a value of 6 / 9 / 12 / 18 / 24 / 36 / 48 / 54 Mbps obtained by combining modulation schemes such as BPSK / QPSK / 16-QAM / 64-QAM with inefficient values such as 1 / 2, 2 / 3, 3 / 4, etc. The total length of the corresponding PPDU can be indicated by combining the information from the L_RATE and L_LENGTH fields. In non-traditional PPDU formats, the L_RATE field is configured with a minimum rate of 6 Mbps.
[0106] The L_LENGTH field is in bytes and is allocated a total of 12 bits, allowing for up to 4095 signal notifications. The length of the PPDU can be indicated in conjunction with the L_RATE field. Traditional and non-traditional terminals may interpret the L_LENGTH field differently.
[0107] First, the method for interpreting the length of the PPDU using the L_LENGTH field through traditional or non-traditional terminals is as follows. When the L_RATE field is set to 6 Mbps, it is possible to transmit 3 bytes (i.e., 24 bits) within 4 µs, where 4 µs is the duration of one symbol in a 64 FFT. Therefore, the number of symbols based on 64 FFT after L-SIG is obtained by adding the 3 bytes corresponding to the SVC field and the tail field to the value of the L_LENGTH field and dividing it by the 3 bytes of transmission as a symbol. The corresponding PPDU length, i.e., the reception time (i.e., RXTIME), is obtained by multiplying the obtained number of symbols by 4 µs as a symbol duration and then adding the 20 µs used for transmitting L-STF, L-LTF, and L-SIG. This can be represented by the following Equation 1.
[0108] [Equation 1]
[0109] in this case, This 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 can be set to up to 5.464 ms. Non-traditional terminals sending PPDUs should set the L_LENGTH field as shown in Equation 2 below.
[0110] [Equation 2]
[0111] Here, TXTIME is the total transmission time that makes up the corresponding PPDU, and is represented by Equation 3 below. In this case, TX represents the transmission time of X.
[0112] [Equation 3]
[0113] Referring to the equation above, the length of the PPDU is calculated based on the up-rounded value of L_LENGTH / 3. Therefore, for random values of k, three different values of L_LENGTH={3k+1, 3k+2, 3(k+1)} indicate the same PPDU length.
[0114] refer to Figure 7 (e) The Universal SIG (U-SIG) field continues to exist in subsequent generations of EHT PPDUs and WLAN PPDUs, and is used to classify PPDUs of a generation including 11be. U-SIG is an OFDM 2 symbol based on 64 FFT and can transmit a total of 52 bits of information. Of these 52 bits, 43 bits, excluding the 9 bits for CRC / tail, are mainly divided into a Version Independent (VI) field and a Version Dependent (VD) field.
[0115] The VI bits enable the current bit configuration to be maintained subsequently, so that even if a next-generation PPDU is defined, the current 11be terminal can obtain information about the PPDU through the VI fields of the PPDU. For this purpose, the VI fields include PHY version, UL / DL, BSS color, TXOP, and a reserved field. The PHY version field is 3 bits and is used to sequentially classify 11be and subsequent generations of wireless LAN standards into versions. The value for 11be is 000b. The UL / DL field identifies whether the PPDU is an uplink / downlink PPDU. The BSS color indicates the identifier of each BSS defined in 11ax and has a value of 6 bits or more. The TXOP indicates the transmission opportunity duration sent in the MAC header, where the PPDU can infer the length of the TXOP included in it by adding the TXOP to the PHY header without having to decode the MPDU, and the TXOP has a value of 7 bits or more.
[0116] The VD field contains signaling information useful only for the 11be version of the PPDU and can include fields common to 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 classifier that categorizes EHT Single User (SU), EHT Multi-User (MU), EHT Trigger-Based (TB), EHT Extended Range (ER) PPDUs, etc. The BW field signals five basic PPDU BW options (BW, which can be set to 20 MHz) at 20, 40, 80, 160 (80+80), and 320 (160+160) MHz. The signaling is expressed as a power of 2 (which can be referred to as the basic BW), and various residual PPDU BWs configured via preamble piercing. After signaling at 320MHz, signaling can be executed in some 80MHz pierced form. The pierced and modified channel type can be signaled directly in the BW field, or the pierced and modified channel type can be signaled using the BW field along with fields appearing after the BW field (e.g., fields within the EHT-SIG field). If the BW field is configured with 3 bits, a total of 8 BW signalings can be executed, and therefore up to 3 signalings can be executed in pierced mode. If the BW field is configured with 4 bits, a total of 16 BW signalings can be executed, and therefore up to 11 signalings can be executed in pierced mode.
[0117] The fields following the BW field vary depending on the type and format of the PPDU. MU PPDUs and SU PPDUs can be signaled in the same PPDU format. Fields used for classification between MU and SU PPDUs can precede the EHT-SIG field, and additional signaling can be applied to this field. Both SU and MU PPDUs include the EHT-SIG field, but some fields not needed in the SU PPDU can be compressed. Information about fields that have been compressed can be omitted or can have a smaller size than the original fields included in the MU PPDU. For example, in the case of SU PPDUs, common fields of EHT-SIG can be omitted or replaced, or the SU PPDU can have a different configuration, where user-specific fields are replaced, reduced to one, etc.
[0118] Alternatively, the SU PPDU may also include a compression field indicating whether compression is performed, and a portion of a field (e.g., the RA field, etc.) may be omitted depending on the value of the compression field.
[0119] If a portion of the EHT-SIG field of the SUPPDU is compressed, the information to be included in the compressed field can also be signaled in the uncompressed field (e.g., the common field, etc.). The MU PPDU corresponds to a PPDU format for simultaneous reception by multiple users, and therefore requires the EHT-SIG field to be transmitted after the U-SIG field, and the amount of information transmitted can vary. That is, multiple MU PPDUs are sent to multiple STAs, such that each STA should identify the location of the RU to which the MU PPDU was transmitted, the STA to which the RU is assigned, and whether the transmitted MU PPDU has been sent to the STA itself. Therefore, the AP should transmit this information by including the above information in the EHT-SIG field. For this purpose, information for valid transmission of the EHT-SIG field is signaled in the U-SIG field, and this can correspond to the MCS as a modulation method and / or the number of symbols in the EHT-SIG field. The EHT-SIG field can include information about the size and location of the RU assigned to each user.
[0120] In the case of SU PPDU, multiple RUs can be assigned to a STA, and these RUs can be consecutive or discontinuous. If the RUs assigned to the STA are discontinuous, the STA should identify the intermediate punched RUs in order to effectively receive the SUPPDU. Therefore, the AP can send a SU PPDU that includes information about the punched RUs among those assigned to the STA (e.g., the punching pattern of the RUs, etc.). That is, in the case of SU PPDU, a punching mode field can be included in the EHT-SIG field. This punching mode field includes information indicating the punching pattern in bitmap format, etc., and whether a punching mode has been applied. The punching mode field can signal the type of discontinuous channel occurring within the bandwidth.
[0121] The types of discontinuous channels notified by signals are limited, and the BW and discontinuous channel information of the SU PPDU are indicated by the combination of the BW field value and the SU PPDU. For example, the SU PPDU is a PPDU sent only to a single terminal, so that the STA can identify the bandwidth allocated to itself via the BW field included in the PPDU, and the SU PPDU can identify the punctured resources in the allocated bandwidth via the punctured mode field of the EHT-SIG field or U-SIG field included in the PPDU. In this case, the terminal can receive the PPDU in the remaining resource units after excluding the specific channels of the punctured resource units. Multiple RUs allocated to the STA can be configured by different frequency bands or tones.
[0122] To reduce the signaling overhead of the SU PPDU, only a limited number of discontinuous channel types are signaled. Puncture can be performed on each 20MHz sub-channel. Therefore, if puncturing is performed on a BW (such as 80, 160, and 320MHz) with a large number of 20MHz sub-channels, then in the case of 320MHz, the discontinuous channel type (if puncturing only the edge 20MHz is also considered discontinuous) should be signaled by indicating whether each of the remaining 15 20MHz sub-channels after excluding the main channel is used. Thus, considering the low transmission rate of the signaling section, allocating 15 bits to signal the discontinuous channel type transmitted by a single user could be excessive signaling overhead.
[0123] This invention proposes a technique for signaling the discontinuous channel type of a SU PPDU, and illustrates the discontinuous channel type determined according to the proposed technique. This invention also proposes a technique for signaling each of the puncture types in a 320MHz BW configuration of a SU PPDU, specifically for the primary 160MHz and secondary 160MHz puncture types.
[0124] One embodiment of the present invention proposes a technique for configuring a PPDU indicated by a preamble piercing (BW) value differently depending on the PPDU format notified by a signal in the PPDU format field. Assuming the BW field is 4 bits, and in the case of an EHTSU PPDU or a TB PPDU, a 1-symbol EHT-SIG-A can be notified by a signal after U-SIG, or EHT-SIG-A can be notified at all. Therefore, considering this, it is necessary to fully signal up to 11 piercing modes via the BW field of U-SIG alone. However, in the case of an EHT MU PPDU, EHT-SIG-B is notified by a signal after U-SIG, thus allowing up to 11 piercing modes to be signaled in a different way than the SU PPDU method. In the case of an EHT ER PPDU, the BW field can be configured to be 1 bit to signal whether the EHT ER PPDU uses a 20MHz or 10MHz band.
[0125] Figure 7(f) illustrates the configuration of the format-specific fields of the VD field when an EHT MU PPDU is indicated in the PPDU format field of the U-SIG. In the case of a MU PPDU, SIG-B is necessary; it is a signaling field used for simultaneous reception by multiple users and can be sent after U-SIG without a separate SIG-A. Therefore, information for decoding SIG-B should be signaled in the U-SIG. These fields include SIG-B MCS, SIG-B DCM, the number of SIG-B symbols, SIG-B compression, and the number of EHT-LTF symbols.
[0126] Figure 8 The illustration shows examples of various Ultra High Throughput (EHT) Physical Protocol Data Unit (PPDU) formats according to embodiments of the present invention, as well as methods for indicating such formats.
[0127] Reference Figure 8 A PPDU can include a preamble and a data portion, and can be classified as an EHT PPDU format based on the U-SIG field included in the preamble. Specifically, the PPDU format field included in the U-SIG field can indicate whether the PPDU is an EHT PPDU.
[0128] Figure 8 (a) shows an example of the EHT SU PPDU format for a single STA. The EHT SU PPDU is a PPDU used for single-user (SU) transmissions between an AP and a single STA, and the EHT-SIG-A field for additional signaling can be located after the U-SIG field.
[0129] Figure 8 (b) shows an example of the EHT trigger-based PPDU format corresponding to the EHT PPDU transmitted based on the trigger frame. The EHT trigger-based PPDU is an EHT PPDU transmitted based on the trigger frame and is an uplink PPDU used in response to the trigger frame. Unlike the EHT SU PPDU, the EHT-SIG-A field is not located after the U-SIG field in the EHT PPDU.
[0130] Figure 8 (c) shows an example of an EHT MU PPDU format corresponding to an EHT PPDU for multiple users. An EHT MU PPDU is a PPDU used to send PPDUs to one or more STAs. In the EHT MU PPDU format, the HE-SIG-B field may follow the U-SIG field.
[0131] Figure 8(d) shows an example of the EHT ERSU PPDU format, which is used for transmission with a single user across an extended range of STAs. Figure 8 Compared to the EHT SU PPDU described in (a), the EHT ER SU PPDU can be used for single-user transmission with a wider range of STAs, and the U-SIG field can be repeatedly positioned on the time axis.
[0132] Figure 8 The EHT MU PPDU described in (c) can be used by the AP to perform downlink transmissions to multiple STAs. Here, the EHT MU PPDU may include scheduling information that allows multiple STAs to simultaneously receive PPDUs sent from the AP. The EHT MU PPDU may transmit the sender's and / or receiver's AID information of the PPDU sent via the user-specific field of EHT-SIG-B to the STA. Therefore, multiple terminals that have received the EHT MU PPDU can perform spatial reuse operations based on the AID information included in the user-specific field of the preamble of the received PPDU.
[0133] Specifically, the Resource Unit Allocation (RA) field of the HE-SIG-B field included in the HE MU PPDU can include information about the configuration (e.g., the partitioning of resource units) of resource units within a specific bandwidth (e.g., 20 MHz, etc.) of the frequency axis. That is, the RA field can indicate the configuration of resource units partitioned within the bandwidth used for the transmission of the HE MU PPDU so that the STA can receive the PPDU. Information about the STA allocated (or designated) to each partitioned resource unit can be included in the user-specific fields of the EHT-SIG-B field for transmission to the STA. That is, the user-specific fields can include one or more user fields corresponding to the respective partitioned resource unit.
[0134] For example, the user field corresponding to at least one resource unit among multiple segmented resource units used for data transmission may include the AID of the receiver or transmitter, and the user field corresponding to the remaining resource units not used for data transmission may include a pre-configured empty STA ID.
[0135] For ease of explanation, frames or MAC frames may be used interchangeably with MPDUs in this specification.
[0136] When a wireless communication device communicates using multiple links, its communication efficiency can be improved. In this case, a link can be a physical path and can consist of a wireless medium that can be used to deliver MAC Service Data Units (MSDUs). For example, if the frequency band of one link is used by another wireless communication device, the wireless communication device can continue to communicate through the other link. In this way, the wireless communication device can usefully utilize multiple channels. Furthermore, when a wireless communication device performs communication simultaneously using multiple links, the total throughput can be increased. However, in existing wireless LANs, it is already stipulated that one wireless communication device uses one link. Therefore, a WLAN operation method using multiple links is needed. This will be discussed later. Figures 9 to 26 This describes a wireless communication method for wireless communication devices using multiple links. First, it will be discussed through... Figure 9 Describe the specific form of a wireless communication device that uses multiple links.
[0137] Figure 9 The illustration shows a multi-link device according to an embodiment of the present disclosure.
[0138] A multi-link device (MLD) can be defined for wireless communication methods using the aforementioned multiple links. A multi-link device can represent a device with one or more affiliated stations. According to a specific embodiment, a multi-link device can represent a device with two or more affiliated stations. Additionally, a multi-link device can exchange multi-link elements. Multi-link elements include information about one or more stations or one or more links. Multi-link elements may include multi-link configuration elements, which will be described later. In this case, the multi-link device can be a logical entity. Specifically, a multi-link device can have multiple affiliated stations. A multi-link device can be referred to as a multi-link logical entity (MLLE) or a multi-link entity (MLE). A multi-link device can have a Media Access Control (MAC) Service Access Point (SAP) up to the Logical Link Control (LLC). An MLD can also have a MAC data service.
[0139] Multiple stations included in a multi-link device can operate on multiple links. Furthermore, multiple stations included in a multi-link device can operate on multiple channels. Specifically, multiple stations included in a multi-link device can operate on multiple different links or multiple different channels. For example, multiple stations included in a multi-link device can operate on multiple different channels at 2.4 GHz, 5 GHz, and 6 GHz.
[0140] The operation of a multi-link device can be referred to as multi-link operation, MLD operation, or multi-band operation. Additionally, when the station attached to the multi-link device is an Access Point (AP), the multi-link device can be called an AP MLD. Furthermore, when the station attached to the multi-link device is a non-AP station, the multi-link device can be called a non-AP MLD.
[0141] Figure 9 The diagram illustrates the operation of communication between non-AP MLD and AP-MLD. Specifically, non-AP MLD and AP-MLD communicate using three links respectively. 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). AP1 and the first non-AP STA (non-AP STA1) communicate via the first link, Link1. The second AP AP2 and the second non-AP STA (non-AP STA2) communicate via the second link, Link2. The third AP AP3 and the third non-AP STA (non-AP STA3) communicate via the third link, Link3.
[0142] Multilink operation may include multilink setup operations. Multilink setup may correspond to the associated operations of the single-link operation described above, and may be performed first in a multilink setup for frame switching. The multilink device can obtain the information required for multilink setup from the multilink setup element. Specifically, the multilink setup element may include capability information associated with the multilink. In this case, the capability information may include information indicating whether any one of the multiple devices included in the multilink device performs a transmission and while another device can perform a reception. Additionally, the capability information may include information about the links available for each station included in the MLD. Furthermore, the capability information may include information about the channels available for each station included in the MLD.
[0143] Multi-link configuration can be set up through negotiation between peer stations. Specifically, multi-link configuration can be performed through communication between stations without communicating with the AP. Alternatively, multi-link configuration can be performed using any single link. For example, even if multiple links are configured from the first to the third link, the multi-link configuration can still be performed using the first link.
[0144] Additionally, a mapping between Service Identifiers (TIDs) and links can be configured. Specifically, frames corresponding to a specific TID value can be interchanged only through pre-specified links. The mapping between TIDs and links can be set based on direction. For example, when multiple links are configured between a first multi-link device and a second multi-link device, the first multi-link device can be configured to send frames with the first TID to multiple first links, while the second multi-link device can be configured to send frames with the second TID to the first links. Furthermore, default settings for the mapping between TIDs and links can exist. Specifically, in a multi-link configuration without additional settings, the multi-link devices can exchange frames corresponding to the TID at each link according to the default settings. In this case, the default setting could be to exchange all TIDs on any one link.
[0145] TIDs will be described in detail. A TID is an ID used to classify services and data to support Quality of Service (QoS). Additionally, TIDs can be used or assigned at layers higher than the MAC layer. Furthermore, a TID can indicate a Service Class (TC) or Service Flow (TS). Moreover, TIDs can be classified into 16 types. For example, a TID can be specified as one of the values in the range of 0 to 15. The TID value to be used can be specified differently depending on the access policy and channel access or media access method. For example, in the case of using Enhanced Distributed Channel Access (EDCA) or Hybrid Coordination Function Contention-Based Channel Access (HCAF), a value in the range of 0 to 7 can be assigned to the TID. In the case of using EDCA, a TID can indicate User Priority (UP). In this example, UP can be specified based on TC or TS. UPs can be assigned at layers higher than the MAC layer. Additionally, in the case of using HCF Controlled Channel Access (HCCA) or SPCA, a value in the range of 8 to 15 can be assigned to the TID. In the case of using HCCA or SPCA, a TID can indicate a TSID. Additionally, when using HEMM or SEMM, a value in the range of 8 to 15 can be assigned to TID. When using HEMM or SEMM, TID can also indicate TSID.
[0146] UP and AC can be mapped. AC can be a label used to provide QoS in EDCA. AC can also be a label used to indicate a set of EDCA parameters. EDCA parameters or a set of EDCA parameters can be parameters used for EDCA channel contention. QoS stations can use AC to guarantee QoS. Additionally, AC can include AC_BK, AC_BE, AC_VI, and AC_VO. AC_BK, AC_BE, AC_VI, and AC_VO can respectively indicate background, best-effort, video, and voice. Furthermore, each of AC_BK, AC_BE, AC_VI, and AC_VO can be classified as a subordinate AC. For example, AC_VI can be subdivided into AC_VI primary and AC_VI standby. Similarly, AC_VO can be subdivided into AC_VO primary and AC_VO standby. Additionally, UP or TID can be mapped to AC. For example, UP or TID with values 1, 2, 0, 3, 4, 5, 6, and 7 can be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI, AC_VI, AC_VO, and AC_VO, respectively. Additionally, UP or TID values 1, 2, 0, 3, 4, 5, 6, and 7 can be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI (standby), AC_VI (primary), AC_VO (primary), and AC_VO (standby), respectively. Furthermore, UP or TID values 1, 2, 0, 3, 4, 5, 6, and 7 can sequentially have high priority. That is, 1 represents low priority, and 7 represents high priority. Therefore, AC_BK, AC_BE, AC_VI, and AC_VO can sequentially have high priority. Additionally, AC_BK, AC_BE, AC_VI, and AC_VO can correspond to AC indices (ACI) 0, 1, 2, and 3, respectively. Due to these characteristics of TIDs, the mapping between TIDs and links can indicate the mapping between ACs and links. Furthermore, the mapping between links and ACs can indicate the mapping between TIDs and links.
[0147] As described above, a TID can be mapped to each of multiple links. The mapping can specify the links capable of exchanging services corresponding to a predetermined TID or AC. Additionally, it can specify the TIDs or ACs that can be sent for each transmission direction within the link. As mentioned above, a default configuration for mapping between TIDs and links can exist. Specifically, in the absence of additional configuration for a multi-link configuration, the multi-link device can exchange frames corresponding to TIDs on each link according to the default configuration. In this example, the default configuration can exchange all TIDs on any one link. Any TID or AC at any given time can always be mapped to at least one link. Management and control frames can be sent on all links.
[0148] When a link is mapped to a TID or AC, only data frames corresponding to the TID or AC mapped to that link can be sent on that link. Therefore, when a link is mapped to a TID or AC, frames that do not correspond to the TID or AC mapped to that link cannot be sent on that link. When a link is mapped to a TID or AC, ACKs can also be sent based on the link to which the TID or AC is mapped. For example, a block ACK protocol can be determined based on the mapping between the TID and the link. According to another embodiment, the mapping between the TID and the link can be determined based on the block ACK protocol. In particular, a block ACK protocol can be set for TIDs mapped to predetermined links.
[0149] QoS can be guaranteed through the mapping between TIDs and links described above. Specifically, high-priority ACs or TIDs can be mapped to links with relatively few station operations or links with good channel conditions. In addition, the mapping between TIDs and links described above allows stations to maintain a power-saving state over long periods of time.
[0150] Figure 10 The illustration shows the simultaneous execution of transmissions on different links in a multi-link operation according to an embodiment of the present disclosure.
[0151] Depending on the implementation of a multi-link device, simultaneous operation may not be supported across multiple links. For example, simultaneous transmission, simultaneous reception, or transmission in one link and reception in another may not be supported. This is because reception or transmission performed in one link may affect reception or transmission performed in another link. Specifically, transmission in one link may act as interference to another link. Interference imposed by a multi-link device from one link to another can be termed internal leakage. Internal leakage can become significant as the frequency spacing between links decreases. When internal leakage is not very large, transmission can be performed in one link while transmission in another link is performed. When internal leakage is large, transmission cannot be performed in one link while transmission in another link is performed. As mentioned above, simultaneous operation by a multi-link device across multiple links can be termed simultaneous transmission and reception (STR). For example, simultaneous transmission, simultaneous transmission in one link and reception in another link, or simultaneous reception in multiple links by a multi-link device can be termed STR.
[0152] As described above, a multilink device may support STR (Signal Execution) or only support STR in a limited way. Specifically, a multilink device supports STR under certain conditions. For example, when the multilink device operates as a single radio device, it may not perform STR. Furthermore, when the multilink device operates as a single antenna, it may not perform STR. A multilink device may also not perform STR when an internal leakage of a size greater than or equal to a predetermined size is detected.
[0153] A station can exchange information with another station regarding its STR capabilities. Specifically, the station can exchange information with another station regarding whether to restrict the ability to perform simultaneous transmission or reception on multiple links. Specifically, the information regarding whether to restrict the ability to perform transmission or reception on multiple links can indicate whether simultaneous transmission, simultaneous reception, or simultaneous transmission and reception on multiple links is possible. The information regarding whether to restrict the ability to perform transmission or reception on multiple links can be information indicating a step representing the magnitude of internal leakage. In a detailed embodiment, the information indicating a step representing the magnitude of internal leakage can be information indicating a step representing the magnitude of interference caused by internal leakage. In another detailed embodiment, this information can be information indicating a step representing the frequency spacing between links that may affect internal leakage. The information indicating a step representing the magnitude of internal leakage can be information indicating the relationship between the frequency spacing between links and the magnitude of internal leakage.
[0154] exist Figure 10 In this setup, the first station (STA1) and the second station (STA2) are attached to a non-AP multi-link device. The first AP (AP1) and the second AP (AP2) can also be attached to a non-AP multi-link device. A first link (link1) is configured between the first AP (AP1) and the first station (STA1), and a second link (link2) is configured between the second AP (AP2) and the second station (STA2). Figure 10In a multi-link system, non-AP devices can perform STR (Transmission Streaming) with limitations. When the second station (STA2) performs a transmission in the second link (link2), the reception of the first station (STA1) in the first link (link1) may be interfered with by the transmission performed in the second link (link2). For example, the reception of the first station (STA1) in the first link (link1) may be interrupted by the transmission performed in the second link (link2) in the following situations: The second station (STA2) sends first data (data1) in the second link (link2), and the first AP (AP1) sends a response (ack) to the first station (STA1) for the first data (data1). The second station (STA2) sends second data (data2) in the second link (link2). Simultaneously, the transmission time of the second data (data2) may overlap with the transmission time of the response (ack) to the first data (data1). The first link (link1) may be interfered with by the transmission from the second link (link1) to the second station (STA2). Therefore, the first station (STA1) may not have received a response (ack for data1) to the first data (data1).
[0155] This describes the operation of channel access performed by multi-link devices. For multi-link operations not described in detail, please refer to the reference. Figure 6 The described channel access.
[0156] A multi-link device can independently perform channel access on multiple links. In this case, channel access can be backoff-based. When the multi-link device independently performs channel access on multiple links and the backoff counters on multiple links reach 0, the multi-link device can simultaneously perform transmission on multiple links. In a detailed embodiment, when one of the backoff counters on multiple links reaches 0 and a predetermined condition is met, the multi-link device can perform channel access not only on the link where the backoff counter reaches 0, but also on another link where the backoff counter has not reached 0. Specifically, when one of the backoff counters on multiple links reaches 0, the multi-link device can detect energy on another link where the backoff counter has not reached 0. At this time, when no energy of a predetermined size or larger is detected, the multi-link device can perform channel access not only on the link where the backoff counter reaches 0, but also on the link where energy is detected. Accordingly, the multi-link device can simultaneously perform transmission on multiple links. The threshold for energy detection can be smaller than the threshold for determining whether to decrease the backoff counter. Furthermore, when determining whether to decrease the backoff counter, the multi-link device can detect any type of signal, including WLAN signals. In energy detection, multi-link devices can detect any type of signal, including WLAN signals. WLAN signals may not detect internal leakage. In this case, the multi-link device can sense signals detected due to internal leakage through energy detection. Furthermore, as mentioned above, the threshold used for energy detection can be smaller than the threshold used to determine whether to decrease the backoff counter. Accordingly, even while transmission is performed in one link, the multi-link device can decrease the backoff counter in another link.
[0157] Based on the level of interference between the links used by the multi-link device, the multi-link device can determine whether a station operating in each link can operate independently. In this case, the level of interference between links can be the magnitude of interference detected by another station of the multi-link device when one station performs a transmission in one link. When a transmission performed by the first station of the multi-link device in the first link introduces interference of a predetermined or greater magnitude to the second station of the multi-link device operating in the second link, the operation of the second station may be restricted. Specifically, the second station's reception or channel access may be restricted. This is because, when interference occurs, the second station may be unable to decode the received signal due to the interference. Furthermore, this is because, when interference occurs, if the second station uses backoff to perform channel access, it may determine that the channel is being used.
[0158] When a transmission by the first station of a multi-link device in the first link introduces interference of less than a predetermined size to the second station of the multi-link device operating in the second link, the first and second stations can operate independently. Specifically, when a transmission by the first station of a multi-link device in the first link introduces interference of less than a predetermined size to the second station of the multi-link device operating in the second link, both the first and second stations can independently perform channel access. Furthermore, when a transmission by the first station of a multi-link device introduces interference of less than a predetermined size to the second station of the multi-link device operating in the second link, both the first and second stations can independently perform transmission or reception. This is because when interference of less than a predetermined size is generated, the second station can successfully decode the received signal even if the interference exists. Moreover, this is because when interference of less than a predetermined size is generated, when the second station uses backoff to perform channel access, the second station can determine that the channel is idle.
[0159] The level of interference generated between stations in a multi-link device can vary depending on the hardware characteristics of the multi-link device and the spacing between the frequency bands of the links in which these stations operate. For example, the internal interference generated in a multi-link device that includes expensive radio frequency (RF) components may be less than the internal interference generated in a multi-link device that includes inexpensive RF components. Accordingly, the level of interference generated between stations in a multi-link device can be determined based on the characteristics of the multi-link device.
[0160] Figure 10 The diagram illustrates how the magnitude of the generated interference varies depending on the spacing between the link's frequency bands and the characteristics of the multi-link devices. Figure 10In one embodiment, the first multi-link device (MLD#1) includes a first station (STA1-1) operating in a first link (link1) and a second station (STA1-2) operating in a second link (link2). The second multi-link device (MLD#2) includes a first station (STA2-1) operating in the first link (link1) and a second station (STA2-2) operating in the second link (link2). The frequency spacing between the first link (link1) and the second link (link2) operated by the first multi-link device (MLD#1) is the same as the frequency spacing between the first link (link1) and the second link (link2) operated by the second multi-link device (MLD#2). However, due to the differences between the characteristics of the first multi-link device (MLD#1) and the second multi-link device (MLD#2), the magnitude of the generated interference may differ. Specifically, the magnitude of the interference generated in the first multi-link device (MLD#1) may be greater than the magnitude of the interference generated in the second multi-link device (MLD#2). As mentioned above, the magnitude of the generated interference can vary depending on the characteristics of the multi-link devices, and when it is assumed that STR is supported on a different basis for each multi-link device, it may be necessary to exchange information about whether STR is supported.
[0161] Multilink devices can signal whether a STR is supported by a station included in the multilink device. Specifically, AP multilink devices and non-AP multilink devices can exchange information about whether a STR is supported by an AP included in the AP multilink device and whether a STR is supported by a STA included in the non-AP multilink device. In such embodiments, an element indicating whether a STR is supported can be used. This element indicating whether a STR is supported can be called an STR support element. The STR support element can indicate whether a STR is supported by a station of the multilink device that sent the STR support element using 1 bit. Specifically, the STR support element can indicate whether a STR is supported by each station included in the multilink device that sent the STR support element using 1 bit. In this case, the value of this bit can be 1 when the station supports the STR, and the value of this bit can be 0 when the station does not support the STR. When the multilink device sending the STR support element includes a first station (STA1), a second station (STA2), and a third station (STA3), where the first station (STA1) and the third station (STA3) support the STR, and the second station (STA2) does not support the STR, the STR support element can include a field with 1011 bits. Assuming stations operating in different frequency bands support STR, the STR support element can omit signaling indicating whether STR is supported between stations operating in different frequency bands. For example, station 1 (STA1) operates on a first link at 2.4 GHz, while station 2 (STA2) and station 3 (STA3) operate on a second and third link at 5 GHz, respectively. The STR support element can indicate STR support between station 2 (STA2) and station 3 (STA3) using 1 bit. Furthermore, when the number of stations signaled by the STR support element is 2, the STR support element can include only 1 bit.
[0162] In a detailed embodiment, the relationship between a link in the 2.4 GHz region and a link in the 5 GHz or 6 GHz region of a multi-link device can always be defined as a STR. Accordingly, the signaling for the STRs of the links in the 2.4 GHz region and the links in the 5 GHz or 6 GHz region can be omitted.
[0163] Figure 11 The illustration shows the operation of a multi-link device according to an embodiment of the present disclosure when a link changes.
[0164] When the link's frequency band changes, the STR support element can be changed. As mentioned above, this is because whether an STR is supported by a station can vary depending on the distance between the link's frequency bands, and when the link's frequency band changes, whether the STR is supported by a station can change. Changing the link's frequency band can include at least one of a change in the center frequency, a change in the frequency band bandwidth, and a 200MHz main channel. The AP and the station can exchange STR support elements through requests and responses. In another detailed embodiment, when the link's frequency band changes, the STR support element can be exchanged without any separate request. Furthermore, in the above embodiments, changing the link's frequency band can include a change in the station's operating channel.
[0165] When a station on a non-AP multi-link device cannot perform STR (Single Link Execution), it can request the AP to change the link. Specifically, the station can request a change in at least one of the following: center frequency, bandwidth, and 20MHz main channel. The link change request can be sent to the AP through the link to which the change is requested. In another detailed embodiment, the link change request can be sent to the AP through a link that has not been requested to be changed. In this case, the link change request can include information indicating the link to be changed. The information indicating the link can be a link number used to identify the link. In such an embodiment, the link change can be a change of the operating channel within a frequency band. Furthermore, the link change can include information about the method of changing the link. Specifically, the link change request can indicate whether to move the link's center frequency to a frequency higher than the current center frequency or to a frequency lower than the current center frequency. In another detailed embodiment, the link change request can implicitly indicate a change to a frequency band far from adjacent links. Furthermore, the link change request can indicate a reduction in bandwidth. The link change request can also be a request to change the location of the main channel. Specifically, a link change request can indicate a change from the primary channel's location to a channel in a lower frequency band or a channel in a higher frequency band than the primary channel's location. The AP receiving the link change request can modify the link accordingly. Furthermore, in a detailed embodiment, the AP receiving the link change request can ignore the link change request.
[0166] exist Figure 11In one embodiment, the second station (STA2) and the third station (STA3) of the non-AP multi-link device do not support STR. The non-AP multi-link device sends a request to the AP multi-link device to change the third link (link3). Upon receiving the link change request, the AP multi-link device changes the operating link of the third AP (AP3). At this time, the third station (STA3) operating in the third link (link3) to be changed can send a change request to the third AP (AP3). In another detailed embodiment, a station not operating in the third link (link3) can send a change request to an AP not operating in the third link (link3).
[0167] When an Access Point (AP) changes a link, it can broadcast information about the link change via a beacon frame. This information may include details about the link frequency, which could include at least one change in operating bandwidth or the primary channel. Furthermore, the information may include details about the timing of the link change. The link change can be completed by sending a beacon containing this information.
[0168] exist Figure 11 In this process, the link operated by the third station (STA3) is changed, and thus the third station (STA3) and the second station (STA2) can support STR. As described above, non-AP multilink devices can send STR support elements to AP multilink devices and signal information indicating the change in STR support.
[0169] Link changes can be disallowed, or STR can be supported without link changes. For example... Figure 11 As shown in the embodiments, AP multilink devices can support STR, but non-AP multilink devices may not. This is because it is common to use relatively expensive equipment for AP multilink devices and relatively inexpensive equipment for non-AP multilink devices. Accordingly, in communication between multilink devices, even when one multilink device does not support STR, an efficient communication method is still required. In this case, STR can indicate simultaneous transmission and reception. This will refer to... Figure 12 To describe.
[0170] Figure 12 The illustration shows a method for restricting channel access for another station of a non-STR multilink device when one station of the non-STR multilink device is receiving data, according to an embodiment of the present disclosure.
[0171] When a non-STR multi-link device performs transmission in one link and reception in another, both reception and transmission of the non-STR multi-link device may fail. To address this issue, when a non-STR multi-link device performs reception in one link, channel access for that non-STR multi-link device in the other link can be restricted. Specifically, when a non-STR multi-link device performs reception in one link, backoff of channel access for that non-STR multi-link device in the other link can be restricted. Correspondingly, when a non-STR multi-link device performs reception in one link, initiation of transmission in the other link by the non-STR multi-link device can be prevented. In a detailed embodiment, backoff of channel access for the non-STR multi-link device in the other link can be restricted when reception of the non-STR multi-link device begins in one link. This can be configured via specific bits of memory, such as a channel access restriction flag. Whether channel access is restricted can be shared within the memory of the multi-link device. Through such an embodiment, channel access restriction can be implemented without separate frame switching. For ease of description, channel access restriction as used herein indicates restrictions on channel access or transmission to protect the transmission or reception of non-STR multi-link devices, unless otherwise described separately.
[0172] When channel access is restricted, a station operating on a link with restricted channel access cannot perform a backoff procedure, regardless of the NAV and CCA results. Furthermore, when channel access is restricted, a station operating on a link with restricted channel access cannot perform transmissions, regardless of the NAV and CCA results. However, even with restricted channel access, a station operating on a link with restricted channel access can still perform reception. Additionally, the channel access restriction in the second link caused by reception performed in the first link can be released based on the time point at which reception in the first link is completed. Specifically, when reception in the first link is completed, the channel access restriction in the second link caused by reception performed in the first link can be released. In another detailed embodiment, the channel access restriction in the second link caused by reception performed in the first link can be released based on the time point at which an ACK is sent after reception in the first link is completed. Specifically, the channel access restriction in the second link caused by reception performed in the first link can be released at the time point at which an ACK is sent after reception in the first link is completed. In another detailed embodiment, the channel access restriction in the second link caused by the reception performed in the first link can be released at the time point after the ACK transmission is completed following the completion of reception in the first link. Furthermore, after releasing the channel access restriction, the station can immediately decrement the backoff counter without additional sensing. In this case, additional sensing can indicate sensing performed during the DCF inter-frame interval (DIFS). In another detailed embodiment, the station can immediately decrement the backoff counter without additional sensing when the channel is idle for exactly a predetermined time before releasing the channel access restriction. In this case, the predetermined time can be one of the PCF inter-frame interval (PIFS), short inter-frame interval (SIFS), and arbitration inter-frame interval (AIFS).
[0173] exist Figure 12 In this embodiment, the non-STR multilink device includes a first station (STA1) operating in a first link (link1) and a second station (STA2) operating in a second link (link2). When the first station (STA1) performs reception and the second station (STA2) performs transmission in the second link (link2), intra-device interference is generated. As described above, when the first station (STA1) operating in the first link (link1) performs reception, the channel access of the second station (STA2) operating in the second link (link2) is restricted. After the first station (STA1) completes reception in the first link (link1), the channel access restriction is released. Immediately after releasing the channel access restriction, the second station (STA2) can decrease the value of its previous backoff counter from 3 to 2 without additional sensing.
[0174] For ease of expression, Figure 12The accompanying figures use a single block (solid Tx line, dashed Rx line) to represent Rx and Tx, and it can be understood that this single block represents operations including Tx / Ack reception and Rx / Ack transmission, even if a separate Ack block is not shown. This can be applied equivalently to the following figures.
[0175] When a station identifies a received PPDU as not being received by its intended receiver, it may stop receiving the PPDU. In this case, it is problematic for a multi-link device to release the channel access ban. The intended receiver in this specification has the same meaning as the destination station.
[0176] Figure 13 The illustration depicts an operation according to an embodiment of the present disclosure to release channel access prohibition when it is determined that the intended receiver of a PDDU received by a station of a non-STR multilink device is not that station.
[0177] When a station identifies that a received PPDU is not the intended receiver for that station, the station can release the channel access prohibition. The station can determine whether it is the intended receiver for the PPDU based on the receiver address information in the signaling field indicating the PPDU. In this case, the receiver address information in the signaling field indicating the PPDU can be the value of the STA-ID field of the EHT-SIG field. Specifically, the station can determine whether the STA-ID field of the EHT-SIG field indicates the station. Furthermore, the station can determine whether it is the intended receiver for the PPDU based on the value of the RA field of the MAC frame included in the PPDU. Specifically, the station can determine whether the RA field of the MAC frame included in the PPDU indicates the station. Figure 13 In this non-STR multi-link setup, there is a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The first station (STA1) receives PPDUs. The first station (STA1) determines that the intended receiver of the received PPDU is not the first station (STA1) and stops receiving PPDUs. At this point, the first station (STA1) can release the channel access restriction of the second station (STA2). Even if the channel access restriction of the second station (STA2) is released, channel access of the second station (STA2) can be delayed according to the NAV configured in the second station (STA2).
[0178] like Figure 13As shown, even after the channel access ban is lifted, stations included in non-STR multilink devices may experience fewer channel access opportunities than stations not included in multilink devices or stations included in STR multilink devices. Therefore, to ensure fair competition with other stations, methods may be needed to guarantee channel access opportunities for stations included in non-STR multilink devices. For example, after lifting the channel access ban, stations whose channel access was previously banned could be allowed to decrease their backoff counter by 2 or more. This will refer to... Figure 14 describe.
[0179] Figure 14 The illustration shows a station performing channel access after releasing a channel access ban, according to an embodiment of the present disclosure.
[0180] After releasing a channel access ban, the station that released the ban can decrease its backoff counter by 2 or more. This is to balance channel access opportunities with other stations, as other stations perform backoff procedures when the station's channel access is banned.
[0181] In another detailed embodiment, a station whose channel access is prohibited can perform a channel access procedure that reduces the CCA (CSMA) and backoff counter when channel access is prohibited. Figure 14 In this context, non-STR multi-link devices include a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). Figure 14 In this scenario, when the first station (STA1) is receiving data, channel access for the second station (STA2) is prohibited. Figure 14 In (a), when channel access for the second station (STA2) is prohibited, the second station (STA2) can perform a channel access procedure that reduces the CCA (CSMA) and backoff counter. Figure 14 In (a), since the channel of the second link (link2) is idle when the channel access of the second station (STA2) is prohibited, the second station (STA2) decreases the backoff counter.
[0182] Furthermore, even when channel access is prohibited, and the backoff counter reaches 0, a station whose channel access is prohibited can delay transmission without initiating transmission. In this case, the station can maintain the backoff counter value at 0. Additionally, although the station delays transmission, it can maintain the CW value. Therefore, this can be distinguished from a situation where the station doubles the CW value due to a busy channel. This is because the reason for the delayed transmission is not a situation where it is certain that the channel is being used. Figure 14 In (b), when channel access of the second station (STA2) is prohibited, the second station (STA2) can perform a channel access procedure that reduces the CCA (CSMA) and backoff counter. Figure 14In (b), since the channel of the second link (link2) is idle when the channel access of the second station (STA2) is prohibited, the second station (STA2) decreases its backoff counter. When the channel access of the second station (STA2) is prohibited, the backoff counter of the second station (STA2) reaches 0. The second station (STA2) delays transmission and begins transmission after the channel access prohibition is released.
[0183] As described above, channel access prohibition can include prohibiting the transmission of the second station when the first station of a non-STR multi-link device is performing a transmission. Furthermore, channel access prohibition can include prohibiting the transmission of the second station when the first station of a non-STR multi-link device is performing a reception.
[0184] When in Figure 14 In the embodiment of (b), when there are multiple stations with blocked channel access, the probability of attempting to simultaneously release the blocked channel access for multiple stations and the simultaneous transmission of multiple stations is high. Therefore, a method to reduce the probability of transmission collisions is needed. This will refer to... Figure 15 Describe it.
[0185] Figure 15 The illustration shows the operation of a station performing transmission after releasing channel access prohibition according to an embodiment of the present disclosure.
[0186] As described above, transmission is performed on the first link among multiple links operated by a non-STR multi-link device, therefore transmission can be prohibited on the second link. When the corresponding transmission is completed on the first link, transmission on the second link can begin via RTS / CTS frame exchange. Therefore, when transmission is performed on the first link among multiple links operated by a non-STR multi-link device, the non-STR multi-link device can begin RTS / CTS frame exchange on the second link. After releasing the channel access prohibition of a station whose transmission has been delayed due to channel access prohibition, the station can begin request-to-transmit (RTS) / clear-to-transmit (CTS) frame exchange before starting the delayed transmission. At this time, if the station does not receive a CTS frame, the delayed transmission may not begin. Figure 15 In embodiment (a), the station whose transmission is delayed due to channel access prohibition sends an RTS frame before starting the delayed transmission. The station starts the delayed transmission after receiving a CTS frame in response to the RTS frame.
[0187] In another detailed embodiment, after releasing the channel access ban of a station whose transmission was delayed due to the channel access ban, the station can send a frame that includes only some delayed transmission. At this time, after receiving a response (e.g., ACK) to the frame that includes only some delayed transmission, the station can send the portion of the delayed transmission that has not yet been sent. When the station does not receive a response to the frame that includes only some delayed transmission, the station may not send the portion of the delayed transmission that has not yet been sent. As mentioned above, after the channel access ban is released, the station begins RTS / CTS switching or sends only some delayed transmission because the probability of collisions in transmissions after the channel access ban may be higher than the probability of collisions in normal transmissions. Therefore, the above embodiments can be enforced for transmissions performed after the channel access ban is released. In conventional WLAN operation, RTS / CTS frames are used to address the hidden node problem and can be used based on the size of the transmitted data. In the above embodiments, RTS / CTS frames are used to prevent transmission collisions with stations performing delayed transmissions in order to protect the transmission or reception of non-STR multilink devices.
[0188] As described above, when one station of a non-STR multi-link device performs reception, the transmission of another station of the same device may be restricted. Furthermore, when one station of a non-STR multi-link device performs transmission, it may be difficult to accurately sense the channel state of the link operated by the other station. Specifically, when the first station of a non-STR multi-link device performs transmission, the second station can determine that the channel state of the link in which the second station operates is always busy. Therefore, even if the channel of the link in which the second station operates is idle, the second station may determine that the channel is busy due to internal interference. As described above, when a station cannot determine its channel state due to internal interference, or when one station of a non-STR multi-link device continuously performs transmission, the other station of the non-STR multi-link device is in a blind state. Due to the above situations, a station in a blind state may find it difficult to attempt transmission through a backoff process. Furthermore, due to the above situations, a station in a blind state may find it difficult to begin receiving PPDUs or to successfully decode them. Therefore, a method is needed that takes into account transmission performed when a station is in a blind state. This will refer to... Figure 16 Describe it.
[0189] Figure 16 The illustration shows a transmission performed based on the status of a station within a non-STR multilink device according to an embodiment of the present disclosure.
[0190] A station intending to perform a transmission to a non-STR multilink device can determine whether to perform the transmission based on whether the non-STR multilink device is in a blind state. In this case, the station intending to perform the transmission to the non-STR multilink device can be a station included in an STR multilink device. Furthermore, the station intending to perform the transmission to the non-STR multilink device can be an AP included in an AP multilink device, and the non-STR multilink device can be a non-AP multilink device. The station intending to perform the transmission to the non-STR multilink device can determine whether the non-STR multilink device is in a blind state based on the following description: The station intending to perform the transmission can determine whether another station in the multilink device that includes it is currently performing a transmission to the corresponding non-STR multilink device. When another station in the multilink device that includes it is currently performing a reception from the corresponding non-STR multilink device, the station can determine that the non-STR multilink device to which it is receiving the transmission is in a blind state. Figure 16 In one embodiment, the STR AP multi-link device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multi-link device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The second station (STA2) is performing a transmission to the second AP (AP2). Therefore, the second AP (AP2) can notify the first AP (AP1) that it is receiving data from the second station (STA2). Specifically, the second AP (AP2) can notify the first AP (AP1) that the transmission entity to the second AP (AP2) is the second station (STA2). In another detailed embodiment, the second AP (AP2) can notify the first AP (AP1) that the second station (STA2) is currently performing a transmission. In this case, the first AP (AP1) can determine that the first station (STA1) is in a blind state based on this notification.
[0191] This station can choose not to perform a transmission to a station in a blind state. This is because even if a transmission is performed to a station in a blind state, the station in a blind state may not be able to start receiving or may not be able to decode the PPDU. In this case, the station can cancel the transmission to the station in a blind state and perform a transmission to another station.
[0192] When an STR multi-link device performs a transmission to a non-STR multi-link device, the STR multi-link device can perform the transmission to the non-STR multi-link device in multiple links. Specifically, when an STR multi-link device performs a transmission to a non-STR multi-link device in the first link, the STR multi-link device can begin a transmission to the non-STR multi-link device in the second link. At this time, the STR multi-link device can determine the length of the transmission performed in the second link based on the transmission corresponding to the transmission to the non-STR multi-link device. Specifically, the STR multi-link device can determine the length of the transmission to the non-STR multi-link device in the second link based on the length of the transmission to the non-STR multi-link device in the first link. In a detailed embodiment, the STR multi-link device can simultaneously terminate the transmission in the first link and the transmission in the second link. This is to prevent the transmission to another station of the non-STR multi-link device from starting after one of the stations of the non-STR multi-link device has finished transmitting first and then sends a response (e.g., ACK). Through the above embodiments, multiple stations of the non-STR multi-link device can simultaneously send responses to the transmission to multiple stations.
[0193] STR multilink devices cannot determine the status of stations included in non-STR multilink devices in real time. Therefore, even if the STR multilink device determines the status based on a reference... Figure 16 The described embodiments may also cause interference or transmission conflicts between links in which non-STR multilink devices operate. For example, in Figure 16 In one embodiment, the first AP (AP1) may begin a transmission to the first station (STA1) before recognizing that the second station (STA2) is performing a transmission to the second AP (AP2). As mentioned above, the probability of inter-link interference or collision may be higher than the probability of intra-link interference or transmission collision. This will refer to... Figure 17 To describe in more detail.
[0194] Figure 17 The diagram illustrates situations that can cause inter-link interference or collisions.
[0195] When transmissions from the second station of a non-STR multi-link device to the second AP of a STR AP multi-link device and from the first AP of a STR AP multi-link device to the first station of a non-STR multi-link device begin simultaneously, transmission conflicts may occur between the links. Figure 17 (a) illustrates this situation. This is because, as mentioned above, STR multilink devices cannot determine the status of stations included in non-STR multilink devices in real time.
[0196] Furthermore, even if a transmission from the second station of a non-STR multilink device to the second AP of a STR AP multilink device starts earlier than a transmission from the first AP of a STR-AP multilink device to the first station of a non-STR multilink device, transmission conflicts may still occur between links. Figure 17 (b) illustrates this situation. This is because the second AP (AP2) needs time to notify the first AP (AP1) that the second station (STA2) is performing a transmission. As mentioned above, due to transmission conflicts between stations that start transmitting at different times, the probability of inter-link interference or transmission conflicts may be higher than the probability of intra-link interference or conflicts. Furthermore, the probability of inter-link interference or transmission conflicts may be even higher due to the delay in the time spent by the transmitter identifying the PPDU received by the AP of the STR multi-link device. Therefore, a method to address this problem is needed. When one station of the STR multi-link device performs reception, another station of the STR multi-link device may not perform channel access. However, when channel access is prohibited, the purpose of implementing the STR function may be lost. Therefore, an operational method other than prohibiting channel access of the STR multi-link device is needed. This will refer to... Figure 18 Describe it.
[0197] Figure 18 The illustration shows the operation of an STR multilink device stopping transmission to a non-STR multilink device according to an embodiment of the present disclosure.
[0198] When a station of an STR multi-link device determines that a station of a non-STR multi-link device is in a blind state during transmission to that station, the STR multi-link device can stop transmission to the blind station. Specifically, the STR multi-link device can determine whether a station of a non-STR multi-link device is in a blind state based on the value indicated by the STA (AID)-ID in the signaling field of the received PPDU or the Transmit Address (TA) field of the MAC frame included in the received PPDU. In this case, the STA-ID can be a value indicating the station that sent the UL PPDU. In a detailed embodiment, when the value indicated by the STA (AID)-ID in the signaling field of the received PPDU indicates a first station included in the non-STR multi-link device, the STR multi-link device can determine that a second station included in the non-STR multi-link device is in a blind state. Furthermore, when the TA field of the MAC frame included in the received PPDU indicates a first station included in the non-STR multi-link device, the STR multi-link device can determine that a second station included in the non-STR multi-link device is in a blind state. The operation after the station cancels the transmission will be described first.
[0199] When leaving a TXOP configured in a station of a non-STR multi-link device, a station that cancels a transmission to a station of a non-STR multi-link device can attempt a transmission to a different station. In this case, the station that cancels a transmission to a station of a non-STR multi-link device can perform a transmission to a different station without a separate backoff procedure. In a detailed embodiment, when an idle channel is detected during a predetermined time interval after canceling a transmission to a station of a non-STR multi-link device without a separate backoff procedure, the station that cancels a transmission to a station of a non-STR multi-link device can perform a transmission to a different station. In this case, the predetermined time interval can be one of SIFS, PDIF, and DIFS.
[0200] When a transmission is executed to a station different from the station of a non-STR multi-link device, the station that cancels the transmission to the non-STR multi-link device can send a service with a priority equal to or higher than the priority of the service whose transmission was canceled. This is because the transmission of services with a lower priority than the channel access used for the canceled transmission is unbalanced. In the above embodiment, the station of the STR multi-link device can be an AP.
[0201] A station that cancels a transmission to a non-STR multilink device can initialize its configured TXOP. Specifically, a station that cancels a transmission to a non-STR multilink device can send a CF-End frame after cancelling the transmission. This allows another station operating on the link in which the transmission was scheduled to use the link.
[0202] exist Figure 18 In this context, an STR AP multi-link device includes a first AP (AP1) operating on the first link (link1) and a second AP (AP2) operating on the second link (link2). A non-STR non-AP multi-link 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 station (STA2) is currently performing a transmission to the second AP (AP2). During a transmission 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) stops its transmission to the first station (STA1). Figure 18 In (a), after stopping the transmission to the first station (STA1), the first AP (AP1) performs a transmission to a station different from the first station (STA1), as described in the first described embodiment. Figure 18 In (b), after stopping the transmission to the first station (STA1), the first AP (AP1) sends a CF-END frame as described in the embodiments described later.
[0203] When a station stops transmitting, it can send the segment being transmitted and then choose not to send subsequent segments. In a detailed embodiment, the station can immediately stop transmitting the packet being sent.
[0204] In the above embodiments, when transmission to a station of a non-STR multilink device in a blind state is stopped and transmission to a station different from the non-STR multilink device's station is performed, the STR multilink device is required to notify the other station that transmission to the other station can be performed for stable reception. The method is described. For ease of description, a station different from the station of a non-STR multilink device in a blind state is referred to as a different station.
[0205] A station of an STR multilink device can insert the addresses of different stations into the MAC frame. Specifically, a station of an STR multilink device can insert the address of the expected receiver of the MAC frame into the receive address (RA) of the MAC frame, and insert the addresses of different stations into separate fields. In a detailed embodiment, the station of the device can insert the addresses of different stations into the EHT-SIG. Specifically, a station of an STR multilink device can insert the address of the expected receiver of the PPDU and the addresses of different stations into the user field of the signaling field of the PPDU. At this time, the addresses of different stations can be inserted after the address of the expected receiver of the PPDU in the user field of the signaling field of the PPDU.
[0206] In another detailed embodiment, the station can monitor the reception of the PPDU for a predetermined period of time after identifying that the expected receiver of the PPDU is not the station. Specifically, the station can monitor whether the PPDU reception continues for the predetermined time after identifying that the expected receiver of the received PPDU is not the station. Therefore, the station can determine whether to stop the transmission of the PPDU and start the transmission to the station. In this embodiment, when it is determined that the PPDU transmission has continued for the predetermined time, the station can enter a sleep state. When it is determined that the PPDU transmission has not continued for the predetermined time, the station can remain awake. At this time, when the station receives a new PPDU, the station can decode the PPDU.
[0207] In another detailed embodiment, the station sending the PPDU can insert a signal indicating that PPDU transmission can be stopped into the PPDU. This signal can be a 1-bit subfield. For example, when the value of this subfield is 1, the station receiving the PPDU can determine that PPDU transmission can be stopped before the time indicated by the length field of the PPDU's signaling field and the duration field of the MAC frame. When the station determines that PPDU transmission can be stopped before the time indicated by the length field of the PPDU's signaling field and the duration field of the MAC frame, the station can postpone entering a sleep state. Furthermore, the station sending the PPDU can insert the signal indicating that transmission can be stopped into a reserved field of the PPDU.
[0208] As mentioned above, unnecessary channel occupation can be prevented by canceling or stopping transmissions.
[0209] When transmission is stopped or delayed due to inter-link collisions, the CW value used for channel access can be doubled as in a normal transmission failure. However, when transmission is stopped or delayed due to inter-link collisions, the CW value used for channel access does not need to be doubled as in a normal transmission failure. That is, the station can maintain the CW value used for channel access. Doubling the CW value is intended to reduce the probability of transmission collisions by increasing the range of values that can be the backoff counter. This requirement may be lower when the station can clearly identify inter-link collisions. Furthermore, doubling the CW value when transmission is stopped or delayed due to inter-link collisions may cause transmission delays. However, when both inter-link and intra-link collisions occur simultaneously, the station needs to double the CW value. This will refer to... Figure 19 Describe it.
[0210] Figure 19 The illustration shows the processing of the CW value when the STR multilink device identifies a transmission conflict between links, according to an embodiment of the present disclosure.
[0211] As described in the embodiments, when a station cancels a transmission due to a transmission performed by a non-STR multilink device, the station can sense the channel state after the transmission is canceled. When the channel is sensed to be non-idle, the station can double the value of CW. In this case, the doubling can follow a reference... Figure 6The described embodiment. Furthermore, when an idle channel is sensed, the station can maintain the CW value. This embodiment is used because, even if an idle channel is sensed, the probability of transmission collisions within the link is still low, thus treating this situation differently from a successful transmission. In another detailed embodiment, when an idle channel is sensed, the station can configure the CW value to the minimum CW value (CW_min). This embodiment is used because, when an idle channel is sensed, the probability of transmission collisions within the link is low, thus treating this situation the same as a successful transmission. The station can apply the above embodiments to the CW of the AC of the service included in the canceled transmission.
[0212] Furthermore, when a transmission is cancelled according to the above embodiments, the station may not need to increment the retry counter. In this case, the retry counter may include at least one of a long retry counter and a short retry counter.
[0213] In this embodiment, canceling a transmission may include at least one of stopping the transmission or delaying the transmission before it begins.
[0214] When a station cancels a transmission after sending a CTS-to-Self frame before attempting to transmit, the station may not begin RTS / CTS frame switching after canceling the transmission but before attempting to transmit again. This is because NAV is configured via the CTS-to-Self frame. Furthermore, when a station leaves a TXOP when attempting to transmit again after canceling the transmission, the station can attempt to transmit without any backoff process.
[0215] exist Figure 19 In this context, an STR multi-link AP device includes a first AP (AP1) operating on the first link (link1) and a second AP (AP2) operating on the second link (link2). A non-STR multi-link 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 station (STA2) is currently performing a transmission to the second AP (AP2). During a transmission 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) stops transmitting to the first station (STA1). Figure 19 In (a), the first AP (AP1) determines that the channel of the first link (link1) is idle. At this point, since no TXOP is reserved, the first AP (AP1) accesses the channel through a backoff process. Figure 19 In (b), the first AP (AP1) determines that the channel of the first link (link1) is not idle. At this time, because TXOP is left, the first AP (AP1) attempts to transmit without a backoff process.
[0216] In the above embodiments, when the channel is detected to be idle during a predetermined time interval without a separate backoff process after a transmission to a station on a non-STR multi-link device is cancelled, the station that cancelled the transmission to the non-STR multi-link device may perform a transmission to a different station than the non-STR multi-link device station. In this case, the duration of the predetermined time interval may be problematic. The station receiving the PPDU whose transmission was cancelled may be unable to decode the PPDU. At this point, when the channel is sensed to be idle within the Extended Inter-Frame Spacing (EIFS), the station unable to decode the PPDU may initiate a backoff process. Therefore, whether to configure the predetermined time interval to be longer than or equal to the EIFS is a question. This will refer to... Figure 20 Describe it.
[0217] Figure 20 The illustration shows an STR multilink device according to an embodiment of the present disclosure performing channel access operation again after stopping transmission to a non-STR multilink device.
[0218] like Figure 20 As shown in (a), the predetermined time interval can be DIFS. This assumes that stations in an STR multi-link device acquire channel access opportunities through a contention process and lose those opportunities due to transmission conflicts between links. In other words, because stations in an STR multi-link device acquire channel access opportunities through a contention process, they are given a higher priority for performing channel access than other stations. When applying EDCA, AIFS[AC] can be used instead of DIFS.
[0219] In another detailed embodiment, the predetermined time interval can be as follows: Figure 20 The EIFS shown in (b) suggests that the STR multilink device can be considered to have exhausted its transmission opportunities and to take into account the balance with other stations.
[0220] In another detailed embodiment, such as Figure 20 As shown in (c), when a signal is sent indicating that transmission can be stopped in the signaling field of the PPDU, the predetermined time interval can be DIFS. Furthermore, when the station receiving the PPDU detects the cessation of PPDU transmission, the station can sense whether the channel is idle during DIFS instead of EIFS. In this case, if the channel is sensed to be idle during DIFS, the corresponding station can begin the backoff process. This embodiment improves the overall network performance and ensures balance between stations. When EDCA is applied, AIFS[AC] can be used instead of DIFS.
[0221] As described above, STR multilink devices can identify potential transmission collisions between links. Specifically, when the first station of an STR multilink device completes its backoff process, the second station may be receiving a PPDU. At this time, before the second station has completed decoding the signaling field of the PPDU, the first station can determine that a transmission collision between links cannot be identified but its possibility exists. In this case, the first station can insert information indicating that the transmission can be stopped into the sent PPDU, as described above. Furthermore, for stable and efficient transmission, NSTR multilink devices can send CTS-to-Self frames before transmitting to non-STR multilink devices. This will refer to... Figure 21 To describe.
[0222] Figure 21 The illustration shows the operation of an STR multilink device sending a CTS-to-Self frame before transmission to a non-STR multilink device according to an embodiment of the present disclosure.
[0223] A station in an STR multilink device can send a CTS-to-Self frame before transmitting to a non-STR multilink device. Specifically, when a second station in an STR multilink device attempts to transmit to a non-STR multilink device while receiving data at the first station, the second station can send a CTS-to-Self frame before the transmission. Therefore, the second station can ensure that TXOPs are used for transmissions to non-STR multilink devices. Furthermore, before performing a transmission to a non-STR multilink device, the second station can determine whether to perform a transmission from the corresponding non-STR multilink device to the first station. The second station can determine the destination station based on whether a transmission from the corresponding non-STR multilink device to the first station is performed. Specifically, when a transmission is not performed from the corresponding non-STR multilink device to the first station, the second station can perform a transmission to the corresponding non-STR multilink device. When a transmission is performed from the corresponding non-STR multilink device to the first station, the second station can perform a transmission to a station not included in the corresponding non-STR multilink device. For example, when the first station plans to transmit a SU-PPDU for a station that is not a non-STR multi-link device, a MU-PPDU including data for a station that is not a non-STR multi-link device, or a PPDU including a trigger frame for triggering transmission of a station that is not a non-STR multi-link device, the first station can cancel the planned transmission. In this case, the first station can attempt to transmit a SU-PPDU for a station that is not a non-STR multi-link device, a MU-PPDU that does not include data for a station that is not a non-STR multi-link device, or a PPDU including a trigger frame that does not trigger transmission of a station that is not a non-STR multi-link device. In this case, the first station can begin transmission after a time longer than SIFS from the start of the CTS-to-Self frame transmission. Specifically, the first station can begin transmission after PIFS from the start of the CTS-to-Self frame transmission. The station sending the CTS-to-Self frame should begin transmission after SIFS from the start of the CTS-to-Self frame transmission. When a planned transmission is canceled and a new transmission is attempted as described in the embodiment, the STR multi-link device needs processing time to generate the new MPDU to be transmitted. Therefore, exceptions can be applied to the rules regarding the time interval between CTS-to-self frames and transmissions. In this embodiment, the second station exceeds the TXOP acquired by the CTS-to-self, so in principle, transmission cannot be performed.
[0224] exist Figure 21In this STR multilink device, there is a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). Since the second AP (AP2) performs reception and the first AP (AP1) plans transmissions to stations not connected to the STR multilink device, the first AP (AP1) sends a CTS-to-Self frame before the planned transmission. As described above, the first AP (AP1) determines the destination station for the transmission based on the determination of the station sending the PPDU received by the second AP (AP2). Furthermore, the first AP (AP1) performs the transmission after a SIFS or PIFS following the transmission of the CTS-to-Self frame.
[0225] The second station can initiate the RTS / CTS frame exchange process by sending RTS frames instead of CTS-to-Self frames. Therefore, the second station can achieve an effect similar to CTS-to-Self frame transmission. In the case of RTS / CTS frame exchange, the second station can obtain TXOPs only if the destination station is not in a blind state.
[0226] Figure 22 The illustration depicts a transmission performed by multiple APs included in an STR multilink device to multiple stations included in a non-STR multilink device, according to an embodiment of the present disclosure.
[0227] Multiple stations included in a non-STR multilink device can perform reception simultaneously. This is because simultaneous reception by multiple stations may only cause minor interference. Figure 22 The illustration depicts simultaneous reception performed by multiple stations included in a non-STR multilink device. In this case, for stable operation of the non-STR multilink device, multiple APs included in the STR multilink device can perform multiple transmissions at their transmission ends synchronized with the multiple stations included in the non-STR multilink device. This will refer to... Figure 23 Describe it.
[0228] Figure 23 The illustration depicts multiple transmissions performed by multiple APs included in an STR multilink device to multiple stations included in a non-STR multilink device, according to an embodiment of the present disclosure, with their transmission ends synchronized.
[0229] When a multi-link device performs a transmission in one of the non-STR links, it can simplify the channel access procedure for the transmission performed in the other link. Specifically, when the first station of the multi-link device completes the backoff channel access procedure in the first link, if the channel is idle for a predetermined time interval within the link of the second station of the STR multi-link device, the second station of the STR multi-link device can begin the transmission in the second link.
[0230] In a detailed embodiment, when one station of an STR multilink device performs a transmission to a station of a non-STR multilink device, the channel access procedure for the other station of the STR multilink device can be simplified. Specifically, when the first station of the STR multilink device completes the backoff channel access procedure for a transmission to the first station of the non-STR multilink device, if the channel is idle during a predetermined time interval within the link of the second station of the STR multilink device, the second station of the STR multilink device can begin a transmission to the second station of the non-STR multilink device. In this case, the predetermined time interval can be PIFS. This operation can be applied when the first and second stations of the STR multilink device perform a transmission to a station included in a non-STR multilink device. In an embodiment, the first and second stations can begin transmission with a difference within the predetermined time interval. The predetermined time interval can be a time slot time.
[0231] Furthermore, when the first and second stations of an STR multilink device perform a transmission to a station included in a non-STR multilink device, the transmission ends of the first and second stations can be synchronized. In this case, the synchronization of the transmission ends of the first and second stations can indicate that the end of the first station and the end of the second station have a difference within a first predetermined time interval. The first predetermined time interval can indicate the interior of a time slot boundary or a symbol boundary.
[0232] Multiple stations of a non-STR multilink device receiving a synchronized transmission endpoint can simultaneously perform subsequent transmissions (e.g., responses). In this case, the response may include an ACK. In a conventional WLAN, subsequent transmissions are performed after the SIFS from the start of reception. However, for multiple transmissions ending with a small time difference, performing subsequent transmissions with a small time difference can be more complex than performing them simultaneously. Therefore, as described above, multiple stations of a non-STR multilink device receiving a synchronized transmission endpoint can simultaneously perform subsequent transmissions. In this case, the interval between at least one of the multiple transmissions synchronized with its transmission endpoint can be the sum of the SIFS and a predetermined time interval. Specifically, a transmission following the first ending transmission among the multiple transmissions synchronized with its transmission endpoint can be performed at an interval obtained by adding the SIFS to the time within the predetermined time interval from the start of transmission. In this case, the predetermined time interval can be either a slot time or a symbol length. Furthermore, the difference within the predetermined time interval can be the difference between the end of the last ending transmission among the multiple transmissions synchronized with its transmission endpoint and the first ending transmission among the multiple transmissions synchronized with its transmission endpoint.
[0233] In another detailed embodiment, when multiple transmissions end with a time difference within a first predetermined time interval, the multiple stations receiving the transmissions can perform synchronized subsequent transmissions. The multiple subsequent transmissions whose transmission ends are synchronized can indicate multiple subsequent transmissions performed with a time difference within a second predetermined time interval. Furthermore, the difference within the second predetermined time interval can be the difference between the last transmission to end among the multiple synchronized transmissions and the first transmission to end among the multiple transmissions whose transmission ends are synchronized. In this case, the second predetermined time interval can be less than the first predetermined time interval. A PPDU whose transmission ends are synchronized can be referred to as a sync PPDU.
[0234] exist Figure 23 In this context, an STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). A non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). Each of the first AP (AP1) and the second AP (AP2) synchronizes the transmission ends to the first station (STA1) and the second station (STA2). That is, after the first station (STA1) finishes its transmission, the second station (STA2) finishes its transmission within a predetermined time interval from the first station (STA1). The first station (STA1) and the second station (STA2) simultaneously send ACKs. At this time, the first station (STA1) sends an ACK after the SIFS starting from the transmission end to the first station (STA1) and the difference between the transmission end of the first station and the transmission end to the second station (STA2).
[0235] The implementation can be applied to transmissions where the ACK policy is not configured as No ACK. Specifically, the ACK policy can be applied to situations other than immediate response. In a detailed implementation, when multiple stations of a multi-link device receive a transmission whose transmission ends are synchronized, the multiple stations of the multi-link device can simultaneously receive an ACK request and send an ACK according to the ACK request. Multiple stations of a multi-link device that receive a transmission in which the ACK policy is configured as a value other than No ACK within a predetermined time can simultaneously initiate ACK.
[0236] When non-STR multilink devices are present, they should be considered during the TXOP configuration operation, which involves sending RTS / CTS frames and CTS-to-Self frames. This will refer to... Figures 24 to 29 Describe
[0237] Figure 24 The illustration shows the exchange of RTS / CTS frames by a multi-link device according to an embodiment of the present disclosure.
[0238] Even when non-STR multilink devices are present, the RTS / CTS frame switching process can follow the procedures defined in a regular WLAN. RTS / CTS frames can be used to configure the NAV of a station operating in another link. Specifically, a station receiving an RTS / CTS frame can operate in a link different from the link in which the corresponding station operates, and can pass the RTS / CTS frame to another station included in a multilink device that includes the corresponding station.
[0239] However, as described in the above embodiments, channel access or transmission may be limited when non-STR multi-link devices are present. Therefore, as Figure 24 As shown, RTS / CTS may not be sent. That is, if the second station of a non-STR multilink device is performing reception, the station scheduled to transmit to the first station of the non-STR multilink device may not attempt RTS / CTS frame exchange.
[0240] exist Figure 24 In this embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). When the first AP (AP1) sends an RTS frame to the first station (STA1), channel access for the second station (STA2) is disabled. The second AP (AP2) can determine that channel access for the second station (STA2) is disabled. 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. This will refer to... Figure 25 Describe it.
[0241] Figure 25 The diagram illustrates the reference. Figure 24 The hidden node problem that occurs during RTS / CTS frame switching in the described embodiment.
[0242] A station performing a transmission to a non-STR multilink device can perform the transmission without the CTS / RTS switching described above. In this case, because TXOP is not configured in the other station, the other station may attempt to transmit, and therefore the non-STR multilink device station may not be able to receive the transmission. Figure 25In one embodiment, the STR AP multi-link device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multi-link device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). Due to the transmission from the first AP (AP1) to the first station (STA1), the second AP (AP2) cannot send an RTS frame before transmission. Therefore, no TXOP is configured in the station operating in the second link (link2) for the transmission of the second AP (AP2). Therefore, when the second AP (AP2) performs a transmission to the second station (STA2), another BSS (OBSS STA) station performs a transmission in the second link (link2). Accordingly, the second station (STA2) cannot receive the transmission of the second AP (AP2). To solve the hidden node problem, the following embodiment can be applied.
[0243] In a detailed embodiment, when one station of a non-STR multilink device is receiving data, the station is not allowed to perform transmissions to any other station of the non-STR multilink device. In another detailed embodiment, when a station is performing a transmission to the first station of a non-STR multilink device while a second station of the non-STR multilink device is receiving data, the station can simultaneously perform both the transmission to the first station and the transmission to the second station. When a station is performing a transmission to the first station of a non-STR multilink device while a second station of the non-STR multilink device is receiving data, the station can synchronize the end of the transmission to the first station and the end of the transmission to the second station. Specifically, when a station is performing a transmission to the first station of a non-STR multilink device while a second station of the non-STR multilink device is receiving data, the station can simultaneously terminate both the transmission to the first station and the transmission to the second station. In this embodiment, the transmission to the second station can be performed by another station of the multilink device that includes that station.
[0244] Figure 26 The illustration shows RTS / CTS frame switching performed by a multi-link device according to an embodiment of the present disclosure.
[0245] In another embodiment of this disclosure, when the first station of the multi-link device continues transmission to the third station of the non-STR multi-link device, and the second station of the multi-link device sends an RTS frame to the fourth station of the non-STR multi-link device, the first station can end its transmission to the third station before the time point at which the fourth station sends the RTS frame. Correspondingly, the fourth station can send a CTS frame to the second station. Therefore, a TXOP for frame exchange between the second and fourth stations can be configured. However, it may be difficult to achieve the end of the transmission before the time point at which the first station sends the RTS frame to the fourth station.
[0246] In another embodiment of this disclosure, when the first station of the multi-link device continues transmission to the third station of the non-STR multi-link device, and the second station of the multi-link device sends an RTS frame to the fourth station of the non-STR multi-link device, the second station can send the RTS frame to the fourth station at the time when the transmission from the first station to the third station ends. For this purpose, the second station can insert padding into the RTS frame. In this case, the RTS frame can be an RTS frame format for flexible control of the transmission length. For ease of description, the RTS frame format is referred to as a multi-link (ML)-RTS frame. The ML-RTS frame may include padding fields for padding. For example, the ML-RTS frame format can be similar to... Figure 26 The RTS frame format shown is the same. Furthermore, the first station can promptly insert padding into the transmission of the third station to conform to the transmission end of the RTS frame.
[0247] exist Figure 26 In this embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The second AP (AP2) promptly sends an ML-RTS frame to the second STA (STA2) at the end of the transmission from the first station (STA1) to the first AP (AP1). Subsequently, when the first station (STA1) sends an ACK to the first AP (AP1), the second station (STA2) sends an ACK to the second AP (AP2). Therefore, a TXOP for frame exchange between the second AP (AP2) and the second station (STA2) is configured in the station operating in the second link channel.
[0248] In another detailed embodiment, a different frame, instead of an RTS / CTS frame, can be used to configure the NAV. In the above embodiment, an ACK request frame can be sent instead of an RTS frame. The ACK request frame may include duration information related to the end time of the transmission. Furthermore, frames including an ACK sent in response to an ACK request may also include duration information. In this case, the duration information of the frame including the ACK can be configured based on the duration information of the ACK request frame.
[0249] The above embodiments have been described for RTS / CTS frame switching, but they can also be used for control frame switching as well as RTS / CTS frames. In this case, control frame switching may include the exchange between PS-Poll frames and PS-Poll response frames.
[0250] Figure 27The illustration shows an exceptional transmission of a control frame response by a multi-link device in a situation where channel access is prohibited, according to an embodiment of the present disclosure.
[0251] As described in the above embodiments, when non-STR multi-link devices are present, channel access for some stations may be prohibited. Even if channel access is prohibited, a station can still send a response to a control frame. Specifically, even if channel access is prohibited, a station can still send a CTS frame in response to an RTS frame.
[0252] As described above, when sending a response to a control frame as an exception to channel access prohibition, the following embodiment can be applied. The first station sends a response to a control frame as an exception to channel access prohibition. When the first station sends a response to the control frame, the third station performs a transmission to the second station, which is included in the multi-link device comprising the first station. In this case, the third station can perform a retransmission to the first station. This is because the third station can anticipate the transmission failure of the second station.
[0253] exist Figure 27 In one embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The first AP (AP) performs a transmission to the first station (STA1). The second AP (AP2) sends an RTS frame to the second station (STA2). Since the first station (STA1) performs reception, channel access for the second station (STA2) is prohibited. However, the second station (STA2) sends a CTS frame to the second AP (AP2) as an exception to the channel access prohibition. The first AP (AP1) can determine that the probability of its transmission failing due to the second station (STA2) transmitting a CTS frame is high. Therefore, the first AP (AP1) performs a retransmission to the first station (STA1). (See reference...) Figure 28 The retransmission method is described in more detail.
[0254] Figure 28 The diagram illustrates the retransmission of data to a station that is not part of the STR multilink device.
[0255] Reference Figure 27In the described retransmission, only some packets included in the initial transmission may be retransmitted. Specifically, the station performing the retransmission may only retransmit some packets included in the initial transmission. The station performing the retransmission may determine the packets included in the initial transmission as the packets to be retransmitted based on the time interval in which the station performing the retransmission receives the CTS frame. Specifically, the station performing the retransmission may determine the packets included in the initial transmission that were transmitted during the time interval in which the station performing the retransmission receives the CTS frame as the packets to be retransmitted. In this case, the station performing the retransmission may retransmit the packets transmitted during the time interval in which the station performing the retransmission receives the CTS frame based on the propagation delay. In another detailed embodiment, the station performing the retransmission may retransmit all packets included in the initial transmission.
[0256] Furthermore, the station performing the retransmission can perform the retransmission before receiving the ACK for transmission. In this case, the station performing the retransmission can receive a block ACK indicating whether the initial transmission and the retransmission were received after the retransmission. Therefore, the station performing the retransmission can perform the retransmission before SIFS after the initial transmission. In another detailed embodiment, a station that fails to receive due to a control frame sent as an exception to channel access prohibition can wait to receive the retransmission without sending an ACK.
[0257] exist Figure 28 In this embodiment, taking into account the interval and transmission delay of the second AP (AP2) receiving CTS frames, the first AP (AP1) retransmits the fourth and fifth packets. After the retransmission, the first AP (AP1) receives an ACK indicating whether the retransmission was received.
[0258] Figure 29 The illustration shows the transmission of control frames through a link operated by an unprohibited station via its channel access, rather than through a link operated by a prohibited station via its channel access, according to an embodiment of the present disclosure.
[0259] like Figure 26 As described in the illustrated embodiment, the endpoints of transmissions to multiple stations of a non-STR multilink device can be synchronized. However, this requires controlling already generated MPDUs or regenerating MPDUs, and may therefore lead to implementation difficulties. Therefore, the multilink device can send control frames via its channel access to a link operated by an unbanned station, rather than via its channel access to a link operated by a banned station. Specifically, the multilink device can send control frames via a link currently being executed by the non-STR multilink device's station that receives data from the multilink device. In this case, the control frame can be an RTS frame.
[0260] exist Figure 29In this embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The first AP (AP1) performs transmissions to the first station (STA1). Even if the second AP (AP2) successfully performs a backoff process, it cannot perform transmissions to the second station (STA2) because the first station (STA1) is receiving transmissions from the first AP (AP1). At this time, the second AP (AP2) requests the first AP (AP1) to send an RTS frame with the second station (STA2) as the receiver. The first AP (AP1) can then insert the RTS frame with the second station (STA2) as the receiver into the transmission performed by the first AP (AP1). In another detailed embodiment, after the first AP (AP1) finishes the transmission being performed by the first AP (AP1), the first AP (AP1) may send an RTS frame to the second station (STA2) on the first link (link1) after the SIFS of the corresponding transmission. The first station (STA1) receives the RTS frame to the second station (STA2) and passes the received RTS frame to the second station (STA2). The second station (STA2) performs CCA during PIFS. When the channel is idle during PIFS, the second station (STA2) sends a CTS-to-Self frame. During the time interval during which the second station (STA2) is expected to send a response to the RTS frame, the first AP (AP1) may stop transmissions to the first station (STA1). Furthermore, when the second station (STA2) sends a response to the RTS frame, the first station (STA1) may send an ACK for the received transmission. In another detailed embodiment, the first station (STA1) may also send a response to the RTS frame when the second station (STA2) sends a response to the RTS frame. Figure 29 This is to aid in understanding the description and can be used to control the transmission of frames, as well as RTS and CTS-to-Self frames. Additionally, another time interval besides PIFS can be used.
[0261] Figure 30 The illustration shows the transmission of an ACK by a multi-link device according to an embodiment of the present disclosure.
[0262] A station in a multi-link device can request a link to send an ACK to a station in a non-STR multi-link device. Specifically, a station in a multi-link device can request to send an ACK on a link different from the link where transmission has already occurred. Figure 28In this embodiment, the first AP (AP1) of the STR multi-link device performs a transmission (TX(#2)) to the first station (STA1) of the non-STR multi-link device. At this time, the first AP (AP1) requests an ACK for the transmission (TX(#2)) via the second link (link2). This is because it is difficult to determine the transmission of the ACK for the transmission (TX(#2)) of the first AP (AP1) since the transmission (TX(#2)) of the first AP (AP1) ends earlier than the transmission from the second AP (AP2) to the second station (STA2).
[0263] Furthermore, for ACK transmissions, a station can configure its ACK policy as implicit BAR to avoid sending an immediate response to the transmission. In another detailed embodiment, the station can configure its ACK policy for transmission as BlockAckReq. However, in order to send a block ACK, BlockAckReq should be sent, which may therefore generate channel access burden and transmission delay. Therefore, a new ACK policy may be needed for multi-link devices.
[0264] A station in a multi-link device can also send an ACK for a transmission received by another station included in the multi-link device, the same ACK used for a transmission received by that station. This ACK transmission can be called a multi-link (ML)-ACK. Furthermore, ML-ACK can be configured as an ACK policy. Figure 30 In one embodiment, the first AP (AP1) configures ML-ACK as the ACK strategy for the transmission (TX(#2)). The first station (STA1) does not send an ACK to the first AP (AP1) after receiving the transmission (TX(#2)). The second station (STA2) completes the reception of the transmission from the second AP (AP2) and sends ACKs for both the transmission from the first AP (AP1) and the transmission from the second AP (AP2). Non-STR multi-link devices may include not only the first station (STA1) and the second station (STA2), but also a third station (STA3), and STR multi-link devices may include not only the first AP (AP1) and the second AP (AP2), but also a third AP (AP3). In this case, ML-ACK can be configured as the ACK strategy for transmissions from the second AP (AP2) to the second station (STA2). When the transmission from the third AP (AP3) to the third station (STA3) is completed later than the transmission from the second AP (AP2) to the second station (STA3), the third station (STA3) can send an ACK to the third AP (AP3) for the transmission from the first AP (AP1) to the first station (STA1), an ACK for the transmission from the second AP (AP2) to the second station (STA2), and an ACK for the transmission from the third AP (AP3) to the third station (STA3).
[0265] These embodiments prevent inter-link interference that may arise from ACK transmissions, even if transmissions to stations on non-STR multi-link devices are not completed simultaneously. In the above embodiments, the ACK policy can be configured as BlockACK instead of ML-ACK. In another detailed embodiment, the ACK policy can be configured as No ACK instead of ML-ACK.
[0266] When a multi-link device performs service transmission, the number of links acquiring transmission opportunities may increase. In this case, the multi-link device can send services through links that acquire transmission opportunities later, and these services are scheduled to be sent through the link that acquires a transmission opportunity first. At this time, the NAV configured in the link where the multi-link device acquires a transmission opportunity first can be configured to be greater than the NAV required to send the service. When the NAV is configured to be greater than the NAV required to send the service in the link where the multi-link device acquires a transmission opportunity first, the multi-link device can send a CF-END frame after completing the transmission in the link where the transmission opportunity was first acquired, in order to reset the NAV.
[0267] refer to Figures 31 to 34 Describes the reception of the synchronization PPDU and the signaling associated with the reception of the synchronization PPDU.
[0268] To receive synchronization PPDUs, the first station of a non-STR multilink device should determine whether a second station with a non-STR relationship to the first station has begun receiving synchronization PPDUs. Furthermore, the first station should continuously perform preamble detection (PD). This operation by the first station may be unreasonable if it is believed that the channel access of the first station receiving synchronization PPDUs is blocked by the reception of another station of a non-STR multilink device. Therefore, the first station can enter a sleep state under predetermined conditions. Synchronization PPDUs can be transmitted within a normally configured TXOP. Therefore, the performance gain that can be obtained by receiving synchronization PPDUs can be determined based on the length of the remaining TXOP. Thus, the first station can determine whether to abandon receiving synchronization PPDUs based on the length of the synchronization PPDU. When the first station abandons receiving synchronization PPDUs, it can enter a sleep state. Such a power-saving operation can be called inter-link TXOP power saving (PS). In an inter-link TXOP PS, a station that has entered a sleep state can be awakened from the sleep state to receive frames periodically transmitted from the AP, such as beacon frames, TIM frames, and DTIM frames. Furthermore, when the TXOP ends, for example, when a CF-END frame is transmitted, a station that has entered a sleep state in an inter-link TXOP PS can be awakened from the sleep state.
[0269] The TXOP can be changed to a time period indicated by the length field of the signaling field of the PPDU or the duration field of the MAC frame. Specifically, in the above embodiment, the station can determine the PPDU occupancy time based on the time period indicated by the length field or duration field of the MAC frame.
[0270] Non-AP multi-link devices can signal to AP multi-link devices whether they have received synchronous PPDUs and the conditions under which synchronous PPDUs are supported. Furthermore, AP multi-link devices can signal to non-AP multi-link devices whether they support PPDU transmission. In this case, the multi-link device can signal whether synchronous PPDUs are supported for each individual multi-link device. For example, the AP multi-link device can signal whether synchronous PPDU transmission is supported for each individual AP. In another detailed embodiment, the multi-link device can signal whether synchronous PPDUs are supported for each station. Specifically, the AP multi-link device can signal whether synchronous PPDU transmission is supported for each AP included in the AP multi-link device. For example, an AP multi-link device including a first AP, a second AP, and a third AP can indicate that the first AP supports synchronous PPDU transmission, while the second and third APs do not.
[0271] When an AP multilink device associated with a non-AP multilink device indicates that it does not support the transmission of synchronization PPDUs, the station of the non-AP multilink device can enter a sleep state in the inter-link PS (Power Separator) instead of receiving data from another station of the non-AP multilink device. This is because the AP multilink device associated with the non-AP multilink device cannot send synchronization PPDUs. In this case, the station of the non-AP multilink device can determine the length of time to maintain the sleep state based on the length of the PPDU received by the other station of the non-AP multilink device.
[0272] Whether to support synchronous PPDU transmission or reception can be determined based on operating strategies and hardware performance. Therefore, the signaling of whether to support synchronous PPDU transmission or reception can be sent not only through performance information but also through information about the operating mode. (See reference...) Figure 31 This describes in detail the methods for signaling support for synchronous PPDU transmission or reception.
[0273] Figure 31 The illustration shows element fields indicating information supporting synchronous PPDU reception or transmission according to embodiments of the present disclosure.
[0274] As described above, information indicating whether synchronous PPDU transmission is supported can be included in the element indicating the station's capabilities. For ease of description, the element indicating the station's capabilities is called a capability element. Furthermore, within the capability element, the field indicating whether synchronous PPDU transmission is supported is called the Synchronous PPDU Support Tx subfield. In this case, the capability element can be a multi-link element, which indicates multi-link capabilities. Additionally, the capability element can be an EHT capability element indicating capabilities related to EHT. Figure 31 (a) An example of a capability element is illustrated.
[0275] When the value of the "Support Synchronous PPDU Tx" subfield is 1, it indicates that the station or multi-link device indicated by the "Support Synchronous PPDU Tx" subfield supports synchronous PPDU transmission. When the value of the "Support Synchronous PPDU Tx" subfield is 0, it indicates that the station or multi-link device indicated by the "Support Synchronous PPDU Tx" subfield does not support synchronous PPDU transmission. Furthermore, when a station not included in a multi-link device transmits a capability element, the "Support Synchronous PPDU Tx" subfield can signal information unrelated to whether synchronous PPDU transmission is supported, or it can be used as a reserved field.
[0276] As described above, information indicating whether synchronous PPDU reception is supported can be included in an element indicating information related to station operation. For ease of description, this element indicating information related to station operation is referred to as an operation element. Furthermore, within the operation element, the field indicating whether synchronous PPDU reception is supported is referred to as the Synchronous PPDU Support Rx Disabled Subfield. Figure 31(b) An example of an operational element is illustrated. When the value of the "Support Synchronous PPDU Rx Disabled Subfield" is 1, it can indicate that synchronous PPDU reception is not supported. Specifically, when the value of the "Support Synchronous PPDU Rx Disabled Subfield" is 1, it can indicate that the station sending the "Support Synchronous PPDU Rx Disabled Subfield" does not wish to wait to receive the synchronous PPDU. When the multilink device configures the value of the "Support Synchronous PPDU Rx Disabled Subfield" to 1, the second station of the multilink device may not perform PD and CCA when the first station of the multilink device performs reception. The AP multilink device associated with the multilink device sending the "Support Synchronous PPDU Rx Disabled Subfield" does not simultaneously send PPDUs to multiple stations of the multilink device sending the "Support Synchronous PPDU Rx Disabled Subfield". The PPDU can be a SU PPDU, a full BW MU PPDU, or an OFDMA MUPPDU sent via one of the following formats: non-HT PPDU format, HT PPDU format, VHT PPDU format, HE PPDU format, and EHT PPDU format. At this time, the AP multilink device should not send frames requesting a response (e.g., an immediate response). Frames requesting a response may include at least one of RTS, multi-user (MU)-RTS, trigger frames, and block Ack requests (BAR).
[0277] In addition, the operation element may include information related to the minimum length of the synchronization PPDU that can be received by the station or multilink device that sent the operation element. In this case, the subfield indicating the information related to the minimum length of the synchronization PPDU is called the remaining TXOP threshold subfield. The remaining TXOP threshold subfield may indicate time. Furthermore, the remaining TXOP threshold subfield may be expressed in µs, ms, or symbols. A multilink device associated with the multilink device that sent the remaining TXOP threshold subfield may not be permitted to send a synchronization PPDU shorter than the length indicated by the remaining TXOP threshold subfield to the multilink device or station that sent the remaining TXOP threshold subfield.
[0278] Furthermore, when the Remaining TXOP Threshold subfield is configured to a predetermined value, it can indicate that the multi-link device or station sending the Remaining TXOP Threshold subfield does not support synchronous PPDU reception. The predetermined value can be a value indicating a time longer than the maximum time that can be represented by the Remaining TXOP Threshold subfield. In another detailed embodiment, the predetermined value can be 0. When applying the embodiment, the Synchronous PPDU Rx Disable subfield can be omitted from the Operation field.
[0279] Furthermore, in the above embodiments, the synchronization PPDU Rx disabled subfield and the remaining TXOP threshold subfield, which can be signaled via an operation element, have been described. The synchronization PPDU Rx disabled subfield and the remaining TXOP threshold subfield can also be signaled via elements other than the operation element or signaling information. (See reference...) Figures 32 to 34 Described according to reference Figure 31 The described signaling implementation example demonstrates an inter-link TXOP power saving mode.
[0280] Figure 32 The illustration shows an inter-link TXOP power saving mode operation performed by a non-STR multi-link device according to an embodiment of the present disclosure.
[0281] When a signal is sent indicating that a non-STR multilink device does not support receiving synchronous PPDUs, the second station of the non-STR multilink device can enter a sleep state while the first station of the non-STR multilink device is receiving data. In this case, the second station can remain in sleep mode until the end time of the TXOP indicated by the PPDU received by the first station. As described above, the second station anticipates receiving frames periodically transmitted from the AP before the end time of the TXOP indicated by the PPDU received by the first station. In this case, the second station can wake up from sleep mode before the end time of the TXOP indicated by the PPDU received by the first station. As described above, the frames periodically transmitted from the AP can include at least one of beacon frames, TIM frames, and DTIM frames.
[0282] Even after the TXOP end time indicated by the PPDU received by the first station, the second station can remain in a dormant state. Specifically, based on information received from the AP associated with the second station, the second station can remain in a dormant state even after the TXOP end time indicated by the PPDU received by the first station. In this case, the information received from the AP associated with the second station can be NAV-related information. Furthermore, the information received from the AP associated with the second station can be operational information of the AP associated with the first station. When the NAV configured for the second AP of the AP multi-link device, which performs a transmission to the second station of the non-AP multi-link device, has not expired, the first AP of the AP multi-link device can send information about the expected time point of the first AP's transmission or reception and the expected time point of NAV expiration to the first station of the non-AP multi-link device. The first station of the non-AP multi-link device signals to indicate that the first AP of the AP multi-link device does not want to receive synchronization PPDU information. When the NAV configured for the second AP of the AP multi-link device, which performs a transmission to the second station of the non-AP multi-link device, has not expired, this may include the second AP receiving or transmitting a PPDU from a station. When the NAV configured in the second AP of the AP multilink device, which is transmitted by the second station to the non-AP multilink device, does not expire, it may be possible to configure the NAV in the second AP via a PPDU not sent by the second station.
[0283] exist Figure 32 In this embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The non-STR non-AP multilink device signals that it does not expect to receive synchronization PPDU information. The first AP (AP1) performs a transmission to the first station (STA1). At this time, the second station (STA2) remains in a dormant state until the time point indicated by the TXOP sent by the first AP (AP1) to the first station (STA1).
[0284] Figure 33 The illustration shows a station of a non-STR multilink device according to an embodiment of the present disclosure receiving a synchronization PPDU and entering a sleep state.
[0285] When the remaining duration of the TXOP indicated by the PPDU received by the first station of the non-STR multi-link device is less than or equal to the length indicated by the remaining TXOP threshold subfield sent by the non-STR multi-link device, the first station of the non-STR multi-link device can enter the inter-link TXOP sleep state. At this time, when the remaining duration of the TXOP indicated by the PPDU being received by the first station is longer than the length indicated by the remaining TXOP threshold subfield sent by the non-STR multi-link device, the second station can receive the synchronization PPDU sent to the second station before entering the sleep state. At this time, the second station can receive the synchronization PPDU. To this end, the second station can perform PD and determine whether the intended receiver of the received PPDU is the second station. Specifically, the second station can determine whether the AID indicated by the signaling field of the PPDU or the RA of the MAC frame included in the PPDU indicates the second station.
[0286] exist Figure 33 In this embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The non-STR non-AP multilink device signals to indicate that it expects to receive synchronization PPDU information. At this time, the non-AP multilink device also signals 'a', which is the minimum TXOP length required for receiving the synchronization PPDU. The first AP (AP1) performs the transmission to the first station (STA1), while the second station (STA2) waits to receive the synchronization PPDU. When the TXOP of the PPDU sent 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 saving state.
[0287] Figure 34 The illustration shows a station of a non-STR multilink device according to another embodiment of the present disclosure receiving a synchronization PPDU and entering a sleep state.
[0288] When a station on a non-STR multilink device is waiting to receive a synchronization PPDU, and a transmission of a PPDU that is not a synchronization PPDU is detected in the BSS operated by the AP associated with the station, the station on the non-STR multilink device can enter an inter-link TXOP power-saving state. At this time, the station can determine that a PPDU with a receiver that is not intended for it is not a synchronization PPDU. Furthermore, when a transmission of a PPDU that is not a synchronization PPDU is detected in the BSS operated by the AP associated with the station on the non-STR multilink device while in sleep mode, the station on the non-STR multilink device can enter an inter-link TXOP power-saving state even if the minimum TXOP signaled by the station is left unused.
[0289] exist Figure 34 In this embodiment, the STR AP multilink device includes a first AP (AP1) operating in the first link (link1) and a second AP (AP2) operating in the second link (link2). The non-STR multilink device includes a first station (STA1) operating in the first link (link1) and a second station (STA2) operating in the second link (link2). The non-STR non-AP multilink device signals to indicate that it expects to receive a synchronization PPDU. At this time, the non-AP multilink device also signals "a", which is the minimum TXOP length required to receive the synchronization PPDU. The first AP (AP1) performs a transmission to the first station (STA1), and the second station (STA2) waits to receive the synchronization PPDU. The second station (STA2) detects the transmission of a PPDU that is not a synchronization PPDU in its BSS. The TXOP of the PPDU sent by the first AP (AP1) to the first station (STA1) is greater than 'a', but the second station (STA2) enters an inter-link TXOP power saving state.
[0290] Although this disclosure has been described above using WLAN communication as an example, it is not limited thereto and can be equivalently applied to other communication systems such as cellular communication. Furthermore, while the methods, apparatus, and systems of this disclosure have been described in conjunction with certain embodiments, some or all of the components and operations of this disclosure can be implemented using a computer system with a general-purpose hardware architecture.
[0291] The features, structures, effects, etc., described in the above embodiments are included in at least one embodiment of this disclosure, and are not necessarily limited to one embodiment. Furthermore, those skilled in the art to which the embodiments pertain can combine or modify the features, structures, effects, etc., shown in each embodiment for other embodiments. Therefore, content related to these combinations and modifications should be interpreted as falling within the scope of this disclosure.
[0292] Although the embodiments have been described above in detail, they are merely examples and not limiting of this disclosure, and those skilled in the art will recognize that various modifications and applications not illustrated above are possible without departing from the essential characteristics of these embodiments. For example, each component specifically shown in the embodiments is a component that can be modified and implemented. Furthermore, differences associated with these modifications and applications should be interpreted as falling within the scope of this disclosure as defined in the appended claims.
Claims
1. An access point (AP) multi-link device: transceiver; as well as processor, in, The processor is configured to: Based on whether the non-STR non-AP multi-link device is performing transmission on the first link, a determination is made as to whether to perform transmission to the non-STR non-AP multi-link device on the second link. The non-STR non-AP multi-link device operates on both the first and second links corresponding to the non-STR link. On one of the first and second links, transmission by the non-STR non-AP multi-link device is restricted to protect the transmission or reception of the non-STR non-AP multi-link device on the other link of the first and second links. During the channel access process on the second link, the processor is further configured to: Get random numbers within the contention window (CW); Configure the random number as the initial value for the backoff counter of the second link; When the channel of the second link is detected to be idle during the time slot, the backoff counter is decremented by 1, wherein when the backoff counter is not 0, transmission of the AP multi-link device on the second link is not allowed; When the backoff counter is 0, while the non-STR, non-AP multi-link device is performing transmission on the first link, it does not perform transmission on the second link; and When the AP multi-link device retryes the channel access procedure after failing to perform a transmission in the second link, the value of the retry counter for the channel access procedure is maintained.
2. The AP multi-link device according to claim 1, wherein, The processor is configured to perform transmissions to a device different from the non-STR non-AP multi-link device in the second link while the non-STR non-AP multi-link device is performing transmissions in the first link, without performing transmissions to the non-STR non-AP multi-link device.
3. The AP multi-link device according to claim 2, wherein, The processor is configured to: when performing a transmission to a device different from the non-STR non-AP multi-link device in the second link, send a service with a priority equal to or higher than that of the service to the non-STR non-AP multi-link device.
4. The AP multi-link device according to claim 1, wherein, The processor is configured to perform synchronous transmissions on the first link and the second link, wherein the synchronous transmissions end with a time difference within a first predetermined time interval, and Receive subsequent transmissions on at least one of the first and second links, following the synchronization transmission. The interval between the subsequent transmission and the synchronous transmission is the sum of the Short Interframe Spacing (SIFS) and the first predetermined time interval.
5. The AP multi-link device according to claim 1, wherein... The processor is configured to perform transmission on both the first and second links if the channel of the second link is idle for a first predetermined time when the backoff counter of the channel access procedure on the first link is 0.
6. The AP multi-link device according to claim 5, wherein, The processor is configured to: if the channel of the second link is idle for a predetermined time when the backoff counter of the channel access procedure on the first link is 0, then to start transmission on the first link and the second link at the difference within a second predetermined time interval.
7. A non-access point AP multi-link device, comprising: transceiver; as well as processor, The non-AP multi-link device is configured to operate on a first link and a second link corresponding to a non-simultaneous transmission and reception STR link. The transmission of the non-AP multi-link device on one of the first and second links is restricted to protect the transmission or reception of the non-AP multi-link device on the other link of the first and second links. During the channel access process on the second link, the processor is configured to: Obtain a random number within the contention window CW for the second link; Configure the random number as the initial value of the backoff counter; When the channel of the second link is detected to be idle during the time slot, the backoff counter is decremented by 1, wherein when the backoff counter is not 0, transmission of the non-AP multilink device in the second link is not allowed; When the backoff counter is 0, while the non-AP multi-link device is receiving data on the first link, it does not transmit data on the second link; and When a non-AP MLD retryes the channel access procedure after failing to perform a transmission in the second link, the retry counter value of the channel access procedure is maintained.
8. The non-AP multi-link device according to claim 7, wherein, The processor is configured to: receive synchronous transmissions in the first link and the second link, wherein the synchronous transmissions terminate in the first link and the second link with a time difference within a first predetermined time interval, and The synchronization transmission is performed on at least one of the first and second links, followed by subsequent transmissions. The interval between the subsequent transmission and the synchronous transmission is the sum of the Short Interframe Spacing (SIFS) and the first predetermined time interval.
9. The non-AP multi-link device according to claim 7, wherein, When the frequency band of one of the first and second links changes, the processor is configured to send information about whether STR is supported.
10. The non-AP multi-link device according to claim 7, in, The processor is configured to perform a transmission to the AP multilink device on the first link and the second link if the channel of the first link is idle during a second predetermined time interval when the backoff counter is 0.
11. A method for operating an access point (AP) multi-link device, the method comprising: Whether to perform a transmission to the non-STR non-AP multi-link device on the corresponding second link is determined based on whether the non-STR non-AP multi-link device performs a transmission on the first link during non-simultaneous transmission and reception. Transmissions by the non-STR non-AP multi-link device on one of the first and second links are restricted to protect the transmission or reception of the non-STR non-AP multi-link device on the other link. During channel access on the second link, the method further includes: Get random numbers within the contention window (CW); Configure the random number as the initial value for the backoff counter of the second link; When the channel of the second link is detected to be idle during the time slot, the backoff counter is decremented by 1, wherein when the backoff counter is not 0, transmission of the AP multi-link device on the second link is not allowed; When the backoff counter is 0, while the non-STR, non-AP multi-link device is performing transmission on the first link, it does not perform transmission on the second link; and When the AP multi-link device retryes the channel access procedure after failing to perform a transmission in the second link, the value of the retry counter for the channel access procedure is maintained.
12. The method of claim 11, further comprising: While the non-STR non-AP multi-link device is performing transmission on the first link, it is performing transmission to a different device on the second link, without performing transmission to the non-STR non-AP multi-link device.
13. The method according to claim 12, wherein, The transmission to a device different from the non-STR non-AP multi-link device further includes: when the transmission to the device different from the non-STR non-AP multi-link device is performed on the second link, sending a service with a priority equal to or higher than that of the transmission to the non-STR non-AP multi-link device.
14. The method of claim 11, further comprising: Perform synchronous transmission on the first link and the second link, wherein the synchronous transmission ends with a time difference within a first predetermined time interval, and Receive subsequent transmissions on at least one of the first and second links, following the synchronization transmission. The interval between the subsequent transmission and the synchronous transmission is the sum of the Short Interframe Spacing (SIFS) and the first predetermined time interval.
