Wireless communication method supporting multiple PPDU formats and wireless communication terminal using the same

Abstract

To disclose a station that communicates wirelessly.SOLUTION: A station includes a transmitting / receiving unit and a processor. The processor receives, via the transmitting / receiving unit, a triggering frame to trigger transmission of the station, determines a value of a length field in a signaling field of a trigger-based (TB) PPDU (Physical layer Protocol Data Unit) based on a type of the triggering frame and a type of the trigger-based PPDU sent as a response to the triggering frame, where the length field indicates a value used to calculate a duration of the TB PPDU, and transmits the TB PPDU.SELECTED DRAWING: Figure 35

Description

[Technical Field]

[0001] The present invention relates to a wireless communication method that supports multiple PPDU formats and a wireless communication terminal that uses the same. [Background technology]

[0002] In recent years, as the proliferation of mobile devices has expanded, Wireless LAN (Wireless LAN) technology, which can provide fast wireless internet services to these devices, has been attracting considerable attention. Wireless LAN technology is a technology that enables mobile devices such as smartphones, smartpads, laptop computers, portable multimedia players, and embedded devices to connect to the internet wirelessly from homes, businesses, or specific service areas, based on short-range wireless communication technology.

[0003] The IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard has been commercializing or developing various technologies since supporting early wireless LAN technologies using the 2.4GHz frequency band. First, IEEE 802.11b supports a maximum communication speed of 11Mbps while using the 2.4GHz band frequency. IEEE 802.11a, which was commercialized after IEEE 802.11b, reduces interference compared to the highly congested 2.4GHz band by using the 5GHz band frequency instead of the 2.4GHz band, and improves communication speeds to a maximum of 54Mbps using OFDM (orthogonal frequency division multiplexing) technology. However, IEEE 802.11a has the disadvantage of a shorter communication range compared to IEEE 802.11b. Furthermore, IEEE 802.11g, like IEEE 802.11b, has attracted considerable attention for achieving a maximum communication speed of 54Mbps using the 2.4GHz band frequency and for satisfying backward compatibility, and it also has an advantage over IEEE 802.11a in terms of communication range.

[0004] Furthermore, IEEE 802.11n is a technical standard established to overcome the limitations in communication speed that have been considered a weakness of wireless LANs. The purpose of IEEE 802.11n is to increase network speed and reliability and extend the operating range of wireless networks. More specifically, IEEE 802.11n supports high throughput (HT) with a data processing speed of 540 Mbps or more, and is based on MIMO (Multiple Inputs and Multiple Outputs) technology, which uses multiple antennas at both the transmitter and receiver ends to minimize transmission errors and optimize data speed. In addition, this standard allows for a coding scheme that transmits multiple duplicate copies to improve data reliability.

[0005] As the proliferation of wireless LANs accelerates and the applications using them diversify, the need for new wireless LAN systems to support very high throughput (VHT) above the data processing speeds supported by IEEE 802.11n has emerged. Among these, IEEE 802.11ac supports a wide bandwidth (80MHz to 160MHz) at the 5GHz frequency. While the IEEE 802.11ac standard is defined only in the 5GHz band, early 11ac chipsets will also support operation in the 2.4GHz band for backward compatibility with existing 2.4GHz band products. Theoretically, this standard allows for wireless LAN speeds of at least 1Gbps for multiple stations and at least 500Mbps for single-link speeds. This extends the wireless interface concepts accepted in 802.11n, including wider radio frequency bandwidth (up to 160MHz), more MIMO spatial streams (up to 8), multiple user MIMO, and high-density modulation (up to 256QAM). Another method for transmitting data using the 60GHz band instead of the existing 2.4GHz / 5GHz bands is IEEE 802.11ad. IEEE 802.11ad is a transmission standard that uses beamforming technology to provide speeds of up to 7Gbps, making it suitable for large amounts of data and high-bitrate video streaming such as uncompressed HD video. However, the 60GHz frequency band has the disadvantage of being difficult to penetrate obstacles, and can only be used between devices in close proximity.

[0006] Meanwhile, the IEEE 802.11ax (High Efficiency WLAN, HEW) standard, which provides highly efficient and high-performance wireless LAN communication technology in high-density environments where access points (APs) and terminals are densely packed, is nearing the end of its development phase as a wireless LAN standard for 802.11ac and 802.11ad and beyond. In an 802.11ax-based wireless LAN environment, it is necessary to provide highly frequency-efficient communication indoors and outdoors in the presence of a high density of stations and APs (Access Points), and various technologies are being developed to realize this.

[0007] Furthermore, new wireless LAN standards are beginning to be developed to increase maximum transmission speeds in order to support new multimedia applications such as high-definition video and real-time games. The 7th generation wireless LAN standard, IEEE 802.11be (Extremely High Throughput, EHT), is being developed with the goal of supporting a maximum transmission rate of 30 Gbps in the 2.4 / 5 / 6 GHz band through wider bandwidth, increased spatial streams, and multiple AP cooperation. [Overview of the project] [Problems that the invention aims to solve]

[0008] One embodiment of the present invention aims to provide a wireless communication method that supports multiple PPDU formats and a wireless communication terminal that uses the same. [Means for solving the problem]

[0009] According to one embodiment of the present invention, a wireless communication station comprises a transmitting and receiving unit,

[0010] A processor, which, via the transceiver, receives a triggering frame that triggers the station to transmit, determines the value of the Length field of the signaling field of the TB PPDU based on the type of the triggering frame and the type of trigger-based (TB) PPDU (physical layer protocol data unit) transmitted in response to the triggering frame, the Length field indicates a value used to calculate the duration of the TB PPDU, and transmits the TB PPDU.

[0011] The processor may, when the triggering frame is a trigger frame, set the value of L_Length of TXVECTOR as the value of the UL Length field of the trigger frame, and set the value obtained based on the L_Length value according to the TB PPDU format as the value of the Length field. When the triggering frame is a frame that includes a TRS Control field, the processor may set the L_Length value based on the TB PPDU format and a formula specified in advance for each TB PPDU format, and set the value of the Length field to the L_Length value plus 2.

[0012] If the triggering frame is a frame containing a TRS Control field and the format of the TB PPDU is HE TB PPDU, the value of L_Length can be set to a value obtained by a formula pre-specified for the HE TB PPDU. If the triggering frame is a frame containing a TRS Control field and the format of the TB PPDU is EHT TB PPDU, the value of L_Length can be set to a value obtained by subtracting 2 from the value obtained by a formula pre-specified for the EHT TB PPDU.

[0013] The remainder when the value of the Length field is divided by 3 may be used to distinguish between the HE TB PPDU and the EHT TB PPDU.

[0014] The formula pre-specified for the aforementioned EHT TB PPDU may be the following formula:

[0015] Length = ceil( (TXTIME - SignalExtension - 20) / 4 )*3 - 3

[0016] ceil(x) represents the rounded-up value of x, SignalExtension represents the length of a signal extension, and TXTIME may be obtained by the formula below.

[0017] TXTIME = 20 + T_EHT_PREAMBLE + N_SYM*T_SYM + T_PE + SignalExtension

[0018] T_EHT_PREAMBLE is the length of the preamble of said EHT TB PPDU excluding L-STF, L-LTF and L-SIG, N_SYM*T_SYM is the length of the data field of said EHT TB PPDU, N_SYM is the number of data OFDM symbols, T_SYM is the length of one OFDM symbol, and T_PE may be the length of a packet extension field.

[0019] When receiving a PPDU (physical layer protocol data unit) via said transmitting / receiving unit, if said PPDU satisfies a pre-specified condition, said processor may acquire the value of a PHY Version Identifier field indicating the format of said PPDU from the signaling field of said received PPDU, and when the acquired value of the PHY Version Identifier field indicates a PPDU format not supported by said station, set the value of FORMAT of RXVECTOR transmitted to the MAC (medium access control) layer of said station to a pre-specified value.

[0020] When the acquired value of the PHY Version Identifier field indicates a PPDU format supported by said station, said processor may set the value of FORMAT of RXVECTOR to a value corresponding to the PPDU format indicated by the acquired value of the PHY Version Identifier field.

[0021] The received PPDU may include a Version Independent field regardless of the value of the PHY Version Identifier field. In this case, if the acquired value of the PHY Version Identifier field indicates a PPDU format not supported by the station, the processor can transmit the information obtained from the Version Independent field to the MAC layer of the station.

[0022] The processor can set the CH_BANDWIDTH, UPLINK_FLAG, BSS_COLOR, and TXOP_DURATION of the RXVECTOR based on the information obtained from the Version Independent field. CH_BANDWIDTH indicates the bandwidth of the received PPDU, UPLINK_FLAG indicates whether the received PPDU is an uplink PPDU, BSS_COLOR indicates the BSS color to which the received PPDU belongs, and TXOP_DURATION indicates the duration of the TXOP to which the received PPDU was exchanged.

[0023] An embodiment of the present invention provides a method for operating a wirelessly communicating station, comprising the steps of: receiving a triggering frame that triggers the station to transmit; determining the value of the Length field of the signaling field of the TB PPDU based on the type of the triggering frame and the type of trigger-based (TB) PPDU (physical layer protocol data unit) transmitted as a response to the triggering frame, wherein the Length field indicates a value used to calculate the duration of the TB PPDU; and transmitting the TB PPDU.

[0024] The steps for determining the value of the Length field of the signaling field of the TB PPDU may include, when the triggering frame is a trigger frame, setting the value of L_Length of TXVECTOR to the value of the UL Length field of the trigger frame, and setting the value obtained based on the L_Length value according to the format of the TB PPDU as the value of the Length field; and when the triggering frame is a frame that includes a TRS Control field, setting the value of L_Length based on the format of the TB PPDU and a formula specified in advance for each format of the TB PPDU, and setting the value of the Length field to the value of L_Length plus 2.

[0025] If the triggering frame is a frame containing a TRS Control field, the step of setting the value of the Length field may include the steps of setting the value of L_Length to a value obtained by a formula pre-specified for the HE TB PPDU if the triggering frame is a frame containing a TRS Control field and the format of the TB PPDU is HE TB PPDU, and setting the value of L_Length to a value obtained by subtracting 2 from the value obtained by a formula pre-specified for the EHT TB PPDU if the triggering frame is a frame containing a TRS Control field and the format of the TB PPDU is EHT TB PPDU.

[0026] The remainder when the value of the Length field is divided by 3 may be used to distinguish between the HE TB PPDU and the EHT TB PPDU.

[0027] The formula pre-specified for the aforementioned EHT TB PPDU may be the following formula:

[0028] Length = ceil( (TXTIME - SignalExtension - 20) / 4 )*3 - 3

[0029] ceil(x) represents the rounded-up value of x,

[0030] SignalExtension may represent the length of the signal extension.

[0031] TXTIME can be obtained using the following formula.

[0032] TXTIME = 20 + T_EHT_PREAMBLE + N_SYM*T_SYM + T_PE + SignalExtension

[0033] T_EHT_PREAMBLE is the length of the preamble of the EHT TB PPDU excluding L-STF, L-LTF, and L-SIG; N_SYM*T_SYM is the length of the data field of the EHT TB PPDU, N_SYM is the number of data OFDM symbols, T_SYM is the length of one OFDM symbol, and T_PE may be the length of the packet extension field.

[0034] The above operating method may further include the steps of: when receiving a PPDU (physical layer protocol data unit) via the transmitting / receiving unit, obtaining the value of the PHY Version Identifier field that indicates the format of the PPDU from the signaling field of the received PPDU if the PPDU satisfies pre-specified conditions; and setting the FORMAT value of RXVECTOR transmitted to the MAC (medium access control) layer of the station to a pre-specified value if the obtained value of the PHY Version Identifier field indicates a PPDU format not supported by the station.

[0035] The above operating method may further include the step of setting the FORMAT value of RXVECTOR to a value corresponding to the PPDU format indicated by the value of the acquired PHY Version Identifier field, when the acquired value of the PHY Version Identifier field indicates a PPDU format supported by the station.

[0036] The received PPDU may include a Version Independent field regardless of the value of the PHY Version Identifier field. In this case, the operation method may further include a step of transmitting information obtained from the Version Independent field to the MAC layer of the station if the value of the acquired PHY Version Identifier field indicates a PPDU format not supported by the station.

[0037] The step of transmitting the information obtained from the Version Independent field to the MAC layer of the station may include the step of setting the CH_BANDWIDTH, UPLINK_FLAG, BSS_COLOR, and TXOP_DURATION of the RXVECTOR based on the information obtained from the Version Independent field. CH_BANDWIDTH indicates the bandwidth of the received PPDU, UPLINK_FLAG indicates whether the received PPDU is an uplink PPDU, BSS_COLOR indicates the BSS color to which the received PPDU belongs, and TXOP_DURATION indicates the duration of the TXOP to which the received PPDU was exchanged. [Effects of the Invention]

[0038] One embodiment of the present invention provides a wireless communication method that efficiently supports multiple PPDU formats and a wireless communication terminal that uses the same. [Brief explanation of the drawing]

[0039] [Figure 1] This shows a wireless LAN system according to one embodiment of the present invention. [Figure 2] This shows a wireless LAN system according to another embodiment of the present invention. [Figure 3] The configuration of a station according to one embodiment of the present invention is shown. [Figure 4] The configuration of an access point according to one embodiment of the present invention is shown. [Figure 5] This outlines the process by which STA establishes a link with AP. [Figure 6] This document describes the CSMA (Carrier Sense Multiple Access) / CA (Collision Avoidance) methods used in wireless LAN communication. [Figure 7] Examples of various standard generational PPDU (PLCP Protocol Data Unit) formats are shown. [Figure 8] Examples of various EHT (Extremely High Throughput) PPDU (Physical Protocol Data Unit) formats and methods for specifying them according to embodiments of the present invention are shown. [Figure 9] This shows a multi-link device according to one embodiment of the present invention. [Figure 10] This shows a multilink mapped by a TID-to-link mapping method according to an embodiment of the present invention. [Figure 11] This illustrates the power management operation performed by a station according to an embodiment of the present invention. [Figure 12] The format of a TIM element according to an embodiment of the present invention is shown. [Figure 13] The format of a Multi-Link Traffic element according to an embodiment of the present invention is shown. [Figure 14]This embodiment of the present invention shows how the Partial Virtual Bitmap subfield of a Multi-Link Traffic element and a TIM element signals buffered traffic to an AP multilink device. [Figure 15] This document describes a method for configuring a Multi-Link Traffic element according to an embodiment of the present invention. [Figure 16] This invention describes a method for setting the Per-Link Traffic Bitmap subfield of a Multi-Link Traffic element when the link set on which the AP multilink device operates and the link set on which the non-AP multilink device communicating with the AP multilink device operates are different. [Figure 17] This invention illustrates a method by which the link indicated by the Per-Link Traffic Bitmap subfield is determined by TID-to-link mapping. [Figure 18] This describes yet another embodiment of the present invention, in which an AP multilink device sets the Per-Link Traffic Indication Bitmap subfield of a Multi-Link Traffic element. [Figure 19] An EHT Operation element according to an embodiment of the present invention is shown. [Figure 20] This shows a Traffic indication virtual bitmap according to an embodiment of the present invention. [Figure 21] This shows a Traffic indication virtual bitmap according to an embodiment of the present invention. [Figure 22] This shows signaling related to a Multi-Link element and MediumSyncDelay according to one embodiment of the present invention. [Figure 23] This shows the multilink setup process according to an embodiment of the present invention. [Figure 24]The format of the Reduced Neighbor Report element according to an embodiment of the present invention is shown. [Figure 25] This document describes a method for setting the ID of a multilink device according to an embodiment of the present invention. [Figure 26] An embodiment of the present invention illustrates a method for assigning an AID to a non-AP station belonging to a multilink device. [Figure 27] An embodiment of the present invention illustrates a method for assigning an AID to a non-AP station belonging to a multilink device. [Figure 28] An embodiment of the present invention illustrates a TID-to-link mapping negotiation in which an AP multilink device transmits a TID-to-link mapping request. [Figure 29] An embodiment of the present invention illustrates a TID-to-link mapping negotiation in which an AP multilink device transmits a TID-to-link mapping request. [Figure 30] This flowchart shows an example of the operation of a terminal according to one embodiment of the present invention. [Figure 31] The frame format and field format according to embodiments of the present invention are shown. [Figure 32] This document illustrates the UL MU operation of a station according to an embodiment of the present invention and the operation by which the station determines the TB PPDU format. [Figure 33] This example demonstrates the UL MU operation of a station according to an embodiment of the present invention, and how the station sets the L_LENGTH of TXVECTOR and transmits PPDU during UL MU operation. [Figure 34] This demonstrates the UL MU operation of a station according to yet another embodiment of the present invention, and how the station transmits a PPDU with the TXVECTOR's L_LENGTH set during UL MU operation. [Figure 35] This demonstrates the UL MU operation of a station according to yet another embodiment of the present invention, and how the station transmits a PPDU with the TXVECTOR's L_LENGTH set during UL MU operation. [Figure 36] This demonstrates that a station according to an embodiment of the present invention receives a PPDU and sets the FORMAT of the RXVECTOR. [Modes for carrying out the invention]

[0040] The terminology used herein has been selected to the greatest extent possible from currently widely used general terms, taking into account the function of the present invention; however, this may differ depending on the intent, conventions, or emergence of new technologies of the articulators. In addition, in certain cases, the applicant has arbitrarily selected some terms, in which case their meaning will be described in the relevant section of the invention description. Therefore, it should be made clear that the terms used herein are not merely names of terms, but should be interpreted based on the substantive meaning of the terms and the overall content of this specification.

[0041] Throughout the specification, when one component is described as being "connected" to another, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other components in between. Furthermore, when a component is described as "containing" a particular component, this means, unless otherwise stated, that it may contain other components rather than excluding them. In addition, limitations such as "greater than or equal to" or "less than or equal to" a specific threshold may be appropriately replaced by "greater than" or "less than" depending on the embodiment.

[0042] In the present invention, the terms "field" and "subfield" may be used interchangeably.

[0043] Figure 1 shows a wireless LAN system according to one embodiment of the present invention.

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

[0045] As shown in Figure 1, the infrastructure BSS BSS1, BSS2 includes one or more stations STA1, STA2, STA3, STA4, STA5, access points AP-1, AP-2 which are stations that provide distribution services, and a distribution system DS that connects multiple access points AP-1, AP-2.

[0046] A Station (STA) is any device that includes Medium Access Control (MAC) and a Physical Layer interface to a wireless medium in accordance with the IEEE 802.11 standard, and in a broad sense includes not only non-AP stations but also all access point (AP) stations. In this specification, "terminal" is used to refer to non-AP, AP, or both. A station for wireless communication includes a processor and a communication unit, and depending on the embodiment, further includes a user interface unit and a display unit, etc. The processor generates frames to be transmitted over the wireless network or processes frames received over the wireless network, and performs various other processing for controlling the station. The communication unit is functionally connected to the processor and sends and receives frames over the wireless network for the station. In this invention, "terminal" is used as a term that includes user equipment (UE).

[0047] An Access Point (AP) is an individual device that provides connectivity to a distribution system (DS) via a wireless medium for stations associated with it. In infrastructure BSS, communication between non-AP stations is generally conducted via APs, however, direct communication is possible between non-AP stations if a direct link is configured. In this invention, AP is used as a concept that includes PCP (Personal BSS Coordination Point), but in a broader sense, it includes all concepts such as central controllers, base stations (BS), node B, BTS (Base Transceiver System), or site controllers. In this invention, AP is also referred to as a base wireless communication terminal, but in a broader sense, base wireless communication terminal is used as a term that includes APs, base stations, eNBs (eNodeBs), and transmission points (TPs). Furthermore, base wireless communication terminals include various forms of wireless communication terminals that allocate and schedule communication medium resources in communication with multiple wireless communication terminals.

[0048] Multiple infrastructure BSSs are connected to each other via a distribution system DS. In this case, multiple BSSs connected via the distribution system are called an Extended Service Set (ESS).

[0049] Figure 2 shows an independent BSS, which is a wireless LAN system according to another embodiment of the present invention. In the embodiment of Figure 2, redundant explanations are omitted for parts that are the same as or corresponding to the embodiment of Figure 1.

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

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

[0052] First, the communication unit 120 transmits and receives wireless signals such as wireless LAN packets and may be incorporated into or externally mounted to the station 100. According to one embodiment, the communication unit 120 may include at least one communication module that uses different frequency bands. For example, the communication unit 120 may include communication modules for different frequency bands such as 2.4GHz, 5GHz, 6GHz, and 60GHz. According to one embodiment, the station 100 may include a communication module that uses a frequency band of 7.125GHz or higher and a communication module that uses a frequency band of 7.125GHz or lower. Each communication module can wirelessly communicate with an AP or external station based on the wireless LAN standard of the frequency band supported by the communication module. Depending on the performance and requirements of the station 100, the communication unit 120 may operate only one communication module at a time or operate multiple communication modules together simultaneously. When the station 100 includes multiple communication modules, each communication module may be provided in an independent form, or the multiple modules may be integrated as a single chip. In embodiments of the present invention, the communication unit 120 can represent an RF (Radio Frequency) communication module that processes RF signals.

[0053] Next, the user interface 140 includes various forms of input / output means provided in the station 100. In other words, the user interface unit 140 receives user input using various input means, and the processor 110 controls the station 100 based on the received user input. The user interface unit 140 also outputs based on instructions from the processor 110 using various output means.

[0054] Next, the display unit 150 outputs an image to the display screen. The display unit 150 outputs various display objects, such as content generated by the processor 110 or user interfaces based on control instructions from the processor 110. The memory 160 stores control programs used by the station 100 and various data associated with them. Such control programs include connection programs necessary for the station 100 to connect with APs or external stations.

[0055] The processor 110 of the present invention executes various instructions or programs and processes data within the station 100. The processor 110 also controls each unit of the station 100 and controls the transmission and reception of data between units. In an embodiment of the present invention, the processor 110 executes a program for connection with the AP stored in the memory 160 and receives a communication setup message transmitted by the AP. The processor 110 also reads information regarding the priority conditions of the station 100 contained in the communication setup message and requests a connection to the AP based on the priority conditions of the station 100. The processor 110 of the present invention may refer to the main control unit of the station 100, or, depending on the embodiment, may refer to a control unit for individually controlling a part of the station 100's configuration, such as the communication unit 120. In other words, the processor 110 may be a modem or a modulator and / or demodulator that modulates and demodulates the wireless signals transmitted and received from the communication unit 120. The processor 110 controls various operations of wireless signal transmission and reception of the station 100 according to an embodiment of the present invention. A detailed embodiment of this will be described later.

[0056] The station 100 shown in Figure 3 is a block diagram according to one embodiment of the present invention, and the separately shown blocks represent logically distinguished elements of the device. Therefore, the above-described elements of the device are mounted on one chip or multiple chips depending on the device design. For example, the processor 110 and the communication unit 120 may be integrated and implemented on a single chip, or they may be implemented on separate chips. Furthermore, in the embodiment of the present invention, some components of the station 100, such as the user interface unit 140 and the display unit 150, may be selectively provided in the station 100.

[0057] Figure 4 is a block diagram showing the configuration of AP200 according to one embodiment of the present invention. As shown, AP200 according to an embodiment of the present invention includes a processor 210, a communication unit 220, and a memory 260. In Figure 4, redundant explanations are omitted for parts of the AP200 configuration that are the same as or correspond to the configuration of station 100 in Figure 3.

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

[0059] Next, the memory 260 stores the control program used by the AP200 and various data associated with it. Such a control program includes a connection program that manages the connection of stations. The processor 210 controls each unit of the AP200 and controls the transmission and reception of data between units. In one embodiment of the present invention, the processor 210 executes the program for connecting with stations stored in the memory 260 and sends a communication setting message to one or more stations. In this case, the communication setting message includes information regarding the connection priority conditions of each station. The processor 210 also sets up the connection in response to the connection request from the station. In one embodiment, the processor 210 is a modem or modulation / demodulation unit that modulates and demodulates the wireless signals transmitted and received from the communication unit 220. The processor 210 controls various operations of wireless signal transmission and reception of the AP200 according to the embodiment of the present invention. A detailed embodiment relating thereto will be described later.

[0060] Figure 5 is a schematic diagram illustrating the process by which STA establishes a link with AP.

[0061] Referring to Figure 5, the link between STA100 and AP200 is established through three main steps: scanning, authentication, and association. First, the scanning step is the step in which STA100 obtains connection information for the BSS operated by AP200. There are two methods for performing scanning: passive scanning, which obtains information using only the beacon message S101 that AP200 periodically transmits, and active scanning, in which STA100 sends a probe request to AP S103, receives a probe response from AP S105, and obtains connection information.

[0062] In the scanning step, if STA100 successfully receives wireless connection information, it sends an authentication request (S107a), receives an authentication response from AP200 (S107b), and performs the authentication step. After the authentication step is performed, STA100 sends an association request (S109a), receives an association response from AP200 (S109b), and performs the association step. In this specification, "association" basically means wireless coupling, but the present invention is not limited to this, and in a broad sense, coupling includes all wireless and wired couplings.

[0063] On the other hand, an additional 802.1X-based authentication step S111 and an IP address acquisition step S113 via DHCP are performed. In Figure 5, Server 300 is a server that processes authentication between STA100 and the 802.1X-based system, and may be physically connected to AP200 or exist as a separate server.

[0064] Figure 6 shows the CSMA (Carrier Sense Multiple Access) / CA (Collision Avoidance) method used in wireless LAN communication.

[0065] A terminal performing wireless LAN communication checks whether a channel is busy or not by performing carrier sensing before transmitting data. If a wireless signal above a certain strength is detected, the channel is determined to be busy, and the terminal delays access to that channel. This process is called Clear Channel Assessment (CCA), and the level at which the detection of the signal is determined is called the CCA threshold. If a wireless signal above the CCA threshold is received by the terminal and the terminal is the recipient, the terminal processes the received wireless signal. On the other hand, if no wireless signal is detected from the channel, or if a wireless signal below the CCA threshold is detected, the channel is determined to be idle.

[0066] If a channel is determined to be idle, each terminal with data to transmit performs a backoff procedure after a time period determined by the status of each terminal, such as an IFS (Inter Frame Space), AIFS (Arbitration IFS), PIFS (PCF IFS), etc. In this embodiment, the AIFS is used as a replacement for the conventional DIFS (DCF IFS). Each terminal waits, decreasing a slot time equal to a random number determined for that terminal during the interval of idle state of the channel, and the terminal that has exhausted all of its slot time attempts to access the channel. The period in which each terminal performs this backoff procedure is called the competition window period. At this time, the random number can be called the backoff counter. That is, the initial value of the backoff counter is set by an integer, which is a random number acquired by the terminal. If a terminal senses that the channel is idle during the slot time, the terminal can decrease the backoff counter by 1. Also, when the backoff counter reaches 0, the terminal may be allowed to access the channel. Therefore, terminal transmission may be permitted when the channel is idle during the AIFS time and the backoff counter slot time.

[0067] If a specific terminal successfully accesses the channel, it transmits data through the channel. However, if the terminal attempting access collides with another terminal, the colliding terminals are each assigned a new random number and perform a further backoff procedure. In one embodiment, the random number newly assigned to each terminal is determined within a range twice the range (competition window, CW) of the random number previously assigned to that terminal (2*CW). Meanwhile, each terminal attempts access again in the next competition window interval by performing a further backoff procedure, but this time, each terminal performs the backoff procedure from the slot time remaining in the previous competition window interval. In this way, each terminal performing wireless LAN communication can avoid collisions with each other for a specific channel.

[0068] <Examples of various PPDU formats>

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

[0070] Referring to Figure 7(a), the legacy PPDU preamble includes L-STF (Legacy Short Training field), L-LTF (Legacy Long Training field), and L-SIG (Legacy Signal field). In embodiments of the present invention, the L-STF, L-LTF, and L-SIG can be referred to as the legacy preamble.

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

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

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

[0074] Referring to Figure 7(d), L-SIG includes the L_RATE field and the L_LENGTH field. The L_RATE field consists of 4 bits and indicates the MCS used for data transmission. Specifically, the L_RATE field indicates one of the transmission speeds of 6 / 9 / 12 / 18 / 24 / 36 / 48 / 54 Mbps, which is a combination of a modulation scheme such as BPSK / QPSK / 16-QAM / 64-QAM and a code rate such as 1 / 2, 2 / 3, or 3 / 4. Combining the information from the L_RATE and L_LENGTH fields allows us to determine the total length of the PPDU. In the non-legacy PPDU format, the L_RATE field is set to the minimum speed of 6 Mbps.

[0075] The L_LENGTH field is measured in bytes, with a total of 12 bits allocated, allowing for signaling up to 4095. In combination with the L_RATE field, it can indicate the length of the PPDU. In this case, legacy and non-legacy terminals can parse the L_LENGTH field in different ways.

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

[0077]

number

[0078] At this time,

number

[0079]

number

[0080] Here, TXTIME is the total transmission time that constitutes the PPDU, as shown in Equation 3 below. In this case, TX represents the transmission time of X.

[0081]

number

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

[0083] Referring to Figure 7(e), the U-SIG (Universal SIG) field persists in EHT PPDUs and subsequent generations of wireless LAN PPDUs, playing a role in distinguishing which generation of PPDU it is, including 11be. The U-SIG is a 64FFT-based OFDM with two symbols, capable of transmitting a total of 52 bits of information. Of these, 43 bits, excluding the 9 bits of CRC / tail, are broadly divided into the VI (Version Independent) field and the VD (Version Dependent) field.

[0084] The VI bit maintains its current bit configuration, allowing current 11be terminals to obtain information about a PPDU from its VI field even when subsequent generations of PPDUs are defined. To this end, the VI field consists of the PHY version, UL / DL, BSS color, TXOP, and Reserved fields. The PHY version field is 3 bits and is responsible for sequentially distinguishing 11be and subsequent generations of wireless LAN standards by version. 11be has a value of 000b. The UL / DL field distinguishes whether the PPDU is an uplink or downlink PPDU. The BSS color represents the BSS identifier defined in 11ax and has a value of 6 bits or more. The TXOP represents the Transmit Opportunity Duration, which was transmitted in the MAC header, but by adding it to the PHY header, the length of the TXOP containing the PPDU can be inferred without decoding the PPDU, and it has a value of 7 bits or more.

[0085] The VD field may consist of the PPDU format as signaling information useful only for the 11be version of PPDU, fields that are common to any PPDU format such as BW, and fields that are defined differently depending on the PPDU format. The PPDU format is a divisor that distinguishes between EHT SU (Single User), EHT MU (Multiple User), EHT TB (Trigger-based), EHT ER (Extended Range) PPDU, etc. The BW field broadly signals five basic PPDU BW options of 20, 40, 80, 160 (80+80), and 320 (160+160) MHz (BW that can be expressed in the form of a power of 20*2 can be called a basic BW), and various remaining PPDU BWs composed of preamble puncturing. In addition, after being signaled at 320 MHz, some 80 MHz may be punctured and then signaled. Furthermore, the punctured and deformed channel shape may be signaled directly in the BW field, or it may be signaled using both the BW field and fields appearing after the BW field (for example, fields within the EHT-SIG field). If the BW field is 3 bits, a total of 8 BW signalings are possible, so a maximum of 3 puncturing modes can be signaled. If the BW field is 4 bits, a total of 16 BW signalings are possible, so a maximum of 11 puncturing modes can be signaled.

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

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

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

[0089] In the case of an SU PPDU, multiple RUs may be assigned to the STA, and these RUs may be consecutive or discontinuous. When the RUs assigned to the STA are not consecutive, the STA can efficiently receive the SU PPDU only if it recognizes the punctured RU in the middle. Therefore, the AP can transmit the SU PPDU including information about the punctured RUs among the RUs assigned to the STA (e.g., the puncturing pattern of the RUs). That is, in the case of an SU PPDU, the EHT-SIG field may contain a puncturing mode field that includes information on whether a puncturing mode was applied and the puncturing pattern shown in bitmap format or similar, and the puncturing mode field can signal the form of discontinuous channels appearing within the bandwidth.

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

[0091] The reason only restricted forms of discontinuous channel configurations are signaled is to reduce the signaling overhead of the SU PPDU. Since puncturing can be performed on each 20MHz subchannel, when puncturing is performed on a bandwidth with multiple 20MHz subchannels, such as 80, 160, and 320MHz, in the case of 320MHz, the usage status of the remaining 15 20MHz subchannels other than the primary channel must be represented, and the discontinuous channel configuration (if a configuration where only the end 20MHz is punctured is also considered discontinuous) must be signaled. Using 15 bits to signal the discontinuous channel configuration for single-user transmission in this way can result in excessive signaling overhead when considering the low transmission speed of the signaling portion.

[0092] This invention proposes a method for signaling the discontinuous channel configuration of an SU PPDU and illustrates the discontinuous channel configuration determined by the proposed method. Furthermore, it proposes a method for signaling the primary 160MHz and secondary 160MHz puncturing configurations of an SU PPDU in a 320MHz BW configuration.

[0093] Furthermore, in one embodiment of the present invention, a method is proposed in which the configuration of the PPDU indicated by the preamble puncturing BW value differs depending on the signaled PPDU format in the PPDU format field. Assuming that the BW field is 4 bits, in the case of an EHT SU PPDU or TB PPDU, one symbol of EHT-SIG-A is further signaled after U-SIG, or it is not necessary to signal EHT-SIG-A from the beginning. Taking this into consideration, it is necessary to fully signal up to 11 puncturing modes using only the BW field of U-SIG. However, in the case of an EHT MU PPDU, EHT-SIG-B is further signaled after U-SIG, so up to 11 puncturing modes can be signaled in a different way than in an SU PPDU. In the case of an EHT ER PPDU, the BW field can be set to 1 bit to signal whether the PPDU uses a 20MHz or 10MHz bandwidth. Detailed puncturing patterns for each PPDU type will be described in detail in Figures 11 and 12.

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

[0095] Figure 8 shows examples of various EHT (Extremely High Throughput) PPDU (Physical Protocol Data Unit) formats and methods for specifying them according to embodiments of the present invention.

[0096] Referring to Figure 8, a PPDU may consist of a preamble and a data portion, and one type of format, EHT PPDU, may be distinguished by a U-SIG field included in the preamble. Specifically, whether or not the PPDU format is EHT PPDU may be indicated based on the PPDU format field included in the U-SIG field.

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

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

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

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

[0101] The EHT MU PPDU described in Figure 8(c) can be used by an AP to transmit downlink data to multiple STAs. In this case, the EHT MU PPDU may include scheduling information so that multiple STAs can simultaneously receive PPDUs transmitted from the AP. The EHT MU PPDU can transmit the AID information of the recipient and / or sender of the PPDU transmitted through the user-specific field of EHT-SIG-B to the STAs. Therefore, multiple terminals that receive the EHT MU PPDU can perform spatial reuse operations based on the AID information in the user-specific field included in the preamble of the received PPDU.

[0102] Specifically, the resource unit allocation (RA) field in the HE-SIG-B field included in the HE MU PPDU may contain information about the configuration of the resource units (e.g., the division of the resource units) within a specific bandwidth on the frequency axis (e.g., 20 MHz). That is, the RA field can instruct the STA on the configuration of the resource units divided by the bandwidth for transmitting the HE MU PPDU in order to receive the PPDU. Information about the STA allocated (or specified) to each divided resource unit may be included in the user-specific field of EHT-SIG-B and transmitted to the STA. That is, the user-specific field may contain one or more user fields corresponding to each divided resource unit.

[0103] For example, among the multiple divided resource units, the user field corresponding to at least one resource unit used for data transmission may contain the recipient's or sender's AID, while the user fields corresponding to the remaining resource units not used for data transmission may contain a previously set Null STA ID.

[0104] For the sake of clarity, the terms frame or MAC frame may be used interchangeably with MPDU in this specification.

[0105] When a single wireless communication device communicates using multiple links, the communication efficiency of the wireless communication device can be increased. In this case, a link is a physical path and may be configured as a single wireless medium that can be used to transmit an MSDU (MAC service data unit). For example, if the frequency band of one link is being used by another wireless communication device, the wireless communication device can continue to communicate using another link. In this way, the wireless communication device can make effective use of multiple channels. Furthermore, when the wireless communication device communicates simultaneously using multiple links, the overall throughput can be increased. However, existing wireless LANs are defined on the premise that one wireless communication device uses one link. Therefore, a wireless LAN operation method for using multiple links is necessary. Referring to Figures 9 to 26, the wireless communication method for a wireless communication device using multiple links will be explained. First, Figure 9 will be used to explain a specific form of a wireless communication device using multiple links.

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

[0107] A multi-link device (MLD) may be defined for the wireless communication method using the multiple links described above. A multi-link device can represent a device having one or more affiliated stations. In specific embodiments, a multi-link device can represent a device having two or more affiliated stations. A multi-link device can also have interchangeable multi-link elements. A multi-link element contains information about one or more stations or one or more links. A multi-link element may include the multi-link setup element described later. In this case, the multi-link device may be a logical entity. Specifically, a multi-link device may have multiple affiliated stations. A multi-link device can be called an MLLE (multi-link logical entity) or an MLE (multi-link entity). A multi-link device may have one medium access control service access point (SAP) up to logical link control (LLC). An MLD may also have one MAC data service.

[0108] Multiple stations included in a multilink system can operate on multiple links. Furthermore, multiple stations included in a multilink system can operate on multiple channels. Specifically, multiple stations included in a multilink system can operate on different links or different channels. For example, multiple stations included in a multilink system can operate on different channels of 2.4GHz, 5GHz, and 6GHz.

[0109] The operation of a multilink device can be called multilink operation, MLD operation, or multi-band operation. Furthermore, if the station paired with the multilink device is an AP (Application Platform), the multilink device can be called an AP MLD (Application Platform Multilink). Conversely, if the station paired with the multilink device is a non-AP station, the multilink device can be called a non-AP MLD (Application Platform Multilink).

[0110] Figure 9 illustrates the communication operation between a non-AP MLD and an AP-MLD. Specifically, the non-AP MLD and AP-MLD communicate using three links each. The AP MLD includes the first AP (AP1), the second AP (AP2), and the third AP (AP3). The non-AP MLD includes the first non-AP STA (non-AP STA1), the second non-AP STA (non-AP STA2), and the third non-AP STA (non-AP STA3). The first AP (AP1) and the first non-AP STA (non-AP STA1) communicate via the first link (Link1). The second AP (AP2) and the second non-AP STA (non-AP STA2) communicate via the second link (Link2). The third AP (AP3) and the third non-AP STA (non-AP STA3) communicate via the third link (Link3).

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

[0112] Multilink configuration may be established through negotiations between peer stations. Specifically, multilink configuration may be performed through communication between stations without communication with the AP. Furthermore, multilink configuration may be established through any one of the links. For example, even if links 1 through 3 are configured via a multilink, the multilink configuration may be performed through link 1.

[0113] Furthermore, a mapping between TIDs (traffic identifiers) and links may be configured. Specifically, frames corresponding to a specific TID value may be exchanged only through pre-specified links. The mapping between TIDs and links may be configured in a directional-based manner. For example, if multiple links are configured between a first multilink device and a second multilink device, the first multilink device may be configured to send frames with a first TID to multiple first links, and the second multilink device may be configured to send frames with a second TID to the first links. Additionally, a default setting may exist for the mapping between TIDs and links. Specifically, if there are no additional settings in the multilink configuration, the multilink device can exchange frames corresponding to TIDs on each link according to the default setting. In this case, the default setting may be such that all TIDs are exchanged on any one link.

[0114] Let's explain TID in detail. TID is an ID used to classify traffic and data to support QoS (Quality of Service). TID may be used and assigned at layers higher than the MAC layer. TID can also indicate traffic category (TC) and traffic stream (TS). There may be 16 distinct TID values. For example, a TID may be specified as any one of 0 to 15. Different TID values ​​may be specified depending on the access policy, channel access, or medium access method. For example, when EDCA (enhanced distributed channel access) or HCAF (hybrid coordination function contention based channel access) is used, the TID value may be assigned in the range of 0 to 7. When EDCA is used, TID can indicate user priority (UP). In this case, UP may be specified by TC or TS. UP may be assigned at layers higher than MAC. Furthermore, when HCCA (HCF controlled channel access) or SPCA is used, the TID value may be assigned in the range of 8 to 15. When HCCA or SPCA is used, TID can represent TSID. Furthermore, when HEMM or SEMM is used, the TID value may be assigned in the range of 8 to 15. When HEMM or SEMM is used, TID can represent TSID.

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

[0116] As mentioned above, a TID may be mapped to each of multiple links. The mapping may specify which links can exchange traffic corresponding to a particular TID or AC. Additionally, TIDs or ACs that can be transmitted in different transmission directions within a link may be specified. As mentioned above, a default setting may exist for the mapping between TIDs and links. Specifically, in a multilink configuration where no additional settings are made, the multilink device can exchange frames corresponding to TIDs on each link according to the default setting. In this case, the default setting may be that all TIDs are exchanged on any one link. At any given time, any TID or AC may always be mapped to at least one link. Management frames and control frames may be transmitted on all links.

[0117] When a link is mapped to a TID or AC, only data frames corresponding to the TID or AC mapped to that link may be transmitted on that link. Therefore, when a link is mapped to a TID or AC, frames that do not correspond to a TID or AC not mapped to that link do not need to be transmitted on that link. When a link is mapped to a TID or AC, the ACK may also be transmitted based on the link to which the TID or AC is mapped. For example, a block ACK agreement may be determined based on the mapping between TIDs and links. Furthermore, in other specific embodiments, the mapping between TIDs and links may be determined based on a block ACK agreement. Specifically, a block ACK agreement may be set for a TID mapped to a particular link.

[0118] The aforementioned mapping of TIDs to links may ensure QoS. Specifically, a relatively small number of stations may be operational, or higher-priority ACs or TIDs may be mapped to links with good channel conditions. Furthermore, the aforementioned mapping of TIDs to links may enable stations to maintain a power-saving state for longer periods.

[0119] Figure 10 shows an example of a TID-to-link mapping method according to one embodiment of the present invention.

[0120] Referring to Figure 10, a mapping relationship between TID and links may exist, as explained in Figure 9. In this invention, the mapping relationship between TID and links can be called TID-to-link mapping, TID-to-link mapping, TID mapping, link mapping, etc. TID may be a traffic identifier. TID may also be an identifier used to classify traffic, data, etc., in order to support QoS (quality of service).

[0121] Furthermore, TID may be an ID used or assigned at a layer higher than the MAC layer. TID can represent TC (traffic categories) or TS (traffic streams). Also, TID can have 16 possible values, for example, it may be represented by a value from 0 to 15. In addition, individual TID values ​​can be used depending on the access policy or channel connection / medium access method. For example, when using EDCA (HCF (hybrid coordination function) linked channel connection, extended distributed channel connection), possible TID values ​​may be from 0 to 7. Also, when using EDCA, the TID value may represent UP (user priority), and the UP may relate to TC or TS. Also, UP may be a value assigned at a layer higher than MAC. Also, when using HCCA (HCF controlled channel access) or SPCA, possible TID values ​​may be from 8 to 15. Also, when using HCCA or SPCA, TID may represent TSID. Furthermore, when using HEMM or SEMM, the possible TID values ​​may be between 8 and 15. Also, when using HEMM or SEMM, the TID may represent the TSID.

[0122] Furthermore, a mapping relationship may exist between UP and access category (AC). AC may be a label that indicates a label or set of EDCA parameters for providing QoS in EDCA. The EDCA parameters or set of EDCA parameters may be used for channel coupling. AC may be used in QoS STA.

[0123] The value of AC may be set to one of AC_BK, AC_BE, AC_VI, or AC_VO. AC_BK, AC_BE, AC_VI, and AC_VO may represent background, best effort, video, and voice, respectively. Furthermore, AC_BK, AC_BE, AC_VI, and AC_VO can be subdivided. For example, AC_VI may be subdivided into AC_VI primary and AC_VI alternate. Similarly, AC_VO may be subdivided into AC_VO primary and AC_VO alternate. Additionally, UP values ​​or TID values ​​may be mapped to AC values. For example, UP values ​​or TID values ​​1, 2, 0, 3, 4, 5, 6, and 7 may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI, AC_VI, AC_VO, and AC_VO, respectively. Alternatively, UP values ​​or TID values ​​1, 2, 0, 3, 4, 5, 6, and 7 may be mapped to AC_BK, AC_BK, AC_BE, AC_BE, AC_VI alternate, AC_VI primary, AC_VO primary, and AC_VO alternate, respectively. Furthermore, UP values ​​or TID values ​​1, 2, 0, 3, 4, 5, 6, and 7 may have increasing priorities in that order. That is, 1 may have a lower priority and 7 may have a higher priority. Therefore, the priorities may be in the order of AC_BK, AC_BE, AC_VI, and AC_VO. Also, AC_BK, AC_BE, AC_VI, and AC_VO may correspond to ACI (AC index) 0, 1, 2, and 3, respectively.

[0124] Therefore, a relationship between TID and AC can exist. Thus, the TID-to-link mapping of the present invention may also be a mapping relationship between AC and the link. Furthermore, in the present invention, the mapping of TID may also mean that AC is mapped, and vice versa.

[0125] According to one embodiment of the present invention, there may be TIDs mapped to each link in a multi-link system. For example, there may be a mapping for which of the multiple links a particular TID or AC is permitted to be transmitted or received. Furthermore, such mappings may be defined individually for each direction in both directions of the link. Also, as mentioned above, there may be a default setting for the mapping between TIDs and links. For example, the mapping between TIDs and links may basically map all TIDs to a certain link. Also, according to one embodiment, at a specific point in time, a certain TID or AC may be mapped to at least one link. Furthermore, management frames or control frames may be transmitted on all links.

[0126] In this invention, data frames corresponding to TID or AC mapped to either direction of the link may be transmitted. Conversely, data frames corresponding to TID or AC that are not mapped to either direction of the link do not need to be transmitted.

[0127] According to one embodiment, TID-to-link mapping may also be applied to acknowledgments. For example, a block ack agreement may be based on TID-to-link mapping. Or, TID-to-link mapping may be based on a block ack agreement. For example, a block ack agreement may exist for a TID that has been TID-to-link mapped.

[0128] By performing TID-to-link mapping, it is possible to provide QoS services. For example, by mapping high-priority ACs and TIDs to links with good channel status or few STAs, it is possible to transmit data for those ACs and TIDs quickly. Alternatively, by performing TID-to-link mapping, it is possible to help STAs on a specific link power save (or enter a doze state).

[0129] Referring to Figure 10, an AP MLD containing AP1 and AP2 may exist. A Non-AP MLD containing STA1 and STA2 may also exist. Furthermore, the AP MLD may contain multiple links, namely Link1 and Link2. AP1 and STA1 may be associated via Link1, and AP2 and STA2 may be associated via Link2.

[0130] Therefore, Link1 may include a link that transmits from AP1 to STA1 and / or a link that transmits from STA1 to AP1, and Link2 may include a link that transmits from AP2 to STA2 and / or a link that transmits from STA2 to AP2. In this case, each link may be mapped to a TID and / or AC.

[0131] For example, all TIDs and all ACs may be mapped to the link from AP1 to STA1 on Link1, and to the link from STA1 to AP1 on Link1. On the other hand, only TIDs corresponding to AC_VO or AC_VO may be mapped to the link from STA2 to AP2 on Link2. Furthermore, only data for mapped TIDs and / or ACs can be transmitted on that link. Data for TIDs or ACs that are not mapped to a link cannot be transmitted on that link.

[0132] Figure 11 shows an example of the multi-link NAV setting operation according to one embodiment of the present invention.

[0133] The simultaneous transmit and receive (STR) operation of the MLD may be limited, and this may be related to the frequency spacing between multiple links operating in a multi-link configuration.

[0134] Therefore, according to the embodiment of the present invention, when the link spacing is m MHz, simultaneous transmission or reception is restricted, but when the link spacing is n MHz for n greater than m, simultaneous transmission or reception is not restricted. This embodiment may be intended to solve the problem of restrictions on simultaneous transmission or reception, and redundant explanations may be omitted. Furthermore, this embodiment can be applied to MLDs that do not support STR.

[0135] According to one embodiment of the present invention, duration information may be shared between links operating as multiple links. In one embodiment, the duration information may be TXOP duration information transmitted in the signaling field of the preamble. The signaling field may be the U-SIG field described above. Alternatively, the signaling field may be the HE-SIG-A field described above. In yet another embodiment, the duration information may be duration information indicated by the Duration / ID field included in the MAC header. In yet another embodiment, the duration information may be duration information indicated by the Length field (L Length field) included in the L-SIG field. According to one embodiment, the duration information indicated by the U-SIG field, HE-SIG-A, or Duration / ID field may be a value indicating the TXOP duration. According to one embodiment, the duration information indicated by the L-SIG field may be a value indicating the length of the PPDU (physical layer protocol data unit) containing the L-SIG field or the end of the PPDU containing the L-SIG field.

[0136] Furthermore, according to embodiments of the present invention, it is possible to restrict transmission or channel connection to a period based on period information shared between links. The method of restricting transmission or channel connection may include setting a NAV. Alternatively, the NAV can be reset to resume transmission or channel connection. In this case, the NAV may be an intra-BSS NAV. An intra-BSS NAV may be a NAV set by an intra-BSS frame (or PPDU). That is, an STA belonging to an MLD can set a NAV based on a frame (or PPDU) destined for another STA belonging to the MLD.

[0137] According to one embodiment of the present invention, an inter-link NAV may exist. The inter-link NAV may be a NAV used by the STAs of multiple links belonging to a certain MLD when operating with multiple links. For example, transmission on link 2 is not required based on the inter-link NAV set based on the period information received on link 1. Furthermore, the inter-link NAV can exist or be used for MLDs that do not support STR. For example, when an inter-link NAV is set, the MLD that set the inter-link NAV does not need to transmit or establish a channel connection on multiple links (or all links used by the MLD).

[0138] Furthermore, in addition to intra-BSS NAV, there may also be a basic NAV. Basic NAV may be a NAV configured by an inter-BSS frame (or PPDU), and basic NAV may also be configured by a frame (or PPDU) that cannot be determined as intra-BSS or inter-BSS.

[0139] Using an inter-link NAV separately may offer advantages in situations where NAV settings are updated compared to not using an inter-link NAV. For example, there may be situations where it is acceptable to reset a NAV set by another link. For instance, if an inter-link NAV is set based on a certain frame (or PPDU), but it is determined that the frame (or PPDU) is not destined for the same MLD, it may be acceptable to reset the set inter-link NAV. For example, if there are MLDs operating on Link 1 and Link 2, the NAV for Link 1 may be set based on frames received on Link 1. Subsequently, the NAV for Link 1 may be updated based on frames from Link 2. However, if the NAV for Link 2 is no longer needed, resetting the NAV for Link 1 would result in the loss of NAV information set based on frames received on Link 1. If an inter-link NAV is used in conjunction with the NAV for each link, the NAV for each link will be maintained even if the inter-link NAV is reset, thus resolving the above problem.

[0140] While the embodiments of the present invention focus on setting the NAV, the embodiments of the present invention are not limited thereto and can also be applied to instructing the physical layer to interrupt the channel connection or to instruct the channel state to be busy. Furthermore, the embodiments are not limited to resetting the NAV and can also be applied to instructing the physical layer to continue the channel connection or to instruct the channel state to be idle. In this case, primitives exchanged between the physical layer and the MAC layer may be used. Alternatively, primitives exchanged between one STA and another STA of the MLD may be used. Alternatively, primitives exchanged between one MAC layer and another MAC layer of the MLD may be used.

[0141] According to an embodiment of the present invention, when an STA belonging to an MLD begins receiving a PPDU, other STAs belonging to the MLD may have to terminate their channel connection. As mentioned above, the channel connection may be terminated based on the received period information, but due to the position of the field containing the period information or the time required for decoding, etc., there may be a time lag between the start of PPDU reception and the acquisition of the period information. Therefore, accessing the channel and starting transmission during this time may lead to the aforementioned problem. For this reason, according to one embodiment of the present invention, an STA of an MLD can suspend its channel connection from the moment other STAs of the MLD begin receiving. Furthermore, the channel connection can be resumed after confirming that the frame received after other STAs of the MLD have started receiving is not destined for those other STAs.

[0142] Figure 12 shows yet another example of the multi-link NAV configuration operation according to one embodiment of the present invention.

[0143] Figure 12 provides a detailed explanation of the specific method described in Figure 11, and redundant explanations may be omitted.

[0144] As mentioned above, based on a frame or PPDU received by an STA belonging to the same MLD, another STA belonging to the same MLD can cancel or resume channel connection or transmission. In this invention, canceling channel connection or transmission may include actions such as setting (updating) the NAV, determining the channel is busy, or canceling CCA. Resumeing channel connection or transmission may include actions such as resetting the NAV, canceling the NAV setting, determining the channel is idle, or performing CCA. In the following, such actions can be instructed as canceling and resuming channel connection. Furthermore, in the following explanation, it can be assumed that STA1 and STA2 belong to the MLD, and that STA1 and STA2 operate on Link1 and Link2, respectively. Frames and PPDUs can also be instructed in a mutually compatible manner. In addition, the NAV in this case may be an intra-BSS NAV or an inter-link NAV, as explained in Figure 11.

[0145] According to an embodiment of the present invention, when STA1 begins receiving frames, STA2 may interrupt the channel connection. Furthermore, when STA1 obtains duration information from the L-SIG, STA2 may maintain the interrupted channel connection state. In this case, STA2 can determine that the interrupted channel connection state will last until the end of the frame received by STA1. Also, if STA1 is unable to decode the L-SIG (i.e., if it is an invalid L-SIG), STA2 can resume the channel connection.

[0146] Furthermore, STA1 can receive the TXOP duration and BSS color from the U-SIG of the frame it receives. If the received BSS color indicates intra-BSS, or if the BSS color is the BSS color corresponding to STA1, the channel connection can be interrupted. In one embodiment, the period for which the channel connection is interrupted at this time may be until the end of the received frame. In this case, there is an advantage in that the channel connection can be started sooner after the end of the received frame. In another embodiment, the period for which the channel connection is interrupted at this time may be the TXOP duration. In this case, the duration of the interrupted channel connection may be updated based on the L-SIG. In this case, there is an advantage in that the sequence following the received frame can be better protected.

[0147] Alternatively, STA1 may have received the TXOP duration and BSS color from the U-SIG of the frame it receives, and the received BSS color may indicate that it is not an intra-BSS, or the BSS color may not be the BSS color corresponding to STA1. Or, STA1 may have failed to successfully decode the U-SIG. In such cases, STA2 can resume the channel connection.

[0148] Alternatively, STA2 can resume the channel connection if the information obtained from the U-SIG of a frame received by STA1 indicates that the frame is one that STA1 did not receive. For example, STA2 can resume the channel connection if the PHY identifier obtained from the U-SIG is an ID that corresponds to a future standard or an ID that is not recognized.

[0149] Furthermore, although the case of receiving a U-SIG has been described, the same embodiment can also be applied when receiving an HE PPDU or an HE-SIG-A. For example, HE-SIG-A may include TXOP duration and BSS color, and therefore the operation described above can be performed.

[0150] Additionally, STA1 may receive an STA-ID from the EHT-SIG of the frame it receives. If the received STA-ID is the indicator that STA1 should receive, for example, if the STA-ID indicates STA1, the group to which STA1 belongs, or broadcast, STA2 can maintain the state of interrupted channel connection.

[0151] Alternatively, STA1 may receive the STA-ID from the EHT-SIG of the frame it receives. If the received STA-ID is an indicator that does not correspond to STA1, for example, if the STA-ID does not indicate an indicator that corresponds to STA1, if the STA-ID does not indicate a group to which STA1 belonged, or if the STA-ID does not indicate broadcast, STA2 can resume the channel connection. Alternatively, STA2 can also resume the channel connection if STA1 is unable to successfully decode the EHT-SIG.

[0152] Furthermore, although the case of receiving EHT-SIG has been described, the same embodiment can also be applied when receiving HE PPDU or HE-SIG-B. For example, HE-SIG-B may include STA-ID, and therefore the operation described above can be performed.

[0153] Furthermore, STA2 may receive the MAC header of the frame that STA1 receives. If the RA (receiver address) or DA (destination address) contained in the received MAC header indicates a value that STA1 should receive—for example, if the RA or DA indicates STA1, the group to which STA1 belongs, or if the STA-ID indicates broadcast—STA2 can maintain a state of interrupted channel connection. In this case, the duration of the interrupted channel access is determined based on the duration information contained in the received MAC header. More specifically, the duration of the interrupted channel access is determined based on the duration information indicated by the Duration / ID field contained in the received MAC header.

[0154] Additionally, STA2 may have received the MAC header of the frame that STA1 is receiving. If the RA or DA included in the received MAC header is an indicator that does not correspond to STA1—for example, if the RA or DA does not indicate an indicator that corresponds to STA1, does not indicate the group to which STA1 belongs, or does not indicate broadcast—STA2 can resume the channel connection. Alternatively, STA1 may not have received all MAC headers. For example, STA1 may fail to receive all MPDUs included in A-MPDU. In this case, STA2 can resume the channel connection.

[0155] The channel connection interruption and resumption described in Figure 12 may be performed in the order in which frames (or PPDUs) are decoded sequentially as STA1 begins receiving and decoding them. The decoding order can be based on the PPDU format, frame format, etc. For example, L-SIG, U-SIG, EHT-SIG, MAC header can be decoded in that order (for EHT PPDU). Or, L-SIG, HE-SIG-A, MAC header can be decoded in that order (for HE SU PPDU and HE TB PPDU). Or, L-SIG, HE-SIG-A, HE-SIG-B, MAC header can be decoded in that order (for HE MU PPDU). Or, L-SIG, MAC header can be decoded in that order (for 11a / g PPDU).

[0156] According to embodiments of the present invention, the aforementioned STA-ID may be a value indicating the intended recipient of the PPDU or RU (resource unit). The STA-ID may also be included in the EHT-SIG field or HE-SIG-B field, etc. Furthermore, the STA-ID can represent a value corresponding to a single STA. For example, when multiple STAs are included in the MLD, the STA-ID can represent a value corresponding to one of the multiple STAs. The STA-ID may also be a value based on the AID or MAC address of the STA.

[0157] Figure 13 shows an example of a BSS classification and operation based thereon according to one embodiment of the present invention.

[0158] According to one embodiment of the present invention, an STA can classify (or determine) a BSS based on a received frame or received PPDU. Classifying a BSS may include the operation of determining whether the received frame or received PPDU belongs to the BSS to which the classifying STA belongs. Alternatively, classifying a BSS may mean determining whether the received frame or received PPDU was transmitted from the BSS to which the classifying STA belongs. Furthermore, classifying a BSS may include the operation of determining whether the received frame or received PPDU belongs to a BSS to which the classifying STA does not belong. Alternatively, classifying a BSS may mean determining whether the received frame or received PPDU was transmitted from the BSS to which the classifying STA does not belong. Furthermore, classifying a BSS may include the operation of determining which BSS the received frame or received PPDU belongs. Alternatively, classifying a BSS may mean determining which BSS the received frame or received PPDU was transmitted from. According to one embodiment of the present invention, a BSS to which a classified STA belongs can be called an intra-BSS. Alternatively, a BSS that includes a BSS to which a classified STA belongs can be called an intra-BSS. Furthermore, a BSS that is not an intra-BSS can be called an inter-BSS. Alternatively, a BSS that is not an intra-BSS may be an inter-BSS or an unclassified BSS. Alternatively, an inter-BSS may include an unclassified BSS. Furthermore, a BSS to which a classified STA does not belong can be called an inter-BSS.

[0159] According to one embodiment, if a received frame or PPDU is determined to be an intra-BSS or to have been transmitted from an intra-BSS, the received frame or PPDU can be referred to as an intra-BSS frame and an intra-BSS PPDU, respectively. Furthermore, if a received frame or PPDU is determined to be an inter-BSS or to have been transmitted from an inter-BSS, the received frame or PPDU can be referred to as an inter-BSS frame and an inter-BSS PPDU, respectively. Additionally, a PPDU containing an intra-BSS frame may be an intra-BSS PPDU. Similarly, a PPDU containing an inter-BSS frame may be an inter-BSS PPDU.

[0160] According to one embodiment of the present invention, BSS can be classified based on one or more BSS classification conditions. For example, BSS can be classified based on whether or not at least one of the one or more BSS classification conditions is met.

[0161] The BSS classification conditions may include conditions based on the BSS color. The BSS color may be an identifier for the BSS. The BSS color may also be included in the PPDU preamble, more specifically in the signaling field (e.g., the HE-SIG-A field, U-SIG field, or VHT-SIG-A field). The BSS color may also be included in the TXVECTOR transmitted from the sender's MAC layer to the PHY layer. The BSS color may also be included in the RXVECTOR transmitted from the receiver's PHY layer to the MAC layer. The parameters included in the TXVECTOR and RXVECTOR can be called TXVECTOR parameters and RXVECTOR parameters, respectively. The BSS color may also be included in the TXVECTOR parameters or RXVECTOR parameters. Furthermore, the AP can inform the STA of the BSS color it has set. According to one embodiment, the BSS can be classified based on the BSS color included in the received PPDU. If the BSS color included in the PPDU received by the STA is different from the BSS color of the BSS corresponding to the STA, the received PPDU can be classified as an inter-BSS PPDU. Alternatively, if the BSS color included in the PPDU received by the STA is different from the BSS color of the BSS corresponding to the STA, and its value is not 0, the received PPDU can be classified as an inter-BSS PPDU. Furthermore, if the BSS color included in the PPDU received by the STA is the same as the BSS color of the BSS corresponding to the STA, the received PPDU can be classified as an intra-BSS PPDU.

[0162] The BSS classification conditions may include conditions based on the MAC address. The MAC address may be included in the MAC header of the frame. The MAC address may also include RA (receiver address), TA (transmitter address), BSSID, SA (source address), DA (destination address), etc. According to one embodiment, BSS can be classified based on the MAC address included in the received frame. If the MAC address included in the received frame is different from the BSSID of a BSS corresponding to an STA, the received frame can be classified as an inter-BSS frame. More specifically, if all of the MAC addresses included in the received frame are different from the BSSIDs of BSSs corresponding to STA, the received frame can be classified as an inter-BSS frame. Also, if the MAC address included in the received frame is the same as the BSSID of a BSS corresponding to an STA, the received frame can be classified as an intra-BSS frame. More specifically, if at least one of the MAC addresses included in the received frame is the same as the BSSID of a BSS corresponding to an STA, the received frame can be classified as an intra-BSS frame.

[0163] The aforementioned BSS may include a BSS to which the STA is associated. Furthermore, the aforementioned BSS may include a BSS included in the same multiple BSSID set as the BSS to which the STA is associated. Also, the aforementioned BSS may include a BSS included in the same co-hosted BSSID set as the BSS to which the STA is associated. Furthermore, information about one or more BSSs included in the same multiple BSSID set or the same co-hosted BSSID set may be transmitted through a single frame.

[0164] The aforementioned BSS classification conditions may include conditions based on the Partial AID field value included in the VHT PPDU. The Partial AID field may be included in the preamble of the VHT PPDU. Alternatively, the Partial AID field may be included in the VHT-SIG-A field included in the VHT PPDU. According to one embodiment, the Partial AID field can represent a portion of the BSS color. For example, when using the partial BSS color function, the Partial AID field can represent a portion of the BSS color. Or, when using an AID assignment rule, the Partial AID field can represent a portion of the BSS color. The AID assignment rule may be a method of assigning AIDs based on the BSS color. Furthermore, if the Group ID field included in the VHT-SIG-A field of the VHT PPDU is already set to a value (for example, if the Group ID field is set to 63), the Partial AID field can represent a portion of the BSS color. According to one embodiment, when the Partial AID field of a received PPDU represents a part of the BSS color, if the value of the received Partial AID field differs from the part of the BSS color corresponding to the received STA, the received PPDU can be classified as an inter-BSS PPDU.

[0165] Furthermore, if the Partial AID field of a received PPDU indicates a part of the BSS color, and the received Partial AID field value is the same as the part of the BSS color corresponding to the received STA, the received PPDU can be classified as an intra-BSS PPDU. In this case, the part of the BSS color can be the 4LSBs of the BSS color. In another embodiment, the Partial AID field can indicate a part of the BSSID. For example, if the Group ID field included in the VHT-SIG-A field of a VHT PPDU is already set to a value (for example, if the Group ID field is set to 0), the Partial AID field can indicate a part of the BSSID. In one embodiment, if the Partial AID field of a received PPDU indicates a part of the BSSID, and the received Partial AID field value is different from the part of the BSSID corresponding to the received STA, the received PPDU can be classified as an inter-BSS PPDU. Furthermore, if the Partial AID field of the received PPDU indicates a part of the BSSID, and the received Partial AID field value is the same as the part of the BSSID corresponding to the received STA, the received PPDU can be classified as an intra-BSS PPDU. In this case, the part of the BSSID can be the 9 MSBs of the BSSID. The Partial AID field value may be included in the TXVECTOR parameter PARTIAL_AID or the RXVECTOR parameter PARTIAL_AID. The Group ID field value may be included in the TXVECTOR parameter GROUP_ID or the RXVECTOR parameter GROUP_ID.

[0166] The BSS classification conditions may include conditions for the AP to receive PPDUs that meet already set conditions. For example, the PPDUs that meet the already set conditions may include downlink PPDUs. According to one embodiment, the downlink PPDU may include a VHT MU PPDU. The downlink PPDU may also include a PPDU with signaling indicating whether it is an uplink or downlink set to a value that has already been set. The signaling indicating whether it is an uplink or downlink may be included in the signaling field of the HE PPDU. Alternatively, the signaling indicating whether it is an uplink or downlink may be included in the U-SIG. The U-SIG may be included in the preamble of the EHT PPDU or a PPDU after the EHT standard.

[0167] Furthermore, there may be cases where a PPDU cannot be classified as either intra-BSS PPDU or inter-BSS PPDU. For example, if a PPDU does not meet either of the aforementioned criteria for classification as intra-BSS PPDU or inter-BSS PPDU, it cannot be classified as either intra-BSS PPDU or inter-BSS PPDU.

[0168] Furthermore, when classifying a BSS, if the classification results based on multiple conditions do not match, it is possible to determine the final result based on the previously set conditions. For example, if the result based on the BSS color condition does not match the result based on the MAC address condition, the result based on the MAC address condition can take precedence, or the result based on the MAC address condition can be determined as the final result. Alternatively, if both the conditions for classifying as intra-BSS PPDU and the conditions for classifying as inter-BSS PPDU are met, it can be classified as intra-BSS PPDU.

[0169] According to one embodiment of the present invention, the STA can perform operations based on the classified BSS. Operations based on the classified BSS may include intra-PPDU power saving operations. Intra-PPDU power saving operations may be power saving operations based on the received PPDU. Intra-PPDU power saving operations can be performed when already set conditions are met. The already set conditions may include conditions for classifying the received PPDU into an intra-BSS PPDU. The already set conditions may also include conditions for the intended receiver of the received PPDU not to be the STA that received the PPDU. For example, if the ID or address included in the PPDU does not correspond to the STA that received the PPDU, the intended receiver of the PPDU does not have to be the STA that received the PPDU. The ID may be included in the PPDU preamble. For example, the ID may be the STA_ID included in the PPDU preamble. The STA_ID may also be included in the HE MU PPDU or EHT PPDU. The address may be the MAC address mentioned above. Furthermore, if the signaling in the received PPDU indicating whether it is an uplink or downlink indicates an uplink, the intended recipient of the PPDU does not have to be the STA that received the PPDU. Also, if the settings of the received PPDU are set to one that is not supported by the STA that received the PPDU, the intended recipient of the PPDU does not have to be the STA that received the PPDU. The settings of the received PPDU may include the PPDU's MCS, the number of spatial streams, the channel width, etc. Also, if the settings of the received PPDU are not supported by the STA that received the PPDU, the PHY-RXEND.indication(UnsupportedRate)primitive may be received. Also, if the received PPDU is in an already configured format, the intended recipient of the PPDU does not have to be the STA that received the PPDU. The already configured format may include TB PPDU.A TB PPDU may include an HE TB PPDU and an EHT TB PPDU. A TB PPDU may also be a PPDU transmitted as a response to a triggering frame. The triggering frame may include a trigger frame. The triggering frame may include a frame containing triggering information. The triggering information may be contained in the MAC header, for example, the A-control field. The triggering information or information contained in the trigger frame may include the length of the response PPDU, the RU used in the response, the PHY configuration used in the response, the MAC configuration, etc. The intra-PPDU power saving operation may be an operation that enters a doze state until the end of the received PPDU. In another embodiment, if the STA determines that the intended recipient of the received PPDU or frame is not the STA, the reception or decoding of the PPDU or frame may be interrupted.

[0170] The actions based on the classified BSS may include the action of setting (or updating) the NAV. According to one embodiment, the STA can operate one or more NAVs. Furthermore, when the STA receives a PPDU or frame, it can set up a NAV that corresponds to the BSS classified based on the received PPDU or frame. For example, an intra-BSS NAV may be a NAV that corresponds to an intra-BSS PPDU. Also, a basic NAV may be a NAV that corresponds to a PPDU that is not an intra-BSS PPDU. Or, a basic NAV may be a NAV that corresponds to an inter-BSS PPDU. Furthermore, when setting up a NAV based on a received PPDU or frame, it is possible to use the duration information contained in the received PPDU or frame. The duration information may include a TXOP. A TXOP can mean the value contained in the TXOP field. The TXOP field may be included in the PPDU preamble. For example, the TXOP field may be included in the HE-SIG-A field of an HE PPDU. Alternatively, the TXOP field may be included in the U-SIG field of the EHT PPDU or a post-EHT standard PPDU. Furthermore, the duration information may be included in the MAC header. For example, the duration information may be included in the Duration / ID field in the MAC header.

[0171] The classified BSS-based operation may include a spatial reuse operation. The classified BSS-based operation may also include a channel connection operation. The spatial reuse operation may be a channel connection operation. When the STA receives a PPDU or frame, if the already set conditions are met, a spatial reuse operation can be performed. The already set conditions may include the condition that the received PPDU or frame is an inter-BSS. The already set conditions may also include the condition that the signal strength of the received PPDU or frame is less than a threshold. For example, the threshold may be variable. The threshold may also be a threshold for OBSS PD-based spatial reuse operation. The threshold may also be a value greater than or equal to the CCA threshold. The threshold may also be a value based on the power to be transmitted. The spatial reuse operation may include the operation of transmitting the PPDU. The spatial reuse operation may also include the operation of resetting the PHY. For example, the action of resetting the PHY may be the action of issuing a PHY-CCARESET.request primitive. Also, the spatial reuse action may include the action of not setting the NAV based on the received PPDU or received frame. If the STA performs the spatial reuse action, it may be possible for the STA to transmit a PPDU while the received PPDU or received frame is being transmitted or received.

[0172] Referring to Figure 13, BSS A and BSS B may exist, and BSS A and BSS B may be different BSSs from each other. Also, BSS A and BSS B may be inter-BSS. That is, a PPDU or frame transmitted by an STA associated with BSS A on BSS B may be classified as an inter-BSS PPDU or an inter-BSS frame. Also, there may be STA1 and STA2 belonging to BSS A (or associated with an AP operating BSS A). There may be STA3 and STA4 belonging to BSS B (or associated with an AP operating BSS B). Referring to Figure 13, STA1 can transmit a PPDU. Also, the PPDU transmitted by STA1 may contain information about the BSS. For example, the information about the BSS may be the information used to classify the BSS as described above. Also, the PPDU transmitted by STA1 may contain duration information.

[0173] STA2 can receive the PPDU transmitted by STA1 and classify the BSS for this PPDU. Since both STA2 and STA1 belong to BSS A, the PPDU received by STA2 may be classified as an intra-BSS PPDU. Furthermore, the PPDU received by STA2 may be a UL PPDU or a PPDU that is not intended for the STA. Therefore, according to the embodiment described above, STA2 can perform intra-PPDU power saving. Referring to Figure 13, STA2 may enter a doze state until the end of the received PPDU. Also, STA2 can set the NAV based on the Duration information contained in the received PPDU. Since STA2 classified the received PPDU as an intra-BSS PPDU, it is possible to set the intra-BSS NAV.

[0174] STA3 can receive the PPDU transmitted by STA1 and classify the BSS for this PPDU. Since STA3 and STA1 belong to BSS B and BSS A respectively, the PPDU received by STA3 can be classified as an inter-BSS PPDU. Furthermore, STA3 can set the NAV based on the Duration information contained in the received PPDU. Since STA3 has classified the received PPDU as an inter-BSS PPDU, it is possible to set the basic NAV.

[0175] STA4 can receive the PPDU transmitted by STA1 and classify the BSS for this PPDU. Since STA4 and STA1 belong to BSS B and BSS A respectively, the PPDU received by STA4 may be classified as an inter-BSS PPDU. Furthermore, the signal strength of the PPDU received by STA4 may be less than the threshold. Therefore, since the PPDU received by STA4 is classified as an inter-BSS PPDU and the signal strength of the PPDU received by STA4 is less than the threshold, STA4 can perform a spatial reuse operation. Consequently, STA4 can perform channel connection, backoff procedure, and start transmitting. For example, STA4 may start transmitting before the PPDU transmitted by STA1 has finished.

[0176] Figure 14 shows a wireless LAN function according to one embodiment of the present invention.

[0177] Referring to Figure 14, one standard wireless LAN may include the functions of other standard wireless LANs. Or, if it is one standard wireless LAN, it may also be another standard wireless LAN. Here, wireless LAN can mean STA. Furthermore, here, wireless LAN may mean MLD including STA. For example, a wireless LAN standard may include the functions of previous generations of standards and include additional functions. For example, HT STA may also be OFDM PHY STA. Also, HT STA may perform additional functions in addition to the functions of OFDM PHY STA. For example, VHT STA may also be HT STA. Also, VHT STA may perform additional functions in addition to the functions of HT STA. For example, HE STA may also be VHT STA. Also, HE STA may perform additional functions in addition to the functions of VHT STA. Also, EHT STA may also be HE STA. Also, EHT STA may perform additional functions in addition to the functions of HE STA. Furthermore, there may be standards after the EHT standard. In this invention, standards after the EHT standard can be called NEXT standards, and STAs that conform to the NEXT standard can be called NEXT STAs. NEXT STAs can also be EHT STAs. Furthermore, NEXT STAs can perform additional functions in addition to those of EHT STAs.

[0178] Figure 14 is a diagram showing the relationships between STAs of each standard. Referring to Figure 14, if it is EHT STA, it can be HE STA, VHT STA, HT STA, and OFDM PHY STA. Similarly, if it is NEXT STA, it can be EHT STA, HE STA, VHT STA, HT STA, and OFDM PHY STA.

[0179] Figure 15 shows an uplink (UL) multi-user (MU) operation according to one embodiment of the present invention.

[0180] Referring to Figure 15, an AP can instruct at least one STA to send a PPDU through a specific frame (e.g., a triggering frame), and at least one STA can simultaneously send PPDUs of the same or different formats based on the specific frame sent from the AP.

[0181] Specifically, as shown in Figure 15, a frame that solicits or triggers multi-user (MU) transmission may be transmitted, and based on such a frame, one or more STAs may transmit or respond to such a frame. In this case, when one or more STAs transmit a response to the frame, one or more STAs may simultaneously and immediately respond based on the frame, and the transmission of the response to the frame may begin after SIFS from the end of the PPDU containing the frame. For example, if the frame solicits an immediate response, one or more STAs may immediately transmit a response to the frame. A frame that solicits or triggers transmission to one or more STAs may be a trigger frame or a frame whose MAC header contains information that instructs or triggers uplink transmission to one or more STAs. In this case, the frame may contain information in its MAC header that triggers or instructs uplink transmission to only one STA (e.g., a TRS control subfield).

[0182] For example, information that instructs or triggers an uplink transmission included in the MAC header may be a triggered response scheduling (TRS) or TRS control subfield contained in the HT control field, control subfield, or A-control subfield.

[0183] Frames to instruct or trigger uplink transmission may be sent by the AP, and if the frame to instruct or trigger uplink transmission is a trigger frame, the response thereto may be sent in trigger-based PPDU (TB PPDU) format. In this case, TB PPDU may include not only the HE TB PPDU and EHT TB PPDU mentioned above, but also NEXT TB PPDU, which may be defined in the following standard.

[0184] An HE TB PPDU may consist of a preamble, data, and a packet extension (PE), and the preamble may include L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, HE-STF, and HE-LTF in that order.

[0185] EHT TB PPDU and NEXT TB PPDU may also consist of a preamble, data, and PE, and the preamble of EHT TB PPDU and NEXT TB PPDU may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, (EHT- / NEXT-)STF, and (EHT- / NEXT-)LTF in that order.

[0186] A frame that instructs or triggers one or more STAs to transmit a PPDU may contain information necessary for one or more STAs to transmit a TB PPDU. For example, if the type subfield included in the frame is "01" (B3 B2) and the subtype subfield is "0010" (B7 B6 B5 B4), then a frame containing such a type subfield and subtype subfield may be a trigger frame that is also a control frame.

[0187] If multiple STAs are instructed or triggered to respond with a TB PPDU, and the formats of the PPDUs sent by the multiple STAs differ from each other, the AP that instructed or triggered the response may have difficulty receiving the PPDUs sent from the multiple STAs. Alternatively, if the information contained in the preambles of the PPDUs sent by the multiple STAs differs from each other due to their formats, the AP that instructed or triggered the response may have difficulty receiving the PPDUs sent from the multiple STAs.

[0188] Therefore, to solve this problem, when multiple STAs respond to an AP frame, the format of the responding PPDU and / or the type of information included in the PPDU preamble may be set to be the same. For example, when multiple STAs transmit HE TB PPDUs as responses to an AP frame, the AP may transmit information such that the information included in L-STF, L-LTF, L-SIG, RL-SIG, and HE-SIG-A is the same, or an agreement may be made regarding the information included in the HE TB PPDU, so that the AP can successfully receive the preambles transmitted by multiple STAs. However, if HE TB PPDU, EHT TB PPDU, and NEXT TB PPDU are transmitted simultaneously on overlapping subbands, the TB PPDU formats may differ from each other, which can cause problems for the AP in receiving them.

[0189] According to embodiments of the present invention, a HE STA can transmit HE TB PPDUs. An EHT STA can transmit EHT TB PPDUs or HE TB PPDUs. A NEXT STA can transmit NEXT TB PPDUs, EHT TB PPDUs, or HE TB PPDUs. This is because, as illustrated in Figure 10, a standard STA may include the functionality of a previous standard.

[0190] As shown in Figure 15, when an AP sends a frame to HE STA and EHT STA to schedule the transmission of a TB PPDU, and uses the frame to instruct or trigger the transmission of a TB PPDU, there may be no precise instructions or protocol for the TB PPDU format. In this case, the HE STA may send an HE TB PPDU in response to the frame, and the EHT STA may respond with an EHT TB PPDU or an HE TB PPDU. In this case, the AP may have difficulty receiving the TB PPDUs sent by these STAs, and the AP may not be able to successfully receive TB PPDUs from multiple STAs, resulting in the medium being occupied despite unsuccessful transmission, thus reducing the transmission opportunities for other STAs.

[0191] In the present invention, giving instructions to the STA means instructing a response from the STA, and the terms "trigger" and "instruction" may be used interchangeably.

[0192] Furthermore, the HE trigger frame, EHT trigger frame, and NEXT trigger frame may be trigger frames as defined in the HE, EHT, and NEXT standards, respectively. Also, in this invention, the HE TRS, EHT TRS, and NEXT TRS may be TRS as defined in the HE, EHT, and NEXT standards, respectively.

[0193] Figure 16 shows a trigger frame format according to one embodiment of the present invention.

[0194] Figure 16(a) shows the trigger frame format, and Figures 16(b) and (c) show the common info (information) field and the user information field, respectively, which are fields included in the trigger frame.

[0195] Referring to Figure 16(a), the trigger MAC header of a frame may include a Frame Control field, a Duration field, and an Address field, and may also include a Common Information field and a User Information List field. The Address field may also include a Resource Allocation (RA) field and a Transmitter Address (TA) field.

[0196] The common information field may contain information that is common to all STAs indicated by the trigger frame. Figure 12(b) shows an example of a common information field.

[0197] The user information list field may contain zero or more user information fields, and the user information list field of a trigger frame, excluding certain types of trigger frames, may contain one or more user information fields. Figure 16(c) shows an example of a user information field.

[0198] The trigger frame may further include a padding field and a frame check sequence (FCS) field. The padding field may be used to increase the length of the frame to allow time for the STA receiving the trigger frame to prepare a response to the trigger frame, and may be selectively included in the trigger frame.

[0199] Referring to Figure 16(b), the common information field may include a trigger type subfield. The trigger type subfield may be used to identify a trigger frame variant. Alternatively, the type of trigger frame may be indicated based on the value of the trigger frame subfield. Furthermore, the information and length of the trigger dependent common information subfield and the trigger dependent user information subfield shown in Figure 12 may be determined based on the trigger type subfield. For example, the trigger type subfield may be indicated by bits B0 to B3 of the common information field.

[0200] The common information field may include an Uplink (UL) length subfield. The UL length subfield may contain information about the length of the TB PPDU, which is a response to a trigger frame, and may contain information about the length of the frame responding to the trigger frame. The UL length subfield can also indicate a value to be included in the length subfield of the L-SIG of the TB PPDU responding to the trigger frame. Therefore, an STA that receives a trigger frame and responds with a TB PPDU can set the value of the length subfield included in the L-SIG of the TB PPDU based on the value of the UL length subfield included in the received trigger frame. Specifically, an STA responding with a TB PPDU can set the length subfield included in the L-SIG of the TB PPDU to the value of the UL length subfield included in the received trigger frame. For example, an STA can set the length subfield included in the L-SIG of the TB PPDU and transmit the TB PPDU based on the values ​​of bits B4 to B15 of the common information field indicating the UL length subfield.

[0201] The common information field may also include an uplink bandwidth subfield (UL Bandwidth (BW) subfield). The UL BW subfield can indicate the BW value included in the signaling field of the TB PPDU responding to the trigger frame (e.g., HE-SIG-A or U-SIG), and can indicate the maximum BW of the TB PPDU transmitted as a response to the trigger frame. Therefore, the STA can set the BW value included in the signaling field of the TB PPDU based on the value of the UL BW subfield included in the trigger frame.

[0202] Furthermore, the common information field may include information contained in the signaling field of the TB PPDU, which is the response to the trigger frame. Therefore, after receiving the trigger frame, the STA can set the information contained in the TB PPDU based on the information contained in the trigger frame.

[0203] Referring to Figure 16(c), the user information field may include an AID12 subfield. The AID12 subfield may be used to indicate the intended recipient of the user information field containing the AID12 subfield, or the function of the user information field. Therefore, the AID12 subfield can also play a role in indicating the intended recipient of the trigger frame containing the AID12 subfield, or the function of the trigger frame. For example, if the value of the AID12 subfield is already set, the user information field can indicate an RA-RU (Random Access Resource Unit). That is, an already set value of the AID12 subfield can indicate that the user information field indicates an RA-RU. Specifically, if the value of the AID12 subfield is "0", the user information field can indicate an RA-RU for associated STAs. For example, if the value of the AID12 subfield is "0", the user information field may indicate an RA-RU for an associated STA, and if the value of the AID12 subfield is "2045", the user information field may indicate an RA-RU for an unassociated STA. The STA corresponding to the STA ID (e.g., AID (association ID)) indicated by the value of the AID12 subfield may respond with a user information field containing the AID12 subfield or a trigger frame containing the AID subfield. For example, the AID12 subfield may indicate the AID or the 12 LSBs of the AID. The STA corresponding to the value indicated by the AID12 subfield may send a TB PPDU as a response to the received trigger frame. In this case, the value of the AID12 subfield may be in the range of "1" to "2007" (including 1 and 2007), and if the AID12 subfield is already set to a value (e.g., "2046"), the RU corresponding to the already set value of the AID12 subfield may not be assigned to any STA.Additionally, if the AID subfield is already set to a value (for example, "4095"), that already set value can indicate when padding for the trigger frame should begin.

[0204] The information in a user information field that includes the AID12 subfield may be the information corresponding to the STA indicated by the AID12 subfield. For example, the Resource Unit (RU) Allocation subfield can indicate the size and location of the RU. In this case, the value of the RU Allocation subfield of the user information field that includes the AID12 subfield may be the information corresponding to the STA indicated by the AID12 subfield. That is, the RU indicated by the RU Allocation subfield of the AID12 subfield may be the RU assigned to the STA indicated by the AID12 subfield.

[0205] Furthermore, the user information field can specify the coding method (UL FEC coding type), modulation method (UL HE-MCS, UL DCM), and power (UL Target RSSI) for generating the TB PPDU sent as a response to the trigger frame.

[0206] Figure 17 shows a method for specifying a triggered-based (TB) PPDU format according to one embodiment of the present invention.

[0207] Referring to Figure 17, a single STA can selectively transmit PPDUs in different formats based on instructions from a triggering frame that instructs the transmission of a PPDU.

[0208] Specifically, an EHT STA can selectively transmit EHT TB PPDUs in addition to legacy PPDUs (e.g., HE TB PPDUs), and a NEXT STA can selectively transmit HE TB PPDUs, EHT TB PPDUs, and / or NEXT TB PPDUs. In this case, STAs to which multiple standards apply can be individually scheduled in a single frame or PPDU. This method can be advantageous in a wireless LAN where multiple STAs to which multiple standards apply share resources. For example, an HE STA (an HE STA other than an EHT STA) and an EHT STA can respond with an HE TB PPDU in a single frame. That is, a non-AP STA can send a triggering frame and instruct the EHT STA, in addition to the HE STA, to transmit an HE TB PPDU.

[0209] Furthermore, information for selecting the TB PPDU format may be included in the triggering frame, the TRS, the PPDU containing the triggering frame, or the PPDU containing the TRS control subfield. That is, the AP STA sends the information for selecting the TB PPDU format in the triggering frame to at least one non-AP STA, and the non-AP STA can select the format of the PPDU to respond based on the information included in the received triggering frame. The at least one non-AP STA can then send the PPDU to the AP based on the selected format.

[0210] Information regarding the format of the PPDU (TB PPDU format), which is the response to such a triggering frame, may exist at the MAC level. A trigger frame, which is one of the triggering frames, may be distinguished into HE trigger frames, EHT trigger frames, and NEXT trigger frames, and the responses to each trigger frame may be distinguished into HE TB PPDU, EHT TB PPDU, and NEXT TB PPDU.

[0211] Furthermore, distinguishing trigger frames into HE trigger frames, EHT trigger frames, and NEXT trigger frames may be equivalent to classifying the TB PPDU format, which is the response to the trigger frame, into HE TB PPDU, EHT TB PPDU, and NEXT TB PPDU, respectively.

[0212] The format of a trigger frame used to distinguish the format of a TB PPDU may be identified based on the Frame Control field included in the MAC header, determining whether it is an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame. Specifically, the format of a trigger frame may be distinguished based on the Type subfield, Subtype subfield, and / or Control Frame Extension subfield. Furthermore, if the values ​​of the Type subfield, Subtype subfield, and / or Control Frame Extension subfield are already set values, the trigger frame may be identified as an HE trigger frame; if they are other already set values, the trigger frame may be identified as an EHT trigger frame. Also, if the values ​​of the Type subfield, Subtype subfield, and / or Control Frame Extension subfield are other already set values, the trigger frame may be identified as a NEXT trigger frame.

[0213] For example, if the type subfield is 01 (B3 B2) and the subtype subfield is 0010 (B7 B6 B5 B4), the format of the frame containing the type subfield and subtype subfield may be an HE trigger frame. In this case, it may be necessary to further use entries for the type subfield (2 bits), subtype subfield (4 bits), and / or control frame extension subfield (4 bits) with a limited number of bits assigned to them in the EHT standard and the NEXT standard.

[0214] Alternatively, whether the trigger frame format is an HE trigger frame or an EHT trigger frame may be identified based on a common information field included in the trigger frame. That is, the format of the PPDU sent as a response to the trigger frame may be determined based on the value of a specific subfield (first subfield) included in the common information field. For example, based on the value of the common information field, a non-AP STA can select either an HE TB PPDU or an EHT TB PPDU and send it on the assigned RU. In this case, in addition to the common information field, a specific subfield (second subfield) of the user information field may also be used to further identify the PPDU format.

[0215] In other words, based on the common information field of the trigger frame, a variant for determining the format of the PPDU, which is the response to the trigger frame, may be determined, and the format of the PPDU may be determined by the determined variant. For example, if the common information field determines that the variant for determining the format of the PPDU is the HE variant, a non-AP STA can respond with an HE TB PPDU, and if the common information field determines that the variant for determining the format of the PPDU is the EHT variant, a non-AP STA can respond with an EHT TB PPDU.

[0216] In this case, user information fields may also be used as variants to determine the PPDU format, in addition to common information fields.

[0217] For example, a trigger frame may be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the trigger type subfield. For example, if the trigger type subfield value is already set, the trigger frame may be an HE trigger frame. Also, if the trigger type subfield value is already set, the trigger frame may be an EHT trigger frame. Also, if the trigger type subfield value is already set, the trigger frame may be a NEXT trigger frame.

[0218] For example, if the trigger type subfield value is between 0 and 7, it is an HE trigger frame, and if it is not between 0 and 7, it may be an EHT trigger frame or a NEXT trigger frame. The trigger type subfield indicates various trigger frame types, but in this case, there is a disadvantage that a limited trigger type subfield space must be used.

[0219] In another embodiment, a trigger frame can be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on its UL length subfield. For example, a trigger frame can be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the value obtained by modulo(remainder) the UL length subfield value. That is, the value of the UL length subfield may be used to determine whether the format of the PPDU sent as a response to the trigger frame is an HE PPDU or an EHT PPDU.

[0220] More specifically, a trigger frame can be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the value obtained by modulo(remainder)3 of the UL length subfield value (the remainder when the UL length subfield is divided by 3). For example, if the result of modulo 3 of the UL length subfield value is not 0, the trigger frame may be an HE trigger frame. Alternatively, if the result of modulo 3 of the UL length subfield value is 1, the trigger frame may be an HE trigger frame. Alternatively, if the result of modulo 3 of the UL length subfield value is 0, the trigger frame does not have to be an HE trigger frame. Alternatively, if the result of modulo 3 of the UL length subfield value is 0, the trigger frame may be an EHT trigger frame or a NEXT trigger frame.

[0221] In other words, if the modulo 3 calculation of the value of the UL length subfield of the trigger frame is not 0, the response to the trigger frame may be sent as HE TB PPDU, and if the modulo 3 calculation of the value of the UL length subfield is 1, the response to the trigger frame may be sent as HE TB PPDU.

[0222] Furthermore, if the value obtained by modulo 3 calculation of the UL length subfield of the trigger frame is 0, the format of the PPDU sent as a response to the trigger frame may be EHT TB PPDU.

[0223] Furthermore, it is possible to distinguish between HE trigger frames, EHT trigger frames, and NEXT trigger frames by using additional trigger frame classification methods in conjunction with these methods. For example, it is possible to distinguish between HE trigger frames, EHT trigger frames, and NEXT trigger frames by using the classification method explained in Figure 16.

[0224] According to one embodiment, the format of the trigger frame may be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the User Info field of the trigger frame.

[0225] In other words, similar to the common information field mentioned above, whether the trigger frame format is an HE trigger frame or an EHT trigger frame can be identified based on the user information field included in the trigger frame. That is, the format of the PPDU sent as a response to the trigger frame may be determined based on the value of a specific subfield (second subfield) included in the user information field. For example, based on the value of the user information field, a non-AP STA can select either an HE TB PPDU or an EHT TB PPDU and send it with the assigned RU. In this case, in addition to the user information field, a specific subfield (first subfield) of the common information field may also be used to identify the PPDU format.

[0226] In other words, a variant for determining the format of the PPDU, which is the response to the trigger frame, may be determined based on the user information field of the trigger frame, and the format of the PPDU may be determined by the determined variant. For example, if the user information field determines that the variant for determining the format of the PPDU is the HE variant, the non-AP STA can respond with an HE TB PPDU, and if the user information field determines that the variant for determining the format of the PPDU is the EHT variant, the non-AP STA can respond with an EHT TB PPDU.

[0227] In this case, in addition to the user information field, a common information field may also be used as a variant to determine the PPDU format.

[0228] For example, a frame may be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on the AID12 subfield. In one embodiment, a frame may be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on whether or not it contains an AID12 subfield with an already set value. In this case, a question may arise as to whether an STA indicated by a certain user information field should continue to check the AID12 subfield that appears after the user information field in order to determine the trigger frame format. To solve this problem, a user information field containing an AID12 subfield indicating which trigger frame it is may be located earlier in the user information list. Furthermore, to prevent an HE STA that does not understand this signaling method from malfunctioning, a user information field containing an AID12 subfield indicating which trigger frame it is may exist after the user information field corresponding to the HE STA.

[0229] Furthermore, in this case, information from subfields other than the AID12 subfield included in the user information field may not be necessary for the TB PPDU response, so the subfield of the user information field that includes the AID12 subfield indicating which trigger frame it is may be omitted. In other words, the length of the user information field may differ based on the AID12 subfield. Referring to Figure 15, the AID12 subfield can play a role in indicating the TB PPDU format to respond with. For example, if the AID12 subfield is already set to a value, the response to a trigger frame containing the AID12 subfield set to that already set value may be EHT TB PPDU. For example, if the AID12 subfield value is 2047, the response to a trigger frame containing the AID12 subfield may be EHT TB PPDU. Also, if the AID12 subfield is already set to a value, the response to a trigger frame containing the AID12 subfield set to that already set value may be NEXT TB PPDU. For example, if the AID12 subfield value is 2048, the response to the trigger frame containing the AID12 subfield may be NEXT TB PPDU.

[0230] Furthermore, according to another embodiment, when responding based on a user information field located at a previously set position relative to an already set value in the AID12 subfield, the response can be in the TB PPDU format corresponding to the already set value. For example, when responding based on a user information field located after an AID12 subfield located after an already set value, the response can be in the TB PPDU format corresponding to the already set value. If there are multiple values ​​indicating the TB PPDU format, and the response is based on a user information field located after both already set value 1 and already set value 2, the response can be in the TB PPDU format corresponding to already set value 1 and the TB PPDU format corresponding to already set value 2, according to the previously set priority. Referring to Figure 15, when responding based on a user information field located after an AID12 subfield set at 2047, the response can be in EHT TB PPDU format. Also, when responding based on a user information field located after an AID12 subfield set at 2048, the response can be in NEXT TB PPDU format. Furthermore, when responding based on user information fields that exist after both the AID12 subfield set to 2047 and the AID12 subfield set to 2048, a NEXT TB PPDU response can be used. Also, when responding based on user information fields that exist before both the AID12 subfield set to 2047 and the AID12 subfield set to 2048, an HE TB PPDU response can be used.

[0231] In this embodiment, we have taken an example in which the AID12 subfield indicates the type of trigger frame, but the present invention is not limited to this, and it is also possible to indicate the type of trigger frame with other subfields of the user information field.

[0232] According to one embodiment, a trigger frame may be classified as either an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame based on its padding field. For example, whether a trigger frame is an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame can be determined by whether or not the padding field contains a pre-set value indicating whether it is an HE trigger frame, an EHT trigger frame, or a NEXT trigger frame.

[0233] According to embodiments of the present invention, it is possible to classify HE trigger frames, EHT trigger frames, and NEXT trigger frames by combining the multiple trigger frame classification methods described in the present invention. Furthermore, the description of trigger frames in the present invention is not limited to the above and can also be applied to TRS.

[0234] In yet another embodiment of the present invention, the AP may not be able to instruct the transmission of both the EHT PPDU and the HE PPDU using a triggering frame. That is, the EHT AP cannot transmit a trigger frame that instructs both the HE TB PPDU and the EHT TB PPDU, and can only instruct one PPDU format.

[0235] Figure 18 shows UL MU operation according to yet another embodiment of the present invention.

[0236] As mentioned above, in addition to the trigger frame, the transmission of the TB PPDU can also be instructed by the TRS. Furthermore, as mentioned above, the TRS may be included in the HT control field. For example, when the HT control field includes the A-control field, it can also include the TRS. The TRS can be transmitted by the TRS control subfield. The A-control field may be in the form of a series of control list fields. Furthermore, the control list field may include the TRS.

[0237] Furthermore, an embedded receiver of a frame containing a TRS can respond to the TRS. For example, an STA corresponding to an RA contained in a frame containing a TRS can respond to the TRS. The TRS may include information about the length of the PPDU or frame in response to the TRS (UL Data Symbols), the location and size of the RU used when responding to the TRS (RU Allocation), information about the power used when responding to the TRS (AP Tx Power, UL Target RSSI), and information about the modulation method used when responding to the TRS (UL HE-MCS).

[0238] The embodiment in Figure 18 may be a method for solving the problems described in Figures 14 and 15. Furthermore, as mentioned above, the above embodiment regarding the trigger frame can also be applied to the TRS. The previously mentioned details are optional.

[0239] According to one embodiment of the present invention, in addition to TRS defined by the HE standard (HE TRS), TRS defined by the EHT standard or the NEXT standard (EHT TRS and NEXT TRS, respectively) may also exist. Therefore, depending on whether the indicated TRS is an HE TRS, EHT TRS, or NEXT TRS, the TB PPDU responding to the TRS may be an HE TB PPDU, an EHT TB PPDU, or a NEXT TB PPDU, respectively. For example, the standard under which the TRS is defined can be determined by the Control ID subfield of the A-control subfield. In an additional embodiment, TRS can be divided into two categories: HE TRS and TRS other than HE TRS.

[0240] Alternatively, for example, whether a TRS is defined by a standard may be determined by whether the HT control field is an HE variant, an EHT variant, or a NEXT variant. Furthermore, whether it is an HE variant, EHT variant, or NEXT variant may be determined by the values ​​of the bits already set in the HT control field. For example, if B0 and B1 of the HT control field are 1, it may be an HE variant. Also, whether it is an HE variant, EHT variant, or NEXT variant can be determined using B0, B1 of the HT control field and an additional bit (e.g., B31).

[0241] According to one embodiment of the present invention, it is possible to determine the TB PPDU format in response to a TRS based on the PPDU format that includes the TRS. That is, when a PPDU that instructs the transmission of a PPDU includes a TRS control subfield, the format of the PPDU may be determined based on the format of the PPDU that includes the TRS control subfield. For example, if the format of the PPDU that includes the TRS control subfield is HE PPDU, the format of the instructed PPDU may be HE PPDU. However, if the format of the PPDU that includes the TRS control subfield is EHT PPDU, the format of the instructed PPDU may be EHT PPDU.

[0242] Referring to Figure 18, when a TRS is transmitted via HE PPDU, the TB PPDU responding to the TRS may be HE TB PPDU. Also, when a TRS is transmitted via EHT PPDU, the TB PPDU responding to the TRS may be EHT TB PPDU. Furthermore, when a TRS is transmitted via NEXT PPDU, the TB PPDU responding to the TRS may be NEXT TB PPDU.

[0243] According to embodiments of the present invention, the subfields contained in the TRS can be interpreted differently based on the PPDU format containing the TRS. For example, if the TRS is contained in an HE PPDU, the UL HE-MCS subfield (or subfield related to MCS) contained in the TRS can indicate a value corresponding to the HE MCS table. If the TRS is contained in an EHT PPDU, the UL HE-MCS subfield (or subfield related to MCS) contained in the TRS can indicate a value corresponding to the EHT MCS table. If the TRS is contained in a NEXT PPDU, the UL HE-MCS subfield (or subfield related to MCS) contained in the TRS can indicate a value corresponding to the NEXT MCS table. The RU Allocation subfield may also be interpreted differently based on the PPDU format containing the TRS.

[0244] Figure 19 shows an example of a packet extension (PE) field for providing processing time according to one embodiment of the present invention.

[0245] Referring to Figure 19, when transmitting a PPDU, certain fields that do not need to be decoded may be included at the end of the PPDU to provide the receiving device with additional processing time to process the received PPDU.

[0246] Specifically, a receiving device that receives a PPDU can decode and interpret the PPDU and send a response to the transmitting device. However, if the time required to process the PPDU increases due to a decrease in the performance of the receiving device, the receiving device may not be able to send a response within the time allotted for sending a response to the PPDU. Therefore, in order to ensure sufficient processing time, the PPDU may include fields that do not require decoding, and these can be called PE fields.

[0247] Since the PE field does not require separate decoding, the duration of the PE field allows the receiving device time to decode and process the PPDU, enabling it to send a response to the PPDU to the transmitting device within a pre-set time. In other words, the PE field is located at the end of the PPDU, providing additional processing time for the receiving device (the terminal).

[0248] Therefore, the PE field may be located at the end of the PPDU or after the data field to provide additional processing time. For example, the PPDU may contain the preamble, data field, and PE field in that order. The preamble and data field may be as described in the above embodiment. For an HE PPDU, the preamble may include L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, HE-SIG-B, HE-STF, and HE-LTF. For an EHT PPDU, the preamble may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG, EHT-STF, and EHT-LTF. A PPDU containing the PE field may be an HE PPDU or an EHT PPDU, or a PPDU in a standard defined after the EHT standard.

[0249] If the PE field is not included in the PPDU, and the receiving device (e.g., STA) does not have high performance, it may be difficult to respond within the pre-set time from the end of the received PPDU due to the time required to process the received PPDU. The pre-set time may be after IFS (inter-frame space) or SIFS (short inter-frame space) from the end of the received PPDU. Therefore, by placing the PE field, which does not need to be decoded, at the end of the received PPDU, time can be secured to process the received PPDU. In other words, by placing the field that does not need to be decoded at the end of the PPDU, the PPDU can be processed sufficiently quickly. Therefore, it is possible to process a PPDU containing the PE field and send an immediate response to it within the time limit. In this case, the immediate response may be sent after SIFS from the end of the PPDU containing the PE field.

[0250] Furthermore, the power used to transmit the PE field can be based on the power used to transmit the data field. For example, the power used to transmit the PE field may be the same as the average power used to transmit the data field.

[0251] The PE field may be transmitted with arbitrary content. Furthermore, the location and size of the PE field transmitted in the frequency domain may be the same as that of the data field or the resource unit (RU) to which the data field is transmitted.

[0252] According to an embodiment of the present invention, the duration of a PE field may be 0 or a multiple of 4 us. For example, the duration of the PE field may be one of 0, 4, 8, 12, 16, and 20 us. In this case, the maximum value of the duration of the PE field may vary depending on the format of the PPDU that includes the PE field. For example, in the case of an HE PPDU, the duration of the PE field may be one of 0, 4, 8, 12, and 16 us, and in the case of an EHT PPDU, it may be one of 0, 4, 8, 12, 16, and 20 us. A PE field with a duration of 0 us corresponds to the absence of a PE field.

[0253] According to an embodiment, the PE field with a configured duration may be used only for the configured settings. For example, the configured duration may be 20 us or longer. The configured duration may be obtained based on an MCS (modulation and coding scheme) or a modulation scheme. That is, a PE field having the configured duration may be set according to a configured MCS index, configured MCS, or configured modulation scheme, and included in a PPDU.

[0254] Alternatively, a PE field with the configured duration may be included in a PPDU for a configured MCS index, configured modulation, or an MCS index, modulation, or MCS that is greater than or equal to the configured MCS. For example, the configured MCS index, configured modulation, or the configured MCS may be based on 4096-QAM.

[0255] In addition to the MCS or modulation scheme, the configured value for the duration of the PE field may also be obtained based on the number of spatial streams. For example, when a number of streams greater than 8 spatial streams is used, the configured value for the duration of the PE field may be used.

[0256] Further, the preset value may be obtained based on the channel width, bandwidth, or RU size to be transmitted. For example, when the channel width, bandwidth, or RU size is set to a preset value, the duration of the PE field may be determined as a specific preset value.

[0257] According to an embodiment, the channel width or bandwidth may be a value corresponding to a PPDU to be transmitted. Alternatively, the channel width or bandwidth may be a value corresponding to PPDUs transmitted simultaneously by a plurality of STAs or an overall PPDU. For example, when the channel width or bandwidth is 320 MHz, use of a specific preset value may be allowed as the duration value of the PE field of the PPDU. For example, use of a duration of 20 us may be allowed only when the channel width or bandwidth is 320 MHz.

[0258] According to another embodiment, the channel width or bandwidth for which use of the specific value is allowed may be a value greater than 160 MHz, and the RU size may be greater than 2×996. Further, the RU size may correspond to the total RU used for transmission. That is, when multiple RUs are used, the RU size may correspond to the sum of the sizes of the plurality of RUs.

[0259] That is, the specific preset value for the duration of the PE field may only be used or set under specific conditions. For example, as described above, the duration for the PE field may be set to one of 0 us, 4 us, 8 us, 12 us, 16 us, or 20 us, and among these values, the specific value may be used or set in a PPDU that meets the following conditions.

[0260] - A PPDU modulated using a 4096-QAM modulation scheme

[0261] - A PPDU transmitted using 8 or more spatial streams (in at least one RU / MRU)

[0262] - If the size of at least one allocated RU or MRU is 2 × 996 or larger, 320MHz PPDU

[0263] - EHT TB PPDU based on the trigger frame (i.e., the format of the PPDU as indicated by the trigger frame),

[0264] For example, the duration of the PE field may be set to differ depending on the format of the PPDU indicated by the frame that triggers the transmission of the PPDU. Specifically, if the PPDU indicated by the frame is an HE TB PPDU, the duration of the PE field of the HE TB PPDU may be set to one of the following values: 0us, 4us, 8us, 12us, or 16us. However, if the PPDU indicated by the frame is an EHT TB PPDU, the duration of the PE field of the HE TB PPDU may be set to one of the following values: 0us, 4us, 8us, 12us, 16us, or 20us. In other words, the value that can be set as the duration of the PE field (e.g., the maximum value) may differ depending on the format of the PPDU indicated by the frame.

[0265] For example, as mentioned above, 20us may only be acceptable under specific conditions.

[0266] For example, the specific value already set in the above explanation may be 20us. That is, a PE field with a duration of 20us may be permitted only under the specific conditions or in specific circumstances described above.

[0267] Figure 20 shows an example of a High Efficiency (HE) operation element and a default PE duration subfield according to one embodiment of the present invention.

[0268] Referring to Figure 20, the AP STA (or AP) can specify the duration value of the PE field using the operation element.

[0269] Specifically, information related to the duration of the PE field in the PPDU may be included in the operation element and transmitted. The information related to the duration of the PE field may be the duration of the PE field included in the PPDU. For example, an AP may set the value of a control ID to a value that points to a TRS in order to trigger the transmission of a PPDU, and a non-AP STA may transmit the PPDU as a response to the PPDU in the TRS. In this case, the PPDU may include a PE field to provide the aforementioned additional processing time, and information related to the duration of the PE field may be transmitted to the non-AP STA in a specific field of the operation element (for example, a default PE duration field).

[0270] In this case, the duration of the PE field or the already set information related to the duration of the PE field can be called the default PE duration, and the default PE duration may be indicated by the default PE duration subfield.

[0271] The values ​​of the default PE duration subfield and / or PE field may be set by the transmission parameter TXVECTOR parameter DEFAULT_PE_DURATION. In this invention, TRS may be used interchangeably with TRS Control.

[0272] An action element may contain information related to the operation of the BSS and may be an HE action element or an EHT action element depending on the format. Such an action element may be transmitted in a Beacon frame, Probe Request frame, Probe Response frame, Association Request frame, Association Response frame, Reassociation Request frame, and Reassociation Request frame.

[0273] The default PE duration subfield included in the operating element can specify the duration of the PE field in a fixed unit (or a previously set unit). In this case, the fixed unit or the previously set unit may be 4us, and if the value of the default PE duration subfield is N, the duration of the PE field specified by the default PE duration subfield may be N*4us. For example, if the value of the default PE duration subfield is "4", the duration of the PE field specified by the default PE duration subfield may be 16us.

[0274] Figure 20(a) shows an example of an HE operation element. Referring to Figure 20(a), the HE operation element may include an HE operation parameter field. Figure 20(b) shows an example of an HE operation parameter field. Referring to Figure 20(b), the HE operation parameter field may include a default PE duration subfield. In this case, the default PE duration subfield may be 3 bits, and values ​​5 to 7 may be reserved. That is, since values ​​5 to 7 of the default PE duration subfield are reserved, only values ​​from 0 to 4 may be valid. Therefore, the durations that can be indicated by the default PE duration subfield may be 0, 4, 8, 12, and 16us. If the reserved value 5 is used, the default PE duration subfield may be indicated up to 20us.

[0275] Figure 21 shows an example of a method for setting the duration of a PE field according to one embodiment of the present invention.

[0276] Referring to Figure 21, when a non-AP STA sends a PPDU in response to an AP's TRS, the non-AP STA can set the duration of the PE field in the PPDU to the default PE duration obtained from the AP.

[0277] Specifically, a terminal that receives a frame to trigger the transmission of a PPDU (for example, a frame containing a control ID subfield with a value indicating TRS, or a trigger frame instructing the transmission of a PPDU) may include a PE field in the PPDU to provide additional processing time. The PE field may be set in fixed time units or already set time units (for example, 0us, 4us, 8us, 12us, 16us, or 20us), as described above. In this case, 20us may be permitted only in specific cases, as described above.

[0278] The duration of the PE field may be set to a value indicated by the default PE duration indicated by the default PE duration field transmitted from the AP, where the default PE duration may be the same as that described above with reference to FIG. 20, and descriptions identical to those given in FIG. 20 will be omitted. The default PE duration field may be indicated by being included in an operation element and transmitted as described in FIG. 20.

[0279] That is, when a non-AP STA responds to a TRS from an AP, the duration for the PE field of a PPDU can be determined based on the default PE duration transmitted and indicated by the AP. In this case, the PPDU may be an HE TB PPDU, an EHT TB PPDU, or a future-version TB PPDU that is a trigger-frame-based PPDU, and the AP may be an AP associated with the non-AP STA.

[0280] As shown in FIG. 21, a STA can receive a trigger frame for triggering or instructing transmission of a PPDU, or a frame including a TRS control field, and can transmit a TB PPDU as a response thereto.

[0281] As described above in FIG. 19 and FIG. 20, a TB PPDU may include a PE field to provide additional processing time, and the duration of the PE field may be set in units of fixed time. If a default PE duration is indicated to a STA by a default PE duration subfield from an AP, the STA may set the duration of the PE field to the indicated default PE duration. For example, the default PE duration may be a value included in an operation element (e.g., an HE operation element, an EHT operation element, or the like) transmitted by the AP. The STA (AP or AP STA) that transmitted the default PE duration and the STA (AP or AP STA) that transmitted the TRS control field may be the same STA.

[0282] If the STA receives a trigger frame from the AP and sends a TB PPDU in response, the TB PPDU may include a PE field, and the duration of the PE field is T. PE This can be calculated using formula 5 below.

[0283]

number

[0284] In other words, in equation 5,

number

[0285] m is a value that varies depending on the PPDU format; for example, the value of m for a TB PPDU may be 2.

[0286] T PREAMBLE This refers to the length of the preamble of the TB PPDU being sent. When HE TB PPDU is sent, T PREAMBLE This may be the sum of the lengths of L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, HE-STF, and HE-LTF. When an EHT PPDU is transmitted, T PREAMBLE T may be the length of the EHT preamble. That is, when an EHT TB PPDU is sent, PREAMBLE This may be the sum of the lengths of L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-STF, and EHT-LTF.

[0287] N SYM may represent the number of data OFDM symbols included in a PPDU to be transmitted. For example, N SYM may be determined by Mathematical Expression 7 below.

[0288]

Math.

[0289] In Mathematical Expression 7, b PE_Disambiguity may be a TXVECTOR parameter TB_PE_DISAMBIGUITY value. Alternatively, b PE_disambiguity may be a value of a PE Disambiguity subfield included in a trigger frame. Furthermore, when transmitting a HE PPDU, the TXVECTOR parameter TB_PE_DISAMBIGUITY may be a TXVECTOR parameter HE_TB_PE_DISAMBIGUITY. When transmitting an EHT PPDU, the TXVECTOR parameter TB_PE_DISAMBIGUITY may be a TXVECTOR parameter EHT_TB_PE_DISAMBIGUITY. In addition, the PE Disambiguity subfield included in the trigger frame may be configured based on whether a preset mathematical expression is satisfied.

[0290] T SYM may be a length of an OFDM symbol. In addition, T SYM may be a value including a GI (guard interval).

[0291] N MA may be the number of midambles or the number of midamble periods. If the Doppler field is 0, N MA may be 0. Furthermore, for an EHT PPDU, whether the Doppler field is 0 or N MAThis may be 0. The mid-amplifier may be inserted in the middle of the PPDU's data field. The mid-amplifier may also consist of multiple LTFs. The mid-amplifier may be present to assist the receiver's channel estimation.

[0292] N LTF This may be the number of LTFs included in the preamble. In this case, the LTF may be an HE-LTF if an HE PPDU is being sent. Alternatively, the LTF may be an EHT-LTF if an EHT PPDU is being sent.

[0293] T LTFSYM may be the length of the OFDM symbol of the LTF. In this case, the LTF may be HE-LTF if it transmits an HE PPDU. Or, in this case, the LTF may be EHT-LTF if it transmits an EHT PPDU. Also, T LTFSYM This value may include GI.

[0294] According to the described example, when a mid-ampoule is not present, T PE This can be determined by the following formula 8.

[0295]

number

[0296] As shown in Figure 21, when the trigger frame instructs the transmission of a TB PPDU, the STA responds to the trigger frame with T PE A PPDU containing a PE field with a duration can be transmitted.

[0297] If a frame containing a TRS and a trigger frame instructing the transmission of a PPDU are both included in a single PPDU and transmitted, the duration of the PE field included in the PPDU sent in response may be set to the same value as the default PE duration, by adjusting (or setting) the values ​​of each field included in the trigger frame. For example, by adjusting (or setting) the values ​​of the UL length subfield and PE Disambiguity subfield of the trigger frame, PE The value of this parameter can be the same as the default PE duration.

[0298] In other words, when the transmission of a PPDU is triggered by a trigger frame and TRS, the duration of the PE field of the PPDU sent in response may be set to the value indicated by the default PE duration subfield. In this case, the T included in the trigger frame PE The field values ​​used to calculate T PE The value may be set to be the same as the value indicated by the default PE duration subfield.

[0299] For example, if a single PPDU contains trigger frames and TRS that instruct different STAs to transmit TB PPDUs, the maximum duration of the PE field in a TB PPDU that is instructed to transmit by the trigger frame alone may be 20us (i.e., a PE field duration of 20us is permitted), while the duration of the PE field in a TB PPDU that is triggered by the TRS may have a maximum value of 16us due to the default PE subfield. In this case, the T included in the trigger frame PE The values ​​of the subfields used to calculate (e.g., the LENGTH field and / or the PE Disambiguity subfield) are the duration value from the default PE subfield and T PE The values ​​may be set to be the same.

[0300] In other words, when a trigger frame instructs the transmission of an EHT TB PPDU, the duration of the PE field of the EHT TB PPDU may be determined to be one of the following values: 0us, 4us, 8us, 12us, 16us, or 20us. However, the PPDU containing the trigger frame may also contain a TRS instructing the transmission of an EHT TB PPDU, and the default PE duration subfield for the EHT TB PPDU instructed by the TRS may be set to one of the following values: 0us, 4us, 8us, 12us, or 16us. In this case, the terminal that triggers the transmission of the TB PPDU by the trigger frame may be STA1, and the terminal that triggers the transmission of the TB PPDU by the TRS may be STA2.

[0301] In this case, a terminal whose transmission of a TB PPDU is triggered by the TRS can set the duration of the PE field to a value indicated by the default PE duration included in the operating element. However, a terminal whose transmission of a TB PPDU is triggered by the trigger frame can use the subfields included in the trigger frame (e.g., the LENGTH field and / or the PE Disambiguity subfield) to calculate the T PE The value can be set as the duration of the PE field included in the TB PPDU. In this case, the T included in the trigger frame PE The value of the subfield used to calculate the value is the value indicated by the default PE duration and T PE The values ​​may be set to be identical.

[0302] In other words, if the maximum value for the duration of the PE field of a TB PPDU, which is contained in a single PPDU and triggers the transmission of TB PPDUs to different STAs, differs from the maximum value of the PE field indicated by the default PE duration subfield of the TRS, the value of the subfield included in the trigger frame and used to calculate the duration of the PE field contained in the TB PPDU may be set (or adjusted) so that the calculated value is the same as the value indicated by the default PE duration subfield.

[0303] In this case, if the default PE duration subfield is set to one of the following values: 0us, 4us, 8us, 12us, or 16us (or 0us, 4us, 8us, 12us, 16us, or 20us), the T calculated by the trigger frame will be PE The value indicated by the default PE duration subfield may be the same.

[0304] Therefore, according to an embodiment of the present invention, when a TRS and a trigger frame that trigger the transmission of a TB PPDU to different STAs are included in a single PPDU, the duration of the PE field included in the PPDU transmitted as a response to the TRS and the duration of the PE field included in the PPDU transmitted as a response to the trigger frame may be the same. That is, in Figure 21, T PE The default PE duration may be the same value.

[0305] According to the embodiment described above, when responding to a TRS or a trigger frame contained in a PPDU containing a TRS, the response includes a PE field with a previously set duration. In this case, the previously set duration may be the default PE duration. Therefore, the AP can set the default PE duration to a sufficiently large value in order to successfully receive or respond to a received PPDU. However, as mentioned above, one of the values ​​for the PE field duration may only be used in the previously set setting. For example, a PE field duration of 20us may only be used in the previously set setting. Therefore, in order to use the previously set setting when responding to a TRS or a trigger frame contained in a PPDU containing a TRS, it may be necessary to set a larger default PE duration. For example, in order to use the previously set setting, it may be necessary to set the default PE duration to 20us. In such cases, even if the previously set setting is not used, a longer default PE duration must be used, which may be redundant. In other words, even for PPDUs configured to be receivable without using a long PE field, a long PE field is still required, which can lead to wasted airtime.

[0306] Furthermore, the maximum value that the default PE duration subfield included in the HE operating element can represent may be 16us. Therefore, a problem may arise where settings requiring a longer PE field are difficult to trigger with trigger frames included in a TRS or a PPDU containing a TRS. If the reserved value of the default PE duration subfield included in the HE operating element is used, the HE STA receiving it will not be able to interpret it and will be unable to operate correctly.

[0307] The following example illustrates a method for resolving this issue.

[0308] Figure 22 shows yet another example of a method for setting the duration of UL MU operation and PE field according to one embodiment of the present invention.

[0309] Referring to Figure 22, in order to solve the problems described in Figure 21, the value of the PE field of the PPDU triggered by the trigger frame or TRS may be restricted.

[0310] Specifically, when triggering an STA response, it can be instructed to respond using restricted settings. For example, when triggering using a TRS or a trigger frame contained in a PPDU containing a TRS, it can be instructed to respond using restricted settings. In this case, the method of instruction may include instruction in a subfield contained in the TRS or trigger frame. In this case, the method of instruction may include implicit instruction when responding to a TRS or a trigger frame contained in a PPDU such as a TRS. Such restricted settings may be settings that do not require a PE field of a pre-set length. In one embodiment, the pre-set length may be 20us or longer. More specifically, the pre-set length may be 20us. In another embodiment, the pre-set length may be longer than 16us. Thus, an STA responding to a TRS or a trigger frame contained in a PPDU containing a TRS can respond using restricted settings.

[0311] In this case, the duration of the PE field included in the responding PPDU may be shorter than the previously set length. For example, the duration of the PE field included in the responding PPDU may be 16us or less.

[0312] Furthermore, the restricted settings may be based on the already configured settings described in Figure 19. For example, the restricted settings may be settings other than the already configured settings described in Figure 19. Or, the restricted settings may be settings other than the settings that allow the use of the PE field of the already configured duration described in Figure 19. Or, the restricted settings may be settings that do not require the PE field of the already configured duration described in Figure 19. For example, the restricted settings may be based on at least one of the following:

[0313] 1) MCS or modulation

[0314] 2) Number of spatial streams

[0315] 3) Channel width, bandwidth, or RU size

[0316] Therefore, according to one embodiment, when transmitting a trigger frame contained in a TRS or a PPDU containing a TRS, it is possible to instruct the system to respond using an MCS index or modulation lower than or equal to an already set MCS index or modulation. Alternatively, when transmitting a trigger frame contained in a TRS or a PPDU containing a TRS, it is not necessary to instruct the system to respond with 4096-QAM. Alternatively, when transmitting a trigger frame contained in a TRS or a PPDU containing a TRS, it is possible to instruct the system to respond with an MCS that does not correspond to 4096-QAM.

[0317] Alternatively, when transmitting a trigger frame contained in a TRS or a PPDU containing a TRS, it can be instructed to respond using a number of spatial streams less than or equal to the number already set. For example, the number of already set streams may be 8.

[0318] Alternatively, when transmitting a trigger frame included in a TRS or a PPDU containing a TRS, it may be instructed to respond using a channel width, bandwidth, or RU size less than or equal to a previously set size. For example, the previously set size may be 160 MHz or 320 MHz. Or, the previously set size may be 2 × 996 size (number of tones).

[0319] If you are sending a trigger frame with a PPDU that does not include TRS, you do not need to use the restricted settings described above.

[0320] Referring to Figure 22, an AP can transmit a frame containing TRS Control. Furthermore, a trigger frame may be included in a PPDU containing such a frame. In this case, the TRS Control and the trigger frame can instruct restricted settings. For example, they do not need to instruct settings that require high capability upon reception. Therefore, the PE fields in the EHT TB PPDU responding to the TRS Control and the EHT TB PPDU responding to the trigger frame may be 16us or less. Thus, resources are not wasted unnecessarily due to long PE fields.

[0321] Figure 23 shows yet another example of a method for setting the duration of UL MU operation and PE field according to one embodiment of the present invention.

[0322] Referring to Figure 23, if the duration of the PE field of the PPDU indicated by the trigger frame differs from the duration of the PE field of the PPDU indicated by the TRS, the duration of the PE field may be set by the PE duration indicated by the TRS.

[0323] Specifically, a TRS control that includes a TRS instructing the transmission of a PPDU can specify the duration of the PE field in the PPDU using a PE duration subfield. For example, an STA responding to a TRS control field can determine the duration of the PE field in the responding PPDU based on the PE duration subfield included in the TRS control field.

[0324] In one embodiment, the PE duration subfield can specify one value from 0, 4, 8, 12, 16, or 20us. In such a case, the PE duration subfield may be 3 bits. This has the advantage that the PE field of the required duration can be individually specified each time the TRS triggers the transmission of the PPDU. For example, the minimum required duration can be specified.

[0325] In another embodiment, the PE duration subfield can indicate whether the use of a 20us PE field is permitted. In this case, the PE duration subfield may be 1 bit. This method has the advantage of having a small number of bits in the PE duration subfield included in the TRS. In one embodiment, if the PE duration subfield included in the TRS control indicates 20us, the duration of the PE field included in the PPDU may be 20us. Also, if the PE duration subfield included in the TRS control does not permit the use of a 20us PE field, the duration indicated by the default PE duration subfield included in the operating element described in Figures 20 and 21 may be set as the duration of the PE field and transmitted in the PPDU.

[0326] The 20us duration of the PE field may be limited to use only in EHT TB PPDUs. If a response is made in HE TB PPDU format, it is impossible to set the PE field duration to 20us. In this case, the terminal can recognize whether the TB PPDU whose transmission is triggered by the TRS or trigger frame is an EHT TB PPDU or an HE TB PPDU based on the TB PPDU format signaling described in Figures 17 and 18. For example, based on the value of a specific field included in the trigger frame, the STA can identify whether the format of the triggered PPDU is an EHT TB PPDU or an HE TB PPDU.

[0327] The TRS control may include signaling indicating whether the PPDU containing the TRS control contains a TRS control or trigger frame configured to request a 20us PE field. If it is indicated that a TRS control or trigger frame configured to request a 20us PE field is included, the response can be made using a PPDU containing a 20us PE field. If it is indicated that a TRS control or trigger frame configured to request a 20us PE field is not included, the duration of the PE field may be set by the default PE duration.

[0328] In another embodiment, when responding to a TRS, it is possible to always respond with a PPDU that includes a PE field with a pre-set duration. For example, the pre-set duration may be 20us. Furthermore, this embodiment may be limited to the case where the response is an EHT TB PPDU. If the response is an HE TB PPDU, the 20us PE field does not need to be used. That is, when responding with an EHT TB PPDU, the 20us PE field is included in the EHT TB PPDU and transmitted, and when responding with an HE TB PPDU, the PE field set by the default PE duration may be included in the HE TB PPDU and transmitted.

[0329] In the described embodiment, the trigger frame included in the PPDU containing the TRS may be set to indicate the duration of the PE field as indicated in the described embodiment. For example, the UL length subfield and PE Disambiguity subfield of the trigger frame included in the PPDU containing the TRS can indicate values ​​such that the duration of the PE field becomes the duration of the PE field as indicated in the described embodiment. In this case, the duration of the PE field is the T as described in Figure 21. PE It may be determined by [the relevant factor].

[0330] Furthermore, according to one embodiment, multiple TRS included in a single PPDU can indicate the duration of the same PE field. For example, multiple TRS included in a single PPDU may include a PE duration subfield set to the same value. The multiple TRS may be included in multiple A-MPDUs of the PPDU.

[0331] Figure 23(a) shows the TRS control field. Referring to Figure 23(a), the TRS control field may include the UL Data Symbols, RU Allocation, AP Tx Power, UL Target RSSI, UL MCS, and PE Duration subfields. The descriptions of each subfield may be as described in Figures 18 to 23. The PE Duration subfield can also indicate whether or not to respond with a 20us PE field. In this case, the PE Duration subfield may be 1 bit.

[0332] Referring to Figure 23(b), an AP can transmit a PPDU containing a trigger frame or a frame containing a TRS control field. The PE duration subfield included in the TRS control field may be set to 0. A PE duration subfield set to 0 may indicate that 20us is not used or that the default PE duration should be used. Other PE duration subfields included in a PPDU containing a PE duration set to 0 may also be set to 0. Furthermore, a trigger frame included in a PPDU containing a PE duration subfield set to 0 may be configured such that the duration of the PE field in the PPDU responding to the trigger frame is the same as the duration indicated by the PE duration subfield set to 0. Referring to Figure 23(b), the default PE duration may be the duration of the PE field in the PPDU responding to a trigger frame containing either 1) a PE duration subfield set to 0, or 2) a PE duration subfield included in a PPDU containing a PE duration subfield set to 0. Alternatively, the duration of the PE field in a PPDU responding to a trigger frame contained in a PPDU that includes a PE duration subfield set to 0 (1) or a PE duration subfield set to 0 (2) may be 16us or less. In this case, the responding PPDU may be an EHT TB PPDU. Alternatively, if responding to a TRS or trigger frame with an HE TB PPDU, the PE field with the default PE duration may be used.

[0333] Referring to Figure 23(b), an AP can transmit a PPDU that includes a trigger frame or a frame that includes a TRS control field. The PE duration subfield included in the TRS control field may be set to 1. The PE duration subfield set to 1 may indicate that 20us should be used or that the default PE duration should not be used. Other PE duration subfields included in a PPDU that includes a PE duration subfield set to 1 may also be set to 1. Furthermore, a trigger frame included in a PPDU that includes a PE duration subfield set to 1 may be set such that the duration of the PE frame in the PPDU responding to the trigger frame is the same as the duration indicated by the PE duration subfield set to 1. Referring to Figure 23(b), the duration of the PE field in a PPDU responding to a trigger frame in a PPDU that includes a PE duration subfield set to 1 may be 20us. Alternatively, the duration of the PE field in a PPDU responding to a trigger frame contained in a PPDU that includes either 1) a PE duration subfield set to 1, or 2) a PE duration subfield set to 1, does not have to be the default PE duration. In this case, the responding PPDU may be an EHT PPDU. Or, in this case, the responding PPDU may be an EHT TB PPDU. That is, it may be limited to responding with an EHT TB PPDU.

[0334] Figure 24 shows yet another example of a method for setting the duration of UL MU operation and PE field according to one embodiment of the present invention.

[0335] Referring to Figure 24, the duration of the PE field included in the TB PPDU may be set to a value indicated by the PE duration field indicated by the TRS control field, or to a value indicated by the default PE duration subfield included in the operating element. Alternatively, if the TB PPDU is triggered only by a trigger frame, the duration of the PE field of the TB PPDU may be set by specific conditions (MCS method, RU size, number of spatial streams used, and / or format of the indicated PPDU (e.g., whether an EHT TB PPDU or an HE TB PPDU is indicated)).

[0336] For example, a PE field duration of 20us may be permitted only if the TB PPDU satisfies the aforementioned specific conditions (e.g., if it is designated as an EHT TB PPDU, if eight or more spatial streams are used, or if the size of at least one RU is greater than 2 × 996, if the bandwidth in which the EHT PPDU (or EHT MU PPDU, etc.) is transmitted is 320 MHz, or if the PPDU is modulated with 4096-QAM).

[0337] If the transmission of a PPDU is instructed by the TRS, the duration of the PE field included in the PPDU may be set to a value indicated by the default PE duration subfield included in the operating element (e.g., an HE operating element or an EHT operating element) or by the PE duration subfield included in the TRS control field.

[0338] If both the TRS and the trigger frame are included in a single PPDU, and both instruct the transmission of the PPDU, and the maximum duration of the PE field when the PPDU is instructed by the trigger frame is the same as the maximum duration of the PE field when it is instructed by the TRS, then it may be set to the value indicated by the default PE duration subfield or the value indicated by the PE duration subfield included in the TRS.

[0339] However, when the TRS and trigger frame are included in a single PPDU and both instruct the transmission of the PPDU, the maximum duration of the PE field when the PPDU is instructed by the trigger frame does not have to be the same as the maximum duration of the PE field instructed by the default PE duration subfield when the PPDU is instructed by the TRS. For example, the TB PPDU instructed by the trigger frame and / or TRS may satisfy certain conditions, and the maximum duration of the PE field may be a first maximum value (e.g., 20us is allowed), while the maximum duration of the PE field instructed by the default PE subfield included in the operating element may be a second maximum value (e.g., 16us). In this case, the duration of the PE field may be set to the value instructed by the default PE subfield or the value instructed by the PE subfield included in the TRS.

[0340] In this case, the PE duration subfield can indicate that 20us is the maximum allowed duration for the PE field, or it can instruct the operating element to set the duration of the PE field as the value of the default PE duration subfield included in the operating element.

[0341] In other words, according to one embodiment of the present invention, the duration of the PE field may be determined based on the PPDU format in response to the TRS. According to one embodiment, when responding to the TRS with an HE PPDU, the duration of the PE field may be the HE default PE duration. Also, when responding to the TRS with an EHT PPDU, the duration of the PE field may be the value indicated by the EHT default PE duration. For example, the HE PPDU may be an HE TB PPDU, or an HE SU PPDU. Also, the EHT PPDU may be an EHT TB PPDU, or an EHT MU PPDU. Furthermore, the HE default PE duration may be the default PE duration described in Figures 20 and 21. For example, the HE default PE duration may be the value indicated by the HE operating element. More specifically, the HE default PE duration may be the value indicated in the default PE duration subfield included in the HE operating element.

[0342] Furthermore, the EHT default PE duration may be a value indicated by the EHT operating element. More specifically, the EHT default PE duration may be a value indicated by the EHT default PE duration subfield included in the EHT operating element.

[0343] In one embodiment, the EHT default PE duration subfield can indicate whether the duration of the PE field is 20us or not. In this case, the EHT default PE duration subfield may be 1 bit.

[0344] In another embodiment, the EHT default PE duration subfield can indicate whether the duration of the PE field is the same as the HE default PE duration. In this case, the EHT default PE duration subfield may be 1 bit. For example, if the EHT default PE duration subfield indicates that the duration of the PE field is the same as the HE default PE duration, the EHT default PE duration may be the default PE duration indicated by the HE operating element. Also, if the EHT default PE duration subfield indicates that the duration of the PE field is not the same as the HE default PE duration, the EHT default PE duration may be 20us.

[0345] In another embodiment, the EHT default PE duration subfield can indicate whether the duration of the PE field is 0, 4, 8, 12, 16, or 20us. In this case, the EHT default PE duration subfield may be 3 bits.

[0346] Furthermore, according to other embodiments, the EHT default PE duration may be 20us.

[0347] Referring to Figure 24(a), the HE operating element may include a default PE duration subfield. The default PE duration subfield may also be included in the HE operating parameter field contained within the HE operating element. Figure 24(a) may be identical to Figure 20(b).

[0348] Referring to Figure 24(b), the EHT operating element may include an EHT default PE duration subfield. The EHT default PE duration subfield may also be included in the EHT operating parameter field contained within the EHT operating element. For example, the EHT default PE duration subfield may be 1 bit.

[0349] Referring to Figure 24(c), there may be cases where an HE PPDU is sent in response to TRS control, and cases where an EHT PPDU is sent. If an HE PPDU is sent as a response, the duration of the PE field included in the HE PPDU may be the default PE duration. The default PE duration may be the value indicated in Figure 24(a). Also, the default PE duration may be a value of 16us or less. If an EHT PPDU is sent as a response, the duration of the PE field included in the EHT PPDU may be the EHT default PE duration. The EHT default PE duration may be set based on the EHT operating element or the HE operating element. For example, the EHT default PE duration may be set to 1) an already set value based on the EHT default PE duration subfield included in the EHT operating element, or 2) a value based on the default PE duration subfield included in the HE operating element. The already set value may be 20us. Referring to Figure 24(c), when responding to TRS control with an EHT PPDU, it is possible to transmit the PPDU including a 20us PE field.

[0350] According to one embodiment of the present invention, multiple PPDUs may be multiplexed in the frequency domain. Such multiple PPDUs can be called an A-PPDU (aggregated PPDU). When an A-PPDU is transmitted, multiple PPDUs may be transmitted simultaneously. For example, an HE PPDU and an EHT PPDU can constitute an A-PPDU. More specifically, an HE TB PPDU and an EHT TB PPDU can constitute an A-PPDU. For example, an A-PPDU composed of an HE TB PPDU and an EHT TB PPDU can be triggered to be transmitted by multiple STAs.

[0351] According to one embodiment of the present invention, the durations of the PE fields included in the PPDUs constituting the A-PPDU may be the same. For example, the durations of the PE fields included in the HE TB PPDU and the EHT TB PPDU may be the same. In this case, the method for setting the durations may be as described in Figures 20 to 24. This simplifies the operation of the STA receiving the A-PPDU.

[0352] As another example, when an A-PPDU consisting of an HE PPDU and an EHT PPDU is transmitted by a single STA, the duration of the included PE field may be the same. This allows for a simpler implementation when constructing the A-PPDU.

[0353] According to one embodiment of the present invention, it is also possible to transmit a PPDU other than a TB PPDU in response to a trigger frame or TRS. For example, an SU PPDU or an MU PPDU can be transmitted. For example, the MU PPDU may be an EHT MU PPDU or an HE MU PPDU. The SU PPDU may be an HE SU PPDU or a non-HT PPDU. According to one embodiment, the method for setting the duration of the PE field may differ depending on whether a TB PPDU is transmitted in response to a trigger frame or TRS, or whether a PPDU other than a TB PPDU is transmitted. For example, when transmitting a TB PPDU, the duration setting method described in Figures 20 to 24 can be used. Also, when transmitting a PPDU other than a TB PPDU, the nominal PE duration can be set as the duration.

[0354] Figure 25 shows an example of a method for setting the CS Required subfield according to one embodiment of the present invention.

[0355] Referring to Figure 25, it is possible to perform carrier sense (CS) when responding to a trigger frame. For example, when a trigger frame is received, the STA can decide whether or not to respond to the trigger frame based on the CS result. Here, CS may include physical CS and virtual CS. Physical CS may include clear channel assessment (CCA). For example, the physical CS performed when deciding whether or not to respond to a trigger frame may be energy detection (ED). Virtual CS may mean considering NAV. The CS performed when deciding whether or not to respond to a trigger frame may be performed between the end of the PPDU containing the trigger frame (or after the PPDU) and the SIFS time (or within the SIFS time).

[0356] According to embodiments of the present invention, there may be a signaling that instructs whether or not to respond based on the CS result when responding to a trigger frame. For example, the CS Required subfield included in the trigger frame shown in Figure 16 may be a signaling that instructs whether or not to respond based on the CS result when responding to a trigger frame. For example, if the CS Required subfield is set to 1, it is possible to decide whether or not to respond based on the CS result when responding to a trigger frame containing the CS Required subfield.

[0357] For example, if CS Required subfield is set to 1, and the CS result is busy when responding to a trigger frame containing the CS Required subfield, then the system does not need to respond to the trigger frame. If CS Required subfield is set to 1, and the CS result is idle when responding to a trigger frame containing the CS Required subfield, then the system may respond to the trigger frame. For example, if CS Required subfield is set to 0, the system can decide whether or not to respond to a trigger frame containing the CS Required subfield without relying on the CS result. If the CS result is busy, then at least one of the physical CS and virtual CS may be busy. If the CS result is idle, then both the physical CS and virtual CS may be idle.

[0358] Furthermore, when responding to a TRS control field, it is possible to decide whether or not to respond without relying on the CS result.

[0359] Furthermore, trigger frames included in the same PPDU as the TRS control field can have their CS Required subfield set to 0 or 1. Alternatively, trigger frames included in the same PPDU as a frame containing the TRS control field can have their CS Required subfield set to 0 or 1.

[0360] As shown in Figure 25, the trigger frame and the frame containing the TRS control may be transmitted in the same PPDU. In this case, the CS Required subfield included in the trigger frame may be set to 0. Therefore, it is possible to respond to the trigger frame without relying on the CS result. Similarly, it is possible to respond to the TRS control without relying on the CS result.

[0361] According to one embodiment of the present invention, the CS Required subfield may be set when a trigger frame is transmitted. For example, the CS Required subfield may be set based on the length of the response indicated by the trigger frame. The UL Length subfield shown in Figure 16 can indicate the length of the response indicated by the trigger frame. The length of the TB PPDU in response to the trigger frame can be obtained based on the UL Length subfield value included in the trigger frame. Furthermore, setting the CS Required subfield based on the UL Length subfield may be limited to cases where the trigger frame is of an already set type. The type of the trigger frame may be indicated by the Trigger Type subfield shown in Figure 16. For example, if the trigger frame is a Basic, BSRP, MU-BAR, BQRP, GCR MU-BAR, or BFRP trigger frame, the CS Required subfield may be set based on the UL Length subfield.

[0362] In one embodiment, if the UL length subfield value is less than or equal to a previously set value (smaller or equal to), the CS Required subfield may be set to 0 or 1. In a more specific embodiment, if the UL length subfield value is less than or equal to a previously set value, the CS Required subfield may be set to 0. Also, if the UL length subfield value exceeds a previously set value (larger), the CS Required subfield may be set to 1. If the UL length subfield value exceeds a previously set value (larger), the CS Required subfield does not have to be set to 0.

[0363] According to one embodiment of the present invention, the previously set value may be 418. For example, when a condition based on the UL Length subfield is used together with the following condition 1 or condition 2, the previously set value may be 418.

[0364] (Condition 1) The trigger frame's RA (receiver address) is the MAC address of an individually addressed STA, and the trigger frame is aggregated into a single A-MPDU with either 1) a QoS Data frame whose Ack Policy is set to respond with an acknowledgment in a TB PPDU (HETP Ack), or 2) a Management frame that solicits an acknowledgment.

[0365] (Condition 2) The trigger frame is either a MU-BAR or a GCR MU-BAR trigger frame.

[0366] Condition 1 may be used in conjunction with the condition that the trigger frame is Basic, BSRP, MU-BAR, BQRP, or GCR MU-BAR.

[0367] The already set value 418 may correspond to a PPDU length of 584us. Also, 584us may be the maximum TB PPDU duration that can be instructed by TRS control. 584us may be the maximum HE TB PPDU duration that can be instructed by TRS control. 584us may be the sum of the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, HE-STF, HE-LTF, Data field, and PE field lengths of the TB PPDU. L-STF, L-LTF, L-SIG, and RL-SIG may be 8, 8, 4, and 4us, respectively. HE-SIG-A may be 8us. HE-STF may be 8us for the TB PPDU. HE-LTF is the TB PPDU that responds to TRS control and may be 16us. 4x HE-LTF with a GI (guard interval) of 3.2us may be 16us. The maximum value of the Data field that TRS control can specify may be the maximum number of symbols with a GI of 3.2us and the specified value. If the maximum number of symbols that can be specified is 32 symbols, the maximum value of the Data field that TRS control can specify may be 32 * 16us, i.e., 512us. Also, the maximum value of the PE field may be 16us. Therefore, the maximum TB PPDU duration that can be specified by TRS control may be (8 + 8 + 4 + 4 + 8 + 8 + 16 + 512 + 16)us, i.e., 584us.

[0368] Therefore, a trigger frame included in the same PPDU as a frame containing TRS control can have its CS Required subfield set to 0 based on whether its UL length subfield value is 418 or less. This is because a trigger frame and a frame containing TRS control included in the same PPDU must indicate the same response TB PPDU duration. Therefore, a trigger frame included in the same PPDU as a frame containing TRS control indicates a length less than or equal to the maximum length that TRS control can indicate, and since its UL length subfield value is already set to 418 or less, it can have its CS Required subfield set to 0. The embodiment shown in Figure 25 may also have its CS Required subfield set to 0 by the method described above.

[0369] If the CS Required subfield of a trigger frame included in the same PPDU as a frame containing TRS control is set to 1, the STA responding to TRS control will respond without basing its response on the CS result, while the STA responding to the trigger frame will respond based on the CS result. This could result in the resources allocated by the trigger frame being wasted if the STA fails to respond to the trigger frame.

[0370] According to other embodiments, the previously set value may be 76. For example, when a condition based on the UL length subfield is used together with the following condition 1 or condition 2, the previously set value may be 76.

[0371] (Condition 1) The trigger frame is a Basic, BSRP, MU-BAR, BQRP, or GCR MU-BAR trigger frame.

[0372] (Condition 2) The trigger frame is a BFRP trigger frame.

[0373] The already set value of 76 may correspond to the value of 128us. Also, 128us may be the duration of a HE TB PPDU with 4x HE-LTF and PE fields.

[0374] In the embodiment of the present invention, the already set value of the length corresponding to Time us may be calculated by the following formula 9 or formula 10.

[0375]

number

[0376]

number

[0377] In embodiments of the present invention, Ceil(x) may be the smallest integer greater than or equal to x. SignalExtension may be the length of the signal extension. The length of the signal extension may be 0us in the 5GHz or 6GHz band. The length of the signal extension may be 6us in the 2.4GHz band.

[0378] Figure 26 shows an example of the CS Required subfield settings and UL MU operation according to one embodiment of the present invention. In Figure 26, the same content as described in Figures 1 to 25 is omitted.

[0379] According to the embodiment described above, there may be cases where the trigger frame instructs to respond with HE TB PPDU and cases where it instructs to respond with EHT TB PPDU. Similarly, there may be cases where the TRS control instructs to respond with HE TB PPDU and cases where it instructs to respond with EHT TB PPDU.

[0380] According to embodiments of the present invention, the maximum TB PPDU duration that can be indicated by the TRS control field indicating the EHT TB PPDU response may be different from the maximum TB PPDU duration that can be indicated by the TRS control indicating the HE TB PPDU response. For example, the maximum TB PPDU duration that can be indicated by the TRS control indicating the EHT TB PPDU response may be longer than the maximum TB PPDU duration that can be indicated by the TRS control indicating the HE TB PPDU response. This is because, as mentioned above, the EHT PPDU may include a PE field of 20us. Alternatively, the method of indicating the length of the TRS control indicating the EHT TB PPDU response may differ from that of the TRS control indicating the HE TB PPDU response.

[0381] Therefore, when specifying the EHT TB PPDU when setting the CS Required subfield based on the UL length subfield, using the same pre-configured value (threshold) as explained in Figure 25 may result in wasted resources.

[0382] For example, when responding to a TRS control that solicits an EHT TB PPDU response, it is possible to respond without relying on the CS result. The trigger frame may be contained within the same PPDU as the frame containing the TRS control that solicits the EHT TB PPDU response. In this case, the trigger frame and the TRS control that solicits the EHT TB PPDU response can instruct the same response length.

[0383] In this case, the trigger frame can set the CS Required subfield based on a value derived from the maximum HE TB PPDU length that TRS control can specify, as explained in Figure 25. In this case, the trigger frame can set the CS Required subfield based on a value smaller than the maximum EHT TB PPDU length that TRS control can specify. Therefore, since the UL length subfield value included in the trigger frame is larger than the already set value used when setting the CS Required subfield, it is possible to set the CS Required subfield to 1.

[0384] As shown in Figure 26, a trigger frame can have the CS Required subfield set to 1. Furthermore, a TRS control may exist that is included in the same PPDU as the trigger frame. In this case, both the TRS control and the trigger frame can instruct an EHT TB PPDU. In this case, an STA responding to the TRS control will respond with an EHT TB PPDU without relying on the CS result, while an STA responding to the trigger frame can decide whether or not to respond with an EHT TB PPDU based on the CS result. Therefore, an STA responding to a trigger frame may be unable to respond if the CS result is busy. In this case, resources allocated by the trigger frame may be wasted. Because some resources were used to respond to the TRS control, those resources may become less available to other STAs.

[0385] Figure 27 shows yet another example of the CS Required subfield setting and UL MU operation according to one embodiment of the present invention.

[0386] The embodiment in Figure 27 may be a method for solving the problems described in Figures 25 and 26. Furthermore, the details mentioned above may be omitted in the embodiment in Figure 27.

[0387] According to one embodiment of the present invention, the pre-set value used when setting the CS Required subfield based on the UL length subfield described in Figures 25 and 26 may differ depending on which TB PPDU the trigger frame indicates. Alternatively, the pre-set value used when setting the CS Required subfield based on the UL length subfield may differ depending on which TB PPDU the trigger frame or TRS control included in the same PPDU indicates. According to one embodiment, when the trigger frame or TRS control solicits an HE TB PPDU, the pre-set value may be threshold 1, and when the trigger frame or TRS control solicits an EHT TB PPDU, the pre-set value may be threshold 2.

[0388] Alternatively, according to one embodiment of the present invention, when HE TB PPDU is indicated, the already set value may be threshold 1. Furthermore, the already set value can be determined using the methods described in Figures 22 to 24. For example, when EHT TB PPDU is presented and the PE duration is 16us or less, the already set value may be threshold 1. When EHT TB PPDU is presented and the PE duration is 20us, the already set value may be threshold 2.

[0389] According to one embodiment, the threshold 1 may be a value already set as described in Figure 25. That is, the threshold 1 may be 418 or 76, and the value already set by the conditions described in Figure 25 may be 418 or 76.

[0390] In one embodiment, threshold 2 may be a value greater than threshold 1. This is because the maximum duration of a TB PPDU that can be instructed by a TRS control that presents an EHT TB PPDU is greater than the maximum duration of a TB PPDU that can be instructed by a TRS control that presents an HE TB PPDU. For example, threshold 2 may be the same as the length value calculated by substituting the value of Time calculated by formula 11 into Time in formula 9 or formula 10.

[0391]

number

[0392] In the above equation 11, the L-STF length may be 8us. The L-LTF length may be 8us. The L-SIG length may be 4us. The RL-SIG length may be 4us. The U-SIG length may be 8us. The EHT-STF length may be 8us.

[0393] The EHT-LTF length may be 4 times the EHT-LTF length using a GI of 3.2us. Therefore, the EHT-LTF length may be 16us.

[0394] The Data field length can be based on the maximum length that the TRS control presenting the EHT TB PPDU can specify. For example, the Data field length can be based on the maximum number of OFDM symbols that the TRS control presenting the EHT TB PPDU can specify. The Data field length can be based on the product of the maximum number of OFDM symbols that the TRS control presenting the EHT TB PPDU can specify and the OFDM symbol length. The Data field length can be based on the product of the maximum number of OFDM symbols that the TRS control presenting the EHT TB PPDU can specify and the maximum OFDM symbol length. The maximum number of OFDM symbols may be 32. The maximum OFDM symbol length may be the symbol length using a GI of 3.2us. The maximum OFDM symbol length may be 16us. Therefore, the Data field length may be 32 * 16us (512us).

[0395] In one embodiment, the maximum length that can be instructed by the TRS control presenting the EHT TB PPDU and the maximum length that can be instructed by the TRS control presenting the HE TB PPDU may be the same. The maximum length that can be instructed by the TRS control presenting the EHT TB PPDU and the maximum number of OFDM symbols that can be instructed by the TRS control presenting the HE TB PPDU may be the same. This allows the EHT STA to perform the same operation as the HE STA based on TRS control, thus making the implementation of the EHT STA easier.

[0396] In other embodiments, the maximum length that a TRS control soliciting EHT TB PPDU can specify may differ from the maximum length that a TRS control soliciting HE TB PPDU can specify. The maximum length that a TRS control soliciting EHT TB PPDU can specify may differ from the maximum number of OFDM symbols that a TRS control soliciting HE TB PPDU can specify. This is because the signaling space that a TRS control can include is limited. For example, a TRS control soliciting EHT TB PPDU may include signaling that a TRS control soliciting HE TB PPDU does not. Therefore, a TRS control soliciting EHT TB PPDU can define a resolution of the maximum length or length that can be specified differently from that of a TRS control soliciting HE TB PPDU.

[0397] In one embodiment, the PE field length may be the maximum PE field length. The PE field length may be 20us. In another embodiment, the PE field length may be the PE field length as described in Figures 22 to 24. For example, the PE field length may be 16us when using a PE field of 16us or less as described in Figures 22 to 24. Also, the PE field length may be 20us when using a PE field of 20us as described in Figures 22 to 24.

[0398] Therefore, according to the described embodiment, the Time value may be as shown in the following formula 12.

[0399]

number

[0400] Furthermore, if we substitute the Time value into equation 10 using equation 12, then threshold 2 may be 421.

[0401] In conjunction with the embodiment described in Figure 25, the following can be stated: A trigger frame presenting an EHT TB PPDU can set the CS Required subfield to 1 if the UL length subfield is greater than threshold 2. Furthermore, a trigger frame presenting an EHT TB PPDU can set the CS Required subfield to 0 or 1 if the UL length subfield is less than or equal to threshold 2. The threshold 2 may be a value greater than 418. The threshold 2 may also be 421. Additionally, threshold 2 may be used in conjunction with the conditions described in Figure 25. For example, when a condition based on the UL length subfield is used in conjunction with the following condition 1 or condition 2, threshold 2 (e.g., a value of 421) can be used.

[0402] (Condition 1) The trigger frame's RA (receiver address) is the MAC address of an individually addressed STA, and the trigger frame is aggregated into a single A-MPDU with either 1) a QoS Data frame whose Ack Policy is set to respond with an acknowledgment in a TB PPDU (HETP Ack), or 2) a Management frame that instructs an acknowledgment.

[0403] (Condition 2) The trigger frame is either a MU-BAR or a GCR MU-BAR trigger frame.

[0404] Condition 1 may be used in conjunction with the condition that the trigger frame is Basic, BSRP, MU-BAR, BQRP, or GCR MU-BAR.

[0405] In other words, when specifying EHT TB PPDU under the condition that the already set value 418 is used when presenting HE TB PPDU, the already set value 421 can be used instead of 418.

[0406] In other embodiments, threshold 2 may be 79. The threshold 2 value of 79 may correspond to a value of 132us. The threshold 2 value of 79 may be the length obtained by substituting 132us for the Time value in formula A or formula B. Also, 132us may be the duration of an EHT TB PPDU having 4x EHT-LTF and PE fields.

[0407] In conjunction with the embodiment described in Figure 25, the following can be stated: A trigger frame presenting an EHT TB PPDU can set the CS Required subfield to 1 if the UL length subfield is greater than threshold 2. Furthermore, a trigger frame presenting an EHT TB PPDU can set the CS Required subfield to 0 or 1 if the UL length subfield is less than or equal to threshold 2. The threshold 2 may be a value greater than 76. The threshold 2 may be 79. The threshold 2 may also be used in conjunction with the conditions described in Figure 25. For example, the threshold 2 (e.g., a value of 79) can be used when the condition based on the UL length subfield is used in conjunction with the following condition 1 or condition 2.

[0408] (Condition 1) The trigger frame is a Basic, BSRP, MU-BAR, BQRP, or GCR MU-BAR trigger frame.

[0409] (Condition 2) The trigger frame is a BFRP trigger frame.

[0410] In other words, when presenting EHT TB PPDU under the condition that the already set value of 76 is used when presenting HE TB PPDU, the already set value of 79 can be used instead of 76.

[0411] As shown in Figure 27, the trigger frame may be transmitted in the same PPDU as the frame containing the TRS control.

[0412] The trigger frame and TRS control included in the sequence labeled "Sequence 1" may present an HE TB PPDU. Therefore, the PE field included in the HE TB PPDU presented at this time may be 16us or less. Furthermore, the trigger frame included in sequence 1 can have its CS Required subfield set based on threshold 1. For example, the trigger frame included in sequence 1 can have its CS Required subfield set based on whether the UL length subfield value is less than or equal to threshold 1. threshold 1 may be 418 or 76. If the trigger frame included in sequence 1 has an UL length subfield value less than or equal to threshold 1, the CS Required subfield can be set to 0 or 1. Therefore, it is possible to set the CS Required subfield to 0. If the trigger frame included in sequence 1 has an UL length subfield value greater than threshold 1, the CS Required subfield can be set to 1. For this reason, there may be cases where the CS Required subfield cannot be set to 0. Therefore, in the illustrated embodiment, neither the STA responding to TRS control nor the STA responding to the trigger frame is based on the CS result, and it is possible to send a TB PPDU response when scheduled.

[0413] The trigger frame and TRS control included in the sequence labeled "Sequence 2" may present an EHT TB PPDU. Therefore, the PE field included in the EHT TB PPDU presented at this time may be 20us or less. Furthermore, the trigger frame included in sequence 2 can have its CS Required subfield set based on threshold 2. As a more specific example, if the trigger frame included in sequence 2 presents a TB PPDU response containing a PE field of 20us, the CS Required subfield can be set based on threshold 2. If the trigger frame included in sequence 2 presents a TB PPDU response containing a PE field of 16us or less, the CS Required subfield can be set based on threshold 1. The following may be an example of using threshold 2. For example, the trigger frame included in sequence 2 can have its CS Required subfield set based on whether the UL length subfield value is less than or equal to threshold 2. threshold 2 may be 421 or 79. If a trigger frame included in sequence 2 has a UL length subfield value that is less than or equal to threshold 2, then the CS Required subfield can be set to 0 or 1. Therefore, it is possible to set the CS Required subfield to 0. Thus, if a frame containing TRS control is included in the same PPDU as the trigger frame, the UL length subfield of the trigger frame should be set to a value less than or equal to threshold 2, and therefore, it is possible to set the CS Required subfield included in the trigger frame to 0. Consequently, as explained in Figure 26, the STA responding to TRS control sends a TB PPDU without relying on the CS result, and the STA responding to the trigger frame does not send a TB PPDU response based on the CS result, thus solving the problem of wasted resources.For example, if the trigger frame included in sequence 2 has a UL length subfield value greater than threshold 2, the CS Required subfield can be set to 1. Therefore, there are cases where the CS Required subfield cannot be set to 0. Consequently, in the illustrated embodiment, both the STA responding to TRS control and the STA responding to the trigger frame can send a TB PPDU response when scheduled, without relying on the CS result.

[0414] In other embodiments, threshold 2 may be a smaller value than threshold 1. This has the advantage of preventing the unnecessary setting of the CS Required subfield to 1 for short PPDUs or short frames. For example, threshold 2 may be smaller than threshold 1 when the maximum response length or maximum number of OFDM symbols that a TRS control indicating an EHT TB PPDU can indicate is smaller than that of a TRS control indicating an HE TB PPDU. For example, when the maximum number of OFDM symbols that a TRS control indicating an EHT TB PPDU can indicate is 16, threshold 2 may be the same as the value obtained by substituting the following Time value into equation 9 or equation 10.

[0415] Time=8+8+4+4+8+8+16+16*16+16=328

[0416] Time=8+8+4+4+8+8+16+16*16+20=332

[0417] Therefore, threshold 2 may be 226 or 229.

[0418] Figure 28 shows an example of a method for setting the PE field when using A(aggregated)-PPDU according to one embodiment of the present invention.

[0419] As explained in Figure 24, the PPDUs included in A-PPDU may have the same PE field duration. Therefore, the PE field duration of an EHT PPDU included in A-PPDU may be 16us or less. More specifically, the PE field duration of an EHT TB PPDU included in A-PPDU may be 16us or less. More specifically, the PE field duration of an EHT TB PPDU included in A-PPDU may be set to the Default PE duration subfield value included in the HE Operation element.

[0420] To achieve this, when transmitting a TRS control that indicates an EHT TB PPDU to be sent as an A-PPDU (or constituting an A-PPDU), the signaling indicating the PE duration can be set to a value of 16us or less. Alternatively, when transmitting a TRS control that indicates an EHT TB PPDU to be sent as an A-PPDU (or constituting an A-PPDU), the signaling indicating the PE duration can be set to use the Default PE duration subfield value included in the HE Operation element as the duration of the PE field.

[0421] Alternatively, when responding to a TRS control requesting an EHT TB PPDU to be sent as an A-PPDU (or constituting an A-PPDU), the PE duration of the transmitted PE field can be set to a value of 16us or less. For this purpose, the responding STA needs to know whether the TB PPDU transmission is sent as an A-PPDU (or constituting an A-PPDU).

[0422] Alternatively, when instructing an A-PPDU, the TRS control that instructs an EHT TB PPDU does not need to be included in the PPDU. This is because there is no way to know whether the responding STA will respond to an A-PPDU. Also, this is because the TRS control does not include signaling that instructs the PE duration.

[0423] In the embodiment shown in Figure 28, the same information as that described in Figures 1 to 27 may be omitted.

[0424] According to an embodiment of the present invention, the pre-set value used when setting the CS Required subfield based on the UL length subfield described in Figures 25 to 27 may differ depending on whether the trigger frame indicating an EHT TB PPDU indicates an EHT TB PPDU included in an A-PPDU or an EHT TB PPDU not included in an A-PPDU. In other words, the pre-set value used when setting the CS Required subfield based on the UL length subfield may differ depending on whether the trigger frame indicating an EHT TB PPDU includes a frame indicating an HE TB PPDU in the PPDU containing the trigger frame.

[0425] According to an embodiment of the present invention, the method described in Figure 27 can be used when the trigger frame indicating EHT TB PPDU is not included in A-PPDU. That is, when the trigger frame indicating EHT TB PPDU is not included in A-PPDU, threshold 2 as described in Figure 27 can be used. More specifically, when the trigger frame indicating EHT TB PPDU is not included in A-PPDU, the CS Required subfield can be set based on the already set values ​​of 421 or 79 as described in Figures 25 to 27.

[0426] Furthermore, when a trigger frame indicating an EHT TB PPDU is included in the A-PPDU, the method described in Figures 25 and 26 can be used. Alternatively, when a trigger frame indicating an EHT TB PPDU is included in the A-PPDU, threshold 1 described in Figure 27 can be used. More specifically, when a trigger frame indicating an EHT TB PPDU is included in the A-PPDU, the CS Required subfield can be set based on the already set values ​​of 418 or 76 as described in Figures 25 to 27. When a trigger frame indicating an EHT TB PPDU is included in the A-PPDU, the CS Required subfield can be set based on the same already set values ​​as in the case of a trigger frame indicating an HE TB PPDU.

[0427] Referring to Figure 28, one frame or multiple frames contained within a single PPDU can indicate an A-PPDU. For example, an HE TB PPDU and an EHT TB PPDU can be indicated simultaneously. For example, referring to sequence 1, the PPDU may contain a TRS control indicating an HE TB PPDU and a TRS control indicating an EHT TB PPDU. In this case, the PE field of the PPDU responding to the TRS control indicating an HE TB PPDU and the PPDU responding to the TRS control indicating an EHT TB PPDU may have the same duration. The same duration may be 16us or less in length. Alternatively, the same duration may be the value indicated by the Default PE duration subfield included in the HE Operation element.

[0428] Referring to Sequence 2, the trigger frame can solicit the EHT TB PPDU that constitutes the A-PPDU. In this case, when setting the CS Required subfield included in the trigger frame, it can be based on threshold 1 as described in Figure 27. The threshold 1 may be a previously set value used when setting the CS Required subfield included in a trigger frame indicating an HE TB PPDU based on the UL length subfield value. The threshold 1 may be 418 or 76. The trigger frame indicating an EHT TB PPDU can indicate a response of the same length as the TRS control or trigger frame indicating an HE TB PPDU. Furthermore, the trigger frame indicating an EHT TB PPDU can set the CS Required subfield based on the same previously set value as the trigger frame indicating an HE TB PPDU. Therefore, the trigger frame indicating an EHT TB PPDU and the trigger frame indicating an HE TB PPDU can set the CS Required subfield to the same value. Furthermore, when a trigger frame indicating an EHT TB PPDU is transmitted together with a TRS control indicating an HE TB PPDU, and the CS Required subfield is set based on threshold 1, it is possible to set the CS Required subfield to 0 or 1. That is, it is possible to set the CS Required subfield to 0. Therefore, among the A-PPDUs presented in the embodiments of the present invention, it is possible to prevent a situation where the HE TB PPDU is transmitted without basing its response on the CS result, and the EHT TB PPDU decides whether or not to respond based on the CS result.

[0429] Figure 29 shows an example of a method for specifying the format of a TB PPDU according to one embodiment of the present invention.

[0430] As described in the above embodiment, a method may be required in which the frame that triggers the PPDU instructs the response PPDU format. For example, the PPDU format may mean the TB PPDU format. The embodiment in Figure 29 may be a specific embodiment of the TB PPDU format instruction method described above. In this embodiment, the above details may be omitted.

[0431] According to an embodiment of the present invention, the format of the PPDU responding to the trigger frame can be determined based on the User Info field included in the trigger frame. Alternatively, the format of the PPDU responding to the trigger frame can be specified by the User Info field included in the trigger frame. In the present invention, the User Info field that determines or specifies the format of the PPDU can be called the Special User Info field.

[0432] In one embodiment, the Special User Info field may be a User Info field in which the AID12 subfield included in the Special User Info field is set to a value that has already been set. For example, the value that has already been set may be 2007. Also, the value that has already been set may be a value that AP does not assign as AID (association ID). Furthermore, the format of the Special User Info field may differ from that of other User Info fields. That is, the subfields included in the Special User Info field may differ from those included in other User Info fields. Also, the Special User Info field and other User Info fields may both include the AID12 subfield in the same position. For example, the first 12 bits of the Special User Info field and User Info fields other than the Special User Info field may be the AID12 subfield. For example, B0 to B11 may be the AID12 subfield of the Special User Info field and User Info fields other than the Special User Info field.

[0433] Furthermore, the trigger frame may include a subfield indicating whether or not it contains a Special User Info field. This subfield can be called the Special User Info Field Present subfield. For example, the Special User Info Field Present subfield may exist in the Common Info field. For instance, bit B55 of the Common Info field may be the Special User Info Field Present subfield. If the Special User Info Field Present subfield is set to 1, the trigger frame may not contain a Special User Info field. Conversely, if the Special User Info Field Present subfield is set to 0, the trigger frame may contain a Special User Info field. This is because, in the 802.11ax standard, bit B55 of the Common Info field is already set to the value 1.

[0434] An STA receiving a trigger frame can determine whether or not the Special User Info field is included based on the Special User Info Field Present subfield, making it easier to determine whether or not the Special User Info field is included compared to when the Special User Info Field Present subfield does not exist. Furthermore, if a trigger frame is received by an STA that is not associated with the AP that sent the trigger frame, the STA can determine, based on the Special User Info Field Present subfield, whether the User Info field, which is set to a pre-configured value indicating the Special User Info field in the AID12 subfield, is the Special User Info field (i.e., whether or not it actually indicates the 12 LSBs of the AID). For example, when instructing an RA-RU for an unassociated STA, if the trigger frame is received by an STA that is not associated with the AP that sent the trigger frame, the STA can act based on the trigger frame. Additionally, the STA can perform spatial reuse operations based on a trigger frame or TB PPDU from a BSS that it is not associated with.

[0435] Furthermore, if the trigger frame includes a Special User Info field, the Special User Info field may be positioned at the very beginning of the User Info fields. Alternatively, the Special User Info field may be positioned immediately after the Common Info field. This may be to allow the STA receiving the trigger frame to easily parse the Special User Info field.

[0436] According to an embodiment of the present invention, the format of the PPDU responding to a trigger frame can be determined based on whether or not the trigger frame contains a Special User Info field. For example, if the trigger frame contains a Special User Info field, the format of the PPDU responding to the trigger frame may be EHT TB PPDU. Also, if the trigger frame does not contain a Special User Info field, the format of the PPDU responding to the trigger frame may be HE TB PPDU. Furthermore, as mentioned above, there may be a Special User Info Field Present subfield, which is a signaling element indicating whether or not the trigger frame contains a Special User Info field. Therefore, it can also be said that the format of the PPDU responding to a trigger frame can be determined based on the Special User Info Field Present subfield. For example, if the Special User Info Field Present subfield is set to 0, the format of the PPDU responding to the trigger frame may be EHT TB PPDU. Also, if the Special User Info Field Present subfield is set to 1, the format of the PPDU responding to the trigger frame may be HE TB PPDU.

[0437] Furthermore, if the trigger frame includes a Special User Info field, the User Info field included in the trigger frame may be an EHT variant User Info field. Also, if the trigger frame does not include a Special User Info field, the trigger frame does not need to include an EHT variant User Info field. If the trigger frame does not include a Special User Info field, the trigger frame may include only an HE variant User Info field.

[0438] The method of indicating RUs may differ depending on whether the User Info field is an EHT variant or an HE variant. For example, the interpretation of a User Info field may differ depending on whether the RU Allocation subfield it contains is an EHT variant or an HE variant. For example, the RU Allocation subfield contained in an EHT variant User Info field may be encoded to indicate RUs supported by the EHT standard. Similarly, the RU Allocation subfield contained in an HE variant User Info field may be encoded to indicate RUs supported by the HE standard.

[0439] Furthermore, when interpreting a RU indicated based on the EHT variant User Info field, it is necessary to rely on two or more subfields. These two or more subfields may include the RU Allocation subfield and the PS160 subfield. The RU Allocation subfield may be located immediately after the AID12 subfield, as shown in Figure 16. The RU Allocation subfield may also be 8 bits. The PS160 subfield can indicate which subchannel the RU indicated by the RU Allocation subfield resides in. Alternatively, the PS160 subfield can indicate which subchannel the RU indicated by the User Info field resides in. In this case, the unit indicating which subchannel it is may be a 160MHz subchannel. The PS160 subfield can indicate whether the indicated RU resides in the primary 160MHz channel or the secondary 160MHz channel. The PS160 subfield may be located immediately before the Trigger Dependent User Info field. The PS160 subfield may be bit B39 of the User Info field. The PS160 subfield may be 1 bit.

[0440] Furthermore, when interpreting a RU indicated based on the HE variant User Info field, it may be based on a single subfield. This single subfield may be the RU Allocation subfield. That is, the location of the RU indicated by the HE variant User Info field can be determined solely based on the RU Allocation subfield contained within the HE variant User Info field.

[0441] Referring to Figure 29, the trigger frame may include a Special User Info field. Whether a User Info field is a Special User Info field may be determined based on the AID12 subfield included in the User Info field. For example, if the AID12 subfield included in the User Info field is a value that has already been set, then the User Info field may be a Special User Info field. Referring to Figure 29, the value that has already been set may be 2007. Also, referring to Figure 29, the Special User Info field may be located immediately after the Common Info field and at the very beginning of the User Info fields. There may also be a Special User Info Field Present subfield, which is a signaling element indicating whether the trigger frame includes a Special User Info field. Referring to Figure 29, the Special User Info Field Present subfield may be included in the Common Info field. If the Special User Info Field Present subfield is set to 0, then the trigger frame may include a Special User Info field. As shown in Figure 29, if the trigger frame contains a Special User Info field, the response PPDU format for it may be EHT TB PPDU.

[0442] In addition, according to an additional embodiment, the format of the PPDU in response to the trigger frame can be determined based on whether the trigger frame contains a Special User Info field and a subfield indicating the TB PPDU format. In the present invention, the subfield indicating the TB PPDU format can be called the HE / EHT P160 subfield. In a more specific embodiment, the HE / EHT P160 subfield may indicate the TB PPDU format for an already configured channel. For example, the HE / EHT P160 subfield may indicate the TB PPDU format for a primary 160MHz channel (P160 channel). For example, if the HE / EHT P160 subfield value is 1, it may indicate to respond with HE TB PPDU. Alternatively, if the HE / EHT P160 subfield value is 0, it may indicate to respond with EHT TB PPDU. The HE / EHT P160 subfield may be 1 bit.

[0443] Referring to Figure 29, the HE / EHT P160 subfield may be included in the Common Info field. More specifically, the HE / EHT P160 subfield may be included in bit B55 of the Common Info field.

[0444] Therefore, when indicating and determining the TB PPDU format based on the Special User Info field and the HE / EHT P160 subfield, the following actions can be taken: When the HE / EHT P160 subfield indicates EHT TB PPDU, the response to the trigger frame can be in EHT TB PPDU format. That is, when the HE / EHT P160 subfield indicates EHT TB PPDU, the response to the trigger frame can be in EHT TB PPDU format regardless of the assigned RU position. Also, when the HE / EHT P160 subfield indicates EHT TB PPDU, the Special User Info field may always be included. That is, the Special User Info Field Present subfield can also indicate that the Special User Info field is included.

[0445] If the HE / EHT P160 subfield indicates an HE TB PPDU, the TB PPDU format can be indicated and determined based on the assigned RU location when responding to the trigger frame. If the HE / EHT P160 subfield indicates an HE TB PPDU and includes RUs assigned to an already configured channel indicated by the HE / EHT P160 subfield (e.g., the P160 channel), the response can be in HE TB PPDU format. Conversely, if the HE / EHT P160 subfield indicates an HE TB PPDU and does not include RUs assigned to an already configured channel indicated by the HE / EHT P160 subfield (e.g., the P160 channel) (for example, if it includes RUs assigned to the secondary 160MHz channel (S160 channel)), the response can be in EHT TB PPDU format. Whether or not RUs assigned to an already configured channel are included can be determined based on the RU Allocation subfield and the PS160 subfield. More specifically, if an already configured channel is a P160 channel, whether or not the RU assigned to the already configured channel is included can be determined based on the PS160 subfield.

[0446] Furthermore, specifying and determining the TB PPDU format based on the HE / EHT P160 subfield and the assigned RU position may be limited to cases where the trigger frame includes a Special User Info field. If the trigger frame includes a Special User Info field, the trigger frame may include the HE / EHT P160 subfield and the PS160 subfield. If the trigger frame does not include a Special User Info field, it is always possible to respond to the trigger frame using HE TB PPDU. Also, as mentioned above, whether or not a Special User Info field is included can be determined based on the Special User Info Field Present subfield. Therefore, when we say that the trigger frame includes a Special User Info field and does not include one, it means that the Special User Info Field Present subfield is set to include a Special User Info field and that it is set not to include a Special User Info field, respectively.

[0447] In this invention, any description of instructing or determining to use EHT TB PPDU when responding to a trigger frame may be replaced with an invention that instructs or determines to use either EHT TB PPDU or NEXT TB PPDU. Furthermore, whether to use EHT TB PPDU or NEXT TB PPDU may be determined based on the Format Identifier subfield. That is, the TB PPDU format indicated by the Format Identifier subfield can be used. For example, if the Format Identifier subfield indicates EHT, EHT TB PPDU can be used.

[0448] The Special User Info field may include the AID12 subfield and information required when responding to a trigger frame. The information required when responding to a trigger frame may include information contained in the preamble of the PPDU responding to the trigger frame. For example, the information required when responding to a trigger frame may include information contained in the U-SIG field of the PPDU responding to the trigger frame. Figure 29 may include an example of the information contained in the U-SIG field. Referring to Figure 29, the Special User Info field may include the AID12, PHY Version ID, UL Bandwidth Extension, Spatial Reuse 1, Spatial Reuse 2, U-SIG Disregard And Validate, Reserved, and Trigger Dependent User Info fields. The fields mentioned may exist in the order they are mentioned. The fields mentioned may have 12, 3, 2, 4, 4, 12, 3, and variable bits, respectively. The PHY Version ID field may be the Format Identifier subfield, the PHY version identifier subfield, or the PHY version field mentioned above. An STA responding to a trigger frame can set the U-SIG field contained in the responding PPDU based on the Special User Info field contained in the trigger frame. For example, the subfield values ​​contained in the Special User Info field can be copied to the subfields contained in the responding U-SIG field. The subfields copied to the subfields contained in the U-SIG field may be the PHY Version ID, Spatial Reuse 1, Spatial Reuse 2, and U-SIG Disregard And Validate subfields.

[0449] Alternatively, the subfields included in the U-SIG field of the responding PPDU can be set based on the subfield values ​​included in the Special User Info field. The subfield used to set the U-SIG field based on the subfields included in the Special User Info field may be the UL Bandwidth Extension subfield. For example, the bandwidth (BW) subfield included in the U-SIG field of the responding PPDU can be set based on the UL Bandwidth Extension subfield included in the Special User Info field and the UL BW subfield included in the Common Info field (see Figure 16).

[0450] Furthermore, the existence and length of the Trigger Dependent User Info field contained within the Special User Info field may depend on the type of the trigger frame. That is, the existence and length of the Trigger Dependent User Info field contained within the Special User Info field may depend on which variant the trigger frame is. The type of the trigger frame may be indicated and determined by the Trigger Type subfield contained within the Common Info field (see Figure 16).

[0451] Figure 30 shows STA, TXVECTOR, and RXVECTOR according to one embodiment of the present invention.

[0452] According to one embodiment of the present invention, the station may be a logical entity including MAC (medium access control) and PHY (physical layer). The station may be a logical entity including singly addressable MACs and PHYs. Alternatively, the station may be an entity that provides PHY and MAC functions (services). Furthermore, the PHY may be a physical layer interface to a wireless medium. Furthermore, the MAC may be in contact with the link layer.

[0453] MAC can be replaced with MAC layer. PHY can be replaced with physical layer or PHY layer.

[0454] Furthermore, the MAC and PHY may be connected via an interface. The interface may include TXVECTOR, RXVECTOR, PHYCONFIG_VECTOR, and TRIG_VECTOR.

[0455] The MAC can communicate PPDU-specific transmission parameters to the PHY using TXVECTOR. Specifically, when a station transmits a PPDU, the MAC can communicate parameters associated with the transmission of the PPDU to the PHY using TXVECTOR. The parameters contained in TXVECTOR can be called TXVECTOR parameters. TXVECTOR may be a vector containing TXVECTOR parameters. The PHY can transmit the PPDU based on the received TXVECTOR parameters. For example, the PHY can encode and transmit the PPDU using TXVECTOR parameters. The PHY can also set the values ​​of fields included in the PPDU's preamble based on TXVECTOR parameters. The types of TXVECTOR parameters contained in TXVECTOR may vary depending on the PHY format used. TXVECTOR may be included in PHY-TXSTART and request primitive.

[0456] The PHY can use RXVECTOR to transmit the parameters of a received PPDU to the MAC. Specifically, when a station receives a PPDU, the PHY can transmit the parameters obtained from the PPDU to the MAC using RXVECTOR. The parameters contained in RXVECTOR can be called RXVECTOR parameters. RXVECTOR may be a vector containing RXVECTOR parameters. For example, the PHY can set RXVECTOR parameters based on fields included in the preamble of the received PPDU and transmit RXVECTOR to the MAC. Also, the types of RXVECTOR parameters contained in RXVECTOR may differ depending on the PHY format used. RXVECTOR may be contained in PHY-RXSTART.indication primitive and PHY-RXEND.indication primitive.

[0457] The TXVECTOR or RXVECTOR parameter may include at least one of the following: FORMAT, EHT_PPDU_TYPE, L_LENGTH, L_DATARATE, RSS, MCS, CH_BANDWIDTH, INACTIVE_SUBCHANNELS, PSDU_LENGTH, TXOP_DURATION, and SPATIAL_REUSE, RU_ALLOCATION, TRIGGER_METHOD, BSS_COLOR, UPLINK_FLAG, and STA_ID. FORMAT can specify the format of the PPDU. EHT_PPDU_TYPE can specify whether the EHT PPDU is transmitted by DL OFDMA, single-user transmission, or sounding NDP. L_LENGTH can specify the value used to calculate the value of the Length field in the L-SIG field. L_DATARATE can specify the data rate of the PPDU. FEC_CODING can specify the FEC encoding method. Specifically, FEC_CODING can specify whether BCC coding or LDPC coding is used. RSSI can specify the RSSI of the signal including the PPDU. MCS can specify the modulation and coding scheme of the PPDU's data field. CH_BANDWIDTH can specify the channel bandwidth of the PPDU. INACTIVE_SUBCHANNELS can specify the punctured subchannels. In this case, INACTIVE_SUBCHANNELS can specify subchannels punctured in 20MHz increments. PSDU_LENGTH can specify the number of octets of the PSDU. NUM_STS can specify the number of spatial streams. TXOP_DURATION can specify the TXOP duration. SPATIAL_REUSE can specify the spatial reuse (SR) parameter. SPATIAL_REUSE can specify at least one of the following: whether or not space reuse is permitted, the extent to which space reuse is permitted, and the values ​​required to be set when using space reuse.RU_ALLOCATION can specify the configuration of the RU or MRU (multiple RU) to which the PPDU is sent. BSS_COLOR can specify the BSS color of the BSS to which the station sending the PPDU belongs. TRIGGER_METHOD can specify how the transmission of the TB PPDU is indicated. Specifically, TRIGGER_METHOD can specify whether the transmission of the TB PPDU was triggered by a trigger frame or by the TRS Control subfield. UPLINK_FLAG can specify whether the PPDU is sent by an AP. STA_ID can specify a list containing the IDs of the stations receiving the PPDU.

[0458] In Figure 30, the station (STA) may include a MAC and a PHY. The MAC can transmit a TXVECTOR to the PHY. The PHY can transmit a PPDU based on the TXVECTOR. The PHY can also receive PPDUs. The PHY can set an RXVECTOR based on the received PPDU. The PHY can transmit the RXVECTOR to the MAC. The MAC can operate based on the RXVECTOR.

[0459] Figure 31 shows a frame format and a field format according to an embodiment of the present invention.

[0460] Figure 31(a) shows the format of a MAC frame. A MAC frame may include a MAC header, a Frame Body, and an FCS. The MAC header may also include a Frame Control field, a Duration / ID field, a MAC address field, a Sequence Control field, a QoS Control field, and an HT Control field. The Frame Control field can indicate the frame type and subtype with its Type and Subtype fields, respectively. The Frame Control field can also indicate whether the frame includes an HT Control field with its +HTC subfield. The Duration / ID field can indicate the duration value. The Duration / ID field can indicate the duration value if the frame is not a PS-Poll frame. A station receiving a MAC frame can also set the NAV (network allocation vector) based on the duration value. The Duration / ID field can indicate an ID, such as an AID. The Duration / ID field can indicate an ID if the frame is a PS-Poll frame. The MAC address field may also include one or more address fields. The Address field can indicate the MAC address. Furthermore, the address field may include at least one of the following fields: BSSID (basic service set identifier), SA (source address), DA (destination address), TA (transmitting STA address or transmitter address), and RA (receiving STA address or receiver address (RA)). Additionally, the Sequence Control field can specify a fragment number or a sequence number.Furthermore, the QoS Control field can specify at least one of the following data contained in the MAC frame: TID, Ack policy, TXOP limit, buffer state, and queue size. The QoS Control field may also further include the aforementioned RDG / More PPDU subfield and AC Constraint subfield. Specifically, the QoS Control field included in the DMG PPDU may further include the RDG / More PPDU subfield and AC Constraint subfield.

[0461] The HT Control field may further include the aforementioned RDG / More PPDU subfield and AC Constraint subfield. The RDG / More PPDU subfield can signal whether a PPDU containing the RDG / More PPDU subfield contains an RDG, or whether there is a PPDU following a PPDU containing the RDG / More PPDU subfield.

[0462] The AC Constraint subfield can indicate whether the TID or AC transmitted by the MAC frame is restricted.

[0463] The HT Control field may be a 4-octet, 32-bit field.

[0464] The MAC header and the fields contained within the MAC header may have a predetermined length.

[0465] The Frame Body field may contain the frame's content. Specifically, the Frame Body field may contain information corresponding to the frame type and subtype.

[0466] The FCS field may contain an FCS (frame check sequence). The value of the FCS field may be used for both the MAC header and the Frame Body field to check whether the MAC header and Frame Body field contain incorrect values.

[0467] Figure 31(b) shows the format of the HT Control field. As previously mentioned, the HT Control field may include the AC Constraint subfield and the RDG / More PPDU subfield.

[0468] The HT Control field may include bits B0 to B31. In this case, bits B30 and B31 may be the AC Constraint subfield and the RDG / More PPDU subfield, respectively. In this case, the HT Control field may be an HT variant or a VHT variant. The HT Control field may have multiple variants. For example, the HT Control field may be an HT variant, a VHT variant, an HE variant, an EHT variant, or a standard variant after EHT. The HE variant described herein may be a standard variant after HE. The HT Control field may also include signaling to indicate which variant the HT Control field is. For example, some bits of the HT Control field can indicate which variant the HT Control field is. For example, if the value of bit B0 is 0, the HT Control field may be an HT variant. Also, if the value of bit B0 is 1, the HT Control field may be one of the VHT variant, an HE variant, or an EHT variant. Furthermore, if the value of the B0 bit is 1 and the value of the B1 bit is 0, the HT Control field may be a VHT variant. Also, if the value of the B0 field is 1 and the value of the B1 field is 1, it may be an HE variant or an EHT variant. Alternatively, if the value of the B0 bit is 1 and the value of the B1 bit is 1, the HT Control field may be an HE variant, an EHT variant, or a standard variant after EHT.

[0469] According to one embodiment, when the HT Control field is an HE variant, an EHT variant, or a standard variant after EHT, the HT Control field may include an A-Control subfield. A-Control can mean aggregated control. The A-Control subfield may contain one or more pieces of control information. For example, bits B2 to B31 of the HT Control field may be the A-Control subfield.

[0470] Figure 31(c) shows the format of the A-Control subfield in Figure 31(b). Referring to Figure 31(c), the A-Control subfield may include a Control List subfield and a Padding subfield. The Control List subfield may contain one or more control information. The Control List subfield may also contain one or more Control subfields. The Padding subfield may or may not be included in the A-Control subfield. For example, the length of the Padding subfield may be the remainder obtained by subtracting the length of the Control List subfield from the length of the pre-specified A-Control subfield. In a specific embodiment, the Padding subfield may be set to a pre-set value. Alternatively, the Padding subfield may have a pre-specified number of start bits set to a pre-specified value.

[0471] Figure 31(d) shows the format of the Control subfield mentioned in Figure 31(c). In the embodiment of Figure 31(d), the Control subfield may include a Control ID subfield and a Control Information subfield. The Control ID subfield can indicate whether or not it contains the content of the Control Information subfield, or what kind of control information the Control subfield containing the Control ID subfield contains. The station can also determine the length of the Control Information subfield based on the value of the Control ID subfield. The Control ID subfield may be a 4-bit field. The information that the Control subfield may contain may include the aforementioned TRS (triggered response scheduling) Control subfield. The Control subfield may contain the TRS field, which is information that triggers the response of the station that receives the Control subfield. The value of the Control ID corresponding to the TRS field may be 0. The Control subfield may also contain information about the operating mode (OM). The value of the Control ID corresponding to OM may be 1. The Control subfield may also contain information about link adaptation. The value of the Control ID corresponding to the link adaptation information may be 2. The Control subfield may also contain information about the buffer, specifically the BSR (buffer status report). The Control ID value corresponding to the BSR may be 3. The Control subfield may also contain information about UL power headroom. The UL power headroom information may indicate how much additional power is available for transmission or may be a value used for power pre-correction. The Control ID value corresponding to UL power headroom may be 4.The Control subfield may also include a signaling indicator of the subchannel's status, such as a BQR (bandwidth query report). The Control ID value corresponding to the BQR may be 5. The BQR may be a signaling indicator of whether the subchannel is available. The Control subfield may also include information about CAS (command and statusCAS). The Control ID value corresponding to CAS may be 6.

[0472] Figure 31(e) shows the Control Information subfield corresponding to the TRS mentioned in Figure 31(d). Figure 31(e) shows the Control Information subfield when the value of the Control ID subfield contained within the Control subfield is 0. The TRS Control subfield includes the TRS, and in this specification, the TRS Control subfield, TRS Control, TRS, and TRS information may be used interchangeably. Referring to Figure 31(e), the TRS Control may include the UL Data Symbols subfield, the RU Allocation subfield, the AP Tx Power subfield, the UL Target Receive Power subfield, the UL MCS subfield, and the Reserved subfield. The subfields mentioned may be 5 bits, 8 bits, 5 bits, 5 bits, 2 bits, and 1 bit, respectively, and may be arranged in the order shown in Figure 31(e).

[0473] TRS Control may include information that triggers the transmission of a TB PPDU. The TB PPDU may include an HE TB PPDU, an EHT TB PPDU, or a NEXT TB PPDU. A station that receives TRS Control can transmit a TB PPDU based on the TRS Control it received. For example, after a station receives a PPDU containing TRS Control, the station can immediately transmit a TB PPDU. In this case, "immediately" can mean "after SIFS after receiving the PPDU." APs can transmit TRS Control. Also, a non-AP station can receive TRS Control and transmit a TB PPDU in response to the TRS Control.

[0474] The UL Data Symbols subfield can specify the number of OFDM symbols to be included in the Data field of the TB PPDU transmitted in response to TRS Control. For example, the value of the UL Data Symbols subfield may be set to the number of OFDM symbols minus 1. In this case, when a station transmits a TB PPDU in response to TRS Control, the station can set the number of OFDM symbols in the Data field of the TB PPDU to the value of the UL Data Symbols subfield included in TRS Control plus 1.

[0475] The RU Allocation subfield can specify the resource unit (RU) that the station will use when responding to TRS Control.

[0476] The AP Tx Power subfield can indicate the transmit power when a station transmits a PPDU containing the AP Tx Power subfield. The transmit power may be indicated in dBm / 20MHz units. The AP Tx Power subfield can also indicate the combined transmit power at all antenna transmit connectors. For example, the transmit power value indicated by the AP Tx Power subfield may be (-20 + 2 * (value of AP Tx Power subfield)) in dBm / 20MHz units.

[0477] The UL Target Receive Power subfield can indicate the expected receive signal power of an AP. It can also indicate the average expected receive signal power across multiple antennas, measured at the AP's antenna connector. Furthermore, the UL Target Receive Power subfield can indicate the signal power measured at RUs assigned later than the RL-SIG field. For example, the UL Target Receive Power subfield can indicate the expected receive signal power at the assigned RUs for the HE portion and EHT portion of an HE TB PPDU and an EHT TB PPDU, respectively.

[0478] The UL MCS subfield can indicate the MCS to use when sending a TB PPDU in response to a TRS Control that contains the UL MCS subfield. The UL MCS subfield can indicate a standard MCS index corresponding to the format of the TB PPDU sent in response to a TRS Control that contains the UL MCS subfield. For example, when responding to a TRS Control with an HE TB PPDU, the UL MCS subfield included in the TRS Control can indicate the HE MCS index. When responding to a TRS Control with an EHT TB PPDU, the UL MCS subfield included in the TRS Control can indicate the EHT MCS index.

[0479] Figure 32 shows the UL MU operation of a station according to an embodiment of the present invention and the operation by which the station determines the TB PPDU format.

[0480] In an embodiment of the present invention, multiple stations can perform uplink transmission to an AP based on UL MU operation.

[0481] For example, an AP can send a triggering frame to one or more stations (non-AP stations) participating in the UL MU operation. The triggering frame may be used to initiate the UL MU operation. A station that receives the triggering frame may send a PPDU to the station that sent the triggering frame (AP) as a response to the triggering frame. The UL MU operation may include sending a triggering frame and sending a response to the triggering frame. The PPDU sent as a response to the triggering frame may be sent after SIFS from the end of the PPDU containing the triggering frame.

[0482] A triggering frame may be a frame that solicits a TB PPDU. A triggering frame may also include 1) a trigger frame, or 2) a frame containing TRS Control. Responses to a triggering frame may be transmitted in TB PPDU format. For example, HE TB PPDU, EHT TB PPDU, or NEXT TB PPDU may be transmitted as a response to a triggering frame. A method may exist for determining which TB PPDU format to use as a response to a triggering frame. Furthermore, the method for determining which TB PPDU format to use as a response to a triggering frame may differ depending on the type of triggering frame.

[0483] In the embodiment shown in Figure 32, the station can receive a triggering frame. The triggering frame may be a trigger frame, or it may be a frame containing TRS Control. When the triggering frame is a trigger frame, the station can determine the format of the TB PPDU to respond to based on the first method. The station can also transmit a TB PPDU as a response to the triggering frame using the TB PPDU format determined based on the first method. When the triggering frame is a frame containing TRS Control, the station can determine the format of the TB PPDU to respond to based on the second method. The station can also transmit a TB PPDU as a response to the triggering frame using the TB PPDU format determined based on the second method.

[0484] When the triggering frame is a trigger frame, the station can set the TXVECTOR parameter TRIGGER_METHOD to TRIGGER_FRAME. When the triggering frame is a frame containing TRS Control, the station can set the TXVECTOR parameter TRIGGER_METHOD to TRS. Therefore, in this specification, when the triggering frame is a trigger frame, it is the same as when the TXVECTOR parameter TRIGGER_METHOD is TRIGGER_FRAME, and it may also be the same as when the triggering frame is a frame containing TRS Control and when the TXVECTOR's TRIGGER_METHOD is TRS. When the station transmits an HE TB PPDU, the TXVECTOR parameter FORMAT may be set to HE_TB. When the station receives an HE TB PPDU, the station can set the RXVECTOR parameter FORMAT to HE_TB. When the station transmits an EHT TB PPDU, the station can set the TXVECTOR's FORMAT to EHT_TB. When receiving an EHT TB PPDU, the RXVECTOR's FORMAT may be set to EHT_TB. When a station transmits an HE TB PPDU, the TXVECTOR's FORMAT may be the same as when it is an HE_TB station, and when a station transmits an EHT TB PPDU, the TXVECTOR's FORMAT may be the same as when it is an EHT_TB station. Also, when a station receives an HE TB PPDU, the RXVECTOR's FORMAT may be the same as when it is an HE_TB station, and when a station receives an EHT TB PPDU, the RXVECTOR's FORMAT may be the same as when it is an EHT_TB station.

[0485] In embodiments of the present invention, the first method may be a method in which the format of the TB PPDU is determined based on information indicated by the trigger frame. In yet another specific embodiment, the first method may include the embodiment described in Figure 17. For example, a station can determine the format of the TB PPDU to respond based on which variant the User Info field of the trigger frame received by the station is. If the User Info field of the trigger frame received by the station is an HE variant User Info field, the station can respond to the trigger frame with an HE TB PPDU. If the User Info field of the trigger frame received by the station is an EHT variant User Info field, the station can respond to the trigger frame with an EHT TB PPDU. If the User Info field of the trigger frame received by the station is a NEXT variant User Info field, the station can respond to the trigger frame with a NEXT TB PPDU. In the above description, the fact that the station has received the User Info field of the trigger frame can indicate that the station has received a User Info field containing the AID12 subfield corresponding to the station's AID.

[0486] The User Info field may be an HE variant User Info field if the value of bit B39 of the User Info field received by the station and the value of bit B54 of the Common Info field of the Trigger frame containing the User Info field are 0 and 1, respectively. Otherwise, the User Info field may be an EHT variant User Info field. Otherwise, the value of bit B39 of the User Info field and the value of bit B54 of the Common Info field of the Trigger frame containing the User Info field may include 0, 0, 1, 0, and 1, 1, respectively.

[0487] The B39 bit of the User Info field may be the PS160 subfield. The PS160 subfield may be used to indicate the RU or MRU (multiple RU) assigned to the station corresponding to the User Info field. The PS160 subfield can indicate whether the RU or MRU assigned to the station corresponding to the User Info field corresponds to a primary 160MHz channel or a secondary 160MHz channel. If the RU or MRU assigned to the station corresponding to the User Info field corresponds to a primary 160MHz channel, the value of the PS160 subfield may be set to 0. If the RU or MRU assigned to the station corresponding to the User Info field corresponds to a secondary 160MHz channel, the value of the PS160 subfield may be set to 1. This applies when the size of the assigned RU or MRU is less than or equal to 2x996 tones.

[0488] The B54 bit of the Common Info field may be the HE / EHT P160 subfield. The HE / EHT P160 subfield can indicate whether a solicited TB PPDU is an HE TB PPDU or an EHT TB PPDU on the primary 160MHz channel. The value of the HE / EHT P160 subfield may be set to 0 if the solicited TB PPDU is an EHT TB PPDU on the primary 160MHz channel. The value of the HE / EHT P160 subfield may be set to 1 if the solicited TB PPDU is an HE TB PPDU on the primary 160MHz channel.

[0489] In embodiments of the present invention, the second method may be a method for determining the format of a TB PPDU based on a PPDU format that includes TRS Control. In yet another specific embodiment, the second method may include the embodiment described in Figure 18. For example, the format of the TB PPDU to respond to TRS Control can be determined based on what PPDU the TRS Control received by the station is contained in. For example, if the TRS Control received by the station is contained in an HE PPDU, the station can respond to the TRS Control with an HE TB PPDU. If the TRS Control received by the station is contained in an EHT PPDU, the station can respond to the TRS Control with an EHT TB PPDU. If the TRS Control received by the station is contained in a NEXT PPDU, the station can respond to the TRS Control with a NEXT TB PPDU.

[0490] When a station receives a PPDU containing TRS Control, if the TRS Control received by the station is contained in an HE PPDU, the FORMAT of the RXVECTOR parameter may be HE_MU, HE_SU, or HE_ER_SU. HE_MU, HE_SU, and HE_ER_SU may be the values ​​of the RXVECTOR parameter or TXVECTOR parameter corresponding to an HE MU PPDU, HE SU PPDU, or HE ER SU PPDU, respectively. When a station receives a PPDU containing TRS Control, if the TRS Control received by the station is contained in an EHT PPDU, the FORMAT of the RXVECTOR parameter may be EHT_MU. EHT_MU may be the value of the FORMAT of the RXVECTOR or TXVECTOR FORMAT corresponding to an EHT MU PPDU. In this specification, the receipt of TRS Control by a station can be indicated by the MAC address of the frame containing TRS Control being set to the station's MAC address. More specifically, in the present invention, the fact that a station has received TRS Control indicates that the RA field of the frame containing TRS Control has been set to the station's MAC address.

[0491] Figure 33 shows an embodiment of the present invention, illustrating the UL MU operation of a station and the station setting the L_LENGTH of TXVECTOR and transmitting a PPDU during UL MU operation.

[0492] A station that receives a triggering frame can transmit a TB PPDU according to the embodiment described in Figure 32. The method by which the station sets the L-SIG field and TXVECTOR will be described below.

[0493] A PPDU, including HE PPDUs and EHT PPDUs, may include an L-SIG field and an RL-SIG field. Therefore, a TB PPDU may include an L-SIG field and an RL-SIG field. The RL-SIG field has the same fields as the L-SIG field, and the value of the RL-SIG field is set to the same value as the L-SIG field. The embodiment for the L-SIG field may also apply to the RL-SIG field. The L-SIG field may include a Length field, a Rate field, a Reserved(R) field, a Parity(P) field, and a Signal tail field. The L-SIG field indicates rate information and length information, and a station receiving the L-SIG field can obtain rate information and length information from the L-SIG field.

[0494] The value of the Rate field may be set to indicate 6 Mbps. The value of the Reserved field may be set to 0. The Parity field may be set to indicate even parity for bits 0 through 16. The value of the Signal tail field may be set to 0.

[0495] The value of the Length field may be set by the format of the PPDU that includes the Length field. Specifically, the method by which a station sets the Length field when sending an EHT PPDU may differ from the method by which a station sets the Length field when sending an HE PPDU. Specifically, when a station sends an HE PPDU, the station may set the value of the Length field based on the HE Length formula. More specifically, when a station sends an HE SU PPDU, HE ER SU PPDU, or HE MU PPDU, the station may set the value of the Length field using the HE Length formula. The HE Length formula may be a formula for setting the Length field included in HE SU PPDU, HE ER SU PPDU, or HE MU PPDU. Also, HE SU PPDU, HE ER SU PPDU, and HE MU PPDU are HE PPDUs that are not TB PPDUs and are not trigger-based HE PPDUs.

[0496] (HE Length formula)

[0497] Length = ceil( (TXTIME - SignalExtension - 20) / 4 )*3 - 3 - m

[0498] In the HE Length formula, TXTIME may be the same as in the HE TXTIME formula. TXTIME may be in microseconds.

[0499] (HE TXTIME formula)

[0500] TXTIME = 20 + T_HE_PREAMBLE + N_SYM*T_SYM + N_MA*N_HE_LTF*T_HE_LTF_SYM + T_PE + SignalExtension

[0501] T_HE_PREAMBLE may be the preamble length of HE PPDU, excluding L-STF, L-LTF, and L-SIG. That is, T_HE_PREAMBLE may be the sum of the lengths of RL-SIG, HE-SIG-A, HE-SIG-B (if present, HE-SIG-B exists in HE MU PPDU. HE-SIG-B does not exist in HE SU PPDU, HE ER SU PPDU, or HE TB PPDU), HE-STF, and HE-LTF.

[0502] N_SYM*T_SYM may be the length of the Data field. N_SYM may be the number of data OFDM symbols. T_SYM may be the length of the OFDM symbol.

[0503] N_MA*N_HE_LTF*T_HE_LTF_SYM may be the total length of the midamble. The midamble may consist of HE-LTFs. N_MA may be the number of midambles. N_HE_LTF may be the number of HE_LTFs. T_HE_LTF_SYM may be the length of the OFDM symbols contained in the midamble or HE-LTF.

[0504] T_PE may be the duration of the packet extension field.

[0505] Furthermore, in the HE Length formula, m may be set to 1 for HE MU PPDU and HE ER SU PPDU. Also, m may be set to 2 for other PPDUs, HE SU PPDU and HE TB PPDU. In such an embodiment, the remainder when the value of the Length field is divided by 3 may be determined based on the PPDU format. If the remainder when the value of the Length field is divided by 3 is 2, the station can determine that the Length field is included in HE MU PPDU or HE ER SU PPDU. If the remainder when the value of the Length field is divided by 3 is 1, the station can determine that the Length field is included in HE SU PPDU or HE TB PPDU.

[0506] SignalExtension may be the length of the signal extension. If the TXVECTOR parameter NO_SIG_EXTN is true, SignalExtension may be 0us. If the TXVECTOR parameter NO_SIG_EXTN is false, SignalExtension may be aSignalExtension. Also, if the PPDU is transmitted in the 5GHz or 6GHz band, aSignalExtension may be 0us. Also, if aSignalExtension is operating in the 2.4GHz band, it may be 6us.

[0507] Furthermore, ceil(A) may be the smallest integer equal to or greater than A.

[0508] The HE Length formula may vary depending on the type of HE PPDU. The value of m mentioned above may be determined based on the type of HE PPDU. Furthermore, the HE Length formula may determine that the value of the Length field is not a multiple of 3.

[0509] Furthermore, when a station transmits an EHT PPDU, the station can set the value of the Length field using an EHT Length formula. Specifically, when a station transmits an EHT MU PPDU, the station can set the value of the Length field based on an EHT Length formula. The EHT Length formula may be any formula used to set the Length field included in an EHT MU PPDU. Also, an EHT MU PPDU is an EHT PPDU that is not a TB PPDU and is not transmitted in a trigger-based manner.

[0510] (EHT length formula)

[0511] Length = ceil( (TXTIME - SignalExtension - 20) / 4 )*3 - 3

[0512] In the EHT Length formula, TXTIME may be the same as in the EHT TXTIME formula. TXTIME may be in microseconds.

[0513] (EHT TXTIME formula)

[0514] TXTIME = 20 + T_EHT_PREAMBLE + N_SYM*T_SYM + T_PE + SignalExtension

[0515] T_EHT_PREAMBLE may be the preamble length of EHT PPDUs excluding L-STF, L-LTF, and L-SIG. That is, T_EHT_PREAMBLE may be the sum of the lengths of RL-SIG, U-SIG, EHT-SIG (if present, EHT-SIG is in EHT MU PPDU and not in EHT TB PPDU), EHT-STF, and EHT-LTF.

[0516] N_SYM*T_SYM may be the length of the Data field. N_SYM may be the number of data OFDM symbols. T_SYM may be the length of the OFDM symbol.

[0517] T_PE may be the length of the packet extension field.

[0518] The remainder when the value of the Length field is divided by 3 may be determined by the PPDU format. The station can determine that a PPDU containing L-SIG is an EHT PPDU if the remainder when the value of the Length field is divided by 3 is 0.

[0519] SignalExtension may be the length of the signal extension. If the TXVECTOR parameter NO_SIG_EXTN is true, SignalExtension may be 0us. If the TXVECTOR parameter NO_SIG_EXTN is false, SignalExtension may be aSignalExtension. Also, if the PPDU is transmitted in the 5GHz or 6GHz band, aSignalExtension may be 0us. Also, if the PPDU is transmitted in the 2.4GHz band, aSignalExtension may be 6us.

[0520] Furthermore, ceil(A) may be the smallest integer equal to or greater than A.

[0521] The EHT Length formula may be a fixed formula that does not vary depending on the type of EHT PPDU. The EHT Length formula can determine that the value of the Length field is a multiple of 3.

[0522] When a station sends a NEXT PPDU, it can set the value of the Length field based on a NEXT Length formula. The NEXT Length formula can set the value of the Length field to a multiple of 3, similar to the EHT Length formula. The NEXT Length formula may be a formula in which the part corresponding to EHT in the EHT Length formula is replaced with the part corresponding to NEXT.

[0523] When a station transmits a TB PPDU, it can set the value of the Length field to a value obtained based on the TXVECTOR parameter L_LENGTH. For example, when a station transmits an HE TB PPDU, it can set the value of the Length field to the same value as the TXVECTOR's L_LENGTH. Also, when a station transmits an EHT TB PPDU, it can set the value of the Length field to the TXVECTOR's L_LENGTH plus 2.

[0524] When a station sends a TB PPDU in response to a trigger frame, the station can set the L_LENGTH value of TXVECTOR to the value of the UL Length subfield of the Common Info field contained in the trigger frame. When a station sends an HE TB PPDU in response to a trigger frame, or when a station sends an EHT TB PPDU in response to a trigger frame, the station can set the L_LENGTH value of TXVECTOR to the value of the UL Length subfield of the Common Info field contained in the trigger frame.

[0525] Furthermore, the station can set the UL Length field of the trigger frame that induces a TB PPDU to a value where m is 2 in the HE Length formula. For example, the value of the UL Length field of the trigger frame that induces an HE TB PPDU can be set to a value where m is 2 in the HE Length formula. Alternatively, the station can set the value of the UL Length field of the trigger frame that induces a TB PPDU to a value obtained by subtracting 2 from the EHT Length formula. For example, the station can set the value of the UL Length field of the trigger frame that induces an EHT TB PPDU to a value obtained by subtracting 2 from the EHT Length formula.

[0526] A station can set the value of the UL Length field in a trigger frame and the L_LENGTH value of the TXVECTOR used when responding to a trigger frame to a value that is not a multiple of 3. Additionally, a station can set the value of the UL Length field in a trigger frame and the L_LENGTH value of the TXVECTOR used when responding to a trigger frame to a value where the remainder when divided by 3 is 1.

[0527] Furthermore, when a station transmits an HE TB PPDU according to the above embodiment and sets the value of the Length field to the same value as L_LENGTH of TXVECTOR, the value of the Length field included in the HE TB PPDU induced by the trigger frame may be set to a value that is not a multiple of 3. Specifically, the value of the Length field may be a value whose remainder when divided by 3 is 1.

[0528] Furthermore, when a station transmits an EHT TB PPDU according to the embodiment described above, the value of the Length field can be set to the value of TXVECTOR's L_LENGTH plus 2. In this case, the value of the Length field included in the EHT TB PPDU induced by the trigger frame may be set to a value that is a multiple of 3. This allows a station transmitting a trigger frame to set the value of the UL Length field in the same way whether it induces the transmission of an HE TB PPDU or an EHT TB PPDU, and a station transmitting an EHT TB PPDU based on the trigger frame to set the value of the L-SIG's Length field to a multiple of 3.

[0529] When a station transmits a TB PPDU in response to TRS Control, the station can set the L_LENGTH value of TXVECTOR to a value calculated by the TB PPDU standard transmitted by the station, i.e., a pre-specified Length formula for each TB PPDU. In this case, the Length formula is calculated using the TXTIME formula corresponding to each standard, and the N_SYM value included in the TXTIME formula may be set to FVAL+1. FVAL may be the value of the UL Data Symbols subfield included in TRS Control.

[0530] When a station transmits an HE TB PPDU in response to TRS Control, the station can set the L_LENGTH of TXVECTOR to a value calculated by the HE Length formula corresponding to the transmitted PPDU. In this case, when calculated by the HE Length formula transmitted by the station, the station can set the N_SYM value included in the HE TXTIME formula to FVAL+1. FVAL may be the value of the UL Data Symbols subfield included in TRS Control.

[0531] When transmitting an HE TB PPDU in response to TRS Control, if TXVECTOR L_LENGTH is calculated using the HE Length formula, then TXVECTOR's L_LENGTH may be a value that is not a multiple of 3, and whose remainder when divided by 3 is 1. Also, when a station transmits an HE TB PPDU using the above embodiment, the station can set the value of the Length field to the same value as TXVECTOR's L_LENGTH. In this case, the value of the Length field included in the HE TB PPDU induced by TRS Control may be set to a value that is not a multiple of 3. Specifically, the value of the Length field may be a value whose remainder when divided by 3 is 1.

[0532] Furthermore, when a station transmits an EHT TB PPDU in response to TRS Control, the station may set the L_LENGTH value of TXVECTOR to a value calculated by the EHT Length formula corresponding to the PPDU transmitted by the station. In this case, when the station calculates the L_LENGTH value using the EHT Length formula, the N_SYM value included in the EHT TXTIME formula may be set to FVAL+1. FVAL may be the value of the UL Data Symbols subfield included in the TRS Control.

[0533] When a station transmits an EHT TB PPDU in response to TRS Control, the station can calculate the L_LENGTH of the TXVECTOR using the EHT Length formula. In this case, the L_LENGTH of the TXVECTOR is set to a value that is a multiple of 3, that is, a value whose remainder when divided by 3 is 0. Also, when a station transmits an EHT TB PPDU using the previously described embodiment, the station can set the value of the Length field of the EHT TB PPDU to a value obtained by adding 2 to the L_LENGTH of the TXVECTOR. In this case, the value of the Length field contained in the EHT TB PPDU induced by TRS Control is set to a value that is not a multiple of 3. Specifically, the value of the Length field has a remainder of 1 when divided by 3.

[0534] As in the embodiment described above, the station determines whether the format is HE PPDU or EHT PPDU based on the remainder when the value of the Length field is divided by 3. If the remainder is 0, the station determines it is an EHT PPDU, and therefore can determine that an EHT TB PPDU is an HE PPDU. Specifically, if the PPDU received by the station does not contain the RL-SIG field, the station can determine that the received PPDU is one of the following: non-HT PPDU, HT PPDU, or VHT PPDU. Also, if the PPDU received by the station contains the RL-SIG field, the station can determine that the received PPDU is either an HE PPDU or an EHT PPDU. Furthermore, in another specific embodiment, if the PPDU received by the station contains the RL-SIG field, the station can determine that the received PPDU is an HE PPDU, an EHT TB PPDU, or a NEXT PPDU. In this embodiment, if the remainder when the value of the L-Length field of a PPDU containing RL-SIG is divided by 3 is not 0, the station can determine that the received PPDU is an HE PPDU. Also, if the remainder when the value of the L-Length field of a PPDU containing RL-SIG is divided by 3 is 0, the station can determine that the received PPDU is an EHT PPDU or a NEXT PPDU. In this case, the station can distinguish between an EHT TB PPDU and a NEXT PPDU based on the value of the PHY Version Identifier subfield of the U-SIG field. Figure 33 shows the operation of a station to which this embodiment is applied.

[0535] In Figure 33, the first station (STA1) receives a triggering frame and sends a TB PPDU in response to the triggering frame. If the triggering frame is a trigger frame, the first station (STA1) sets the value of L_LENGTH of TXVECTOR to the value of the UL Length subfield contained in the trigger frame. If the triggering frame contains TRS Control, the first station (STA1) sets the value obtained by the HE Length formula or EHT Length formula as the value of L_LENGTH of TXVECTOR. The PHY of the first station (STA1) can set the value of the Length field of the L-SIG field based on the value of L_LENGTH of TXVECTOR. When the first station (STA1) sends an HE TB PPDU in response to the triggering frame, the first station (STA1) sets the value of the Length field to the value of L_LENGTH of TXVECTOR. When Station 1 (STA1) sends an EHT TB PPDU in response to a triggering frame, Station 1 (STA1) sets the value of the Length field to the value of L_LENGTH of TXVECTOR plus 2.

[0536] In relation to the problem described in Figure 33, the station can determine how to set the value of the Length subfield of the L-SIG field of the EHT TB PPDU based on what triggering frame induced the EHT TB PPDU. This is explained in detail in Figure 34.

[0537] Figure 34 shows a further embodiment of the present invention, illustrating the UL MU operation of a station and the station setting the L_LENGTH of TXVECTOR and transmitting a PPDU during UL MU operation.

[0538] In an embodiment of the present invention, the station can set the value of the L_LENGTH parameter of the TXVECTOR used when transmitting the TB PPDU and the value of the Length subfield of the L-SIG field of the TB PPDU, based on the type of triggering frame that induces the TB PPDU and the format of the TB PPDU. Specifically, the station can determine how to set the value of the L_LENGTH parameter of the TXVECTOR when transmitting the EHT TB PPDU, based on what triggering frame induced the EHT TB PPDU. In a specific embodiment, if the transmission of the EHT TB PPDU is induced by a trigger frame, the station can set the value of the Length subfield of the L-SIG field of the EHT TB PPDU to the value of the L_LENGTH parameter of the TXVECTOR used when transmitting the EHT TB PPDU plus 2. Furthermore, if the transmission of an EHT TB PPDU is induced by a frame containing TRS Control, the station can set the value of the Length subfield of the L-SIG field of the EHT TB PPDU to the L_LENGTH value of the TXVECTOR parameter used when transmitting the EHT TB PPDU. When applying such an embodiment, the station can use the formula used to set the L_LENGTH value of the TXVECTOPR parameter for an EHT PPDU that is not an EHT TB PPDU to set the L_LENGTH value of the TXVECTOPR parameter for an EHT TB PPDU. The formula used to set the L_LENGTH value of the TXVECTOPR parameter for an EHT PPDU that is not an EHT TB PPDU is the EHT Length formula described above. In other words, such an embodiment allows the station to set the value of the Length field of the L-SIG of the EHT PPDU to a multiple of 3, thereby reducing the complexity of the method for setting the L_LENGTH value of the TXVECTOPR parameter for an EHT PPDU.

[0539] When a station transmits an HE TB PPDU, the station can set the value of the L_LENGTH parameter of the TXVECTOR parameter used to transmit the HE TB PPDU value as the value of the Length field of the L-SIG in the HE TB PPDU. In this case, the L_LENGTH value of the TXVECTOR parameter of the HE PPDU may be set by the HE Length formula described above.

[0540] In Figure 34, the first station (STA1) receives a triggering frame and sends a TB PPDU in response to the triggering frame. If the triggering frame is a trigger frame, the first station (STA1) sets the value of L_LENGTH of TXVECTOR to the value of the UL Length subfield contained in the trigger frame. If the triggering frame contains TRS Control, the first station (STA1) sets the value obtained by the HE Length formula or EHT Length formula as the value of L_LENGTH of TXVECTOR. The PHY of the first station (STA1) can set the value of the Length field of the L-SIG field based on the value of L_LENGTH of TXVECTOR. When the first station (STA1) sends an HE TB PPDU in response to the triggering frame, the first station (STA1) sets the value of the Length field to the value of L_LENGTH of TXVECTOR. If Station 1 (STA1) sends an EHT TB PPDU in response to a triggering frame, and the trigger frame induces the transmission of an EHT TB PPDU, Station 1 (STA1) sets the value of the Length field to the value of L_LENGTH of TXVECTOR plus 2. Also, if Station 1 (STA1) sends an EHT TB PPDU in response to a triggering frame, and the frame containing TRS Control induces the transmission of an EHT TB PPDU, Station 1 (STA1) sets the value of the Length field to the value of L_LENGTH of TXVECTOR.

[0541] As illustrated in the embodiment shown in Figure 34, the operation of the PHY receiving the PPDU can be complex. In yet another specific embodiment, the station can determine how to set the L_LENGTH value of the TXVECTOR used when transmitting the EHT TB PPDU based on what triggering frame induced the EHT TB PPDU. This is illustrated in detail in Figure 35.

[0542] Figure 35 shows a UL MU operation of a station according to yet another embodiment of the present invention, and the station setting the L_LENGTH of TXVECTOR and transmitting a PPDU during the UL MU operation.

[0543] When a station transmits a TB PPDU, it can set the L_LENGTH value of the TXVECTOR based on the format of the TB PPDU and the type of triggering frame that prompted the transmission of the TB PPDU. Specifically, if the triggering frame is a trigger frame, the station can set the L_LENGTH value of the TXVECTOR to the value of the UL Length subfield of the trigger frame. If the triggering frame contains TRS Control, and the station transmits an EHT TB PPDU in response to the triggering frame, the station can set the L_LENGTH value of the TXVECTOR to a value obtained by subtracting 2 from the value obtained by the formula used to set the L_LENGTH value of the TXVECTOR for EHT PPDUs other than EHT TB PPDUs. In this case, the formula used to set the L_LENGTH value of the TXVECTOR for EHT PPDUs other than EHT TB PPDUs may be the EHT Length formula described above. When a triggering frame includes TRS Control and the station transmits an HE TB PPDU in response to the triggering frame, the station can set the L_LENGTH value of the TXVECTOR to the value obtained by the formula used to set the L_LENGTH value of the TXVECTOR in the HE PPDU. In this case, the formula used to set the L_LENGTH value of the TXVECTOR in the HE PPDU may be the HE Length formula described above.

[0544] Furthermore, when a station transmits a PPDU other than an EHT TB PPDU, the station can set the value of the L_LENGTH field of the TXVETOR as the value of the Length field of the L-SIG. When a station transmits an EHT TB PPDU, the station can set the value of the Length field of the L-SIG to the value of the L_LENGTH field of the TXVETOR plus 2. In this embodiment, the value of the Length field of the L-SIG for an EHT TB PPDU may be set to a multiple of 3, and the value of the Length field of the L-SIG for an EHT TB PPDU may be set to a value that is not a multiple of 3. Therefore, a station receiving an EHT TB PPDU can determine the format of the EHT TB PPDU based on the value of the Length field of the L-SIG. Also, in this embodiment, a station transmitting an EHT TB PPDU can set the value of the L-SIG field using the L_LENGTH value of the TXVECTOR regardless of the type of triggering frame that induced the transmission of the EHT TB PPDU.

[0545] In Figure 35, the first station (STA1) receives a triggering frame and sends a TB PPDU in response to the triggering frame. If the triggering frame is a trigger frame, the first station (STA1) sets the value of L_LENGTH of TXVECTOR to the value of the UL Length subfield contained in the trigger frame. If the triggering frame contains TRS Control and the station sends an HE TB PPDU in response to the triggering frame, the first station (STA1) sets the value obtained by the HE Length formula as the value of L_LENGTH of TXVECTOR. If the triggering frame contains TRS Control and the station sends an EHT TB PPDU in response to the triggering frame, the first station (STA1) sets the value obtained by the EHT Length formula minus 2 as the value of L_LENGTH of TXVECTOR. The PHY of the first station (STA1) can set the value of the Length field of the L-SIG field based on the value of L_LENGTH of TXVECTOR. When Station 1 (STA1) sends an HE TB PPDU in response to a triggering frame, Station 1 (STA1) sets the value of the Length field to the L_LENGTH value of TXVECTOR. When Station 1 (STA1) sends an EHT TB PPDU in response to a triggering frame, Station 1 (STA1) sets the value of the Length field to the L_LENGTH value of TXVECTOR plus 2.

[0546] The same may apply when the station described in the embodiment shown in Figures 34-35 transmits a NEXT TB PPDU. Specifically, it may apply to the operation of setting the L_LENGTH value of the TXVECTOR used for transmitting an EHT TB PPDU as described in the embodiment shown in Figures 34-35, and to the operation of setting the value of the Length field of the L-SIG of the EHT TB PPDU.

[0547] Furthermore, in Figures 30 to 35, the operations of adding or subtracting 2 in the embodiments may use a predetermined value instead of 2.

[0548] Figure 36 shows that a station according to an embodiment of the present invention receives a PPDU and sets the FORMAT of RXVECTOR.

[0549] As mentioned above, if the PPDU received by the station does not contain the RL-SIG field, the station can determine that the received PPDU is one of the following: non-HT PPDU, HT PPDU, or VHT PPDU. Also, if the PPDU received by the station contains the RL-SIG field, the station can determine that the received PPDU is either an HE PPDU or an EHT PPDU. Furthermore, in another specific embodiment, if the PPDU received by the station contains the RL-SIG field, the station can determine that the received PPDU is either an HE PPDU, an EHT TB PPDU, or a NEXT PPDU. In such an embodiment, if the remainder when the value of the L-Length field of the PPDU containing RL-SIG is divided by 3 is not 0, the station can determine that the received PPDU is an HE PPDU. Also, if the remainder when the value of the L-Length field of the PPDU containing RL-SIG is divided by 3 is 0, the station can determine that the received PPDU is either an EHT PPDU or a NEXT PPDU. Furthermore, if the remainder of dividing the value of the L-Length field of a PPDU containing RL-SIG by 3 is 0, the station can determine that the received PPDU contains a U-SIG field. The station can distinguish between EHT TB PPDUs and NEXT PPDUs based on the value of the PHY Version Identifier subfield of the U-SIG field. Figure 33 shows the operation of a station to which such an embodiment is applied.

[0550] Furthermore, the U-SIG field may include at least one of the following fields: PHY Version Identifier field, Bandwidth field, UL / DL field, BSS Color field, TXOP field, PPDU Type And Compression Mode field, Punctured Channel Information field, MCS field, and Number Of SIG Symbols field. The U-SIG field may also include version-independent and version-dependent fields. Version-independent fields may be fields identically included in the U-SIG field regardless of the PHY Version Identifier field indicated by the U-SIG field. Version-dependent fields may be fields set in the U-SIG field based on the PHY Version Identifier field indicated by the U-SIG field. Version-independent fields may include the PHY Version Identifier field, Bandwidth field, UL / DL field, BSS Color field, and TXOP field.

[0551] The station can defer the duration of the PPDU based on the Version Independent field of the received U-SIG field. In this case, the PPDU duration may be the TXOP duration indicated by the U-SIG field. Specifically, the station can configure the NAV based on at least one of the BSS color field and TXOP field of the Version Independent field. Specifically, the station can configure either a basic NAV or an intra-BSS NAV based on at least one of the BSS color field and TXOP field of the Version Independent field.

[0552] A station can operate based on the Version Independent field even when it receives a PPDU that it does not support, such as a standard-defined PPDU that it does not support. Specifically, a station can retrieve the Version Independent field from a PPDU it does not support. In this case, the station can perform a defer operation based on the retrieved Version Independent field. Specifically, the station can configure the NAV based on the retrieved Version Independent field. Since such operations are performed by MAC, in order to perform such operations, the station needs to transmit information obtained from the physical layer signaling field to the MAC layer. For this purpose, we will explain how to specify the format of an unsupported PPDU.

[0553] The following describes an example of the position of the Version Independent field mentioned above. The U-SIG field may contain two OFDM symbols. Of the two OFDM symbols, the U-SIG field contained in the first OFDM symbol may be called the U-SIG1 field, and the U-SIG field contained in the second OFDM symbol may be called the U-SIG2 field. The U-SIG1 field may contain the Version Independent field. In other specific examples, the U-SIG2 field may contain the Version Independent field.

[0554] Until now, each PPDU format was indicated by a single variable. However, in order to support future PPDU formats and utilize the value of the Version Independent field of the PPDU, a method is needed to effectively indicate it. The PHY of a station receiving a PPDU can communicate to the MAC that an unknown version of the PPDU is specified by a pre-specified value. Specifically, the PHY of a station receiving a PPDU can set the REXVECTOR's FORMAT to a pre-specified value. Specifically, if the value of the PHY Version Identifier field of the PPDU is 0, it can indicate EHT or EHT PPDU. Also, if the value of the PHY Version Identifier field of the PPDU is between 1 and 7, it can indicate NEXT or NEXT PPDU. Furthermore, if the value of the PHY Version Identifier field of the PPDU is between 1 and 7, the station can determine that the PHY Version Identifier field is valid. Even if the value in the PHY Version Identifier field indicates a PPDU in a format not supported by the station, the station can defer the PPDU's duration. Furthermore, even if the value in the PHY Version Identifier field indicates a PPDU in a format not supported by the station, the station's PHY can transmit the information indicated by the Version Independent field to the MAC. For this reason, the station can set the RXVECTOR's CH_BANDWIDTH, UPLINK_FLAG, BSS_COLOR, and TXOP_DURATION based on the information indicated by the Version Independent field. In this case, the station does not need to set RXVECTOR parameters other than FORMAT, CH_BANDWIDTH, UPLINK_FLAG, BSS_COLOR, and TXOP_DURATION, which cannot be set using the information indicated by the Version Independent field.

[0555] As mentioned above, the station's PHY can communicate an unknown PPDU format to the MAC by setting the RXVECTOR's FORMAT to a pre-specified value. The pre-specified value may be UNK. Also, if the value of the PHY Version Identifier field indicates a PPDU format not supported by the station, the value of the PHY Version Identifier field may be one of 1 to 7. The RXVECTOR's FORMAT value UNK is distinct from NON_HT, HT_MF, HT_GF, VHT, HE_SU, HE_MU, HE_ER_SU, HE_TB, EHT_MU, and EHT_TB. NON_HT indicates a non-HT PPDU or a non-HT duplicate PPDU. HT_MF indicates an HT-mixed PPDU. HT_GF indicates an HT-greenfield PPDU. VHT indicates a VHT PPDU. HE_SU indicates an HE SU PPDU. Furthermore, HE_MU indicates HE MU PPDU, HE_ER_SU indicates HE ER SU PPDU, HE_TB indicates HE TB PPDU, EHT_MU indicates EHT MU PPDU, and EHT_TB indicates EHT TB PPDU. Additionally, pre-specified values ​​do not need to be used as TXVECTOR FORMAT values, as stations transmitting PPDUs already support the formatting of the PPDUs they transmit.

[0556] In the embodiment shown in Figure 36, the first station (STA1) receives a NEXT PPDU that it does not support. At this time, the first station (STA1) obtains the U-SIG field from the PPDU. Since the value of the PHY Version Identifier field in the U-SIG field indicates that the first station (STA1) does not support the PPDU, the PHY of the first station (STA1) sets the FORMAT value of RXVECTOR to UNK and transmits the information obtained from the Version Independent field of the U-SIG field to the MAC. At this time, the PHY of the first station (STA1) sets RXVECTOR based on the information obtained from the Version Independent field of the U-SIG field.

[0557] In the embodiment described above, the pre-specified value may be the latest PPDU format indicated by the station, rather than UNK. For example, an EHT station may use EHT_MU or EHT TB as the pre-specified value.

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

[0559] The features, structures, and effects described in the examples above are included in at least one embodiment of the present invention, but are not necessarily limited to a single embodiment. Furthermore, the features, structures, and effects exemplified in each embodiment can be combined or modified and implemented in other embodiments by a person with ordinary skill in the art to which the embodiment belongs. Therefore, it should be interpreted that such combinations and modifications are included within the scope of the present invention.

[0560] The above description has focused on embodiments, but these are merely examples and do not limit the present invention. Anyone with ordinary skill in the art to which the present invention belongs will understand that various modifications and applications not exemplified above are possible, as long as they do not deviate from the essential characteristics of these embodiments. For example, each component specifically shown in the embodiments can be modified and implemented. Such differences related to modifications and applications should be interpreted as being within the scope of the present invention as defined in the attached claims.

Claims

1. It is a station that communicates wirelessly, Transmitter / receiver unit, Includes a processor, The aforementioned processor The PPDU (physical layer protocol data unit) is received via the aforementioned transmitting / receiving unit. If the PPDU satisfies the conditions specified in advance, the value of the PHY Version Identifier field, which indicates the format of the PPDU, is obtained from the signaling field of the received PPDU. If the acquired PHY Version Identifier field value indicates a PPDU format not supported by the station and is valid, the RXVECTOR FORMAT value transmitted to the station's MAC (medium access control) layer is set to a predetermined value. The aforementioned PPDU includes a Version Independent field regardless of the value of the PHY Version Identifier field. The PPDU is a station that includes a Version Dependent field based on the value of the PHY Version Identifier field.

2. The aforementioned processor, The station according to claim 1, wherein if the acquired value of the PHY Version Identifier field indicates the format of the PPDU supported by the station, the value of RXVECTOR's FORMAT is set to a value corresponding to the format of the PPDU indicated by the acquired value of the PHY Version Identifier field.

3. The aforementioned processor, The station according to claim 1, wherein if the acquired value of the PHY Version Identifier field indicates a PPDU format not supported by the station and is valid, the station transmits the information acquired from the Version Independent field to the MAC layer of the station.

4. The aforementioned processor, Based on the information obtained from the Version Independent field, set the CH_BANDWIDTH, UPLINK_FLAG, BSS_COLOR, and TXOP_DURATION of RXVECTOR. The CH_BANDWIDTH indicates the bandwidth of the PPDU, The UPLINK_FLAG indicates whether the PPDU is an uplink PPDU. The BSS_COLOR indicates the BSS color to which the PPDU belongs. The station according to claim 3, wherein the TXOP_DURATION indicates the duration of the TXOP from which the PPDU has been replaced.

5. The aforementioned processor, The station according to claim 4, wherein if the value of the acquired PHY Version Identifier field indicates a PPDU format that the station does not support and is valid, the station delays channel access based on the PPDU.

6. The aforementioned processor, The station according to claim 4, wherein if the value of the acquired PHY Version Identifier field indicates a PPDU format not supported by the station and is valid, the station sets the NAV (network allocation vector) based on the PPDU.

7. The station according to claim 1, wherein the pre-specified value is a value not used for the TXVECTOR FORMAT value.

8. A method for operating a wireless communication station, The stage of receiving a PPDU (physical layer protocol data unit), If the PPDU satisfies pre-specified conditions, the step of obtaining the value of the PHY Version Identifier field, which indicates the format of the PPDU, from the signaling field of the received PPDU; The process includes the step of setting the value of the RXVECTOR FORMAT transmitted to the MAC (medium access control) layer of the station to a predetermined value if the acquired value of the PHY Version Identifier field indicates a PPDU format not supported by the station and is valid, The aforementioned PPDU includes a Version Independent field regardless of the value of the PHY Version Identifier field. The PPDU is an operation method that includes a Version Dependent field based on the value of the PHY Version Identifier field.

9. The aforementioned operation method is, The operation method according to claim 8, further comprising the step of setting the value of RXVECTOR's FORMAT to a value corresponding to the PPDU format indicated by the value of the acquired PHY Version Identifier field when the acquired value of the PHY Version Identifier field indicates the format of the PPDU supported by the station.

10. The aforementioned operation method is, The operation method according to claim 8, further comprising the step of transmitting information obtained from the Version Independent field to the MAC layer of the station if the value of the acquired PHY Version Identifier field indicates a PPDU format not supported by the station and is valid.

11. The step of transmitting the information obtained from the Version Independent field to the MAC layer of the station is as follows: This includes the step of setting CH_BANDWIDTH, UPLINK_FLAG, BSS_COLOR, and TXOP_DURATION of RXVECTOR based on the information obtained from the Version Independent field, The CH_BANDWIDTH indicates the bandwidth of the PPDU, The UPLINK_FLAG indicates whether the PPDU is an uplink PPDU. The BSS_COLOR indicates the BSS color to which the PPDU belongs. The operation method according to claim 10, wherein the TXOP_DURATION indicates the duration of the TXOP that the PPDU has replaced.

12. The operation method according to claim 11, further comprising the step of delaying channel access based on the PPDU if the value of the acquired PHY Version Identifier field indicates a PPDU format not supported by the station and is valid.

13. The operation method according to claim 11, further comprising the step of setting a NAV (network allocation vector) based on the PPDU if the value of the acquired PHY Version Identifier field indicates a PPDU format not supported by the station and is valid.

14. The operation method according to claim 8, wherein the predetermined value is a value not used for the TXVECTOR FORMAT value.

Images