Trigger Frame-Based PPDU Transmission / Reception Method and Apparatus in a Wireless LAN System

Abstract

A method and apparatus for transmitting and receiving trigger frame-based PPDUs in a wireless LAN system are disclosed. In a wireless LAN system according to an embodiment of the present disclosure, a method performed by a station (STA) includes receiving, from an access point (AP), a trigger frame including a common information field and a special user information field; and transmitting, to the AP, a TB PPDU corresponding to one of one or more TB PPDUs triggered by the trigger frame. Here, the common information field includes an uplink (UL) bandwidth subfield, the special user information field includes a first UL bandwidth extension subfield and a second UL bandwidth extension subfield, and the bandwidth of the TB PPDU may be indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for transmitting or receiving a PPDU (physical layer protocol data unit) based on a trigger frame in a wireless LAN (Wireless Local Area Network, WLAN) system.

Background Art

[0002] New technologies for improving the transmission rate, increasing the bandwidth, improving the reliability, reducing the errors, and reducing the latency of wireless LAN (WLAN) have been introduced. Among the wireless LAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, the technologies recently introduced into the wireless LAN include enhancements for VHT (Very High-Throughput) of the 802.11ac standard, enhancements for HE (High Efficiency) of the IEEE 802.11ax standard, and the like.

[0003] In order to provide a more improved wireless communication environment, improvement technologies for EHT (Extremely High Throughput) are being discussed. For example, technologies for increasing the bandwidth, efficiently utilizing multiple bands, MIMO (Multiple Input Multiple Output) that supports an increased number of spatial streams, and technologies for adjusting multiple access points (APs) are being studied. In particular, various technologies for supporting traffic with low latency or real-time characteristics are being studied. Furthermore, new technologies for supporting ultra high reliability (UHR), including improvements or extensions of EHT technologies, are being discussed.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving a PPDU (physical layer protocol data unit) based on a trigger frame in a wireless LAN system.

[0005] The technical problem of the present disclosure is to provide a method and apparatus for performing bandwidth indication for transmitting or receiving a combined PPDU for TB (trigger based) PPDUs of different versions based on a trigger frame.

[0006] The technical problem to be achieved in the present disclosure is not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those having ordinary knowledge in the technical field to which the present disclosure pertains from the following description.

Means for Solving the Problems

[0007] In a wireless LAN system according to one aspect of the present disclosure, a method performed by a station (STA) may include receiving, from an access point (AP), a trigger frame including a common info field and a special user info field; and transmitting, to the AP, a TB PPDU corresponding to one of one or more trigger based (TB) physical layer protocol data units (PPDUs) triggered by the trigger frame. Here, the common info field includes an aggregated PPDU (A-PPDU) related uplink (UL) bandwidth subfield, the one or more special user info fields include a first UL bandwidth extension subfield and a second UL bandwidth extension subfield, the configuration of the TB PPDU may be indicated based on the A-PPDU related subfield, and the bandwidth may be indicated based on at least one other UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield included in the common info field.

[0008] In a wireless LAN system according to a further aspect of the present disclosure, a method performed by an access point (AP) may include transmitting, to a station (STA), a trigger frame including a common info field and a special user info field; and receiving, from the STA, a TB PPDU corresponding to one of one or more trigger based (TB) physical layer protocol data units (PPDUs) triggered by the trigger frame. Here, the common info field includes an aggregated PPDU (A-PPDU) related uplink (UL) bandwidth subfield, the one or more special user info fields include a first UL bandwidth extension subfield and a second UL bandwidth extension subfield, and the configuration of the TB PPDU may be indicated based on the A-PPDU related subfield, and the bandwidth may be indicated based on at least one other UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield included in the common info field.

Advantages of the Invention

[0009] According to the present disclosure, it is possible to provide a method and apparatus for transmitting or receiving a physical layer protocol data unit (PPDU) based on a trigger frame in a wireless LAN system.

[0010] According to the present disclosure, it is possible to provide a method and apparatus for performing a bandwidth indication for transmitting or receiving an aggregated PPDU for TB PPDUs of different versions from each other based on a trigger frame.

[0011] According to the present disclosure, by supporting the transmission and reception of a new version of PPDU and / or a merged PPDU based on a trigger frame, there is an effect that latency can be reduced, and throughput and efficiency can be improved.

[0012] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those of ordinary skill in the technical field to which the present disclosure pertains from the following description.

Brief Description of the Drawings

[0013] The accompanying drawings, included as part of the detailed description to assist in understanding the present disclosure, provide examples of embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description.

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Mode for Carrying Out the Invention

[0015] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is for explaining exemplary embodiments of the present disclosure and is not for showing the only embodiments in which the present disclosure can be implemented. The following detailed description includes specific details for providing a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0016] In some cases, to avoid obscuring the concept of the present disclosure, known structures and devices may be omitted, and may be shown in the form of a block diagram centered on the core functions of each structure and device.

[0017] In the present disclosure, when a component is "connected", "coupled", or "joined" to another component, this may include not only a direct connection relationship but also an indirect connection relationship in which there are additional components between them. Also, in the present disclosure, the terms "comprising" or "having" identify the presence of the recited features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0018] In the present disclosure, terms such as "first", "second", etc. are used only for the purpose of distinguishing one component from another and are not used to limit the components. Unless otherwise specified, they do not limit the order or importance, etc. between the components. Therefore, within the scope of the present disclosure, the first component in one embodiment can also be referred to as the second component in another embodiment, and similarly, the second component in one embodiment can be referred to as the first component in another embodiment.

[0019] The terms used in the present disclosure are for the purpose of describing specific embodiments and are not for limiting the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms are also intended to include the plural forms unless the context clearly dictates otherwise. The term "and / or" used in the present disclosure means that it may refer to one of the related listed items or include any and all possible combinations of two or more of them. Also, in the present disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0020] The examples of the present disclosure may be applied to various wireless communication systems. For example, the examples of the present disclosure may be applied to a wireless LAN system. For example, the examples of the present disclosure may be applied to IEEE 802.11a / g / n / ac / ax standard-based wireless LANs. Note that the examples of the present disclosure may be applied to a newly proposed IEEE 802.11be (or, EHT)-standard-based wireless LAN. The examples of the present disclosure may also be applied to an IEEE 802.11be release-2 standard-based wireless LAN that corresponds to further improved technologies of the IEEE 802.11be release-1 standard. Furthermore, the examples of the present disclosure may be applied to a next-generation standard-based wireless LAN after IEEE 802.11be. Also, the examples of the present disclosure may be applied to a cellular wireless communication system. For example, it may be applied to a cellular wireless communication system based on the technologies of the LTE (Long Term Evolution) series and the 5G NR (New Radio) series of the 3GPP (registered trademark) (3rd Generation Partnership Project) standard.

[0021] Hereinafter, the technical features to which the examples of the present disclosure can be applied will be described.

[0022] FIG. 1 is a block configuration diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0023] The first device 100 and the second device 200 illustrated in FIG. 1 may be referred to by various terms such as a terminal, a wireless device, a Wireless Transmit Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Mobile Subscriber Unit (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), a Wireless Terminal (WT), or simply a user. Also, the first device 100 and the second device 200 may be referred to by various terms such as an Access Point (AP), a Base Station (BS), a fixed station, a Node B, a Base Transceiver System (BTS), a network, an Artificial Intelligence (AI) system, a Road Side Unit (RSU), a repeater, a router, a relay, or a gateway.

[0024] The devices 100 and 200 illustrated in FIG. 1 may also be referred to as a station (STA). For example, the devices 100 and 200 illustrated in FIG. 1 may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, or a receiving STA. For example, the STAs 110 and 200 may play the role of an AP (Access Point) or a non-AP. That is, in the present disclosure, the STAs 110 and 200 may have the functions of an AP and / or a non-AP. When the STAs 110 and 200 have the AP function, they may simply be referred to as an AP, and when the STAs 110 and 200 have the non-AP function, they may simply be referred to as an STA. Also, in the present disclosure, an AP may be denoted as an AP STA.

[0025] Referring to FIG. 1, the first device 100 and the second device 200 can transmit and receive wireless signals using various wireless LAN technologies (e.g., IEEE 802.11 series). The first device 100 and the second device 200 may include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that comply with the provisions of the IEEE 802.11 standard.

[0026] In addition, the first device 100 and the second device 200 can further support various communication standards other than wireless LAN technologies (e.g., standards of the 3GPP LTE series, 5G NR series, etc.). Also, the devices of the present disclosure may be embodied by various devices such as mobile phones, vehicles, personal computers, AR (Augmented Reality) equipment, VR (Virtual Reality) equipment, etc. Further, the STA in this specification can support various communication services such as voice calls, video calls, data communication, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), IoT (Internet-of-Things), etc.

[0027] The first device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts in the present disclosure. For example, after processing the information in the memory 104 to generate a first information / signal, the processor 102 can transmit a radio signal including the first information / signal via the transceiver 106. Also, after receiving a radio signal including a second information / signal via the transceiver 106, the processor 102 can store the information obtained from the signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and can store various information related to the operation of the processor 102. For example, the memory 104 can store software code including instructions for executing part or all of the processes controlled by the processor 102 or for executing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., the IEEE 802.11 series). The transceiver 106 may be connected to the processor 102 and can transmit and / or receive radio signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in the same sense as an RF (Radio Frequency) unit. In the present disclosure, the device can also mean a communication modem / circuit / chip.

[0028] The second device 200 includes one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 controls the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. For example, after processing the information in the memory 204 to generate a third information / signal, the processor 202 can transmit a radio signal including the third information / signal via the transceiver 206. Also, after receiving a radio signal including a fourth information / signal via the transceiver 206, the processor 202 can store the information obtained from the signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and can store various information related to the operation of the processor 202. For example, the memory 204 can store software code including instructions to execute part or all of the processes controlled by the processor 202 or to execute the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., the IEEE 802.11 series). The transceiver 206 may be connected to the processor 202 and can transmit and / or receive radio signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in the same sense as an RF unit. In the present disclosure, the device can also mean a communication modem / circuit / chip.

[0029] Hereinafter, the hardware elements of devices 100 and 200 will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 can implement one or more layers (e.g., functionally equivalent layers such as PHY and MAC). One or more processors 102 and 202 can generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams in the present disclosure. One or more processors 102 and 202 can generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams in the present disclosure. One or more processors 102 and 202 can generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data, or information according to the functions, procedures, proposals, and / or methods in the present disclosure, and provide it to one or more transceivers 106 and 206. One or more processors 102 and 202 can receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206, and obtain a PDU, an SDU, a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams in the present disclosure.

[0030] One or more processors 102, 202 can be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors 102, 202 may be embodied by hardware, firmware, software, or a combination thereof. As an example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, and the like. The firmware or software configured to execute the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure may be included in one or more processors 102, 202, stored in one or more memories 104, 204, and driven by one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure may be embodied by firmware or software in the form of code, instruction words, and / or a set of instruction words.

[0031] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and can store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 may be constituted by a ROM, a RAM, an EPROM, a flash memory, a hard drive, a register, a cache memory, a computer-readable storage medium, and / or a combination thereof. The one or more memories 104, 204 may be located inside and / or outside the one or more processors 102, 202. Also, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 by various techniques such as wired or wireless connections.

[0032] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc. mentioned in the methods and / or operation sequence diagrams of the present disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Also, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure via one or more antennas 108, 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed using one or more processors 102, 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0033] For example, either one of STA100 and 200 can perform the intended operation of the AP, and the other one of STA100 and 200 can perform the intended operation of a non-AP STA. For example, the transceivers 106 and 206 in FIG. 1 can perform the transmission and reception operations of signals (for example, packets or PPDUs (Physical layer Protocol Data Units) conforming to IEEE 802.11a / b / g / n / ac / ax / be, etc.). Also, in the present disclosure, operations in which various STAs generate transmission and reception signals or perform data processing and calculations in advance for the transmission and reception signals may be performed by the processors 102 and 202 in FIG. 1. For example, an example of an operation in which a transmission and reception signal is generated or data processing and calculations are performed in advance for the transmission and reception signal includes: 1) an operation of determining / acquiring / configuring / calculating / decoding / encoding bit information of fields (such as SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in a PPDU; 2) an operation of determining / configuring / acquiring time resources and frequency resources (such as subcarrier resources) used for fields (such as SIG, STF, LTF, Data, etc.) included in a PPDU; 3) an operation of determining / configuring / acquiring a specific sequence (such as a pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for fields (such as SIG, STF, LTF, Data, etc.) included in a PPDU; 4) a power control operation and / or power saving operation applied to an STA; 5) operations related to determining / acquiring / configuring / calculating / decoding / encoding an ACK signal. Also, in the following example, various information (for example, information regarding fields / sub-fields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding transmission and reception signals may be stored in the memories 104 and 204 in FIG. 1.

[0034] Hereinafter, the downlink (DL) means a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted and received through the downlink. In downlink communication, the transmitter may be part of the AP STA and the receiver may be part of the non-AP STA. The uplink (UL) means a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted and received through the uplink. In uplink communication, the transmitter may be part of the non-AP STA and the receiver may be part of the AP STA.

[0035] FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure is applicable.

[0036] The structure of the wireless LAN system may be composed of a plurality of components. A wireless LAN that supports STA mobility transparent to the upper layer may be provided by the interaction of the plurality of components. A BSS (Basic Service Set) corresponds to the basic configuration block of the wireless LAN. In FIG. 2, an example is shown where there are two BSSs (BSS1 and BSS2), and each BSS includes two STAs (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). In FIG. 2, the ellipse representing the BSS may be understood to represent the coverage area in which the STAs included in the BSS maintain communication. This area can be referred to as a BSA (Basic Service Area). When a STA moves outside the BSA, it can no longer communicate directly with other STAs within the BSA.

[0037] If the DS shown in Fig. 2 is not considered, the most basic type of BSS in a wireless LAN is an Independent BSS (IBSS). For example, an IBSS can have the smallest form consisting of only two STAs. For example, assuming that other components are omitted, BSS1 consisting of only STA1 and STA2, or BSS2 consisting of only STA3 and STA4 can each correspond to a typical example of an IBSS. Such a configuration is possible when STAs can communicate directly without an AP. Also, in a wireless LAN of such a form, it is not pre-planned and configured, and it may be configured when a LAN is needed, and this can also be referred to as an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity that performs management functions centrally. That is, in an IBSS, STAs are managed in a distributed manner. In an IBSS, all STAs may be composed of mobile STAs, connection to a distributed system (DS) is not allowed, and it forms a self-contained network.

[0038] Due to STAs joining or leaving, or STAs entering or leaving the BSS area, etc., the membership of STAs in the BSS may be dynamically changed. In order to become a member of the BSS, an STA can join the BSS using a synchronization process. In order to access all services of the BSS-based structure, an STA needs to be associated with the BSS. Such an association may be set dynamically and may include the use of a Distribution System Service (DSS).

[0039] In a wireless LAN, the direct STA-to-STA distance may be limited by PHY performance. In some cases, such distance limitations may be sufficient, but in some cases, communication between STAs at a greater distance may be required. A distributed system (DS) may be configured to support extended coverage.

[0040] DS means a structure in which BSSs are interconnected. Specifically, as shown in FIG. 2, a BSS may exist as a component of an extended form of a network composed of a plurality of BSSs. DS is a logical concept and may be specified by the characteristics of a distributed system medium (DSM). In this regard, a wireless medium (Wireless Medium, WM) and DSM may be logically separated. Each logical medium is used for different purposes and is used by different components. These media are not limited to being the same or different. In this way, the flexibility of a wireless LAN structure (DS structure or other network structure) can be explained in terms of a plurality of media being logically different from each other. That is, a wireless LAN structure may be implemented in various ways, and the wireless LAN structure may be specified independently according to the physical characteristics of each implementation example.

[0041] DS can support mobile devices by providing seamless integration of a plurality of BSSs and providing the logical services necessary for handling addresses to destinations. Further, DS may further include a component called a portal that acts as a bridge for connecting a wireless LAN and other networks (e.g., IEEE 802.X).

[0042] AP means an entity that enables access to the DS through the WM for an associated non-AP STA and also has the functionality of a STA. Data movement between the BSS and the DS can be performed via the AP. For example, STA2 and STA3 shown in FIG. 2 provide the function of enabling the associated non-AP STAs (STA1 and STA4) to access the DS while having the functionality of a STA. Also, since all APs basically correspond to STAs, all APs are addressable entities. The address used by the AP for communication on the WM and the address used by the AP for communication on the DSM do not necessarily have to be the same. A BSS composed of an AP and one or more STAs can be referred to as an infrastructure BSS.

[0043] Data transmitted from one of the STAs associated with an AP to the STA address of the AP is always received at an uncontrolled port and may be processed by an IEEE 802.1X port access entity. Also, when the controlled port is authenticated, the transmitted data (or frame) can be transmitted to the DS.

[0044] An Extended Service Set (ESS) for providing a wider coverage may be set in the structure of the DS described above.

[0045] An ESS means a network composed of a DS and BSSs, where the network can have an arbitrary size and complexity. An ESS can correspond to a set of BSSs connected to one DS. However, an ESS does not include a DS. The ESS network is characterized in that it appears as an IBSS at the LLC (Logical Link Control) layer. STAs included in an ESS can communicate with each other, and a mobile STA can transparently move from one BSS to another (within the same ESS) to the LLC. APs included in one ESS may have the same SSID (service set identification). The SSID is distinguished from the BSSID, which is the identifier of the BSS.

[0046] In a wireless LAN system, without making any assumptions about the relative physical positions of BSSs, any of the following forms are possible. BSSs may partially overlap, which is a commonly used form to provide continuous coverage. Also, BSSs do not have to be physically connected, and logically there is no limit to the distance between BSSs. Also, BSSs may be physically located at the same position, which may be used to provide redundancy. Also, one (or one or more) IBSS or ESS networks may physically exist in the same space as one (or one or more) ESS networks. This can correspond to the ESS network form when an ad hoc network operates at the location where the ESS network exists, when wireless networks physically overlap by different organizations, or when two or more different access and security policies are required at the same location.

[0047] Figure 3 is a diagram for explaining the link setup process to which the present disclosure is applicable.

[0048] In order for a STA to set up a link with a network and transmit and receive data, it must first discover the network, perform authentication, establish an association, and carry out authentication procedures for security. The link setup process can be referred to as the session start process and the session setup process. Also, the processes of discovery, authentication, association, and security settings in the link setup process can be collectively referred to as the association process.

[0049] In step S310, the STA can perform a network discovery operation. The network discovery operation may include the scanning operation of the STA. That is, in order for the STA to access the network, it must search for networks that it can participate in. The STA must identify compatible networks before participating in a wireless network, and the process of identifying networks existing in a specific area is called scanning.

[0050] Scanning methods include active scanning and passive scanning. In FIG. 3, by way of example, a network discovery operation including an active scanning process is shown. In active scanning, the STA performing the scanning sends a probe request frame (probe request frame) to search for what APs exist in the vicinity while moving channels, and waits for a response thereto. The responder sends a probe response frame as a response to the probe request frame to the STA that sent the probe request frame. Here, the responder may be the STA that last sent a beacon frame in the BSS of the channel being scanned. Since the AP sends a beacon frame in the BSS, the AP becomes the responder. In the IBSS, since the STAs in the IBSS send beacon frames alternately, the responder is not constant. For example, the STA that sent a probe request frame on channel 1 and received a probe response frame on channel 1 saves the BSS-related information included in the received probe response frame, moves to the next channel (for example, channel 2), and can perform scanning in the same way (that is, send and receive probe requests / responses on channel 2).

[0051] Although not shown in FIG. 3, the scanning operation may be performed in a passive scanning mode. In passive scanning, the STA that performs scanning waits for beacon frames while moving channels. A beacon frame is one of the management frames defined by IEEE 802.11, which notifies the existence of a wireless network and is periodically transmitted so that a STA performing scanning can search for a wireless network and participate in the wireless network. In a BSS, the AP plays the role of periodically transmitting beacon frames, and in an IBSS, STAs within the IBSS transmit beacon frames alternately. When the STA performing scanning receives a beacon frame, it stores the information about the BSS contained in the beacon frame and records the beacon frame information on each channel while moving to other channels. The STA that has received a beacon frame can store the BSS-related information contained in the received beacon frame and move to the next channel to perform scanning on the next channel in the same way. Comparing active scanning and passive scanning, active scanning has the advantage that the delay and power consumption are smaller than those of passive scanning.

[0052] After the STA discovers the network, an authentication process may be performed in step S320. Such an authentication process can be called the first authentication process in order to clearly distinguish it from the security setup operation in step S340 described later.

[0053] The authentication process includes a process in which the STA transmits an authentication request frame (authentication request frame) to the AP and, in response, the AP transmits an authentication response frame to the STA. The authentication frame used for authentication request / response corresponds to a management frame.

[0054] The authentication frame may include information regarding the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), Finite Cyclic Group, etc. This corresponds to an example of some of the information that may be included in the authentication request / response frame, and may be replaced by other information or may further include additional information.

[0055] The STA can send an authentication request frame to the AP. The AP can determine whether to allow authentication for the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA using an authentication response frame.

[0056] After the STA is successfully authenticated, the association process may be performed at stage S330. The association process includes the process in which the STA sends an association request frame to the AP and, in response, the AP sends an association response frame to the STA.

[0057] For example, the association request frame may include information regarding various capabilities, beacon listen interval, SSID (service set identifier), supported rates, supported channels, RSN, mobility domain, supported operating classes, TIM (Traffic Indication Map) broadcast request, information regarding interworking service capabilities, and the like. For example, the association response frame may include information regarding various capabilities, status code, AID (Association ID), supported rates, EDCA (Enhanced Distributed Channel Access) parameter set, RCPI (Received Channel Power Indicator), RSNI (Received Signal to Noise Indicator), mobility domain, timeout interval (e.g., association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS (Quality of Service) map, and the like. This corresponds to an example of some of the information that may be included in the association request / response frame, and may be replaced by other information or may further include additional information.

[0058] After the STA is successfully associated with the network, the security setup process may be performed in step S340. The security setup process in step S340 can also be said to be an authentication process using RSNA (Robust Security Network Association) requests / responses. The authentication process in step S320 is referred to as the first authentication process, and the security setup process in step S340 can also be simply referred to as the authentication process.

[0059] The security setup process in step S340 may include, for example, a process of setting up a private key using a 4-way handshake using EAPOL (Extensible Authentication Protocol over LAN) frames. Also, the security setup process may be performed by a security method not defined in the IEEE 802.11 standard.

[0060] Figure 4 is a diagram for explaining a backoff process to which the present disclosure is applicable.

[0061] In a wireless LAN system, the basic access mechanism of MAC (Medium Access Control) is the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA / CA mechanism, which is also called the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, basically adopts a "listen before talk" access mechanism. According to such a type of access mechanism, the AP and / or STA can perform a Clear Channel Assessment (CCA) to sense the wireless channel or medium (for example, DIFS (DCF Inter-Frame Space)) for a predetermined time interval prior to starting transmission. As a result of sensing, if it is determined that the medium is in an idle status, frame transmission is started through the medium. On the other hand, if the medium is sensed as being in an occupied or busy state, the AP and / or STA does not start its own transmission and can set a delay period for medium access (for example, a random backoff period) and wait, and then attempt frame transmission. By applying the random backoff period, it is expected that multiple STAs will attempt frame transmission after waiting for different times from each other, so that collisions can be minimized.

[0062] In addition, the IEEE 802.11 MAC protocol provides HCF (Hybrid Coordination Function). HCF is based on the above-mentioned DCF and PCF (Point Coordination Function). PCF refers to a polling-based synchronous access method, in which all receiving APs and / or STAs periodically poll so that they can receive data frames. In addition, HCF has EDCA (Enhanced Distributed Channel Access) and HCCA (HCF Controlled Channel Access). EDCA is an access method in which the provider makes the access method for providing data frames to multiple users be contention-based, and HCCA is to use a non-contention-based channel access method using a polling mechanism. In addition, HCF includes a medium access mechanism for improving the QoS (Quality of Service) of a wireless LAN, and QoS data can be transmitted in both the Contention Period (CP) and the Contention Free Period (CFP).

[0063] Referring to FIG. 4, the operation based on the random backoff period will be described. When the medium that was in the occupied / busy state changes to the idle state, multiple STAs can attempt to transmit data (or frames). As a solution to minimize collisions, each STA can select a random backoff count and attempt transmission after waiting for the corresponding slot time. The random backoff count has a pseudo-random integer value and can be determined to be any one of the values in the range of 0 to CW. Here, CW is the contention window parameter value. The CW parameter is given an initial value of CWmin, but can take a value twice as large in the case of a transmission failure (for example, when an ACK for the transmitted frame cannot be received). When the CW parameter value reaches CWmax, data transmission can be attempted while maintaining the CWmax value until data transmission is successful, and when data transmission is successful, it is reset to the CWmin value. The CW, CWmin, and CWmax values are preferably set to 2 n -1 (n = 0, 1, 2,...).

[0064] When the random backoff process starts, the STA continues to monitor the medium while counting down the backoff slots by the determined backoff count value. When the medium is monitored as being in the occupied state, the countdown stops and waits, and when the medium becomes idle, the remaining countdown resumes.

[0065] In the example of FIG. 4, when a packet to be transmitted arrives at the MAC of STA3, STA3 can confirm that the medium is idle for only the DIFS period and immediately transmit a frame. The remaining STAs monitor that the medium is in the occupied / busy state and wait. During this time, data to be transmitted may occur at each of STA1, STA2, and STA5. Each STA can count down the backoff slots by the randomly selected backoff count value it has chosen after waiting for only the DIFS period when the medium is monitored as being idle. Assume that STA2 selects the minimum backoff count value and STA1 selects the maximum backoff count value. That is, an example is illustrated where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 finishes the backoff count and starts frame transmission. STA1 and STA5 stop counting down for a while and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for only the DIFS period and then resume the stopped backoff count. That is, after counting down the remaining backoff slots for only the remaining backoff time, frame transmission can be started. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. Data to be transmitted may also occur at STA4 while STA2 occupies the medium. From the perspective of STA4, when the medium becomes idle, after waiting for only the DIFS period, it can count down by the randomly selected backoff count value it has chosen and start frame transmission. The example of FIG. 4 shows a case where the remaining backoff time of STA5 accidentally coincides with the random backoff count value of STA4. In this case, a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 can receive an ACK, and the data transmission will fail. In this case, STA4 and STA5 can select a random backoff count value after doubling the CW value and perform the countdown.STA1 waits while the medium is busy due to the transmissions of STA4 and STA5. However, when the medium becomes idle, after waiting for only DIFS and then when the remaining backoff time has elapsed, it can start transmitting a frame.

[0066] As shown in the example of FIG. 4, a data frame is a frame used for transmitting data to be forwarded to the upper layer, and may be transmitted after a backoff that occurs after the expiration of DIFS when the medium becomes idle. Further, a management frame is a frame used for exchanging management information that is not forwarded to the upper layer, and is transmitted after a backoff that occurs after the expiration of an IFS such as DIFS or PIFS (Point coordination function IFS). As subtypes of the management frame, there are Beacon, Association request / response, re-Association request / response, probe request / response, authentication request / response, etc. A control frame is a frame used for controlling access to the medium. As subtypes of the control frame, there are RTS (Request-To-Send), CTS (Clear-To-Send), ACK (Acknowledgment), PS-Poll (Power Save-Poll), BlockAck, BlockACKReq, NDP null data packet announcement, Trigger, etc. A control frame is transmitted after a backoff that occurs after the expiration of DIFS when it is not a response frame to a previous frame, and is transmitted without a backoff after the expiration of SIFS (short IFS) when it is a response frame to a previous frame. The type and subtype of a frame may be identified by the type field and subtype field within the frame control (FC) field.

[0067] A QoS (Quality of Service) STA can transmit a frame after performing a backoff that occurs after the expiration of AIFS (Arbitration IFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC). Here, the frames for which AIFS[i] can be used can be data frames, management frames, or control frames that are not response frames.

[0068] FIG. 5 is a diagram for explaining a CSMA / CA-based frame transmission operation to which the present disclosure is applicable.

[0069] As described above, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing in which the STA directly senses the medium. Virtual carrier sensing is for complementing problems that may occur in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of the STA can utilize the NAV (Network Allocation Vector). The NAV is a value that indicates to other STAs the time remaining until the medium becomes available for use by the STA that is currently using the medium or has the authority to use it. Therefore, the value set as the NAV corresponds to the period during which the medium use is planned by the STA that transmits the frame, and the STA that receives the NAV value is prohibited from accessing the medium during that period. For example, the NAV may be set based on the value of the "duration" field in the MAC header of the frame.

[0070] In the example of FIG. 5, assume that STA1 is about to transmit data to STA2, and STA3 is in a position where it can overhear part or all of the frames transmitted and received between STA1 and STA2.

[0071] In order to reduce the possibility of transmission collisions among multiple STAs in the CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames may be applied. In the example of FIG. 5, while the transmission of STA1 is in progress, as a result of the carrier sensing of STA3, it may be determined that the medium is idle. That is, STA1 may be a hidden node to STA3. Or, in the example of FIG. 5, while the transmission of STA2 is in progress, as a result of the carrier sensing of STA3, it may be determined that the medium is idle. That is, STA2 may be a hidden node to STA3. Before data transmission and reception between STA1 and STA2, by exchanging RTS / CTS frames, STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for the transmission from STA1 or STA3, can be prevented from attempting to occupy the channel during the data transmission and reception between STA1 and STA2.

[0072] Specifically, STA1 can use carrier sensing to determine whether the channel is in use. In terms of physical carrier sensing, STA1 can determine the channel occupancy idle state based on the energy magnitude or signal correlation detected from the channel. Also, in terms of virtual carrier sensing, STA1 can use the NAV (network allocation vector) timer to judge the occupancy state of the channel.

[0073] When the channel is idle at DIFS, STA1 can transmit an RTS frame to STA2 after performing backoff. When STA2 receives the RTS frame, it can transmit a CTS frame, which is a response to the RTS frame, to STA1 after SIFS.

[0074] Although STA3 cannot overhear the CTS frame from STA2, if it can overhear the RTS frame from STA1, STA3 can use the duration information included in the RTS frame to set the NAV timer for the subsequent consecutive frame transmission period (for example, SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Or, although STA3 cannot overhear the RTS frame from STA1, if it can overhear the CTS frame from STA2, STA3 can use the duration information included in the CTS frame to set the NAV timer for the subsequent consecutive frame transmission period (for example, SIFS + data frame + SIFS + ACK frame). That is, when STA3 can overhear one or more of the RTS or CTS frames from at least one of STA1 or STA2, it can set the NAV based on this. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information included in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0075] When STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when the reception of the CTS frame is completed. When STA2 successfully receives the data frame, it can transmit an ACK frame, which is a response to the data frame, to STA1 after SIFS. When the NAV timer of STA3 expires, it can use carrier sensing to determine whether the channel is in use. If STA3 determines that the channel is not used by other terminals during the period from the expiration of the NAV timer to DIFS, it can attempt channel access after the contention window (CW) by random backoff has passed.

[0076] FIG. 6 is a diagram for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure is applicable.

[0077] By an instruction or primitive (meaning a set of an instruction or parameters) from the MAC layer, the PHY layer can prepare an MPDU (MAC PDU) to be transmitted. For example, when receiving an instruction from the MAC layer that requests the start of transmission in the PHY layer, the PHY layer switches to the transmission mode and can configure and transmit information (e.g., data) provided from the MAC layer in the form of a frame. Also, in the PHY layer, when detecting a valid preamble of the received frame, the PHY layer monitors the preamble header and sends an instruction to the MAC layer notifying the start of reception in the PHY layer.

[0078] As described above, information transmission / reception in a wireless LAN system is performed in the form of a frame, and for this purpose, a Physical layer Protocol Data Unit (PPDU) frame format is defined.

[0079] A basic PPDU frame may include a Short Training Field (STF), a Long Training Field (LTF), a SIGNAL (SIG) field, and a Data field. The most basic (e.g., non-HT (High Throughput)) PPDU frame format may be composed of only a Legacy-STF (L-STF), a Legacy-LTF (L-LTF), a SIG field, and a Data field. Also, depending on the type of the PPDU frame format (e.g., an HT-mixed format PPDU, an HT-greenfield format PPDU, a Very High Throughput (VHT) PPDU, etc.), additional (or other types of) STF, LTF, and SIG fields may be included between the SIG field and the Data field (this will be described later with reference to FIG. 7).

[0080] The STF is a signal for signal detection, AGC (Automatic Gain Control), diversity selection, precise time synchronization, etc., and the LTF is a signal for channel estimation, frequency error estimation, etc. It can be said that the STF and LTF are signals for the synchronization and channel estimation of the OFDM physical layer.

[0081] The SIG field may include a RATE field, a LENGTH field, etc. The RATE field may include information regarding the modulation and coding rate of data. The LENGTH field may include information regarding the length of data. Further, the SIG field may include parity bits, SIG TAIL bits, etc.

[0082] The data field may include a SERVICE field, a PSDU (Physical layer Service Data Unit), PPDU TAIL bits, and may include padding bits if necessary. Some bits of the SERVICE field may be used for the synchronization of the descrambler at the receiving end. The PSDU corresponds to the MAC PDU defined at the MAC layer and may include data generated / used at the upper layer. The PPDU TAIL bits may be used to return the encoder to the 0 state. The padding bits may be used to align the length of the data field to a predetermined unit.

[0083] The MAC PDU is defined by various MAC frame formats, and the basic MAC frame is composed of a MAC header, a frame body, and an FCS (Frame Check Sequence). The MAC frame is composed of the MAC PDU and may be transmitted / received by the PSDU in the data part of the PPDU frame format.

[0084] The MAC header includes a Frame Control field, a Duration / ID field, an Address field, etc. The Frame Control field may include control information necessary for frame transmission / reception. The Duration / ID field may be set to the time for transmitting the frame, etc. For the specific contents of the Sequence Control, QoS Control, and HT Control sub-fields of the MAC header, reference can be made to the IEEE 802.11 standard document.

[0085] The Null Data Packet (NDP) frame format means a frame format that does not contain a data packet. That is, the NDP frame means a frame format that includes the PLCP (physical layer convergence procedure) header part (i.e., the STF, LTF, and SIG fields) in the general PPDU frame format and does not include the remaining part (i.e., the data field). The NDP frame can also be referred to as a short frame format.

[0086] FIG. 7 is a diagram showing an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure is applicable.

[0087] In standards such as IEEE 802.11a / g / n / ac / ax, various forms of PPDUs are used. The basic PPDU format (IEEE 802.11a / g) includes an L-LTF, an L-STF, an L-SIG, and a Data field. The basic PPDU format can also be referred to as a non-HT PPDU format.

[0088] The HT PPDU format (IEEE 802.11n) further includes the HT-SIG, HT-STF, and HT-LFT(s) fields in the basic PPDU format. The HT PPDU format shown in FIG. 7 can be referred to as the HT-mixed format. An HT-greenfield format PPDU may be further defined, which corresponds to a format that does not include the L-STF, L-LTF, and L-SIG and is composed of the HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and the Data field (not shown).

[0089] An example of the VHT PPDU format (IEEE 802.11ac) further includes the VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in the basic PPDU format.

[0090] An example of the HE PPDU format (IEEE 802.11ax) further includes the RL-SIG (Repeated L-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and PE (Packet Extension) fields in the basic PPDU format. Depending on the detailed illustration of the HE PPDU format, some fields may be excluded or their lengths may change. For example, the HE-SIG-B field is included in the HE PPDU format for multi-user (MU), and the HE-SIG-B is not included in the HE PPDU format for single-user (SU). Also, the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may change to 8 us. The HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may change to 16 us.

[0091] FIGS. 8 to 10 are diagrams for explaining examples of resource units of a wireless LAN system to which the present disclosure is applicable.

[0092] Referring to FIGS. 8 to 10, the resource unit (RU) defined in the wireless LAN system will be described. The RU may include a plurality of subcarriers (or tones). The RU may be used when transmitting signals to a plurality of STAs based on the OFDMA method. Also, the RU may be defined even when transmitting a signal to one STA. The RU may be used for the STF, LTF, data field, etc. of the PPDU.

[0093] As shown in FIGS. 8 to 10, RUs corresponding to different numbers of tones (i.e., subcarriers) are used, and can constitute a part of the fields of 20 MHz, 40 MHz, or 80 MHz X-PPDU (X is HE, EHT, etc.). For example, resources may be allocated in units of RUs shown for the X-STF, X-LTF, and Data fields.

[0094] FIG. 8 is a diagram showing an exemplary arrangement of resource units (RUs) used in the 20 MHz band.

[0095] As shown at the topmost part of FIG. 8, 26 units (i.e., units corresponding to 26 tones) may be allocated. Six tones may be used as guard bands in the leftmost band of the 20 MHz band, and five tones may be used as guard bands in the rightmost band of the 20 MHz band. Also, seven DC tones may be inserted in the center band, i.e., the DC band, and there may be 26 units corresponding to 13 tones on each side of the DC band. Also, 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for an STA or a user.

[0096] The RU arrangement in FIG. 8 is utilized not only in the situation for multiple users (MUs) but also in the situation for a single user (SU). In this case, as shown at the bottommost part of FIG. 8, it is possible to use one 242-unit. In this case, three DC tones may be inserted.

[0097] In an example of FIG. 8, RUs of various sizes are illustrated, namely, 26-RU, 52-RU, 106-RU, 242-RU, etc. However, the specific sizes of such RUs may be reduced or expanded. Therefore, in the present disclosure, the specific size of each RU (i.e., the number of corresponding tones) is not limited and is exemplary. Also, in the present disclosure, within a predetermined bandwidth (e.g., 20, 40, 80, 160, 320 MHz,...), the number of RUs may vary depending on the size of the RU. The point that the size and / or the number of RUs can be changed in the examples of FIGS. 9 and / or 10 described below is the same as the example of FIG. 8.

[0098] FIG. 9 is a diagram showing an exemplary arrangement of resource units (RUs) used on a 40 MHz band.

[0099] Similar to the use of RUs of various sizes in an example of FIG. 8, in an example of FIG. 9, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. may be used. Also, five DC tones may be inserted at the center frequency, twelve tones may be used as guard bands in the leftmost band of the 40 MHz band, and eleven tones may be used as guard bands in the rightmost band of the 40 MHz band.

[0100] Also, as shown in the same figure, when used for a single user, 484-RU may be used.

[0101] FIG. 10 is a diagram showing an exemplary arrangement of resource units (RUs) used on an 80 MHz band.

[0102] In an example of FIG. 8 and FIG. 9, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. may also be used in an example of FIG. 10, just as RUs of various sizes were used. Also, in an 80 MHz PPDU, the RU arrangements of HE PPDU and EHT PPDU may be different from each other, and the illustration in FIG. 10 shows an example of the RU arrangement for an 80 MHz EHT PPDU. In the illustration of FIG. 10, 12 tones are used as a Guard band in the leftmost band of the 80 MHz band, and 11 tones are used as a Guard band in the rightmost band of the 80 MHz band, which is the same in both HE PPDU and EHT PPDU. Different from the case where 7 DC tones are inserted in the DC band in HE PPDU and there is one 26-RU corresponding to 13 tones on each side of the DC band, in EHT PPDU, 23 DC tones are inserted in the DC band, and there is one 26-RU on each of the left and right sides of the DC band. Different from the case where there is one null subcarrier between 242-RUs that are not in the center band in HE PPDU, there are 5 null subcarriers in EHT PPDU. One 484-RU in HE PPDU does not include null subcarriers, but one 484-RU in EHT PPDU includes 5 null subcarriers.

[0103] Also, as shown in the same figure, when used for a single user, 996-RU may be used, and in this case, the insertion of 5 DC tones is common in both HE PPDU and EHT PPDU.

[0104] EHT PPDUs above 160 MHz may be configured with multiple 80 MHz sub-blocks of FIG. 10. The RU arrangement for each 80 MHz sub-block may be the same as the RU arrangement of the 80 MHz EHT PPDU of FIG. 10. When the 80 MHz sub-blocks of a 160 MHz or 320 MHz EHT PPDU are not punctured and the entire 80 MHz sub-blocks are used as part of an RU or MRU (Multiple RU), the 80 MHz sub-blocks may use the 996-RU of FIG. 10.

[0105] Here, an MRU corresponds to a group of sub-carriers (or tones) composed of multiple RUs. The multiple RUs that make up an MRU may be RUs of the same size or RUs of different sizes from each other. For example, a single MRU may be defined as 52 + 26 - tone, 106 + 26 - tone, 484 + 242 - tone, 996 + 484 - tone, 996 + 484 + 242 - tone, 2×996 + 484 - tone, 3×996 - tone, or 3×996 + 484 - tone. Here, the multiple RUs that make up one MRU may correspond to RUs of a small size (e.g., 26, 52, 106) or RUs of a large size (e.g., 242, 484, 996, etc.). That is, one MRU including RUs of a small size and RUs of a large size may not be configured / defined. Also, the multiple RUs that make up one MRU may be continuous or non - continuous in the frequency domain.

[0106] When an 80 MHz sub - block contains RUs smaller than 996 tones or a portion of the 80 MHz sub - block is punctured, the 80 MHz sub - block may use an RU arrangement other than the 996 - tone RU.

[0107] The RU of the present disclosure may be used for uplink (UL) and / or downlink (DL) communication. For example, when trigger-based UL-MU communication is performed, the STA (e.g., AP) that transmits the trigger may use trigger information (e.g., a trigger frame or TRS (triggered response scheduling)) to allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA. Thereafter, the first STA can transmit a first trigger-based (TB) PPDU based on the first RU, and the second STA can transmit a second TB PPDU based on the second RU. The first / second TB PPDUs may be transmitted to the AP in the same time interval.

[0108] For example, when a DL MU PPDU is configured, the STA (e.g., AP) that transmits the DL MU PPDU can allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA. That is, the transmitting STA (e.g., AP) can transmit the HE-STF, HE-LTF, and Data fields for the first STA using the first RU and the HE-STF, HE-LTF, and Data fields for the second STA using the second RU within one MU PPDU.

[0109] Information regarding the RU allocation may be signaled in the HE-SIG-B of the HE PPDU format.

[0110] FIG. 11 shows an exemplary structure of the HE-SIG-B field.

[0111] As shown in the figure, the HE-SIG-B field may include a common field and a user-specific field. When HE-SIG-B compression is applied (e.g., in the case of full-bandwidth MU-MIMO transmission), the common field may not be included in HE-SIG-B, and the HE-SIG-B content channel may include only the user-specific field. When HE-SIG-B compression is not applied, the common field may be included in HE-SIG-B.

[0112] The common field may include information regarding RU allocation (e.g., RU assignment, RUs allocated for MU-MIMO, the number of MU-MIMO users (STAs), etc.).

[0113] The common field may include N * 8 RU allocation sub-fields. Here, N is the number of sub-fields, and it may have values such as N = 1 for a 20 or 40 MHz MU PPDU, N = 2 for an 80 MHz MU PPDU, N = 4 for a 160 MHz or 80 + 80 MHz MU PPDU,.... One 8-bit RU allocation sub-field can indicate the size (26, 52, 106, etc.) and frequency position (or RU index) of the RUs included in the 20 MHz band.

[0114] For example, if the value of the 8-bit RU allocation sub-field is 00000000, 9 26-RUs from the leftmost to the rightmost in the example of Figure 8 are arranged in order. If the value is 00000001, 7 26-RUs and 1 52-RU are arranged in order from the leftmost to the rightmost. If the value is 00000010, it can be shown that 5 26-RUs, 1 52-RU, and 2 26-RUs are arranged in order from the leftmost to the rightmost.

[0115] As an additional example, if the value of the 8-bit RU allocation subfield is 01000y2y1y0, it can be shown that one 106-RU and five 26-RUs are arranged in order from the leftmost to the rightmost in the example of FIG. 8. In this case, for the 106-RU, multiple users / STAs may be allocated in the MU-MIMO mode. Specifically, up to eight users / STAs may be allocated to the 106-RU, and the number of users / STAs allocated to the 106-RU is determined based on 3-bit information (i.e., y2y1y0). For example, when the 3-bit information (y2y1y0) corresponds to the decimal value N, the number of users / STAs allocated to the 106-RU may be N + 1.

[0116] Basically, one user / STA may be allocated to each of the plurality of RUs, and different users / STAs may be allocated to different RUs. For RUs of a predetermined size or more (e.g., 106, 242, 484, 996-tone,...), multiple users / STAs may be allocated to one RU, and the MU-MIMO mode may be applied to the multiple users / STAs.

[0117] The set of user-specific fields includes information on how all users (STAs) of the PPDU decode their own payloads. The user-specific field may include zero or more user block fields. The non-final user block field includes two user fields (i.e., information used for decoding at two STAs). The final user block field includes one or two user fields. The number of user fields may be indicated by the RU allocation subfield of HE-SIG-B, by the number of symbols of HE-SIG-B, or by the MU-MIMO user field of HE-SIG-A. The user-specific field may be encoded separately or independently from the common field.

[0118] FIG. 12 is a diagram for explaining the MU-MIMO scheme in which a plurality of users / STAs are assigned to one RU.

[0119] In the example of FIG. 12, assume that the value of the RU allocation subfield is 01000010. This corresponds to the case where y2y1y0 = 010 in 01000y2y1y0. 010 corresponds to 2 in decimal (i.e., N = 2), and it can be shown that 3 (= N + 1) users are assigned to one RU. In this case, one 106-RU and five 26-RUs may be arranged in order from the leftmost to the rightmost of a specific 20 MHz band / channel. Three users / STAs may be assigned to the 106-RU in the MU-MIMO scheme. As a result, a total of 8 users / STAs are assigned to the 20 MHz band / channel, and the user-specific field of HE-SIG-B may include 8 user fields (i.e., 4 user block fields). The 8 user fields may be assigned (assign) to the RU as shown in FIG. 12.

[0120] The user field may be configured based on two formats. The user field for MU-MIMO assignment may be configured in the first format, and the user field for non-MU-MIMO assignment may be configured in the second format. Referring to an example of FIG. 12, user fields 1 to 3 may be based on the first format, and user fields 4 to 8 may be based on the second format. The first format and the second format may include bit information of the same length (e.g., 21 bits).

[0121] The user field of the first format (i.e., the format for MU-MIMO allocation) may be configured as follows. For example, out of the total 21 bits of one user field, B0 to B10 include the identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11 to 14 include spatial configuration information such as the number of spatial streams for the user, B15 to B18 include MCS (Modulation and coding scheme) information applied to the Data field of the PPDU, B19 is defined as a reserved field, and B20 may include coding type (e.g., BCC (binary convolutional coding) or LDPC (low-density parity check)) information applied to the Data field of the PPDU.

[0122] The user field of the second format (i.e., the format for non-MU-MIMO allocation) may be configured as follows. For example, out of the total 21 bits of one user field, B0 to B10 include the identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11 to B13 include the number of spatial streams (NSTS) information applied to the RU, B14 includes information indicating the availability of beamforming (or the availability of applying the beamforming steering matrix), B15 to B18 include MCS (Modulation and coding scheme) information applied to the Data field of the PPDU, B19 includes information indicating the availability of DCM (dual carrier modulation), and B20 may include coding type (e.g., BCC or LDPC) information applied to the Data field of the PPDU.

[0123] The MCS, MCS information, MCS index, MCS field, etc. used in the present disclosure may be displayed with specific index values. For example, the MCS information may be displayed as index 0 to index 11. The MCS information may include information regarding the constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information regarding the coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). Information regarding the channel coding type (e.g., BCC or LDPC) may be omitted from the MCS information.

[0124] FIG. 13 shows an example of a PPDU format to which the present disclosure is applicable.

[0125] The PPDU in FIG. 13 may be given various names such as an EHT PPDU, a transmission PPDU, a reception PPDU, a first type or an Nth type PPDU. For example, the PPDU or EHT PPDU of the present disclosure can be given various names such as a transmission PPDU, a reception PPDU, a first type or an Nth type PPDU. Also, the EHT PPU is available in an EHT system and / or a new wireless LAN system that improves the EHT system.

[0126] The EHT MU PPDU in FIG. 13 corresponds to a PPDU that carries one or more data (or PSDU) for one or more users. That is, the EHT MU PPDU may be used for either SU transmission or MU transmission. For example, the EHT MU PPDU may correspond to a PPDU for one receiving STA or a plurality of receiving STAs.

[0127] The EHT TB PPDU in FIG. 13 omits the EHT-SIG as compared to the EHT MU PPDU. A STA that has received a trigger (e.g., a trigger frame or TRS) for UL MU transmission can perform UL transmission based on the EHT TB PPDU format.

[0128] In the exemplification of the EHT PPDU format of FIG. 13, L-STF to EHT-LTF may correspond to a preamble or a physical preamble and may be generated / transmitted / received / acquired / decoded at the physical layer.

[0129] The subcarrier frequency spacing of L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and the EHT-SIG field (which are referred to as the pre-EHT modulated fields) may be defined as 312.5 kHz. The subcarrier frequency spacing of EHT-STF, EHT-LTF, Data, and the PE field (which are referred to as the EHT modulated fields) may be defined as 78.125 kHz. That is, the tone / subcarrier index of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be displayed in units of 312.5 kHz, and the tone / subcarrier index of the EHT-STF, EHT-LTF, Data, and PE fields may be displayed in units of 78.125 kHz.

[0130] L-LTF and L-STF in FIG. 13 may be configured identically to the corresponding fields of the PPDU described in FIGS. 6 and 7.

[0131] The L-SIG field in FIG. 13 is composed of 24 bits and may be used to communicate rate and length information. For example, the L-SIG field may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit Tail field. For example, the 12-bit Length field may include information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the Length field may be determined to be a multiple of 3. For example, for HE PPDUs, the value of the Length field may be determined to be a multiple of 3 + 1 or a multiple of 3 + 2.

[0132] For example, the transmitting STA can apply BCC encoding based on a coding rate of 1 / 2 to the 24-bit information in the L-SIG field. Subsequently, the transmitting STA can obtain 48-bit BCC-coded bits. BPSK modulation may be applied to the 48-bit coded bits, and 48 BPSK symbols may be generated. The transmitting STA can map the 48 BPSK symbols to positions excluding pilot subcarriers (e.g., {subcarrier indices -21, -7, +7, +21}) and the DC subcarrier (e.g., {subcarrier index 0}). As a result, the 48 BPSK symbols may be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can further map signals of {-1, -1, -1, 1} to the subcarrier indices {-28, -27, +27, +28}. The signals may be used for channel estimation for the frequency regions corresponding to {-28, -27, +27, +28}.

[0133] The transmitting STA can generate an RL-SIG that is generated identically to the L-SIG. BPSK modulation is applied to the RL-SIG. The receiving STA can determine that the received PPDU is a HE PPDU or an EHT PPDU based on the presence of the RL-SIG.

[0134] A U-SIG (Universal SIG) may be inserted after the RL-SIG in FIG. 13. The U-SIG can have various names such as the first SIG field, the first SIG, the first type SIG, the control signal, the control signal field, the first (type) control signal, etc.

[0135] The U-SIG may include N-bit information and may include information for identifying the type of the EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol for the U-SIG (e.g., an OFDM symbol) may have a duration of 4 us, and the U-SIG may have an overall duration of 8 us. Each symbol of the U-SIG may be used to transmit 26-bit information. For example, each symbol of the U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.

[0136] In the U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 un-coded bits) may be transmitted. The first symbol of the U-SIG (e.g., U-SIG-1) transmits the first X-bit information (e.g., 26 un-coded bits) among the total A-bit information, and the second symbol of the U-SIG (e.g., U-SIG-2) can transmit the remaining Y-bit information (e.g., 26 un-coded bits) among the total A-bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can perform convolutional encoding (e.g., BCC encoding) based on a rate of R = 1 / 2 to generate 52-coded bits and can perform interleaving on the 52-coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols assigned to each U-SIG symbol. One U-SIG symbol may be transmitted based on 56 tones (sub-carriers) from sub-carrier index -28 to sub-carrier index +28 except for the DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (sub-carriers) excluding the tones -21, -7, +7, +21 which are pilot tones.

[0137] For example, the A-bit information (e.g., 52 un-coded bit) transmitted by U-SIG may include a CRC field (e.g., a 4-bit long field) and a tail field (e.g., a 6-bit long field). The CRC field and the tail field may be transmitted in the second symbol of U-SIG. The CRC field may be generated based on 26 bits assigned to the first symbol of U-SIG and the remaining 16 bits excluding the CRC / tail field within the second symbol, and may be generated based on a conventional CRC calculation algorithm. Also, the tail field may be used to terminate the trellis of a convolutional decoder and may be set to 0, for example.

[0138] The A-bit information (e.g., 52 un-coded bit) transmitted by U-SIG (or, U-SIG field) can be distinguished into version-independent bits and version-dependent bits. For example, the size of the version-independent bits may be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first symbol and the second symbol of U-SIG. For example, the version-independent bits and the version-dependent bits may be named variously such as the first control bit and the second control bit.

[0139] For example, the version-independent bits of U-SIG may include a 3-bit physical layer version identifier. For example, the 3-bit physical layer version identifier may include information about the physical layer version of the transmitted and received PPDU. For example, the first value of the 3-bit physical layer version identifier can indicate that the transmitted and received PPDU is an EHT PPDU. In other words, when the transmitting STA transmits an EHT PPDU, it can set the 3-bit physical layer version identifier to the first value. In other words, the receiving STA can determine that the received PPDU is an EHT PPDU based on the physical layer version identifier having the first value.

[0140] For example, the version-independent bits of U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.

[0141] For example, the version-independent bits of U-SIG may include information about the length of the TXOP (transmission opportunity) and information about the BSS color ID.

[0142] For example, when EHT PPDUs are classified into various types (for example, various types such as EHT PPDUs related to SU mode, EHT PPDUs related to MU mode, EHT PPDUs related to TB mode, EHT PPDUs related to Extended Range transmission, etc.), information about the type of EHT PPDU may be included in the version-dependent bits of U-SIG.

[0143] For example, the U-SIG may include: 1) a bandwidth field containing information about the bandwidth; 2) a field containing information about the MCS method applied to the EHT-SIG; 3) an indication field containing information about whether the DCM method is applied to the EHT-SIG; 4) a field containing information about the number of symbols used for the EHT-SIG; 5) a field containing information about whether the EHT-SIG is generated across the entire bandwidth; 6) a field containing information about the type of EHT-LTF / STF; 7) information about a field indicating the length of the EHT-LTF and the CP length.

[0144] Preambles puncturing may be applied to the PPDU of FIG. 13. Preambles puncturing can mean transmitting a PPDU where there is no signal present in one or more 20 MHz subchannels in the bandwidth of the PPDU. Preambles puncturing may be applied to the PPDU transmitted to one or more users. For example, the resolution of preambles puncturing may be 20 MHz for EHT MU PPDUs in OFDMA transmissions with a bandwidth greater than 40 MHz and non-OFDMA transmissions with 80 MHz and 160 MHz bandwidths. That is, in the above cases, puncturing for subchannels smaller than a 242-tone RU may not be allowed. Also, for EHT MU PPDUs in non-OFDMA transmissions with a 320 MHz bandwidth, the resolution of preambles puncturing may be 40 MHz. That is, puncturing for subchannels smaller than a 484-tone RU in the 320 MHz bandwidth may not be allowed. Also, preambles puncturing may not be applied to the primary 20 MHz channel in the EHT MU PPDU.

[0145] For example, for an EHT MU PPDU, information regarding preamble puncturing may be included in the U-SIG and / or EHT-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding the preamble puncturing applied to the PPDU.

[0146] For example, the U-SIG and EHT-SIG can include information regarding preamble puncturing based on the following method. When the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in 80 MHz units. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding the preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Also, the first field of the second U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding the preamble puncturing applied to the second 80 MHz band (i.e., information regarding the preamble puncturing pattern). The EHT-SIG consecutive to the first U-SIG may include information regarding the preamble puncturing applied to the second 80 MHz band (i.e., information regarding the preamble puncturing pattern), and the EHT-SIG consecutive to the second U-SIG may include information regarding the preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern).

[0147] As an addition or alternative, the U-SIG and EHT-SIG may include information regarding preamble puncturing based on the following method. The U-SIG may include information regarding preamble puncturing for the entire band (i.e., information regarding the preamble puncturing pattern). That is, the EHT-SIG may not include information regarding preamble puncturing, and only the U-SIG may include information regarding preamble puncturing (i.e., information regarding the preamble puncturing pattern).

[0148] The U-SIG may be configured in units of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG may be replicated. That is, the same four U-SIGs may be included in the 80 MHz PPDU. A PPDU with a bandwidth exceeding 80 MHz may include different U-SIGs.

[0149] The EHT-SIG in FIG. 13 may include control information for the receiving STA. The EHT-SIG may be transmitted in at least one symbol, and one symbol may have a length of 4 us. Information regarding the number of symbols used for the EHT-SIG may be included in the U-SIG.

[0150] The EHT-SIG may include the technical features of the HE-SIG-B described in FIGS. 11 and 12. For example, the EHT-SIG may include a common field and a user-specific field, as in the example of FIG. 8. The common field of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0151] Similar to an example of FIG. 11, the common fields of the EHT-SIG and the user-specific fields of the EHT-SIG may be coded separately. One user block field included in the user-specific field contains information for two user fields, but the last user block field included in the user-specific field may contain one or two user fields. That is, one user block field of the EHT-SIG may contain at most two user fields. Similar to an example of FIG. 12, each user field may be related to a MU-MIMO allocation or a non-MU-MIMO allocation.

[0152] Similar to an example of FIG. 11, the common field of the EHT-SIG may include CRC bits and Tail bits. The length of the CRC bits may be determined to be 4 bits, the length of the Tail bits may be determined to be 6 bits, and may be set to 000000.

[0153] Similar to an example of FIG. 11, the common field of the EHT-SIG may include RU allocation information. RU allocation information can mean information regarding the location of the RUs to which a plurality of users (i.e., a plurality of receiving STAs) are allocated. RU allocation information may be configured in units of 9 bits (or, N bits).

[0154] Modes in which common fields of the EHT-SIG are omitted may be supported. A mode in which common fields of the EHT-SIG are omitted can be called the compressed mode. When the compressed mode is used, multiple users of the EHT PPDU (i.e., multiple receiving STAs) can decode the PPDU (e.g., the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) received in the same frequency band. When the non-compressed mode is used, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU can receive the PPDU (e.g., the data field of the PPDU) in different frequency bands from each other.

[0155] The EHT-SIG may be configured based on various MCS techniques. As described above, information related to the MCS technique applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on the DCM technique. The DCM technique can provide an effect similar to frequency diversity, reduce interference, and improve coverage by reusing the same signal on two subcarriers. For example, modulated symbols to which the same modulation technique is applied may be repeatedly mapped on available tones / subcarriers. For example, among the N data tones (e.g., 52 data tones) allocated for the EHT-SIG, modulated symbols (e.g., BPSK modulated symbols) to which a specific modulation technique is applied are mapped to the first consecutive half of the tones (e.g., the 1st to 26th tones), and modulated symbols (e.g., BPSK modulated symbols) to which the same specific modulation technique is applied are also mapped to the remaining consecutive half of the tones (e.g., the 27th to 52nd tones). That is, the modulated symbol mapped to the 1st tone is the same as the modulated symbol mapped to the 27th tone. As described above, information (e.g., a 1-bit field) related to whether the DCM technique is applied to the EHT-SIG may be included in the U-SIG. The EHT-STF in FIG. 13 may be used to improve automatic gain control (AGC) estimation in a MIMO environment or an OFDMA environment. The EHT-LTF in FIG. 13 may be used to estimate the channel in a MIMO environment or an OFDMA environment.

[0156] Information regarding the type of STF and / or LTF (including information regarding the GI (guard interval) applied to the LTF) may be included in the U-SIG field and / or the EHT-SIG field in FIG. 13, etc.

[0157] The PPDU in FIG. 13 (i.e., the EHT PPDU) may be configured based on an example of the RU arrangement in FIGS. 8 to 10.

[0158] For example, an EHT PPDU transmitted on a 20 MHz band, i.e., a 20 MHz EHT PPDU, may be configured based on the RUs in FIG. 8. That is, the locations of the RUs of the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in FIG. 8. An EHT PPDU transmitted on a 40 MHz band, i.e., a 40 MHz EHT PPDU, may be configured based on the RUs in FIG. 9. That is, the locations of the RUs of the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in FIG. 9.

[0159] An EHT PPDU transmitted on an 80 MHz band, i.e., an 80 MHz EHT PPDU, may be configured based on the RUs in FIG. 10. That is, the locations of the RUs of the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in FIG. 10. The tone-plan for 80 MHz in FIG. 10 may correspond to two repetitions of the tone-plan for 40 MHz in FIG. 9.

[0160] The tone-plan for 160 / 240 / 320 MHz may be configured in a form that repeats the pattern in FIG. 9 or FIG. 10 a plurality of times.

[0161] The PPDU in FIG. 13 may be identified as an EHT PPDU based on the following method.

[0162] The receiving STA can determine that the type of the received PPDU is an EHT PPDU based on the following items. For example, 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) an RL-SIG in which the L-SIG of the received PPDU is repeated is detected, and 3) when the result of applying modulo 3 operation to the value of the Length field of the L-SIG of the received PPDU (i.e., the remainder when divided by 3) is detected as 0, the received PPDU may be determined to be an EHT PPDU. When the received PPDU is determined to be an EHT PPDU, the receiving STA can determine the type of the EHT PPDU based on the bit information included in the symbol after the RL-SIG in FIG. 13. In other words, the receiving STA can determine that the received PPDU is an EHT PPDU based on 1) the first symbol after the L-LTF signal that is BSPK, 2) the RL-SIG that is consecutive to the L-SIG field and is the same as the L-SIG, and 3) the L-SIG including the Length field whose result of applying modulo 3 is set to 0.

[0163] For example, the receiving STA can determine that the type of the received PPDU is an HE PPDU based on the following items. For example, 1) the first symbol after the L-LTF signal is BPSK, 2) an RL-SIG in which the L-SIG is repeated is detected, and 3) when the result of applying modulo 3 to the Length value of the L-SIG is detected as 1 or 2, the received PPDU may be determined to be an HE PPDU.

[0164] For example, the receiving STA can determine that the type of the received PPDU is a non-HT, HT, and VHT PPDU based on the following items. For example, 1) the first symbol after the L-LTF signal is BPSK, and 2) when an RL-SIG in which the L-SIG is repeated is not detected, the received PPDU may be determined to be a non-HT, HT, and VHT PPDU.

[0165] Also, when the receiving STA detects an RL-SIG in which the L-SIG is repeated in the received PPDU, it can be determined that the PPDU is a HE PPDU or an EHT PPDU. In this case, if the rate (6 Mbps) check fails, the received PPDU may be determined to be a non-HT, HT, or VHT PPDU. If the rate (6 Mbps) check and the parity check are passed, and it is detected that the result of applying modulo 3 to the Length value of the L-SIG is 0, the received PPDU may be determined to be an EHT PPDU, and if the result of Length mod 3 is not 0, it may be determined to be a HE PPDU.

[0166] The PPDU of FIG. 13 may be used to transmit and receive various types of frames. For example, the PPDU of FIG. 13 may be used for one or more (simultaneous) transmissions and receptions of control frames, management frames, or data frames.

[0167] FIG. 14 is a diagram showing an exemplary format of a trigger frame to which the present disclosure is applicable.

[0168] The trigger frame can allocate resources for one or more TB PPDU transmissions and request TB PPDU transmissions. The trigger frame may also include other information required by the STA that transmits the TB PPDU in response thereto. The trigger frame may include a common information (common info) and a user information list (user info list) field in the frame body.

[0169] The common information field may include information that is commonly applied to one or more TB PPDU transmissions requested by the trigger frame, such as trigger type, UL length, presence or absence of a subsequent trigger frame (e.g., More TF), presence or absence of a CS (channel sensing) requirement, UL BW (bandwidth), etc. FIG. 14 exemplarily shows the EHT variant common information field format.

[0170] The 4-bit sized trigger type subfield may have values from 0 to 15. Among them, the values 0, 1, 2, 3, 4, 5, 6, and 7 of the trigger type subfield are defined to correspond to basic, BFRP (Beamforming Report Poll), MU-BAR (multi user-block acknowledgement request), MU-RTS (multi user-request to send), BSRP (Buffer Status Report Poll), GCR (groupcast with retries) MU-BAR, BQRP (Bandwidth Query Report Poll), and NFRP (NDP Feedback Report Poll) respectively, and the values from 8 to 15 are defined as reserved.

[0171] Among the common information, the trigger dependent common info subfield may include information selectively included based on the trigger type.

[0172] A special user info field may be included in the trigger frame. The special user info field does not include user-specific information and includes extended common information not provided in the common information field.

[0173] The user information list includes one or more user info fields. In FIG. 14, the EHT variant user information field format is exemplarily shown.

[0174] The AID12 subfield basically indicates that it is a user information field for the STA having the said AID. Additionally, when the AID12 field has a predefined specific value, it may be utilized for other purposes such as allocating a Random Access (RA)-RU or being configured in the form of a special user info field. The special user info field is a user information field that does not contain user-specific information but contains extended common information not provided in the common information field. For example, the special user info field may be identified by an AID12 value of 2007, and the special user info field flag subfield within the common information field can indicate whether it includes the special user info field.

[0175] The RU allocation subfield can indicate the size and position of the RU / MRU. For this purpose, the RU allocation subfield may be analyzed together with the PS160 (primary / secondary 160MHz) subfield of the user information field, the UL BW subfield of the common information field, etc.

[0176] Additionally, in the present disclosure, the tone plan may be related to the rules for determining the size and / or position of the Resource Unit (RU). Hereinafter, the tone plan applied to the HE PPDU (i.e., the PPDU based on the IEEE 802.11ax standard) will be described as an example. Specifically, the size / position of the RU applied to the HE PPDU and the control information related to the RU applied to the HE PPDU will be described.

[0177] In the present disclosure, the control information related to the RU (or the control information related to the tone plan) may include control information regarding the size, position of the RU, information of the user (user) STA assigned to the specific RU, the frequency bandwidth for the PPDU in which the RU is included, and / or the modulation method applied to the specific RU. The control information related to the RU may be included in the SIG field. For example, the control information related to the RU may be included within the HE-SIG-B field. That is, in the process of generating the transmission PPDU, the transmitting STA can include the control information for the RU included in the PPDU within the HE-SIG-B field. Also, the receiving STA receives the HE-SIG-B included in the received PPDU, obtains the control information included in the HE-SIG-B, determines whether there is an RU assigned to the receiving STA, and can decode the RU assigned based on the HE-SIG-B.

[0178] In an existing wireless LAN system (e.g., the IEEE 802.11ax standard), the HE-STF, HE-LTF, and data fields may be configured in units of RUs. That is, when a first RU for a first receiving STA is set, the STF / LTF / data fields for the first receiving STA may be transmitted and received in the first RU.

[0179] In an existing wireless LAN system (e.g., the IEEE 802.11ax standard), a PPDU for one receiving STA (i.e., an SU PPDU) and a PPDU for multiple receiving STAs (i.e., an MU PPDU) may be defined separately, and the tone plan for each may be defined separately.

[0180] Specifically, an RU may include a plurality of subcarriers. For example, when an RU includes N subcarriers, it may be expressed as N-tone RU or N RU. The position of a specific RU may be indicated by a subcarrier index. Here, the subcarrier index may be defined in units of subcarrier frequency spacing. For example, in a wireless LAN system, the subcarrier frequency spacing is 312.5 kHz or 78.125 kHz, and the subcarrier frequency spacing for an RU may be 78.125 kHz. That is, the subcarrier index "+1" for an RU means a position further increased by 78.125 kHz based on the DC tone, and the subcarrier index "-1" for an RU may mean a position further decreased by 78.125 kHz based on the DC tone. For example, when the position of a specific RU is displayed as [-121:-96], the RU is located in the region from subcarrier index -121 to subcarrier index -96, and as a result, the RU may include 26 subcarriers. Also, an N-tone RU may include already set pilot tones.

[0181] Bandwidth indication based on a trigger frame for non-legacy PPDUs and / or aggregated PPDUs

[0182] In a wireless LAN system, a trigger frame can be used to perform TB PPDU transmission corresponding to UL multi-user (MU) transmission.

[0183] In connection with this, in the present disclosure, based on the aforementioned trigger frame (e.g., related to FIG. 14), a trigger frame for transmission and reception of a TB PPDU in a next-generation wireless LAN system (e.g., Next 11 be, UHR, etc.), and a method for performing a bandwidth indication for the TB PPDU based on the same are proposed.

[0184] In addition, with respect to the proposed method in the present disclosure, in terms of improving efficiency and throughput, a trigger frame considering a TB PPDU considering a next-generation wireless LAN system and / or a TB A-PPDU (aggregated-PPDU) capable of simultaneously transmitting PPDUs of different wireless LAN versions may be considered.

[0185] The trigger frame proposed in the present disclosure may be used to trigger / solicit the transmission of a TB PPDU in a next-generation wireless LAN system. As an addition or alternative, the trigger frame proposed in the present disclosure may be used to trigger / solicit the transmission of a TB A-PPDU.

[0186] FIG. 15 illustrates an A-PPDU structure to which the present disclosure is applicable.

[0187] Referring to FIG. 15, the A-PPDU may be composed of a first sub PPDU, a second sub PPDU, and a third sub PPDU.

[0188] For example, the first sub PPDU may support a 160 MHz bandwidth, the second sub PPDU may support an 80 MHz bandwidth, and the third sub PPDCU may support an 80 MHz bandwidth.

[0189] In this regard, each sub PPDU may be a PPDU for different wireless LAN versions. For example, each sub PPDU may correspond to a HE PPDU, an EHT PPDU, or a next-generation PPDU (e.g., next version PPDU, UHR PPDU, etc.).

[0190] In the present disclosure, an enhanced trigger frame that improves the existing trigger frame (e.g., related to FIG. 14) is proposed to trigger / solicit a TB PPDU and various TB A-PPDUs in a next-generation wireless LAN system.

[0191] The upward trigger frame may correspond to the next version trigger frame considered in the next-generation wireless LAN system.

[0192] For clarity of explanation, the improved trigger frame proposed in the present disclosure is referred to as a non-legacy trigger frame. As an example, the legacy trigger frame may include a trigger frame that triggers / requests a PPDU of the HE version, a trigger frame that triggers / requests a PPDU of the EHT version (e.g., FIG. 14).

[0193] In the description of the present disclosure, "non-legacy" can mean the next version after the existing version / variant.

[0194] As a specific example, in the present disclosure, the expression of the version / variant after the EHT version / variant (e.g., UHR) may be alternatively applied for "non-legacy".

[0195] The non-legacy trigger frame may include a non-legacy variant common info field, a non-legacy variant special user info field, and a non-legacy user info field.

[0196] Here, the non-legacy variant common info field, the non-legacy variant special user info field, and the non-legacy user info field can respectively mean the variant common info field, the variant special user info field, and the user info field for the next version (e.g., next 11 be, UHR, etc.) in the next-generation wireless LAN system.

[0197] The non-legacy variant common information field in the proposal of the present disclosure may include information / sub-fields based on the legacy variant common information field (e.g., the HE / EHT variant common information field related to FIG. 14), and may further include instruction information for the non-legacy trigger frame, etc. Note that the non-legacy variant common information field may include instruction information on what form of TB PPDU to trigger, etc.

[0198] In this regard, the proposed method in the present disclosure may correspond to the bandwidth indication method for each TB PPDU when the TB PPDU configuration is indicated based on the non-legacy trigger frame.

[0199] Note that the non-legacy variant special user information field in the proposal of the present disclosure may include information / sub-fields based on the legacy variant special user information field (e.g., the EHT variant special user information field related to FIG. 14). In this regard, in the case of the non-legacy variant special user information field, the reserved subfield of the legacy variant special user information field may be utilized to indicate additional bandwidth.

[0200] Note that the non-legacy variant user information field in the proposal of the present disclosure may include information / sub-fields based on the legacy variant special user information field (e.g., the EHT variant special user information field related to FIG. 14). In this regard, in the case of the non-legacy variant user information field, the RU allocation subfield and / or the reserved subfield, etc. of the legacy variant special user information field may be utilized to indicate the channel and the allocated RU / MRU information in wide bandwidth.

[0201] Depending on the type / composition of the triggered TB PPDU, a special user information field, a legacy variant user information field (e.g., HE variant user information field, EHT variant user information field), etc. may be present / included in the non-legacy trigger frame.

[0202] As described above, hereinafter, in the present disclosure, a method for indicating the bandwidth of the TB PPDU is proposed. In connection with this proposal, in addition to the bandwidth up to 320 MHz defined in the existing wireless LAN system, bandwidths of 480 MHz / 640 MHz may also be further considered.

[0203] For the bandwidth indication proposed in the present disclosure, the UL BW (bandwidth) subfield of the non-legacy variant common information field and the UL BW extension subfield of the non-legacy variant special user information field may be used. In connection with this, the UL BW subfield may follow the definition in the existing common information field, and the UL BW extension subfield may follow the definition in the existing special user information field or a new definition for the proposed method in the present disclosure.

[0204] As an example, Table 1 below illustrates a method of defining and using additional bandwidth for the reserved values of the UL BW subfield and the UL BW extension subfield. The illustration in Table 1 may be utilized to trigger TB A-PPDU, etc.

[0205]

Table 1

[0206] Note that, different from the existing special user information field (e.g., EHT special user information field), an additional UL BW extension subfield (e.g., UL BW Extension2 subfield) may be further defined / exist in the non-legacy variant special user information field. Here, the additional UL BW extension subfield may be defined based on some or all of the bits (e.g., B37~B39, etc.) corresponding to the reserved subfields in the existing special user information field.

[0207] Hereinafter, in the present disclosure, for clarity of description, the aforementioned UL BW extension subfield is referred to as the first UL BW extension subfield, and the aforementioned additional UL BW extension subfield is referred to as the second UL BW extension subfield.

[0208] In the present disclosure, various embodiments propose specific methods for indicating the bandwidth in various TB PPDU situations / configurations by utilizing the UL BW subfield of the non-legacy variant common information field and the first and second UL BW extension subfields of the non-legacy variant special user information field.

[0209] The embodiments described below are only divided for clarity of description, and for bandwidth indication based on non-legacy trigger frames, one or more embodiments may be considered / applied independently or together.

[0210] In the following embodiments, P160 / S160 / P320 / S320 HE TB PPDU / EHT TB PPDU / non-legacy TB PPDU represent HE TB PPDU / EHT TB PPDU / non-legacy TB PPDU with a bandwidth of primary 160MHz / secondary 160MHz / primary 320MHz / secondary 320MHz.

[0211] Example 1

[0212] This embodiment relates to a scheme for indicating bandwidth considering the case where only non-legacy TB PPDUs are triggered.

[0213] The UL BW subfield and / or the first UL BW extension subfield may be utilized to indicate bandwidth up to 320 MHz. The bandwidth indication based on the UL BW subfield and / or the first UL BW extension subfield may be analyzed / considered as the bandwidth indication within the primary 320 (hereinafter, P320).

[0214] The second UL BW extension subfield can further indicate a bandwidth of 480 MHz / 640 MHz.

[0215] In this regard, the second UL BW extension subfield set to a value of 0 can indicate that the bandwidth indicated by the UL BW subfield and the first UL BW extension subfield corresponds to the TB PPDU bandwidth.

[0216] Values other than 0 in the second UL BW extension subfield may be used to indicate wide bandwidth.

[0217] For example, when only 480 MHz is defined / added as the bandwidth, the second UL BW extension subfield set to a value of 1 can indicate a 480 MHz bandwidth. Alternatively, the second UL BW extension subfield set to a value of 1 / 2 can indicate a 480 - 1 MHz / 480 - 2 MHz bandwidth. Alternatively, the second UL BW extension subfield set to a value of 1 / 2 / 3 can indicate a 480 - 1 MHz / 480 - 2 MHz / 480 - 3 MHz bandwidth.

[0218] Here, 480 - 1 MHz / 480 - 2 MHz / 480 - 3 MHz can mean different 480 MHz types (types) divided based on the position of the 480 MHz bandwidth within the frequency band. Additional values may be available depending on the 480 MHz type.

[0219] As another example, when only 640 MHz is defined / added as the bandwidth, the second UL BW extension subfield set to a value of 1 can indicate a 640 MHz bandwidth. Alternatively, the second UL BW extension subfield set to a value of 1 / 2 can indicate a 640 - 1 MHz / 640 - 2 MHz bandwidth. Alternatively, the second UL BW extension subfield set to a value of 1 / 2 / 3 can indicate a 640 - 1 MHz / 640 - 2 MHz / 640 - 3 MHz bandwidth.

[0220] Here, 640 - 1 MHz / 640 - 2 MHz / 640 - 3 MHz can mean different 640 MHz types that are differentiated based on the position of the 640 MHz bandwidth within the frequency band. Additional values may be available depending on the 640 MHz type.

[0221] As another example, when 480 MHz and 640 MHz are defined / added as the bandwidth, the second UL BW extension subfield set to 1 value / 2 values can indicate the 480 MHz / 640 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values can indicate the 480 MHz / 640 - 1 MHz / 640 - 2 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values / 4 values can indicate the 480 MHz / 640 - 1 MHz / 640 - 2 MHz / 640 - 3 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values can indicate the 480 - 1 MHz / 480 - 2 MHz / 640 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values / 4 values can indicate the 480 - 1 MHz / 480 - 2 MHz / 640 - 1 MHz / 640 - 2 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values / 4 values / 5 values can indicate the 480 - 1 MHz / 480 - 2 MHz / 640 - 1 MHz / 640 - 2 MHz / 640 - 3 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values / 4 values can indicate the 480 - 1 MHz / 480 - 2 MHz / 480 - 3 MHz / 640 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values / 4 values / 5 values can indicate the 480 - 1 MHz / 480 - 2 MHz / 480 - 3 MHz / 640 - 1 MHz / 640 - 2 MHz bandwidth. Alternatively, the second UL BW extension subfield set to 1 value / 2 values / 3 values / 4 values / 5 values / 6 values can indicate the 480 - 1 MHz / 480 - 2 MHz / 480 - 3 MHz / 640 - 1 MHz / 640 - 2 MHz / 640 - 3 MHz bandwidth.

[0222] Here, 480 - 1MHz / 480 - 2MHz / 480 - 3MHz can mean different 480MHz types that are divided based on the position of the 480MHz bandwidth within the frequency band. 640 - 1MHz / 640 - 2MHz / 640 - 3MHz can mean different 640MHz types that are divided based on the position of the 640MHz bandwidth within the frequency band. Additional values may be available depending on the 480MHz type and / or 640MHz type.

[0223] The range of available values may be determined by the number of bits used in the various examples described above, and the remaining values other than those in the examples may be reserved.

[0224] Hereinafter, Examples 2 to 4 relate to a scheme for indicating the bandwidth when various forms of TB A - PPDU are triggered.

[0225] In connection with these examples, it is assumed that the sub - PPDU unit (i.e., each PPDU unit that constitutes the A - PPDU) is 160MHz or 320MHz, and the sub - PPDU may be configured using only a part of the bandwidth within the 160MHz / 320MHz channel.

[0226] In these examples, when the bandwidth of the sub - PPDU is indicated, an example where the bandwidth is indicated in the sub - PPDU unit is described, but the indication may be made based on the bandwidth size of the actually transmitted sub - PPDU.

[0227] In the case of the second UL BW extension sub - field, the values proposed in Example 1 described above may be used / applied as they are.

[0228] Example 2

[0229] This example relates to a scheme for indicating the bandwidth considering the case where a TB A - PPDU composed of a HE TB PPDU and a non - legacy TB PPDU is triggered.

[0230] Various forms such as those exemplified below may be considered in connection with the TB A-PPDU, and one or more of the forms exemplified below may be defined. In the following examples, SS160 represents a specific 160 MHz channel within the S320 MHz channel.

[0231] For example, the TB A-PPDU may include a P160 HE TB PPDU and an S160 non-legacy TB PPDU.

[0232] In this case, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., a 160 MHz channel). Whether the non-legacy TB PPDU bandwidth is indicated in the UL BW subfield / First UL BW extension subfield (e.g., a 160 MHz channel), the TB A-PPDU bandwidth may be indicated (e.g., a 320 MHz channel). At this time, the second UL BW extension subfield may be set to 0.

[0233] As another example, the TB A-PPDU may include a P160 HE TB PPDU, an S160 non-legacy TB PPDU, and an SS160 non-legacy TB PPDU.

[0234] In this case, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., a 160 MHz channel). Whether the non-legacy TB PPDU bandwidth within P320 is indicated in the UL BW subfield / First UL BW extension subfield (e.g., a 160 MHz channel), the TB A-PPDU bandwidth within P320 may be indicated (e.g., a 320 MHz channel). The second UL BW extension subfield may indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel).

[0235] As yet another example, the TB A-PPDU may include a P160 HE TB PPDU and an S320 non-legacy TB PPDU.

[0236] In this case, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., 160 MHz channel). The TB A-PPDU bandwidth within P320 may be indicated in the UL BW subfield / First UL BW extension subfield (e.g., 160 MHz channel). The Second UL BW extension subfield may indicate the TB A-PPDU bandwidth (e.g., 480 MHz channel or 640 MHz channel).

[0237] In connection with this example, it may be difficult to indicate the non-legacy TB PPDU bandwidth within P320. Therefore, considering this point, it would be preferable for the UL BW subfield / First UL BW extension subfield to indicate the TB A-PPDU bandwidth not only in this configuration but also in other configurations.

[0238] Alternatively, a reserved value (e.g., 3 / 0 setting) among the values of the UL BW subfield / First UL BW extension subfield may be defined as the 0 MHz channel, and the non-legacy TB PPDU bandwidth within P320 can be indicated (e.g., 0 MHz channel). In this case, it would be preferable for the UL BW subfield / First UL BW extension subfield to indicate the non-legacy TB PPDU in all configurations.

[0239] As an addition or alternative, an exceptional indication method rather than a bandwidth indication within P320 may be considered for the UL BW subfield / First UL BW extension subfield.

[0240] In the case of this exceptional indication method, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., 160 MHz channel). The non-legacy TB PPDU bandwidth may be indicated in the UL BW subfield / First UL BW extension subfield (e.g., 320 MHz channel). The Second UL BW extension subfield may indicate the TB A-PPDU bandwidth (e.g., 480 MHz channel or 640 MHz channel) or may be set to a 0 value.

[0241] When the exceptional indication method is assumed to be preferable when configuring TB A-PPDUs including HE TB PPDUs and non-legacy TB PPDUs, only the configurations of P160 HE TB PPDUs and S160 non-legacy TB PPDUs and that configuration (i.e., the configuration of P160 HE TB PPDUs and S320 non-legacy TB PPDUs) are defined.

[0242] Note that when the exceptional indication method is applied, the UL BW subfield / First UL BW extension subfield needs to be related to the non-legacy TB PPDU bandwidth indication even in the case of other TB A-PPDU configurations, and the specific meaning may vary depending on the configuration. Therefore, this method may not be preferable in terms of consistency. As an example, in some TB A-PPDU configurations, the non-legacy TB PPDU bandwidth within P320 may be indicated, and in some other configurations, the overall non-legacy TB PPDU bandwidth may be indicated.

[0243] As yet another example, the TB A-PPDU may include a P160 HE TB PPDU, an S160 non-legacy TB PPDU, and an S320 non-legacy TB PPDU.

[0244] In this case, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., a 160 MHz channel). Whether the non-legacy TB PPDU bandwidth within P320 is indicated in the UL BW subfield / First UL BW extension subfield (e.g., a 160 MHz channel), or the TB A-PPDU bandwidth within P320 may be indicated (e.g., a 320 MHz channel). The Second UL BW extension subfield can indicate the TB A-PPDU bandwidth (e.g., a 640 MHz channel).

[0245] Example 3

[0246] This embodiment relates to a solution for indicating bandwidth considering the case where a TB A-PPDU composed of an EHT TB PPDU and a non-legacy TB PPDU is triggered.

[0247] In this regard, the proposed method in the present disclosure is proposed by classifying it into the case where an existing special user information field (for example, an EHT variant special user information field) and a non-legacy variant special user information field coexist (hereinafter, Example 3-1) and the case where only the non-legacy variant special user information field exists (hereinafter, Example 3-2).

[0248] (Example 3-1)

[0249] First, regarding the TB A-PPDU composed of an EHT TB PPDU and a non-legacy TB PPDU, the case where an existing special user information field (for example, an EHT variant special user information field) and a non-legacy variant special user information field coexist will be described.

[0250] That is, this corresponds to the case where two UL BW extension sub-fields (the first UL BW extension sub-field in the non-legacy variant special user information field) exist and can be used to indicate the EHT TB PPDU bandwidth and the non-legacy TB PPDU bandwidth, respectively.

[0251] For the TB A-PPDU, bandwidth indication may be performed considering various forms as exemplified below, and one or more of the following exemplified forms may be defined. In the following exemplification, SS160 represents a specific 160 MHz channel within the S320 MHz channel.

[0252] For example, the TB A-PPDU may include a P160 EHT TB PPDU and an S160 non-legacy TB PPDU.

[0253] In this case, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / legacy special user information field (e.g., a 160 MHz channel). Whether the non-legacy TB PPDU bandwidth is indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel), or the TB A-PPDU bandwidth may be indicated (e.g., a 320 MHz channel). At this time, the second UL BW extension subfield within the non-legacy variant special user information field may be set to 0.

[0254] As another example, the TB A-PPDU may include a P160 EHT TB PPDU, an S160 non-legacy TB PPDU, and an SS160 non-legacy TB PPDU.

[0255] In this case, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / legacy special user information field (e.g., a 160 MHz channel). Whether the non-legacy TB PPDU bandwidth within P320 is indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel), or the TB A-PPDU bandwidth within P320 may be indicated (e.g., a 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel).

[0256] As yet another example, the TB A-PPDU may include a P160 EHT TB PPDU and an S320 non-legacy TB PPDU.

[0257] In this case, the EHT TB PPDU bandwidth may be indicated in the UL BW subfield / UL BW extended subfield within the existing special user information field (e.g., a 160 MHz channel). The TB A-PPDU bandwidth in P320 may be indicated in the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel). The second UL BW extended subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel).

[0258] In connection with this example, it may be difficult to indicate the non-legacy TB PPDU bandwidth in P320. Therefore, considering this point, the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field would preferably indicate the TB A-PPDU bandwidth in this configuration as well as in other configurations.

[0259] Alternatively, a reserved value (e.g., a 3 / 0 setting) among the values of the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field can be defined as a 0 MHz channel, and the non-legacy TB PPDU bandwidth in P320 can be indicated (e.g., a 0 MHz channel). In this case, the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field would preferably indicate the non-legacy TB PPDU in all configurations.

[0260] As an addition or alternative, an exceptional indication method rather than a bandwidth indication in P320 may be considered for the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field.

[0261] In the case of such an exceptional indication method, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / existing special user information field (e.g., a 160 MHz channel). The non-legacy TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field may either indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel) or be set to a value of 0.

[0262] Such an exceptional indication method may be preferable when assuming that only the configurations of P160 EHT TB PPDU and S160 non-legacy TB PPDU, P320 EHT TB PPDU and S320 / SS160 non-legacy TB PPDU, and the configuration (i.e., P160 EHT TB PPDU and S320 non-legacy TB PPDU configuration) are defined during the composition of TB A-PPDU including EHT TB PPDU and non-legacy TB PPDU.

[0263] Note that when such an exceptional indication method is applied, the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field needs to be associated with the non-legacy TB PPDU bandwidth indication even in the case of other TB A-PPDU configurations, and the specific meaning may vary depending on the configuration. That is, this method may not be preferable in terms of consistency. As an example, in some TB A-PPDU configurations, the non-legacy TB PPDU bandwidth within P320 may be indicated, and in some other configurations, the overall non-legacy TB PPDU bandwidth may be indicated.

[0264] As yet another example, the TB A-PPDU may include a P160 EHT TB PPDU, an S160 non-legacy TB PPDU, and an S320 non-legacy TB PPDU.

[0265] In this case, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / existing special user information field (e.g., 160 MHz channel). Whether the non-legacy TB PPDU bandwidth within P320 is indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., 160 MHz channel), or the TB A-PPDU bandwidth within P320 may be indicated (e.g., 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., 640 MHz channel).

[0266] As yet another example, the TB A-PPDU may include a P320 EHT TB PPDU and an S320 non-legacy TB PPDU.

[0267] In this case, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / existing special user information field (e.g., 320 MHz channel). Whether the TB A-PPDU bandwidth within P320 is indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., 320 MHz channel), or a reserved value (e.g., 3 / 0 setting) among the values of the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field is defined as the 0 MHz channel, and the non-legacy TB PPDU bandwidth within P320 may be indicated (e.g., 0 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., 640 MHz channel).

[0268] As an addition or alternative, for the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field, an exceptional indication method rather than the bandwidth indication in P320 may be considered.

[0269] In the case of such an exceptional indication method, the EHT TB PPDU bandwidth may be indicated in the UL BW extended subfield within the UL BW subfield / existing special user information field (e.g., 320 MHz channel). The non-legacy TB PPDU bandwidth may be indicated in the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field (e.g., 320 MHz channel). The second UL BW extended subfield within the non-legacy variant special user information field may indicate the TB A-PPDU bandwidth (e.g., 640 MHz channel) or may be set to a value of 0.

[0270] When such an exceptional indication method is applied, the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field needs to be associated with the non-legacy TB PPDU bandwidth indication even in the case of other TB A-PPDU configurations, and the specific meaning may vary depending on the configuration. Therefore, this method may not be preferable in terms of consistency.

[0271] As yet another example, the TB A-PPDU may include the P320 EHT TB PPDU and the SS160 non-legacy TB PPDU.

[0272] In this case, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / Existing Special User Information Field (e.g., 320 MHz channel). Whether the TB A-PPDU bandwidth in P320 is indicated in the first UL BW extension subfield within the UL BW subfield / Non-legacy Variant Special User Information Field (e.g., 320 MHz channel), or a reserved value (e.g., 3 / 0 setting) among the values of the first UL BW extension subfield within the UL BW subfield / Non-legacy Variant Special User Information Field is defined as the 0 MHz channel, and the non-legacy TB PPDU bandwidth in P320 may be indicated (e.g., 0 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., 480 MHz channel or 640 MHz channel).

[0273] As an addition or alternative, an exceptional indication method rather than a bandwidth indication in P320 may be considered for the first UL BW extension subfield within the UL BW subfield / Non-legacy Variant Special User Information Field.

[0274] In the case of such an exceptional indication method, the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / Existing Special User Information Field (e.g., 320 MHz channel). The non-legacy TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / Non-legacy Variant Special User Information Field (e.g., 160 MHz channel or 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field may either indicate the TB A-PPDU bandwidth (e.g., 480 MHz channel or 640 MHz channel) or be set to a 0 value.

[0275] When the exceptional indication method is applied, the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field should be associated with the non-legacy TB PPDU bandwidth indication even in the case of other TB A-PPDU configurations, and the specific meaning may vary depending on the configuration. Therefore, this method may not be preferable in terms of consistency.

[0276] (Example 3-2)

[0277] Next, in relation to a TB A-PPDU composed of an EHT TB PPDU and a non-legacy TB PPDU, the case where there is no existing special user information field (e.g., EHT variant special user information field) and only the non-legacy variant special user information field exists will be described.

[0278] That is, this corresponds to the case where only one UL BW extended subfield (i.e., the first UL BW extended subfield in the non-legacy variant special user information field) exists, and it is necessary to use this to simultaneously indicate the EHT TB PPDU bandwidth and the non-legacy TB PPDU bandwidth.

[0279] For the TB A-PPDU, bandwidth indication may be performed considering various forms as exemplified below, and one or more of the following exemplified forms may be defined. In the following exemplification, SS160 represents a specific 160 MHz channel within the S320 MHz channel.

[0280] For example, the TB A-PPDU may include a P160 EHT TB PPDU and an S160 non-legacy TB PPDU.

[0281] In this case, the EHT TB PPDU bandwidth may be indicated in the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel), and the TB A-PPDU bandwidth within P320 may be indicated (e.g., a 320 MHz channel). At this time, the second UL BW extended subfield within the non-legacy variant special user information field may be set to 0. In this regard, a value of 0 may imply an A-PPDU indication for a 320 MHz channel. This would not be a problem if the configurations of the EHT TB PPDU and non-legacy TB PPDU are indicated in the non-legacy variant common information field and only A-PPDUs in units of 160 MHz and above are defined.

[0282] As another example, the TB A-PPDU may include a P160 EHT TB PPDU, an S160 non-legacy TB PPDU, and an SS160 non-legacy TB PPDU.

[0283] In this case, the EHT TB PPDU bandwidth may be indicated in the first UL BW extended subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel). The second UL BW extended subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel).

[0284] In connection with this, the bandwidth indication method for the TB A-PPDU configuration may be the same as the indication method in the case of the same TB A-PPDU in the third configuration (i.e., the example described below, the TB A-PPDU configuration including P160 EHT TB PPDU and S320 non-legacy TB PPDU, the aforementioned Example 3-1). At this time, when the 480 MHz bandwidth is defined, since the 480 MHz channel has already been determined by channelization, only one of the second configuration (i.e., the TB A-PPDU configuration of this example) or the third configuration should be used, so there should be no problem in terms of indication.

[0285] If there is no definition for the 480 MHz bandwidth and both the second configuration and the third configuration are included in 640 MHz as specific cases, then there may be an implicit indication for the unused 160 MHz channel by the RU / MRU allocation information in the RU allocation subfield, only without an explicit indication for the unused 160 MHz channel. Note that in a broad sense, the second configuration and the third configuration are the same configuration (e.g., the 640 MHz TB A-PPDU indication where P160 EHT TB PPDU and non-legacy TB PPDU are transmitted simultaneously), so problems caused by the same indication do not occur.

[0286] As yet another example, the TB A-PPDU may include a P160 EHT TB PPDU and an S320 non-legacy TB PPDU.

[0287] In this case, the EHT TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel).

[0288] In this regard, the bandwidth indication method for the TB A-PPDU configuration may be the same as the indication method in the second configuration described above (i.e., the TB A-PPDU configuration including the P160 EHT TB PPDU, S160 non-legacy TB PPDU, and SS160 non-legacy TB PPDU, which are the above-described examples). However, for the same reason as described above, no problems will occur.

[0289] As yet another example, the TB A-PPDU may include a P160 EHT TB PPDU, an S160 non-legacy TB PPDU, and an S320 non-legacy TB PPDU.

[0290] In this case, the EHT TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., a 640 MHz channel).

[0291] In this regard, if there is no definition for a 480 MHz bandwidth and both the second and third configurations are included in 640 MHz as specific cases, the bandwidth indication method for the TB A-PPDU configuration may be the same as the indication methods in the second and third configurations described above. However, there is no explicit indication for the specific configuration of the non-legacy TB PPDU, and implicit indication may be possible by the RU / MRU allocation information in the RU allocation subfield. In a broad sense, since the TB A-PPDU configuration, the second configuration, and the third configuration are the same configuration (e.g., a 640 MHz TB A-PPDU indication where a P160 EHT TB PPDU and a non-legacy TB PPDU are transmitted simultaneously), problems caused by the same indication will not occur.

[0292] As yet another example, the TB A-PPDU may include a P320 EHT TB PPDU, an S320 non-legacy TB PPDU.

[0293] In this case, the EHT TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field may indicate the TB A-PPDU bandwidth (e.g., a 640 MHz channel).

[0294] As yet another example, the TB A-PPDU may include a P320 EHT TB PPDU, an SS160 non-legacy TB PPDU.

[0295] In this case, the EHT TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field may indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel).

[0296] Example 4

[0297] This embodiment relates to a scheme for indicating bandwidth considering the case where a TB A-PPDU composed of a HE TB PPDU, an EHT TB PPDU, and a non-legacy TB PPDU is triggered.

[0298] In connection with this, the proposed method in the present disclosure is proposed by being classified into the case where both an existing special user information field (for example, an EHT variant special user information field) and a non-legacy variant special user information field exist simultaneously (hereinafter, Example 4-1), and the case where only the non-legacy variant special user information field exists (hereinafter, Example 4-2).

[0299] (Example 4-1)

[0300] First, regarding a TB A-PPDU composed of a HE TB PPDU, an EHT TB PPDU, and a non-legacy TB PPDU, the case where both an existing special user information field (for example, an EHT variant special user information field) and a non-legacy variant special user information field exist simultaneously will be described.

[0301] That is, this corresponds to the case where two UL BW extension sub-fields (the first UL BW extension sub-field in the non-legacy variant special user information field) exist and can be used to indicate the EHT TB PPDU bandwidth and the non-legacy TB PPDU bandwidth, respectively.

[0302] For the TB A-PPDU, bandwidth indication may be performed in consideration of forms such as the following examples, and only some of them may be defined. In the following examples, SS160 represents a specific 160 MHz channel within a 320 MHz channel.

[0303] For example, the TB A-PPDU may include a P160 HE TB PPDU, an S160 EHT TB PPDU, and an SS160 / S320 non-legacy TB PPDU.

[0304] In this case, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., 160 MHz channel), the EHT TB PPDU bandwidth may be indicated in the UL BW extension subfield within the UL BW subfield / legacy special user information field (e.g., 160 MHz channel), or the A-PPDU bandwidth in P320 may be indicated (e.g., 320 MHz channel). Whether the TB A-PPDU bandwidth in P320 is indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., 320 MHz channel), the reserved value among the values of the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., 3 / 0 setting) is defined as the 0 MHz channel, and the non-legacy TB PPDU bandwidth in P320 may be indicated (e.g., 0 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., 480 MHz channel or 640 MHz channel; always 640 MHz channel for S320 non-legacy TB PPDU).

[0305] (Example 4-2)

[0306] Next, in connection with the TB A-PPDU composed of HE TB PPDU, EHT TB PPDU, and non-legacy TB PPDU, the case where there is no existing special user information field (e.g., EHT variant special user information field) and only the non-legacy variant special user information field exists will be described.

[0307] That is, this corresponds to the case where only one UL BW extension subfield (i.e., the first UL BW extension subfield in the non-legacy variant special user information field) exists and it is necessary to simultaneously use it to indicate both the EHT TB PPDU bandwidth and the non-legacy TB PPDU bandwidth.

[0308] For the TB A-PPDU, bandwidth indication may be performed considering forms such as those exemplified below, and only some of them may be defined. In the following examples, SS160 represents a specific 160 MHz channel within the S320 MHz channel.

[0309] For example, the TB A-PPDU may include a P160 HE TB PPDU, an S160 EHT TB PPDU, and an SS160 / S320 non-legacy TB PPDU.

[0310] In this case, the HE TB PPDU bandwidth may be indicated in the UL BW subfield (e.g., a 160 MHz channel), the EHT TB PPDU bandwidth may be indicated in the first UL BW extension subfield within the UL BW subfield / non-legacy variant special user information field (e.g., a 160 MHz channel), or the A-PPDU bandwidth within P320 may be indicated (e.g., a 320 MHz channel). The second UL BW extension subfield within the non-legacy variant special user information field can indicate the TB A-PPDU bandwidth (e.g., a 480 MHz channel or a 640 MHz channel; in the case of an S320 non-legacy TB PPDU, it is always a 640 MHz channel).

[0311] In the present disclosure, only some of the various TB PPDU / TB A-PPDU configurations described in the foregoing embodiments may be defined.

[0312] As an addition or alternative, the meanings of the UL BW subfield / UL BW extension subfield may be defined consistently for all configurations. That is, the meanings of the UL BW subfield / UL BW extension subfield may be defined in a manner that indicates the bandwidth of the A-PPDU in all configurations, or may be defined in a manner that indicates the bandwidth of a specific version / variant.

[0313] FIG. 16 is a flowchart for explaining the operation of a STA based on a trigger frame according to the present disclosure.

[0314] In stage S1610, the STA can receive a trigger frame including a common information field and a special user information field from an access point (AP).

[0315] For example, the STA may correspond to a non-AP STA.

[0316] For example, the STA can receive a trigger frame associated with a trigger of a non-legacy TB PPDU (e.g., a TB PPDU of the next version of EHT). The trigger frame may include a non-legacy common information field and a non-legacy special user information field.

[0317] Here, the common information field includes a UL bandwidth subfield, and the special user information field may include a first UL bandwidth extension subfield and a second UL bandwidth extension subfield.

[0318] For example, the second UL bandwidth extension subfield can indicate 480MHz / 640MHz bandwidth related information. In connection with this, the remaining values other than the 0 value among the values of the second UL bandwidth extension subfield can each indicate different 480MHz / 640MHz bandwidth types.

[0319] For example, the second UL bandwidth extension subfield may be composed of one or more bits among the bits corresponding to B37, B38, and B39 of the special user information field.

[0320] For example, when the non-legacy TB PPDU included in the one or more TB PPDUs is assigned only to one 160 MHz channel of the secondary 320 MHz channel, the combination of the UL bandwidth subfield and the first UL bandwidth extension subfield (for example, when the UL bandwidth subfield value is set to three values and the first UL bandwidth extension subfield value is set to zero value) can indicate that the bandwidth of the non-legacy TB PPDU within the primary 320 MHz channel is 0 MHz.

[0321] Note that the trigger frame may further include a legacy (e.g., EHT variant) special user information field in addition to the non-legacy special user information field described above. Here, the legacy special user information field may include only one UL bandwidth extension subfield.

[0322] In step S1620, the STA can send a TB PPDU corresponding to one of the one or more TB PPDUs triggered / requested by the trigger frame to the AP.

[0323] In this regard, the bandwidth of the TB PPDU may be indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

[0324] As a specific example, the case where the one or more TB PPDUs correspond to a TB aggregated (A)-PPDU composed of a HE (high efficiency) TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 160 MHz channel may be considered. In this case, the UL bandwidth subfield can indicate the bandwidth of the HE TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield can indicate the bandwidth of the non-legacy TB PPDU. The second UL bandwidth extension subfield may be set to zero value.

[0325] As another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of a HE TB PPDU in a primary 160 MHz channel, a non-legacy TB PPDU in a secondary 160 MHz channel, and a non-legacy TB PPDU in any one 160 MHz channel of a secondary 320 MHz channel. In this case, the UL bandwidth subfield can indicate the bandwidth of the HE TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield can indicate the bandwidth of the non-legacy TB PPDU within the primary 320 MHz channel. The second UL bandwidth extension subfield can indicate the bandwidth of the TB A-PPDU.

[0326] As yet another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of a HE TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 320 MHz channel. In this case, the UL bandwidth subfield can indicate the bandwidth of the HE TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield can indicate that the bandwidth of the non-legacy TB PPDU within the primary 320 MHz channel is 0 MHz. The second UL bandwidth extension subfield can indicate the bandwidth of the TB A-PPDU.

[0327] As yet another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT (extremely high throughput) TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 160 MHz channel. In this case, the combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field can indicate the bandwidth of the EHT TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield can indicate the bandwidth of the non-legacy TB PPDU. The second UL bandwidth extension subfield may be set to a value of 0.

[0328] As yet another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT TB PPDU in a primary 160 MHz channel, a non-legacy TB PPDU in a secondary 160 MHz channel, and a non-legacy TB PPDU in any one 160 MHz channel of a secondary 320 MHz channel. In this case, the combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field can indicate the bandwidth of the EHT TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield can indicate the bandwidth of the non-legacy TB PPDU within a primary 320 MHz channel. The second UL bandwidth extension subfield can indicate the bandwidth of the TB A-PPDU.

[0329] As yet another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 320 MHz channel. In this case, the combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field can indicate the bandwidth of the EHT TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield can indicate that the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel is 0 MHz. The second UL bandwidth extension subfield can indicate the bandwidth of the TB A-PPDU.

[0330] As yet another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT TB PPDU in a primary 320 MHz channel and a non-legacy TB PPDU in any one of the 160 MHz channels in a secondary 320 MHz channel. In this case, the combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field can indicate the bandwidth of the EHT TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates that the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel is 0 MHz and can indicate the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel. The second UL bandwidth extension subfield can indicate the bandwidth of the TB A-PPDU.

[0331] As yet another specific example, it may be considered that the one or more TB PPDUs correspond to a TB A-PPDU composed of any one of a HE TB PPDU in a primary 160 MHz channel, an EHT TB PPDU in a secondary 160 MHz channel, and a non-legacy TB PPDU in any one 160 MHz channel of a secondary 320 MHz channel. In this case, the UL bandwidth subfield may indicate the bandwidth of the HE TB PPDU. The combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field may indicate the bandwidth of the EHT TB PPDU. The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield may indicate that the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel is 0 MHz. The second UL bandwidth extension subfield may indicate the bandwidth of the TB A-PPDU.

[0332] The method performed by the STA described in the example of FIG. 16 may be performed by the first device 100 of FIG. 1. For example, one or more processors 102 of the first device 100 of FIG. 1 may receive, via one or more transceivers 106, a trigger frame including a common information field from the AP 200, and may be configured to transmit to the AP 200 a TB PPDU corresponding to one of the one or more TB PPDUs triggered by the trigger frame. Note that one or more memories 104 of the first device 100 may store instructions for performing the method described in the example of FIG. 16 when executed by one or more processors 102.

[0333] FIG. 17 is a flowchart for explaining the operation of an AP based on a trigger frame according to the present disclosure.

[0334] In step S1710, the AP may transmit to the STA a trigger frame including a common information field and a special user information field.

[0335] Here, the common information field includes a UL bandwidth subfield, and the special user information field may include a first UL bandwidth extension subfield and a second UL bandwidth extension subfield.

[0336] Note that the trigger frame may further include a legacy (e.g., EHT variant) special user information field in addition to the aforementioned non-legacy special user information field. Here, the legacy special user information field may include only one UL bandwidth extension subfield.

[0337] In step S1720, the AP can receive from the STA a TB PPDU corresponding to one of the one or more TB PPDUs triggered / requested by the trigger frame.

[0338] In this regard, the bandwidth of the TB PPDU may be indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

[0339] The specific contents of the common information field, the subfields within the special user information field, and the TB PPDU bandwidth indication based thereon are the same as those described above with reference to FIG. 16, and the overlapping descriptions are omitted.

[0340] The method performed by the AP illustrated in FIG. 17 may be performed by the second device 200 in FIG. 1. For example, one or more processors 202 of the second device 200 in FIG. 1 may be configured to transmit, via one or more transceivers 206, a trigger frame including a common information field to the STA 100 and receive from the STA 100 a TB PPDU corresponding to one of the one or more TB PPDUs triggered by the trigger frame. Note that one or more memories 204 of the second device 200 may store instructions for performing the method illustrated in FIG. 17 when executed by one or more processors 202.

[0341] As described above, compared with the trigger frame that triggers a TB PPDU (e.g., HE TB PPDU, EHT TB PPDU) in an existing wireless LAN system, the trigger frame proposed in the present disclosure has a new feature of performing bandwidth indication for the TB PPDU in consideration of a wider bandwidth (e.g., 480 MHz, 640 MHz) in consideration of a new version (e.g., the next version of EHT, UHR) of the TB PPDU and the merged PPDU (A-PPDU).

[0342] By using the trigger frame proposed in the present disclosure to support triggering / requesting for A-PPDU in addition to the new version of the TB PPDU, aspects of throughput and efficiency in the wireless LAN system can be enhanced.

[0343] The embodiments described above are those in which the components and features of the present disclosure are combined in a predetermined form. Each component or feature should be considered as optional unless otherwise explicitly mentioned. Each component or feature may be implemented in a form that does not combine with other components or features. It is also possible to configure embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of an embodiment may be included in other embodiments, or may be replaced with corresponding components or features of other embodiments. It is obvious that embodiments can be configured by combining claims that do not have an explicit citation relationship in the claims, or can be included as new claims by amendment after filing.

[0344] It will be apparent to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features thereof. Accordingly, the foregoing detailed description should not be construed in any way as limiting, but rather should be considered exemplary. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and any changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0345] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause an apparatus or computer to perform operations according to the methods of various embodiments, and a non-transitory computer-readable medium on which such software or instructions are stored and executable on the apparatus or computer. Instructions available for programming a processing system to perform the features described in the present disclosure may be stored on / within a storage medium or computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product including such a storage medium. The storage medium can include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and can include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory can optionally include one or more storage devices located remotely from the processor. The memory or, alternatively, the non-volatile memory device within the memory includes a non-transitory computer-readable storage medium. The features described in the present disclosure may be stored in any one of the machine-readable media, control the hardware of the processing system, and be integrated into software and / or firmware that enables the processing system to interact with other mechanisms to utilize the results according to the embodiments of the present disclosure. Such software or firmware can include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

Industrial Applicability

[0346] Although the method proposed in the present disclosure has been mainly described with an example applied to an IEEE 802.11-based system, it can also be applied to various wireless LANs or wireless communication systems other than the IEEE 802.11-based system.

Claims

1. A method performed by a station (STA) in a wireless LAN system, the method comprising: receiving, from an access point (AP), a trigger frame including a common information field and a special user information field; transmitting, to the AP, a TB PPDU corresponding to one of one or more trigger-based (TB) physical layer protocol data units (PPDUs) triggered by the trigger frame; wherein the common information field includes an uplink (UL) bandwidth subfield, and the special user information field includes a first UL bandwidth extension subfield and a second UL bandwidth extension subfield; wherein the bandwidth of the TB PPDU is indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

2. The method according to claim 1, wherein the second UL bandwidth extension subfield indicates 480 MHz bandwidth related information.

3. The method according to claim 2, wherein each of the remaining values other than the value of 0 in the values of the second UL bandwidth extension subfield indicates a different 480 MHz bandwidth type.

4. The method according to claim 1, wherein the second UL bandwidth extension subfield is composed of one or more bits among the bits corresponding to B37, B38, and B39 of the special user information field.

5. Based on that the non-legacy TB PPDU included in the one or more TB PPDUs is allocated only to one of the 160 MHz channels of the secondary 320 MHz channel, the combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates that the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel is 0 MHz. The method according to claim 1.

6. Based on the fact that the one or more TB PPDUs correspond to a TB aggregated (A)-PPDU constructed of a HE (high efficiency) TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 160 MHz channel, the UL bandwidth subfield indicates the bandwidth of the HE TB PPDU, a combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates the bandwidth of the non-legacy TB PPDU, the second UL bandwidth extension subfield is set to a value of 0, the method according to claim 1.

7. Based on the fact that the one or more TB PPDUs correspond to a TB A-PPDU composed of a HE TB PPDU in a primary 160 MHz channel, a non-legacy TB PPDU in a secondary 160 MHz channel, and a non-legacy TB PPDU in any one 160 MHz channel of a secondary 320 MHz channel, the UL bandwidth subfield indicates the bandwidth of the HE TB PPDU, a combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates the bandwidth of the non-legacy TB PPDU within a primary 320 MHz channel, the second UL bandwidth extension subfield indicates the bandwidth of the TB A-PPDU, the method according to claim 1.

8. Based on the fact that the one or more TB PPDUs correspond to a TB A-PPDU composed of a HE TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 320 MHz channel, the UL bandwidth subfield indicates the bandwidth of the HE TB PPDU, a combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates that the bandwidth of the non-legacy TB PPDU within a primary 320 MHz channel is 0 MHz, the second UL bandwidth extension subfield indicates the bandwidth of the TB A-PPDU, the method according to claim 1.

9. Based on the fact that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT (extremely high throughput) TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 160 MHz channel, The combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field indicates the bandwidth of the EHT TB PPDU, The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates the bandwidth of the non-legacy TB PPDU, The second UL bandwidth extension subfield is set to a value of 0, the method according to claim 1. **Claim 10** Based on the fact that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT TB PPDU in a primary 160 MHz channel, a non-legacy TB PPDU in a secondary 160 MHz channel, and a non-legacy TB PPDU in any one 160 MHz channel of a secondary 320 MHz channel, The combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field indicates the bandwidth of the EHT TB PPDU, The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates the bandwidth of the non-legacy TB PPDU within the primary 320 MHz channel, The second UL bandwidth extension subfield indicates the bandwidth of the TB A-PPDU, the method according to claim 1. **Claim 11** Based on the fact that the one or more TB PPDUs correspond to a TB A-PPDU composed of an EHT TB PPDU in a primary 160 MHz channel and a non-legacy TB PPDU in a secondary 320 MHz channel, The combination of the UL bandwidth subfield and the UL bandwidth extension subfield in the EHT variant special user information field indicates the bandwidth of the EHT TB PPDU, The combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates that the bandwidth of the non-legacy TB PPDU within the primary 320 MHz channel is 0 MHz, The method according to claim 1, wherein the second UL bandwidth extension subfield indicates the bandwidth of the TB A-PPDU.

12. Based on the one or more TB PPDUs corresponding to a TB A-PPDU composed of either an EHT TB PPDU in a primary 320 MHz channel or a non-legacy TB PPDU in a 160 MHz channel of one of the secondary 320 MHz channels, a combination of the UL bandwidth subfield and a UL bandwidth extension subfield in an EHT variant special user information field indicates the bandwidth of the EHT TB PPDU, a combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates that the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel is 0 MHz and indicates the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel, The method according to claim 1, wherein the second UL bandwidth extension subfield indicates the bandwidth of the TB A-PPDU.

13. Based on the one or more TB PPDUs corresponding to a TB A-PPDU composed of an HE TB PPDU in a primary 160 MHz channel, an EHT TB PPDU in a secondary 160 MHz channel, and a non-legacy TB PPDU in a 160 MHz channel of one of the secondary 320 MHz channels, the UL bandwidth subfield indicates the bandwidth of the HE TB PPDU, a combination of the UL bandwidth subfield and a UL bandwidth extension subfield in an EHT variant special user information field indicates the bandwidth of the EHT TB PPDU, a combination of the UL bandwidth subfield and the first UL bandwidth extension subfield indicates that the bandwidth of the non-legacy TB PPDU in the primary 320 MHz channel is 0 MHz, The method according to claim 1, wherein the second UL bandwidth extension subfield indicates the bandwidth of the TB A-PPDU.

14. A station (STA) device operating in a wireless LAN system, the device comprising: one or more transceivers; one or more processors coupled to the one or more transceivers, wherein the one or more processors Receiving, from an access point (AP), a trigger frame including a common information field and a special user information field, Configuring the AP to transmit a TB PPDU corresponding to one of one or more trigger-based (TB) physical layer protocol data units (PPDUs) triggered by the trigger frame, The common information field includes an uplink (UL) bandwidth subfield, and the special user information field includes a first UL bandwidth extension subfield and a second UL bandwidth extension subfield, An apparatus, wherein a bandwidth of the TB PPDU is indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

15. A processing unit configured to control a station (STA) in a wireless LAN system, the processing unit including: One or more processors; One or more computer memories operably coupled to the one or more processors and storing instructions for performing the method according to any one of claims 1 to 13 based on being executed by the one or more processors.

16. One or more non-transitory computer-readable media storing one or more instructions, The one or more instructions are executed by one or more processors to control a station (STA) device in a wireless LAN system To perform the method according to any one of claims 1 to 13.

17. A method performed by an access point (AP) in a wireless LAN system, the method including: Transmitting, to a station (STA), a trigger frame including a common information field and a special user information field. Receiving, from the STA, a TB PPDU corresponding to one of one or more trigger-based PPDUs (physical layer protocol data units) triggered by the trigger frame; The common information field includes an uplink bandwidth subfield, and the special user information field includes a first UL bandwidth extension subfield and a second UL bandwidth extension subfield; A method in which the bandwidth of the TB PPDU is indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

18. An access point (AP) device operating in a wireless LAN system, the device comprising: One or more transceivers; One or more processors coupled to the one or more transceivers; The one or more processors are: Configured to transmit, to a station (STA), a trigger frame including a common information field and a special user information field; Configured to receive, from the STA, a TB PPDU corresponding to one of one or more trigger-based PPDUs (physical layer protocol data units) triggered by the trigger frame; The common information field includes an uplink bandwidth subfield, and the special user information field includes a first UL bandwidth extension subfield and a second UL bandwidth extension subfield; An apparatus in which the bandwidth of the TB PPDU is indicated based on the UL bandwidth subfield, the first UL bandwidth extension subfield, and the second UL bandwidth extension subfield.

Images