WO2022240210A1 - 무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 수정 방법 및 장치 - Google Patents
무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 수정 방법 및 장치 Download PDFInfo
- Publication number
- WO2022240210A1 WO2022240210A1 PCT/KR2022/006802 KR2022006802W WO2022240210A1 WO 2022240210 A1 WO2022240210 A1 WO 2022240210A1 KR 2022006802 W KR2022006802 W KR 2022006802W WO 2022240210 A1 WO2022240210 A1 WO 2022240210A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- twt
- information
- sta
- frame
- end time
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 123
- 230000005540 biological transmission Effects 0.000 claims abstract description 80
- 230000004048 modification Effects 0.000 claims description 72
- 238000012986 modification Methods 0.000 claims description 72
- 230000015654 memory Effects 0.000 claims description 27
- 230000009471 action Effects 0.000 claims description 24
- 230000008093 supporting effect Effects 0.000 claims description 23
- 238000012545 processing Methods 0.000 claims description 11
- 238000010586 diagram Methods 0.000 description 51
- 230000004044 response Effects 0.000 description 44
- 101100161473 Arabidopsis thaliana ABCB25 gene Proteins 0.000 description 43
- 101100096893 Mus musculus Sult2a1 gene Proteins 0.000 description 43
- 101150081243 STA1 gene Proteins 0.000 description 43
- 230000008569 process Effects 0.000 description 42
- 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 34
- 101000988961 Escherichia coli Heat-stable enterotoxin A2 Proteins 0.000 description 34
- 239000010410 layer Substances 0.000 description 29
- 238000004891 communication Methods 0.000 description 27
- 101000752249 Homo sapiens Rho guanine nucleotide exchange factor 3 Proteins 0.000 description 23
- 102100021689 Rho guanine nucleotide exchange factor 3 Human genes 0.000 description 23
- 230000006870 function Effects 0.000 description 23
- 238000005516 engineering process Methods 0.000 description 16
- 230000007246 mechanism Effects 0.000 description 15
- 230000003111 delayed effect Effects 0.000 description 13
- 238000007726 management method Methods 0.000 description 13
- 101100395869 Escherichia coli sta3 gene Proteins 0.000 description 12
- 239000000523 sample Substances 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 10
- 230000011664 signaling Effects 0.000 description 7
- 101100172132 Mus musculus Eif3a gene Proteins 0.000 description 6
- 238000012549 training Methods 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- HMUNWXXNJPVALC-UHFFFAOYSA-N 1-[4-[2-(2,3-dihydro-1H-inden-2-ylamino)pyrimidin-5-yl]piperazin-1-yl]-2-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)ethanone Chemical compound C1C(CC2=CC=CC=C12)NC1=NC=C(C=N1)N1CCN(CC1)C(CN1CC2=C(CC1)NN=N2)=O HMUNWXXNJPVALC-UHFFFAOYSA-N 0.000 description 2
- LDXJRKWFNNFDSA-UHFFFAOYSA-N 2-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)-1-[4-[2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidin-5-yl]piperazin-1-yl]ethanone Chemical compound C1CN(CC2=NNN=C21)CC(=O)N3CCN(CC3)C4=CN=C(N=C4)NCC5=CC(=CC=C5)OC(F)(F)F LDXJRKWFNNFDSA-UHFFFAOYSA-N 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 230000001976 improved effect Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 108700026140 MAC combination Proteins 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 238000002789 length control Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
- H04W74/0875—Non-scheduled access, e.g. ALOHA using a dedicated channel for access with assigned priorities based access
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
- H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
- H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/002—Transmission of channel access control information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- 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]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present disclosure relates to a target wake time (TWT) operation in a wireless local area network (WLAN) system, and more particularly, to modification of a restricted-TWT (Restricted-TWT) service period in a next-generation wireless LAN system. It relates to methods and devices.
- TWT target wake time
- WLAN wireless local area network
- Wi-Fi wireless local area network
- technologies recently introduced to wireless LANs include enhancements for VHT (Very High-Throughput) of the 802.11ac standard, and enhancements for HE (High Efficiency) of the IEEE 802.11ax standard. do.
- VHT Very High-Throughput
- HE High Efficiency
- EHT Extremely High Throughput
- MIMO multiple input multiple output
- APs multiple access points
- a technical problem of the present disclosure is to provide a method and apparatus for transmitting latency-sensitive traffic in a WLAN system.
- An additional technical problem of the present disclosure is to provide a method and apparatus related to modification of a limited TWT service period (SP) in a wireless LAN system.
- SP limited TWT service period
- An additional technical problem of the present disclosure is to provide a method and apparatus for requesting or instructing extension of an endpoint of a limited TWT SP in a WLAN system.
- a method for performing frame exchange by a station (STA) in a WLAN system includes: receiving limited target wake time (r-TWT) related information from an access point (AP); receiving, from the AP, information related to a modified end time of the r-TWT SP after the starting time of the r-TWT service period (SP) based on the r-TWT related information; and performing the frame exchange based on the modified end time point of the r-TWT SP.
- r-TWT limited target wake time
- SP r-TWT service period
- a method for performing frame exchange by an access point (AP) in a wireless LAN system includes: transmitting limited target wake time (r-TWT) related information to one or more first stations (STAs). ; After the start time of the r-TWT service period (SP) based on the r-TWT related information, one or more second STAs including the one or more first STAs transmit information related to the modified end time of the r-TWT SP sending to; and performing the frame exchange with the one or more second STAs based on the modified end time of the r-TWT SP.
- r-TWT limited target wake time
- a method and apparatus for transmitting latency-sensitive traffic in a WLAN system may be provided.
- a method and apparatus related to modification of a limited TWT service period (SP) in a wireless LAN system may be provided.
- a method and apparatus for requesting or instructing extension of an end point of a limited TWT SP in a wireless LAN system may be provided.
- FIG. 1 illustrates a block configuration diagram of a wireless communication device according to an embodiment of the present disclosure.
- FIG. 2 is a diagram illustrating an exemplary structure of a WLAN system to which the present disclosure may be applied.
- FIG 3 is a diagram for explaining a link setup process to which the present disclosure may be applied.
- FIG. 4 is a diagram for explaining a backoff process to which the present disclosure may be applied.
- FIG. 5 is a diagram for explaining a frame transmission operation based on CSMA/CA to which the present disclosure may be applied.
- FIG. 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.
- FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure may be applied.
- 8 to 10 are diagrams for explaining examples of resource units of a WLAN system to which the present disclosure can be applied.
- FIG. 11 shows an exemplary structure of a HE-SIG-B field.
- FIG. 12 is a diagram for explaining a MU-MIMO method in which a plurality of users/STAs are allocated to one RU.
- FIG. 13 shows an example of a PPDU format to which the present disclosure can be applied.
- FIG. 14 is a diagram for explaining an example of an individual TWT operation to which the present disclosure can be applied.
- 15 is a diagram for explaining an example of a broadcast TWT operation to which the present disclosure can be applied.
- 16 is a diagram for explaining an example of a TWT information field format.
- 17 is a diagram for explaining an example of a TWT information element format.
- 18 is a diagram for explaining examples of individual TWT parameter set field formats.
- 19 is a diagram for explaining examples of a broadcast TWT parameter set field format.
- 20 is a diagram for explaining an example of a limited TWT operation.
- 21 is a diagram for explaining modification of a starting point of an r-TWT SP.
- 22 is a diagram for explaining an example of a modified r-TWT SP according to the present disclosure.
- FIG. 23 is a diagram for explaining an example of a limited TWT operation.
- 24 is a diagram for explaining an example of a modified r-TWT SP according to the present disclosure.
- 25 is a diagram for explaining an operation of an STA supporting a modified r-TWT SP according to an embodiment of the present disclosure.
- 26 is a diagram for explaining an operation of an AP supporting a modified r-TWT SP according to an embodiment of the present disclosure.
- first and second are used only for the purpose of distinguishing one component from another component and are not used to limit the components, unless otherwise specified. The order or importance among them is not limited. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment. can also be called
- Examples of the present disclosure may be applied to various wireless communication systems.
- examples of the present disclosure may be applied to a wireless LAN system.
- examples of the present disclosure may be applied to an IEEE 802.11a/g/n/ac/ax standards-based wireless LAN.
- examples of the present disclosure may be applied to a wireless LAN based on the newly proposed IEEE 802.11be (or EHT) standard.
- Examples of the present disclosure may be applied to a wireless LAN based on the IEEE 802.11be Release-2 standard corresponding to an additional improvement technology of the IEEE 802.11be Release-1 standard.
- examples of the present disclosure may be applied to a next-generation standards-based wireless LAN after IEEE 802.11be.
- examples of this disclosure may be applied to a cellular wireless communication system.
- a cellular wireless communication system based on Long Term Evolution (LTE)-based technology and 5G New Radio (NR)-based technology of the 3rd Generation Partnership Project (3GPP) standard.
- LTE Long Term Evolution
- NR 5G New Radio
- FIG. 1 illustrates a block configuration diagram of a wireless communication device according to an embodiment of the present disclosure.
- the first device 100 and the second device 200 illustrated in FIG. 1 are a terminal, a wireless device, a wireless transmit receive unit (WTRU), a user equipment (UE), and a mobile station (MS). ), UT (user terminal), MSS (Mobile Subscriber Station), MSS (Mobile Subscriber Unit), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), or simply user. term can be replaced.
- the first device 100 and the second device 200 include an access point (AP), a base station (BS), a fixed station, a Node B, a base transceiver system (BTS), a network, It can be replaced with various terms such as AI (Artificial Intelligence) system, RSU (road side unit), repeater, router, relay, and gateway.
- AP access point
- BS base station
- BTS base transceiver system
- AI Artificial Intelligence
- RSU road side unit
- repeater router, relay, and gateway.
- the devices 100 and 200 illustrated in FIG. 1 may also be referred to as stations (STAs).
- the devices 100 and 200 illustrated in FIG. 1 may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, and a receiving STA.
- the STAs 110 and 200 may perform an access point (AP) role or a non-AP role. That is, in the present disclosure, the STAs 110 and 200 may perform functions of an AP and/or a non-AP.
- AP access point
- the STAs 110 and 200 may perform functions of an AP and/or a non-AP.
- an AP may also be indicated as an AP STA.
- the first device 100 and the second device 200 may transmit and receive wireless signals through various wireless LAN technologies (eg, IEEE 802.11 series).
- the first device 100 and the second device 200 may include an interface for a medium access control (MAC) layer and a physical layer (PHY) conforming to the IEEE 802.11 standard.
- MAC medium access control
- PHY physical layer
- the first device 100 and the second device 200 may additionally support various communication standards (eg, 3GPP LTE series, 5G NR series standards, etc.) technologies other than wireless LAN technology.
- the device of the present disclosure may be implemented in various devices such as a mobile phone, a vehicle, a personal computer, augmented reality (AR) equipment, and virtual reality (VR) equipment.
- the STA of the present specification includes voice call, video call, data communication, autonomous-driving, machine-type communication (MTC), machine-to-machine (M2M), device-to-device (D2D), Various communication services such as IoT (Internet-of-Things) may be supported.
- MTC machine-type communication
- M2M machine-to-machine
- D2D device-to-device
- IoT Internet-of-Things
- the first device 100 includes one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and/or one or more antennas 108.
- the processor 102 controls the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or flowcharts of operations set forth in this disclosure.
- the processor 102 may process information in the memory 104 to generate first information/signal, and transmit a radio signal including the first information/signal through the transceiver 106 .
- the processor 102 may receive a radio signal including the second information/signal through the transceiver 106, and then store information obtained from signal processing of the second information/signal in the memory 104.
- the memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102 .
- memory 104 may perform some or all of the processes controlled by processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure. (instructions) may be stored.
- the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a wireless LAN technology (eg, IEEE 802.11 series).
- the transceiver 106 may be coupled to the processor 102 and may transmit and/or receive wireless signals via one or more antennas 108 .
- the transceiver 106 may include a transmitter and/or a receiver.
- the transceiver 106 may be used interchangeably with a radio frequency (RF) unit.
- a device may mean a communication modem/circuit/chip.
- the second device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208.
- the processor 202 controls the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or flowcharts of operations set forth in this disclosure.
- the processor 202 may process information in the memory 204 to generate third information/signal, and transmit a radio signal including the third information/signal through the transceiver 206 .
- the processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 and store information obtained from signal processing of the fourth information/signal in the memory 204 .
- the memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202 .
- memory 204 may perform some or all of the processes controlled by processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed in this disclosure. It may store software codes including them.
- the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement a wireless LAN technology (eg, IEEE 802.11 series).
- the transceiver 206 may be coupled to the processor 202 and may transmit and/or receive wireless signals via one or more antennas 208 .
- the transceiver 206 may include a transmitter and/or a receiver.
- the transceiver 206 may be used interchangeably with an RF unit.
- a device may mean a communication modem/circuit/chip.
- one or more protocol layers may be implemented by one or more processors 102, 202.
- one or more processors 102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC).
- One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) in accordance with the descriptions, functions, procedures, proposals, methods and/or operational flow charts disclosed herein.
- PDUs Protocol Data Units
- SDUs Service Data Units
- One or more processors 102, 202 may generate messages, control information, data or information in accordance with the descriptions, functions, procedures, proposals, methods and/or operational flow diagrams set forth in this disclosure.
- One or more processors 102, 202 may process PDUs, SDUs, messages, control information, data or signals containing information (e.g., baseband signals) according to the functions, procedures, proposals and/or methods disclosed herein. generated and provided to one or more transceivers (106, 206).
- One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, the descriptions, functions, procedures, suggestions, methods and/or described in this disclosure.
- PDUs, SDUs, messages, control information, data or information may be acquired according to the operational flowcharts.
- One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor or microcomputer.
- One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof.
- ASICs Application Specific Integrated Circuits
- DSPs Digital Signal Processors
- DSPDs Digital Signal Processing Devices
- PLDs Programmable Logic Devices
- FPGAs Field Programmable Gate Arrays
- the descriptions, functions, procedures, proposals, methods and/or operational flow charts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like.
- Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed in this disclosure may be included in one or more processors (102, 202) or stored in one or more memories (104, 204). It can be driven by the above processors 102 and 202.
- the descriptions, functions, procedures, suggestions, methods and/or operational flow diagrams disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.
- One or more memories 104, 204 may be coupled with one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions and/or instructions.
- One or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
- One or more memories 104, 204 may be located internally and/or external to one or more processors 102, 202. Additionally, one or more memories 104, 204 may be coupled to one or more processors 102, 202 through various technologies, such as wired or wireless connections.
- One or more transceivers 106, 206 may transmit user data, control information, radio signals/channels, etc., as referred to in the methods and/or operational flow charts of this disclosure, to one or more other devices.
- the one or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in the descriptions, functions, procedures, proposals, methods and/or operational flow charts, etc. disclosed in this disclosure from one or more other devices. have.
- one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive wireless signals.
- one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices. Additionally, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled with one or more antennas 108, 208, and one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, as described herein. , procedures, proposals, methods and / or operation flowcharts, etc. can be set to transmit and receive user data, control information, radio signals / channels, etc.
- one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
- One or more transceivers (106, 206) convert the received radio signals/channels from RF band signals in order to process the received user data, control information, radio signals/channels, etc. using one or more processors (102, 202). It can be converted into a baseband signal.
- One or more transceivers 106 and 206 may convert user data, control information, and radio signals/channels processed by one or more processors 102 and 202 from baseband signals to RF band signals.
- one or more of the transceivers 106, 206 may include (analog) oscillators and/or filters.
- one of the STAs 100 and 200 may perform an intended operation of an AP, and the other of the STAs 100 and 200 may perform an intended operation of a non-AP STA.
- the transceivers 106 and 206 of FIG. 1 transmit and receive signals (eg, packets conforming to IEEE 802.11a/b/g/n/ac/ax/be or PPDU (Physical Layer Protocol Data Unit)). action can be performed.
- signals eg, packets conforming to IEEE 802.11a/b/g/n/ac/ax/be or PPDU (Physical Layer Protocol Data Unit)
- PPDU Physical Layer Protocol Data Unit
- an operation in which various STAs generate transmission/reception signals or perform data processing or calculation in advance for transmission/reception signals may be performed by the processors 102 and 202 of FIG. 1 .
- an example of an operation of generating a transmission/reception signal or performing data processing or calculation in advance for the transmission/reception signal is, 1) a field included in the PPDU (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) operation of determining/acquiring/constructing/operating/decoding/encoding, 2) time resource or frequency used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU Operation of determining/constructing/acquiring resources (eg, subcarrier resources), etc.
- SIG signal
- STF short training field
- LTF long training field
- Data etc.
- time resource or frequency used for fields SIG, STF, LTF, Data, etc.
- ACK signal may include operations related to / calculation / decoding / encoding.
- various information eg, information related to fields / subfields / control fields / parameters / power, etc. used by various STAs to determine / acquire / configure / calculate / decode / encode transmission and reception signals may be stored in the memories 104 and 204 of FIG. 1 .
- downlink refers to a link for communication from an AP STA to a non-AP STA, and a downlink PPDU/packet/signal may be transmitted and received through the downlink.
- a transmitter may be part of an AP STA, and a receiver may be part of a non-AP STA.
- Uplink refers to a link for communication from non-AP STAs to AP STAs, and UL PPDUs/packets/signals may be transmitted and received through uplink.
- a transmitter may be part of a non-AP STA, and a receiver may be part of an AP STA.
- FIG. 2 is a diagram illustrating an exemplary structure of a WLAN system to which the present disclosure may be applied.
- the structure of the WLAN system may be composed of a plurality of components.
- a wireless LAN supporting STA mobility transparent to an upper layer may be provided by interaction of a plurality of components.
- a Basic Service Set (BSS) corresponds to a basic building block of a wireless LAN.
- BSS1 and BSS2 there are two BSSs (BSS1 and BSS2), and two STAs are included as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2) by way of example.
- An ellipse representing a BSS in FIG. 2 may also be understood as representing a coverage area in which STAs included in the corresponding BSS maintain communication. This area may be referred to as a Basic Service Area (BSA).
- BSA Basic Service Area
- the most basic type of BSS in a wireless LAN is an independent BSS (Independent BSS, IBSS).
- IBSS may have a minimal form consisting of only two STAs.
- BSS1 composed of only STA1 and STA2 or BSS2 composed of only STA3 and STA4 may respectively correspond to representative examples of IBSS.
- This configuration is possible when STAs can communicate directly without an AP.
- this type of wireless LAN it is not configured in advance, but may be configured when a LAN is required, and this may be referred to as an ad-hoc network.
- IBSS does not include an AP, there is no centralized management entity. That is, in IBSS, STAs are managed in a distributed manner. In the IBSS, all STAs can be made up of mobile STAs, and access to the distributed system (DS) is not allowed, forming a self-contained network.
- DS distributed system
- the STA's membership in the BSS may be dynamically changed by turning on or off the STA, entering or exiting the BSS area, and the like.
- the STA may join the BSS using a synchronization process.
- the STA In order to access all services of the BSS infrastructure, the STA must be associated with the BSS. This association may be dynamically established and may include the use of a Distribution System Service (DSS).
- DSS Distribution System Service
- Direct STA-to-STA distance in a WLAN may be limited by PHY performance. In some cases, this distance limit may be sufficient, but in some cases, communication between STAs at a longer distance may be required.
- a distributed system (DS) may be configured to support extended coverage.
- DS means a structure in which BSSs are interconnected.
- a BSS may exist as an extended form of a network composed of a plurality of BSSs.
- DS is a logical concept and can be specified by the characteristics of Distributed System Media (DSM).
- DSM Distributed System Media
- WM wireless medium
- DSM may be logically separated.
- Each logical medium is used for a different purpose and is used by different components. These media are not limited to being the same, nor are they limited to being different.
- the flexibility of the WLAN structure (DS structure or other network structure) can be explained in that a plurality of media are logically different. That is, the WLAN structure may be implemented in various ways, and the corresponding WLAN structure may be independently specified by the physical characteristics of each embodiment.
- a DS can support a mobile device by providing seamless integration of multiple BSSs and providing logical services needed to address addresses to destinations.
- the DS may further include a component called a portal that serves as a bridge for connection between the wireless LAN and other networks (eg, IEEE 802.X).
- An AP means an entity that enables access to a DS through a WM for coupled non-AP STAs and also has the functionality of an STA. Data movement between the BSS and the DS may be performed through the AP.
- STA2 and STA3 shown in FIG. 2 have the functionality of STAs, and provide a function allowing combined non-AP STAs (STA1 and STA4) to access the DS.
- all APs basically correspond to STAs, all APs are addressable entities.
- the address used by the AP for communication on the WM and the address used by the AP for communication on the DSM are not necessarily the same.
- a BSS composed of an AP and one or more STAs may be referred to as an infrastructure BSS.
- Data transmitted from one of the STA(s) coupled to an AP to an STA address of that AP is always received on an uncontrolled port and may be processed by an IEEE 802.1X port access entity.
- transmission data or frames can be delivered to the DS.
- An extended service set may be set to provide wide coverage in addition to the above-described DS structure.
- ESS refers to a network in which a network having an arbitrary size and complexity is composed of DS and BSS.
- An ESS may correspond to a set of BSSs connected to one DS. However, ESS does not include DS.
- An ESS network is characterized by being seen as an IBSS in the LLC (Logical Link Control) layer. STAs included in the ESS can communicate with each other, and mobile STAs can move from one BSS to another BSS (within the same ESS) transparently to the LLC.
- APs included in one ESS may have the same service set identification (SSID).
- the SSID is distinguished from the BSSID, which is an identifier of the BSS.
- BSSs can partially overlap, which is a form commonly used to provide continuous coverage.
- BSSs may not be physically connected, and logically there is no limit on the distance between BSSs.
- the BSSs may be physically located in the same location, which may be used to provide redundancy.
- one (or more than one) IBSS or ESS networks may physically exist in the same space as one (or more than one) ESS network. This is when an ad-hoc network operates in a location where an ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required in the same location. It may correspond to the form of an ESS network in the like.
- FIG 3 is a diagram for explaining a link setup process to which the present disclosure may be applied.
- the STA In order for the STA to set up a link with respect to the network and transmit/receive data, it first discovers the network, performs authentication, establishes an association, and authenticates for security have to go through
- the link setup process may also be referred to as a session initiation process or a session setup process.
- the processes of discovery, authentication, association, and security setting of the link setup process may be collectively referred to as an association process.
- the STA may perform a network discovery operation.
- the network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access the network, it needs to find a network in which it can participate.
- the STA must identify a compatible network before participating in a wireless network, and the process of identifying a network existing in a specific area is called scanning.
- FIG. 3 exemplarily illustrates a network discovery operation including an active scanning process.
- active scanning an STA performing scanning transmits a probe request frame to discover which APs exist around it while moving channels and waits for a response thereto.
- a responder transmits a probe response frame as a response to the probe request frame to the STA that has transmitted the probe request frame.
- the responder may be an STA that last transmitted a beacon frame in the BSS of the channel being scanned.
- the AP since the AP transmits the beacon frame, the AP becomes a responder.
- the STAs in the IBSS rotate to transmit the beacon frame, so the responder is not constant.
- an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 stores BSS-related information included in the received probe response frame and transmits the probe request frame on the next channel (e.g., channel 2).
- channel e.g., channel 2
- scanning ie, probe request/response transmission/reception on channel 2
- the scanning operation may be performed in a passive scanning manner.
- passive scanning an STA performing scanning waits for a beacon frame while moving channels.
- a beacon frame is one of the management frames defined in IEEE 802.11, and is periodically transmitted to notify the existence of a wireless network and to allow an STA performing scanning to find a wireless network and participate in the wireless network.
- the AP serves to transmit beacon frames periodically, and in the IBSS, STAs within the IBSS rotate to transmit beacon frames.
- an STA performing scanning receives a beacon frame, it stores information about the BSS included in the beacon frame and records beacon frame information in each channel while moving to another channel.
- the STA receiving the beacon frame may store BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same way. Comparing active scanning and passive scanning, active scanning has an advantage of having less delay and less power consumption than passive scanning.
- step S320 After the STA discovers the network, an authentication process may be performed in step S320.
- This authentication process may be referred to as a first authentication process in order to be clearly distinguished from the security setup operation of step S340 to be described later.
- the authentication process includes a process in which the STA transmits an authentication request frame to the AP, and in response, the AP transmits an authentication response frame to the STA.
- An authentication frame used for authentication request/response corresponds to a management frame.
- the authentication frame includes authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), finite cyclic group Group), etc. This corresponds to some examples of information that may be included in the authentication request/response frame, and may be replaced with other information or additional information may be further included.
- the STA may transmit an authentication request frame to the AP.
- the AP may determine whether to allow authentication of the corresponding STA based on information included in the received authentication request frame.
- the AP may provide the result of the authentication process to the STA through an authentication response frame.
- an association process may be performed in step S330.
- the association process includes a process in which the STA transmits an association request frame to the AP, and in response, the AP transmits an association response frame to the STA.
- the association request frame includes information related to various capabilities, beacon listen interval, service set identifier (SSID), supported rates, supported channels, RSN, mobility It may include information about domain, supported operating classes, TIM broadcast request (Traffic Indication Map Broadcast request), interworking service capability, and the like.
- the combined response frame includes information related to various capabilities, status code, association ID (AID), supported rate, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), received signal to RSNI (received signal to Noise Indicator), mobility domain, timeout interval (e.g., association comeback time), overlapping BSS scan parameters, TIM broadcast response, Quality of Service (QoS) map, etc. can do. This corresponds to some examples of information that may be included in the association request/response frame, and may be replaced with other information or additional information may be further included.
- AID association ID
- EDCA enhanced distributed channel access
- RCPI received channel power indicator
- RSNI received signal to Noise Indicator
- timeout interval
- a security setup process may be performed in step S340.
- the security setup process of step S340 may be referred to as an authentication process through RSNA (Robust Security Network Association) request/response, and the authentication process of step S320 is referred to as a first authentication process, and the security setup process of step S340 may also simply be referred to as an authentication process.
- RSNA Robot Security Network Association
- the security setup process of step S340 may include, for example, a process of setting up a private key through 4-way handshaking through an Extensible Authentication Protocol over LAN (EAPOL) frame.
- the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.
- FIG. 4 is a diagram for explaining a backoff process to which the present disclosure may be applied.
- a basic access mechanism of medium access control is a carrier sense multiple access with collision avoidance (CSMA/CA) mechanism.
- the CSMA/CA mechanism is also called Distributed Coordination Function (DCF) of IEEE 802.11 MAC, and basically adopts a "listen before talk" access mechanism.
- DCF Distributed Coordination Function
- the AP and / or STA senses a radio channel or medium for a predetermined time interval (eg, DCF Inter-Frame Space (DIFS)) prior to starting transmission
- a predetermined time interval eg, DCF Inter-Frame Space (DIFS)
- DIFS DCF Inter-Frame Space
- the medium is determined to be in an idle state, frame transmission is started through the corresponding medium, while the medium is occupied or If it is detected that it is busy, the corresponding AP and/or STA does not start its own transmission and waits by setting a delay period (eg, random backoff period) for medium access.
- Frame transmission may be attempted later, and since several STAs are expected to attempt frame transmission after waiting for different periods of time due to the application of the random backoff period, collision may be minimized.
- HCF Hybrid Coordination Function
- HCF is based on the DCF and Point Coordination Function (PCF).
- PCF is a polling-based synchronous access method and refers to a method in which all receiving APs and/or STAs periodically poll to receive data frames.
- HCF has Enhanced Distributed Channel Access (EDCA) and HCF Controlled Channel Access (HCCA).
- EDCA is a contention-based access method for a provider to provide data frames to multiple users, and HCCA uses a non-contention-based channel access method using a polling mechanism.
- the HCF includes a medium access mechanism for improving WLAN QoS (Quality of Service), and can transmit QoS data in both a Contention Period (CP) and a Contention Free Period (CFP). .
- the random backoff count has a pseudo-random integer value and may be determined as one of values ranging from 0 to CW.
- CW is a contention window parameter value.
- the CW parameter is given CWmin as an initial value, but may take a value twice as large in case of transmission failure (for example, when an ACK for the transmitted frame is not received).
- CW parameter value When the CW parameter value reaches CWmax, data transmission may be attempted while maintaining the CWmax value until data transmission is successful, and when data transmission is successful, the CWmin value is reset.
- the STA continuously monitors the medium while counting down the backoff slots according to the determined backoff count value.
- the medium is monitored for occupancy, it stops counting down and waits, and resumes the rest of the countdown when the medium becomes idle.
- STA3 when a packet to be transmitted arrives at the MAC of STA3, STA3 can transmit the frame immediately after confirming that the medium is idle as much as DIFS. The remaining STAs monitor and wait for the medium to be occupied/occupied. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA waits as long as DIFS when the medium is monitored as idle, and then counts down the backoff slot according to the random backoff count value selected by each STA. can be performed. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value.
- STA1 and STA5 temporarily stop counting down and wait while STA2 occupies the medium.
- STA1 and STA5 wait for DIFS and resume the stopped backoff count. That is, frame transmission may be started after counting down the remaining backoff slots for the remaining backoff time. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. While STA2 occupies the medium, data to be transmitted may also occur in STA4.
- the STA4 may perform a countdown according to the random backoff count value selected by the STA4 and start transmitting frames.
- the example of FIG. 4 shows a case where the remaining backoff time of STA5 coincides with the random backoff count value of STA4 by chance. In this case, a collision may occur between STA4 and STA5. When a collision occurs, both STA4 and STA5 do not receive an ACK, so data transmission fails. In this case, STA4 and STA5 may double the CW value, select a random backoff count value, and perform a countdown.
- STA1 waits while the medium is occupied due to transmission of STA4 and STA5, waits for DIFS when the medium becomes idle, and then starts frame transmission after the remaining backoff time has elapsed.
- the data frame is a frame used for transmission of data forwarded to a higher layer, and may be transmitted after a backoff performed after DIFS elapses from when the medium becomes idle.
- the management frame is a frame used for exchange of management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS such as DIFS or Point Coordination Function IFS (PIFS). Beacon, association request/response, re-association request/response, probe request/response, authentication request/response as subtype frames of management frame. request/response), etc.
- a control frame is a frame used to control access to a medium.
- control frame is not a response frame of the previous frame, it is transmitted after backoff performed after DIFS elapses, and if it is a response frame of the previous frame, it is transmitted without performing backoff after SIFS (short IFS) elapses.
- the type and subtype of the frame may be identified by a type field and a subtype field in a frame control (FC) field.
- QoS (Quality of Service) STA is AIFS (arbitration IFS) for the access category (AC) to which the frame belongs, that is, AIFS[i] (where i is a value determined by AC) Backoff performed after elapsed After that, the frame can be transmitted.
- AIFS[i] may be used for a data frame, a management frame, or a control frame other than a response frame.
- FIG. 5 is a diagram for explaining a frame transmission operation based on CSMA/CA to which the present disclosure may be applied.
- the CSMA/CA mechanism includes virtual carrier sensing in addition to physical carrier sensing in which an STA directly senses a medium.
- Virtual carrier sensing is intended to compensate for problems that may occur in medium access, such as a hidden node problem.
- the STA's MAC may use a Network Allocation Vector (NAV).
- NAV Network Allocation Vector
- the STA's MAC may use a Network Allocation Vector (NAV).
- NAV Network Allocation Vector
- NAV is a value that indicates to other STAs the remaining time until the medium is available for use by an STA currently using or having the right to use the medium.
- the value set as the NAV corresponds to a period in which the medium is scheduled to be used by the STA transmitting the frame, and the STA receiving the NAV value is prohibited from accessing the medium during the corresponding period.
- the NAV may be set based on the value of the “duration” field of the MAC header of the frame.
- STA1 intends to transmit data to STA2, and STA3 is in a position capable of overhearing some or all of frames transmitted and received between STA1 and STA2.
- a mechanism using RTS/CTS frames may be applied.
- STA1 while transmission of STA1 is being performed, as a result of carrier sensing of STA3, it may be determined that the medium is in an idle state. That is, STA1 may correspond to a hidden node to STA3.
- STA2 it may be determined that the carrier sensing result medium of STA3 is in an idle state while transmission of STA2 is being performed. That is, STA2 may correspond to a hidden node to STA3.
- STA1 may determine whether a channel is being used through carrier sensing. In terms of physical carrier sensing, STA1 may determine a channel occupation idle state based on an energy level or signal correlation detected in a channel. In addition, in terms of virtual carrier sensing, STA1 may use a network allocation vector (NAV) timer to determine a channel occupancy state.
- NAV network allocation vector
- STA1 may transmit an RTS frame to STA2 after performing a backoff when the channel is in an idle state during DIFS.
- STA2 may transmit a CTS frame as a response to the RTS frame to STA1 after SIFS.
- STA3 uses duration information included in the RTS frame to transmit frames continuously transmitted thereafter
- a NAV timer for (eg, SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame) may be set.
- STA3 uses duration information included in the CTS frame to transmit frames that are subsequently transmitted continuously
- a NAV timer for a period (eg, SIFS + data frame + SIFS + ACK frame) may be set.
- STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set the NAV accordingly.
- the STA3 may update the NAV timer using duration information included in the new frame. STA3 does not attempt channel access until the NAV timer expires.
- STA1 When STA1 receives the CTS frame from STA2, it may transmit a data frame to STA2 after SIFS from the time when reception of the CTS frame is completed. When the STA2 successfully receives the data frame, it may transmit an ACK frame as a response to the data frame to the STA1 after SIFS.
- STA3 may determine whether the channel is being used through carrier sensing when the NAV timer expires. When the STA3 determines that the channel is not used by other terminals during DIFS after expiration of the NAV timer, the STA3 may attempt channel access after a contention window (CW) according to a random backoff has passed.
- CW contention window
- FIG. 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.
- the PHY layer may prepare an MPDU (MAC PDU) to be transmitted. For example, when a command requesting transmission start of the PHY layer is received from the MAC layer, the PHY layer switches to the transmission mode and configures information (eg, data) provided from the MAC layer in the form of a frame and transmits it. . In addition, when the PHY layer detects a valid preamble of the received frame, it monitors the header of the preamble and sends a command notifying the start of reception of the PHY layer to the MAC layer.
- MPDU MPDU
- PPDU PHY layer protocol data unit
- a basic PPDU frame may include a Short Training Field (STF), a Long Training Field (LTF), a SIGNAL (SIG) field, and a Data field.
- the most basic (eg, non-high throughput (HT)) PPDU frame format may consist of only legacy-STF (L-STF), legacy-LTF (L-LTF), SIG field, and data field.
- L-STF legacy-STF
- L-LTF legacy-LTF
- SIG field legacy-LTF
- data field e.g, legacy-STF
- L-LTF legacy-LTF
- data field e.g., HT-mixed format PPDU, HT-greenfield format PPDU, VHT (Very High Throughput) PPDU, etc.
- an additional (or different type) STF, LTF, and SIG fields may be included (this will be described later with reference to FIG. 7).
- the STF is a signal for signal detection, automatic gain control (AGC), diversity selection, precise time synchronization, and the like
- the LTF is a signal for channel estimation and frequency error estimation.
- the STF and LTF may be referred to as signals for synchronization and channel estimation of the OFDM physical layer.
- the SIG field may include a RATE field and a LENGTH field.
- the RATE field may include information on modulation and coding rates of data.
- the LENGTH field may include information about the length of data. Additionally, the SIG field may include a parity bit, a SIG TAIL bit, and the like.
- the data field may include a SERVICE field, a physical layer service data unit (PSDU), and a PPDU TAIL bit, and may also include padding bits if necessary.
- Some bits of the SERVICE field may be used for synchronization of the descrambler at the receiving end.
- the PSDU corresponds to the MAC PDU defined in the MAC layer, and may include data generated/used in the upper layer.
- the PPDU TAIL bit can be used to return the encoder to a 0 state.
- Padding bits may be used to adjust the length of a data field in a predetermined unit.
- a MAC PDU is defined according to various MAC frame formats, and a basic MAC frame is composed of a MAC header, a frame body, and a Frame Check Sequence (FCS).
- the MAC frame may be composed of MAC PDUs and transmitted/received through the PSDU of the data part of the PPDU frame format.
- the MAC header includes a frame control field, a duration/ID field, an address field, and the like.
- the frame control field may include control information required for frame transmission/reception.
- the duration/ID field may be set to a time for transmitting a corresponding frame or the like.
- a null-data packet (NDP) frame format means a frame format that does not include a data packet. That is, the NDP frame refers to a frame format that includes a physical layer convergence procedure (PLCP) header part (ie, STF, LTF, and SIG fields) in a general PPDU frame format and does not include the remaining parts (ie, data field). do.
- PLCP physical layer convergence procedure
- An NDP frame may also be referred to as a short frame format.
- FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure may be applied.
- the basic PPDU format (IEEE 802.11a/g) includes L-LTF, L-STF, L-SIG and Data fields.
- the basic PPDU format may also be referred to as a non-HT PPDU format.
- the HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields to the basic PPDU format.
- the HT PPDU format shown in FIG. 7 may be referred to as an HT-mixed format.
- an HT-greenfield format PPDU may be defined, which does not include L-STF, L-LTF, and L-SIG, but includes HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, Data Corresponds to a format composed of fields (not shown).
- VHT PPDU format (IEEE 802.11ac) includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in addition to the basic PPDU format.
- HE PPDU format IEEE 802.11ax
- R-SIG Repeated L-SIG
- HE-SIG-A HE-SIG-B
- HE-STF HE-LTF(s)
- PE Packet Extension
- Some fields may be excluded or their length may vary according to detailed examples of the HE PPDU format.
- the HE-SIG-B field is included in the HE PPDU format for multi-user (MU), and the HE-SIG-B is not included in the HE PPDU format for single user (SU).
- the HE trigger-based (TB) PPDU format does not include HE-SIG-B, and the length of the HE-STF field may vary to 8us.
- the HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us.
- 8 to 10 are diagrams for explaining examples of resource units of a WLAN system to which the present disclosure can be applied.
- An RU may include a plurality of subcarriers (or tones).
- the RU may be used when transmitting signals to multiple STAs based on the OFDMA technique.
- an RU may be defined even when a signal is transmitted to one STA.
- RU may be used for STF, LTF, data fields, etc. of the PPDU.
- RUs corresponding to different numbers of tones are used to select some fields of a 20 MHz, 40 MHz, or 80 MHz X-PPDU (X is HE, EHT, etc.) can be configured.
- resources may be allocated in RU units shown for the X-STF, X-LTF, and Data fields.
- FIG. 8 is a diagram illustrating an exemplary arrangement of resource units (RUs) used on a 20 MHz band.
- 26-units ie, units corresponding to 26 tones
- 6 tones may be used as a guard band in the leftmost band of the 20 MHz band
- 5 tones may be used as a guard band in the rightmost band of the 20 MHz band.
- 7 DC tones are inserted in the center band, that is, the DC band
- 26-units corresponding to each of the 13 tones may exist on the left and right sides of the DC band.
- 26-unit, 52-unit, and 106-unit may be allocated to other bands. Each unit may be allocated for either a STA or a user.
- the RU arrangement of FIG. 8 is utilized not only in a situation for multiple users (MU) but also in a situation for a single user (SU), and in this case, as shown at the bottom of FIG. 8, using one 242-unit it is possible In this case, three DC tones may be inserted.
- RUs of various sizes that is, 26-RU, 52-RU, 106-RU, and 242-RU are exemplified, but the specific size of these RUs may be reduced or expanded. Therefore, in the present disclosure, the specific size of each RU (ie, the number of corresponding tones) is exemplary and not restrictive. In addition, within a predetermined bandwidth (eg, 20, 40, 80, 160, 320 MHz, ...) in the present disclosure, the number of RUs may vary according to the size of the RU. In the examples of FIGS. 9 and/or 10 to be described below, the fact that the size and/or number of RUs can be changed is the same as the example of FIG. 8 .
- FIG. 9 is a diagram illustrating an exemplary arrangement of resource units (RUs) used on a 40 MHz band.
- 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, and the like may also be used in the example of FIG.
- 5 DC tones may be inserted at the center frequency, 12 tones are used as a guard band in the leftmost band of the 40MHz band, and 11 tones are used in the rightmost band of the 40MHz band. This can be used as a guard band.
- a 484-RU when used for a single user, a 484-RU may be used.
- FIG. 10 is a diagram illustrating an exemplary arrangement of resource units (RUs) used on an 80 MHz band.
- RUs resource units
- RUs of various sizes are used, in the example of FIG. 10, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. can be used. have.
- RU arrangements of HE PPDUs and EHT PPDUs may be different, and the example of FIG. 10 shows an example of RU arrangements for 80 MHz EHT PPDUs.
- 12 tones are used as the guard band in the leftmost band of the 80 MHz band and 11 tones are used as the guard band in the rightmost band of the 80 MHz band.
- EHT PPDU EHT PPDU.
- the EHT PPDU Unlike the HE PPDU in which 7 DC tones are inserted into the DC band and there is one 26-RU corresponding to each of the 13 tones on the left and right sides of the DC band, in the EHT PPDU, 23 DC tones are inserted into the DC band, There is one 26-RU on the left and right side of the DC band. Unlike the HE PPDU where one null subcarrier exists between 242-RUs rather than the center band, there are five null subcarriers in the EHT PPDU. In the HE PPDU, one 484-RU does not include null subcarriers, but in the EHT PPDU, one 484-RU includes 5 null subcarriers.
- 996-RU when used for a single user, 996-RU may be used, and in this case, the insertion of 5 DC tones is common to HE PPDU and EHT PPDU.
- EHT PPDUs of 160 MHz or higher may be set to a plurality of 80 MHz subblocks in FIG. 10 .
- the RU arrangement for each 80 MHz subblock may be the same as that of the 80 MHz EHT PPDU of FIG. 10 . If the 80 MHz subblock of the 160 MHz or 320 MHz EHT PPDU is not punctured and the entire 80 MHz subblock is used as part of RU or Multiple RU (MRU), the 80 MHz subblock may use 996-RU of FIG. 10 .
- MRU Multiple RU
- the MRU corresponds to a group of subcarriers (or tones) composed of a plurality of RUs
- the plurality of RUs constituting the MRU may be RUs of the same size or RUs of different sizes.
- single MRUs are: 52+26-ton, 106+26-ton, 484+242-ton, 996+484-ton, 996+484+242-ton, 2 ⁇ 996+484-ton, 3 ⁇ 996-ton, or 3 ⁇ 996+484-tons.
- the plurality of RUs constituting one MRU may correspond to small-sized (eg, 26, 52, or 106) RUs or large-sized (eg, 242, 484, or 996) RUs.
- one MRU including a small size RU and a large size RU may not be set/defined.
- a plurality of RUs constituting one MRU may or may not be consecutive in the frequency domain.
- the 80 MHz subblock may use RU arrangements other than the 996-tone RU.
- the RU of the present disclosure may be used for uplink (UL) and/or downlink (DL) communication.
- an STA eg, an AP
- a trigger may include trigger information (eg, a trigger frame or a triggered response scheduling (TRS) ), a first RU (eg, 26/52/106/242-RU, etc.) is allocated to the first STA, and a second RU (eg, 26/52/106/242-RU, etc.) is allocated to the second STA.
- RU, etc. can be allocated.
- the first STA may transmit a first trigger-based (TB) PPDU based on the first RU
- the second STA may transmit a second TB PPDU based on the second RU.
- the first/second TB PPDUs may be transmitted to the AP in the same time interval.
- an STA transmitting the DL MU PPDU sends a first RU (eg, 26/52/106/242-RU, etc.) to the first STA.
- a second RU eg, 26/52/106/242-RU, etc.
- the transmitting STA may transmit HE-STF, HE-LTF, and Data fields for the first STA through the first RU within one MU PPDU, and through the second RU HE-STF, HE-LTF, and Data fields for 2 STAs may be transmitted.
- Information on the arrangement of RUs may be signaled through HE-SIG-B in HE PPDU format.
- FIG. 11 shows an exemplary structure of a HE-SIG-B field.
- the HE-SIG-B field may include a common field and a user-specific field. If HE-SIG-B compression is applied (eg, full-bandwidth MU-MIMO transmission), the common field may not be included in HE-SIG-B, and HE-SIG-B content A content channel may contain only user-specific fields. If HE-SIG-B compression is not applied, the common field may be included in HE-SIG-B.
- the common field may include information on RU allocation (eg, RU assignment, RUs allocated for MU-MIMO, the number of MU-MIMO users (STAs), etc.) .
- RU allocation eg, RU assignment, RUs allocated for MU-MIMO, the number of MU-MIMO users (STAs), etc.
- the common field may include N*8 RU allocation subfields.
- One 8-bit RU allocation subfield may indicate the size (26, 52, 106, etc.) and frequency location (or RU index) of RUs included in the 20 MHz band.
- the value of the 8-bit RU allocation subfield is 00000000
- nine 26-RUs are sequentially arranged from the leftmost to the rightmost in the example of FIG.
- the value is 00000010
- five 26-RUs, one 52-RU, and two 26-RUs are arranged in order from leftmost to rightmost.
- the value of the 8-bit RU allocation subfield is 01000y 2 y 1 y 0 , it indicates that one 106-RU and five 26-RUs are sequentially arranged from the leftmost to the rightmost in the example of FIG. 8 can In this case, multiple users/STAs may be allocated to the 106-RU in the MU-MIMO scheme. Specifically, up to 8 users/STAs can be allocated to the 106-RU, and the number of users/STAs allocated to the 106-RU is determined based on 3-bit information (ie, y 2 y 1 y 0 ). For example, when 3-bit information (y 2 y 1 y 0 ) corresponds to a decimal value N, the number of users/STAs allocated to the 106-RU may be N+1.
- one user/STA may be allocated to each of a plurality of RUs, and different users/STAs may be allocated to different RUs.
- a predetermined size e.g, 106, 242, 484, 996-tones, .
- a plurality of users/STAs may be allocated to one RU, and for the plurality of users/STAs, MU -MIMO scheme can be applied.
- the set of user-specific fields includes information on how all users (STAs) of the PPDU decode their payloads.
- User-specific fields may include zero or more user block fields.
- the non-final user block field includes two user fields (ie, information to be used for decoding in two STAs).
- the final user block field contains one or two user fields.
- the number of user fields may be indicated by the RU allocation subfield of HE-SIG-B, the number of symbols of HE-SIG-B, or the MU-MIMO user field of HE-SIG-A have.
- User-specific fields may be encoded separately from or independently of common fields.
- FIG. 12 is a diagram for explaining a MU-MIMO method in which a plurality of users/STAs are allocated to one RU.
- HE-SIG-B may include 8 user fields (ie, 4 user block fields). Eight user fields may be assigned to an RU as shown in FIG. 12 .
- User fields can be constructed based on two formats.
- the user field for MU-MIMO assignments may be in a first format
- the user field for non-MU-MIMO assignments may be in a second format.
- user fields 1 to 3 may be based on a first format
- user fields 4 to 8 may be based on a second format.
- the first format and the second format may include bit information of the same length (eg, 21 bits).
- the user field of the first format may be configured as follows. For example, among all 21 bits of one user field, B0-B10 includes identification information (e.g., STA-ID, AID, partial AID, etc.) of the corresponding user, and B11-14 contains information about the corresponding user. It includes spatial configuration information such as the number of spatial streams, B15-B18 includes Modulation and Coding Scheme (MCS) information applied to the Data field of the corresponding PPDU, and B19 is a reserved field. defined, and B20 may include information on a coding type (eg, binary convolutional coding (BCC) or low-density parity check (LDPC)) applied to the Data field of the corresponding PPDU.
- BCC binary convolutional coding
- LDPC low-density parity check
- the user field of the second format (ie format for non-MU-MIMO assignment) may be configured as follows.
- B0-B10 includes identification information (e.g., STA-ID, AID, partial AID, etc.) of the user, and B11-13 applies to the corresponding RU.
- B14 includes information indicating the number of spatial streams to be used (NSTS), B14 includes information indicating whether beamforming is performed (or whether a beamforming steering matrix is applied), and B15-B18 include MCS (Modulation and coding scheme) information, B19 includes information indicating whether dual carrier modulation (DCM) is applied, and B20 includes coding type (eg, BCC or LDPC) information applied to the Data field of the PPDU.
- DCM dual carrier modulation
- B20 includes coding type (eg, BCC or LDPC) information applied to the Data field of the PPDU.
- coding type eg, BCC or LDPC
- MCS MCS information
- MCS index MCS field, etc. used in this disclosure may be indicated by a specific index value.
- MCS information may be displayed as index 0 to index 11.
- MCS information includes information on constellation modulation type (eg, BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.), and coding rate (eg, 1/2, 2/ 3, 3/4, 5/6, etc.)
- coding rate eg, 1/2, 2/ 3, 3/4, 5/6, etc.
- Information on a channel coding type eg, BCC or LDPC
- FIG. 13 shows an example of a PPDU format to which the present disclosure can be applied.
- the PPDU of FIG. 13 may be called various names such as EHT PPDU, transmitted PPDU, received PPDU, first type or Nth type PPDU.
- the PPDU or EHT PPDU of the present disclosure may be called various names such as a transmission PPDU, a reception PPDU, a first type or an Nth type PPDU.
- the EHT PPU may be used in an EHT system and/or a new wireless LAN system in which the EHT system is improved.
- the EHT MU PPDU of FIG. 13 corresponds to a PPDU carrying one or more data (or PSDUs) for one or more users. That is, the EHT MU PPDU can be used for both SU transmission and MU transmission.
- the EHT MU PPDU may correspond to a PPDU for one receiving STA or a plurality of receiving STAs.
- the EHT-SIG is omitted compared to the EHT MU PPDU.
- the STA may perform UL transmission based on the EHT TB PPDU format.
- L-STF to EHT-LTF correspond to a preamble or a physical preamble, and can be generated/transmitted/received/acquired/decoded in the physical layer.
- Subcarrier frequency spacing of L-STF, L-LTF, L-SIG, RL-SIG, Universal SIGNAL (U-SIG), EHT-SIG fields (these are referred to as pre-EHT modulated fields) (subcarrier frequency spacing) may be set to 312.5 kHz.
- the subcarrier frequency interval of the EHT-STF, EHT-LTF, Data, and PE fields (these are referred to as EHT modulated fields) may be set to 78.125 kHz.
- the tone/subcarrier index of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields is displayed in units of 312.5 kHz, and the EHT-STF, EHT-LTF, Data,
- the tone/subcarrier index of the PE field may be displayed in units of 78.125 kHz.
- the L-LTF and L-STF of FIG. 13 may have the same configuration as the corresponding fields of the PPDU described in FIGS. 6 to 7.
- the L-SIG field of FIG. 13 consists of 24 bits and can be used to communicate rate and length information.
- the L-SIG field includes a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit tail (Tail) field may be included.
- the 12-bit Length field may include information about the length or time duration of the PPDU.
- the value of the 12-bit Length field may be determined based on the type of PPDU. For example, for a non-HT, HT, VHT, or EHT PPDU, the value of the Length field may be determined as a multiple of 3.
- the value of the Length field may be determined as a multiple of 3 + 1 or a multiple of 3 + 2.
- the transmitting STA may apply BCC encoding based on a coding rate of 1/2 to 24-bit information of the L-SIG field. Thereafter, the transmitting STA may obtain 48-bit BCC coded bits. BPSK modulation may be applied to 48-bit coded bits to generate 48 BPSK symbols. The transmitting STA transmits 48 BPSK symbols, pilot subcarriers (eg, ⁇ subcarrier index -21, -7, +7, +21 ⁇ ) and DC subcarriers (eg, ⁇ subcarrier index 0 ⁇ ) It can be mapped to any location except for .
- pilot subcarriers eg, ⁇ subcarrier index -21, -7, +7, +21 ⁇
- DC subcarriers eg, ⁇ subcarrier index 0 ⁇
- the transmitting STA may additionally map the signals of ⁇ -1, -1, -1, 1 ⁇ to the subcarrier index ⁇ -28, -27, +27, +28 ⁇ .
- the above signal may be used for channel estimation in the frequency domain corresponding to ⁇ -28, -27, +27, +28 ⁇ .
- the transmitting STA may generate the same RL-SIG as the L-SIG.
- BPSK modulation is applied.
- the receiving STA may know that the received PPDU is a HE PPDU or an EHT PPDU based on the existence of the RL-SIG.
- U-SIG Universal SIG
- the U-SIG may be called various names such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, and a first (type) control signal.
- the U-SIG may include N bits of information and may include information for identifying the type of EHT PPDU.
- U-SIG may be configured based on two symbols (eg, two consecutive OFDM symbols).
- Each symbol (eg, OFDM symbol) for U-SIG may have a duration of 4us, and the U-SIG may have a duration of 8us in total.
- Each symbol of U-SIG can be used to transmit 26 bits of information.
- each symbol of U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.
- a bit information (eg, 52 uncoded bits) may be transmitted through the U-SIG (or U-SIG field), and the first symbol of the U-SIG (eg, U-SIG-1) transmits the first X bit information (eg, 26 un-coded bits) of the total A bit information, and transmits the second symbol of U-SIG (eg, U-SIG -2) may transmit the remaining Y-bit information (eg, 26 un-coded bits) of the total A-bit information.
- the transmitting STA may obtain 26 un-coded bits included in each U-SIG symbol.
- the transmitting STA may generate 52 BPSK symbols allocated to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits.
- One U-SIG symbol may be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, except for DC index 0.
- the 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) excluding pilot tones -21, -7, +7, and +21 tones.
- the A-bit information (e.g., 52 un-coded bits) transmitted by U-SIG includes a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit field). ) may be included.
- the CRC field and the tail field may be transmitted through the second symbol of U-SIG.
- the CRC field may be generated based on 26 bits allocated to the first symbol of U-SIG and 16 bits remaining except for the CRC/tail field in the second symbol, and may be generated based on a conventional CRC calculation algorithm.
- the tail field may be used to terminate the trellis of the convolution decoder, and may be set to 0, for example.
- a bit information (eg, 52 un-coded bits) transmitted by U-SIG may be divided into version-independent bits and version-independent bits.
- the size of version-independent bits can be fixed or variable.
- version-independent bits may be allocated only to the first symbol of the U-SIG, or version-independent bits may be allocated to both the first symbol and the second symbol of the U-SIG.
- version-independent bits and version-dependent bits may be called various names such as a first control bit and a second control bit.
- the version-independent bits of the U-SIG may include a 3-bit physical layer version identifier (PHY version identifier).
- the 3-bit PHY version identifier may include information related to the PHY version of the transmitted/received PPDU.
- the first value of the 3-bit PHY version identifier may indicate that the transmission/reception PPDU is an EHT PPDU.
- the transmitting STA may set the 3-bit PHY version identifier to a first value.
- the receiving STA may determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value.
- the version-independent bits of the U-SIG may include a 1-bit UL/DL flag field.
- a first value of the 1-bit UL/DL flag field is related to UL communication, and a second value of the UL/DL flag field is related to DL communication.
- the version-independent bits of the U-SIG may include information about the length of a transmission opportunity (TXOP) and information about a BSS color ID.
- TXOP transmission opportunity
- EHT PPDUs are classified into various types (e.g., EHT PPDU related to SU mode, EHT PPDU related to MU mode, EHT PPDU related to TB mode, EHT PPDU related to extended range transmission, etc.)
- information on the type of EHT PPDU may be included in version-dependent bits of the U-SIG.
- U-SIG includes 1) a bandwidth field including information about bandwidth, 2) a field including information about MCS scheme applied to EHT-SIG, 3) whether DCM scheme is applied to EHT-SIG
- Preamble puncturing may be applied to the PPDU of FIG. 13 .
- Preamble puncturing means applying puncturing to a partial band (eg, a secondary 20 MHz band) among all bands of the PPDU. For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band of the 80 MHz band and transmits the PPDU only through the primary 20 MHz band and the secondary 40 MHz band. have.
- a preamble puncturing pattern may be set in advance. For example, when the first puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band within an 80 MHz band. For example, when the second puncturing pattern is applied, puncturing may be applied only to one of two secondary 20 MHz bands included in a secondary 40 MHz band within an 80 MHz band. For example, when the third puncturing pattern is applied, puncturing may be applied only to a secondary 20 MHz band included in a primary 80 MHz band within a 160 MHz band (or 80+80 MHz band).
- the primary 40 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band) is present and does not belong to the primary 40 MHz band. Puncture can be applied to at least one 20 MHz channel that does not
- Information on preamble puncturing applied to the PPDU may be included in the U-SIG and/or the EHT-SIG.
- the first field of the U-SIG includes information about the contiguous bandwidth of the PPDU
- the second field of the U-SIG includes information about preamble puncturing applied to the PPDU. have.
- U-SIG and EHT-SIG may include information about preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG includes information about the 160 MHz bandwidth, and the second field of the first U-SIG includes information about preamble puncturing applied to the first 80 MHz band (ie, preamble information on a puncturing pattern).
- the first field of the second U-SIG includes information about the 160 MHz bandwidth
- the second field of the second U-SIG includes information about preamble puncturing applied to the second 80 MHz band (ie, preamble fung information about the processing pattern).
- the EHT-SIG following the first U-SIG may include information on preamble puncturing applied to the second 80 MHz band (ie, information on the preamble puncturing pattern), and
- the EHT-SIG may include information on preamble puncturing applied to the first 80 MHz band (ie, information on a preamble puncturing pattern).
- the U-SIG and EHT-SIG may include information about preamble puncturing based on the method below.
- the U-SIG may include information on preamble puncturing for all bands (ie, information on a preamble puncturing pattern). That is, EHT-SIG does not include information on preamble puncturing, and only U-SIG may include information on preamble puncturing (ie, information on preamble puncturing patterns).
- U-SIG may be configured in units of 20 MHz. For example, if an 80 MHz PPDU is configured, the U-SIG may be duplicated. That is, the same 4 U-SIGs may be included in the 80 MHz PPDU. PPDUs exceeding 80 MHz bandwidth may include different U-SIGs.
- the EHT-SIG of FIG. 13 may include control information for the receiving STA.
- EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4us.
- Information on the number of symbols used for EHT-SIG may be included in U-SIG.
- EHT-SIG may include technical features of HE-SIG-B described with reference to FIGS. 11 and 12 .
- EHT-SIG like the example of FIG. 8, may include a common field and a user-specific field. Common fields of EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.
- the common field of EHT-SIG and the user-specific field of EHT-SIG may be individually coded.
- One user block field included in the user-specific field contains information for two user fields, but the last user block field included in the user-specific field contains information for one or two user fields. May contain fields. That is, one user block field of the EHT-SIG may include up to two user fields.
- each user field may be related to MU-MIMO allocation or non-MU-MIMO allocation.
- the common field of EHT-SIG may include a CRC bit and a Tail bit
- the length of the CRC bit may be determined as 4 bits
- the length of the Tail bit may be determined as 6 bits and set to 000000.
- the common field of EHT-SIG may include RU allocation information.
- RU allocation information may mean information about the location of an RU to which a plurality of users (ie, a plurality of receiving STAs) are allocated.
- RU allocation information may be configured in units of 8 bits (or N bits).
- a mode in which the common field of EHT-SIG is omitted may be supported.
- a mode in which the common field of the EHT-SIG is omitted may be called a compressed mode.
- a plurality of users (ie, a plurality of receiving STAs) of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) based on non-OFDMA. That is, a plurality of users of the EHT PPDU can decode a PPDU (eg, a data field of the PPDU) received through the same frequency band.
- multiple users of the EHT PPDU can decode the PPDU (eg, the data field of the PPDU) based on OFDMA. That is, a plurality of users of the EHT PPDU may receive the PPDU (eg, the data field of the PPDU) through different frequency bands.
- EHT-SIG can be configured based on various MCS techniques. As described above, information related to the MCS scheme applied to the EHT-SIG may be included in the U-SIG. EHT-SIG may be configured based on the DCM technique. For example, among N data tones (eg, 52 data tones) allocated for EHT-SIG, the first modulation scheme is applied to half of the continuous tones, and the second modulation scheme is applied to the remaining half of the tones. techniques can be applied.
- N data tones eg, 52 data tones
- the transmitting STA modulates specific control information into a first symbol based on a first modulation scheme and allocates to consecutive half tones, modulates the same control information into a second symbol based on a second modulation scheme, and modulates the remaining consecutive can be assigned to half a ton.
- information related to whether the DCM technique is applied to the EHT-SIG eg, a 1-bit field
- the EHT-STF of FIG. 13 can be used to improve automatic gain control (AGC) estimation in a MIMO environment or an OFDMA environment.
- the EHT-LTF of FIG. 13 may be used to estimate a channel in a MIMO environment or an OFDMA environment.
- Information about the type of STF and/or LTF may be included in the U-SIG field and/or the EHT-SIG field of FIG. 13 .
- GI guard interval
- the PPDU (ie, EHT PPDU) of FIG. 13 may be configured based on examples of RU arrangements of FIGS. 8 to 10 .
- an EHT PPDU transmitted on a 20 MHz band may be configured based on the RU of FIG. 8 . That is, the location of the EHT-STF, EHT-LTF, and RU of the data field included in the EHT PPDU may be determined as shown in FIG. 8 .
- An EHT PPDU transmitted on a 40 MHz band, that is, a 40 MHz EHT PPDU may be configured based on the RU of FIG. 9 . That is, the location of the EHT-STF, EHT-LTF, and RU of the data field included in the EHT PPDU may be determined as shown in FIG. 9 .
- the EHT PPDU transmitted on the 80 MHz band may be configured based on the RU of FIG. 10 . That is, the location of the EHT-STF, EHT-LTF, and RU of the data field included in the EHT PPDU may be determined as shown in FIG. 10 .
- the tone-plan for 80 MHz in FIG. 10 may correspond to two repetitions of the tone-plan for 40 MHz in FIG.
- the tone-plan for 160/240/320 MHz may be configured in the form of repeating the pattern of FIG. 9 or 10 several times.
- the PPDU of FIG. 13 can be identified as an EHT PPDU based on the following method.
- the receiving STA may determine the type of the received PPDU as the EHT PPDU based on the following items. For example, 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) RL-SIG in which the L-SIG of the received PPDU is repeated is detected, and 3) the L-LTF signal of the received PPDU is detected. When a result of applying a modulo 3 operation to the value of the Length field of the SIG (ie, a remainder after dividing by 3) is detected as 0, the received PPDU may be determined as an EHT PPDU.
- the receiving STA may determine the type of the EHT PPDU based on bit information included in symbols subsequent to the RL-SIG of FIG. 13 .
- the receiving STA is 1) the first symbol after the L-LTF signal that is BSPK, 2) the RL-SIG that is consecutive to the L-SIG field and the same as the L-SIG, and 3) the result of applying modulo 3 is 0
- the received PPDU may be determined as an EHT PPDU.
- the receiving STA may determine the type of the received PPDU as the HE PPDU based on the following. For example, 1) the first symbol after the L-LTF signal is BPSK, 2) RL-SIG in which L-SIG is repeated is detected, and 3) the result of applying modulo 3 to the length value of L-SIG is If 1 or 2 is detected, the received PPDU may be determined as a HE PPDU.
- the receiving STA may determine the type of the received PPDU as non-HT, HT, and VHT PPDU based on the following items. For example, if 1) the first symbol after the L-LTF signal is BPSK and 2) RL-SIG in which L-SIG is repeated is not detected, the received PPDU is determined to be non-HT, HT, and VHT PPDU. can In addition, even if the receiving STA detects repetition of the RL-SIG, if the result of applying modulo 3 to the Length value of the L-SIG is detected as 0, the received PPDU can be determined as non-HT, HT, and VHT PPDUs have.
- the PPDU of FIG. 13 can be used to transmit and receive various types of frames.
- the PPDU of FIG. 13 may be used for (simultaneous) transmission and reception of one or more of a control frame, a management frame, or a data frame.
- target wake time TWT
- TWT defines a Service Period (SP) between an AP and a non-AP STA and shares information about the SP to reduce media contention, thereby improving the energy efficiency of non-AP STAs. It is PS (Power Saving) technology.
- An STA that performs Request/Suggest/Demand in the TWT setup step may be referred to as a TWT Requesting STA.
- an AP that responds to the request such as accept/reject, may be referred to as a TWT responding STA.
- the setup step may include a process of determining/defining a TWT request from an STA to an AP, a type of a TWT operation to be performed, and a frame type to be transmitted and received. TWT operation can be divided into individual TWT and broadcast TWT.
- FIG. 14 is a diagram for explaining an example of an individual TWT operation to which the present disclosure can be applied.
- AP and STA1 may form a trigger-enabled TWT agreement through a TWT request frame and a TWT response frame.
- the method used by the STA1 is a solicited TWT method.
- STA2 performing the unsolicited TWT method may receive information on a trigger-enabled TWT agreement setting from the AP through an unsolicited TWT response.
- STA2 may calculate the next TWT by adding a specific number from the current TWT value.
- the AP may transmit a trigger frame to STAs.
- the trigger frame may inform STAs that the AP has buffered data.
- STA1 may inform the AP of its awake state by transmitting a PS-Poll frame.
- STA2 may inform the AP of its activated state by transmitting a QoS Null frame.
- the data frames transmitted by STA1 and STA2 may be TB PPDU format frames.
- the AP may transmit a DL MU PPDU to activated STAs.
- STA1 and STA2 may switch to a doze state.
- 15 is a diagram for explaining an example of a broadcast TWT operation to which the present disclosure can be applied.
- a non-AP STA transmits and receives a TWT request/response frame with an AP (or TWT scheduled STA) to obtain information on target beacon transmission time (TBTT) and listen interval, etc. It's a TWT way of doing it.
- TBTT target beacon transmission time
- the AP may define a frame including TWT scheduling information through a beacon frame.
- STA1 performs a requested TWT operation
- STA2 performs an unsolicited TWT operation.
- the AP may transmit the DL MU PPDU after checking the awake state of the STAs through the trigger transmitted by the AP. This may be the same as the process of individual TWT.
- a trigger-enabled TWT SP including a beacon frame may be repeated several times at regular intervals.
- Transmission of TWT information may be performed through a TWT information frame and a TWT information element.
- 16 is a diagram for explaining an example of a TWT information element format.
- the TWT information frame is transmitted by an STA to request or deliver information on a TWT agreement, and is transmitted by one of the STAs of an existing TWT agreement.
- the action frame of the TWT Information frame includes a TWT information field.
- the TWT Information field is a 3-bit TWT flow identifier subfield, a 1-bit response requested subfield, a 1-bit next TWT request subfield, a 2-bit next TWT It may include a next TWT subfield size subfield, a 1-bit all TWT (all TWT) subfield, and a 0/32/48/64-bit next TWT (next TWT) subfield.
- the size of the TWT Information field is variable according to the size of the next TWT field.
- the TWT flow identifier subfield includes an identifier of a TWT flow for which TWT information is requested or provided.
- the TWT flow identifier subfield may be reserved when the value of the all TWT subfield is 1.
- the response requested subfield may indicate whether the STA transmitting the frame including the TWT information field requests transmission of the TWT information frame in response to the frame. If the response requested subfield is set to 0, the receiving STA may be requested not to transmit the TWT information frame in response to the frame. If the response requested subfield is set to 1, the receiving STA may be requested to transmit the TWT information frame in response to the corresponding frame.
- next TWT request subfield may indicate that the TWT information frame is a request for delivery of a TWT information frame including a next TWT field of a non-zero length. Otherwise, the next TWT request subfield may be set to 0.
- next TWT subfield size subfield is 0, 1, 2, and 3 it may indicate that the size of the next TWT subfield is 0, 32, 48, and 64, respectively.
- the TWT information frame may indicate rescheduling of all TWTs. Otherwise, the all TWT subfield may be set to 0.
- the next TWT subfield may have a variable length according to the value of the next TWT subfield size.
- a value included in the next TWT subfield may have a value corresponding to the least significant portion of a timing synchronization function (TSF) in the next TWT for the TWT specified by the TWT flow identifier subfield.
- TSF timing synchronization function
- 17 is a diagram for explaining an example of a TWT information element format.
- the TWT information element may be transmitted and received by being included in a beacon, a probe response, a (re)association response frame, and the like.
- the TWT information element may include an element ID field, a length field, a control field, and a TWT parameter information field.
- the control field of the TWT information element has the same format regardless of individual TWT and broadcast TWT.
- the NDP paging indication subfield may have a value of 1 if the NDP paging field exists and may have a value of 0 if the NDP paging field does not exist.
- a responder PM mode subfield may indicate a power management (PM) mode.
- the negotiation type subfield may indicate whether the information included in the TWT element is for broadcast TWT or negotiation of parameters of individual TWT (s), or for a wake TBTT interval. .
- the TWT subfield is for the start time of an individual TWT SP in the future, and the TWT element includes one individual TWT parameter set. This may correspond to individual TWT negotiations between the TWT requesting STA and the TWT responding STA, or to individual TWT announcements by the TWT responder.
- the TWT subfield is for the next TBTT time, and the TWT element includes one individual TWT parameter set. This may correspond to wake TBTT and wake interval negotiation between a TWT scheduled STA and a TWT scheduling AP.
- the TWT subfield is for a future broadcast TWT SP start time
- the TWT element includes one or more broadcast TWT parameter sets. This may correspond to providing a broadcast TWT schedule to a TWT-scheduled STA by including a TWT element in a broadcast management frame transmitted by the TWT scheduling AP.
- the TWT subfield is for a future broadcast TWT SP start time
- the TWT element includes one or more broadcast TWT parameter sets. This may correspond to managing membership in a broadcast TWT schedule by including a TWT element in an individually addressed management frame transmitted by either a TWT-scheduled STA or a TWT-scheduled AP.
- TWT information frame disabled subfield If the TWT information frame disabled subfield is set to 1, it indicates that reception of the TWT information frame by the STA is disabled, otherwise it may be set to 0.
- the wake duration unit subfield indicates the unit of the nominal minimum TWT wake duration field.
- the wake duration unit subfield may be set to 0 when the unit is 256 us and set to 1 when the unit is TU. In the case of non-HE/EHT STAs, the wake duration unit subfield may be set to 0.
- a most significant bit (MSB) of the negotiation type field may correspond to a broadcast field. If the broadcast field is 1, one or more broadcast TWT parameter sets may be included in the TWT element. If the broadcast field is 0, only one individual TWT parameter set may be included in the TWT element.
- a TWT element in which the broadcast field is set to 1 may be referred to as a broadcast TWT element.
- 18 is a diagram for explaining examples of individual TWT parameter set field formats.
- 19 is a diagram for explaining examples of a broadcast TWT parameter set field format.
- the TWT parameter information field included in the TWT element of FIG. 17 may have a different configuration according to individual TWT or broadcast TWT.
- the TWT parameter information field in the TWT element contains a single individual TWT parameter set field.
- the TWT parameter information field in the TWT element includes one or more broadcast TWT parameter set fields.
- Each broadcast TWT parameter set may include specific information about one broadcast TWT.
- the individual TWT parameter set field and the broadcast TWT parameter set field include common subfields.
- the request type subfield may have the same size in the individual TWT parameter set field and the broadcast TWT parameter set field, but may have different detailed configurations. This will be described later.
- the target wake time subfield indicates the start time of a scheduled individual/broadcast TWT SP.
- the nominal minimum TWT wake duration subfield indicates the minimum unit that the TWT requesting STA expects to wake up to complete the frame exchange associated with the TWT flow identifier during the TWT wake interval duration.
- the TWT wake interval may mean an average time between consecutive TWT SPs expected by the TWT requesting STA.
- the TWT Wake Interval Mantissa subfield is a binary value of the TWT wake interval value and can be expressed in microseconds.
- the TWT group assignment subfield, TWT channel, and NDP paging subfield are included only in individual TWT parameter set fields.
- the TWT group assignment subfield includes information on the TWT group to which the STA is assigned and provides it to the TWT requesting STA.
- a TWT value within a TWT group may be calculated using the corresponding information.
- the TWT value of the STA may be equal to a value obtained by multiplying a value of a zero offset and a TWT offset by a value of a TWT unit.
- the TWT channel subfield represents a bitmap representing allowed channels.
- the TWT channel subfield may include a bitmap indicating a channel that the STA requests to use as a temporary basic channel during the TWT SP.
- the TWT channel subfield may include a bitmap indicating channels for which TWT requests are allowed.
- the NDP paging subfield is optional and may include an identifier of an STA to be paged, information related to the maximum number of TWT wake intervals between NDP paging frames, and the like.
- the broadcast TWT info subfield is included only in the broadcast TWT parameter set field.
- the broadcast TWT information subfield may include a 3-bit reserved bit, a 5-bit broadcast TWT identifier (ID) subfield, and an 8-bit broadcast TWT persistence subfield.
- the broadcast TWT identifier subfield indicates the broadcast ID of a specific broadcast TWT for which the STA requests participation or provides TWT parameters according to the value of the TWT setup command subfield of the TWT element.
- the broadcast TWT duration subfield indicates the number of TBTTs planned on the broadcast TWT schedule.
- the TWT request subfield may indicate whether it is a requesting STA or a responding STA. If the value is 1, it may indicate a TWT requesting STA or a scheduled STA, and if the value is 0, it may indicate a TWT responding STA or a scheduling AP.
- the TWT setup command subfield may indicate a command such as Request, Suggest, Demand, Accept, Alternate, Dictate, Reject, etc.
- the trigger subfield indicates whether to use a trigger frame in the TWT SP. If the value is 1, the trigger is used, and if the value is 0, the trigger may not be used.
- the implicit subfield may indicate whether it is an implicit TWT or an explicit TWT. If the value is 1, it may indicate implicit TWT, and if it is 0, it may indicate explicit TWT.
- the flow type subfield may indicate an interaction type between a TWT requesting STA (or a TWT scheduled STA) and a TWT responding STA (or a TWT scheduling AP). If the value is 1, the STA sends a PS-Poll or automatic power save delivery (APSD) trigger frame to send a wake-up signal to the AP before a frame other than the trigger frame is transmitted from the AP to the STA. Announced can mean TWT. If the value is 0, it may mean an unknown TWT.
- PS-Poll or automatic power save delivery (APSD) trigger frame to send a wake-up signal to the AP before a frame other than the trigger frame is transmitted from the AP to the STA.
- Announced can mean TWT. If the value is 0, it may mean an unknown TWT.
- the TWT flow identifier subfield may include a 3-bit value that uniquely identifies specific information about a corresponding TWT request in another request made between the same TWT requesting STA and TWT responding STA pair.
- the TWT wake interval exponent subfield may set the TWT wake interval value in binary microsecond units. In the case of individual TWTs, this may mean intervals between individual TWT SPs.
- the TWT wake interval of the requesting STA may be defined as [TWT Wake Interval Mantissa * 2 * TWT Wake Interval Exponent].
- the TWT protection subfield may indicate whether to use the TWT protection mechanism. If the value is 1, the TXOP in the TWT SP may start with a NAV protection mechanism such as (MU) RTS / CTS or CTS-to-self frame, and if it is 0, the NAV protection mechanism may not be applied.
- a NAV protection mechanism such as (MU) RTS / CTS or CTS-to-self frame
- the Last Broadcast Parameter Set subfield indicates whether it is the last broadcast TWT parameter set. If the value is 1, it may indicate that it is the last broadcast TWT parameter set, and if it is 0, it may indicate that the next broadcast TWT parameter set exists.
- the broadcast TWT recommendation subfield may indicate recommendations for a frame type transmitted by an AP during a broadcast TWT SP with a value of 1-7.
- the last 1 bit of the request type subfield of the broadcast TWT parameter set field may be reserved.
- latency may mean latency defined in the IEEE 802.11 family standard. For example, after a frame to be transmitted enters the queue of the MAC layer of the transmitting STA, transmission of the transmitting STA is successfully completed in the PHY layer, and the transmitting STA receives ACK/block ACK from the receiving STA to It may mean the time until the corresponding frame is deleted from the MAC layer queue of the transmitting STA.
- a non-AP STA supporting transmission of latency sensitive data may be referred to as a low latency STA.
- data other than latency-sensitive data may be referred to as regular data.
- 20 is a diagram for explaining an example of a limited TWT operation.
- restricted-TWT restricted-TWT
- the AP sets a special broadcast TWT for a low-latency STA that transmits latency-sensitive data, so that the possibility of data transmission for a low-latency STA is preferentially compared to other STAs can assist in obtaining
- the STA may establish membership for one or more r-TWT schedules for the AP.
- the r-TWT agreement may be established by the same process as the broadcast TWT agreement, and the broadcast TWT element for this may be defined to include an r-TWT parameter set field.
- an r-TWT parameter set may refer to a specific broadcast TWT parameter set field distinct from other broadcast TWT parameter set fields. That is, the r-TWT parameter set field may correspond to a special case of the broadcast TWT parameter set field.
- the AP may announce the r-TWT SP.
- an STA related to the r-TWT may perform traffic transmission/reception with priority over the other STAs within the r-TWT SP.
- a low latency STA related to a specific r-TWT is referred to as a member r-TWT scheduled STA, and other STAs are referred to as non-member STAs.
- the non-member STA has the capability to support the r-TWT operation but is not a member of any r-TWT, supports the r-TWT operation and is a member of another r-TWT, or supports the r-TWT operation. It may be an STA without capability.
- An STA eg, a low latency STA supporting the limited SP (or r-TWT SP) operation of broadcast TWT may inform the AP that latency sensitive data should be transmitted based on the r-TWT operation. If the AP supports the r-TWT operation/mode, the AP may transmit a frame including scheduling information of TWTs requested by each STA to STA(s) other than the low latency STA.
- non-AP STAs may use a beacon frame, a probe response frame, a (re)association response frame, or another frame of an undefined format (e.g., broadcast It is possible to obtain r-TWT related information from the AP through a frame for cast, advertisement, or announcement purpose.
- a separate TXOP i.e., access by other STAs is limited
- TXOP i.e., access by other STAs is limited
- a TXOP of another STA ie, a non-member STA
- TXOP of the other STA may be additionally performed after the specific r-TWT SP ends. This may be referred to as a TXOP rule-based operation for the r-TWT SP of a non-member STA.
- STA1 may correspond to a low latency STA
- STA2 may correspond to an STA that transmits and receives regular data.
- the AP may notify STAs of r-TWT related information through a frame such as a beacon.
- the TXOP holder, STA2 must end the corresponding TXOP before the start time of any r-TWT SP advertised by the associated AP.
- 21 is a diagram for explaining modification of a starting point of an r-TWT SP.
- the start time of the r-TWT SP may be modified or postpone for various reasons.
- a non-AP STA e.g., STA2
- a corresponding AP that supports r-TWT SPs announced from the AP and at the same time announces the corresponding r-TWT SP
- the corresponding STA can maintain its TXOP before the r-TWT SP. In this case, the starting point of the r-TWT SP may be delayed.
- a non-AP STA that does not support the r-TWT SP announced from the AP cannot know information about the schedule of the r-TWT SP in advance, its own TXOP held before the start of the r-TWT SP can keep In this case, the starting point of the r-TWT SP may be delayed.
- OBSS NAV TXOP
- 22 is a diagram for explaining an example of a modified r-TWT SP according to the present disclosure.
- the r-TWT SP when the start time of the r-TWT SP is modified/delayed, in order to secure sufficient time (eg, original r-TWT SP length) for latency-sensitive data/traffic transmission/reception, the r-TWT SP The end point of can be modified/extended/expanded.
- the r-TWT SP of FIG. 21 starts at a later point in time than the starting position of the r-TWT STA of FIG. 20 .
- it corresponds to a case in which data transmission and reception in the TXOP in progress before the start of the r-TWT SP ends before the start time of the r-TWT SP.
- FIG. 21 it corresponds to a case where data transmission and reception in the TXOP in progress before the start of the r-TWT SP is not ended before the start time of the r-TWT SP. Accordingly, in the example of FIG.
- the start time of the r-TWT SP is located later in time than the start time of the r-TWT SP of FIG. 20 (ie, the original starting time of FIG. 21).
- the start time of the r-TWT SP is determined by the frame transmitted and received by the corresponding STA in time It can be pushed back (i.e. postponed).
- the start time of the r-TWT SP starts later in time than the initially set time due to various factors in which the wireless medium (WM) is busy before the start time of the r-TWT SP. .
- the STA may transmit and receive related data during the duration of the SP of the TWT secured by scheduling in the AP.
- the starting point of the corresponding r-TWT SP is delayed due to ongoing data transmission and reception prior to the r-TWT SP, but the ending point of the r-TWT is the end of the SP of the r-TWT originally set by the AP. same as point of view In this case, time for transmission and reception of latency-sensitive data/traffic between the AP and the low-latency STA may not be sufficient.
- data/traffic scheduled to be transmitted/received within the original r-TWT SP duration may not all be transmitted/received within the shortened r-TWT SP duration due to the delay in starting time, resulting in residual data/traffic.
- the end time of the corresponding r-TWT SP can be postponed/extended to a later time point in time. Suggest. Also, whether to modify the end point of the corresponding r-TWT SP may be determined according to whether or not the start point of the r-TWT SP is modified.
- the r-TWT configured by the AP is referred to as the original r-TWT, and the r-TWT modified at one or more of the start time or end time point is referred to as the modified r-TWT.
- the duration of the SP of the r-TWT may not exceed the duration of the original SP of the r-TWT.
- the total time from the delayed starting point of the r-TWT to starting to transmit latency private data/traffic and ending the transmission cannot exceed the duration of the original SP.
- the total time from the delayed starting point of the r-TWT to starting to transmit latency private data/traffic and ending the transmission cannot exceed the duration of the original SP.
- the ending time of the corresponding r-TWT SP can be delayed by up to A ms.
- the length of time for which the end time is delayed may be determined within a range that does not exceed the length of time for which the start time is delayed. For example, when the start time is delayed by A ms, the length of time for which the end time is delayed may be set to a value equal to or less than A ms. Accordingly, the duration of the original r-TWT SP can be guaranteed as much as possible, and time to sufficiently exchange latency-sensitive data/traffic between the AP and the low-latency STA can be secured.
- the AP is configured so that other TWT SPs scheduled for a time after the original r-TWT SP are protected from the modified r-TWT SP (i.e., the modified r-TWT SP and other TWT SPs do not collide in time). , scheduling or rescheduling between TWT SPs can be performed.
- the AP may change the modified r-TWT SP to other TWTs (e.g., individual/broadcast TWT SPs and/or other r-TWT SPs).
- TWT can be scheduled so as not to overlap. That is, frame exchange in the modified r-TWT SP may be set so as not to overlap with frame exchange or TXOP in another scheduled TWT SP.
- a downlink (DL) transmission method in which an AP transmits latency-sensitive data/traffic to STA1 in an r-TWT SP is exemplarily shown.
- the present disclosure is not limited to this DL transmission scheme, but also includes an uplink (UL) transmission scheme in which an STA transmits latency-sensitive data/traffic to an AP within an r-TWT SP.
- FIG. 23 is a diagram for explaining an example of a limited TWT operation.
- FIG. 20 shows DL transmission and reception between AP and STA1 in the original (ie, unmodified) r-TWT SP
- the example of FIG. 23 shows AP and STA1 in the original (ie, unmodified) r-TWT SP.
- Indicates UL transmission and reception between The description of FIG. 20 is also applied to FIG. 23 and overlapping descriptions are omitted.
- 24 is a diagram for explaining an example of a modified r-TWT SP according to the present disclosure.
- FIG. 22 shows DL transmission and reception between the AP and STA1 in the modified r-TWT SP
- the example of FIG. 24 shows UL transmission and reception between the AP and STA1 in the modified r-TWT SP.
- the description of FIG. 22 is also applied to FIG. 24, and duplicate descriptions are omitted.
- STAs associated with an AP may include STAs with different capabilities for support of individual, broadcast, or limited TWT operations/mechanisms.
- STAs include STAs that do not support the TWT operation (eg, TWT operation itself including individual, broadcast, and limited TWT), and STAs that do not support the r-TWT operation (eg, individual/broadcast operation itself).
- STAs that support broadcast TWT operation but not r-TWT operation) and STAs that support r-TWT operation e.g., STAs that support individual, broadcast, and limited TWT operations). have.
- These various STAs may attempt channel access through EDCA after the TWT SP is terminated.
- an STA supporting r-TWT can know information about the r-TWT SP through a beacon, etc., and accordingly, can attempt channel access through EDCA after the original r-TWT SP ends.
- an STA that does not support r-TWT may be configured not to attempt channel access during the original r-TWT SP duration through a quiet interval or the like.
- the STA not aware of the modification of the r-TWT SP (in particular, the modification/extension of the end point of the r-TWT SP), the time from the end point of the original r-TWT SP to the end point of the modified r-TWT SP Channel access may be attempted during a period (hereinafter referred to as an extended time period).
- This may be a threat/interference to transmission/reception of latency-sensitive data/traffic during an extended time period.
- the modified r-TWT SP related information is provided by the AP to the STAs associated with the corresponding AP A new method of signaling (or notifying) is required.
- an AP notifies non-AP STAs assigned to the r-TWT SP of information related to modification/extension of the r-TWT SP termination point, and an STA associated with the AP (ie, including STAs not assigned r-TWT).
- the modification/extension of the end time of the r-TWT SP may be based on the modification/postponement of the start time of the corresponding r-TWT SP.
- the situation/reason for the modification/postponement of the start time of the r-TWT SP is not limited in the present disclosure. That is, the examples of the present disclosure may be applied to a case in which a start time of data exchange between an AP and a non-AP within an r-TWT SP starts later in time than the start time of the original r-TWT SP.
- the examples of this disclosure may be applied to modify/extend (only) the end time of the original r-TWT SP independently of the modification/postponement of the start time of the original r-TWT SP.
- latency-sensitive data/traffic or low latency data (LLD)
- LLD low latency data
- Modifying/extending the termination time of the r-TWT SP in this way may mean reallocating an already allocated r-TWT SP.
- information related to the modified r-TWT SP (in particular, information related to modification/extension of the end point of the r-TWT SP) is transmitted from the AP to the STA (information related to the existing r-TWT SP) through a method of signaling information related to the r-TWT SP. ) can be forwarded to.
- the message transmitted from the AP to the STAs includes information related to r-TWT SP modification (e.g., information on the modified/extended end point of the r-TWT SP, request for modification/extension of the r-TWT SP) information, etc.) may be included.
- a message may be required to be transmitted and received between the AP and the non-AP STA before the end of the original r-TWT SP.
- the AP may transmit a message including information related to modification of the r-TWT SP to STAs before the original r-TWT SP ends.
- one or more of the STAs assigned the r-TWT SP may transmit a message requesting modification of the r-TWT SP to the AP before the original r-TWT SP ends.
- 25 is a diagram for explaining an operation of an STA supporting a modified r-TWT SP according to an embodiment of the present disclosure.
- the STA may receive r-TWT related information from the AP.
- the r-TWT SP-related information may include information on an initially set (ie, original) r-TWT start time and r-TWT end time.
- the STA may receive information related to the modified end point of the r-TWT SP from the AP after the start point of the r-TWT SP.
- the start time of the r-TWT SP may be the start time of the r-TWT SP that has been modified/postponed due to a predetermined cause, or may be the start time of the original r-TWT SP. That is, information related to modification/extension of the r-TWT SP end time may be signaled based on or independently of the modification/delay of the r-TWT SP start time.
- the information related to the modified end time of the r-TWT SP includes an indication of whether the end time of the r-TWT SP is modified, the duration of the modified r-TWT SP, and the end time and modification based on the r-TWT related information. It may include one or more of a time difference between the modified end points, or a modified end point.
- information related to the modified end point of the r-TWT SP may be provided from the AP at the request of the STA or without the request of the STA.
- the STA's request may be for modification/extension of the r-TWT SP termination point itself, or may be a request for scheduling information for one or more TWT SPs other than the r-TWT SP.
- the STA Accordingly, the AP may request modification/extension of the r-TWT SP termination point. Specific examples for this will be described later in Examples 1 and 2.
- information related to the modified end time of the r-TWT SP may be signaled to STA(s) supporting the r-TWT operation, and STA(s) including STAs not supporting the r-TWT operation ) may be signaled to.
- the modified end point of the r-TWT SP may be signaled. Specific examples for this will be described later in Example 3-1 and its sub-embodiments.
- whether or not the end time of the r-TWT SP is modified and/or the modified end time of the r-TWT SP may be signaled through the trigger frame. Specific examples for this will be described later in Example 3-2.
- information related to the modified end time of the r-TWT SP may be signaled through a new format. Specific examples for this will be described later in Example 4.
- the STA may perform frame exchange with the AP based on the modified end time of the r-TWT SP.
- the STA may perform frame exchange with the AP in a time interval between the start of the delayed r-TWT SP and the end of the extended r-TWT SP.
- frame exchange may include transmission and reception of DL/UL latency sensitive data/traffic.
- other STA(s) signaled with information related to the modified end of the r-TWT SP attempt channel access may not be present in the time interval between the end of the original r-TWT SP and the end of the modified/extended r-TWT SP.
- 26 is a diagram for explaining an operation of an AP supporting a modified r-TWT SP according to an embodiment of the present disclosure.
- the AP may transmit r-TWT related information to one or more first STAs.
- r-TWT-related information is the same as that described in step S2510 of FIG. 25, so duplicate descriptions are omitted.
- One or more first STAs may include STAs supporting the r-TWT operation.
- the AP may transmit information related to the modified end point of the r-TWT SP to one or more second STAs after the starting point of the r-TWT SP.
- the one or more second STAs may include one or more of an STA supporting the r-TWT operation, an STA supporting the TWT operation but not supporting the r-TWT operation, or an STA not supporting the TWT operation itself.
- the AP may perform frame exchange with one or more first STAs based on the modified end point of the r-TWT SP.
- an STA eg, a second STA
- the STA eg, the first STA
- APs and STAs related to the signaling of the modified r-TWT SP related information depends on the subject (ie, DL/UL) that transmits data (eg, latency-sensitive data/traffic) within the r-TWT SP.
- data eg, latency-sensitive data/traffic
- DL/UL data that transmits data
- data e.g., latency-sensitive data/traffic
- an AP and a non-AP STA transmit specific data (e.g., the first data/traffic among multiple data/traffic in the SP) in the r-TWT SP to the AP (i.e., DL ) or non-AP STA (ie, UL), it may operate differently.
- This embodiment corresponds to an r-TWT SP modification operation initiated by an AP (AP-initiated).
- This example may be applied when data transmitted in the r-TWT SP is DL, but is not limited thereto and may also be applied to UL.
- the AP may notify the non-AP STA(s) that the end point of the extended r-TWT SP is extended. This notification may be signaled to STAs from the AP at or after the start of the modified/postponed r-TWT SP.
- the STAs may include not only the STA to which the corresponding r-TWT is allocated/reallocated, but also other STAs to which the r-TWT is not allocated/reallocated.
- the AP may signal information related to r-TWT SP modification (eg, information indicating an extended r-TWT SP termination point) to STAs.
- STAs to which the modified/extended r-TWT SP is allocated/reassigned may be all or part of the STA group to which the original r-TWT SP is allocated.
- the r-TWT SP modification/extension information includes all STAs belonging to the STA group assigned the original r-TWT SP, including the STA(s) to which the modified/extended r-TWT SP is applied. It may be notified to STAs that do not support the r-TWT operation.
- an AP when an AP transmits latency-sensitive data/traffic to a non-AP STA (ie, DL), the AP transmits the corresponding
- related information eg, extended SP time, etc.
- This embodiment corresponds to an r-TWT SP modification operation initiated by a non-AP STA (STA-initiated).
- STA-initiated This example may be applied when data transmitted in the r-TWT SP is UL, but is not limited thereto and may also be applied to DL.
- the STA may request the AP to modify/extend the r-TWT SP. Accordingly, the AP may notify STAs of information related to modification/extension of the r-TWT SP.
- the STA's r-TWT SP modification/extension request is the STA requesting related information from the AP (eg, scheduling information scheduled after the original r-TWT SP), or the STA requesting r-TWT SP from the AP.
- This may include notifying the need for TWT SP modification/extension.
- the STA determines whether the r-TWT SP can be modified/extended based on the scheduling information provided from the AP, and can request the AP to modify/extend the r-TWT SP accordingly.
- the STA may request r-TWT SP modification/extension without considering scheduling information.
- the AP may determine whether r-TWT SP modification/extension is possible based on the STA's request. If the AP determines that the r-TWT SP modification/extension (specifically, the modification/extension of the r-TWT SP termination point) is possible, the AP informs the non-AP STA(s) that the termination point of the extended r-TWT SP is An extension may be announced. This notification may be signaled to STAs from the AP at or after the start of the modified/postponed r-TWT SP.
- the STAs may include not only the STA to which the corresponding r-TWT is allocated/reallocated, but also other STAs to which the r-TWT is not allocated/reallocated.
- the AP may signal information related to r-TWT SP modification (eg, information indicating an extended r-TWT SP termination point) to STAs.
- the AP may transmit an approval or rejection message to the STA requesting r-TWT SP modification/extension.
- the r-TWT SP modification/extension notification (and the modified/extended r-TWT SP termination time information) may be transmitted to STAs including the requesting STA without an explicit approval message.
- the requesting STA may determine that the r-TWT SP modification/extension is rejected.
- the STA determines the modified/extended r-TWT SP (particularly, the modified/extended r-TWT SP end point) and provides it to the AP You may.
- the AP may use the end time provided by the STA as it is or may modify and apply it.
- the AP may deliver to the STA an approval or rejection message for the end time provided by the STA.
- the AP may provide the STA with information about the end point of the r-TWT SP modified by the AP along with a rejection message.
- the r-TWT SP when there is only one STA requesting, the r-TWT SP may be extended only for the corresponding STA. In addition, when there are a plurality of requesting STAs, the r-TWT SP may be extended based on the maximum value among the times required for data transmission and reception of the corresponding STAs.
- r-TWT SP modification/extension may be applied to some or all of the STA groups to which the original r-TWT SP is allocated.
- the r-TWT SP modification/extension information includes all STAs belonging to the STA group assigned the original r-TWT SP, including the STA(s) to which the modified/extended r-TWT SP is applied. It may be notified to STAs that do not support the r-TWT operation.
- the non-AP STA when the non-AP STA transmits latency-sensitive data/traffic to the AP (ie, UL case), the non-AP STA sends the AP an individual scheduled after the current (ie, original) r-TWT SP. / Broadcast TWT SP or other r-TWTs can be requested for scheduling information about SPs (hereinafter, other TWT SPs).
- the non-AP STA extends the end point of the r-TWT SP You may decide you can't. In this case, the end point of the corresponding r-TWT SP follows the original end point set by the AP.
- the non-AP STA is You may decide that you may request an extension. That is, the extension of the r-TWT SP may be possible if the end point of the corresponding r-TWT SP is not infringed/overlapped with another TWT SP.
- the non-AP STA may request the AP to extend the termination point of the corresponding r-TWT SP.
- the AP may perform an operation capable of approving or rejecting the request of the corresponding non-AP STA.
- the non-AP STA may determine that it can request an extension of the termination point of the r-TWT SP. In this case, the non-AP STA may request the AP to extend the termination point of the corresponding r-TWT SP.
- the AP may perform an operation capable of approving or rejecting the request of the corresponding non-AP STA.
- This embodiment relates to a method for an AP to signal information about r-TWT SP modification/extension to STAs.
- Information (or elements, fields, subfields, etc.) described below can be transmitted and received between AP and non-AP STA (s) based on a defined frame (eg, management / action / control / data frame) have.
- a defined frame eg, management / action / control / data frame
- This embodiment relates to a method for an AP to notify r-TWT SP modification/extension related information to non-AP STA(s) supporting TWT operation.
- TWT information field Using the value of the TWT information field, whether the end point of the r-TWT SP is modified/extended, the duration of the modified/extended r-TWT SP, the time difference between the original end point and the modified/extended end point, or Information on one or more of the modified/extended end points may be transmitted and received.
- the modified/extended end point of the r-TWT SP (eg, TSF timer value) may be indicated.
- TWT extension can be defined in the action frame of the TWT information frame. Using the TWT extension subfield, whether the end time of the r-TWT SP is modified/extended, the duration of the modified/extended r-TWT SP, the time difference between the original end time and the modified/extended end time, or modified /Can transmit/receive information about one or more of the extended end points.
- the TWT setup action frame may include a TWT element (eg, FIGS. 17 to 19). Additionally or alternatively, a TWT setup command subfield within a TWT element subfield of a TWT setup action frame (or a TWT setup command subfield and other subfields within a TWT element subfield (e.g., in the examples of FIGS. 17 to 19) Modification/extension of the end point of the r-TWT SP may be indicated through one or more combinations of reserved fields). This embodiment may be referred to as an implicit notification scheme.
- the AP sends an unsolicited TWT setup action frame including the same identification information (eg, broadcast TWT ID) identifying the corresponding r-TWT SP to the STA(s) ) can be sent to Additionally or alternatively, after starting the original r-TWT SP, the AP may transmit to the STA(s) a TWT setup action frame in which the TWT setup command (or a combination of the TWT setup command and one or more other subfields) has a specific value. can Accordingly, the STA(s) may recognize that the r-TWT SP is modified/extended.
- the same identification information eg, broadcast TWT ID
- the AP may transmit to the STA(s) a TWT setup action frame in which the TWT setup command (or a combination of the TWT setup command and one or more other subfields) has a specific value.
- the STA(s) may recognize that the r-TWT SP is modified/extended.
- the STA(s) receives a frame including a broadcast TWT ID in the r-TWT SP and/or receives a frame in which the TWT setup command has a specific value, based on the r-TWT SP
- the modification/extension of may be implicitly recognized.
- the modified/extended r-TWT SP end point can be obtained based on the value of the target wake time subfield in the TWT parameter set field.
- r-TWT SP modification/extension related information is signaled to STA(s) having the same identification information (eg, broadcast TWT ID), explicit signaling (eg, , an indication of a specific value through the TWT setup command), the STA(s) can understand that the TWT setup action frame transmitted in the r-TWT SP is signaling for r-TWT SP modification/extension.
- identification information eg, broadcast TWT ID
- explicit signaling eg, an indication of a specific value through the TWT setup command
- TWT setup command subfields in the TWT element subfields of unsolicited TWT setup action frames (or TWT setup command subfields and other subfields in the TWT element subfields (eg, in the examples of FIGS. 17 to 19)
- Modification/extension of the end point of the r-TWT SP may be indicated through one or more combinations of reserved fields).
- Information on the end time of the modified/extended r-TWT SP may be included in the corresponding frame. This embodiment may be referred to as an explicit notification scheme.
- the AP uses the TWT setup command subfield (and additional fields) to inform the modification/extension of the end point of the r-TWT SP, and the modified/extended r-TWT SP
- the end point of can be signaled.
- implicit notification method instead of notifying only the STA(s) with the same broadcast TWT ID, according to the explicit notification method, all STAs supporting the broadcast TWT operation are notified of the r-TWT SP. Modification/extension related information may be notified.
- a TWT setup action frame transmitted in an r-TWT SP and having a TWT setup command set to a specific value may indicate/indicate modification/extension of the end time of the corresponding r-TWT SP.
- the value of the TWT setup command subfield is 0, 1, 2, 3, 4, 5, 6, and 7, request, proposal, request, grouping, acceptance, change, command, rejection ( Request, Suggest, Demand, Grouping, Accept, Alternate, Dictate, Reject) can be indicated respectively.
- a specific value of the TWT setup command subfield may be 5 or 6. This is just an example, and the specific value of the TWT setup command is not limited to 5 or 6.
- an unsolicited TWT setup action frame transmitted from the AP with the value of the TWT setup command subfield set to 5 or 6 indicates modification/extension notification at the end of the r-TWT SP. can do.
- the end point of the modified/extended r-TWT SP may be signaled based on the value of the target wake time subfield in the TWT parameter set field.
- modification of the end point of the r-TWT SP/ You may request an extension.
- the TWT setup action frame in which the TWT setup command subfield is set to a specific value provides information on the end time of the modified/extended r-TWT SP. Including can be indicated.
- the second example may explicitly indicate that the r-TWT SP is a TWT element (or TWT setup action frame) for modification/extension through a specific field/value.
- B15 defined as a currently reserved field/bit
- the request type field of the TWT parameter set field of the TWT element can be newly defined as a new subfield (eg, SP extension subfield).
- SP extension subfield e.g, 1, it can indicate that the r-TWT SP is modified/extended (in particular, the end point of the r-TWT SP is modified/extended), and if it is 0, the r-TWT SP is modified/extended. It can be indicated that it does not.
- the AP transmits an unsolicited TWT setup action frame with the value of the SP extension subfield set to 1 and the value of the TWT setup command subfield set to a specific value (5 or 6) after starting the r-TWT SP, the corresponding The TWT setup command may mean modification/extension of the r-TWT SP.
- the end point of the modified/extended r-TWT SP may be signaled based on a new/changed value of the target wake time subfield in the TWT parameter set field.
- one specific value among possible values of the TWT setup command subfield may be newly defined to mean r-TWT SP modification/extension.
- the TWT element (or TWT setup action frame) including the TWT setup command set to a specific value is for modification/extension of the r-TWT SP without combining with other information.
- a value of 1, 2, 5, or 6 in the TWT setup command subfield indicates an extension to the TWT (ie, suggest TWT, demand TWT, alternate TWT, or dictate TWT) alternatively) can be defined.
- the AP transmits an unsolicited TWT setup action frame in which the value of the TWT setup command subfield is set to a specific value (1, 2, 5 or 6) after starting the r-TWT SP, the corresponding TWT setup command is r-TWT It can mean modification/extension of SP.
- the end point of the modified/extended r-TWT SP may be signaled based on a new/changed value of the target wake time subfield in the TWT parameter set field.
- This embodiment relates to a method for an AP to notify r-TWT SP modification/extension related information to non-AP STA(s) including a non-AP STA supporting a TWT operation. For example, r-TWT SP modification/extension and/or related information may be notified without using the TWT element.
- a new field/value related to modification/extension of the r-TWT SP may be included in a trigger frame initially transmitted within the original r-TWT SP.
- the trigger frame may include a common info field and zero or more user info fields.
- the common information field is information commonly applied to transmission of one or more TB PPDUs requested by the trigger frame, for example, trigger type, UL length, presence or absence of a subsequent trigger frame (eg, More TF), CS (channel) sensing) request, UL BW (bandwidth), and the like.
- Each user information field includes AID12, RU allocation, UL FEC (forward error correction) coding type, UL EHT-MCS, SS (spatial stream) allocation / RA (random access) -RU information, UL target received power, It may include subfields such as PS160 and trigger dependent user information, and may also include reserved subfields.
- information indicating whether the r-TWT SP is modified/extended may be included in the common information field of the trigger frame.
- specific information such as the end point of the modified/extended r-TWT SP may be included in the user information field of the trigger frame.
- This embodiment defines a new frame (eg, management / action / control / data frame) that is not defined, so that information on r-TWT SP modification / extension is transmitted and received between the AP and non-AP STA (s) It's about how to do it.
- a new frame eg, management / action / control / data frame
- r-TWT SP modification/extension related information may be included in the form of an A-control field of a MAC header.
- the HT control subfield of the MAC header may include an aggregated (A)-control subfield.
- the A-control subfield may include control list bits of variable length and zero or more padding bits.
- a control list may include one or more control subfields.
- One control subfield may include a 4-bit control ID and variable length control information.
- one of reserved values (eg, 7 to 14) of the control ID may be newly defined as a value indicating r-TWT SP correction/extension.
- the control information of the A-control subfield having a control ID set to such a specific value may include specific information such as a modified/extended r-TWT SP end point.
- r-TWT SP modification/extension related information may be included as an element in an action frame of an aggregated (A)-MPDU.
- A-MPDU may correspond to an action frame added to a data MPDU.
- r-TWT SP modification/extension related information may be included in a newly defined element or may be included in a TWT element.
- the AP can signal information related to the modification/extension of the original r-TWT SP end point (or start point and end point) to the STA(s), flexible modification/extension of the r-TWT SP and can quickly secure the time required for urgent transmission and reception of necessary data (eg, latency-sensitive data/traffic).
- the scope of the present disclosure is software or machine-executable instructions (eg, operating systems, applications, firmware, programs, etc.) that cause operations in accordance with the methods of various embodiments to be executed on a device or computer, and such software or It includes a non-transitory computer-readable medium in which instructions and the like are stored and executable on a device or computer. Instructions that may be used to program a processing system that performs the features described in this disclosure may be stored on/in a storage medium or computer-readable storage medium and may be viewed using a computer program product that includes such storage medium. Features described in the disclosure may be implemented.
- the storage medium may include, but is not limited to, high speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or It may include non-volatile memory, such as other non-volatile solid state storage devices.
- the memory optionally includes one or more storage devices located remotely from the processor(s).
- the memory, or alternatively, the non-volatile memory device(s) within the memory includes non-transitory computer readable storage media.
- Features described in this disclosure may be stored on any one of the machine readable media to control hardware of a processing system and to allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. It may be integrated into software and/or firmware.
- Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments/containers.
- the method proposed in the present disclosure has been described focusing on an example applied to an IEEE 802.11 based system, but it can be applied to various wireless LANs or wireless communication systems other than the IEEE 802.11 based system.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (28)
- 무선랜 시스템에서 스테이션(STA)에 의한 프레임 교환을 수행하는 방법에 있어서, 상기 방법은:액세스 포인트(AP)로부터 제한된 타겟 웨이크 시간(r-TWT) 관련 정보를 수신하는 단계;상기 r-TWT 관련 정보에 기초한 상기 r-TWT 서비스 기간(SP)의 시작 시점 후에, 상기 r-TWT SP의 수정된 종료 시점에 관련된 정보를 상기 AP로부터 수신하는 단계; 및상기 r-TWT SP의 수정된 종료 시점에 기초하여 상기 프레임 교환을 수행하는 단계를 포함하는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 상기 STA의 요청 없이 상기 AP에 의해서 시그널링되는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 상기 STA의 요청에 기초하여 상기 AP에 의해서 시그널링되는, 방법.
- 제 3 항에 있어서,상기 STA의 요청은, 상기 r-TWT SP의 종료 시점의 수정에 대한 요청, 또는 상기 r-TWT SP 이외의 하나 이상의 TWT SP에 대한 스케줄링 정보에 대한 요청인, 방법.
- 제 4 항에 있어서,상기 스케줄링 정보에 기초하여, 상기 r-TWT SP의 종료 시점의 수정에 대한 요청이 상기 AP에게 전송되는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, r-TWT 동작을 지원하는 하나 이상의 STA에게 시그널링되는, 방법.
- 제 6 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, TWT 정보 필드, 또는 TWT 요소 중의 하나 이상에 포함되는, 방법.
- 제 7 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 상기 TWT 정보 필드의 모든(all) TWT 필드, TWT 플로우 식별자 필드, 다음 TWT 필드 중의 하나 이상에 기초하여 지시되는, 방법.
- 제 7 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 상기 TWT 정보 필드의 TWT 연장(extension) 서브필드에 기초하여 지시되는, 방법.
- 제 7 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 미요청형(unsolicited) TWT 셋업 액션 프레임을 통하여 전달되는 상기 TWT 요소에 기초하여 지시되는, 방법.
- 제 10 항에 있어서,상기 TWT 요소에 포함되는 상기 r-TWT SP에 대한 식별 정보가 상기 r-TWT 관련 정보에 포함되는 상기 r-TWT SP에 대한 식별 정보와 동일함에 기초하여, 상기 r-TWT SP의 수정된 종료 시점은 상기 TWT 요소 내의 타겟 웨이크 타입 서브필드의 값을 통하여 시그널링되는, 방법.
- 제 10 항에 있어서,상기 TWT 요소에 포함되는 TWT 셋업 커맨드 서브필드가 특정 값으로 설정되는 것에 기초하여, 상기 r-TWT SP의 수정된 종료 시점은 상기 TWT 요소 내의 타겟 웨이크 타입 서브필드의 값을 통하여 시그널링되는, 방법.
- 제 10 항에 있어서,상기 TWT 요소는 상기 r-TWT SP의 종료 시점의 수정 여부를 지시하는 특정 서브필드를 포함하고,상기 특정 서브필드가 상기 r-TWT SP의 종료 시점의 수정을 지시하고, 상기 TWT 요소에 포함되는 TWT 셋업 커맨드 서브필드가 특정 값으로 설정되는 것에 기초하여, 상기 r-TWT SP의 수정된 종료 시점은 상기 TWT 요소 내의 타겟 웨이크 타입 서브필드의 값을 통하여 시그널링되는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, r-TWT 동작을 지원하지 않는 STA을 포함하는 하나 이상의 STA에게 시그널링되는, 방법.
- 제 14 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 트리거 프레임에 포함되는, 방법.
- 제 15 항에 있어서,상기 트리거 프레임의 공통 정보 필드에 상기 r-TWT SP의 종료 시점의 수정 여부를 지시하는 정보가 포함되고,상기 r-TWT SP의 수정된 종료 시점은 상기 트리거 프레임의 사용자 정보 필드를 통하여 시그널링되는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, A(aggregated)-control 필드, 또는 A(aggregated)-MPDU(MAC protocol data unit)의 액션 프레임 중의 하나 이상에 포함되는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점에 관련된 정보는, 상기 r-TWT SP의 종료 시점의 수정 여부 지시, 수정된 r-TWT SP의 듀레이션, 상기 r-TWT 관련 정보에 기초한 종료 시점과 수정된 종료 시점 간의 시간 차이, 또는 수정된 종료 시점 중의 하나 이상을 포함하는, 방법.
- 제 1 항에 있어서,상기 프레임 교환은 하향링크(DL) 또는 상향링크(UL) 레이턴시 민감 데이터의 송수신을 포함하는, 방법.
- 제 1 항에 있어서,상기 r-TWT SP의 수정된 종료 시점은, 상기 r-TWT 관련 정보에 기초한 상기 r-TWT SP의 종료 시점보다 연장된 시점인, 방법.
- 제 1 항에 있어서,상기 프레임 교환은 상기 r-TWT SP의 수정된 시작 시점 후에 시작되는, 방법.
- 제 1 항에 있어서,상기 r-TWT 관련 정보는 상기 AP로부터 브로드캐스트되는, 방법.
- 제 1 항에 있어서,상기 STA은 r-TWT 동작을 지원하는 STA인, 방법.
- 무선랜 시스템에서 프레임 교환을 수행하는 스테이션(STA)에 있어서, 상기 STA은:하나 이상의 송수신기; 및상기 하나 이상의 송수신기와 연결된 하나 이상의 프로세서를 포함하고,상기 하나 이상의 프로세서는:액세스 포인트(AP)로부터 제한된 타겟 웨이크 시간(r-TWT) 관련 정보를 상기 하나 이상의 송수신기를 통하여 수신하고;상기 r-TWT 관련 정보에 기초한 상기 r-TWT 서비스 기간(SP)의 시작 시점 후에, 상기 r-TWT SP의 수정된 종료 시점에 관련된 정보를 상기 AP로부터 상기 하나 이상의 송수신기를 통하여 수신하고; 및상기 r-TWT SP의 수정된 종료 시점에 기초하여 상기 프레임 교환을 상기 하나 이상의 송수신기를 통하여 수행하도록 설정되는, STA.
- 무선랜 시스템에서 액세스 포인트(AP)에 의한 프레임 교환을 수행하는 방법에 있어서, 상기 방법은:하나 이상의 제 1 스테이션(STA)에게 제한된 타겟 웨이크 시간(r-TWT) 관련 정보를 전송하는 단계;상기 r-TWT 관련 정보에 기초한 상기 r-TWT 서비스 기간(SP)의 시작 시점 후에, 상기 r-TWT SP의 수정된 종료 시점에 관련된 정보를 상기 하나 이상의 제 1 STA을 포함하는 하나 이상의 제 2 STA에게 전송하는 단계; 및상기 r-TWT SP의 수정된 종료 시점에 기초하여 상기 하나 이상의 제 1 STA과 상기 프레임 교환을 수행하는 단계를 포함하는, 방법.
- 무선랜 시스템에서 프레임 교환을 수행하는 액세스 포인트(AP)에 있어서, 상기 AP는:하나 이상의 송수신기; 및상기 하나 이상의 송수신기와 연결된 하나 이상의 프로세서를 포함하고,상기 하나 이상의 프로세서는:하나 이상의 제 1 스테이션(STA)에게 제한된 타겟 웨이크 시간(r-TWT) 관련 정보를 상기 하나 이상의 송수신기를 통하여 전송하는 단계;상기 r-TWT 관련 정보에 기초한 상기 r-TWT 서비스 기간(SP)의 시작 시점 후에, 상기 r-TWT SP의 수정된 종료 시점에 관련된 정보를 상기 하나 이상의 제 1 STA을 포함하는 하나 이상의 제 2 STA에게 상기 하나 이상의 송수신기를 통하여 전송하는 단계; 및상기 r-TWT SP의 수정된 종료 시점에 기초하여 상기 하나 이상의 제 1 STA과 상기 프레임 교환을 상기 하나 이상의 송수신기를 통하여 수행하는 단계를 포함하는, AP.
- 무선랜 시스템에서 프레임 교환을 수행하기 위해 스테이션(STA)을 제어하도록 설정되는 프로세싱 장치에 있어서, 상기 프로세싱 장치는:하나 이상의 프로세서; 및상기 하나 이상의 프로세서에 동작 가능하게 연결되고, 상기 하나 이상의 프로세서에 의해 실행됨에 기반하여, 동작들을 수행하는 명령들을 저장하는 하나 이상의 컴퓨터 메모리를 포함하며,상기 동작들은:액세스 포인트(AP)로부터 제한된 타겟 웨이크 시간(r-TWT) 관련 정보를 수신하는 동작;상기 r-TWT 관련 정보에 기초한 상기 r-TWT 서비스 기간(SP)의 시작 시점 후에, 상기 r-TWT SP의 수정된 종료 시점에 관련된 정보를 상기 AP로부터 수신하는 동작; 및상기 r-TWT SP의 수정된 종료 시점에 기초하여 상기 프레임 교환을 수행하는 동작을 포함하는, 프로세싱 장치.
- 하나 이상의 명령을 저장하는 하나 이상의 비-일시적(non-transitory) 컴퓨터 판독가능 매체로서,상기 하나 이상의 명령은 하나 이상의 프로세서에 의해서 실행되어, 무선랜 시스템에서 프레임 교한을 수행하는 장치가:액세스 포인트(AP)로부터 제한된 타겟 웨이크 시간(r-TWT) 관련 정보를 수신하고;상기 r-TWT 관련 정보에 기초한 상기 r-TWT 서비스 기간(SP)의 시작 시점 후에, 상기 r-TWT SP의 수정된 종료 시점에 관련된 정보를 상기 AP로부터 수신하고; 및상기 r-TWT SP의 수정된 종료 시점에 기초하여 상기 프레임 교환을 수행하도록 제어하는, 컴퓨터 판독가능 매체.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22807857.2A EP4340520A1 (en) | 2021-05-12 | 2022-05-12 | Method and apparatus for modifying target wake time service period in wireless lan system |
KR1020237036195A KR20240005695A (ko) | 2021-05-12 | 2022-05-12 | 무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 수정방법 및 장치 |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR10-2021-0061434 | 2021-05-12 | ||
KR20210061434 | 2021-05-12 | ||
KR10-2021-0074277 | 2021-06-08 | ||
KR20210074277 | 2021-06-08 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022240210A1 true WO2022240210A1 (ko) | 2022-11-17 |
Family
ID=84029351
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/006802 WO2022240210A1 (ko) | 2021-05-12 | 2022-05-12 | 무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 수정 방법 및 장치 |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP4340520A1 (ko) |
KR (1) | KR20240005695A (ko) |
WO (1) | WO2022240210A1 (ko) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190053155A1 (en) * | 2017-08-09 | 2019-02-14 | Apple Inc. | Device-Availability-Based Wake-Up Time Schedule |
US20210007168A1 (en) * | 2019-07-01 | 2021-01-07 | Qualcomm Incorporated | Signaling for multi-link communication in a wireless local area network (wlan) |
-
2022
- 2022-05-12 WO PCT/KR2022/006802 patent/WO2022240210A1/ko active Application Filing
- 2022-05-12 EP EP22807857.2A patent/EP4340520A1/en active Pending
- 2022-05-12 KR KR1020237036195A patent/KR20240005695A/ko unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190053155A1 (en) * | 2017-08-09 | 2019-02-14 | Apple Inc. | Device-Availability-Based Wake-Up Time Schedule |
US20210007168A1 (en) * | 2019-07-01 | 2021-01-07 | Qualcomm Incorporated | Signaling for multi-link communication in a wireless local area network (wlan) |
Non-Patent Citations (3)
Title |
---|
CHUNYU HU (FACEBOOK): "Restricted-TWT-Quiet-Interval-TBD-CR", IEEE DRAFT; 11-21-0683-05-00BE-RESTRICTED-TWT-QUIET-INTERVAL-TBD-CR, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 5, 11 May 2021 (2021-05-11), Piscataway, NJ USA , pages 1 - 5, XP068180150 * |
PATRICE NEZOU (CANON): "Low-Latency Triggered TWT", IEEE DRAFT; 11-20-1843-03-00BE-LOW-LATENCY-TRIGGERED-TWT, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 3, 20 February 2021 (2021-02-20), Piscataway, NJ USA , pages 1 - 15, XP068178804 * |
SUNHEE BAEK: "CR for Restricted TWT SP", IEEE DRAFT; 11-21-0672-00-00BE-CR-FOR-RESTRICTED-TWT-SP, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 0, 15 April 2021 (2021-04-15), Piscataway, NJ USA , pages 1 - 3, XP068179753 * |
Also Published As
Publication number | Publication date |
---|---|
KR20240005695A (ko) | 2024-01-12 |
EP4340520A1 (en) | 2024-03-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2023224336A1 (ko) | 무선랜 시스템에서 센싱 절차를 수행하는 방법 및 장치 | |
WO2022260351A1 (ko) | 무선랜 시스템에서 타겟 웨이크 타임 기반의 통신 수행 방법 및 장치 | |
WO2022203416A1 (ko) | 무선랜 시스템에서 타겟 웨이크 타임 동작에 관련된 우선순위 기반 전송 방법 및 장치 | |
WO2022240210A1 (ko) | 무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 수정 방법 및 장치 | |
WO2023172068A1 (ko) | 무선랜 시스템에서 제한된 타겟 웨이크 타임 기반의 통신 수행 방법 및 장치 | |
WO2023177262A1 (ko) | 무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 재스케줄링 방법 및 장치 | |
WO2023121333A1 (ko) | 무선랜 시스템에서 중첩 침묵 인터벌 기반 송신 또는 수신 방법 및 장치 | |
WO2023153913A1 (ko) | 무선랜 시스템에서 타겟 웨이크 타임 기반 서브채널 선택적 전송을 수행하는 방법 및 장치 | |
WO2023063782A1 (ko) | 무선랜 시스템에서 서비스 기간 기반 센싱 방법 및 장치 | |
WO2023167509A1 (ko) | 무선랜 시스템에서 타겟 웨이크 타임 서비스 기간 재스케줄링 방법 및 장치 | |
WO2023219328A1 (ko) | 무선랜 시스템에서 센싱 절차를 수행하는 방법 및 장치 | |
WO2023075327A1 (ko) | 무선랜 시스템에서 센싱 측정을 수행하는 방법 및 장치 | |
WO2023022564A1 (ko) | 무선랜 시스템에서 센싱 절차를 수행하는 방법 및 장치 | |
WO2023234720A1 (ko) | 무선랜 시스템에서 확장된 대역폭을 위한 동작 모드를 지시하는 방법 및 장치 | |
WO2023128571A1 (ko) | 무선랜 시스템에서 센싱 측정을 위한 방법 및 장치 | |
WO2023018275A1 (ko) | 무선랜 시스템에서 ndp 피드백 보고 응답 송수신 방법 및 장치 | |
WO2023128642A1 (ko) | 무선랜 시스템에서 센싱 측정 방법 및 장치 | |
WO2023224306A1 (ko) | 무선랜 시스템에서 센싱 절차를 수행하는 방법 및 장치 | |
WO2023182810A1 (ko) | 무선랜 시스템에서 센싱 절차를 수행하는 방법 및 장치 | |
WO2023128569A1 (ko) | 무선랜 시스템에서 센싱 측정을 위한 방법 및 장치 | |
WO2023204514A1 (ko) | 무선랜 시스템에서 병합 물리 계층 프로토콜 데이터 유닛 송수신 방법 및 장치 | |
WO2023229312A1 (ko) | 무선랜 시스템에서 트리거 프레임 기반 ppdu 송수신 방법 및 장치 | |
WO2022220487A1 (ko) | 무선랜 시스템에서 프리앰블 펑처링 기반의 전송 방법 및 장치 | |
WO2023191501A1 (ko) | 무선랜 시스템에서 채널 액세스 방법 및 장치 | |
WO2023136692A1 (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: 22807857 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18558512 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022807857 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: 2022807857 Country of ref document: EP Effective date: 20231212 |