WO2022265479A1 - 멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는 무선 통신 단말 - Google Patents
멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는 무선 통신 단말 Download PDFInfo
- Publication number
- WO2022265479A1 WO2022265479A1 PCT/KR2022/008730 KR2022008730W WO2022265479A1 WO 2022265479 A1 WO2022265479 A1 WO 2022265479A1 KR 2022008730 W KR2022008730 W KR 2022008730W WO 2022265479 A1 WO2022265479 A1 WO 2022265479A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ppdu
- frame
- sta
- link
- mediumsyncdelay
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 77
- 238000004891 communication Methods 0.000 title claims abstract description 75
- 230000005540 biological transmission Effects 0.000 claims description 166
- 230000000670 limiting effect Effects 0.000 claims description 15
- 230000004044 response Effects 0.000 description 106
- OVGWMUWIRHGGJP-WTODYLRWSA-N (z)-7-[(1r,3s,4s,5r)-3-[(e,3r)-3-hydroxyoct-1-enyl]-6-thiabicyclo[3.1.1]heptan-4-yl]hept-5-enoic acid Chemical compound OC(=O)CCC\C=C/C[C@H]1[C@H](/C=C/[C@H](O)CCCCC)C[C@H]2S[C@@H]1C2 OVGWMUWIRHGGJP-WTODYLRWSA-N 0.000 description 77
- 101100366889 Caenorhabditis elegans sta-2 gene Proteins 0.000 description 77
- 101150081243 STA1 gene Proteins 0.000 description 74
- 238000010586 diagram Methods 0.000 description 39
- 230000011664 signaling Effects 0.000 description 27
- 238000013507 mapping Methods 0.000 description 26
- 230000006870 function Effects 0.000 description 23
- 230000036961 partial effect Effects 0.000 description 19
- 230000008569 process Effects 0.000 description 19
- 239000000523 sample Substances 0.000 description 17
- 238000005516 engineering process Methods 0.000 description 12
- VYLDEYYOISNGST-UHFFFAOYSA-N bissulfosuccinimidyl suberate Chemical compound O=C1C(S(=O)(=O)O)CC(=O)N1OC(=O)CCCCCCC(=O)ON1C(=O)C(S(O)(=O)=O)CC1=O VYLDEYYOISNGST-UHFFFAOYSA-N 0.000 description 9
- 238000012549 training Methods 0.000 description 8
- 230000002829 reductive effect Effects 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000006835 compression Effects 0.000 description 4
- 238000007906 compression Methods 0.000 description 4
- 101100161473 Arabidopsis thaliana ABCB25 gene Proteins 0.000 description 3
- 101100096893 Mus musculus Sult2a1 gene Proteins 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000001934 delay Effects 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- OVGWMUWIRHGGJP-WVDJAODQSA-N (z)-7-[(1s,3r,4r,5s)-3-[(e,3r)-3-hydroxyoct-1-enyl]-6-thiabicyclo[3.1.1]heptan-4-yl]hept-5-enoic acid Chemical compound OC(=O)CCC\C=C/C[C@@H]1[C@@H](/C=C/[C@H](O)CCCCC)C[C@@H]2S[C@H]1C2 OVGWMUWIRHGGJP-WVDJAODQSA-N 0.000 description 2
- 201000004569 Blindness Diseases 0.000 description 2
- 101710082751 Carboxypeptidase S1 homolog A Proteins 0.000 description 2
- 102100023804 Coagulation factor VII Human genes 0.000 description 2
- 101000988961 Escherichia coli Heat-stable enterotoxin A2 Proteins 0.000 description 2
- 238000003722 High energy mechanical milling Methods 0.000 description 2
- 101000752249 Homo sapiens Rho guanine nucleotide exchange factor 3 Proteins 0.000 description 2
- 102100021689 Rho guanine nucleotide exchange factor 3 Human genes 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000008054 signal transmission Effects 0.000 description 2
- 101100395869 Escherichia coli sta3 gene Proteins 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000004929 transmission Raman spectroscopy Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/14—Multichannel or multilink protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
- H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Definitions
- the present invention relates to a wireless communication method using multi-links and a wireless communication terminal using the same.
- Wireless LAN technology is a technology that allows mobile devices such as smart phones, smart pads, laptop computers, portable multimedia players, and embedded devices to wirelessly access the Internet at home, businesses, or specific service areas based on wireless communication technology in a short distance. to be.
- IEEE 802.11b supports a communication speed of up to 11 Mbps while using a frequency of the 2.4 GHz band.
- IEEE 802.11a which was commercialized after IEEE 802.11b, uses a frequency of the 5GHz band rather than the 2.4GHz band, reducing the effect of interference compared to the frequency of the significantly congested 2.4GHz band, and using OFDM (orthogonal frequency division multiplexing) technology. communication speed up to 54 Mbps.
- IEEE 802.11a has a short communication distance compared to IEEE 802.11b.
- IEEE 802.11g like IEEE 802.11b, uses a frequency of 2.4 GHz band to realize a communication speed of up to 54 Mbps, and has received considerable attention because it satisfies backward compatibility. have the upper hand
- IEEE 802.11n As a technical standard established to overcome the limitation of communication speed, which has been pointed out as a weakness in the wireless LAN. IEEE 802.11n aims to increase the speed and reliability of networks and extend the operating distance of wireless networks. More specifically, IEEE 802.11n supports High Throughput (HT) with a data processing rate of up to 540 Mbps or more, and also uses multiple antennas at both the transmitter and receiver to minimize transmission errors and optimize data rates. It is based on Multiple Inputs and Multiple Outputs (MIMO) technology. In addition, this standard can use a coding scheme that transmits multiple redundant copies to increase data reliability.
- HT High Throughput
- MIMO Multiple Inputs and Multiple Outputs
- IEEE 802.11ac supports a wide bandwidth (80 MHz to 160 MHz) at a frequency of 5 GHz.
- the IEEE 802.11ac standard is defined only in the 5GHz band, but early 11ac chipsets will support operation in the 2.4GHz band for backward compatibility with existing 2.4GHz band products.
- the wireless LAN speed of multiple stations can be at least 1 Gbps and the maximum single link speed can be at least 500 Mbps.
- IEEE 802.11ad is a transmission standard that provides a speed of up to 7 Gbps using beamforming technology, and is suitable for high-bitrate video streaming such as large amounts of data or uncompressed HD video.
- the 60 GHz frequency band has a disadvantage in that it is difficult to pass through obstacles and can only be used between devices in a short distance.
- the IEEE 802.11ax High Efficiency WLAN, HEW
- HEW High Efficiency WLAN
- IEEE 802.11be Extremely High Throughput, EHT
- EHT Extremely High Throughput
- An object of an embodiment of the present invention is to provide a wireless communication method using multi-link and a wireless communication terminal using the same.
- an object of an embodiment of the present invention is to provide a sync recovery method of a station using multi-links.
- a multi-link device including a plurality of stations each operating in a plurality of links including a first link and a second link
- the processor comprising: one If a frame transmitted from one of the above stations (STAs) is received through a second STA operating in the second link, and the medium sync delay timer is not '0', based on the received frame Reset a Medium Sync Delay timer for application of the Medium Sync Delay of the second STA, but the Medium Sync Delay determines whether the data transmission / After reception, a period for limiting data transmission/reception through the second link is indicated, and the medium sync delay timer is reset when the frame corresponds to a valid MPDU except for a request to send (RTS) frame.
- STAs stations
- RTS request to send
- first link and the second link NSTR Non-Simultaneous Transmission and Reception link pair.
- the medium sync delay timer is started when transmission on the first link ends.
- the medium sync delay timer starts when a specific delay time passes after transmission on the first link ends.
- the specific delay time is a delay time for link switching.
- the medium sync delay timer is reset when the frame is transmitted from an AP associated with the second STA or an AP included in the same multi-BSSID set as the associated AP.
- An embodiment of the present invention provides a wireless communication method using multi-links efficiently and a wireless communication terminal using the same.
- FIG. 1 shows a WLAN system according to an embodiment of the present invention.
- FIG. 2 shows a wireless LAN system according to another embodiment of the present invention.
- FIG 3 shows the configuration of a station according to an embodiment of the present invention.
- FIG 4 shows the configuration of an access point according to an embodiment of the present invention.
- FIG. 5 schematically illustrates a process in which a station establishes a link with an access point.
- CSMA carrier sense multiple access
- CA collision avoidance
- PPDU 7 illustrates an embodiment of various standard generational PLCP Protocol Data Unit (PPDU) formats.
- PPDU Protocol Data Unit
- EHT Extremely High Throughput
- FIG. 9 is a diagram illustrating a multi-link device according to an embodiment of the present invention.
- FIG. 10 is a diagram illustrating an example of a TID-to-link mapping method according to an embodiment of the present invention.
- FIG. 11 is a diagram illustrating an example of a multi-link NAV configuration operation according to an embodiment of the present invention.
- FIG. 12 is a diagram illustrating another example of a multi-link NAV configuration operation according to an embodiment of the present invention.
- FIG. 13 is a diagram illustrating an example of BSS classification and an operation based thereon according to an embodiment of the present invention.
- FIG. 14 shows a wireless LAN function according to an embodiment of the present invention.
- FIG 15 illustrates an uplink (UL) multi-user (MU) operation according to an embodiment of the present invention.
- UL uplink
- MU multi-user
- FIG. 16 shows a trigger frame format according to an embodiment of the present invention.
- FIG. 17 illustrates a method for indicating a trigger-based PPDU format according to an embodiment of the present invention.
- FIG. 18 shows an example of a UL MU operation according to an embodiment of the present invention.
- 19 illustrates end time alignment of a high priority frame according to an embodiment of the present invention.
- 20 shows another example of end time alignment of high priority frames according to an embodiment of the present invention.
- 21 shows another example of end time alignment of high priority frames according to an embodiment of the present invention.
- FIG. 22 is a diagram illustrating an example of a medium access recovery procedure according to an embodiment of the present invention.
- 23 is a diagram illustrating an example of signaling related to a multi-link element and MediumSyncDelay according to an embodiment of the present invention.
- 24 is a diagram illustrating an example of a MediumSyncDelay timer reset operation according to an embodiment of the present invention.
- 25 is a diagram illustrating an example of a MediumSyncDelay timer reset operation according to an embodiment of the present invention.
- 26 is a diagram illustrating an example of medium synchronization OFDM ED threshold subfield encoding according to an embodiment of the present invention.
- FIG. 27 is a diagram illustrating an example of a transmission operation when the MediumSyncDelay timer is not 0 according to an embodiment of the present invention.
- FIG. 28 is a diagram illustrating another example of a transmission operation when the MediumSyncDelay timer is not 0 according to an embodiment of the present invention.
- 29 is a diagram illustrating another example of a MediumSyncDelay timer reset operation according to an embodiment of the present invention.
- FIG. 30 is a diagram illustrating an example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- FIG. 31 is a diagram illustrating another example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- FIG. 32 is a diagram illustrating another example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- FIG 33 is a diagram illustrating another example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- 34 is a flowchart illustrating an example of an operation of a non-AP MLD according to an embodiment of the present invention.
- FIG. 1 shows a WLAN system according to an embodiment of the present invention.
- a wireless LAN system includes one or more basic service sets (BSS), and the BSS represents a set of devices that can successfully synchronize and communicate with each other.
- BSS basic service sets
- the BSS can be divided into an infrastructure BSS (infrastructure BSS) and an independent BSS (Independent BSS, IBSS), and FIG. 1 shows the infrastructure BSS.
- the infrastructure BSS (BSS1, BSS2) includes one or more stations (STA1, STA2, STA3, STA4, and STA5), an access point (AP-1) that is a station providing a distribution service, , AP-2), and a distribution system (DS) connecting a plurality of access points (AP-1, AP-2).
- BSS1, BSS2 includes one or more stations (STA1, STA2, STA3, STA4, and STA5), an access point (AP-1) that is a station providing a distribution service, , AP-2), and a distribution system (DS) connecting a plurality of access points (AP-1, AP-2).
- a station is an arbitrary device that includes a medium access control (MAC) conforming to the provisions of the IEEE 802.11 standard and a physical layer interface for a wireless medium, and in a broad sense is a non-access point ( It includes both access points (APs) as well as non-AP stations.
- MAC medium access control
- 'terminal' may refer to a non-AP STA or an AP, or may be used as a term indicating both.
- a station for wireless communication includes a processor and a communication unit, and may further include a user interface unit and a display unit according to embodiments.
- the processor may generate a frame to be transmitted through the wireless network or process a frame received through the wireless network, and may perform various other processes for controlling the station.
- the communication unit is functionally connected to the processor and transmits/receives a frame for a station through a wireless network.
- a terminal may be used as a term including a user equipment (UE).
- UE user equipment
- An access point is an entity that provides access to a distribution system (DS) via a wireless medium for stations associated with it. Although it is a principle that communication between non-AP stations in an infrastructure BSS is performed via an AP, direct communication is possible even between non-AP stations when a direct link is established. Meanwhile, in the present invention, an AP is used as a concept including a PCP (Personal BSS Coordination Point), and in a broad sense is a centralized controller, a base station (BS), a Node-B, a BTS (Base Transceiver System), or a site It may include all concepts such as a controller.
- PCP Personal BSS Coordination Point
- the AP may also be referred to as a base wireless communication terminal
- the base wireless communication terminal is a term that includes all of an AP, a base station, an eNodeB (eNB), and a transmission point (TP) in a broad sense.
- the base wireless communication terminal may include various types of wireless communication terminals that allocate communication medium resources and perform scheduling in communication with a plurality of wireless communication terminals.
- a plurality of infrastructure BSSs may be interconnected through a distribution system (DS).
- DS distribution system
- ESS Extended Service Set
- FIG. 2 illustrates an independent BSS that is a WLAN system according to another embodiment of the present invention.
- redundant descriptions of parts identical to or corresponding to those of the embodiment of FIG. 1 will be omitted.
- BSS3 shown in FIG. 2 is an independent BSS and does not include an AP, all stations STA6 and STA7 are not connected to the AP.
- An independent BSS is not allowed access to the distribution system and forms a self-contained network.
- each of the stations STA6 and STA7 may be directly connected to each other.
- a station 100 may include a processor 110, a communication unit 120, a user interface unit 140, a display unit 150, and a memory 160.
- the communication unit 120 transmits/receives wireless signals such as wireless LAN packets, and may be built into the station 100 or provided externally.
- the communication unit 120 may include at least one communication module using different frequency bands.
- the communication unit 120 may include communication modules of different frequency bands such as 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz.
- the station 100 may include a communication module using a frequency band of 7.125 GHz or higher and a communication module using a frequency band of 7.125 GHz or lower.
- Each communication module may perform wireless communication with an AP or an external station according to the wireless LAN standard of the frequency band supported by the corresponding communication module.
- the communication unit 120 may operate only one communication module at a time or simultaneously operate multiple communication modules according to the performance and requirements of the station 100 .
- each communication module may be provided in an independent form, or a plurality of modules may be integrated into a single chip.
- the communication unit 120 may represent an RF communication module that processes a Radio Frequency (RF) signal.
- RF Radio Frequency
- the user interface unit 140 includes various types of input/output means provided in the station 100 . That is, the user interface unit 140 may receive user input using various input means, and the processor 110 may control the station 100 based on the received user input. In addition, the user interface unit 140 may perform output based on the command of the processor 110 using various output means.
- the display unit 150 outputs an image on the display screen.
- the display unit 150 may output various display objects such as content executed by the processor 110 or a user interface based on a control command of the processor 110 .
- the memory 160 stores control programs used in the station 100 and various data corresponding thereto.
- Such a control program may include an access program necessary for the station 100 to access an AP or an external station.
- the processor 110 of the present invention may execute various commands or programs and process data inside the station 100 .
- the processor 110 may control each unit of the above-described station 100 and may control data transmission/reception between units.
- the processor 110 may execute a program for accessing an AP stored in the memory 160 and receive a communication setting message transmitted by the AP.
- the processor 110 may read information about the priority condition of the station 100 included in the communication establishment message and request access to the AP based on the information about the priority condition of the station 100 .
- the processor 110 of the present invention may refer to the main control unit of the station 100, and may refer to a control unit for individually controlling some components of the station 100, such as the communication unit 120, according to embodiments.
- the processor 110 may be a modem or a modulator and/or demodulator for modulating and demodulating a radio signal transmitted/received from the communication unit 120 .
- the processor 110 controls various operations of radio signal transmission/reception of the station 100 according to an embodiment of the present invention. A specific embodiment for this will be described later.
- the station 100 shown in FIG. 3 is a block diagram according to an embodiment of the present invention, and the separately displayed blocks logically distinguish the elements of the device. Accordingly, the elements of the device described above may be mounted as one chip or as a plurality of chips according to the design of the device. For example, the processor 110 and the communication unit 120 may be integrated into one chip or implemented as a separate chip. Also, in the embodiment of the present invention, some components of the station 100, such as the user interface unit 140 and the display unit 150, may be selectively provided in the station 100.
- the AP 200 may include a processor 210, a communication unit 220, and a memory 260.
- the AP 200 in FIG. 4 redundant descriptions of components identical to or corresponding to those of the station 100 in FIG. 3 will be omitted.
- the AP 200 includes a communication unit 220 for operating a BSS in at least one frequency band.
- the communication unit 220 of the AP 200 may also include a plurality of communication modules using different frequency bands. That is, the AP 200 according to an embodiment of the present invention may include two or more communication modules among different frequency bands, for example, 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz.
- the AP 200 may include a communication module using a frequency band of 7.125 GHz or higher and a communication module using a frequency band of 7.125 GHz or lower.
- Each communication module may perform wireless communication with a station according to a wireless LAN standard of a frequency band supported by the corresponding communication module.
- the communication unit 220 may operate only one communication module at a time or simultaneously operate multiple communication modules according to the performance and requirements of the AP 200 .
- the communication unit 220 may represent an RF communication module that processes a Radio Frequency (RF) signal.
- RF Radio Frequency
- the memory 260 stores a control program used in the AP 200 and various data corresponding thereto.
- a control program may include an access program that manages access of stations.
- the processor 210 may control each unit of the AP 200 and control data transmission/reception between the units.
- the processor 210 may execute a program for connection with a station stored in the memory 260 and transmit a communication setting message for one or more stations.
- the communication setting message may include information about priority conditions for connection of each station.
- the processor 210 performs connection setup according to the connection request of the station.
- the processor 210 may be a modem or a modulator and/or demodulator for modulating/demodulating a radio signal transmitted/received from the communication unit 220 .
- the processor 210 controls various operations of radio signal transmission/reception of the AP 200 according to an embodiment of the present invention. A specific embodiment for this will be described later.
- FIG. 5 schematically illustrates a process in which a station establishes a link with an access point.
- the scanning step is a step in which the STA 100 acquires access information of the BSS operated by the AP 200.
- a passive scanning method in which information is obtained by utilizing only a beacon message (S101) transmitted periodically by the AP 200, and a probe request by the STA 100 to the AP
- an active scanning method for obtaining access information by transmitting a probe request (S103) and receiving a probe response from an AP (S105).
- the STA 100 that has successfully received the radio access information in the scanning step transmits an authentication request (S107a), receives an authentication response from the AP 200 (S107b), and performs the authentication step do.
- the STA 100 transmits an association request (S109a), receives an association response from the AP 200 (S109b), and performs the association step.
- association basically means wireless association, but the present invention is not limited thereto, and association in a broad sense may include both wireless association and wired association.
- the authentication server 300 is a server that processes the STA 100 and 802.1X-based authentication, and may exist physically coupled to the AP 200 or may exist as a separate server.
- CSMA carrier sense multiple access
- CA collision avoidance
- a terminal performing wireless LAN communication checks whether a channel is busy by performing carrier sensing before transmitting data. If a radio signal of a certain strength or higher is detected, the corresponding channel is determined to be busy, and the terminal delays access to the corresponding channel. This process is called clear channel assessment (CCA), and a level for determining whether a corresponding signal is detected is called a CCA threshold. If a radio signal of a CCA threshold or higher received by the terminal makes the corresponding terminal a receiver, the terminal processes the received radio signal. Meanwhile, when no radio signal is detected in the corresponding channel or a radio signal having an intensity smaller than the CCA threshold is detected, the channel is determined to be in an idle state.
- CCA clear channel assessment
- each terminal with data to be transmitted performs a backoff procedure after a time such as IFS (Inter Frame Space), such as AIFS (Arbitration IFS) or PIFS (PCF IFS) according to the situation of each terminal. do.
- IFS Inter Frame Space
- AIFS Aribitration IFS
- PCF IFS PIFS
- the AIFS may be used as a configuration that replaces the existing DIFS (DCF IFS).
- DCF IFS DIFS
- Each terminal waits while decreasing the slot time as much as the random number determined for the corresponding terminal during the interval of the idle state of the channel, and the terminal that exhausts the slot time attempts access to the corresponding channel. do. In this way, a period in which each terminal performs a backoff procedure is referred to as a contention window period.
- a specific terminal successfully accesses the channel, the corresponding terminal can transmit data through the channel.
- each collided terminal receives a new random number and performs a backoff procedure again.
- a random number newly allocated to each terminal may be determined within a range (2*CW) twice the range (contention window, CW) of a random number previously allocated to the corresponding terminal.
- each terminal attempts access by performing the backoff procedure again in the next contention window period, and at this time, each terminal performs the backoff procedure from the remaining slot time in the previous contention window period. In this way, each terminal performing wireless LAN communication can avoid collision with each other on a specific channel.
- a terminal may be referred to as a non-AP STA, an AP STA, an AP, an STA, a receiving device, or a transmitting device, but the present invention is not limited thereto.
- an AP STA may be referred to as an AP.
- FIG. 7 illustrates an example of a PLCP Protocol Data Unit (PPDU) format for each standard generation. More specifically, FIG. 7(a) illustrates an embodiment of a legacy PPDU format based on 802.11a/g, FIG. 7(b) illustrates an embodiment of an HE PPDU format based on 802.11ax, and FIG. 7(c) illustrates an embodiment of a HE PPDU format based on 802.11ax. Illustrates an embodiment of a non-legacy PPDU (ie, EHT PPDU) format based on 802.11be. In addition, FIG. 7(d) shows detailed field configurations of L-SIG and RL-SIG commonly used in the PPDU formats.
- PPDU PLCP Protocol Data Unit
- the preamble of the legacy PPDU includes a legacy short training field (L-STF), a legacy long training field (L-LTF), and a legacy signal field (L-SIG).
- L-STF legacy short training field
- L-LTF legacy long training field
- L-SIG legacy signal field
- the L-STF, L-LTF and L-SIG may be referred to as a legacy preamble.
- the preamble of the HE PPDU includes a repeated legacy short training field (RL-SIG), a high efficiency signal A field (HE-SIG-A), and a high efficiency signal (HE-SIG-B) in the legacy preamble.
- B field HE-STF (High Efficiency Short Training field), and HE-LTF (High Efficiency Long Training field) are additionally included.
- the RL-SIG, HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF may be referred to as HE preambles.
- a specific configuration of the HE preamble may be modified according to the HE PPDU format. For example, HE-SIG-B can be used only in the HE MU PPDU format.
- the preamble of the EHT PPDU includes a repeated legacy short training field (RL-SIG), a universal signal field (U-SIG), and an extremely high throughput signal A field (EHT-SIG-A) in the legacy preamble.
- EHT-SIG-A Extremely High Throughput Signal B field
- EHT-STF Extremely High Throughput Short Training field
- EHT-LTF Extra High Throughput Long Training field
- the RL-SIG, EHT-SIG-A, EHT-SIG-B, EHT-STF, and EHT-LTF may be referred to as EHT preambles.
- a specific configuration of the non-legacy preamble may be modified according to the EHT PPDU format. For example, EHT-SIG-A and EHT-SIG-B may be used only in some of the EHT PPDU formats.
- L-SIG includes an L_RATE field and an L_LENGTH field.
- the L_RATE field consists of 4 bits and indicates the MCS used for data transmission.
- the L_RATE field is a combination of modulation schemes such as BPSK/QPSK/16-QAM/64-QAM and inefficiencies such as 1/2, 2/3, and 3/4. It represents one of the transmission rates of 36/48/54 Mbps.
- Combining the information of the L_RATE field and the L_LENGTH field can indicate the total length of the corresponding PPDU.
- the L_RATE field is set to the minimum rate of 6 Mbps.
- the unit of the L_LENGTH field is a byte, and a total of 12 bits are allocated to signal up to 4095, and the length of the corresponding PPDU can be indicated in combination with the L_RATE field.
- the legacy terminal and the non-legacy terminal may interpret the L_LENGTH field in different ways.
- a method for interpreting the length of a corresponding PPDU by a legacy terminal or a non-legacy terminal using the L_LENGTH field is as follows.
- 3 bytes ie, 24 bits
- 4us which is one symbol duration of 64FFT.
- the number of 64FFT reference symbols after L-SIG is obtained by adding 3 bytes corresponding to the SVC field and the Tail field to the value of the L_LENGTH field and dividing it by 3 bytes, which is the transmission amount of one symbol.
- the length of the PPDU that is, the reception time (RXTIME) is obtained by multiplying the number of obtained symbols by 4us, which is one symbol duration, and then adding 20us required for L-STF, L-LTF, and L-SIG transmission. If this is expressed as a formula, it is as shown in Equation 1 below.
- the length of the PPDU can be set up to 5.484 ms.
- a non-legacy terminal transmitting the corresponding PPDU must set the L_LENGTH field as shown in Equation 2 below.
- TXTIME is the total transmission time constituting the corresponding PPDU, as shown in Equation 3 below. At this time, TX represents the transmission time of X.
- the U-SIG Universal SIG
- EHT PPDUs and WLAN PPDUs of subsequent generations and serves to distinguish which generation PPDUs, including 11be, belong to.
- U-SIG is a 64FFT-based OFDM 2 symbol and can deliver a total of 52 bits of information. Among them, 43 bits, excluding 9 bits of CRC/Tail, are largely divided into a VI (Version Independent) field and a VD (Version Dependent) field.
- the VI bit maintains the current bit configuration in the future, so even if a PPDU of a subsequent generation is defined, the current 11be terminals can obtain information about the PPDU through the VI fields of the PPDU.
- the VI field consists of PHY version, UL/DL, BSS Color, TXOP, and Reserved fields.
- the PHY version field is 3 bits and serves to sequentially classify 11be and subsequent generation wireless LAN standards into versions. In the case of 11be, it has a value of 000b.
- the UL/DL field identifies whether the corresponding PPDU is an uplink/downlink PPDU.
- BSS Color means an identifier for each BSS defined in 11ax and has a value of 6 bits or more.
- TXOP means the Transmit Opportunity Duration that was delivered in the MAC header. By adding it to the PHY header, the length of the TXOP containing the PPDU can be inferred without the need to decode the MPDU and has a value of 7 bits or more.
- the VD field is signaling information useful only for the PPDU of the 11be version, and may consist of fields commonly used in any PPDU format, such as PPDU format and BW, and fields differently defined for each PPDU format.
- the PPDU format is a separator that distinguishes EHT SU (Single User), EHT MU (Multiple User), EHT TB (Trigger-based), and EHT ER (Extended Range) PPDU.
- the BW field consists of five basic PPDU BW options of 20, 40, 80, 160 (80 + 80), and 320 (160 + 160) MHz (the BW that can be expressed in the exponential form of 20 * 2 can be called the basic BW.
- the punctured and modified channel shape may be signaled directly in the BW field or signaled using the BW field and a field appearing after the BW field (eg, a field in the EHT-SIG field) together. If the BW field is 3 bits, a total of 8 BWs can be signaled, so only 3 can be signaled in the puncturing mode. If the BW field is set to 4 bits, since a total of 16 BW signaling is possible, a maximum of 11 BWs can be signaled in the puncturing mode.
- the field located after the BW field depends on the type and format of the PPDU, and the MU PPDU and SU PPDU can be signaled in the same PPDU format.
- a field for distinguishing the MU PPDU and SU PPDU is located before the EHT-SIG field. It can be done, and additional signaling for this can be performed.
- Both the SU PPDU and the MU PPDU include the EHT-SIG field, but some fields not required in the SU PPDU may be compressed. In this case, the information of the compressed field may be omitted or may have a size reduced from the size of the original field included in the MU PPDU. For example, in the case of the SU PPDU, a common field of the EHT-SIG may be omitted or replaced, or a user specific field may be replaced or reduced to one.
- the SU PPDU may further include a compression field indicating whether to compress or not, and some fields (eg, an RA field) may be omitted depending on the value of the compression field.
- a compression field indicating whether to compress or not
- some fields eg, an RA field
- the EHT-SIG field of the SU PPDU When part of the EHT-SIG field of the SU PPDU is compressed, information to be included in the compressed field may be signaled together in an uncompressed field (eg, common field, etc.).
- the EHT-SIG field since it is a PPDU format for simultaneous reception by multiple users, the EHT-SIG field must necessarily be transmitted after the U-SIG field, and the amount of signaled information can be variable. That is, since a plurality of MU PPDUs are transmitted to a plurality of STAs, each STA must recognize the location of the RU to which the MU PPDU is transmitted, the STA to which each RU is assigned, and whether the transmitted MU PPDU has been transmitted to itself.
- the AP must include the above information in the EHT-SIG field and transmit it.
- the U-SIG field signals information for efficiently transmitting the EHT-SIG field, which may be the number of symbols of the EHT-SIG field and/or MCS, which is a modulation method.
- the EHT-SIG field may include size and location information of an RU allocated to each user.
- the AP may include and transmit information on punctured RUs among RUs allocated to the STA in the SU PPDU (eg, a puncturing pattern of the RUs). That is, in the case of the SU PPDU, the puncturing mode field including information indicating whether the puncturing mode is applied and the puncturing pattern in a bitmap format may be included in the EHT-SIG field. The shape of the discontinuous channel may be signaled.
- the type of the signaled discontinuous channel is limited, and indicates the BW of the SU PPDU and information about the discontinuous channel in combination with the value of the BW field.
- the STA can recognize the bandwidth allocated to it through the BW field included in the PPDU, and the U-SIG field or EHT-SIG field included in the PPDU A punctured resource among allocated bandwidths can be recognized through the puncturing mode field of .
- the terminal can receive the PPDU in the remaining resource units except for the specific channel of the punctured resource unit.
- the plurality of RUs allocated to the STA may be configured in different frequency bands or tones.
- the reason why only a limited type of discontinuous channel type is signaled is to reduce the signaling overhead of the SU PPDU. Since puncturing can be performed for each 20 MHz subchannel, if puncturing is performed on a BW that has multiple 20 MHz subchannels, such as 80, 160, and 320 MHz, in the case of 320 MHz, the remaining 20 MHz subchannels except for the primary channel
- the type of discontinuous channel (when only the edge 20 MHz is punctured is regarded as discontinuous) must be signaled by expressing whether or not 15 are used. As such, allocating 15 bits to signal the discontinuous channel type of single user transmission may act as an excessively large signaling overhead considering the low transmission rate of the signaling part.
- the present invention proposes a method for signaling the form of a discontinuous channel of an SU PPDU, and shows the form of the form of a form of a form of a non-contiguous channel determined according to the proposed method.
- a method for signaling each of the primary 160 MHz and secondary 160 MHz puncturing types in the 320 MHz BW configuration of the SU PPDU, we propose a method for signaling each of the primary 160 MHz and secondary 160 MHz puncturing types.
- an embodiment of the present invention proposes a technique of changing the configuration of PPDUs indicated by preamble puncturing BW values according to the PPDU format signaled in the PPDU format field.
- the length of the BW field is 4 bits
- 1 symbol of EHT-SIG-A is additionally signaled after U-SIG or EHT-SIG-A is not signaled at all. Therefore, in consideration of this, it is necessary to signal up to 11 puncturing modes completely through only the BW field of the U-SIG.
- EHT MU PPDU since the EHT-SIG-B is additionally signaled after the U-SIG, up to 11 puncturing modes can be signaled in a different way from the SU PPDU.
- EHT ER PPDU it is possible to signal whether the PPDU uses the 20 MHz or 10 MHz band by setting the BW field to 1 bit.
- SIG-B which is a signaling field for simultaneous reception by multiple users, is essential, and SIG-B can be transmitted without a separate SIG-A after U-SIG.
- U-SIG needs to signal information for decoding SIG-B.
- EHT Extremely High Throughput
- a PPDU may consist of a preamble and a data part, and the format of one type of EHT PPDU may be distinguished according to the U-SIG field included in the preamble. Specifically, whether the format of the PPDU is the EHT PPDU may be indicated based on the PPDU format field included in the U-SIG field.
- the EHT SU PPDU is a PPDU used for single user (SU) transmission between an AP and a single STA, and an EHT-SIG-A field for additional signaling may be located after the U-SIG field.
- FIG. 8 shows an example of an EHT Trigger-based PPDU format, which is an EHT PPDU transmitted based on a trigger frame.
- the EHT trigger-based PPDU is an EHT PPDU transmitted based on a trigger frame and is an uplink PPDU used for a response to the trigger frame.
- the EHT-SIG-A field is not located after the U-SIG field.
- FIG. 8 shows an example of an EHT MU PPDU format that is an EHT PPDU for multiple users.
- the EHT MU PPDU is a PPDU used to transmit a PPDU to one or more STAs.
- the HE-SIG-B field may be located after the U-SIG field.
- EHT ER SU PPDU shows an example of an EHT ER SU PPDU format used for single user transmission with an STA in an extended range.
- the EHT ER SU PPDU can be used for single-user transmission with STAs in a wider range than the EHT SU PPDU described in (a) of FIG. 8, and the U-SIG field can be repeatedly located on the time axis.
- the EHT MU PPDU described in (c) of FIG. 8 can be used by an AP for downlink transmission to a plurality of STAs.
- the EHT MU PPDU may include scheduling information so that a plurality of STAs can simultaneously receive the PPDU transmitted from the AP.
- the EHT MU PPDU may deliver AID information of a receiver and/or sender of the PPDU transmitted through a user specific field of the EHT-SIG-B to the STA. Accordingly, a plurality of terminals receiving the EHT MU PPDU may perform a spatial reuse operation based on the AID information of the user specific field included in the preamble of the received PPDU.
- the resource unit allocation (RA) field of the HE-SIG-B field included in the HE MU PPDU is a configuration of resource units in a specific bandwidth (eg, 20 MHz, etc.) of the frequency axis (eg, , a division type of a resource unit) may be included. That is, the RA field may indicate the configuration of resource units divided in the bandwidth for transmission of the HE MU PPDU in order for the STA to receive the PPDU.
- Information on the STA allocated (or designated) to each divided resource unit may be included in a user specific field of the EHT-SIG-B and transmitted to the STA. That is, the user specific field may include one or more user fields corresponding to each divided resource unit.
- a user field corresponding to at least one resource unit used for data transmission among a plurality of divided resource units may include an AID of a receiver or sender, and the remaining resource units not performed for data transmission ( s) may include a preset null STA ID.
- Two or more PPDUs shown in FIG. 8 may be indicated with values indicating the same PPDU format. That is, two or more PPDUs may be indicated in the same PPDU format through the same value.
- the EHT SU PPDU and the EHT MU PPDU may be indicated with the same value through the U-SIG PPDU format subfield.
- the EHT SU PPDU and the EHT MU PPDU may be distinguished by the number of STAs receiving the PPDU. For example, a PPDU received by only one STA may be identified as an EHT SU PPDU, and if the number of STAs is configured to be received by two or more STAs, it may be identified as an EHT MU PPDU.
- two or more PPDU formats shown in FIG. 8 may be indicated through the same subfield value.
- some fields or some information of fields may be omitted, and a case in which some fields or some information of fields are omitted may be defined as compression mode or compressed mode.
- FIG. 9 is a diagram illustrating a multi-link device according to an embodiment of the present invention.
- the concept of a device to which one or more STAs are affiliated may be defined.
- devices to which more than one (ie, two or more) STAs are affiliated may be defined.
- the device may be a logical concept. Therefore, devices to which one or more or more STAs of this concept are affiliated are multi-link devices (MLD), multi-band devices, or multi-link logical entities (multi-link logical entities: MLLE).
- MLD multi-link devices
- multi-band devices multi-band devices
- multi-link logical entities multi-link logical entities
- the devices of the above concept may be referred to as a multi-link entity (MLE).
- MLE multi-link entity
- the MLD may have one MAC medium access control service access point (SAP) up to a logical link control (LLC), and the MLD may have one MAC data service.
- SAP medium access control service access point
- LLC logical link control
- STAs included in the MLD can operate in one or more links or channels. That is, STAs included in the MLD can operate in a number of different channels. For example, STAs included in the MLD can operate using channels of different frequency bands of 2.4 GHz, 5 GHz, and 6 GHz. Through this, the MLD can obtain gains in channel access and increase the performance of the entire network. Existing wireless LANs operated with a single link, but MLD operation uses multiple links to obtain more channel access opportunities, or STAs can operate efficiently in multiple links in consideration of channel conditions. .
- the MLDs affiliated with the APs may be AP MLDs.
- the STAs affiliated with the MLD are non-AP STAs
- the MLD affiliated with the non-APs may be a non-AP MLD.
- an AP multi-link device may be a device including one or more wireless access points (APs), and may be a device connected through one interface as a higher layer. That is, the AP MLD may be connected to a Logical Link Control (LLC) layer through one interface. Multiple APs included in an AP MLD may share some functions in the MAC layer. Each AP in the AP MLD can operate on different links.
- the STA MLD may be a device including one or more non-AP STAs, and may be a device connected to a higher layer through one interface.
- the STA MLD may be connected to the LLC layer through one interface. Several STAs included in the STA MLD may share some functions in the MAC layer. Also, the STA MLD may be referred to as a non-AP MLD.
- the AP MLD and the STA MLD may perform a multi-link operation of communicating using a plurality of individual links. That is, when an AP MLD includes several APs, each AP may configure a separate link and perform frame transmission/reception operations using multiple links with each terminal included in the STA MLD. In this case, each link may operate in a 2.4 GHz, 5 GHz, or 6 GHz band, and each link may perform a bandwidth extension operation.
- frame transmission can be performed with a bandwidth of 40 MHz through a bandwidth extension method in the 2.4 GHz band.
- frame transmission can be performed with a bandwidth of up to 320 MHz by utilizing non-contiguous bandwidth.
- STR Simultaneous Transmit and Receive
- the AP MLD may be capable of STR operation for all links.
- the STR operation may be impossible in some links of the AP MLD.
- a terminal MLD capable of the STR operation may be connected to the AP MLD, and an MLD incapable of the STR operation for some or all links may be connected.
- a terminal not belonging to the MLD eg, an IEEE 802.11a/b/g/n/ac/ax terminal
- the AP MLD and the STA MLD may perform a negotiation process for a multi-link use operation in the scanning and access process described in FIG. 5 .
- the AP included in the AP MLD may transmit a beacon frame including an indicator indicating that multi-link operation is available, the number of available links, and information on a plurality of available links.
- the UE belonging to the STA MLD may include and transmit an indicator indicating that multi-link operation is available in the probe request frame, and the AP belonging to the AP MLD may transmit the probe response frame indicating that multi-link operation is available Can contain directives.
- the AP may additionally include and transmit the number of available links and link information during multi-link operation.
- the STA MLD that has checked the multi-link operation of the AP MLD and used link information may perform an access process with the AP MLD.
- the AP MLD and STA MLD may start a negotiation process for multi-link operation.
- the negotiation process for the multi-link operation may be performed during an access process between an AP belonging to an AP MLD and a terminal belonging to an STA MLD. That is, an indicator indicating that a terminal belonging to the STA MLD (eg, STA1) can use multi-link operation of the terminal while sending an access request frame to any AP belonging to the AP MLD (eg, AP1) and a request indicator requesting to perform a multi-link operation.
- the AP receiving the access request frame from the terminal can check an indicator requesting multi-link operation, and if the AP is capable of multi-link operation, including link information to be used for multi-link operation and parameters used in each link, An access response frame allowing multi-link operation may be transmitted to the corresponding terminal.
- the parameter for the multi-link operation may include one or more of a band of each link used, a bandwidth extension direction, a target beacon transmission time (TBTT), and whether or not the STR operates.
- the access request frame and the response frame are exchanged and the AP MLD and the STA MLD for which the use of the multi-link operation is confirmed. After the access process, multiple APs included in the AP MLD and multiple terminals included in the STA MLD are used to access multiple links.
- the used frame transfer operation can be performed.
- an MLD including multiple STAs may exist, and multiple STAs included in the MLD may operate in multiple links.
- MLD including APs AP1, AP2, and AP3 may be referred to as AP MLD
- MLD including non-AP STAs non-AP STA1, non-AP STA2, and non-AP STA3 may be referred to as non-AP MLD
- can be said STAs included in the MLD may operate on Link 1 (Link 1), Link 2 (Link 2), Link 3 (Link 3), or some of Links 1 to 3.
- a multi-link operation may include a multi-link setup operation.
- a multi-link configuration operation may be an operation corresponding to an association performed in a single link operation.
- multi-link configuration may have to be preceded.
- a multi-link setup operation may be performed using a multi-link setup element.
- the multi-link configuration element may include capability information related to multiple links, and the capability information enables an STA included in the MLD to receive a frame through a certain link and at the same time another STA included in the MLD to receive a frame through another link. It may include information related to whether the frame can be transmitted.
- the capability information may include information related to whether STAs (non-AP STAs) and/or APs (or AP STAs) can simultaneously transmit/receive frames in different transmission directions through links included in the MLD.
- the capability information may further include information related to a usable link or an operating channel Multi-link configuration may be configured through negotiation between peer STAs, Multi-link operation can be set through one link.
- a mapping relationship may exist between links of TID and MLD. For example, when a TID and a link are mapped, the TID may be transmitted through the mapped link. Mapping between TIDs and links may be performed through a directional-based transmission direction. For example, mapping may be performed for each of both directions between MLD1 and MLD2. In addition, a default setting may exist for mapping between TID and link. For example, mapping between TIDs and links may basically be all TIDs mapped to a certain link.
- FIG. 10 is a diagram illustrating an example of a TID-to-link mapping method according to an embodiment of the present invention.
- a mapping relationship between a TID and a link may exist.
- the mapping relationship between TID and link may be referred to as TID-to-link mapping, TID to link mapping, TID mapping, link mapping, and the like.
- TID may be a traffic identifier.
- the TID may be an ID (identifier) for classifying traffic, data, and the like to support quality of service (QoS).
- QoS quality of service
- the TID may be an ID used or allocated in a layer higher than the MAC layer.
- TID can represent traffic categories (TC) and traffic streams (TS).
- the TID can be 16 values, and can be represented by values from 0 to 15, for example.
- the TID value used is different according to the access policy, channel access, or medium access method. For example, when using EDCA (hybrid coordination function (HCF) contention based channel access, enhanced distributed channel access), possible TID values may be 0 to 7.
- EDCA hybrid coordination function
- the TID value may indicate user priority (UP), and the UP may relate to TC or TS.
- UP may be a value assigned in a higher layer than MAC.
- possible TID values may be 8 to 15.
- the TID may indicate a TSID.
- possible TID values may be 8 to 15.
- the TID may indicate a TSID.
- AC may be a label for providing QoS in EDCA or a label indicating a set of EDCA parameters.
- An EDCA parameter or a set of EDCA parameters may be used for channel connection.
- AC may be used by QoS STAs.
- the value of AC can be set to one of AC_BK, AC_BE, AC_VI, and AC_VO.
- AC_BK, AC_BE, AC_VI, and AC_VO may represent background, best effort, video, and voice, respectively. It is also possible to subdivide AC_BK, AC_BE, AC_VI, and AC_VO.
- AC_VI can be subdivided into AC_VI primary and AC_VI alternate.
- AC_VO can be subdivided into AC_VO primary and AC_VO alternate.
- the UP value or the TID value may be mapped with the AC value.
- UP values or TID values of 1, 2, 0, 3, 4, 5, 6, and 7 may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI, AC_VI, AC_VO, and AC_VO, respectively.
- the UP values or TID values 1, 2, 0, 3, 4, 5, 6, and 7 may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI alternate, AC_VI primary, AC_VO primary, and AC_VO alternate, respectively.
- UP values or TID values 1, 2, 0, 3, 4, 5, 6, and 7 may have high priority in order. That is, 1 may be a low priority, and 7 may be a high priority.
- priority may be increased in the order of AC_BK, AC_BE, AC_VI, and AC_VO.
- AC_BK, AC_BE, AC_VI, and AC_VO may correspond to AC index (ACI) 0, 1, 2, and 3, respectively.
- the TID-to-link mapping of the present invention can also be a mapping relationship between an AC and a link.
- the TID is mapped may mean that the AC is mapped, or vice versa.
- a TID mapped to each link of multi-link may exist.
- this mapping can be defined separately for each bi-directional link.
- mapping between TID and link may have a default setting.
- mapping between TIDs and links may basically be all TIDs mapped to a certain link.
- a certain TID or a certain AC may be mapped with at least one link at a specific time point.
- the management frame or control frame may be transmitted on all links.
- a Data frame corresponding to a TID or AC mapped to a certain direction of a link can be transmitted. Also, a Data frame corresponding to a TID or AC that is not mapped to a certain direction of the link may not be transmitted.
- TID-to-link mapping may also be applied to acknowledgment.
- block ack agreement may be based on TID-to-link mapping.
- TID-to-link mapping may be based on block ack agreement.
- TID-to-link mapping it is possible to provide QoS service by performing TID-to-link mapping. For example, by mapping an AC and TID with a high priority to a link with good channel conditions or few STAs, it is possible to quickly transmit data of the corresponding AC and TID. Alternatively, by performing TID-to-link mapping, it is possible to help an STA of a specific link to perform power save (or go to a doze state).
- an AP MLD including AP 1 and AP 2 may exist.
- a Non-AP MLD including STA 1 and STA 2 may exist.
- Link 1 and Link 2 which are multiple links, may exist in the AP MLD.
- AP 1 and STA 1 may be associated in Link 1
- AP 2 and STA 2 may be associated in Link 2.
- Link 1 may include a link transmitted from AP 1 to STA 1 and/or a link transmitted from STA 1 to AP 1
- Link 2 may include a link transmitted from AP 2 to STA 2 and/or a link transmitted from STA 2 It may include a link transmitted to AP 2.
- each link may have a TID and/or an AC mapped thereto.
- all TIDs and all ACs may be mapped to a link transmitted from AP 1 to STA 1 in Link 1 and a link transmitted from STA 1 to AP 1 in Link 1.
- only a TID corresponding to AC_VO or AC_VO may be mapped to a link transmitted from STA 2 to AP 2 in Link 2.
- data of TID or AC not mapped to a link cannot be transmitted on a corresponding link.
- FIG. 11 is a diagram illustrating an example of a multi-link NAV configuration operation according to an embodiment of the present invention.
- Simultaneous transmission and reception (STR; simultaneous transmit and receive) of the MLD may be limited, which may be associated with a frequency interval between multiple links operating as multi-links.
- simultaneous transmission or reception is limited when the interval between links is m MHz, and simultaneous transmission or reception is not restricted when the interval between links is n MHz for n greater than m. there is.
- This embodiment may be for solving a problem of limiting simultaneous transmission or reception, and redundant descriptions may be omitted.
- duration information may be shared between links operating in multiple links.
- the duration information may be TXOP duration information transmitted in a signaling field of a preamble.
- the signaling field may be the previously described U-SIG field.
- the signaling field may be the previously described HE-SIG-A field.
- the duration information may be duration information indicated by a Duration/ID field included in the MAC header.
- the period information may be period information indicated by a Length field (L Length field) included in the L-SIG field.
- the period information indicated by the U-SIG field, HE-SIG-A, or Duration/ID field may be a value indicating the TXOP duration.
- the duration information indicated by the L-SIG field may be a value indicating the length of a physical layer protocol data unit (PPDU) including the L-SIG field or the end of the PPDU including the L-SIG field. there is.
- PPDU physical layer protocol data unit
- a method of limiting transmission or channel access may include setting a NAV.
- the NAV may be reset to resume transmission or channel access.
- the NAV may be an intra-BSS NAV.
- Intra-BSS NAV may be a NAV set by an intra-BSS frame (or PPDU). That is, an STA belonging to an MLD may set an NAV based on a frame (or PPDU) directed to another STA belonging to the MLD.
- an inter-link NAV may exist.
- Inter-link NAV may be a NAV used by STAs of multiple links belonging to an MLD when operating in multiple links. For example, transmission may not be performed on link 2 based on an inter-link NAV set based on period information received on link 1.
- inter-link NAVs exist or can be used for MLDs that cannot be STRed. For example, when an inter-link NAV is set, the MLD with the corresponding inter-link NAV may not perform transmission or channel access on multiple links (or all links used by the MLD).
- basic NAV may exist as a type of NAV in addition to intra-BSS NAV.
- the basic NAV may be an NAV set by an inter-BSS frame (or PPDU), and a basic NAV may also be set by a frame (or PPDU) that does not determine whether it is intra-BSS or inter-BSS.
- inter-link NAV When inter-link NAV is separately used, compared to the case where inter-link NAV is not used, an advantage can be obtained in a situation where NAV settings are updated. For example, a situation in which it is okay to reset the NAV set by another link may occur. For example, although an inter-link NAV is set based on a certain frame (or PPDU), it may be okay to reset the set inter-link NAV after determining that the frame (or PPDU) is not directed to the same MLD. When there are MLDs operating on link 1 and link 2, the NAV for link 1 may be set based on the frame received on link 1. Afterwards, the NAV of link 1 may be updated based on the frame of link 2.
- the NAV information set based on the frame received in link 1 may be lost. If the inter-link NAV is used together with the NAV for each link, this problem can be solved because the NAV for each link can be maintained even if the inter-link NAV is reset.
- NAV is set as an example in the embodiment of the present invention
- the embodiment of the present invention is not limited thereto, and may be applied to instructing the physical layer to stop accessing a channel or instructing the channel state to be busy.
- it is not limited to resetting the NAV, and may be applied to instructing the physical layer to continue channel access or instructing the channel state to idle.
- a primitive exchanged between the physical layer and the MAC layer may be used.
- a primitive exchanged between one STA and another STA of the MLD may be used.
- primitives exchanged between one MAC layer of the MLD and another MAC layer may be used.
- an STA belonging to an MLD when an STA belonging to an MLD starts receiving a PPDU, another STA belonging to the MLD may have to stop accessing a channel.
- channel access can be stopped based on the received duration information, but due to the position of the field containing duration information or the time required for decoding, etc., there may be a period of time from the start of PPDU reception to acquisition of duration information. . Therefore, if the channel is accessed and transmission is started during this time, the aforementioned problem may occur. Therefore, according to an embodiment of the present invention, an STA of an MLD may stop accessing a channel from the time when another STA of the MLD starts reception. In addition, if it is confirmed that the received frame is not directed to the other STA after the other STA of the MLD starts receiving, channel access may be restarted.
- FIG. 12 is a diagram illustrating another example of a multi-link NAV configuration operation according to an embodiment of the present invention.
- stopping channel access or transmission may include operations such as setting (updating) a NAV, determining a channel as busy, or stopping CCA.
- resuming channel access or transmission may include operations such as resetting the NAV, canceling the NAV setting, determining the channel as idle, or performing CCA.
- this operation may be indicated as stopping and resuming channel access.
- STA 1 and STA 2 belong to the MLD, and STA 1 and STA 2 operate in Link 1 and Link 2, respectively.
- frame and PPDU can be used together to indicate.
- the NAV at this time may be an intra-BSS NAV or an inter-link NAV as described in FIG. 11.
- STA 2 when STA 1 starts receiving frames, STA 2 may stop accessing the channel. In addition, when STA 1 obtains duration information from L-SIG, STA 2 may continue to stop channel access. At this time, the state in which STA 2 has stopped accessing the channel may be determined as the end of the frame received by STA 1. In addition, when STA 1 fails to correctly decode the L-SIG (invalid L-SIG), STA 2 may resume channel access.
- STA 1 may have received the TXOP duration and BSS color from the U-SIG of the frame received. If the received BSS color indicates intra-BSS or if the BSS color is a BSS color corresponding to STA 1, channel access can be stopped. In one embodiment, the period during which channel access is stopped may be until the end of the received frame. In this case, there is an advantage in that channel access can be started more quickly after the received frame ends. In another embodiment, the period for stopping channel access at this time may be a TXOP duration. In this case, the period of interrupted channel access may be updated based on the L-SIG. In this case, there is an advantage in that the sequence following the received frame can be better protected.
- STA 1 has received the TXOP duration and BSS color from the U-SIG of the received frame, and the received BSS color indicates that it is not intra-BSS, or the BSS color may not be the BSS color corresponding to STA 1. there is. Alternatively, there may be a case where STA 1 fails to successfully decode the U-SIG. In this case, STA 2 may resume channel access.
- STA 2 may resume channel access. For example, if the PHY identifier obtained from the U-SIG is an ID corresponding to a future standard or an unrecognized ID, STA 2 may resume channel access.
- HE-SIG-A may include TXOP duration and BSS color, and accordingly, the same operation as described above may be performed.
- the STA-ID may have been received from the EHT-SIG of the frame received by STA 1. If the received STA-ID is an indicator that STA 1 should receive, for example, STA-ID indicates STA 1, STA-ID indicates a group to which STA 1 belongs, or STA-ID indicates broadcast, STA 2 may continue to interrupt channel access.
- the STA-ID may be received from the EHT-SIG of the frame received by STA 1. If the received STA-ID is an indicator that does not correspond to STA 1, for example, the STA-ID does not indicate an indicator corresponding to STA 1, the STA-ID does not indicate a group to which STA 1 belongs, and the STA-ID broadcasts If not indicated, STA 2 may resume channel access. Alternatively, even when STA 1 fails to successfully decode the EHT-SIG, STA 2 may resume channel access.
- HE-SIG-B may include STA-ID, and accordingly, the same operation as described above may be performed.
- the MAC header of the frame received by STA 1 may have been received. If RA (receiver address) or DA (destination address) included in the received MAC header indicates a value that STA 1 should receive, for example, RA or DA indicates STA 1 or a group to which STA 1 belongs Or, if the STA-ID indicates broadcast, STA 2 may continue to stop accessing the channel. At this time, the period of the interrupted channel access may be based on duration information included in the received MAC header. More specifically, the duration of the interrupted channel access may be based on duration information indicated by the Duration/ID field included in the received MAC header.
- the MAC header of the frame received by STA 1 may have been received. If the RA or DA included in the received MAC header is an indicator that does not correspond to STA 1, for example, if the RA or DA does not indicate an indicator corresponding to STA 1, does not indicate a group to which STA 1 belongs, and does not indicate broadcast , STA 2 may resume channel access. Alternatively, STA 1 may not receive all MAC headers. For example, STA 1 may fail to receive all MPDUs included in the A-MPDU. In this case, STA 2 may resume channel access.
- the channel access interruption and resumption described in FIG. 12 may operate sequentially in the order of decoding as STA 1 starts receiving frames (or PPDUs) and sequentially decodes them.
- the order of decoding may be based on PPDU format, frame format, and the like. For example, it can be decoded in order of L-SIG, U-SIG, EHT-SIG, MAC header (in case of EHT PPDU).
- L-SIG, HE-SIG-A, and MAC headers can be decoded in order (in the case of HE SU PPDU and HE TB PPDU).
- decoding may be performed in the order of L-SIG, HE-SIG-A, HE-SIG-B, and MAC header (in case of HE MU PPDU). Alternatively, it can be decoded in the order of L-SIG and MAC header (in case of 11a/g PPDU).
- the aforementioned STA-ID may be a value indicating an intended receiver of a PPDU or resource unit (RU).
- the STA-ID may be included in the EHT-SIG field or the HE-SIG-B field.
- the STA-ID can indicate a value corresponding to a single STA. For example, when a plurality of STAs are included in the MLD, the STA-ID may indicate a value corresponding to one STA among the plurality of STAs.
- the STA-ID may be a value based on the STA's AID or MAC address.
- FIG. 13 is a diagram illustrating an example of BSS classification and an operation based thereon according to an embodiment of the present invention.
- an STA can classify (or determine) a BSS based on a received frame or a received PPDU.
- Classifying the BSS may include an operation of classifying whether or not the received frame or the received PPDU corresponds to the BSS to which the classifying STA belongs.
- classifying the BSS may mean an operation of classifying whether or not the received frame or the received PPDU is transmitted from the BSS to which the classifying STA belongs.
- classifying the BSS may include an operation of classifying whether the received frame or the received PPDU corresponds to a BSS to which the STA to be classified does not belong.
- classifying the BSS may mean an operation of classifying whether or not the received frame or the received PPDU is transmitted from a BSS to which the STA that is classified does not belong.
- classifying the BSS may include an operation of classifying to which BSS the received frame or the received PPDU belongs.
- classifying the BSS may mean an operation of classifying from which BSS the received frame or the received PPDU is transmitted.
- a BSS to which an STA to classify belongs may be referred to as an intra-BSS.
- BSSs including the BSS to which the classifying STA belongs may be referred to as intra-BSSs.
- BSS other than intra-BSS may be referred to as inter-BSS.
- a BSS other than an intra-BSS may be an inter-BSS or an unclassified BSS.
- the inter-BSS may include BSSs that are not classified.
- a BSS to which the STA to be classified does not belong may be referred to as an inter-BSS.
- the received frame or the received PPDU when it is determined that the received frame or the received PPDU corresponds to an intra-BSS or is transmitted from an intra-BSS, the received frame or the received PPDU is referred to as an intra-BSS frame and an intra-BSS PPDU, respectively. can do.
- the received frame or the received PPDU when it is determined that the received frame or the received PPDU corresponds to the inter-BSS or is transmitted from the inter-BSS, the received frame or the received PPDU may be referred to as an inter-BSS frame and an inter-BSS PPDU, respectively.
- a PPDU including an intra-BSS frame may be an intra-BSS PPDU.
- a PPDU including an inter-BSS frame may be an inter-BSS PPDU.
- BSSs may be classified based on one or more BSS classification conditions. For example, BSSs may be classified according to whether at least one of the one or more BSS classification conditions is satisfied.
- the BSS classification condition may include a condition based on BSS color.
- BSS color may be an identifier for BSS.
- the BSS color can be included in the preamble of the PPDU, more specifically, in the signaling field (eg HE-SIG-A field, U-SIG field, or VHT-SIG-A field).
- the BSS color may be included in TXVECTOR transmitted from the sender's MAC layer to the PHY layer.
- the BSS color may be included in RXVECTOR transmitted from the receiver's PHY layer to the MAC layer. Parameters included in TXVECTOR and RXVECTOR may be called TXVECTOR parameter and RXVECTOR parameter, respectively.
- BSS color can be included in the TXVECTOR parameter or the RXVECTOR parameter.
- the BSS color set by the AP may be notified to STAs.
- the BSS may be classified based on the BSS color included in the received PPDU. If the BSS color included in the PPDU received by the STA is different from the BSS color of the BSS corresponding to the STA, the received PPDU may be classified as an inter-BSS PPDU. Alternatively, if the BSS color included in the PPDU received by the STA is different from the BSS color of the BSS corresponding to the STA and the value is not 0, the received PPDU may be classified as an inter-BSS PPDU. Also, if the BSS color included in the PPDU received by the STA is the same as the BSS color of the BSS corresponding to the STA, the received PPDU may be classified as an intra-BSS PPDU.
- the BSS classification condition may include a condition based on a MAC address.
- the MAC address may be included in the MAC header of the frame.
- the MAC address may include a receiver address (RA), a transmitter address (TA), a BSSID, a source address (SA), and a destination address (DA).
- the BSS may be classified based on the MAC address included in the received frame. If the MAC address included in the received frame is different from the BSSID of the BSS corresponding to the STA, the received frame may be classified as an inter-BSS frame. More specifically, if all of the MAC addresses included in the received frame are different from the BSSID of the BSS corresponding to the STA, the received frame may be classified as an inter-BSS frame.
- the received frame may be classified as an intra-BSS frame. More specifically, if at least one of the MAC addresses included in the received frame is the same as the BSSID of the BSS corresponding to the STA, the received frame may be classified as an intra-BSS frame.
- the corresponding BSS may include a BSS to which the STA is associated.
- the corresponding BSS may include a BSS included in the same multiple BSSID set as the BSS to which the STA is associated.
- the corresponding BSS may include a BSS included in the same co-hosted BSSID set as the BSS to which the STA is associated.
- information about one or more BSSs included in the same multiple BSSID set or the same co-hosted BSSID set may be transmitted through one frame.
- the BSS classification condition may include a condition based on a Partial AID field value included in the VHT PPDU.
- the Partial AID field may be included in the preamble of the VHT PPDU.
- the Partial AID field may be included in the VHT-SIG-A field included in the VHT PPDU.
- the Partial AID field can indicate a part of BSS color.
- the Partial AID field can represent a part of the BSS color.
- the Partial AID field can represent part of the BSS color.
- the AID assignment rule may be a method of allocating an AID based on BSS color.
- the Partial AID field can indicate part of the BSS color.
- the received PPDU is classified as an inter-BSS PPDU. can be classified.
- the Partial AID field of the received PPDU indicates part of the BSS color
- the received Partial AID field value is equal to part of the BSS color corresponding to the received STA
- the received PPDU can be classified as an intra-BSS PPDU.
- part of the BSS color is 4 LSBs of the BSS color.
- the Partial AID field can indicate a part of the BSSID. For example, when the Group ID field included in the VHT-SIG-A field of the VHT PPDU is a preset value (eg, when the Group ID field is set to 0), the Partial AID field can indicate part of the BSSID.
- the received PPDU when the Partial AID field of the received PPDU indicates a part of the BSSID, and the value of the Partial AID field is different from a part of the BSSID corresponding to the received STA, the received PPDU is classified as an inter-BSS PPDU.
- the received PPDU when the Partial AID field of the received PPDU indicates a part of the BSSID, the received PPDU can be classified as an intra-BSS PPDU when the value of the received Partial AID field is equal to a part of the BSSID corresponding to the received STA. Also, at this time, it is possible that a part of the BSSID is 9 MSBs of the BSSID.
- Partial AID field value can be included in the TXVECTOR parameter PARTIAL_AID or the RXVECTOR parameter PARTIAL_AID.
- the Group ID field value can be included in TXVECTOR parameter GROUP_ID or RXVECTOR parameter GROUP_ID.
- the BSS classification condition may include a condition for the AP to receive a PPDU under a preset condition.
- the PPDU of the preset condition may include a downlink PPDU.
- the downlink PPDU may include a VHT MU PPDU.
- the downlink PPDU may include a PPDU in which signaling indicating whether it is uplink or downlink is set to a preset value. Signaling indicating whether it is uplink or downlink can be included in the signaling field of the HE PPDU. Alternatively, signaling indicating whether it is an uplink or a downlink may be included in the U-SIG.
- U-SIG can be included in the EHT PPDU or the preamble of the PPDU following the EHT standard.
- intra-BSS PPDU intra-BSS PPDU or inter-BSS PPDU.
- condition for classification as an intra-BSS PPDU and the condition for classification as an inter-BSS PPDU are not satisfied, it may not be classified as an intra-BSS PPDU or inter-BSS PPDU.
- the result of the condition based on the BSS color and the result of the condition based on the MAC address do not match, the result of the condition based on the MAC address takes precedence or the result of the condition based on the MAC address determines the final result.
- the result of the condition based on the MAC address takes precedence or the result of the condition based on the MAC address determines the final result.
- both conditions for classification as an intra-BSS PPDU and conditions for classification as an inter-BSS PPDU are satisfied, it may be classified as an intra-BSS PPDU.
- the STA may perform an operation based on the classified BSS.
- An operation based on the classified BSS may include an intra-PPDU power save operation.
- the intra-PPDU power save operation may be a power save operation based on the received PPDU.
- a predetermined condition is satisfied, it is possible to perform an intra-PPDU power save operation.
- the preset condition may include a condition for classifying the received PPDU as an intra-BSS PPDU. Also, the preset condition may include a condition that the intended receiver of the received PPDU is not the STA that received the PPDU.
- the intended receiver of the PPDU may not be the STA that received the PPDU.
- the ID can be included in the preamble of the PPDU.
- the ID may be STA_ID included in the preamble of the PPDU.
- the STA_ID can be included in the HE MU PPDU or EHT PPDU.
- adderess may be the MAC address described above.
- the intended receiver of the PPDU may not be the STA that received the PPDU.
- the intended receiver of the PPDU may not be the STA that received the PPDU.
- Settings of the received PPDU may include MCS of the PPDU, number of spatial streams, channel width, and the like.
- PHY-RXEND.indication (UnsupportedRate) primitive may be received.
- the intended receiver of the PPDU may not be the STA that has received the PPDU.
- the preset format may include a TB PPDU.
- the TB PPDU may include HE TB PPDU and EHT TB PPDU.
- the TB PPDU may be a PPDU transmitted in response to a triggering frame.
- a triggering frame may include a trigger frame.
- the triggering frame may include a frame including triggering information. Triggering information can be included in a MAC header, for example, an A-control field.
- triggering information or information included in a trigger frame may include the length of a PPDU to respond, an RU to be used when responding, a PHY configuration to be used when responding, and a MAC configuration to be used when responding.
- the intra-PPDU power save operation may be an operation that can enter the doze state until the end of the received PPDU. In another embodiment, when it is determined that the intended receiver of the PPDU or frame received by the STA is not the STA, reception or decoding of the PPDU or frame may be stopped.
- An operation based on the classified BSS may include an operation of setting (or updating) a NAV.
- an STA it is possible for an STA to operate one or more NAVs.
- the STA receives a PPDU or frame, it is possible to set an NAV corresponding to a BSS classified based on the received PPDU or frame.
- the intra-BSS NAV may be an NAV corresponding to an intra-BSS PPDU.
- the basic NAV may be an NAV corresponding to a PPDU other than an intra-BSS PPDU.
- the basic NAV may be an NAV corresponding to an inter-BSS PPDU.
- the duration information may include TXOP.
- TXOP may mean a value included in the TXOP field.
- the TXOP field can be included in the preamble of the PPDU.
- the TXOP field can be included in the HE-SIG-A field of the HE PPDU.
- the TXOP field may be included in the U-SIG field of the EHT PPDU or the standard PPDU after EHT.
- the duration information may be included in a MAC header.
- the duration information may be included in a Duration/ID field included in a MAC header.
- An operation based on the classified BSS may include a spatial reuse operation.
- an operation based on the classified BSS may include a channel access operation.
- Spatial reuse operation may be a channel access operation.
- the preset condition may include a condition in which the received PPDU or the received frame corresponds to inter-BSS.
- the preset condition may include a condition in which the signal strength of the received PPDU or received frame is smaller than the threshold.
- the threshold can be variable.
- the threshold may be a threshold for OBSS PD-based spatial reuse operation.
- the threshold may be a value greater than or equal to the CCA threshold.
- the threshold may be a value based on power to be transmitted.
- the spatial reuse operation may include an operation of transmitting a PPDU.
- the spatial reuse operation may include an operation of resetting the PHY.
- an operation of resetting the PHY may be an operation of issuing a PHY-CCARESET.request primitive.
- the spatial reuse operation may include an operation of not setting an NAV based on a received PPDU or a received frame. If an STA performs a spatial reuse operation, it may be possible for the STA to transmit a PPDU while a received PPDU or a received frame is being transmitted or received.
- BSS A and BSS B may exist, and BSS A and BSS B may be different BSSs. Also, BSS A and BSS B may correspond to each other as inter-BSS. That is, a PPDU or frame transmitted from BSS B by an STA associated with BSS A may be classified as an inter-BSS PPDU or inter-BSS frame.
- STA 1 and STA 2 belonging to BSS A may exist.
- STA 3 and STA 4 belonging to BSS B (or associated with an AP operating BSS B) may exist.
- STA 1 may transmit a PPDU.
- the PPDU transmitted by STA 1 may include information about the BSS. For example, the information on the BSS may be information for classifying the BSS described above.
- the PPDU transmitted by STA 1 may include Duration information.
- STA 2 may receive the PPDU transmitted by STA 1 and classify a BSS for this PPDU. Also, since STA 2 and STA 1 belong to BSS A, the PPDU received by STA 2 may be classified as an intra-BSS PPDU. In addition, the PPDU received by STA 2 may be a UL PPDU or a PPDU for which the STA is not the intended receiver. Therefore, according to the aforementioned embodiment, STA 2 can perform intra-PPDU power save. Referring to FIG. 13, STA 2 may enter the doze state until the received PPDU end time. Also, STA 2 may set the NAV based on Duration information included in the received PPDU. Since STA 2 classifies the received PPDU as an intra-BSS PPDU, it is possible to configure an intra-BSS NAV.
- STA 3 may receive the PPDU transmitted by STA 1 and classify a BSS for this PPDU. Also, since STA 3 and STA 1 belong to BSS B and BSS A, respectively, the PPDU received by STA 3 may be classified as an inter-BSS PPDU. In addition, STA 3 may set the NAV based on Duration information included in the received PPDU. Since STA 3 classifies the received PPDU as an inter-BSS PPDU, it is possible to set a basic NAV.
- STA 4 may receive the PPDU transmitted by STA 1 and classify a BSS for this PPDU. Also, since STA 4 and STA 1 belong to BSS B and BSS A, respectively, the PPDU received by STA 4 may be classified as an inter-BSS PPDU. In addition, the signal strength of the PPDU received by STA 4 may be smaller than the threshold. Therefore, since the PPDU received by STA 4 is classified as an inter-BSS PPDU and the signal strength of the PPDU received by STA 4 is smaller than the threshold, STA 4 can perform a spatial reuse operation. Therefore, STA 4 can perform channel access and backoff procedure, and can start transmission. For example, it may be possible for STA 4 to start transmission when the PPDU transmitted by STA 1 is not finished.
- FIG. 14 shows a wireless LAN function according to an embodiment of the present invention.
- a wireless LAN of a certain standard may include functions of a wireless LAN of another standard.
- the wireless LAN may mean an STA.
- the wireless LAN may mean an MLD including an STA.
- the wireless LAN standard may include standard functions of the previous generation and additional functions.
- an HT STA may also be an OFDM PHY STA.
- the HT STA may perform additional functions as well as the functions of the OFDM PHY STA.
- a VHT STA may also be an HT STA.
- the VHT STA may perform additional functions as well as the functions of the HT STA.
- a HE STA may also be a VHT STA.
- the HE STA may perform additional functions as well as the functions of the VHT STA.
- the EHT STA may also be a HE STA.
- the EHT STA may perform additional functions as well as the functions of the HE STA.
- Standards after the EHT standard may also exist. In the present invention, standards following the EHT standard may be referred to as NEXT standards, and STAs conforming to the NEXT standards may be referred to as NEXT STAs.
- a NEXT STA may also be an EHT STA. In addition, the NEXT STA may perform additional functions as well as the function of the EHT STA.
- an EHT STA may be a HE STA, a VHT STA, an HT STA, and an OFDM PHY STA.
- the NEXT STA it may be an EHT STA, HE STA, VHT STA, HT STA, or OFDM PHY STA.
- FIG 15 illustrates an uplink (UL) multi-user (MU) operation according to an embodiment of the present invention.
- UL uplink
- MU multi-user
- an AP may instruct at least one STA to transmit a PPDU through a specific frame (eg, a triggering frame), and the at least one STA may instruct at least one STA to transmit a PPDU in a specific frame transmitted from the AP.
- PPDUs of the same or different formats can be simultaneously transmitted based on the
- a frame soliciting or triggering multi-user (MU) transmission may be transmitted, and one or more STAs transmit based on this frame Or you can respond to these frames.
- one or more STAs may respond simultaneously and immediately based on the frame, and the response to the frame is SIFS at the end of the PPDU including the frame. Transmission can begin later. For example, if the frame indicates an immediate response, one or more STAs may immediately transmit a response to the frame.
- a frame for instructing or triggering transmission to one or more STAs may be a trigger frame or a frame including information indicating that uplink transmission is instructing or triggering one or more STAs in a MAC header. In this case, the frame may include information (eg, TRS control subfield) triggering or instructing uplink transmission to only one STA in the MAC header.
- information indicating or triggering uplink transmission included in the MAC header is included in the HT control field, control subfield, or A-control subfield. It may be triggered response scheduling (TRS) or TRS control subfield (TRS control subfield).
- TRS triggered response scheduling
- TRS control subfield TRS control subfield
- a frame for instructing or triggering uplink transmission may be transmitted by an AP, and if the frame for instructing or triggering uplink transmission is a trigger frame, a response to this is a trigger-based PPDU (TB PPDU) ) format.
- the TB PPDDU may include not only the previously described HE TB PPDU and EHT TB PPDU but also the NEXT TB PPDU that may be defined in the next standard.
- the HE TB PPDU may consist of a preamble, data, and packet extension (PE), and the preamble is L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, HE -STF, HE-LTF can be included in sequence.
- PE packet extension
- EHT TB PPDU and NEXT TB PPDU can also be composed of preamble, data and PE, and the preamble of EHT TB PPDU and NEXT TB PPDU is L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, (EHT-/NEXT-)STF and (EHT-/NEXT-)LTF can be included in sequence.
- a frame instructing or triggering transmission of a PPDU to one or more STAs may include information necessary for one or more STAs to transmit a TB PPDU.
- the frame may be a trigger frame that is a control frame.
- a response of a TB PPDU is instructed or triggered to multiple STAs, if the formats of the PPDUs to which the multiple STAs respond are different, the AP that instructed or triggered the response sends the PPDU, which is a response transmitted from the multiple STAs, Difficulty receiving may occur.
- the information included in the preamble of the PPDU to which multiple STAs respond differs according to the format, a problem may occur that it is difficult for the AP that instructed or triggered the response to receive the PPDU, which is a response transmitted from multiple STAs.
- the format of the responding PPDU and/or the type of information included in the preamble of the PPDU may be set to be the same.
- L-STF, L-LTF, and L-SIG so that the AP can successfully receive preambles transmitted by multiple STAs
- RL-SIG, and HE-SIG-A may deliver information so that the information included is the same, or an appointment for information included in the HE TB PPDU may be determined.
- the HE TB PPDU, EHT TB PPDU, and NEXT TB PPDU are simultaneously transmitted through overlapping subbands, it may be difficult for the AP to receive them because the TB PPDU formats are different.
- a HE STA may transmit a HE TB PPDU.
- the EHT STA may transmit an EHT TB PPDU or HE TB PPDU.
- the NEXT STA may transmit a NEXT TB PPDU, EHT TB PPDU, or HE TB PPDU. This is because, as described in FIG. 10, an STA of a certain standard may include functions of a previous standard.
- the AP transmits a frame for scheduling transmission of the TB PPDU to the HE STA and the EHT STA, and instructs or triggers the transmission of the TB PPDU through the frame
- an accurate indication of the TB PPDU format or There may be no protocol.
- the HE STA may transmit the HE TB PPDU in response to the frame
- the EHT STA may respond with the EHT TB PPDU or the HE TB PPDU.
- the AP may be difficult for the AP to receive the TB PPDU transmitted by the STAs, and although successful transmission was not made because the AP did not successfully receive the TB PPDU from a plurality of STAs, the medium was occupied and other STAs had transmission opportunities. Downsizing problems can occur.
- instructing the STA may mean instructing a response from the STA, and a trigger and an instruction may be used in the same meaning.
- HE trigger frame may be trigger frames defined in HE, EHT, and NEXT standards, respectively.
- HE TRS, EHT TRS, and NEXT TRS may be TRSs defined in HE, EHT, and NEXT standards, respectively.
- FIG. 16 shows a trigger frame format according to an embodiment of the present invention.
- FIG. 16(a) shows a trigger frame format
- FIG. 16(b) and (c) show a common info (information) field and a user information field (User Info), which are fields included in the trigger frame, respectively. field).
- User Info user information field
- a frame as a trigger MAC header includes a frame control field, a duration field, and an address field, and a common information field and a user information list field.
- the address field may include a resource allocation (RA) field and a transmitter address (TA) field.
- the common information field may include information commonly applicable to all STAs indicated by the trigger frame. 12(b) shows an example of a common information field.
- the user information list field may include zero or more user information fields, and a user information list field of a trigger frame excluding a specific type of trigger frame may include one or more user information fields.
- 16(c) shows an example of a user information field.
- the trigger frame may additionally include a padding field and a frame check sequence (FCS) field.
- the padding field may be used to increase the length of the frame in order to secure time required for the STA receiving the trigger frame to prepare a response to the trigger frame, and may optionally be included in the trigger frame.
- the common information field may include a trigger type subfield.
- the trigger type subfield may be used to identify a trigger frame variant.
- the type of trigger frame may be indicated based on the value of the trigger frame subfield.
- information and length included in the trigger dependent common information subfield and the trigger dependent user information subfield shown in FIG. 12 based on the trigger type subfield can be determined
- the trigger type subfield may be indicated through bits B0 to B3 of the common information field.
- the common information field may include an uplink (UL) length subfield.
- the UL length subfield may include information on the length of a TB PPDU that is a response to the trigger frame, and may include information on the length of a frame responding to the trigger frame.
- the UL length subfield may indicate a value to be included in the L-SIG length subfield of the TB PPDU responding to the trigger frame. Accordingly, an STA receiving the trigger frame and responding with the TB PPDU may set the value of the length subfield included in the L-SIG of the TB PPDU based on the value of the UL length subfield included in the received trigger frame.
- the STA responding with the TB PPDU may set the length subfield included in the L-SIG of the TB PPDU to the value of the UL length subfield included in the received trigger frame.
- the STA may transmit the TB PPDU by setting the length subfield included in the L-SIG of the TB PPDU based on the values of bits B4 to B15 of the common information field indicating the UL length subfield.
- the common information field may further include a UL Bandwidth (BW) subfield.
- the UL BW subfield may indicate a BW value included in a signaling field (eg, HE-SIG-A or U-SIG, etc.) of a TB PPDU responding to the trigger frame, transmitted in response to the trigger frame
- the maximum BW of the TB PPDU may be indicated. Accordingly, the STA may set the BW value included in the signaling field of the TB PPDU based on the value of the UL BW subfield included in the trigger frame.
- the common information field may additionally include information to be included in the signaling field of the TB PPDU, which is a response to the trigger frame. Accordingly, after receiving the trigger frame, the STA may configure information included in the TB PPDU based on information included in the trigger frame.
- the user information field may include an AID12 subfield.
- the AID12 subfield may be used to indicate the intended recipient of the user information field including the AID12 subfield or the function of the user information field. Accordingly, the AID12 subfield may also play a role of indicating an intended recipient of a trigger frame including the AID12 subfield or a function of the trigger frame.
- the user information field may indicate a random access resource unit (RA-RU). That is, the preset value of the AID12 subfield may represent that the user information field indicates the RA-RU.
- RA-RU random access resource unit
- the user information field may indicate a RA-RU for associated STAs.
- the user information field may indicate RA-RU for combined STAs, and when the value of the AID12 subfield is '2045', the user information field is RA-RUs for unassociated STAs may be indicated.
- the STA corresponding to the STA ID (eg, AID (association ID)) indicated by the value of the AID12 subfield is instructed to respond by a user information field including the AID12 subfield or a trigger frame including the AID subfield can For example, the AID12 subfield may indicate AID or 12 LSBs of AID.
- the STA corresponding to the value indicated by the AID12 subfield may transmit the TB PPDU in response to the received trigger frame.
- the value of the AID12 subfield may range from '1' to '2007' (including 1 and 2007), and when the AID12 subfield is a preset value (eg '2046', etc.), the AID12 subfield The RU corresponding to the preset value of the field may not be allocated to any STAs.
- the preset value may indicate that padding of the trigger frame starts.
- Information of the user information field including the AID12 subfield may be information corresponding to STAs indicated by the AID12 subfield.
- the Resource Unit (RU) Allocation subfield may indicate the size and location of the RU.
- the value of the RU allocation subfield of the user information field including the AID12 subfield may be information corresponding to the STA indicated by the AID12 subfield. That is, the RU indicated by the RU allocation subfield of the AID12 subfield may be the RU allocated to the STA indicated by the AUD12 subfield.
- the user information field includes a coding method (UL FEC coding type) for generating a TB PPDU transmitted in response to a trigger frame, a modulation method (UL HE-MCS, UL DCM), and power (UL Target RSSI ), etc. can be indicated.
- a coding method (UL FEC coding type) for generating a TB PPDU transmitted in response to a trigger frame
- a modulation method (UL HE-MCS, UL DCM), and power (UL Target RSSI ), etc.
- UL Target RSSI UL Target RSSI
- FIG. 17 illustrates a method for indicating a triggered-based (TB) PPDU (PPDU) format according to an embodiment of the present invention.
- one STA may selectively transmit PPDUs of different formats based on what is indicated by a triggering frame indicating PPDU transmission.
- the EHT STA may selectively transmit EHT TB PPDU as well as the legacy PPDU (eg, HE TB PPDU), and the NEXT STA may selectively transmit HE TB PPDU, EHT TB PPDU, and/or NEXT TB PPDU.
- STAs to which various standards are applied may be individually scheduled with one frame or one PPDU.
- This method can be advantageous because STAs to which a plurality of standards are applied share common resources in a WLAN.
- a HE STA (a HE STA other than an EHT STA) and an EHT STA may respond with a HE TB PPDU through one frame. That is, the non-AP STA may transmit a triggering frame to instruct not only the HE STA but also the EHT STA to transmit the HE TB PPDU.
- information for selecting a TB PPDU format may be included in a PPDU including a trigger frame, a TRS, and a trigger frame, which is a triggering frame, or a PPDU including a TRS control subfield. That is, information for selecting the format of the TB PPDU is included in the triggering frame and transmitted by the AP STA to at least one non-AP STA, and the non-AP STA responds based on the information included in the transmitted triggering frame PPDU format can be selected. Then, at least one non-AP STA may transmit a PPDU to the AP based on the selected format.
- TB PPDU format which is a response to such a triggering frame
- a trigger frame which is one of the triggering frames, can be classified into a HE trigger frame, an EHT trigger frame, and a NEXT trigger frame
- Responses to each trigger frame may be classified into HE TB PPDU, EHT TB PPDU, and NEXT TB PPDU.
- distinguishing trigger frames into HE trigger frames, EHT trigger frames, and NEXT trigger frames may mean the same as dividing the TB PPDU format, which is a response to the trigger frame, into HE TB PPDU, EHT TB PPDU, and NEXT TB PPDU, respectively. there is.
- the format of the trigger frame for distinguishing the format of the TB PPDU is a HE trigger frame, an EHT trigger frame, or a NEXT trigger frame can be identified based on a frame control field included in the MAC header.
- the format of the trigger frame may be distinguished based on the type subfield, the subtype subfield, and/or the control frame extension subfield.
- the value of the type subfield, subtype subfield, and/or control frame extension subfield is a preset value
- the trigger frame is identified as an HE trigger frame, and if it is another preset value, the trigger frame will be identified as an EHT trigger frame.
- the values of the type subfield, subtype subfield, and/or control frame extension subfield are different preset values
- the trigger frame may be identified as a NEXT trigger frame.
- the format of the frame including the type subfield and the subtype subfield may be a HE trigger frame.
- entries in the type subfield (2 bits), subtype subfield (4 bits), and/or control frame extension subfield (4 bits) to which a limited number of bits are allocated may be additionally used in the EHT standard and the NEXT standard. there is.
- whether the format of the trigger frame is a HE trigger frame or an EHT trigger frame may be identified based on a common information field included in the trigger frame. That is, the format of the PPDU to be transmitted in response to the trigger frame may be determined based on the value of a specific subfield (first subfield) included in the common information field. For example, the non-AP STA may select HE TB PPDU or EHT TB PPDU and transmit it through the allocated RU according to the value of the common information field. In this case, not only the common information field but also a specific subfield (second subfield) of the user information field may be additionally used to identify the format of the PPDU.
- a variant for determining the format of a PPDU that is a response to the trigger frame may be determined based on the common information field of the trigger frame, and the format of the PPDU may be determined according to the determined variant. For example, when the HE variant is determined as the variant for determining the format of the PPDU by the common information field, the non-AP STA may respond with the HE TB PPDU, and the common information field for determining the format of the PPDU If the variant is determined as the EHT variant, the non-AP STA may respond with the EHT TB PPDU.
- a user information field as well as a common information field may be additionally used.
- a trigger frame may be identified as an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the trigger type subfield.
- the trigger frame may be the HE trigger frame.
- the trigger frame may be an EHT trigger frame.
- the trigger frame may be a NEXT trigger frame.
- the trigger type subfield value when it is 0 to 7, it is an HE trigger frame, and when it is not 0 to 7, it may be an EHT trigger frame or a NEXT trigger frame.
- the trigger type subfield indicates various types of trigger frame types. In this case, there may be a disadvantage in that a limited trigger type subfield space must be used.
- the trigger frame is an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the UL Length subfield of the trigger frame. For example, based on a value obtained by mod (remainder) the UL length subfield value, it is possible to distinguish whether the frame is an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame. That is, whether the format of the PPDU to be transmitted in response to the trigger frame is the HE PPDU or the EHT PPDU can be determined using the value of the UL length subfield.
- the trigger frame may be the HE trigger frame.
- the trigger frame may be the HE trigger frame.
- the trigger frame may not be the HE trigger frame.
- the trigger frame may be an EHT trigger frame or a NEXT trigger frame.
- the response to the trigger frame can be transmitted as a HE TB PPDU, and the value obtained by mod 3 of the value of the UL length subfield of the trigger frame is 1.
- the response to the trigger frame may be transmitted as HE TB PPDU.
- the format of the PPDU to be transmitted in response to the trigger frame may be an EHT TB PPDU.
- a HE trigger frame, an EHT trigger frame, and a NEXT trigger frame by using an additional trigger frame identification method together with this method.
- an additional trigger frame identification method it is possible to distinguish a HE trigger frame, an EHT trigger frame, and a NEXT trigger frame by using the classification method described in FIG. 16 together.
- the format of the trigger frame is a HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the user information field of the trigger frame.
- the format of the PPDU to be transmitted in response to the trigger frame may be determined based on the value of a specific subfield (second subfield) included in the user information field.
- the non-AP STA may select HE TB PPDU or EHT TB PPDU and transmit it through the allocated RU.
- a specific subfield (first subfield) of the common information field may be additionally used to identify the format of the PPDU.
- a variant for determining the format of a PPDU that is a response to the trigger frame may be determined based on the user information field of the trigger frame, and the format of the PPDU may be determined according to the determined variant. For example, when the variant for determining the format of the PPDU is determined as the HE variant by the user information field, the non-AP STA may respond with the HE TB PPDU, and the user information field for determining the format of the PPDU If the variant is determined as the EHT variant, the non-AP STA may respond with the EHT TB PPDU.
- not only the user information field but also the common information field may be additionally used.
- an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame may be distinguished based on the AID12 subfield.
- whether a HE trigger frame, an EHT trigger frame, or a NEXT trigger frame can be distinguished according to whether or not the AID12 subfield of a preset value is included.
- a user information field including an AID12 subfield indicating which trigger frame is present may be present at the front of the user information list.
- a user information field including an AID12 subfield indicating which trigger frame is present may exist behind user information fields corresponding to the HE STA.
- the AID12 subfield may play a role of indicating a TB PPDU format to be responded to. For example, when the AID12 subfield is a preset value, a response to a trigger frame including the AID12 subfield set to the preset value may be an EHT TB PPDU.
- the response to the trigger frame including the AID12 subfield may be an EHT TB PPDU.
- the AID12 subfield is a preset value
- a response to a trigger frame including the AID12 subfield set to the preset value may be a NEXT TB PPDU.
- a response to a trigger frame including the AID12 subfield may be a NEXT TB PPDU.
- a response when a response is made based on a user information field existing at a preset location from an AID12 subfield of a preset value, a response may be made in a TB PPDU format corresponding to the preset value. For example, when responding based on a user information field existing after the AID12 subfield of a preset value, a response may be made in a TB PPDU format corresponding to the preset value.
- a TB PPDU format according to a preset priority may be responded.
- the TB PPDU format when responding based on the user information field existing after the AID12 subfield set to 2047, it may respond with EHT TB PPDU.
- the AID12 subfield set to 2048 when responding based on the user information field existing after the AID12 subfield set to 2048, it may respond with NEXT TB PPDU.
- a NEXT TB PPDU when responding based on the user information field existing after both the AID12 subfield set to 2047 and the AID12 subfield set to 2048, a NEXT TB PPDU may be responded. In addition, when responding based on the user information field that precedes both the AID12 subfield set to 2047 and the AID12 subfield set to 2048, a HE TB PPDU may be responded.
- the present invention is not limited thereto and it is possible to indicate the type of trigger frame through other subfields of the user information field.
- a HE trigger frame, an EHT trigger frame, or a NEXT trigger frame may be distinguished based on the padding field of the trigger frame. For example, whether a HE trigger frame, an EHT trigger frame, or a NEXT trigger frame can be determined according to whether the padding field includes a preset value indicating whether the frame is a HE trigger frame, an EHT trigger frame, or a NEXT trigger frame.
- a HE trigger frame an EHT trigger frame, and a NEXT trigger frame by combining a plurality of trigger frame identification methods described in the present invention.
- the description of the trigger frame in the present invention is not limited thereto and can be applied to the TRS as well.
- an AP may not be able to indicate transmission of the EHT PPDU and the HE PPDU together through a triggering frame. That is, the EHT AP cannot transmit a trigger frame indicating both the HE TB PPDU and the EHT TB PPDU, and can indicate only one PPDU format.
- transmission of the TB PPDU may be indicated through not only the trigger frame but also the TRS.
- TRS may be included in the HT control field as described above.
- TRS can be conveyed by the TRS control subfield.
- the A-control field may have a form in which control list fields may be consecutively followed.
- the control list field may include TRS.
- an intended receiver of a frame including the TRS to respond to the TRS.
- an STA corresponding to an RA included in a frame including the TRS to respond to the TRS.
- the TRS includes information on the length of a PPDU or frame responding to the TRS (UL Data Symbols), location and size of an RU to be used when responding to the TRS (RU Allocation), and information on power when responding to the TRS (AP Tx Power, UL Target RSSI), information on the modulation method when responding to the TRS (UL HE-MCS), and the like.
- the embodiment of FIG. 18 may be a method for solving the problems described in FIGS. 14 and 15 .
- the embodiment of the trigger frame can also be applied to the TRS. Also, you may have omitted the previously described details.
- TRS defined by the EHT standard or the NEXT standard may exist in addition to the TRS (HE TRS) defined by the HE standard. Accordingly, depending on whether the indicated TRS is HE TRS, EHT TRS, or NEXT TRS, TB PPDUs responding to the TRS may be HE TB PPDU, EHT TB PPDU, or NEXT TB PPDU, respectively. For example, it is possible to determine which TRS is defined by a standard through the Control ID subfield of the A-Control subfield. As an additional embodiment, TRS can be divided into HE TRS and TRS other than HE TRS.
- TRS defined by a standard may be determined according to whether the HT control field is an HE variant, an EHT variant, or a NEXT variant.
- it may be determined according to whether it is an HE variant, an EHT variant, or a NEXT variant. For example, when B0 and B1 of the HT control field are 1, 1, it may be a HE variant.
- it can be determined according to whether it is a HE variant, an EHT variant, or a NEXT variant by using B0, B1 and additional bits (eg, B31) of the HT control field.
- the format of the PPDU may be determined based on the format of the PPDU including the TRS control subfield. For example, if the format of the PPDU including the TRS control subfield is the HE PPDU, the format of the indicated PPDU may be the HE PPDU. However, when the format of the PPDU including the TRS control subfield is the EHT PPDU, the format of the indicated PPDU may be the EHT PPDU.
- the TB PPDU responding to the TRS may be the HE TB PPDU.
- the TB PPDU responding to the TRS may be the EHT TB PPDU.
- the TRS is delivered through the NEXT PPDU, the TB PPDU responding to the TRS may be the NEXT TB PPDU.
- interpretation of subfields included in the TRS can be changed based on the PPDU format including the TRS.
- the UL HE-MCS subfield (or subfield related to the MCS) included in the TRS may indicate a value corresponding to the HE MCS table.
- the UL HE-MCS subfield (or subfield related to MCS) included in the TRS may indicate a value corresponding to the EHT MCS table.
- the UL HE-MCS subfield (or subfield related to the MCS) included in the TRS may indicate a value corresponding to the NEXT MCS table. Also, the interpretation of the RU Allocation subfield may be different based on the PPDU format including the TRS.
- 19 illustrates end time alignment of a high priority frame according to an embodiment of the present invention.
- aligning PPDU transmission end times or alignment may be referred to as end time alignment, end time alignment, PPDU end time alignment, ending time alignment, and the like.
- whether to perform end time alignment may be determined based on whether a high priority frame is included in the multiple PPDUs.
- the end time alignment operation may be different based on whether a high priority frame is included in the multiple PPDUs.
- end time alignment may mean that a difference in end times of PPDUs to be aligned is equal to or less than a preset time.
- the MLD it is possible for the MLD to start transmitting multiple PPDUs simultaneously.
- the transmission start times of multiple PPDUs transmitted by the MLD are exactly the same or the difference between the transmission start times of the multiple PPDUs is equal to or less than a preset time, it can be said that transmission starts simultaneously.
- the MLD starts transmitting multiple PPDUs simultaneously it may be referred to as start time sync.
- Whether a frame is a high priority frame may be based on a traffic identifier (TID) or access category (AC) corresponding to the frame. Also, whether a frame is a high priority frame may be based on the type and subtype of the frame. The type and subtype of the frame may be indicated in the MAC header of the frame. Alternatively, it may be a high priority frame when the frame is transmitted within the allocated time interval. In this case, time allocation for high priority frame transmission may be performed by the AP. Also, according to an embodiment, an absolute criterion may exist whether a frame is a high priority frame. For example, a frame corresponding to a preset TID or a preset AC may be a high priority frame.
- whether a frame is a high priority frame may be relative to other frames. For example, whether a frame is a high priority frame may be determined based on whether a frame transmitted on a link different from the frame has a high priority. Alternatively, the sender may determine whether the frame is a high priority frame.
- the non-STR MLD may be an MLD in which simultaneous transmission and reception in a used link pair is restricted.
- a link pair in which simultaneous transmission and reception are restricted may be referred to as a non-STR link pair or an NSTR link pair.
- a link pair in which simultaneous transmission and reception are not restricted may be referred to as an STR link pair.
- end time alignment when an MLD transmits multiple PPDUs, if a high priority frame is included in the transmitted PPDU, end time alignment may not be performed. For example, even when the multiple PPDUs are transmitted to STAs belonging to the same MLD, if a high priority frame is included, end time alignment may not be performed. In addition, even if neither the MLD transmitting multiple PPDUs nor the receiving MLD operate on the STR link pair (ie, even if at least one MLD operates on the NSTR link pair), if a high priority frame is included, end time alignment is performed. may not
- an MLD transmits multiple PPDUs
- the transmitted PPDUs include a high priority frame
- end time alignment is not performed because the PPDU including the high priority frame is a high priority frame. It may be limited to a case where transmission starts before a PPDU that does not include.
- an AP MLD to which AP 1 and AP 2 belong may exist.
- a non-AP MLD to which STA 1 and STA 2 belong may exist.
- AP MLD and non-AP MLD can be multi-link setup in Link 1 and Link 2.
- Link 1 and Link 2 may be an NSTR link pair.
- AP 1 and STA 1 can operate in Link 1
- AP 2 and STA 2 can operate in Link 2.
- An AP MLD may transmit multiple PPDUs. The times of the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may overlap.
- the PPDU transmitted by AP 1 may not include a high priority frame.
- the PPDU transmitted by AP 2 may include a high priority frame.
- the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may be start time synchronized, or the PPDU transmitted by AP 2 may start earlier than the PPDU transmitted by AP 1. In this case, the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may not be aligned in end time. Referring to FIG. 19, the PPDU transmitted by AP 2 ends later than the PPDU transmitted by AP 1. If the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 are end time aligned, AP 2 may not be able to transmit all the high priority frames to be transmitted in one PPDU and may have to terminate the PPDU. Therefore, it may be possible to quickly transmit a high priority frame by not performing end time alignment for a PPDU including a high priority frame.
- a frame transmitted by AP 1 may request an immediate response.
- a frame transmitted by AP 2 may require an immediate response.
- STA 1 may prevent reception of a high priority frame by responding to a frame transmitted by AP 1 .
- an STA of an MLD when an STA of an MLD receives a high priority frame on another link, it may not respond even if it is requested to transmit an immediate response.
- STA 1 since STA 2 is receiving a high priority frame, STA 1 may not transmit an immediate response requested by the frame transmitted by AP 1.
- the MLD when the MLD receives a frame on an NSTR link pair and the frame requests an immediate response, if the response to the frame interferes with reception on another link, it may not respond.
- this may be limited to a case where the frame is not a high priority frame. That is, when the MLD receives a frame on an NSTR link pair and the frame requests an immediate response, it may necessarily respond even if the response to the frame interferes with reception on another link.
- 20 shows another example of end time alignment of high priority frames according to an embodiment of the present invention.
- This embodiment may be related to end time alignment or PPDU end time, the transmission MLD or the reception MLD operating in an NSTR link pair, the PPDU including a frame requesting an immediate response, and the PPDU a QoS Data frame.
- Related conditions such as including, that the PPDU includes a QoS Data frame requiring an immediate response, that multiple PPDUs are transmitted by STAs of the same MLD, and that multiple PPDUs are received by STAs of the same MLD. could have been omitted.
- the described embodiment may be performed when these conditions are satisfied.
- an AP MLD to which AP 1 and AP 2 belong may exist.
- a non-AP MLD to which STA 1 and STA 2 belong may exist.
- AP MLD and non-AP MLD can be multi-link setup in Link 1 and Link 2.
- Link 1 and Link 2 may be an NSTR link pair.
- AP 1 and STA 1 can operate in Link 1
- AP 2 and STA 2 can operate in Link 2.
- An AP MLD may transmit multiple PPDUs. The times of the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may overlap.
- the PPDU transmitted by AP 1 may include a high priority frame.
- the PPDU transmitted by AP 2 may not include a high priority frame.
- the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may be start time synchronized, or the PPDU transmitted by AP 1 may start earlier than the PPDU transmitted by AP 2.
- Case 1 shown in FIG. 20 (a) and Case 2 shown in FIG. 50 (b) may be embodiments in which end time alignment is not performed.
- the PPDU transmitted by AP 2 may end later than the PPDU transmitted by AP 1. In this case, reception of high priority frames may not be disturbed by in-device interference. However, a response to a PPDU including a high priority frame may prevent reception of a PPDU not including a high priority frame.
- the PPDU transmitted by AP 2 may end before the PPDU transmitted by AP 1.
- transmission of STA 2 may prevent reception of a high priority frame on link 1. Therefore, high priority frames may not be received successfully quickly.
- Case 3 shown in FIG. 20 (c) may be an embodiment of performing end time alignment. Therefore, when receiving a PPDU including a high priority frame, it may not be disturbed by in-device interference. As in Case 2, it is possible to solve a problem in which reception of a high priority frame is hindered.
- the preset condition may include a case where one PPDU includes a high priority frame and another PPDU does not include a high priority frame.
- the preset condition may include a case in which a PPDU including a high priority frame is started to be transmitted before or at the same time as a PPDU not including a high priority frame.
- the preset condition may include a case in which a frame of a PPDU not including a high priority frame requests an immediate response.
- a preset condition (Case 1 or Case 3 ). More specifically, even when multiple PPDUs including high-priority frames are transmitted, it is possible to perform end time alignment under preset conditions or to determine the end point of one PPDU (Case 1 or Case 3). More specifically, even when multiple PPDUs containing high-priority frames are transmitted, it is possible to perform end time alignment under preset conditions or to end a PPDU without high-priority frames later than a PPDU containing high-priority frames. .
- the preset condition may include a case where one PPDU includes a high priority frame and another PPDU does not include a high priority frame.
- the preset condition may include a case in which a PPDU including a high priority frame is started to be transmitted before or at the same time as a PPDU not including a high priority frame.
- the preset condition may include a case in which a frame of a PPDU not including a high priority frame requests an immediate response.
- 21 shows another example of end time alignment of high priority frames according to an embodiment of the present invention.
- This embodiment may be related to end time alignment or PPDU end time, the transmission MLD or the reception MLD operating in an NSTR link pair, the PPDU including a frame requesting an immediate response, and the PPDU a QoS Data frame.
- Related conditions such as including, that the PPDU includes a QoS Data frame requiring an immediate response, that multiple PPDUs are transmitted by STAs of the same MLD, and that multiple PPDUs are received by STAs of the same MLD. could have been omitted.
- the described embodiment may be performed when these conditions are satisfied.
- the present invention when multiple PPDUs including high-priority frames are transmitted, it is determined whether to perform end time alignment or when to end the PPDUs based on whether at least two or more PPDUs include high-priority frames. It is possible. Alternatively, when multiple PPDUs including high-priority frames are transmitted, it is possible to determine whether to perform end time alignment based on whether at least two or more PPDUs include high-priority frames.
- an MLD when an MLD transmits multiple PPDUs and two or more transmitted PPDUs include a high priority frame, there may be no restriction on the PPDU end time. For example, in this case, there may be no restriction on the end time of the PPDU even if the condition for executing the restriction on the end time of the PPDU including the end time alignment described above is satisfied. For example, even if one MLD transmits PPDUs including a frame (eg, QoS Data frame) requesting an immediate response to STAs belonging to the same MLD, and the STAs operate in an NSTR link pair, for the PPDU to be transmitted End time alignment may not be performed.
- a frame eg, QoS Data frame
- redundancy such as padding may need to be included in the PPDU in order to perform end time alignment, and the time at which the frame of the PPDU including the redundancy is completed may be delayed. Also, if end time alignment is not performed, reception of any one PPDU may be disturbed due to in-device interference. Therefore, it is possible for the transmitting MLD to decide whether or not to apply the restriction on the end time of the PPDU. Alternatively, it may be possible for the receiving MLD to make a recommendation about the restriction on the end time of the PPDU.
- an MLD when an MLD transmits multiple PPDUs, when two or more transmitted PPDUs include high priority frames, it is possible to perform end time alignment on multiple PPDUs. For example, when the MLD transmits two PPDUs, if the two PPDUs to be transmitted each include a high priority frame, it is possible to perform end time alignment for multiple PPDUs. This is because, if end time alignment is not performed, reception of any one PPDU may be disturbed due to in-device interference.
- this embodiment may be limited to a case in which at least two PPDUs including a high priority frame require an immediate response. For example, when MLD transmits two PPDUs, if each of the two PPDUs to be transmitted includes a high priority frame and requires an immediate response, it is possible to perform end time alignment on the two PPDUs.
- an AP MLD to which AP 1 and AP 2 belong may exist.
- a non-AP MLD to which STA 1 and STA 2 belong may exist.
- AP MLD and non-AP MLD can be multi-link setup in Link 1 and Link 2.
- Link 1 and Link 2 may be an NSTR link pair.
- AP 1 and STA 1 can operate in Link 1
- AP 2 and STA 2 can operate in Link 2.
- An AP MLD may transmit multiple PPDUs. The times of the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may overlap.
- the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may include a high priority frame.
- the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may or may not be start time synchronized.
- the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 may be transmitted in end time alignment. This may be because the PPDU transmitted by AP 1 and the PPDU transmitted by AP 2 each require an immediate response.
- a high priority frame included in the PPDU transmitted by AP 1 may request an immediate response.
- a high priority frame included in a PPDU transmitted by AP 2 may require an immediate response.
- a PPDU includes a high priority frame may mean that the PPDU includes at least one high priority frame. Also, that the PPDU does not include a high priority frame may mean that the PPDU does not include any high priority frame.
- FIG. 22 is a diagram illustrating an example of a medium access recovery procedure according to an embodiment of the present invention.
- simultaneous transmission and reception by a multi-link device (MLD) on multiple links may be restricted.
- the restrictive may be the impossible.
- simultaneous transmission and reception may include transmission on one link and reception on at least one other link at least simultaneously (at the same time).
- whether simultaneous transmission and reception in multiple links is restricted or not may be based on the capabilities of the MLD and each link. That is, there are MLDs that restrict simultaneous transmission and reception on multiple links, and there may be MLDs that are not restrictive.
- simultaneous transmission and reception on multiple links may be restricted, and when the MLD operates in a link set different from the certain link set, simultaneous transmission and reception on multiple links may be restricted. may not be
- simultaneous transmission/reception is possible on multiple links, this may be referred to as simultaneous transmit (transmission) and receive (reception) (STR). Those with limited STR may be referred to as non-STR or NSTR.
- NSTR A pair of links for NSTR operation may be referred to as an NSTR link pair.
- STR is not restrictive
- a link pair having a restricted or non-restricted STR may be referred to as an STR link pair and an NSTR link pair, respectively.
- MLDs with restricted or non-restricted STRs may be referred to as STR MLDs and NSTR MLDs, respectively.
- MLD may be NSTR MLD when at least one link pair of an operating link set is an NSTR link pair.
- the description of the MLD operating on the NSTR (or STR) link pair in the embodiment of the present invention can also be read as the embodiment described for the NSTR (or STR) MLD.
- NSTR or STR
- the limitation of STR may be because MLD transmission on one link acts as interference to another link. More specifically, the limitation of STR may be because transmission of an MLD on one link acts as interference to reception of the MLD on another link. Such interference may be referred to as in-device interference.
- the limitation of the STR may be due to the limitation of the number of radios of the MLD. For example, an MLD operating with a single radio may have a limited STR. An MLD operating with a single radio may be able to receive or transmit on only one link at a time. Alternatively, an MLD operating as a single radio may be capable of simultaneously listening or monitoring on multiple links, but may be capable of receiving or transmitting only on one link at a time. At this time, listening or monitoring may mean receiving a PPDU or frame with a preset configuration.
- PPDU end time alignment can be performed so that the MLD can not simultaneously transmit and receive on the NSTR link pair.
- MLD 1 can transmit multiple PPDUs to MLD 2 over multiple links.
- end time alignment of PPDUs transmitted in NSTR link pairs may be performed.
- End time alignment of PPDUs may be to align end time differences of multiple PPDUs with a preset time or less. The preset time may be 8 us.
- the preset time may be 4 us. If the PPDU includes a trigger frame and the CS Required subfield (a subfield indicating whether to respond to the trigger frame or determine based on carrier sense (CS)) included in the trigger frame indicates to respond based on the CS result, the preset time may be 4 us. If the PPDU includes a trigger frame and the CS Required subfield (a subfield indicating whether to respond to the trigger frame or determine based on carrier sense (CS)) included in the trigger frame indicates to respond based on the CS result, When other PPDUs end earlier than this PPDU, if they are end time aligned, the preset time may be 4 us.
- the MLD shall ensure that the end time of one or more PPDUs that carries a frame soliciting an immediate response frame is at most 4 us earlier than the end time of any of PPDUs containing a Trigger frame with the CS Required subfield set to 1.
- Performing end time alignment of PPDUs may be limited to a case in which a frame included in at least one of the PPDUs solicits an immediate response.
- performing end time alignment of PPDUs may be limited to a case in which a frame included in at least two of the PPDUs solicits an immediate response. It is possible to add padding to perform end time alignment.
- MLD can perform start time sync when transmitting PPDUs on multiple links.
- the MLD may be an MLD operating in an NSTR link pair.
- the MLD can obtain a transmission opportunity based on a backoff procedure or backoff counter in each link and transmit the PPDU. For example, it is possible to transmit a PPDU on a slot boundary where the backoff counter becomes 0. This may be a case of using a distributed coordination function (DCF). Alternatively, it is possible to transmit the PPDU on the slot boundary next to the slot boundary where the backoff counter becomes 0. This may be a case of using EDCA (enhanced distributed channel access; EDCAF (EDCA function)).
- EDCAF enhanced distributed channel access
- an STA whose backoff counter reaches 0 may maintain backoff counter 0 without transmitting.
- an STA maintaining a backoff counter of 0 can transmit when an STA belonging to the same MLD reaches 0 in the backoff counter.
- an MLD operating on an NSTR link pair when an MLD operating on an NSTR link pair has links 1 and 2 constituting the NSTR link pair and transmits on link 1, it may be difficult to receive on link 2. Therefore, it may be difficult to receive duration information of a PPDU or frame transmitted from other STAs on link 2.
- the STA operating on link 2 of the MLD operating on the NSTR link pair may express that medium synchronization has been lost.
- Link 2 when this happens in Link 2, it can be said that the STA operating in link 2 of the MLD operating in the NSTR link pair is blind.
- the STA operating on link 2 of the MLD operating on the NSTR link pair may not receive the transmitted duration information and may not perform an operation to defer channel access that would have been performed if the duration information was received. Accordingly, transmission and reception of other STAs may be hindered.
- AP 1 and AP 2 operating on link 1 and link 2 may exist, and AP 1 and AP 2 may belong to the same MLD, AP MLD.
- STA 1 and STA 2 operating on link 1 and link 2 may belong to the same MLD, a non-AP MLD.
- AP MLD and non-AP MLD may have multi-link setup on link 1 and link 2.
- the non-AP MLD may be NSTR MLD.
- link 1 and link 2 may be an NSTR link pair.
- STA 1 may transmit Data 1. In this case, transmitting Data 1 may act as interference to STA 2. Accordingly, STA 2 may be blind in a section in which Data 1 is transmitted.
- channel access of an STA may be restricted for a certain period of time in order to alleviate a problem that may occur because the STA does not receive duration information while the STA is blind.
- This period of time can be called MediumSyncDelay.
- MediumSyncDelay timer may be set to a value other than 0, and MediumSyncDelay may be applied while the timer is a value other than 0.
- the certain time period may start when the blind is released. Alternatively, the certain period of time may start at the point in time when the transmission that caused blindness ends. Referring to FIG.
- STA 2 may set the MediumSyncDelay timer to a value other than 0. At this time, the MediumSyncDeley timer can be set to the MediumSyncDelay value.
- STA 2 may have limited channel access during MediumSyncDelay. For example, an STA applying MediumSyncDelay may belong to an MLD operating on an NSTR link pair. Alternatively, an STA applying MediumSyncDelay may belong to the NSTR MLD. Also, an STA applying MediumSyncDelay may belong to a non-AP MLD.
- MediumSyncDelay may not be applied when a transmission period causing blindness is shorter than a preset time.
- the MediumSyncDelay value may have a default value.
- the default value may be the maximum duration of the PPDU.
- the maximum duration of the PPDU may be 5.484 ms.
- the MediumSyncDelay value may be a value transmitted from a multi-link setup peer MLD (AP MLD). If the non-AP MLD does not receive the MediumSyncDelay value from the AP MLD, the default value can be used as the MediumSyncDelay value. If the non-AP MLD receives the MediumSyncDelay value from the AP MLD, the received value may be used as the MediumSyncDelay value.
- AP MLD multi-link setup peer MLD
- Restricting channel access when MediumSyncDelay is applied may include the following operations.
- restricted channel access may be related to trying to gain a transmit opportunity (TXOP).
- Restricting channel access may include limiting the type of the first frame to be transmitted when TXOP is obtained.
- the type of frame can be defined by the Type subfield or Subtype subfield indicated by the MAC header of the frame.
- the type of the first frame may be a request to send (RTS) frame.
- RTS frame may be a type of control frame.
- the Type subfield B3 B2 bits may be set to 0 and 1, respectively.
- the Subtype subfields B7, B6, B5, and B4 bits may be set to 1, 0, 1, and 1, respectively.
- the bit index may be a bit index of the Frame Control field.
- B2 may be the least significant bit (LSB) of the type subfield, and B3 may be the most significant bit (MSB) of the type subfield.
- B4 may be the LSB of the Subtype subfield, and B7 may be the MSB of the Subtype subfield. Therefore, if the STA transmits the RTS frame as the first frame and does not receive the CTS frame as a response, transmission may not continue.
- limiting channel access may include limiting the size or length of the first frame or PPDU to be transmitted when TXOP is obtained.
- the size or length of the first frame or PPDU may be smaller than a preset value. Accordingly, even if there is duration information that the STA has not received while blind, transmission of other STAs may not be significantly disturbed.
- Restricting channel access may also include changing a clear channel assessment (CCA) threshold. More specifically, limiting channel access may include changing a clear channel assessment (CCA) threshold to a lower level than before. According to an embodiment, it may be determined that the channel is busy when a signal of more than (or exceeding) the CCA threshold is detected. Otherwise, it can be determined that the channel is idle.
- the CCA threshold may include a threshold for detecting a PPDU (Wi-Fi signal).
- a CCA using such a CCA threshold may be referred to as CCA PD (preamble detection; packet detection), and in this case, the threshold may be referred to as a CCA PD threshold or PD threshold.
- the CCA threshold may include a threshold for detecting any signal.
- CCA ED energy detection
- the threshold may be referred to as a CCA ED threshold or ED threshold. More specifically, limiting channel access may mean changing the ED threshold.
- the PD threshold When MediumSyncDelay is not applied, the PD threshold may be -82 dBm.
- the ED threshold When MediumSyncDelay is not applied, the ED threshold may be -62 dBm.
- the CCA threshold When MediumSyncDelay is applied, the CCA threshold may have a default value. Also, when MediumSyncDelay is applied, the CCA threshold may be a value transmitted from a multi-link setup peer MLD (AP MLD).
- AP MLD multi-link setup peer MLD
- the default value can be used as the CCA threshold when MediumSyncDelay is applied. If the non-AP MLD receives the CCA threshold from the AP MLD when MediumSyncDelay is applied, the received value can be used as the CCA threshold when MediumSyncDelay is applied.
- the default value of ED threshold may be -72 dBm. Also, when MediumSyncDelay is applied, a value that can be indicated as ED threshold may be -72 dBm or more.
- the ED threshold may be dot11MSDOFDMEDthreshold.
- the CCA threshold referred to in the present invention may be a threshold corresponding to a 20 MHz subchannel.
- limiting channel access may include limiting the number of transmission attempts during MediumSyncDelay. For example, the STA may not attempt transmission exceeding a certain number of times during MediumSyncDelay. That is, if the STA has a certain number of transmission failures during MediumSyncDelay, it may not attempt transmission any more during MediumSyncDelay. This predetermined number of times may be MSD_TXOP_MAX.
- a backoff procedure may be invoked. Alternatively, the backoff counter can be reset in order not to attempt transmission.
- the contention window (CW) may not change (left unchanged). CW may be a value used when resetting the backoff counter.
- the retry counter when resetting the backoff counter, an integer randomly selected from 0 to CW values can be used as a reset value.
- the retry counter may not be changed when resetting the backoff counter in order not to attempt transmission. If the retry counter reaches a preset value, the frame attempted to be transmitted may not be attempted to be transmitted any longer or the frame attempted to be transmitted may be discarded.
- the MSD_TXOP_MAX value may have a default value. The default value can be 1.
- the MediumSyncDelay value may be a value transmitted from a multi-link setup peer MLD (AP MLD).
- the non-AP MLD does not receive the MSD_TXOP_MAX value from the AP MLD, the default value can be used as the MSD_TXOP_MAX value. If the non-AP MLD receives the MSD_TXOP_MAX value from the AP MLD, the received value may be used as the MSD_TXOP_MAX value.
- 23 is a diagram illustrating an example of signaling related to a multi-link element and MediumSyncDelay according to an embodiment of the present invention.
- an STA of an MLD may include information related to a medium sync delay in a frame and transmit the frame.
- a Multi-Link element as shown in FIG. 23 may exist. It is possible to perform multi-link discovery, setup, and operation based on a frame including a multi-link element.
- the Multi-Link element may be included in a Beacon frame, a Probe Request frame, a Probe Response frame, an Authentication frame, an Association Request frame, an Association Response frame, a Reassociation Request frame, a Reassociation Response frame, and the like.
- the Multi-Link element may include Element ID, Length, Element ID Extension, Multi-Link Control, Common Info, and Link Info fields.
- the Element ID or Element ID Extension may indicate which element is an element including the Element ID or the Element ID Extension, that is, a Multi-Link element.
- the Length field may indicate the length of an element including the Length field.
- the Multi-Link Control field may include a Type subfield and a Presence Bitmap field.
- the Type subfield may indicate what type the Multi-Link element is. Also, the format of the Multi-Link element may be determined based on the type of the Multi-Link element.
- the Presence Bitmap field may indicate whether a subfield that may be included in the Multi-Link element is included.
- the Presence Bitmap field may indicate whether a subfield that can be included in the Common Info field included in the Multi-Link element is included.
- a subfield indicating whether the Presence Bitmap field is included may include MLD MAC address, Link ID Info, BSS Parameters Change Count, Medium Synchronization Delay Information, EML Capabilities, and MLD Capabilities fields (subfields).
- the Medium Synchronization Delay Information field may include information related to MediumSyncDelay.
- the Common Info field may include information about multiple links or all links.
- the Common Info field may include information commonly necessary for multiple links or all links, or the same information.
- the Link Info field may include information about each link.
- information related to MediumSyncDelay may have a default value.
- information related to MediumSyncDelay may be signaled.
- information related to MediumSyncDelay may be included in the Medium Synchronization Delay Information field shown in FIG. 20 .
- MLD can initialize information related to MediumSyncDelay with default values.
- AP MLD peer MLD
- the default value can be used as information related to MediumSyncDelay.
- MLD non-AP MLD
- MLD receives information related to MediumSyncDelay from peer MLD (AP MLD)
- it can use the received value as information related to MediumSyncDelay.
- the Medium Synchronization Delay Information field may include a Medium Synchronization Duration subfield, a Medium Synchronization OFDM ED Threshold subfield, and a Medium Synchronization Maximum Number Of TXOPs subfield.
- the Medium Synchronization Duration subfield may indicate MediumSyncDelay. That is, the Medium Synchronization Duration subfield may indicate a value for setting the MediumSyncDelay timer. For example, the Medium Synchronization Duration subfield may be 8-bit. Also, the Medium Synchronization Duration subfield may indicate a duration of 32 us units. That is, when the Medium Synchronization Duration subfield is set to A, the time indicated by the Medium Synchronization Duration subfield may be A*32 us.
- the Medium Synchronization OFDM ED Threshold subfield may indicate the CCA threshold when MediumSyncDelay is applied. More specifically, the CCA threshold indicated at this time may be a CCA ED threshold. That is, the Medium Synchronization OFDM ED Threshold subfield may indicate dot11MSDOFDMEDthreshold. Medium Synchronization OFDM ED Threshold subfield may be 4-bit.
- the CCA threshold indicated by the Medium Synchronization OFDM ED Threshold subfield is a value obtained by adding -72 to the value of the Medium Synchronization OFDM ED Threshold subfield, and its unit may be dBm.
- the indicated CCA threshold may be -72 dBm or more.
- the maximum CCA threshold indicated by the Medium Synchronization OFDM ED Threshold subfield may be -62 dBm.
- the Medium Synchronization OFDM ED Threshold subfield may be set to a value of 0 to 10. In this case, values of 11 to 15 may be reserved. That is, when the Medium Synchronization OFDM ED Threshold subfield value is 0 to 10, CCA thresholds of -72 dBm to -62 dBm may be indicated, respectively.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate MSD_TXOP_MAX. That is, the Medium Synchronization Maximum Number Of TXOPs subfield may indicate the maximum number of transmission attempts while MediumSyncDelay is applied.
- the Medium Synchronization Maximum Number Of TXOPs subfield may be 4-bit. According to an embodiment, the value of the Medium Synchronization Maximum Number Of TXOPs subfield may be the value of MSD_TXOP_MAX. According to another embodiment, the value of the Medium Synchronization Maximum Number Of TXOPs subfield may be (MSD_TXOP_MAX + 1).
- the value of the Medium Synchronization Maximum Number Of TXOPs subfield may be (MSD_TXOP_MAX - 1). Also, this may be limited to the case where the value of the Medium Synchronization Maximum Number Of TXOPs subfield is not set to the maximum value. If the value of the Medium Synchronization Maximum Number Of TXOPs subfield is set to the maximum value (15 in the case of 4-bit), it may indicate that there is no limit to the number of transmission attempts.
- 24 is a diagram illustrating an example of a MediumSyncDelay timer reset operation according to an embodiment of the present invention.
- MediumSyncDelay may be applied because there may be duration information, frames, or PPDUs that may not have been received while an STA belonging to an MLD operating on an NSTR link pair is blind.
- MediumSyncDelay may be a way to reduce the problem of limited channel access.
- the MediumSyncDelay timer may be reset (reset or set) to 0.
- an STA to which MediumSyncDelay is applied may have the same meaning as an STA in which MediumSyncDelay timer is a value other than 0.
- applying MediumSyncDelay by STA or MLD may have the same meaning as setting MediumSyncDelay timer to a value other than 0.
- resetting the MediumSyncDelay timer to 0 can mean the same as terminating MediumSyncDelay application.
- duration information may be included in a frame. More specifically, duration information may be included in the MAC header included in the frame. More specifically, duration information may be included in the Duration/ID field included in the MAC header. Therefore, when the STA to which MediumSyncDelay is applied receives a valid frame or MPDU during MediumSyncDelay, the MediumSyncDelay timer may be reset to 0.
- the STA to which MediumSyncDelay is applied receives a valid frame or MPDU during MediumSyncDelay
- the MediumSyncDelay timer may be reset to 0.
- what is described as a frame, MPDU, MAC header, Duration / ID field, and duration information may be replaced with each other.
- duration information may be included in the PPDU. More specifically, duration information may be included in the preamble included in the PPDU. More specifically, duration information may be included in the TXOP field included in the preamble. Also, the TXOP field may be included in the HE-SIG-A field included in the HE PPDU. In addition, the TXOP field may be included in the EHT PPDU or the U-SIG field included in the PPDU of a future standard rather than the EHT. When the STA receives the PPDU or TXOP field, the RXVECTOR parameter TXOP_DURATION may be set based on the TXOP field value.
- the RXVECTOR parameter may be a parameter transmitted from the STA's PHY to the MAC. Therefore, duration information may include RXVECTOR parameter TXOP_DURATION.
- duration information may include RXVECTOR parameter TXOP_DURATION.
- TXOP field or the RXVECTOR parameter TXOP_DURATION is set to UNSPECIFIED. If the TXOP field or RXVECTOR parameter TXOP_DURATION is set to UNSPECIFIED, this may mean that duration information does not exist.
- TXOP field or RXVECTOR parameter TXOP_DURATION is set to a value other than UNSPECIFIED, this may indicate that duration information exists.
- the MediumSyncDelay timer may be reset to 0.
- the MediumSyncDelay timer can be reset to 0.
- link 1 and link 2 may configure multi-link.
- AP 1 operating on link 1 may transmit a trigger frame.
- a trigger frame may solicit responses from multiple STAs.
- link 1 and link 2 for each STA of the plurality of STAs may be an NSTR link pair. That is, transmission on link 1 by STA 1, which is one of the STAs, may act as interference to STA 2 belonging to the same MLD as STA 1.
- an STA belonging to the same MLD as each STA of the plurality of STAs may be in a blind state, and when blinding ends, the MediumSyncDelay timer may be set to a value other than 0. That is, while multiple TB PPDUs are transmitted in response to the trigger frame, multiple STAs operating on link 2 may be blind, and multiple STAs may set the MediumSyncDelay timer to a value other than 0 after the TB PPDU transmission ends. there is.
- STA 1 of link 1 applies MediumSyncDelay
- STA 2 of link 1 starts to apply MediumSyncDelay, and at some point there may be a plurality of STAs whose MediumSyncDelay timer is not 0.
- 25 is a diagram illustrating an example of a MediumSyncDelay timer reset operation according to an embodiment of the present invention.
- the STA to which the medium sync delay is applied may operate the medium sync delay timer for applying the medium sync delay after the blind period ends, and the medium sync delay timer receives a valid PPDU except for a specific frame. It can be reset to '0'.
- the STA of the link to which MediumSyncDelay is applied may operate by setting the MediumSyncDelay timer to a value other than '0'. At this time, the MediumSyncDelay timer may be started at the point where transmission of another link ends. However, if the MLD is in EMLSR mode operating on a single radio, the MediumSyncDelay timer can start immediately after a specific delay. For example, the MediumSyncDelay timer may be started immediately after delay time for link switching or return to listening operation.
- the STA of the link to which MediumSyncDelay is applied receives a PPDU for a valid frame or a valid MPDU
- the MediumSyncDelay timer if it is not '0', it may reset the MediumSyncDelay timer to '0'.
- the MediumSyncDelay timer when receiving a PPDU having a value other than an unspecified value of TXOP_Duration, which is a reception parameter (RXVECTOR parameter), if the MediumSyncDelay timer is not '0', the MediumSyncDelay timer may be reset to '0'.
- valid frames may be frames other than RTS frames.
- the valid frame may be a frame transmitted by an AP other than the STA that caused the MediumSyncDelay or a non-AP STA.
- the valid frame transmitted by the AP includes the RTS frame, but the valid frame transmitted by the non-AP STA is It may be a frame other than the RTS frame.
- transmission/reception of one or more STAs on the second link is restricted due to a PPDU transmitted on the first link, and the MediumSyncDelay timer operates when the transmission of the PPDU ends, so that MediumSyncDelay is set to one or more STAs.
- one or more STAs on the second link may reset the MediumSyncDelay timer when a valid frame is received. That is, one or more STAs to which a specific frequency band is allocated may reset the MediumSyncDelay timer when receiving a PPDU for a valid MPDU excluding the RTS frame transmitted through 20 MHz of the same BSS or another BSS.
- one or more STAs may reset the MediumSyncDelay timer even if the received PPDU or frame is an RTS frame.
- whether the STA is allowed to reset the MediumSyncDelay timer to 0 based on whether the STA receives a valid frame (or MPDU) for which the MediumSyncDelay timer is not 0, based on whether this is a frame of the type allowed as the first frame during MediumSyncDelay. can be determined. According to an embodiment of the present invention, even if an STA whose MediumSyncDelay timer is not 0 receives a valid frame (or MPDU), if this is a frame allowed as the first frame during MediumSyncDelay, resetting the MediumSyncDelay timer to 0 is not allowed.
- a type of frame allowed as the first frame during MediumSyncDelay may be an RTS frame.
- a valid frame (or MPDU) is received by an STA whose MediumSyncDelay timer is not 0, it may be determined whether an operation of resetting the MediumSyncDelay timer to 0 is allowed based on whether this is an RTS frame. For example, when an STA whose MediumSyncDelay timer is not 0 receives an RTS frame, resetting the MediumSyncDelay timer to 0 may not be allowed. In addition, when an STA whose MediumSyncDelay timer is not 0 receives a frame other than an RTS frame, an operation of resetting the MediumSyncDelay timer to 0 may be allowed.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- the plurality of STAs may successfully receive the RTS frame. That is, the plurality of STAs can successfully receive duration information from the RTS frame.
- the plurality of STAs may not reset the MediumSyncDelay timer. Therefore, when the response to the RTS frame does not follow, the plurality of STAs can protect channel of link 2 or transmission on link 2 by maintaining MediumSyncDelay application.
- a CTS frame may be transmitted as a response to the RTS frame.
- STA 2 may transmit a frame (subsequent frame in the drawing). In this case, even if the plurality of STAs do not reset the MediumSyncDelay timer based on the RTS frame, it may be possible to reset the MediumSyncDelay timer based on the CTS frame or the subsequent frame. Therefore, unnecessary application of MediumSyncDelay can be prevented.
- the MediumSyncDelay timer may not be allowed. This may be because the PS-Poll frame does not include duration information. That is, when an STA whose MediumSyncDelay timer is not 0 receives a valid frame other than a PS-Poll frame, it may be allowed to reset the MediumSyncDelay timer.
- the STA determines whether the received frame (or PPDU) is an intra-BSS frame (or PPDU) or an inter-BSS frame (or PPDU) MAC address field included in the received frame or BSS color included in the PPDU containing the received frame It can be judged based on the field.
- the STA determines that the received frame is an intra-BSS frame when the MAC address field included in the received frame or the BSS color field included in the PPDU including the received frame is set to a value corresponding to the STA.
- the STA determines that the received frame is an inter-BSS frame when the MAC address field included in the received frame or the BSS color field included in the PPDU including the received frame is not set to a value corresponding to the STA.
- the frame or PPDU received by the STA is sent by an associated AP (or an AP included in the same multiple BSSID set as the associated AP)
- To reset the MediumSyncDelay timer Whether or not this is allowed can be determined. For example, if the MediumSyncDelay timer is not 0 and the frame or PPDU received by the STA is sent by an associated AP (or an AP included in the same multiple BSSID set as the associated AP), resetting the MediumSyncDelay timer may be allowed. .
- the MediumSyncDelay timer is not 0 and the frame or PPDU received by the STA is not sent by an associated AP (or an AP included in the same multiple BSSID set as the associated AP), resetting the MediumSyncDelay timer may not be allowed. This may be because the AP is highly likely to know the channel status of the corresponding link.
- the frame was sent by an associated AP (or an AP included in the same multiple BSSID set as the associated AP). For example, based on a TA (transmitter address) field included in the received frame, it may be determined whether the frame was sent by an associated AP (or an AP included in the same multiple BSSID set as the associated AP). For example, when the TA (transmitter address) field included in the received frame is set to the address of an associated AP (or an AP included in the same multiple BSSID set as the associated AP), the associated AP (or the same as the associated AP) AP included in multiple BSSID set) may have sent it.
- the TA (transmitter address) field included in the received frame is not an associated AP address and is not an address of an AP included in the same multiple BSSID set as the associated AP, it was not sent by the associated AP, but the associated AP and It may not be sent by an AP included in the same multiple BSSID set.
- the AP address may be replaced with a BSSID.
- the frame was sent to an associated AP (or an AP included in the same multiple BSSID set as the associated AP). For example, it may be determined whether the frame was sent to an associated AP (or an AP included in the same multiple BSSID set as the associated AP) based on a receiver or recipient address (RA) field included in the received frame. For example, when the RA field included in the received frame is set to the address of an associated AP (or an AP included in the same multiple BSSID set as the associated AP), the associated AP (or the same multiple BSSID set as the associated AP) included AP).
- RA receiver or recipient address
- the message was not sent to the associated AP, but the same multiple BSSID set as the associated AP. It may not have been sent to the AP included in .
- the AP address may be replaced with a BSSID.
- the frame is sent from inter-BSS, it can be determined based on the MAC address field included in the MAC header included in the received frame. For example, based on the RA, TA, or BSSID field included in the received frame, it may be determined whether the frame was sent from inter-BSS. For example, the RA field, TA field, and BSSID field included in the received frame (included in the condition only when each field exists) are all associated with the AP (or AP included in the same multiple BSSID set as the associated AP) If it is set to a value other than address, it may be sent from inter-BSS.
- At least one of the RA field, TA field, or BSSID field (included in the condition only when each field exists) included in the received frame is associated with the AP (or AP included in the same multiple BSSID set as the associated AP) If it is set as an address value, it may be sent from intra-BSS. In this embodiment, the AP address may be replaced with a BSSID.
- the received PPDU is an associated AP (or associated It may be sent by an AP included in the same multiple BSSID set as the AP). Otherwise, the received PPDU may not have been sent by an associated AP or by an AP included in the same multiple BSSID set as the associated AP.
- Multiple BSSIDs may be multiple BSSIDs indicated by a single Beacon frame or a single Probe Response frame. At this time, a plurality of Beacon frames or a plurality of Probe Response frames corresponding to each of a plurality of BSSIDs may not be used.
- a single TIM element included in a single Beacon frame or single TIM frame can be used to indicate buffered frames corresponding to multiple BSSIDs. For example, a single Beacon frame or a single Probe Response frame may be transmitted, and these frames may include multiple BSSID elements.
- the Multiple BSSID element may indicate multiple BSSs or multiple BSSIDs.
- a BSSID through which the single Beacon frame or the single probe response frame is transmitted may be referred to as a transmitted BSSID.
- a BSSID excluding a transmitted BSSID may be referred to as a nontransmitted BSSID.
- Beacon frame or Probe Response frame may not be transmitted.
- a set of BSSIDs indicated by one multiple BSSID element may be referred to as a multiple BSSID set.
- the described set of transmitted BSSID and nontransmitted BSSID may be referred to as multiple BSSID set.
- the maximum number of possible BSSIDs in a multiple BSSID set may be 2 ⁇ n.
- n may be a value signaled by multiple BSSID elements.
- n may be a value indicated by the MaxBSSID Indicator included in the Multiple BSSID element.
- the STA receiving the Multiple BSSID element can know the address or BSSID of the AP included in the Multiple BSSID set based on the received Multiple BSSID element.
- the received frame is a type of frame (RTS frame) allowed as the first frame during MediumSyncDelay and whether the sender or receiver of the frame is an associated AP (or an AP included in the same multiple BSSID set as an associated AP) Awareness can be considered together.
- RTS frame type of frame allowed as the first frame during MediumSyncDelay
- the sender or receiver of the frame is an associated AP (or an AP included in the same multiple BSSID set as an associated AP) Awareness can be considered together.
- MediumSyncDelay timer is not 0 and an STA receives a valid frame (or MPDU)
- this is the type of frame allowed as the first frame during MediumSyncDelay
- multiple BSSID sets identical to the associated AP or associated AP
- the frame is not transmitted by the AP included in the , resetting the MediumSyncDelay timer to 0 may not be allowed.
- the MediumSyncDelay timer is reset to 0. Actions may not be permitted.
- a type of frame allowed as the first frame during MediumSyncDelay may be an RTS frame. Therefore, even if an STA whose MediumSyncDelay timer is not 0 receives a valid frame (or MPDU), 1) this is an RTS frame, and 2) it is not a frame transmitted by an associated AP (or an AP included in the same multiple BSSID set as an associated AP). In this case, resetting the MediumSyncDelay timer to 0 may not be allowed.
- an operation of resetting the MediumSyncDelay timer to 0 may be allowed. That is, when an RTS frame transmitted by an associated AP (or an AP included in the same multiple BSSID set as an associated AP) is received, an operation of resetting the MediumSyncDelay timer to 0 may be allowed. In addition, when an RTS frame transmitted to an associated AP (or an AP included in the same multiple BSSID set as an associated AP) or transmitted in inter-BSS is received, resetting the MediumSyncDelay timer to 0 may not be allowed.
- the MediumSyncDelay timer is not 0 and the STA receives a valid frame (or MPDU)
- this is the type of frame allowed as the first frame during MediumSyncDelay
- the associated AP or the same multiple as the associated AP
- resetting the MediumSyncDelay timer to 0 may not be allowed.
- a type of frame allowed as the first frame during MediumSyncDelay may be an RTS frame. Therefore, even if an STA whose MediumSyncDelay timer is not 0 receives a valid frame (or MPDU), 1) this is an RTS frame, and 2) it is not a frame transmitted by an associated AP (or an AP included in the same multiple BSSID set as an associated AP). In this case, resetting the MediumSyncDelay timer to 0 may not be allowed.
- an operation of resetting the MediumSyncDelay timer to 0 may be allowed. That is, when an RTS frame transmitted by an associated AP (or an AP included in the same multiple BSSID set as an associated AP) is received, an operation of resetting the MediumSyncDelay timer to 0 may be allowed.
- an operation of resetting the MediumSyncDelay timer to 0 may be allowed.
- an operation of resetting the MediumSyncDelay timer to 0 may not be permitted.
- 26 is a diagram illustrating an example of medium synchronization OFDM ED threshold subfield encoding according to an embodiment of the present invention.
- a changed CCA threshold can be used during MediumSyncDelay. Also, at this time, the default value of the changed CCA threshold exists, and it is possible to signal the changed CCA threshold. In addition, it is possible to signal the changed CCA threshold using the previously described Medium Synchronization OFDM ED Threshold subfield. In the embodiment of the present invention, the above description may be omitted.
- the CCA ED threshold when MediumSyncDelay is not applied, the CCA ED threshold may be -62 dBm. However, depending on regulation, it is possible to use a CCA ED threshold lower than -62 dBm. It is possible to use a CCA ED threshold of -72 dBm in certain regions, eg europe. However, since the CCA threshold that can be indicated by the Medium Synchronization OFDM ED Threshold subfield described in FIG. 20 is -72 dBm or more, it may be difficult to achieve limiting channel access using a lower CCA threshold when MediumSyncDelay is applied. There is The embodiment of FIG. 23 may be a method for solving this problem.
- the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be a value smaller than -72 dBm.
- the minimum value that the Medium Synchronization OFDM ED Threshold subfield can indicate may be -82 dBm.
- the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -77 dBm.
- the maximum value that the Medium Synchronization OFDM ED Threshold subfield can indicate may be -62 dBm.
- the maximum value that the Medium Synchronization OFDM ED Threshold subfield can indicate may be -72 dBm.
- the default value of dot11MSDOFDMEDthreshold may be less than -72 dBm.
- the default value of dot11MSDOFDMEDthreshold may be the same as the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield.
- the default value of dot11MSDOFDMEDthreshold may be -77 dBm.
- the default value of dot11MSDOFDMEDthreshold may be -82 dBm.
- the default value of dot11MSDOFDMEDthreshold may be -72 dBm.
- the Medium Synchronization OFDM ED Threshold subfield value may be referred to as Fval.
- the Medium Synchronization OFDM ED Threshold subfield may be an integer.
- dot11MSDOFDMEDthreshold may be an integer in dBm.
- dot11MSDOFDMEDthreshold may be (-77 + Fval) dBm.
- the Medium Synchronization OFDM ED Threshold subfield may be 4-bit, and Fval may be an integer ranging from 0 to 15.
- dot11MSDOFDMEDthreshold indicated by Fvals 0 to 15 may be -77 to -62 dBm, respectively. That is, in this case, the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -77 dBm.
- the maximum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -62 dBm.
- the dot11MSDOFDMEDthreshold indicated by the Medium Synchronization OFDM ED Threshold subfield may not have a uniform interval.
- dot11MSDOFDMEDthreshold may be (-82 + 2*Fval) dBm.
- dot11MSDOFDMEDthreshold may be (-82 + 5 + Fval) dBm. That is, when Fval > A, dot11MSDOFDMEDthreshold may be (-77 + Fval) dBm.
- A may be 4. Therefore, referring to FIG.
- dot11MSDOFDMEDthreshold indicated by Fvals 0 to 15 is -82, -80, -78, -76, -74, -72, -71, -70, -69, -68, -67, - It can be 66, -65, -64, -63, -62 dBm. That is, in this case, the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -82 dBm. Also, the maximum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -62 dBm. In this embodiment, the size of the Medium Synchronization OFDM ED Threshold subfield may be 4-bit.
- the dot11MSDOFDMEDthreshold indicated by the Medium Synchronization OFDM ED Threshold subfield may not have a uniform interval.
- dot11MSDOFDMEDthreshold may be (-82 + Fval) dBm.
- dot11MSDOFDMEDthreshold may be (-92 + 2*Fval) dBm.
- B may be 10.
- dot11MSDOFDMEDthreshold indicated by Fval 0 to 15 is -82, -81, -80, -79, -78, -77, -76, -75, -74, -73, -72, -70, -68, It can be -66, -64, -62 dBm. That is, in this case, the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -82 dBm. Also, the maximum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -62 dBm. In this embodiment, the size of the Medium Synchronization OFDM ED Threshold subfield may be 4-bit.
- dot11MSDOFDMEDthreshold may be (-82 + 2*Fval) dBm.
- the Medium Synchronization OFDM ED Threshold subfield may be 4-bit, and Fval may be an integer ranging from 0 to 15.
- dot11MSDOFDMEDthreshold indicated by Fvals 0 to 10 may be -82, -80, -78, -76, -74, -72, -70, -68, -66, -64, and -62 dBm, respectively.
- Fvals 11 to 15 may be reserved.
- the minimum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -82 dBm.
- the maximum value indicated by the Medium Synchronization OFDM ED Threshold subfield may be -62 dBm.
- the size of the Medium Synchronization OFDM ED Threshold subfield may be 4-bit.
- the dot11MSDOFDMEDthreshold interval indicated by the Medium Synchronization OFDM ED Threshold subfield includes 2 dBm is shown, but other intervals are possible.
- the size of the Medium Synchronization OFDM ED Threshold subfield may be greater than 4-bit.
- the size of the Medium Synchronization OFDM ED Threshold subfield may be 5-bit. This may be for expressing a wider range of CCA thresholds than those described in FIG. 20 .
- possible Fvals may be 0 to 31.
- dot11MSDOFDMEDthreshold can be (-82 + Fval) dBm. Therefore, when Fval is 0 to 20, dot11MSDOFDMEDthreshold -82 dBm to -62 dBm may be indicated, respectively.
- values of Medium Synchronization OFDM ED Threshold subfields 21 to 31 may be reserved.
- the size of the Medium Synchronization OFDM ED Threshold subfield is larger than 4-bit
- the size of other subfields included in the Medium Synchronization Delay Information may need to be reduced to maintain the size of the Medium Synchronization Delay Information described in FIG. 20 .
- the Medium Synchronization Duration subfield can be less than 8-bit.
- the Medium Synchronization Duration subfield may be 7-bit.
- the Medium Synchronization Duration subfield may indicate a time in units of 32 us as described above. At this time, the time indicated by the Medium Synchronization Duration subfield may be up to 32*(2 ⁇ 7-1) us.
- the time indicated by the Medium Synchronization Duration subfield can be from 0 to 32*(2 ⁇ 7-1) us.
- the Medium Synchronization Duration subfield may indicate a time in units of 64 us. At this time, the time indicated by the Medium Synchronization Duration subfield may be up to 64*(2 ⁇ 7-1) us (8128 us). The time indicated by the Medium Synchronization Duration subfield can be from 0 to 64*(2 ⁇ 7-1) us.
- the Medium Synchronization Maximum Number Of TXOPs subfield may be less than 4-bit.
- the Medium Synchronization Maximum Number Of TXOPs subfield may be 3-bit.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate the number of transmission attempts in units of 1.
- MSD_TXOP_MAX can be indicated as an integer number of 0 to 6.
- MSD_TXOP_MAX may be indicated as an integer number of 1 to 6.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate the number of transmission attempts in units of 2.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate MSD_TXOP_MAX 0, 2, 4, 6, 8, 10, or 12.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate MSD_TXOP_MAX 2, 4, 6, 8, 10, 12, or 14.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate MSD_TXOP_MAX 1, 3, 5, 7, 9, 11, or 13.
- the Medium Synchronization Maximum Number Of TXOPs subfield may indicate MSD_TXOP_MAX 0, 1, 3, 5, 7, 9, or 11.
- Medium Synchronization Maximum Number Of TXOPs subfield indicates that there is no limit on the number of transmission attempts when the Medium Synchronization Maximum Number Of TXOPs subfield is set to the largest value (eg 3-bit to 7 value) even if it is less than 4-bit. can do.
- the maximum value that can be indicated by the Medium Synchronization OFDM ED Threshold subfield may be 1 smaller than the maximum value that can be indicated in the above-described embodiments. Also, at this time, each subfield value may be 1 smaller than that described above.
- the maximum value that the Medium Synchronization OFDM ED Threshold subfield can indicate may be -63 dBm.
- the Medium Synchronization OFDM ED Threshold subfields are 14 and 15, -64 and -63 dBm can be indicated, respectively.
- the time to set the MediumSyncDelay timer may be different from that of MLD operating in multi radio.
- the MediumSyncDelay timer is set at the end of transmission.
- the MediumSyncDelay timer can be set at the time when transmission is finished and the time based on the latency.
- the MediumSyncDelay timer can be set after latency has elapsed after receiving the PPDU including the immediate response. This may be limited to the case where the MLD operating with a single radio is a TXOP holder.
- the MediumSyncDelay timer may be set after latency has elapsed after transmitting the PPDU. This may be limited to the case where the MLD operating with a single radio is a TXOP holder.
- the MediumSyncDelay timer can be set after more latency has passed since the TXOP holder no longer transmits frames.
- MLD operating in single radio can set the MediumSyncDelay timer after latency has passed at the time when TXOP is terminated. In addition, this may be limited to the case where the MLD operating in a single radio is a TXOP responder.
- STAs operating in the NSTR link pair can operate by setting the MediumSyncDelay timer for applying MediumSyncDelay to a value other than '0'.
- the MediumSyncDelay timer may be operated at the point in time when the transmission of another STA ends.
- additional delays such as link switching to change from a single radio to multiple radios or a delay to return to a listening operation may be required. Therefore, in this case, the MediumSyncDelay timer can be operated after an additional delay after the end of transmission. For example, when the MLD operates in the EMLSR mode, the STA can operate the MediumSyncDelay timer immediately after returning to the listening operation.
- FIG. 27 is a diagram illustrating an example of a transmission operation when the MediumSyncDelay timer is not 0 according to an embodiment of the present invention.
- FIG. 27 may be for solving the problem described in FIG. 24 .
- the previously described details may have been omitted.
- an STA an STA belonging to an MLD
- reset the MediumSyncDelay timer it may be determined whether reset is allowed based on the type of the received frame.
- the type of frame may be determined based on a value included in the MAC header of the frame. More specifically, the type of frame may be determined based on the Frame Control field included in the MAC header. More specifically, the type of frame may be determined based on the Type subfield and/or Subtype subfield included in the Frame Control field.
- the Type subfield may be located at bits of bit indices B2 to B3 of the Frame Control field.
- the Subtype subfield may be located at bits of bit indexes B4 to B7 of the Frame Control field.
- the frame type may be determined based on the Type subfield and/or Subtype subfield and/or Control Frame Extension subfield included in the Frame Control field.
- the Control Frame Extension subfield may be located at bits of bit indexes B8 to B11 of the Frame Control field.
- B3 and B2 of the Type subfield when B3 and B2 of the Type subfield are 00, 01, and 10, it may indicate that frames including the Type subfield are Management frame, Control frame, and Data frame, respectively. Also, B3 and B2 of the Type subfield are 11
- Type extension can be indicated.
- the RTS frame may be a frame soliciting the CTS frame.
- the RTS frame may be a frame soliciting a CTS frame from a single STA.
- the RTS frame may include a Frame Control field, Duration field, RA field, TA field, and FCS field.
- the Duration field may include time information for setting NAVs by STAs receiving the Duration field.
- the RA field may include the address of the intended immediate recipient. For example, when the RA field included in the RTS frame received by the STA is the address of the STA, it is possible to respond with a CTS frame to the RTS frame. Also, whether a frame is an RTS frame can be determined based on a Frame Control field included in the frame.
- whether a frame is an RTS frame can be determined based on the Type subfield and Subtype subfield included in the Frame Control field included in the frame. For example, when the Type subfield is 01 (B3 B2) and the Subtype subfield is 1011 (B7 B6 B5 B4), it may indicate that a frame including the Type subfield and the Subtype subfield is an RTS frame.
- the RTS frame may be a control frame.
- the STA in order to solve the problem described in FIG. 21, it can be determined whether or not the MediumSyncDelay timer can be reset based on the type of frame received.
- the problem described in FIG. 22 may not be completely solved because the STA can reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION according to the resetting condition described above.
- the STA can reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION according to the resetting condition described above.
- the MediumSyncDelay timer of one of these STAs is not 0, it can transmit a frame based on limited channel access.
- the transmitted frame may be an RTS frame.
- the STA receiving the PPDU transmitted by the one STA may receive the PPDU including the RXVECTOR parameter TXOP_DURATION. Therefore, the STA receiving the PPDU transmitted by the one STA can reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION even if the MediumSyncDelay timer is not reset based on the RTS frame. That is, since there may be multiple STAs that receive the PPDU transmitted by the one STA, it is possible for multiple STAs to reset the MediumSyncDelay timer.
- the MediumSyncDelay timer may be reset unnecessarily. For example, STAs resetting the MediumSyncDelay timer may transmit frames based on unrestricted channel access, thereby disrupting frame exchange in existing transmission.
- non-HT PPDU or non-HT duplicate PPDU
- HT may mean high throughput, IEEE 802.11n standard.
- VHT may mean a very high throughput, IEEE 802.11ac standard.
- HE may mean a high efficiency, IEEE 802.11ax standard.
- EHT may mean extremely high throughput, IEEE 802.11be standard.
- the TXOP field may be included in the preamble of the PPDU. More specifically, the TXOP field may be included in the HE-SIG-A field or U-SIG field. Also, the HE PPDU may include a HE-SIG-A field. EHT PPDU may include a U-SIG field. That is, the HE PPDU or EHT PPDU may include a TXOP field. For example, a TXOP field may be included in the preamble of the PPDU. In addition, a non-HT PPDU (or non-HT duplicate PPDU), HT PPDU, and VHT PPDU may not include a TXOP field.
- the STA when an STA receives a PPDU including a TXOP field, the STA may receive a PPDU in which the RXVECTOR parameter TXOP_DURATION exists. In addition, when the STA transmits a PPDU including the TXOP field, the STA may transmit a PPDU in which the TXVECTOR parameter TXOP_DURATION exists.
- the PPDU format when an STA transmits a MediumSyncDelay timer other than 0.
- the PPDU format is restricted when transmitting the first frame in TXOP.
- the STA may not transmit (or use) a PPDU including the TXOP field.
- the STA may transmit a PPDU that does not include the TXOP field.
- the STA may transmit a non-HT PPDU, a non-HT duplicate PPDU, a HT PPDU, or a VHT PPDU without transmitting a HE PPDU or EHT PPDU. More specifically, if there is a restriction on the PPDU format, the STA may transmit a non-HT PPDU or a non-HT duplicate PPDU.
- an STA whose MediumSyncDelay timer is not 0 may not transmit using a PPDU format including a TXOP field.
- an STA whose MediumSyncDelay timer is not 0 may transmit using a PPDU format that does not include a TXOP field.
- this may be limited to when transmitting the first frame of TXOP. That is, an STA whose MediumSyncDelay timer is not 0 may not transmit the first frame of the TXOP using a PPDU format including the TXOP field.
- an STA whose MediumSyncDelay timer is not 0 may transmit the first frame of the TXOP using a PPDU format that does not include the TXOP field.
- the RTS frame may be transmitted as the first frame of the TXOP.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- a PPDU without a TXOP field may be used.
- non-HT PPDU, non-HT duplicate PPDU, HT PPDU, and VHT PPDU may be used. Accordingly, even if the STA applying MediumSyncDelay receives the frame or PPDU transmitted by STA 2, it does not receive the TXOP field, so the RXVECTOR parameter TXOP_DURATION does not exist.
- the STA receiving the frame or PPDU transmitted by STA 2 may not reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION.
- the MediumSyncDelay timer may not be reset based on the frame type transmitted by STA 2. Therefore, even if the STA to which MediumSyncDelay is applied receives the PPDU including the first frame or the first frame transmitted by STA 2, the MediumSyncDelay timer will not be reset based on the first frame or the PPDU including the first frame. can Therefore, when the response to the RTS frame does not follow, the plurality of STAs can protect channel of link 2 or transmission on link 2 by maintaining MediumSyncDelay application.
- a CTS frame may be transmitted as a response to the RTS frame. Also, following the CTS frame, STA 2 may transmit a frame (subsequent frame in the drawing). In this case, even if the plurality of STAs do not reset the MediumSyncDelay timer based on the RTS frame, it may be possible to reset the MediumSyncDelay timer based on the CTS frame or the subsequent frame. Therefore, applying MediumSyncDelay unnecessarily can be prevented.
- FIG. 28 is a diagram illustrating another example of a transmission operation when the MediumSyncDelay timer is not 0 according to an embodiment of the present invention.
- FIG. 28 may be for solving the problem described in FIG. 24 .
- the previously described details may have been omitted.
- the PPDU including the TXOP field is used, so that the STA receiving the PPDU resets the MediumSyncDelay timer based on the TXOP field.
- the TXVECTOR parameter TXOP_DURATION when the STA transmits when the MediumSyncDelay timer is not 0.
- the TXVECTOR parameter TXOP_DURATION can be set to UNSPECIFIED. If the TXVECTOR parameter TXOP_DURATION is set to UNSPECIFIED, duration information may not exist in the TXOP field. In addition, this may be limited to the case where the STA transmits the first frame of the TXOP.
- the TXVECTOR parameter TXOP_DURATION may be set to UNSPECIFIED. Accordingly, even if the RXVECTOR parameter TXOP_DURATION exists, the STA receiving such a PPDU may not reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION because the value is set to UNSPECIFIED.
- the TXOP field may be set to 127. That is, when the TXOP field is 7 bits, setting all bits to 1 may indicate UNSPECIFIED.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- the TXVECTOR parameter TXOP_DURATION may be set to UNSPECIFIED. Therefore, even if one STA among the plurality of STAs receives the PPDU transmitted by STA 2, the RXVECTOR parameter TXOP_DURATION may be set to UNSPECIFIED. Therefore, the one STA may not reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION.
- the one STA may not reset the MediumSyncDelay timer based on the first frame or PPDU of the TXOP transmitted by STA 2.
- the one STA can reset the MediumSyncDelay timer based on the succeeding frame or PPDU.
- 29 is a diagram illustrating another example of a MediumSyncDelay timer reset operation according to an embodiment of the present invention.
- FIG. 29 may be for solving the problem described in FIG. 24 .
- the previously described details may have been omitted.
- an STA whose MediumSyncDelay timer is not 0 can reset the MediumSyncDelay timer based on the received frame (or duration information included in the frame) or PPDU (or RXVECTOR parameter TXOP_DURATION).
- PPDU or RXVECTOR parameter TXOP_DURATION
- the STA for which MediumSyncDelay timer is not 0 receives both the frame (or duration information included in the frame) and the PPDU preamble (or RXVECTOR parameter TXOP_DURATION), the PPDU preamble (or RXVECTOR parameter TXOP_DURATION), the MediumSyncDelay timer may not be reset. Also, in this case, the STA whose MediumSyncDelay timer is not 0 may be able to reset the MediumSyncDelay timer based on the frame (or duration information included in the frame). Reception at this time may mean successful reception or reception of a valid one. Also, at this time, the embodiment described in FIG. 22 can be used together.
- TXOP field TXVECTOR parameter TXOP_DURATION
- RXVECTOR parameter TXOP_DURATION may be used interchangeably.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- STA 2 may transmit using a PPDU including a TXOP field.
- one STA whose MediumSyncDelay timer is not 0 can successfully receive both the TXOP field and the frame from the PPDU transmitted by STA 2.
- the one STA may not reset the MediumSyncDelay timer based on the TXOP field.
- the MediumSyncDelay timer may not be reset based on the RTS frame.
- the one STA can reset the MediumSyncDelay timer based on the subsequent frame or PPDU.
- resetting the MediumSyncDelay timer may not be allowed.
- the MediumSyncDelay timer is not 0 and the frame or PPDU received by the STA corresponds to inter-BSS, it may be allowed to reset the MediumSyncDelay timer. This may be for protecting an intra-BSS frame or an intra-BSS PPDU.
- whether or not to reset the MediumSyncDelay timer when an STA whose MediumSyncDelay timer is not 0 receives a frame or PPDU may be based on whether the frame or PPDU is uplink or downlink.
- resetting the MediumSyncDelay timer may not be allowed.
- the STA whose MediumSyncDelay timer is not 0 receives a frame or PPDU, and it is a downlink, it may be allowed to reset the MediumSyncDelay timer.
- the downlink frame (or PPDU) is transmitted by the AP
- the AP is highly likely to know the overall channel situation of the BSS
- the uplink frame (or PPDU) is transmitted by a non-AP STA, and the non-AP STA This is because they may not know the overall channel status of the BSS compared to the AP.
- Whether a frame or PPDU is uplink or downlink may be based on a preamble of the PPDU including the frame or signaling included in the preamble of the PPDU.
- the preamble may include a UL/DL field or an Uplink field.
- the UL/DL field or Uplink field may be 1-bit, and may indicate uplink or downlink.
- the preamble may include a Group ID field.
- the Group ID field may be set to a preset value depending on whether the PPDU including the Group ID field is uplink or downlink.
- whether a frame or PPDU is uplink or downlink may be determined based on a MAC header included in a frame included in the frame or PPDU.
- the MAC header may include a MAC address.
- the MAC address may indicate whether it is uplink or downlink. For example, when a TA (transmitter address) field is set to the MAC address of an AP, a frame including the TA field may be downlink. When the RA (receiver address) field is set to the MAC address of the AP, a frame including the RA field may be uplink. or
- whether or not to reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION when an STA whose MediumSyncDelay timer is not 0 receives a PPDU is determined based on whether the PPDU is uplink or downlink. For example, if the UL/DL field indicates uplink when a PPDU is received by an STA whose MediumSyncDelay timer is not 0, it may not be allowed to reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION. If the UL/DL field indicates downlink when the STA receives the PPDU with the MediumSyncDelay timer not equal to 0, it may be allowed to reset the MediumSyncDelay timer based on the RXVECTOR parameter TXOP_DURATION.
- an embodiment in which it is determined whether resetting the MediumSyncDelay timer is allowed based on whether the received frame or PPDU is uplink or downlink is whether the frame or the PPDU corresponds to intra-BSS, inter-BSS Depending on whether or not to perform can be determined. That is, whether or not resetting the MediumSyncDelay timer is allowed may be determined based on whether the received frame or PPDU corresponds to 1) uplink or downlink and 2) intra-BSS or inter-BSS. For example, when the received frame or PPDU corresponds to intra-BSS, it may be determined whether resetting the MediumSyncDelay timer is allowed based on whether it is uplink or downlink according to the above-described embodiment.
- the received frame or PPDU when the received frame or PPDU corresponds to inter-BSS, it may be allowed to reset the MediumSyncDelay timer regardless of whether it is uplink or downlink. For example, when the received frame or PPDU is intra-BSS and uplink, resetting the MediumSyncDelay timer may not be allowed. Also, when the received frame or PPDU is intra-BSS and downlink, resetting the MediumSyncDelay timer may be allowed. In addition, when the received frame or PPDU is inter-BSS, it may be allowed to reset the MediumSyncDelay timer regardless of uplink or downlink.
- FIG. 30 is a diagram illustrating an example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- the STA with MediumSyncDelay timer when the STA with MediumSyncDelay timer is not 0 successfully receives the L preamble, it may be possible to reset the MediumSyncDelay timer.
- the L preamble may be a legacy preamble or a legacy preamble described above, such as in FIG. 7 .
- the L preamble may be referred to as a non-HT PHY preamble. This is because the L preamble is a preamble of non-HT (duplicate) PPDU format.
- an operation when the L preamble is successfully received may be the same as an operation when the L-SIG field is successfully received. This is because the L preamble includes the L-SIG field. Also, the L-SIG field may be present at the end of the L preamble.
- the L-SIG field when the L-SIG field is successfully received, it may be when a field indicating the duration of a PHY protocol data unit (PPDU) including the L-SIG field is successfully received.
- PPDU PHY protocol data unit
- the PPDU It is possible to determine the length of Also, the length of the PPDU including the L-SIG field may be determined based on the RATE field and the LENGTH field included in the L-SIG field.
- the RATE field and the LENGTH field may be the above-described L_RATE field and L_LENGTH field, respectively.
- the L preamble may include L-STF, L-LTF, and L-SIG fields.
- L-STF, L-LTF, and L-SIG fields may occupy 8 us, 8 us, and 4 us, respectively, from the front of the PPDU. That is, the L preamble may exist 20 us before the PPDU.
- the L-SIG field may include RATE, reserved, LENGTH, parity, and SIGNAL TAIL fields.
- RATE and LENGTH may be referred to as a value indicated by the RATE field (Mbps) and a value of the LENGTH field, respectively.
- LENGTH can be set as follows.
- TXTIME may be PPDU transmission length or PPDU length.
- SignalExtension may be the length of signal extension. SignalExtension may be 0 us in the 5 GHz band or the 6 GHz band. SignalExtension may be 6 us in the 2.4 GHz band.
- m may be 1 or 2 for the HE PPDU. In addition, m may be 0 for PPDUs other than the HE PPDU (ie, non-HT (duplicate) PPDU, HT PPDU, VHT PPDU, EHT PPDU, etc.).
- RXTIME or PPDU length can be calculated as follows. This may be the PPDU length indicated by L-SIG (or LENGTH field and RATE field),
- RXTIME Ceil( (LENGTH+3) / (RATE/8*4) ) * 4 + 20 + SignalExtension
- values that RATE can indicate may be 6, 9, 12, 18, 24, 36, 48, or 54 Mbps. This may be an embodiment when the channel spacing is 20 MHz.
- the RATE field value indicating a value that can be indicated by the aforementioned RATE may be when the values from LSB to MSB of the RATE field are 1101, 1111, 0101, 0111, 1001, 1011, 0001, and 0011, respectively. That is, when the RATE field is 1101, the rate indicated by the RATE field may be 6 Mbps.
- RATE is 6 Mbps
- LENGTH may be as follows.
- RXTIME Ceil( (LENGTH+3) / 3 ) * 4 + 20 + SignalExtension
- resetting the MediumSyncDelay timer may be because the duration of the PPDU including the L preamble is successfully received and determined.
- the STA when it successfully receives the L preamble, it may determine that the medium is busy or may not perform medium (channel) access during the duration of the PPDU including the L preamble.
- it may be difficult to protect the frame exchange sequence compared to the embodiment of resetting based on valid duration information or valid MPDU or RXVECTOR parameter TXOP_DURATION described in FIGS. 21 to 26.
- the embodiment of FIG. 27 may reset the MediumSyncDelay timer and increase the possibility of quick channel access compared to the embodiments described in FIGS. 21 to 26 . This is because there may be cases in which the L preamble is successfully received and valid duration information or valid MPDU or RXVECTOR parameter TXOP_DURATION is not successfully received because the L preamble exists in the front part of the PPDU.
- the embodiment for solving the problem of resetting the MediumSyncDelay timer based on the first frame or RTS frame during MediumSyncDelay described in FIGS. 24 to 25 and 27 to 29 can be applied to the embodiment of FIG. 30 .
- the embodiment referred to as the first frame or RTS frame during MediumSyncDelay is not limited thereto, and it may be possible to substitute and apply the first frame during RTS frame or MediumSyncDelay, respectively.
- whether a received frame is an RTS frame may be determined based on the duration when whether to reset is determined based on whether the received frame is an RTS frame.
- duration may be PPDU duration.
- the MediumSyncDelay timer when the MediumSyncDelay timer is not 0 and the STA successfully receives the L preamble, resetting the MediumSyncDelay timer only when the duration of the PPDU including the L preamble is longer than the duration of the RTS frame that could be possible That is, when the duration of the PPDU including the L preamble is less than or equal to the duration of the RTS frame, the MediumSyncDelay timer may not be reset.
- the PPDU duration may be as follows. If the value indicated by RATE is 6, 9, 12, 18, 24, 36, 48, or 54 Mbps, it may be 52, 44, 36, 32, 28, 28, 24, or 24 us, respectively. Therefore, when a PPDU equal to or shorter than 52 us is received, the MediumSyncDelay timer may not be reset.
- the PPDU length can be calculated as follows.
- PPDU duration Ceil( (FrameOctet * 8 + ServiceTailBits) / RATE / 4 ) * 4 + Preamble
- FrameOctet may be an octet number in MAC frame format.
- FrameOctet may be 20.
- ServiceTailBits may be the sum of the number of bits of the service field and the tail bit.
- ServiceTailBits may be 22 bits.
- RATE may be the aforementioned RATE.
- 4 may be an OFDM symbol length (us).
- Preamble may be the length of L preamble in case of non-HT PPDU or non-HT duplicate PPDU. That is, in case of non-HT PPDU or non-HT duplicate PPDU, the preamble may be 20 us.
- the STA with MediumSyncDelay timer when the STA with MediumSyncDelay timer is not 0 successfully receives the L preamble, resetting the MediumSyncDelay timer only when the duration of the PPDU including the L preamble is longer than the duration of the RTS frame.
- the duration of the PPDU including the L preamble is longer than the duration of the RTS frame.
- Reset the MediumSyncDelay timer it is possible to determine the duration of the RTS frame based on the LENGTH field and the RATE field. That is, the threshold for comparing the duration of the PPDU may be different based on the received RATE field value.
- the duration of the PPDU including the RTS frame may assume that the RTS frame is included in a non-HT PPDU or a non-HT duplicate PPDU.
- the duration of the PPDU including the RTS frame may be determined by considering the preamble length and/or data rate of the corresponding PPDU format when the PPDU format including the RTS frame is determined.
- the MediumSyncDelay timer when a frame having the same or smaller octet number than the RTS frame is received.
- the CF-End frame or the PS-Poll frame may have the same octet number as the RTS frame of 20 octets.
- the Ack frame or the CTS frame may have a smaller octet number than the RTS frame.
- An Ack frame or CTS frame may be 14 octets.
- the MediumSyncDelay timer even when a PPDU using a high data rate is received, it may be difficult to reset the MediumSyncDelay timer. For example, even if the octet number of the frame is greater than that of the RTS frame, it can be transmitted as a short PPDU using a high MCS, and in this case, it may be difficult to reset the MediumSyncDelay timer because the PPDU duration is below the threshold.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- STA 3 (for example, one of the plurality of STAs) for which MediumSyncDelay timer is not 0 is a PPDU including the RTS frame or a PPDU including a CTS frame following it or a PPDU including a subsequent frame following the CTS frame Based on this, it can be determined whether or not to reset the MediumSyncDelay timer.
- the MediumSyncDelay timer when STA 3 successfully receives the L preamble, it may be determined whether it is possible to reset the MediumSyncDelay timer based on the PPDU duration indicated by the L preamble. If the PPDU duration is greater than the PPDU duration including the RTS frame, it may be possible to reset, and if it is less than or equal to, it may be impossible to reset.
- the PPDU duration including the RTS frame may be 52 us.
- the PPDU duration including the RTS frame is 52, 44, 36, 32, 28, 28, 24 when the RATE field indicates 6, 9, 12, 18, 24, 36, 48, and 54 Mbps, respectively. , can be 24 us. This may be the case where the RTS frame is included in a non-HT PPDU or a non-HT duplicate PPDU.
- STA 3 may be impossible for STA 3 to reset the MediumSyncDelay timer based on the PPDU including the RTS frame and the PPDU including the CTS frame. If STA 3 receives a PPDU including subsequent frames, it may determine whether it is possible to reset the MediumSyncDelay timer based on the conditions described above.
- FIG. 31 is a diagram illustrating another example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- FIG. 31 is a diagram illustrating MediumSyncDelay timer reset according to an embodiment of the present invention.
- FIG. 31 may be an embodiment for solving the problem described in FIG. 30 . Also, you may have omitted the previously described details.
- whether a received frame is an RTS frame may be determined based on the duration when whether to reset is determined based on whether the received frame is an RTS frame.
- duration may be PPDU duration.
- the MediumSyncDelay timer when the MediumSyncDelay timer is not 0 and the STA successfully receives the L preamble, resetting the MediumSyncDelay timer only when the duration of the PPDU including the L preamble is different from the duration of the RTS frame that could be possible That is, when the duration of the PPDU including the L preamble is equal to the duration of the RTS frame, the MediumSyncDelay timer may not be reset. That is, compared to the embodiment described in FIG.
- the MediumSyncDelay timer is reset even if the duration of the PPDU including the L preamble is shorter than the duration of the RTS frame it may be possible to do
- the duration of the RTS frame may be the same as described in FIG. 27.
- the MediumSyncDelay timer cannot be reset if they are identical, and if they are not identical, it may be possible to reset the MediumSyncDelay timer.
- the present embodiment even when a frame smaller or shorter than the RTS frame or a high data rate or MCS is used, it may be possible to reset the MediumSyncDelay timer based on such a frame or PPDU.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- STA 3 (for example, one of the plurality of STAs) for which MediumSyncDelay timer is not 0 is a PPDU including the RTS frame or a PPDU including a CTS frame following it or a PPDU including a subsequent frame following the CTS frame Based on this, it can be determined whether or not to reset the MediumSyncDelay timer.
- the PPDU duration including the RTS frame may be 52 us.
- the PPDU duration including the RTS frame is 52, 44, 36, 32, 28, 28, 24 when the RATE field indicates 6, 9, 12, 18, 24, 36, 48, and 54 Mbps, respectively. , can be 24 us. This may be the case where the RTS frame is included in a non-HT PPDU or a non-HT duplicate PPDU.
- STA 3 may be unable to reset the MediumSyncDelay timer based on the PPDU including the RTS frame. Also, when STA 3 receives the PPDU including the CTS frame, it may be possible to reset the MediumSyncDelay timer based on the PPDU including the CTS frame. If STA 3 receives a PPDU including subsequent frames, it may determine whether it is possible to reset the MediumSyncDelay timer based on the conditions described above.
- an STA existing in a location hidden from the STA that transmitted the RTS frame may be able to reset the MediumSyncDelay timer based on the CTS frame or the PPDU including the CTS frame.
- the octet number of the frame is different from that of the RTS frame, it can be transmitted as a PPDU with the same length as the case where the RTS frame is included using a high MCS. In this case, it is difficult to reset the MediumSyncDelay timer because the PPDU duration is equal to the threshold.
- PPDUs (HT PPDU, VHT PPDU, HE PPDU, EHT PPDU) other than non-HT PPDU or non-HT duplicate PPDU always set the RATE field included in the L-SIG field to a preset value, for example 6 Mbps can be set to a value indicating
- the actually used rate may be included in a field (eg, HT-SIG, VHT-SIG-A, HE-SIG-A, U-SIG, EHT-SIG field, etc.) included after the L-SIG field. Therefore, when determining the PPDU duration based on the RATE field included in the L-SIG field, the same duration as the PPDU including the RTS frame may be calculated even if the PPDU does not include the RTS frame.
- FIG. 32 is a diagram illustrating another example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- FIG. 32 may be an embodiment for solving the problems described in FIGS. 30 to 31 . Also, you may have omitted the previously described details. In particular, the previously described content regarding duration may have been omitted.
- a method for determining whether it is possible to reset the MediumSyncDelay timer may be different depending on whether a frame (MAC frame) is received.
- the method for determining whether it is possible to reset the MediumSyncDelay timer may be different depending on whether a frame is received or only a preamble is received without receiving a frame.
- the MediumSyncDelay timer when a frame is received from the PPDU, it may be possible to reset the MediumSyncDelay timer based on the embodiment described in FIGS. 25 and 27 to 29 . For example, when a frame is received from the PPDU, it may be possible to reset the MediumSyncDelay timer when the frame is not an RTS frame. Alternatively, when a frame is received from the PPDU, it may be possible to reset the MediumSyncDelay timer when the frame is not an RTS frame or a PS-Poll frame.
- a frame is not received from the PPDU, it may be possible to reset the MediumSyncDelay timer based on the embodiment described in FIGS. 30 to 31. For example, when a frame is not received from the PPDU or when an L preamble is successfully received from the PPDU, it may be possible to reset the MediumSyncDelay timer (the embodiment of FIG. 30). Alternatively, when no frame is received from the PPDU, when an L preamble is successfully received from the PPDU and the duration of the PPDU is greater than the duration of the PPDU including the RTS frame, it may be possible to reset the MediumSyncDelay timer (Fig. Example of 30).
- the duration of the RTS frame or the duration of the PPDU including the RTS frame may be the same as those described in FIGS. 30 to 31.
- the MediumSyncDelay timer cannot be reset if they are identical, and if they are not identical, it may be possible to reset the MediumSyncDelay timer.
- the STA when the STA receives a frame other than an L preamble or an RTS frame, it may be possible to reset the MediumSyncDelay timer. At this time, the STA may be a STA whose MediumSyncDelay timer value is not 0. Received may also mean successful reception.
- the STA 1) when the STA 1) receives an L preamble and the duration is longer than the duration of the RTS frame, or 2) receives a frame other than the RTS frame, it may be possible to reset the MediumSyncDelay timer.
- the duration may be a duration indicated by the LENGTH field included in the L preamble or L-SIG field. That is, when the STA receives the RTS frame in the received PPDU, it may be impossible to reset the MediumSyncDelay timer.
- the STA receives a CTS frame, CF-End frame, or PS-Poll frame in the received PPDU, it may be possible to reset the MediumSyncDelay timer.
- the MediumSyncDelay timer can be reset "or 3) when RXVECTOR parameter TXOP_DURATION, which is not an UNSPECIFIED value, is received" in the condition 1) or 2).
- the STA 1) when the STA 1) receives an L preamble and the duration is different from the duration of the RTS frame, or 2) receives a frame other than the RTS frame, it may be possible to reset the MediumSyncDelay timer.
- the duration may be a duration indicated by the LENGTH field included in the L preamble or L-SIG field. That is, when the STA receives the RTS frame in the received PPDU, it may be impossible to reset the MediumSyncDelay timer.
- the STA receives a CTS frame, CF-End frame, or PS-Poll frame in the received PPDU, it may be possible to reset the MediumSyncDelay timer.
- the MediumSyncDelay timer can be reset "or 3) when RXVECTOR parameter TXOP_DURATION, which is not an UNSPECIFIED value, is received" in the condition 1) or 2).
- the above-described embodiment can be used together with the reset condition.
- the above-described embodiment can be used together with the reset condition. For example, not only when a frame other than the RTS frame is received, but even when an RTS frame is received, it may be possible to reset the RTS frame transmitted by an associated AP or an AP corresponding to a BSSID included in the same multiple BSSID set as the associated AP.
- an embodiment of determining whether a reset is possible based on an uplink or a downlink may be used together.
- a plurality of STAs operating on link 2 may apply MediumSyncDelay.
- STA 2 of link 2 applying MediumSyncDelay may obtain a TXOP and transmit an RTS frame as the first frame.
- STA 3 (for example, one of the plurality of STAs) for which MediumSyncDelay timer is not 0 is a PPDU including the RTS frame or a PPDU including a CTS frame following it or a PPDU including a subsequent frame following the CTS frame Based on this, it can be determined whether or not to reset the MediumSyncDelay timer.
- STA 3 when STA 3 successfully receives the L preamble, it may be determined whether it is possible to reset the MediumSyncDelay timer based on the PPDU duration indicated by the L preamble. In this case, STA 3 may be unable to reset the MediumSyncDelay timer based on the L preamble of the PPDU including the RTS frame. Alternatively, when STA 3 receives a frame other than the RTS frame, it may be possible to reset the MediumSyncDelay timer. Therefore, even if STA 3 receives the RTS frame following the L preamble of the PPDU including the RTS frame, it may be impossible to reset the MediumSyncDelay timer.
- the duration of the PPDU including the subsequent frame received by STA 3 is the same as the duration of the PPDU including the RTS frame, it may be possible to reset the MediumSyncDelay timer when STA 3 receives the subsequent frame. Alternatively, it may be possible to reset the MediumSyncDelay timer even when STA 3 receives the CTS frame.
- the received PPDU or frame is the intra-BSS It may be limited to being reset only when corresponding to . This is because only the STA's basic NAV is set, and a frame or PPDU may be transmitted when the intra-BSS NAV is not set. For example, when only the STA's basic NAV is set and the intra-BSS NAV is not set, the intra-BSS AP or associated AP transmits a triggering frame (trigger frame or frame including TRS Control) to the STA. It may be possible for the STA to transmit a frame or PPDU.
- a triggering frame trigger frame or frame including TRS Control
- FIG 33 is a diagram illustrating another example of resetting the MediumSyncDelay timer according to an embodiment of the present invention.
- the MediumSyncDelay timer there may be an operation of resetting the MediumSyncDelay timer. Also, as described above, whether or not to perform a resetting operation may be based on the type of the received frame. In addition, whether or not to perform the resetting operation may be based on which STA transmitted the received frame. In the present invention, the above description may be omitted.
- the plurality of STAs may include STAs (ie, APs) belonging to an AP MLD.
- STAs ie, APs
- the AP MLD operates on an NSTR link pair.
- Such AP MLD may be referred to as NSTR AP MLD, NSTR mobile AP MLD, or NSTR soft AP MLD.
- AP 1 and AP 2 may belong to an AP MLD that is an NSTR mobile AP MLD. Also, AP 1 and AP 2 can operate on link 1 and link 2, respectively. NSTR mobile AP MLD and association (multi-link setup) non-AP MLD may exist. STA 1 and STA 2 may belong to the non-AP MLD. Also, STA 1 and STA 2 may operate on link 1 and link 2, respectively. Link 1 and link 2 may be a primary link and a nonprimary link, respectively. For example, there may be a case where AP 1 and STA 1 perform frame exchange. AP 1 may transmit PPDU 1. Also, STA 1 may transmit PPDU 2.
- the MediumSyncDely timer can be started when AP 2 is out of blind.
- STA 1 transmits PPDU 2
- this transmission acts as interference to STA 2
- STA 2 may be blinded while transmitting PPDU 2.
- the MediumSyncDely timer may be started when STA 2 is out of blind. In this way, there may be a case where the MediumSyncDelay timer of a plurality of STAs including the AP is not 0.
- the existing frame exchange can be interrupted by resetting the MediumSyncDelay timer based on the first frame. That is, in FIG. 30, AP 2 may transmit the RTS frame as the first frame while MediumSyncDelay timer is not 0 (for example, this first frame may be transmitted to STA 3 rather than STA 2), and receive it One STA 2 may reset the MediumSyncDelay timer based on the first frame. In this case, STA 2 may start transmission and cause interference to frame exchange in transmission.
- NSTR mobile AP MLD can configure, assign, and designate primary and nonprimary links.
- the NSTR mobile AP MLD and the non-AP MLD with multi-link setup can receive and determine information about which link is the primary link and which link is the non-primary link from the NSTR mobile AP MLD.
- the NSTR mobile AP MLD may be able to transmit a Beacon frame, a Probe Response frame, an Association Response frame, and a Reassociation Response frame only on the primary link.
- the NSTR mobile AP MLD may be unable to transmit a Beacon frame, a Probe Response frame, an Association Response frame, and a Reassociation Response frame on a nonprimary link.
- non-AP MLDs that have (or intend to do) multi-link setup with NSTR mobile AP MLDs may be able to transmit Probe Request frames, Association Request frames, and Reassociation Request frames only on the primary link.
- a non-AP MLD that is associated with (or intends to do) multi-link setup with the NSTR mobile AP MLD may not be able to transmit the Probe Request frame, Association Request frame, or Reassociation Request frame on the nonprimary link.
- the NSTR mobile AP MLD or the non-AP MLD associated with the NSTR mobile AP MLD may necessarily use the primary link together to start TXOP (start frame transmission) on the nonprimary link.
- TXOP start frame transmission
- the primary link may need to start PPDU transmission simultaneously with the nonprimary link.
- there may be a backoff procedure for simultaneously starting PPDU transmission on the primary link and the nonprimary link. For example, a backoff counter value of 0 can be maintained in a link in which the backoff counter reaches 0, and PPDU transmission can be started in a link with a backoff counter 0 when the backoff counter reaches 0 in another link.
- the AP MLD may indicate whether it is an NSTR mobile AP MLD or an AP MLD other than the NSTR mobile AP MLD (AP MLD operating in an STR link pair).
- the Multi-Link element described in FIG. 20 may include the indication.
- the MLD Capabilities field of the Common Info field included in the Multi-Link element may include the indication.
- the B7 bit of the MLD Capabilities field may indicate the indication. The indication may be present when the AP MLD transmits the Multi-Link element. For example, when the NSTR mobile AP MLD transmits the Multi-Link element, the bit value may be set to 1.
- the bit value may be set to 0.
- a non-AP MLD receiving the bit may determine based on the bit whether the Multi-Link element including the bit is an NSTR mobile AP MLD.
- the NSTR mobile AP MLD transmits the Reduced Neighbor Report element
- only the MLD Parameters subfield may be included in the TBTT Information field corresponding to the NSTR mobile AP MLD.
- an AP MLD other than the NSTR mobile AP MLD transmits a Reduced Neighbor Report element
- the Reduced Neighbor Report element may be included in a Beacon frame, a Probe Response frame, an Association Response frame, and a Reassociation Response frame.
- a non-AP MLD receiving the TBTT Information field can determine whether the AP MLD corresponding to the TBTT Information field is an NSTR mobile AP MLD or not depending on whether the TBTT Information field includes only the MLD Parameters field. Whether the TBTT Information field includes only the MLD Parameters subfield may be determined based on a field indicating the length or type of the TBTT Information field. For example, the MLD Parameters subfield may have a preset length, for example, 3-octet. In addition, when the value indicating the length of the TBTT Information field indicates the preset length, it can be determined that the TBTT Information field includes only the MLD Parameters subfield and the TBTT Information field corresponds to the NSTR mobile AP MLD.
- a STA whose MediumSyncDelay timer is not 0 receives a valid frame (or MPDU)
- MediumSyncDelay based on whether the AP MLD associated (multi-link setup) by the STA is the NSTR mobile AP MLD It can determine whether resetting the timer is allowed.
- the frame received by the STA is a frame of a type allowed as the first frame and is not a frame transmitted by an associated AP (or an AP included in the same multiple BSSID set as an associated AP)
- MediumSyncDelay The operation to reset the timer to 0 was not allowed.
- the frame received by the STA is not a type of frame allowed as the first frame or is a frame transmitted by an associated AP (or an AP included in the same multiple BSSID set as an associated AP), resetting the MediumSyncDelay timer to 0 Action allowed.
- this may be limited to the case where the associated AP (or an AP included in the same multiple BSSID set as an associated AP) belongs to an AP MLD other than the NSTR mobile AP MLD.
- a valid frame (or MPDU) is received by an STA whose MediumSyncDelay timer is not 0, 1) it is not a frame of a type allowed as the first frame during MediumSyncDelay, or 2) an associated AP belonging to an AP MLD other than the NSTR mobile AP MLD ( Alternatively, if the frame is transmitted by an AP included in the same multiple BSSID set as an associated AP), an operation of resetting the MediumSyncDelay timer to 0 may be allowed.
- the associated AP belongs to the NSTR mobile AP MLD, and the associated AP transmits the received frame, The operation of resetting the MediumSyncDelay timer to 0 may not be permitted.
- the frame received by the STA is a type of frame allowed as the first frame during MediumSyncDelay (eg RTS frame), the associated AP belongs to an AP MLD other than the NSTR mobile AP MLD, and the associated AP transmits the received frame In one case, resetting the MediumSyncDelay timer to 0 may be allowed.
- the frame received by the STA is a type of frame allowed as the first frame during MediumSyncDelay (eg RTS frame) and the associated AP does not transmit the received frame, resetting the MediumSyncDelay timer to 0 is not allowed. may not be
- the frame received by the STA is not a type of frame allowed as the first frame during MediumSyncDelay (eg, RTS frame)
- an operation of resetting the MediumSyncDelay timer to 0 may be allowed.
- the STA receiving the frame may be an STA in a state in which the MediumSyncDelay timer value is not 0.
- the above embodiment of determining whether to allow MediumSyncDelay reset based on whether the frame is transmitted by the associated AP may be limited to when the non-AP MLD determines. If the NSTR mobile AP MLD determines whether to allow MediumSyncDelay reset, it can determine whether or not to allow the MediumSyncDelay reset regardless of who transmitted the received frame. For example, when NSTR mobile AP MLD determines whether to allow MediumSyncDelay reset, regardless of who transmitted the received frame, it can be determined based only on whether or not the received frame is a type of frame allowed as the first frame during MediumSyncDelay. .
- an STA belonging to the NSTR mobile AP MLD receives a valid frame
- the frame is not a type of frame (eg RTS frame) allowed as the first frame during MediumSyncDelay
- the operation of resetting the MediumSyncDelay timer to 0 this may be allowed.
- the frame is a type of frame allowed as the first frame during MediumSyncDelay (eg RTS frame)
- the operation of resetting the MediumSyncDelay timer to 0 is allowed It may not be.
- 34 is a flowchart illustrating an example of an operation of a non-AP MLD according to an embodiment of the present invention.
- the MediumSyncDelay timer for applying MediumSyncDelay may be reset to '0' in a specific case.
- a multi-link device including a plurality of stations each operating on a plurality of links including a first link and a second link is one of one or more stations (STAs)
- the frame transmitted from the STA of may be received through the second STA operating in the second link (S34010).
- the medium sync delay timer is not '0', resetting the medium sync delay timer for applying the medium sync delay of the second STA based on the received frame. It can (S34020).
- STAs operating in the NSTR link pair may operate by setting the medium sync delay timer to a value other than '0'.
- the medium sync delay timer may be operated at the time when transmission of another STA ends.
- additional delays such as link switching to change from a single radio to multiple radios or a delay to return to a listening operation may be required. Therefore, in this case, the MediumSyncDelay timer can be operated after an additional delay after the end of transmission. For example, when the MLD operates in the EMLSR mode, the STA can operate the MediumSyncDelay timer immediately after returning to the listening operation.
- an STA of a link to which a medium sync delay is applied may reset the medium sync delay timer to '0' if the medium sync delay timer is not '0'.
- TXOP_Duration which is a reception parameter (RXVECTOR parameter)
- the MediumSyncDelay timer may be reset to '0'.
- valid frames may be frames other than RTS frames.
- the first link and the second link may be NSTR (Non-Simultaneous Transmission and Reception) link pairs that do not support simultaneous transmission/reception within the same MLD because transmission/reception in each link causes interference in another link. there is.
- NSTR Non-Simultaneous Transmission and Reception
- transmission/reception of one or more STAs on the second link is restricted due to a PPDU transmitted on the first link, and the MediumSyncDelay timer operates when the transmission of the PPDU ends, so that MediumSyncDelay is set to one or more STAs.
- one or more STAs on the second link may reset the MediumSyncDelay timer when a valid frame is received. That is, one or more STAs to which a specific frequency band is allocated may reset the MediumSyncDelay timer when receiving a PPDU for a valid MPDU excluding the RTS frame transmitted through 20 MHz of the same BSS or another BSS.
- one or more STAs may reset the MediumSyncDelay timer even if the received PPDU or frame is an RTS frame.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (12)
- 제1 링크 및 제2 링크를 포함하는 복수 개의 링크들에서 각각 동작하는 복수 개의 스테이션들을 포함하는 멀티 링크 장치(Multi-link Device: MLD)에서,프로세서는,하나 이상의 스테이션(Station: STA)들 중 하나의 STA으로부터 전송된 프레임을 상기 제2 링크에서 동작하는 제2 STA을 통해서 수신하고,미디엄 싱크 지연 타이머가 '0'이 아니면, 상기 수신된 프레임에 기초하여 상기 제2 STA의 미디엄 싱크 지연(Medium Sync Delay)의 적용을 위한 미디엄 싱크 지연 타이머(Medium Sync Delay timer)를 리셋 하되,상기 미디엄 싱크 지연은 상기 제1 링크를 통해서 상기 제1 STA의 데이터 송/수신 이후, 상기 제2 링크를 통한 데이터 송/수신을 제한하기 위한 구간을 나타나며,상기 미디엄 싱크 지연 타이머는 상기 프레임이 RTS(request to send) 프레임을 제외한 유효한 MPDU에 대한 프레임인 경우 리셋되는 MLD
- 제1 항에 있어서,상기 제1 링크와 상기 제2 링크는 각 링크에서의 송/수신이 다른 링크에서 간섭을 발생시켜 동일한 MLD 내에서 동시 송/수신을 지원하지 않는 NSTR(Non- Simultaneous Transmission and Reception) 링크 쌍인 MLD.
- 제2 항에 있어서,상기 미디엄 싱크 지연 타이머는 상기 제1 링크에서의 전송이 끝난 시점에 시작되는 MLD.
- 제1 항에 있어서,상기 MLD가 단일 라디오(Single Radio)로 동작하는 경우, 상기 미디엄 싱크 지연 타이머는 상기 제1 링크에서의 전송이 끝난 이후 특정 지연 시간이 지난 시점에 시작되는 MLD.
- 제4 항에 있어서,상기 특정 지연 시간은 링크 스위칭을 위한 지연 시간인 MLD.
- 제1 항에 있어서,상기 미디엄 싱크 지연 타이머는 상기 프레임이 상기 제2 STA와 결합된(Associated) AP 또는 상기 결합된 AP와 동일한 다중 BSSID set에 포함된 AP로부터 전송된 프레임인 경우 리셋되는 MLD.
- 무선 통신 시스템에서 제1 링크 및 제2 링크를 포함하는 복수 개의 링크들에서 각각 동작하는 복수 개의 스테이션들을 포함하는 멀티 링크 장치(Multi-link Device: MLD)에 의해서 수행되는 방법에 있어서, 상기 방법은,하나 이상의 스테이션(Station: STA)들 중 하나의 STA으로부터 전송된 프레임을 상기 제2 링크에서 동작하는 제2 STA을 통해서 수신하는 단계; 및미디엄 싱크 지연 타이머가 '0'이 아니면, 상기 수신된 프레임에 기초하여 상기 제2 STA의 미디엄 싱크 지연(Medium Sync Delay)의 적용을 위한 미디엄 싱크 지연 타이머(Medium Sync Delay timer)를 리셋하는 단계를 포함하되,상기 미디엄 싱크 지연은 상기 제1 링크를 통해서 상기 제1 STA의 데이터 송/수신 이후, 상기 제2 링크를 통한 데이터 송/수신을 제한하기 위한 구간을 나타나며,상기 미디엄 싱크 지연 타이머는 상기 프레임이 RTS(request to send) 프레임을 제외한 유효한 MPDU에 대한 프레임인 경우 리셋되는 방법.
- 제7 항에 있어서,상기 제1 링크와 상기 제2 링크는 각 링크에서의 송/수신이 다른 링크에서 간섭을 발생시켜 동일한 MLD 내에서 동시 송/수신을 지원하지 않는 NSTR(Non- Simultaneous Transmission and Reception) 링크 쌍인 방법.
- 제8 항에 있어서,상기 미디엄 싱크 지연 타이머는 상기 제1 링크에서의 전송이 끝난 시점에 시작되는 방법.
- 제7 항에 있어서,상기 MLD가 단일 라디오(Single Radio)로 동작하는 경우, 상기 미디엄 싱크 지연 타이머는 상기 제1 링크에서의 전송이 끝난 이후 특정 지연 시간이 지난 시점에 시작되는 방법.
- 제10 항에 있어서,상기 특정 지연 시간은 링크 스위칭을 위한 지연 시간인 방법.
- 제7 항에 있어서,상기 미디엄 싱크 지연 타이머는 상기 프레임이 상기 제2 STA와 결합된(Associated) AP 또는 상기 결합된 AP와 동일한 다중 BSSID set에 포함된 AP로부터 전송된 프레임인 경우 리셋되는 방법.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020237043789A KR20240013151A (ko) | 2021-06-19 | 2022-06-20 | 멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는무선 통신 단말 |
EP22825402.5A EP4358635A1 (en) | 2021-06-19 | 2022-06-20 | Wireless communication method using multilink, and wireless communication terminal using same |
US18/389,634 US20240129866A1 (en) | 2021-06-19 | 2023-12-19 | Wireless communication method using multilink, and wireless communication terminal using same |
Applications Claiming Priority (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR20210079667 | 2021-06-19 | ||
KR10-2021-0079667 | 2021-06-19 | ||
KR20210082262 | 2021-06-24 | ||
KR10-2021-0082262 | 2021-06-24 | ||
KR20210103938 | 2021-08-06 | ||
KR10-2021-0103938 | 2021-08-06 | ||
KR10-2021-0159671 | 2021-11-18 | ||
KR20210159671 | 2021-11-18 | ||
KR10-2022-0041391 | 2022-04-01 | ||
KR20220041391 | 2022-04-01 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/389,634 Continuation US20240129866A1 (en) | 2021-06-19 | 2023-12-19 | Wireless communication method using multilink, and wireless communication terminal using same |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022265479A1 true WO2022265479A1 (ko) | 2022-12-22 |
Family
ID=84527574
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/008730 WO2022265479A1 (ko) | 2021-06-19 | 2022-06-20 | 멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는 무선 통신 단말 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20240129866A1 (ko) |
EP (1) | EP4358635A1 (ko) |
KR (1) | KR20240013151A (ko) |
TW (1) | TW202325085A (ko) |
WO (1) | WO2022265479A1 (ko) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005159451A (ja) * | 2003-11-20 | 2005-06-16 | Matsushita Electric Ind Co Ltd | データ送信装置及びデータ受信装置 |
KR20080113642A (ko) * | 2007-06-25 | 2008-12-31 | 한국과학기술정보연구원 | 이동노드의 tcp 성능 개선을 위한 수직적 핸드오프 장치및 운용방법 |
KR101656999B1 (ko) * | 2015-05-11 | 2016-09-12 | 금오공과대학교 산학협력단 | 무선 랜의 협력 통신 방법 및 시스템 |
-
2022
- 2022-06-20 KR KR1020237043789A patent/KR20240013151A/ko unknown
- 2022-06-20 WO PCT/KR2022/008730 patent/WO2022265479A1/ko active Application Filing
- 2022-06-20 TW TW111122937A patent/TW202325085A/zh unknown
- 2022-06-20 EP EP22825402.5A patent/EP4358635A1/en active Pending
-
2023
- 2023-12-19 US US18/389,634 patent/US20240129866A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005159451A (ja) * | 2003-11-20 | 2005-06-16 | Matsushita Electric Ind Co Ltd | データ送信装置及びデータ受信装置 |
KR20080113642A (ko) * | 2007-06-25 | 2008-12-31 | 한국과학기술정보연구원 | 이동노드의 tcp 성능 개선을 위한 수직적 핸드오프 장치및 운용방법 |
KR101656999B1 (ko) * | 2015-05-11 | 2016-09-12 | 금오공과대학교 산학협력단 | 무선 랜의 협력 통신 방법 및 시스템 |
Non-Patent Citations (2)
Title |
---|
SHARAN NARIBOLE (SAMSUNG): "Multi-Link Operation Channel Access Discussion", IEEE DRAFT; 11-19-1405-07-00BE-MULTI-LINK-OPERATION-CHANNEL-ACCESS-DISCUSSION, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 7, 14 November 2019 (2019-11-14), Piscataway, NJ USA , pages 1 - 18, XP068164763 * |
SHARAN NARIBOLE (SAMSUNG): "Non-STR Blindness Rules Discussion", IEEE DRAFT; 11-20-1263-02-00BE-NON-STR-BLINDNESS-RULES-DISCUSSION, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 2, 30 November 2020 (2020-11-30), Piscataway, NJ USA , pages 1 - 14, XP068175311 * |
Also Published As
Publication number | Publication date |
---|---|
TW202325085A (zh) | 2023-06-16 |
US20240129866A1 (en) | 2024-04-18 |
KR20240013151A (ko) | 2024-01-30 |
EP4358635A1 (en) | 2024-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022075821A1 (ko) | 무선 통신 시스템에서 프레임을 송수신하기 위한 방법 및 무선 통신 단말 | |
WO2017022898A1 (ko) | 무선 통신 시스템에서 데이터 전송 방법 및 이를 위한 장치 | |
WO2016089059A1 (ko) | 무선 통신 시스템에서 데이터 전송 방법 및 이를 위한 장치 | |
WO2016159513A1 (ko) | 무선 통신 시스템의 데이터 전송 방법 및 장치 | |
WO2016186469A1 (ko) | 무선랜 시스템에서 nav를 관리하는 방법 및 이를 위한 장치 | |
WO2016099139A1 (ko) | 무선 통신 시스템에서 데이터 전송 방법 및 이를 위한 장치 | |
WO2022050802A1 (ko) | 무선 통신 시스템에서 데이터를 송수신하기 위한 방법 및 무선 통신 단말 | |
WO2016053024A1 (ko) | 무선 통신 시스템에서 데이터 전송 방법 및 이를 위한 장치 | |
WO2016021838A1 (ko) | 무선 통신 시스템에서 프레임 전송 방법 및 이를 위한 장치 | |
WO2020050528A1 (ko) | Rf의 최대 전송 가능한 대역폭이 서로 다른 무선장치가 있는 wlan 환경에서 최적화된 위상 회전을 적용하는 방법 및 장치 | |
WO2016028124A1 (ko) | 무선 통신 시스템에서 데이터 전송 방법 및 이를 위한 장치 | |
WO2016024750A1 (ko) | 무선 통신 시스템에서 하향링크 다중 사용자 전송 방법 및 이를 위한 장치 | |
WO2016143970A1 (ko) | 무선 통신 시스템의 데이터 전송 방법 및 장치 | |
WO2016028125A2 (ko) | 무선 통신 시스템에서 상향링크 전송 방법 및 이를 위한 장치 | |
WO2016182390A1 (ko) | 무선랜 시스템에서 프레임을 송수신하는 방법 및 이를 위한 장치 | |
WO2016032258A2 (ko) | 무선 통신 시스템에서 데이터 전송 방법 및 이를 위한 장치 | |
WO2022164293A1 (ko) | 멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는 무선 통신 단말 | |
WO2016068582A1 (ko) | 무선 통신 시스템에서의 데이터 전송 방법 및 이를 위한 장치 | |
WO2022025629A1 (ko) | 멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는 무선 통신 단말 | |
WO2022035291A1 (ko) | 무선 통신 시스템에서 데이터를 송수신하기 위한 방법 및 무선 통신 단말 | |
WO2022114907A1 (ko) | 무선 통신 시스템에서 다중 링크(multi-link)를 통해 데이터를 송수신하기 위한 방법 및 무선 통신 단말 | |
WO2022149858A1 (ko) | 무선 통신 시스템에서 데이터를 송수신하기 위한 방법 및 무선 통신 단말 | |
WO2022260486A1 (ko) | 멀티 링크를 사용하는 무선 통신 방법 및 이를 사용하는 무선 통신 단말 | |
WO2016122086A1 (ko) | 무선 통신 시스템의 송수신 장치 및 방법 | |
WO2016175439A1 (ko) | 무선 통신 시스템의 데이터 전송 방법 및 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22825402 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20237043789 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2023578123 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022825402 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022825402 Country of ref document: EP Effective date: 20240119 |