Trigger frame-based PPDU transmission / reception method and device in wireless LAN system

Abstract

A method and apparatus for transmitting and receiving a trigger frame-based PPDU in a wireless LAN system are disclosed. A method performed by a station (STA) in a wireless LAN system according to an embodiment of the present disclosure may include receiving a trigger frame including a common information field from an access point (AP), and transmitting a TB PPDU corresponding to one of one or more trigger based physical layer protocol data units (TB) triggered by the trigger frame to the AP. Here, the common information field may include an aggregated PPDU (A-PPDU) related subfield, and a configuration of the one or more TB PPDUs may be indicated based on the A-PPDU related subfield and at least one other subfield included in the common information field.

Description

[Technical field]

[0001] The present disclosure relates to a method and apparatus for transmitting or receiving a physical layer protocol data unit (PPDU) based on a trigger frame in a wireless local area network (WLAN) system. [Background technology]

[0002] New technologies have been introduced to wireless LANs (WLANs) to improve transmission rates, increase bandwidth, improve reliability, reduce errors, and reduce latency. Among wireless LAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be called Wi-Fi. For example, technologies recently introduced to wireless LANs include enhancements for the 802.11ac standard for Very High-Throughput (VHT) and enhancements for the IEEE 802.11ax standard for High Efficiency (HE).

[0003] To provide a more improved wireless communication environment, improved technologies for EHT (Extremely High Throughput) are being discussed. For example, technologies for increased bandwidth, efficient use of multiple bands, MIMO (Multiple Input Multiple Output) to support increased spatial streams, and multiple access point (AP) coordination are being studied, and in particular, various technologies for supporting traffic with low latency or real-time characteristics are being studied. In addition, new technologies for supporting ultra high reliability (UHR), including improvements or extensions of EHT technology, are being discussed. Summary of the Invention [Problem 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 physical layer protocol data unit (PPDU) 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 transmitting or receiving a merged PPDU for PPDUs of different versions based on a trigger frame.

[0006] The technical problems to be achieved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0007] A method performed by a station (STA) in a wireless LAN system according to an embodiment of the present disclosure may include receiving a trigger frame including a common information field from an access point (AP), and transmitting a TB PPDU corresponding to one of one or more trigger based physical layer protocol data units (TB PPDUs) triggered by the trigger frame to the AP, where the common information field includes an aggregated PPDU (A-PPDU) related subfield, and a configuration of the one or more TB PPDUs may be indicated based on the A-PPDU related subfield and at least one other subfield included in the common information field.

[0008] A method performed by an access point (AP) in a wireless LAN system according to a further aspect of the present disclosure may include transmitting a trigger frame including a common information field to a station (STA), and receiving a TB (trigger based) PPDU (physical layer protocol data unit) corresponding to one of one or more TB (trigger based) PPDUs triggered by the trigger frame from the STA, where the common information field includes an aggregated PPDU (A-PPDU) related subfield, and a configuration of the one or more TB PPDUs may be indicated based on the A-PPDU related subfield and at least one other subfield included in the common information field. Effect 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, a method and apparatus can be provided for transmitting or receiving a merged PPDU for different version PPDUs based on a trigger frame.

[0011] According to the present disclosure, by supporting the transmission and reception of trigger frame-based new version PPDUs and / or merged PPDUs, it is possible to reduce latency and improve throughput and efficiency.

[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 a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief description of the drawings]

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

[0014] [Figure 1] 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. [Diagram 2] FIG. 1 is a diagram illustrating an exemplary structure of a wireless LAN system to which the present disclosure can be applied. [Diagram 3] FIG. 2 is a diagram illustrating a link setup process to which the present disclosure can be applied. [Figure 4] FIG. 13 is a diagram for explaining a backoff process to which the present disclosure can be applied. [Diagram 5] 1 is a diagram for explaining a CSMA / CA base frame transmission operation to which the present disclosure can be applied. [Figure 6] 1 is a diagram for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied. [Figure 7] FIG. 2 illustrates an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure can be applied. [Figure 8] FIG. 2 is a diagram for explaining an example of a resource unit of a wireless LAN system to which the present disclosure can be applied. [Figure 9] FIG. 2 is a diagram for explaining an example of a resource unit of a wireless LAN system to which the present disclosure can be applied. [Figure 10] FIG. 2 is a diagram for explaining an example of a resource unit of a wireless LAN system to which the present disclosure can be applied. [Figure 11] FIG. 2 illustrates an exemplary structure of an HE-SIG-B field. [Figure 12] FIG. 1 is a diagram for explaining a MU-MIMO scheme in which multiple users / STAs are assigned to one RU. [Figure 13]A figure showing an example of a PPDU format to which the present disclosure can be applied. [Figure 14] FIG. 2 illustrates an exemplary format of a trigger frame to which the present disclosure can be applied. [Figure 15] A figure illustrating an A-PPDU structure to which the present disclosure can be applied. [Figure 16] 11 is a flowchart for explaining the operation of a STA based on a trigger frame according to the present disclosure. [Figure 17] 11 is a flowchart for explaining an operation of an AP based on a trigger frame according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, preferred embodiments of 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 intended to describe exemplary embodiments of the present disclosure, and is not intended to show the only embodiment in which the present disclosure can be implemented. The detailed description below includes specific details to provide 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, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or may be shown in the form of a block diagram focusing on the core functions of each structure and device.

[0017] In this disclosure, when a component is "coupled," "coupled," or "connected" to another component, this may include a direct connection as well as an indirect connection where there is another component between them. Also, in this disclosure, the term "comprise" or "have" specifies the presence of a referenced feature, step, operation, element, and / or component, but does not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0018] In this disclosure, the terms "first", "second", etc. are used only to distinguish one component from another component, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0019] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form unless the context dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be included, or any and all possible combinations of two or more of them. Also, in this 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 an IEEE 802.11a / g / n / ac / ax standard-based wireless LAN. 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 be applied to an IEEE 802.11be release-2 standard-based wireless LAN, which corresponds to a further improvement technology 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, the examples of the present disclosure may be applied to a cellular wireless communication system based on the Long Term Evolution (LTE) series technology and the New Radio (NR) series technology of the 3rd Generation Partnership Project (3GPP) standard.

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

[0022] FIG. 1 is a block 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 as 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. In addition, the first device 100 and the second device 200 may be referred to as 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, a gateway, etc.

[0024] The devices 100 and 200 illustrated in FIG. 1 may also be referred to as stations (STAs). For example, the devices 100 and 200 illustrated in FIG. 1 may be referred to as various terms such as a transmitting device, a receiving device, a transmitting STA, and 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 function 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 indicated as an AP STA.

[0025] 1, the first device 100 and the second device 200 may 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 to a medium access control (MAC) layer and a physical layer (PHY) in accordance with the provisions of the IEEE 802.11 standard.

[0026] In addition, the first device 100 and the second device 200 may further support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than the WLAN technology. In addition, the device of the present disclosure may be embodied by various devices such as a mobile phone, a vehicle, a personal computer, an Augmented Reality (AR) device, and a Virtual Reality (VR) device. In addition, the STA of the present specification may support various communication services such as voice calls, image calls, data communications, autonomous driving, machine-type communication (MTC), machine-to-machine (M2M), device-to-device (D2D), and Internet-of-Things (IoT).

[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 may be configured to control the memory 104 and / or the transceiver 106 to embody the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in the present disclosure. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for executing some or all of the processes controlled by the processor 102 or for executing the descriptions, functions, procedures, suggestions, methods and / or operational flow 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., IEEE 802.11 series). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a device may also refer to a communication modem / circuit / chip.

[0028] The second device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including a fourth information / signal via the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for executing some or all of the processes controlled by the processor 202 or for executing the descriptions, functions, procedures, suggestions, methods and / or operational flow 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., IEEE 802.11 series). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a device may also refer to a communication modem / circuit / chip.

[0029] The hardware elements of the devices 100, 200 are described in more detail below. Without being limited thereto, one or more protocol layers may be embodied by one or more processors 102, 202. For example, one or more processors 102, 202 may embody one or more layers (e.g., the same functional layers such as PHY, MAC). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in the present disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods in this disclosure to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in this disclosure.

[0030] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow 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, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be embodied in firmware or software in the form of code, instructions and / or collections of instructions.

[0031] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to 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 coupling.

[0032] The one or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flow diagrams of the present disclosure, to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams of the present disclosure, from one or more other devices. For example, the one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, radio signals / channels, etc., as described, functions, procedures, suggestions, methods, and / or operation flow diagrams disclosed in the present disclosure, via the one or more antennas 108, 208. In the present disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received radio signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, radio signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0033] For example, one of the STAs 100 and 200 can perform operations intended for an AP, and the other of the STAs 100 and 200 can perform operations intended for a non-AP STA. For example, the transceivers 106 and 206 in FIG. 1 can perform operations of transmitting and receiving signals (e.g., packets or PPDUs (Physical layer Protocol Data Units) conforming to IEEE 802.11a / b / g / n / ac / ax / be, etc.). In addition, in the present disclosure, operations of various STAs generating transmission and reception signals and performing data processing and calculations in advance for transmission and reception signals may be performed by the processors 102 and 202 in FIG. 1. For example, examples of operations for generating transmission / reception signals or performing data processing or calculations in advance for transmission / reception signals may include: 1) operations for determining / obtaining / configuring / calculating / decoding / encoding bit information of fields (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in the PPDU; 2) operations for determining / configuring / obtaining time resources and frequency resources (e.g., subcarrier resources) used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU; 3) operations for determining / configuring / obtaining specific sequences (e.g., pilot sequences, STF / LTF sequences, extra sequences applied to SIGs) used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU; 4) power control operations and / or power saving operations applied to STAs; and 5) operations related to determining / obtaining / configuring / calculating / decoding / encoding an ACK signal, etc. In addition, various information (e.g., information regarding fields / subfields / control fields / parameters / power, etc.) used by various STAs in the following example for determining / obtaining / configuring / calculating / decoding / encoding transmitted / received signals may be stored in memory 104, 204 of FIG. 1.

[0034] Hereinafter, downlink (DL) refers to 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, a transmitter may be part of an AP STA, and a receiver may be part of a non-AP STA. Uplink (UL) refers to 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, a transmitter may be part of a non-AP STA, and a receiver may be part of an AP STA.

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

[0036] The structure of a wireless LAN system may be composed of a number of components. A wireless LAN supporting STA mobility that is transparent to higher layers may be provided by the interaction of a number of components. A basic service set (BSS) corresponds to a basic building block of a wireless LAN. FIG. 2 illustrates an example in which there are two BSSs (BSS1 and BSS2) and two STAs are included as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). In FIG. 2, an ellipse representing a BSS may be understood to represent a coverage area in which STAs included in the BSS maintain communication. This area may be referred to as a basic service area (BSA). When a STA moves outside a BSA, it cannot directly communicate with other STAs in the BSA.

[0037] Without considering the DS shown in FIG. 2, the most basic type of BSS in a wireless LAN is an independent BSS (IBSS). For example, an IBSS may have a minimal form consisting of only two STAs. For example, assuming that other components are omitted, a BSS1 consisting of only STA1 and STA2, or a BSS2 consisting of only STA3 and STA4, may correspond to representative examples of an IBSS. Such a configuration is possible when the STAs can communicate directly without an AP. In addition, in such a form of wireless LAN, the IBSS is not configured in advance, but may be configured when the LAN requires it, and this may also be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity that performs a management function. That is, in an IBSS, the STAs are managed in a distributed manner. In an IBSS, all STAs may be mobile STAs, and connection to a distributed system (DS) is not allowed, forming a self-contained network.

[0038] The membership of STAs in a BSS may change dynamically as STAs come on and go, enter and leave the BSS domain, etc. To become a member of a BSS, a STA may join the BSS using a synchronization process. To access all the services of the BSS-based structure, a STA must be associated with the BSS. Such association may be configured 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 the PHY performance. In some cases, such distance limits are sufficient, but in other cases, communication between STAs at greater distances 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 expanded form of a network composed of multiple 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 (WM) and a DSM may be logically distinguished. Each logical medium is used for different purposes and by different components. These media are not limited to being the same or different. In this way, the flexibility of a WLAN structure (DS structure or other network structure) can be explained in that multiple media are logically different from each other. That is, the WLAN structure may be embodied in various ways, and the WLAN structure may be independently specified according to the physical characteristics of each embodiment.

[0041] The DS can support mobile devices by providing seamless integration of multiple BSSs and logical services necessary to address destinations. The DS may also include a portal component that acts as a bridge between the wireless LAN and other networks (e.g., IEEE 802.X).

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

[0043] Data sent from one of the STAs coupled to the AP to the STA address of the AP is always received on an uncontrolled port and may be processed by the IEEE 802.1X port access entity, and the transmitted data (or frame) may be delivered to the DS if the controlled port is authenticated.

[0044] In the above-mentioned DS structure, an Extended Service Set (ESS) may be configured to provide wider coverage.

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

[0046] In a wireless LAN system, no assumptions are made regarding the relative physical locations of the BSSs, and any of the following configurations are possible: The BSSs may overlap, which is a configuration commonly used to provide continuous coverage; The BSSs may not be physically connected, and there is no logical limit to the distance between the BSSs; The BSSs may be physically located in the same location, which may be used to provide redundancy; One (or more) IBSS or ESS network may physically exist in the same space as one (or more) ESS network. This may be the case when an ad-hoc network operates in the location where the ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required in the same location.

[0047] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

[0048] In order for an STA to set up a link to a network and transmit and receive data, it must first discover the network, perform authentication, establish an association, and perform authentication procedures for security. The link setup process can be called a session initiation process or a session setup process. In addition, the discovery, authentication, association, and security setting processes of the link setup process can be collectively called an association process.

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

[0050] There are two types of scanning methods: active scanning and passive scanning. FIG. 3 illustrates a network discovery operation including an active scanning process. In active scanning, a scanning STA transmits a probe request frame to search for APs in the vicinity while changing channels, and waits for a response to the probe request frame. A responder transmits a probe response frame to the STA that transmitted the probe request frame as a response to the probe request frame. Here, the responder may be the STA that transmitted a beacon frame last in the BSS of the channel being scanned. In the BSS, the AP transmits a beacon frame, so the AP becomes the responder, and in the IBSS, the STAs in the IBSS transmit beacon frames alternately, so the responder is not constant. For example, a STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store the BSS-related information contained in the received probe response frame and move to the next channel (e.g., channel 2) and perform scanning in the same manner (i.e., sending and receiving a probe request / response on channel 2).

[0051] Although not shown in FIG. 3, the scanning operation may be performed in a passive scanning manner. In passive scanning, the scanning STA waits for a beacon frame while changing channels. A beacon frame is one of the management frames defined in IEEE 802.11, and is periodically transmitted to inform the existence of a wireless network and to allow the scanning STA to find and join the wireless network. In a BSS, an AP is responsible for periodically transmitting a beacon frame, and in an IBSS, STAs in the IBSS transmit beacon frames in turn. When a scanning STA receives a beacon frame, it stores information about the BSS included in the beacon frame and records beacon frame information on each channel while moving to another channel. A STA that receives a beacon frame stores information about the BSS included in the received beacon frame, moves to the next channel, and can perform scanning on the next channel in the same manner. Comparing active scanning with passive scanning, active scanning has an advantage of having a smaller delay and power consumption than passive scanning.

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

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

[0054] The authentication frame may include information regarding an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), a Finite Cyclic Group, etc. These are only examples of information that may be included in an authentication request / response frame, and other information may be substituted or additional information may be included.

[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, an association process may be performed in step S330. The association process includes the STA sending an association request frame to the AP, and in response, the AP sending an association response frame to the STA.

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

[0058] After the STA is successfully connected to the network, a security setup process may be performed in step S340. The security setup process in step S340 may be referred to as an authentication process using a Robust Security Network Association (RSNA) request / response, the authentication process in step S320 may be referred to as a first authentication process, and the security setup process in step S340 may simply be referred to as an authentication process.

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

[0060] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0061] In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is the Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism is also called the Distributed Coordination Function (DCF) of the IEEE 802.11 MAC, and basically adopts a "listen before talk" access mechanism. According to this type of access mechanism, the AP and / or STA may perform a Clear Channel Assessment (CCA) to sense the wireless channel or medium at a predetermined time interval (e.g., DCF Inter-Frame Space (DIFS)) prior to starting transmission. If the medium is determined to be in an idle status as a result of the sensing, the AP and / or STA may start transmitting a frame through the medium. On the other hand, if the medium is detected to be occupied or busy, the AP and / or STA may not start its own transmission, but may set a delay period (e.g., a random backoff period) for medium access and wait before attempting to transmit a frame. By applying the random backoff period, multiple STAs are expected to wait for different times before attempting to transmit a frame, thereby minimizing collisions.

[0062] The IEEE 802.11 MAC protocol also provides a Hybrid Coordination Function (HCF). The HCF is based on the DCF and the Point Coordination Function (PCF). The PCF is a polling-based synchronous access method that periodically polls so that all receiving APs and / or STAs can receive data frames. The HCF also includes Enhanced Distributed Channel Access (EDCA) and HCF Controlled Channel Access (HCCA). EDCA refers to a contention-based access method for a provider to provide data frames to multiple users, and HCCA refers to a non-contention-based channel access method using a polling mechanism. The HCF also includes a medium access mechanism for improving the Quality of Service (QoS) of a wireless LAN, and can transmit QoS data in both a contention period (CP) and a contention-free period (CFP).

[0063] An operation based on the random backoff period will be described with reference to FIG. 4. When an occupied / busy medium is changed to an idle state, multiple STAs can attempt to transmit data (or frames). As a method for minimizing collisions, each STA can select a random backoff count and attempt transmission after waiting for a slot time corresponding to the random backoff count. The random backoff count has a pseudo-random integer value and may be determined to any one of values ​​in the range of 0 to CW. Here, CW is a 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 (e.g., when an ACK for a transmitted frame cannot be received). When the CW parameter value becomes CWmax, data transmission can be attempted while maintaining the CWmax value until data transmission is successful, and when data transmission is successful, the CW parameter is reset to the CWmin value. The CW, CWmin, and CWmax values ​​are determined to be two times as large as the CWmin value. n It is preferably set to -1 (n=0,1,2,...).

[0064] When the random backoff process begins, the STA continuously monitors the medium while counting down the backoff slots according to the determined backoff count value. If the medium is monitored as occupied, the STA stops the countdown and waits, and resumes the remaining countdown when the medium becomes idle.

[0065] In the example of FIG. 4, when a packet to be transmitted arrives at the MAC of STA3, STA3 confirms that the medium is idle for DIFS and can immediately transmit a frame. The remaining STAs monitor the medium for occupied / busy state and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5. When the medium is monitored as idle, each STA can count down the backoff slots according to the random backoff count value selected by each STA after waiting for DIFS. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. That is, the example shows a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 at the time 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 ends its occupation and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the backoff count that they had stopped. That is, after counting down the remaining backoff slots by the remaining backoff time, STA5 can start frame transmission. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. While STA2 occupies the medium, STA4 may also have data to transmit. From STA4's perspective, when the medium becomes idle, it waits for DIFS and then counts down the random backoff count value it has selected, and can start frame transmission. The example of FIG. 4 shows a case where the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, in which case a collision may occur between STA4 and STA5. When a collision occurs, neither STA4 nor STA5 can receive an ACK, and data transmission will fail. In this case, STA4 and STA5 can select a random backoff count value and count down after doubling the CW value.STA1 waits while the medium is occupied by transmissions from STA4 and STA5, but when the medium becomes idle, it waits for DIFS and can begin frame transmission after the remaining backoff time has elapsed.

[0066] As shown in the example of FIG. 4, a data frame is a frame used for transmitting data to be forwarded to a higher layer, and may be transmitted after a backoff performed after a DIFS has elapsed since the medium became idle. Furthermore, a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS such as a DIFS or a PIFS (Point coordination function IFS). Subtype frames of the management frame include a beacon, an association request / response, a re-association request / response, a probe request / response, and an authentication request / response. A control frame is a frame used to control access to a medium. Subtype frames of control frames include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), BlockAck, BlockACKReq, null data packet announcement, and Trigger. If a control frame is not a response frame of a previous frame, it is transmitted after a backoff that is performed after a DIFS has elapsed, and if a control frame is a response frame of a previous frame, it is transmitted without a backoff after a short IFS (SIFS). The type and subtype of a frame may be identified by a type field and a subtype field in a frame control (FC) field.

[0067] A Quality of Service (QoS) STA can transmit a frame after backing off after the arbitration IFS (AIFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), where the frame can be a data frame, a management frame, or a control frame that is not a response frame.

[0068] FIG. 5 is a diagram for explaining a CSMA / CA base frame transmission operation to which the present disclosure can be applied.

[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 intended to compensate for problems that may occur in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of the STA can use a network allocation vector (NAV). The NAV is a value that indicates to other STAs the time remaining until the medium becomes available to the STA that is currently using or has the authority to use the medium. Therefore, the value set as the NAV corresponds to the period during which the STA that transmits the frame is scheduled to use the medium, 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 attempting to transmit data to STA2, and that STA3 is in a position where it may overhear some or all of the frames transmitted between STA1 and STA2.

[0071] In order to reduce the possibility of collision of transmissions of multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, the carrier sensing of STA3 may determine that the medium is idle. That is, STA1 may correspond to a hidden node to STA3. Or, in the example of FIG. 5, while STA2 is transmitting, the carrier sensing of STA3 may determine that the medium is idle. That is, STA2 may correspond to 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 transmissions from STA1 or STA3, may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0072] Specifically, STA1 can determine whether the channel is occupied or not using carrier sensing. 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. In addition, in terms of virtual carrier sensing, STA1 can determine the channel occupancy state using a network allocation vector (NAV) timer.

[0073] When the channel is idle in DIFS, STA1 can send an RTS frame to STA2 after backing off. When STA2 receives the RTS frame, it can send a CTS frame, which is a response to the RTS frame, to STA1 after SIFS.

[0074] If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can set a NAV timer for a frame transmission period (e.g., SIFS+CTS frame+SIFS+data frame+SIFS+ACK frame) that will be transmitted subsequently using duration information included in the RTS frame. Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can set a NAV timer for a frame transmission period (e.g., SIFS+data frame+SIFS+ACK frame) that will be transmitted subsequently using duration information included in the CTS frame. That is, if STA3 can overhear one or more of the RTS or CTS frames from at least one of STA1 and STA2, it can set the NAV based thereon. 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 will 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 point when reception of the CTS frame is completed. When STA2 successfully receives a data frame, it can transmit an ACK frame, which is a response to the data frame, to STA1 after SIFS. When the NAV timer expires, STA3 can determine whether the channel is in use using carrier sensing. When STA3 determines that the channel is not in use by another terminal during the DIFS period after the expiration of the NAV timer, it can attempt channel access after the contention window (CW) with 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 can be applied.

[0077] The PHY layer can prepare an MPDU (MAC PDU) to be transmitted according to an instruction or primitive (meaning a set of instructions or parameters) from the MAC layer. For example, when a command requesting the PHY layer to start transmission is received from the MAC layer, the PHY layer switches to a transmission mode and transmits information (e.g., data) provided by the MAC layer in the form of a frame. Also, when the PHY layer detects a valid preamble of a received frame, it monitors the preamble header and sends a command to the MAC layer to inform the PHY layer of the start of reception.

[0078] Thus, information transmission / reception in a wireless LAN system is performed in the form of frames, for which a PHY 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-High Throughput (HT)) PPDU frame format may be composed of only Legacy-STF (L-STF), Legacy-LTF (L-LTF), a SIG field, and a Data field. Depending on the type of PPDU frame format (e.g., HT-mixed format PPDU, HT-greenfield format PPDU, Very High Throughput (VHT) PPDU, etc.), additional (or other types) 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. The STF and LTF can be said to be signals for synchronization and channel estimation of the OFDM physical layer.

[0081] The SIG field may include a RATE field and a LENGTH field, etc. The RATE field may include information about the modulation and coding rate of the data. The LENGTH field may include information about the length of the data. Furthermore, 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, if necessary, padding bits. Some bits of the SERVICE field may be used for synchronization of a descrambler at the receiving end. The PSDU corresponds to a MAC PDU defined in the MAC layer and may include data generated / used by a higher layer. The PPDU TAIL bits may be used to return the encoder to a 0 state. The padding bits may be used to adjust the length of the data field to a predetermined unit.

[0083] A MAC PDU is defined by various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a Frame Check Sequence (FCS). A MAC frame is composed of a MAC PDU and may be transmitted / received by a PSDU in the data portion 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 required for frame transmission / reception. The Duration / ID field may be set to the time for transmitting the frame, etc. For specific contents of the Sequence Control, QoS Control, and HT Control subfields of the MAC header, refer to the IEEE 802.11 standard document.

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

[0086] FIG. 7 is a diagram illustrating an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0087] Various forms of PPDU are used in standards such as IEEE 802.11a / g / n / ac / ax. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and Data fields. The basic PPDU format can also be called non-HT PPDU format.

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

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

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

[0091] 8 to 10 are diagrams for explaining examples of resource units in a wireless LAN system to which the present disclosure can be applied.

[0092] With reference to Fig. 8 to Fig. 10, a resource unit (RU) defined in a wireless LAN system will be described. An RU may include a plurality of subcarriers (or tones). An RU may be used when transmitting signals to a plurality of STAs based on an OFDMA technique. An RU may also be defined when transmitting a signal to one STA. An RU may be used for the STF, LTF, data field, etc. of a PPDU.

[0093] 8 to 10, RUs corresponding to different numbers of tones (i.e., subcarriers) may be used to configure some 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 illustrating an exemplary arrangement of resource units (RUs) used on a 20 MHz band.

[0095] As shown at the top of FIG. 8, 26 units (i.e., units corresponding to 26 tones) may be allocated. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Seven DC tones may be inserted into 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. 26 units, 52 units, or 106 units may be allocated to other bands. Each unit may be allocated for a STA or a user.

[0096] The RU arrangement in Figure 8 can be utilized not only for multiple user (MU) situations, but also for single user (SU) situations, in which case one 242 unit can be used as shown at the bottom of Figure 8. In this case, three DC tones may be inserted.

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

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

[0099] Just as various sizes of RUs are used in the example of Figure 8, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. may be used in the example of Figure 9. In addition, five DC tones may be inserted at the center frequency, 12 tones may be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used as a guard band in the rightmost band of the 40 MHz band.

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

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

[0102] As various sizes of RUs are used in the examples of Figures 8 and 9, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. may be used in the example of Figure 10. In addition, in the 80 MHz PPDU, the RU arrangements of the HE PPDU and the EHT PPDU may differ from each other, and the example of Figure 10 shows an example of the RU arrangement for the 80 MHz EHT PPDU. In the example of Figure 10, the HE PPDU and the EHT PPDU are the same in that 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. In the HE PPDU, 7 DC tones are inserted into the DC band, and there is one 26-RU corresponding to 13 tones on each side of the DC band. In the EHT PPDU, 23 DC tones are inserted into the DC band, and there is one 26-RU on the left and right side of the DC band. In the HE PPDU, there is one null subcarrier between the 242-RUs that are not in the center band, but there are five null subcarriers in the EHT PPDU. In the HE PPDU, one 484-RU does not contain a null subcarrier, but in the EHT PPDU, one 484-RU contains five null subcarriers.

[0103] Also, as shown in the figure, when used for a single user, 996-RU may be used, and in this case, five DC tones are inserted, which is common to both the HE PPDU and the EHT PPDU.

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

[0105] Here, the MRU corresponds to a group of subcarriers (or tones) composed of multiple RUs, and the multiple RUs constituting the MRU may be RUs of the same size or may be RUs of different sizes. For example, a single MRU may be defined as 52+26-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2×996+484-tones, 3×996-tones, or 3×996+484-tones. Here, the multiple RUs constituting one MRU may correspond to RUs of small size (e.g., 26, 52, 106) or RUs of large size (e.g., 242, 484, 996, etc.). That is, one MRU including RUs of small size and RUs of large size may not be set / defined. In addition, the multiple RUs constituting one MRU may be contiguous or not contiguous in the frequency domain.

[0106] If an 80 MHz sub-block contains RUs with fewer than 996 tones or if portions of the 80 MHz sub-block are punctured, the 80 MHz sub-block may use an RU placement that excludes 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, a STA (e.g., an AP) that transmits a trigger may use trigger information (e.g., a trigger frame or TRS (triggered response scheduling)) to assign 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. Then, the first STA may transmit a first trigger-based (TB) PPDU based on the first RU, and the second STA may transmit a second TB PPDU based on the second RU. The first and second TB PPDUs may be transmitted to the AP in the same time interval.

[0108] For example, when a DL MU PPDU is configured, a STA (e.g., an AP) transmitting the DL MU PPDU can assign 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., an AP) can transmit the HE-STF, HE-LTF, and Data fields for the first STA using the first RU and can transmit the HE-STF, HE-LTF, and Data fields for the second STA using the second RU in one MU PPDU.

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

[0110] FIG. 11 illustrates an example structure of an HE-SIG-B field.

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

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

[0113] The common field may include N*8 RU allocation subfields, where N is the number of subfields, and may have values ​​of N=1 for 20 or 40 MHz MU PPDU, N=2 for 80 MHz MU PPDU, N=4 for 160 MHz or 80+80 MHz MU PPDU, .... One 8-bit RU allocation subfield may indicate the size (26, 52, 106, etc.) and frequency location (or RU index) of the RUs included in the 20 MHz band.

[0114] For example, if the value of the 8-bit RU allocation subfield is 00000000, nine 26-RUs are arranged in order from the leftmost to the rightmost in the example of Figure 8, if the value is 00000001, seven 26-RUs and one 52-RU are arranged in order from the leftmost to the rightmost, and if the value is 00000010, five 26-RUs, one 52-RU, and two 26-RUs are arranged in order from the leftmost to the rightmost.

[0115] As a further example, consider the 8-bit RU allocation subfield with a value of 01000y. 2 y 1 y 0 8, 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, multiple users / STAs may be assigned to the 106-RU in the MU-MIMO scheme. Specifically, a maximum of eight users / STAs may be assigned to the 106-RU, and the number of users / STAs assigned to the 106-RU is represented by 3-bit information (i.e., y 2 y 1 y 0 For example, the 3-bit information (y 2 y 1 y 0 ) corresponds to a decimal value N, the number of users / STAs assigned to 106-RU may be N+1.

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

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

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

[0119] In the example of FIG. 12, it is assumed that the value of the RU allocation subfield is 01000010. 2 y 1 y 0 In y 2 y 1 y 0 = 010. 010 corresponds to 2 in decimal (i.e., N = 2), and it can be indicated 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 manner. As a result, a total of eight users / STAs are assigned to the 20 MHz band / channel, and the user-specific field of HE-SIG-B may include eight user fields (i.e., four user block fields). The eight user fields may be assigned to RUs as shown in FIG. 12.

[0120] The user fields may be configured based on two formats. The user fields for MU-MIMO allocation may be configured in a first format, and the user fields for non-MU-MIMO allocation may be configured in a second format. With reference to an example in 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., a format for MU-MIMO allocation) may be configured as follows: For example, among the total 21 bits of one user field, B0 to B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11 to B14 include spatial configuration information such as the number of spatial streams for the user, B15 to B18 include modulation and coding scheme (MCS) information applied to the Data field of the PPDU, B19 is defined as a reserved field, and B20 may include coding type (e.g., binary convolutional coding (BCC) or low-density parity check (LDPC)) information applied to the Data field of the PPDU.

[0122] The user field of the second format (i.e., a format for non-MU-MIMO allocation) may be configured as follows: For example, among the total 21 bits of one user field, B0 to B10 may include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11 to B13 may include information on the number of spatial streams (NSTS) applied to the RU, B14 may include information indicating whether beamforming is possible (or whether a beamforming steering matrix is ​​applicable), B15 to B18 may include information on modulation and coding scheme (MCS) applied to the Data field of the PPDU, B19 may include information indicating whether dual carrier modulation (DCM) is applicable, and B20 may include information on a coding type (e.g., BCC or LDPC) 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 represented as a specific index value. For example, the MCS information may be represented as index 0 to index 11. The MCS information may include information about a constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information about a coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). The MCS information may omit information about a channel coding type (e.g., BCC or LDPC).

[0124] FIG. 13 shows an example of a PPDU format to which the present disclosure can be applied.

[0125] The PPDU in Fig. 13 may be variously named, such as EHT PPDU, transmit PPDU, receive PPDU, first type or Nth type PPDU, etc. For example, the PPDU or EHT PPDU of the present disclosure may be variously named, such as transmit PPDU, receive PPDU, first type or Nth type PPDU, etc. Also, the EHT PPU can be used 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 PSDUs) for one or more users. That is, the EHT MU PPDU may be used for both SU transmission and MU transmission. For example, the EHT MU PPDU may correspond to a PPDU for one receiving STA or multiple receiving STAs.

[0127] The EHT-SIG is omitted in the EHT TB PPDU in Fig. 13, unlike the EHT MU PPDU. A STA that receives a trigger for UL MU transmission (e.g., a trigger frame or a TRS) can perform UL transmission based on the EHT TB PPDU format.

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

[0129] The subcarrier frequency spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields (these are referred to as pre-EHT modulated fields) may be determined to be 312.5 kHz. The subcarrier frequency spacing of the EHT-STF, EHT-LTF, Data, and PE fields (these are referred to as EHT modulated fields) may be determined to be 78.125 kHz. That is, the tone / subcarrier indexes 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 indexes of the EHT-STF, EHT-LTF, Data, and PE fields may be displayed in units of 78.125 kHz.

[0130] The L-LTF and L-STF in FIG. 13 may be configured in the same manner as the corresponding fields of the PPDU described in FIG. 6 and FIG.

[0131] The L-SIG field in FIG. 13 may be 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 PPDU. For example, for a non-HT, HT, VHT, or EHT PPDU, the value of the Length field may be determined as a multiple of 3. For example, for a HE PPDU, the value of the Length field may be determined as a multiple of 3+1 or a multiple of 3+2.

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

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

[0134] A U-SIG (Universal SIG) may be inserted after the RL-SIG in Fig. 13. The U-SIG may be variously named, such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, a first (type) control signal, etc.

[0135] The U-SIG may include N-bit information and may include information for identifying the type of EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4us, and the U-SIG may have a total duration of 8us. 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, and the first symbol of the U-SIG (e.g., U-SIG-1) transmits the first X-bit information (e.g., 26 un-coded bits) of the total A-bit information, and the second symbol of the U-SIG (e.g., U-SIG-2) transmits the remaining Y-bit information (e.g., 26 un-coded bits) of 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 convolution encoding (e.g., BCC encoding) based on a rate of R=1 / 2 to generate 52-coded bits and 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 (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) excluding the pilot tones -21, -7, +7, and +21.

[0137] For example, the A-bit information (e.g., 52 un-coded bits) transmitted by the 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 the U-SIG. The CRC field may be generated based on the 26 bits assigned to the first symbol of the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and may be generated based on a conventional CRC calculation algorithm. The tail field may also 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 bits) transmitted by the 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 the U-SIG, or the version-independent bits may be assigned to both the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.

[0139] For example, the version independent bits of the 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 (PHY version) of the transmitted / received PPDU. For example, a first value of the 3-bit physical layer version identifier may indicate that the transmitted / received PPDU is an EHT PPDU. In other words, when the transmitting STA transmits an EHT PPDU, the transmitting STA may set the 3-bit physical layer version identifier to a first value. In other words, the receiving STA may 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 the U-SIG may include a one-bit UL / DL flag field, where a first value of the one-bit UL / DL flag field is associated with UL communications and a second value of the UL / DL flag field is associated with DL communications.

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

[0142] For example, when EHT PPDUs are classified into various types (e.g., EHT PPDUs associated with SU mode, EHT PPDUs associated with MU mode, EHT PPDUs associated with TB mode, EHT PPDUs associated with Extended Range transmission, etc.), information regarding the type of EHT PPDU may be included in the version-dependent bits of the U-SIG.

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

[0144] Preamble puncturing may be applied to the PPDU in FIG. 13. Preamble puncturing may mean transmission of a PPDU in which no signal is present in one or more 20 MHz subchannels in the bandwidth of the PPDU. Preamble puncturing may be applied to a PPDU transmitted to one or more users. For example, the resolution of preamble puncturing may be 20 MHz for EHT MU PPDU in OFDMA transmissions with a bandwidth larger than 40 MHz and non-OFDMA transmissions with 80 MHz and 160 MHz bandwidths. That is, in the above case, puncturing for subchannels smaller than 242 tone RUs may not be allowed. Also, for EHT MU PPDU in non-OFDMA transmissions with a 320 MHz bandwidth, the resolution of preamble puncturing may be 40 MHz. That is, puncturing for subchannels smaller than 484 tone RUs may not be allowed in the 320 MHz bandwidth. Also, preamble 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 the EHT-SIG, for example, a first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and a second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.

[0146] For example, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. When the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured in units of 80 MHz individually. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG may include information about the 160 MHz bandwidth, and the second field of the first U-SIG may include information about the preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern). Also, the first field of the second U-SIG may include information about the 160 MHz bandwidth, and the second field of the second U-SIG may include information about the preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern). The EHT-SIG subsequent 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 subsequent 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] Additionally or alternatively, the U-SIG and the 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 duplicated. That is, four identical U-SIGs may be included in the 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth may contain 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 4us. 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 Figures 11 and 12. For example, the EHT-SIG may include a common field and a user-specific field, the same as the example of Figure 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] 11, the common fields of the EHT-SIG and the user-specific fields of the EHT-SIG may be coded separately. A user block field included in the user-specific fields includes information for two user fields, but the last user block field included in the user-specific fields may include one or two user fields. That is, a user block field of the EHT-SIG may include up to two user fields. Similarly to the example of FIG. 12, each user field may be associated with a MU-MIMO allocation or a non-MU-MIMO allocation.

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

[0153] As in the example of FIG. 11, the common field of the EHT-SIG may include RU allocation information. The RU allocation information may refer to information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are assigned. The RU allocation information may be configured in units of 9 bits (or N bits).

[0154] A mode in which the common field of the EHT-SIG is omitted may be supported. The mode in which the common field of the EHT-SIG is omitted may be called a 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 schemes. As described above, information related to the MCS scheme applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on the DCM scheme. The DCM scheme provides an effect similar to frequency diversity by reusing the same signal on two subcarriers, thereby reducing interference and improving coverage. For example, modulation symbols to which the same modulation scheme is applied may be repeatedly mapped on available tones / subcarriers. For example, among N data tones (e.g., 52 data tones) allocated for the EHT-SIG, the first consecutive half tones (e.g., 1st to 26th tones) may be mapped with modulation symbols to which a specific modulation scheme is applied (e.g., BPSK modulation symbols), and the remaining consecutive half tones (e.g., 27th to 52nd tones) may also be mapped with modulation symbols to which the same specific modulation scheme is applied (e.g., BPSK modulation symbols). That is, the modulation symbol mapped to the 1st tone and the modulation symbol mapped to the 27th tone are the same. 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 of FIG. 13 may be used to improve automatic gain control (AGC) estimation in a MIMO environment or an OFDMA environment. The EHT-LTF of FIG. 13 may be used to estimate a channel in a MIMO environment or an OFDMA environment.

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

[0157] The PPDU in FIG. 13 (ie, the EHT PPDU) may be configured based on the example of the RU arrangement in FIGS.

[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 RU in Fig. 8. That is, the RU locations of the EHT-STF, EHT-LTF, and data fields 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 RU in Fig. 9. That is, the RU locations of the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown in Fig. 9.

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

[0160] The tone plan for 160 / 240 / 320 MHz may be configured to repeat the pattern of FIG. 9 or FIG. 10 multiple times.

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

[0162] The receiving STA may determine the type of the received PPDU as EHT PPDU based on the following: 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) the result of applying modulo 3 arithmetic 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 as EHT PPDU. If the received PPDU is determined as EHT PPDU, the receiving STA may determine the type of EHT PPDU based on bit information included in the symbol after the RL-SIG in FIG. 13. In other words, the receiving STA may determine the received PPDU as EHT PPDU based on 1) the first symbol after the L-LTF signal which is BSPK, 2) an RL-SIG which is consecutive to the L-SIG field and is the same as the L-SIG, and 3) an L-SIG including a Length field in which the result of applying modulo 3 is set to 0.

[0163] For example, the receiving STA may determine that the type of the received PPDU is an HE PPDU based on the following: 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) 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 the type of the received PPDU as non-HT, HT, or VHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, and 2) 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, or 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 determine that the PPDU is an HE PPDU or EHT PPDU. In this case, if the rate (6Mbps) check fails, the received PPDU may be determined as a non-HT, HT, or VHT PPDU. If the rate (6Mbps) check and the parity check are passed, the received PPDU may be determined as an EHT PPDU if the result of applying modulo 3 to the Length value of the L-SIG is detected as 0, and may be determined as an HE PPDU if the result of Length mod 3 is not 0.

[0166] The PPDU in Figure 13 may be used to transmit and receive various types of frames. For example, the PPDU in Figure 13 may be used to transmit and receive one or more (simultaneous) 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 can be applied.

[0168] The trigger frame may allocate resources for one or more TB PPDU transmissions and may request a TB PPDU transmission. The trigger frame may also include other information required by the STAs transmitting the TB PPDUs in response. The trigger frame may include common info and user info list fields in the frame body.

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

[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 as corresponding 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 ​​8 to 15 are defined as reserved.

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

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

[0173] The user information list includes zero or more user info fields. Figure 14 shows an example of an EHT variant user information field format.

[0174] The AID12 subfield basically indicates that it is a user information field for the STA having the AID. In addition, when the AID12 field has a predetermined specific value, it may be used 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 information field is a user information field that does not include user specific information but includes extended common information that is not provided in the common information field. For example, the special user information field may be identified by the AID12 value 2007, and the special user information field flag subfield in the common information field may indicate whether or not the special user information field is included.

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

[0176] Additionally, in the present disclosure, a tone plan may refer to a rule for determining the size and / or location of a resource unit (RU). In the following, a tone plan applied to an HE PPDU (i.e., a PPDU based on the IEEE 802.11ax standard) is described as an example. In particular, the size / location of the RU applied to the HE PPDU and the control information related to the RU applied to the HE PPDU are 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 related to the size and location of the RU, information of a user STA assigned to a specific RU, a frequency bandwidth for a PPDU including the RU, and / or a modulation scheme applied to a specific RU. The control information related to the RU may be included in a SIG field. For example, the control information related to the RU may be included in the HE-SIG-B field. That is, in the process of generating a transmission PPDU, the transmitting STA may include control information for the RU included in the PPDU in the HE-SIG-B field. In addition, the receiving STA may receive the HE-SIG-B included in the received PPDU to obtain the control information included in the HE-SIG-B, determine whether there is an RU assigned to the receiving STA, and decode the assigned RU 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 configured, the STF / LTF / data fields for the first receiving STA may be transmitted and received in the first RU.

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

[0180] Specifically, an RU may include multiple subcarriers. For example, when an RU includes N subcarriers, it may be expressed as an N-tone RU or N RU. The location of a particular RU may be represented 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 may be 312.5 kHz or 78.125 kHz, and the subcarrier frequency spacing for the RU may be 78.125 kHz. That is, a subcarrier index "+1" for an RU may mean a position that is 78.125 kHz higher than the DC tone, and a subcarrier index "-1" for an RU may mean a position that is 78.125 kHz lower than the DC tone. For example, when the location of a particular RU is represented as [-121:-96], the RU is located in the area from subcarrier index -121 to subcarrier index -96, and as a result, the RU may include 26 subcarriers. Additionally, the N-tone RU may include pilot tones that have already been configured.

[0181] Trigger frames for non-legacy PPDUs and / or aggregated PPDUs

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

[0183] In relation to this, the present disclosure proposes a trigger frame for TB PPDU transmission and reception in a next-generation wireless LAN system (eg, Next 11be, UHR, etc.) based on the above-mentioned trigger frame (eg, in relation to FIG. 14).

[0184] In addition, in this disclosure, in order to improve efficiency and throughput, a trigger frame that takes into account TB A-PPDU (agrregulated-PPDU) in which PPDUs of different WLAN versions can be transmitted simultaneously is proposed.

[0185] That is, the trigger frame proposed in the present disclosure may be used to trigger / solocit the transmission of a TB PPDU in a next-generation WLAN system. Additionally or alternatively, the trigger frame proposed in the present disclosure may be used to trigger / solocit the transmission of a TB A-PPDU.

[0186] FIG. 15 illustrates an A-PPDU structure to which the present disclosure can be applied.

[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, a first sub-PPDU may support a 160 MHz bandwidth, a second sub-PPDU may support an 80 MHz bandwidth, and a third sub-PPDU may support an 80 MHz bandwidth.

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

[0190] In this disclosure, an enhanced trigger frame is proposed that improves on the existing trigger frame (eg, see FIG. 14) in order to trigger / request a TB PPDU and various TB A-PPDUs in a next-generation WLAN system.

[0191] The improved trigger frame may correspond to a next version trigger frame that is being considered in next generation wireless LAN systems.

[0192] For clarity of description, the enhanced trigger frame proposed in this 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 an HE version, and a trigger frame that triggers / requests a PPDU of an EHT version (e.g., FIG. 14).

[0193] In the context of this disclosure, "non-legacy" may mean the next version after the existing version / variant.

[0194] As a specific example, "non-legacy" in this disclosure may alternatively apply to a version / variant representation (e.g., UHR) that is later than the EHT version / variant.

[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 information field, the non-legacy variant special user information field, and the non-legacy user information field can respectively mean the variant common information field, the variant special user information field, and the user information field for the next version in the next-generation wireless LAN system (e.g., next 11be, UHR, etc.).

[0197] In the unlikely event that a non-legacy trigger frame triggers the A-PPDU, it may include a (legacy) special user information field, a legacy variant user information field (eg, a HE variant user information field, an EHT variant user information field).

[0198] In the following, this disclosure will explain a trigger frame for when only up to a 320 MHz bandwidth is defined in a wireless LAN system (hereinafter, Example 1), and a trigger frame for when up to a 480 MHz bandwidth / 640 MHz bandwidth is defined in a wireless LAN system (hereinafter, Example 2).

[0199] Example 1

[0200] This embodiment relates to non-legacy trigger frames as defined up to 320 MHz bandwidth / channel width.

[0201] (Non-legacy variant common information field)

[0202] The non-legacy variant common information field may be defined based on the legacy variant common information field (eg, the EHT variant common information field in FIG. 14).

[0203] The non-legacy variant common information field may be used to indicate information of a non-legacy (i.e., next version) TB PPDU. Furthermore, during A-PPDU transmission, i.e., when the A-PPDU transmission is triggered / requested by the non-legacy trigger frame, the non-legacy variant common information field may also indicate information of a legacy TB PPDU (e.g., HE TB PPDU / EHT TB PPDU).

[0204] The subfields of the non-legacy variant common information field may be as follows:

[0205] The Trigger Type subfield may be defined as shown in FIG. 14 and may be set to a value of 0 (ie, Basic Trigger type) for triggers such as TB PPDU.

[0206] In addition, the UL length subfield, the More TF subfield, the CS required subfield, and the UL BW subfield may be defined as shown in FIG.

[0207] In addition, the GI And HE / EHT-LTF Type / Triggered TXOP sharing Mode subfield may include a non-legacy (i.e., next version) LTF Type indication, and the name of the subfield may be changed accordingly. As an example, the subfield may be changed to the GI And HE / EHT / Next version-LTF Type / Triggered TXOP sharing Mode subfield, or another name may be used. The definition of the subfield value may be the same as that of FIG. 14.

[0208] In addition, the Number Of HE / EHT-LTF Symbols subfield may include the number of non-legacy (i.e., next version) LTF symbols, and the name of the subfield may be changed accordingly. As an example, the subfield may be changed to the Number Of HE / EHT / Next version-LTF Symbols subfield, or another name may be used. The definition of the subfield value may be defined as shown in FIG. 14, and may further be specified up to 16.

[0209] In addition, in relation to the definition of the subfield value, B23 to B25 and B22 or B26 may be further used / utilized. In relation to this, when a non-legacy trigger frame triggers an A-PPDU, the subfield may indicate only up to 8, in which case B22 / B26 may be reserved or may be used to indicate a parameter defined in a legacy variant common information field (e.g., an HE variant common information field).

[0210] In addition, the LDPC Extra Segment subfield, the AP Tx Power subfield, the Pre-FEC Padding Factor subfield, the PE Disambiguity subfield, and the UL Spatial Reuse subfield may be defined as in FIG. 14.

[0211] In this regard, the UL Spatial Reuse subfield may be set using the value of the Spatial Reuse 1 / 2 subfield of the non-legacy variant special user information field when triggering a non-legacy (i.e., next version) TB PPDU. The setting method may be the same as the setting method using the value of the Spatial Reuse 1 / 2 subfield of the special user information field when triggering a legacy TB PPDU (e.g., EHT TB PPDU).

[0212] Note that B53 may be a reserved subfield as in FIG.

[0213] In the present disclosure, B54 and B55 in the non-legacy variant common information field can be used to distinguish which TB PPDU the non-legacy trigger frame triggers / requests. In this regard, in the legacy variant common information field (e.g., EHT variant common information field), B54 may correspond to the HE / EHT P160 subfield, and B55 may be a Special User Info Field Flag subfield.

[0214] At least one specific bit included in the non-legacy variant common information field may be defined as an A-PPDU Flag subfield, and the subfield may be used to indicate the A-PPDU. The subfield may be named a non-legacy (i.e., next version) P160 subfield, or may be named by another name.

[0215] Here, the specific at least one bit may correspond to one of bits B56 to B62 in the non-legacy variant common information field. As an example, B56 may be used to indicate A-PPDU related information. In this regard, in the legacy variant common information field (e.g., EHT variant common information field), B56 to B62 may correspond to a reserved subfield (e.g., EHT Reserved subfield).

[0216] For example, the subfield may be set to a value of 0 to indicate that the TB PPDU triggered / requested by the trigger frame corresponds to an A-PPDU, and the subfield may be set to a value of 1 to indicate that the TB PPDU triggered / requested by the trigger frame does not correspond to an A-PPDU.

[0217] In relation to the setting / definition of the A-PPDU-related subfields described above, one of bits B22, B26, and B53 may be used as another example of the reserved bit. However, considering the case of A-PPDU, it may be preferable not to use B22, B26, and B53 since information transmission errors may occur to legacy STAs (e.g., HE STAs).

[0218] B56 to B62 in the non-legacy variant common information field may be changed to a non-legacy (i.e., next version) reserved subfield. Alternatively, some bits of B56 to B62 in the variant common information field may be defined as a specific subfield, and the remaining bits may be changed to a non-legacy (i.e., next version) reserved subfield.

[0219] Note that B63 in the non-legacy variant common information field may be a reserved field.

[0220] Hereinafter, in this embodiment, a method for distinguishing various TB PPDUs will be specifically proposed.

[0221] [Table 1]

[0222] With reference to Table 1, the last row in the table enables a non-AP EHT STA to transmit an HE TB PPDU on the primary 160 MHz in response to a trigger frame containing a special user information field.

[0223] Referring to Table 1, various TB PPDUs may be triggered / requested by the trigger frame defined in FIG.

[0224] For example, the trigger frame may trigger / request an HE TB PPDU, an EHT TB PPDU, and a P160 HE TB PPDU+S160 EHT TB PPDU. Here, P160 HE TB PPDU and S160 EHT TB PPDU respectively represent an HE TB PPDU in the primary 160MHz bandwidth and an EHT TB PPDU in the secondary 160MHz bandwidth. In this regard, the bandwidth actually used by P160 and S160 may be equal to or smaller than 160MHz. In addition, the PPDUs transmitted may be distinguished by B54, B55, and B39 in the user information field.

[0225] The non-legacy trigger frame (i.e., trigger frame in the next version) proposed in the present disclosure may be defined / configured to trigger / request non-legacy (i.e., next version) TB PPDU, P160 HE TB PPDU+S160 non-legacy TB PPDU, and P160 EHT TB PPDU+S160 non-legacy TB PPDU in addition to the HE TB PPDU, EHT TB PPDU, and P160 HE TB PPDU+S160 EHT TB PPDU in the above examples. In this regard, the bandwidth actually used by P160 and S160 may be equal to or smaller than 160 MHz.

[0226] As mentioned above, the B54, B55 and A-PPDU flag subfields may be used to distinguish and trigger / request various TB PPDUs by the non-legacy trigger frame, and the user information field variant and assigned PPDU may be distinguished by B39 of the user information field.

[0227] In this disclosure, when triggering TB PPDU / TB A-PPDU based on a non-legacy trigger frame, a bit setting scheme for each TB PPDU configuration is proposed.

[0228] Below, specific bit setting methods are proposed for i) HE TB PPDU, ii) EHT TB PPDU, iii) P160 HE TB PPDU+S160 EHT TB PPDU, iv) non-legacy TB PPDU, v) P160 HE TB PPDU+S160 non-legacy TB PPDU, and vi) P160 EHT TB PPDU+S160 non-legacy TB PPDU.

[0229] First, to trigger / indicate a HE TB PPDU, B54 may be set to a value of 1, B55 may be set to a value of 1, and the A-PPDU Flags subfield may be set to a value of 1.

[0230] Then, to trigger / indicate an EHT TB PPDU, B54 may be set to a value of 0, B55 may be set to a value of 0, and the A-PPDU flags subfield may be set to a value of 1. Note that a PHY version identifier subfield in a special user information field (e.g., an EHT variant special user information field) may indicate EHT.

[0231] Then, to trigger / indicate a P160 HE TB PPDU+S160 EHT TB PPDU, B54 may be set to a value of 1, B55 may be set to a value of 0, and the A-PPDU Flags subfield may be set to a value of 1 or 0. Note that a PHY Version Identifier subfield in a Special User Information field (e.g., an EHT variant Special User Information field) may indicate EHT.

[0232] In this regard, it may be preferable that the A-PPDU Flags subfield is defined as a value of 1. It should be noted that the variants of the User Information field may be differentiated by B39 of the User Information field, where B39 set to a value of 0 indicates the HE variant and B39 set to a value of 1 indicates the EHT variant.

[0233] In conjunction with the above-mentioned TB PPDU structure, when decoding the trigger frame, (all) non-legacy (i.e., next version) STAs may also interpret it as a legacy trigger frame (e.g., the trigger frame in FIG. 14), in which case this is not problematic since the above-mentioned TB PPDU structure is not associated with the non-legacy TB PPDU.

[0234] Then, to trigger / indicate a non-legacy TB PPDU, B54 may be set to a 0 value, B55 may be set to a 1 value, and the A-PPDU flag subfield may be set to a 1 value.

[0235] This setting is not used in the legacy trigger frame, so when decoding this trigger frame, (all) non-legacy STAs can parse it as a non-legacy trigger frame (i.e., an enhanced trigger frame).

[0236] This scheme may be preferable in terms of power saving for legacy STAs (eg, EHT STAs).

[0237] Additionally, non-legacy variant special user information fields may be present.

[0238] Alternatively, to trigger / indicate a non-legacy TB PPDU, B54 may be set to a value of 0, B55 may be set to a value of 0, and the A-PPDU Flags subfield may be set to a value of 1. Note that the PHY Version Identifier subfield in the Special User Information field (e.g., the non-legacy variant Special User Information field) may indicate non-legacy (i.e., next version).

[0239] This setting is the same as the method of triggering the EHT TB PPDU described above, but may be differentiated by the PHY version identifier subfield of the special user information field.

[0240] Although this method may require additional time for non-legacy STAs to recognize the trigger frame that triggers the non-legacy TB PPDU, it has the advantage of being less complex since it maintains the existing design method. This method may not be preferable from the viewpoint of power saving for legacy STAs (e.g., EHT STAs).

[0241] Additionally, non-legacy variant special user information fields may be present.

[0242] Then, to trigger / indicate a P160 HE TB PPDU+S160 non-legacy TB PPDU, B54 may be set to a 0 value, B55 may be set to a 1 value, and the A-PPDU flag subfield may be set to a 0 value.

[0243] This setting is not used in the legacy trigger frame, so when decoding this trigger frame, (all) non-legacy STAs can parse it as a non-legacy trigger frame (i.e., an enhanced trigger frame).

[0244] In this configuration, EHT STAs may not be assigned HE TB PPDUs, resulting in reduced channel utilization.

[0245] Since the B54, B55 and A-PPDU flag subfields for the HE STA are bits corresponding to the UL HE-SIG-A2 Reserved subfield, the HE STA can ignore the corresponding settings and the HE TB PPDU allocation for the HE STA may be possible.

[0246] The variants of the User Information field may be distinguished by B39 in the User Information field, where B39 set to a 0 value indicates the HE variant and B39 set to a 1 value may indicate the non-legacy variant.

[0247] Additionally, non-legacy variant special user information fields may be present.

[0248] Alternatively, in conjunction with an HE TB PPDU allocation for an EHT STA, B54 may be set to a value of 1, B55 may be set to a value of 1, and the A-PPDU flag subfield may be set to a value of 0 to trigger / indicate a P160 HE TB PPDU+S160 non-legacy TB PPDU.

[0249] In this configuration, the A-PPDU flags subfield is set to a zero value, so that when decoding this trigger frame, (all) non-legacy STAs can parse it as a non-legacy trigger frame (ie, an enhanced trigger frame).

[0250] The A-PPDU flag subfield may be a reserved subfield for EHT STAs, and may be a bit corresponding to the UL HE-SIG-A2 Reserved subfield for HE STAs. Therefore, EHT STAs / HE STAs may ignore this setting, and HE TB PPDU allocation for EHT STAs / HE STAs may be possible.

[0251] The variants of the User Information field may be distinguished by B39 in the User Information field, where B39 set to a 0 value indicates the HE variant and B39 set to a 1 value may indicate the non-legacy variant.

[0252] Note that non-legacy variant special user information fields may be present.

[0253] Alternatively, to trigger / indicate a P160 HE TB PPDU+S160 non-legacy TB PPDU, B54 may be set to a value of 1, B55 may be set to a value of 0, and the A-PPDU Flags subfield may be set to a value of 0 or 1. Note that the PHY Version Identifier subfield in the Special User Information field (e.g., the non-legacy variant Special User Information field) may indicate non-legacy (i.e., next version).

[0254] This setting is the same as the method of triggering the P160 HE TB PPDU+S160 EHT TB PPDU described above, but may be distinguished by the PHY version identifier subfield of the special user information field.

[0255] Although this method may require additional time for non-legacy STAs to recognize the trigger frame that triggers P160 HE TB PPDU+S160 non-legacy TB PPDU, it has the advantage of low complexity because it maintains the existing design method. In this method, EHT STAs can be assigned to HE TB PPDU and transmit, but since there is no EHT variant special user information field, errors may occur depending on the implementation.

[0256] Additionally, non-legacy variant special user information fields may be present.

[0257] Then, to trigger / indicate a P160 EHT TB PPDU+S160 non-legacy TB PPDU, B54 may be set to a zero value, B55 may be set to a zero value, and the A-PPDU flag subfield may be set to a zero value.

[0258] In this configuration, the A-PPDU flags subfield is set to a zero value, so that when decoding this trigger frame, (all) non-legacy STAs can parse it as a non-legacy trigger frame (ie, an enhanced trigger frame).

[0259] EHT STAs can analyze that the trigger frame will trigger EHT TB PPDUs in all channels. In this context, only non-legacy STAs should be assigned to S160, so such analysis is not an issue.

[0260] The variants of the User Information field may be distinguished by B39 in the User Information field, where B39 set to a 0 value indicates the EHT variant and B39 set to a 1 value may indicate the non-legacy variant.

[0261] Additionally, non-legacy variant special user information fields may be present.

[0262] In relation to the bit settings for triggering / indicating each TB PPDU configuration described above, the bit settings in Table 2 below may be a preferred scheme.

[0263] [Table 2]

[0264] In relation to Table 2, B54 set to a value of 1 indicates that an HE TB PPDU is located in the primary 160 MHz, and B54 set to a value of 0 indicates that an EHT TB PPDU or a non-legacy (i.e., next version) TB PPDU is located in the primary 160 MHz. That is, in a next-generation wireless LAN system (e.g., a next-version WiFi system), the meaning of B54 may be modified as described above.

[0265] Note that B55 set to a value of 1 indicates that the EHT variant special user information field is not present, and B55 set to a value of 0 can indicate that the EHT variant special user information field is present. B55 may not be related to the presence or absence of a non-legacy variant special user information field (e.g., a UHR variant special user information field). That is, in the next generation wireless LAN system (e.g., the next version of the WiFi system), the meaning of B55 may have the same meaning as EHT.

[0266] In addition, the A-PPDU flag set to a value of 1 indicates an A-PPDU that is not an A-PPDU or does not include a non-legacy PPDU, and the A-PPDU flag set to a value of 0 indicates an A-PPDU that includes a non-legacy PPDU. That is, in a next-generation wireless LAN system (e.g., a next-version WiFi system), the meaning of the A-PPDU flag subfield may be limited as described above.

[0267] In this regard, even if the non-legacy variant special user information field flag subfield is not present, the presence or absence of a non-legacy variant special user information field (e.g., a UHR variant special user information field) may be implicitly indicated.

[0268] Information for triggering a non-legacy TB PPDU or an A-PPDU containing a non-legacy TB PPDU may be transmitted in the non-legacy variant common information field and the non-legacy variant special user information field, where the presence or absence of the non-legacy variant special user information field may be indicated in the non-legacy variant common information field.

[0269] In this regard, a non-legacy variant special user information field flags subfield may be defined / utilized for this indication.

[0270] For example, the subfield may be one bit (e.g., B57) of B56 to B62 of the non-legacy variant common information field other than the A-PPDU flag subfield. A value of 0 in the subfield may indicate the presence of a non-legacy variant special user information field, and a value of 1 in the subfield may indicate the absence of a non-legacy variant special user information field. As examples of other reserved bits, B22, B26, or B53 may be used, but it may be preferable not to use B22, B26, or B53 because information transmission errors may occur to the HE STA when considering the A-PPDU.

[0271] Alternatively, as previously discussed, the non-legacy variant special user information field flag subfield may not be necessary: ​​non-legacy STAs can distinguish between TB PPDUs triggered by the B54, B55 and A-PPDU flag subfields and can therefore use that information alone to determine the presence or absence of a non-legacy variant special user information field (i.e., an implicit indication).

[0272] (Non-legacy variant special user information fields)

[0273] The non-legacy variant special user information field may be defined based on the legacy special user information field (eg, the special user information field in FIG. 14).

[0274] The non-legacy variant special user information field may be used to indicate information of the non-legacy TB PPDU. In relation to this, the non-legacy variant special user information field may also indicate information of the EHT TB PPDU.

[0275] If a non-legacy variant special user information field is present, it may be located next to the non-legacy common information field. If a legacy special user information field (e.g., an EHT variant special user information field) is present in the trigger frame, the non-legacy common information field may be followed by the legacy special user information field, which may then be followed by the non-legacy variant special user information field.

[0276] The subfields of the non-legacy variant special user information field may be as follows:

[0277] The AID12 subfield may be set to a value such as 2007 (eg, the same as the existing value) or 2008.

[0278] Note that the PHY version identifier subfield can indicate non-legacy (i.e., next version).

[0279] In addition, the UL Bandwidth Extension subfield can indicate up to 320 MHz bandwidth together with the UL BW subfield, and can indicate additional bandwidth using reserved values.

[0280] In addition, the EHT Spatial Reuse 1 / 2 subfield may be renamed to the non-legacy Spatial Reuse 1 / 2 subfield and may be defined the same as the existing one.

[0281] In addition, the U-SIG Disregard and Validate subfield may be set to a value that is applied to the setting of the U-SIG Disregard / Validate field of the non-legacy TB PPDU. (In practice) Only some bits may be used by the Disregard / Validate field defined in the non-legacy TB PPDU, or some or all of the reserved subfields B37 to B39 may be used.

[0282] When triggering / requesting a P160 EHT TB PPDU+S160 non-legacy TB PPDU, both the EHT variant Special User Information field and the non-legacy variant Special User Information field may be present, or only the non-legacy variant Special User Information field may be present if the contents are almost the same.

[0283] In this case, the AID12 subfield must be set to 2007, and EHT STAs can parse the non-legacy variant special user information field based on the existing definition as if it were an EHT variant special user information field, while non-legacy STAs can parse the non-legacy variant special user information field based on the new definition.

[0284] In this regard, the PHY version identifier subfield must be set to EHT, but non-legacy STAs can parse it based on the new definition. However, since non-legacy STAs may be assigned to the EHT TB PPDU portion, double parsing must be possible, which may increase implementation complexity.

[0285] (Non-legacy variant user information field)

[0286] The non-legacy variant user information field may be defined based on the legacy user information field (eg, the EHT variant user information field in FIG. 14).

[0287] The non-legacy variant user information field may be used to indicate the information of the user assigned to the non-legacy TB PPDU transmission.

[0288] The non-legacy variant user information field may be next to the non-legacy variant special user information field. If a legacy user information field (e.g., a HE / EHT variant user information field) is present in the trigger frame, the non-legacy variant special user information field may be next to the legacy user information field (e.g., a HE / EHT variant user information field), followed by the non-legacy variant user information field.

[0289] The subfields of the non-legacy variant user information field may be as follows:

[0290] The AID12 subfield may indicate the AID of a non-legacy STA.

[0291] The RU allocation subfield indicates RU allocation information, and the definition of the existing RU allocation subfield may be used as is, or some of the RU allocation information may be changed / added / removed.

[0292] In addition, the UL FEC coding type subfield may be defined in the same manner as in the existing method.

[0293] In addition, the UL EHT-MCS subfield may be renamed to the UL non-legacy-MCS subfield (or another name may be used), and may be defined the same as the existing scheme, or some MCS may be changed / added / removed.

[0294] In addition, the reserved subfields may be kept the same as in the existing method.

[0295] In addition, the SS allocation subfield may be defined the same as in the existing scheme, or may further indicate up to 16 streams.

[0296] In addition, the RA-RU information subfield and the UL target received power subfield may be defined in the same way as in existing methods.

[0297] In addition, the PS160 subfield may be used together with the RU allocation subfield to indicate RU allocation information. In particular, the subfield may indicate information regarding whether the RU is in P160 or S160. This may indicate variant information of the user information field in the case of A-PPDU.

[0298] Example 2

[0299] This embodiment relates to non-legacy trigger frames when defined up to 480 MHz or 640 MHz bandwidth / channel width.

[0300] In the next generation wireless LAN system (e.g., the next version of the WiFi system), a bandwidth of up to 480 MHz or 640 MHz may be defined. In consideration of this, additional subfields may be defined in the manner described in this embodiment, and the subfields may be used for bandwidth indication and PPDU / user information field variant discrimination.

[0301] (Bandwidth indication method)

[0302] In existing WLAN systems, a method is defined to indicate a bandwidth of up to 320 MHz using the UL BW subfield of the EHT variant common information field and the UL BW extension subfield of the special user information field, and some of the value combinations are reserved.

[0303] A trigger frame in a next-generation wireless LAN system (i.e., the non-legacy trigger frame described above) can also specify a bandwidth of up to 320 MHz using the method described above. Note that the reserved value may be used to specify a wider bandwidth.

[0304] That is, a bandwidth of up to 320 MHz can be indicated using a combination of values ​​as in the existing ones, using the UL BW subfield of the non-legacy variant common information field and the UL BW extension subfield of the non-legacy variant special user information field. A wider bandwidth may be indicated using various combinations of reserved bits, such as:

[0305] Depending on the channelization, there may be only one 480MHz / 640MHz, or there may be various types such as 320-1MHz / 320-2MHz, etc. The proposed scheme in this disclosure is described assuming that a specific channel type is defined.

[0306] The following is an example of a method for indicating the 480 MHz / 640 MHz bandwidth proposed in this disclosure.

[0307] For example, to indicate a 480 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 640 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 2. In this example, other value combinations may follow existing indication methods.

[0308] For example, to indicate a 480 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 2. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 3. In this example, other value combinations may follow existing indication methods.

[0309] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 2. To indicate a 640 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 3. In this example, other value combinations may follow existing indication methods.

[0310] For example, to indicate a 480 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1, and the UL BW extension subfield may be set to a value of 1. To indicate a 640 MHz bandwidth, the UL BW subfield may be set to a value of 1 / 2, and the UL BW extension subfield may be set to a value of 1. In this example, other value combinations may follow existing indication schemes.

[0311] For example, to indicate a 480 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 and the UL BW extension subfield may be set to a value of 1. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a value of 1 / 2 and the UL BW extension subfield may be set to a value of 1. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a value of 1 / 2 and the UL BW extension subfield may be set to a value of 2. In this example, other value combinations may follow existing indication methods.

[0312] For example, to indicate a 480 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1, and the UL BW extension subfield may be set to a value of 1. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a value of 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a value of 1 / 2, and the UL BW extension subfield may be set to a value of 2. To indicate a 640-3 MHz bandwidth, the UL BW subfield may be set to a value of 1 / 2, and the UL BW extension subfield may be set to a value of 3. In this example, other value combinations may follow existing indication methods.

[0313] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a value of 1. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a value of 2. To indicate a 640 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a value of 1. In this example, other value combinations may follow existing indication schemes.

[0314] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 1 value. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 2 value. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 1 value. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 2 value. In this example, other value combinations may follow existing indication methods.

[0315] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 1 value. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 2 value. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 1 value. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 2 value. To indicate a 640-3 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 3 value. In this example, other value combinations may follow existing indication methods.

[0316] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 1 value. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 2 value. To indicate a 480-3 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 3 value. To indicate a 640 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 1 value. In this example, other value combinations may follow existing indication methods.

[0317] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 1 value. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 2 value. To indicate a 480-3 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 3 value. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 1 value. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 2 value. In this example, other value combinations may follow existing indication methods.

[0318] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 1 value. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 2 value. To indicate a 480-3 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 value and the UL BW extension subfield may be set to a 3 value. To indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 1 value. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 2 value. To indicate a 640-3 MHz bandwidth, the UL BW subfield may be set to a 1 / 2 value and the UL BW extension subfield may be set to a 3 value. In this example, other value combinations may follow existing indication methods.

[0319] For example, to indicate a 480 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. In this example, other value combinations may follow existing indication methods.

[0320] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 2. In this example, other value combinations may follow existing indication methods.

[0321] For example, to indicate a 480-1 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 / 2 value, and the UL BW extension subfield may be set to a value of 1. To indicate a 480-2 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 / 2 value, and the UL BW extension subfield may be set to a value of 2. To indicate a 480-3 MHz bandwidth, the UL BW subfield may be set to a 0 / 1 / 2 value, and the UL BW extension subfield may be set to a value of 3. In this example, other value combinations may follow existing indication methods.

[0322] For example, to indicate a 640 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. In this example, other value combinations may follow existing indication methods.

[0323] For example, to indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 2. In this example, other value combinations may follow existing indication methods.

[0324] For example, to indicate a 640-1 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 1. To indicate a 640-2 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 2. To indicate a 640-3 MHz bandwidth, the UL BW subfield may be set to a value of 0 / 1 / 2, and the UL BW extension subfield may be set to a value of 3. In this example, other value combinations may follow existing indication methods.

[0325] In relation to the proposed method described above, when triggering the TB A-PPDU of the EHT TB PPDU and the non-legacy TB PPDU, the existing special user information field (especially the UL BW extension subfield in the field) must be present in addition to the non-legacy special user information field. This is because the bandwidth of the EHT TB PPDU must be indicated in addition to the bandwidth of the non-legacy TB PPDU, and the combination of values ​​in the proposed method described above cannot indicate the bandwidth of the EHT TB PPDU.

[0326] Additionally or alternatively, a method of indicating additional bandwidth using one or more bits (e.g., B37 to B39) corresponding to reserved subfields of the existing special user information field in the non-legacy variant special user information field for indicating bandwidth may be considered. In this case, the UL BW subfield of the non-legacy variant common information field and the UL BW extension subfield of the non-legacy variant special user information field can use the existing indication method.

[0327] When the bandwidth is indicated using the relevant bits (e.g., B37 to B39), the bandwidth can be indicated independently. Alternatively, in this case, the additional bandwidth may be indicated using a combination of the values ​​of the UL BW subfield, UL BW extension subfield, and the relevant bit value, as in the existing method.

[0328] As described above, when using the additional bit, only the non-legacy special user information field may be present when triggering the EHT TB PPDU and the TB A-PPDU of the non-legacy TB PPDU. In this case, the EHT STA can interpret the non-legacy special user information field as an existing special user information field and parse it as before. Meanwhile, the non-legacy STA can parse the non-legacy special user information field according to the newly defined method.

[0329] Therefore, in this method, the bandwidth of the EHT TB PPDU and the non-legacy TB PPDU can be indicated at the same time. In this case, the PHY version identifier subfield must be set to EHT, but the non-legacy STA can be analyzed based on the new definition. However, since the non-legacy STA may be assigned to the EHT TB PPDU portion, double analysis must be possible, which may increase the implementation complexity.

[0330] (Various TB PPDU distinction methods)

[0331] For distinguishing TB PPDU in 480MHz / 640MHz bandwidth, the method for triggering / indicating TB PPDU configuration in the above-mentioned first embodiment (eg, bit setting method) may be used.

[0332] It should be noted that various bit combinations described below may be considered to indicate a particular channel in various situations considering a wider bandwidth (ie, 480 MHz / 640 MHz bandwidth).

[0333] In this regard, it may be assumed that the RU allocation subfield of the non-legacy variant user information field can indicate RU allocation information within 160 MHz units. In this case, the subfield may indicate some large RUs / MRUs corresponding to channels exceeding 160 MHz as an exception. Therefore, in relation to indicating a specific channel, a scheme of indicating at least a 160 MHz channel may be considered.

[0334] Specific bit setting methods are proposed below for i) non-legacy TB PPDU, ii) P160 HE TB PPDU+(S160 non-legacy TB PPDU)+S320 / SS160 non-legacy TB PPDU, iii) P320 EHT TB PPDU+S320 / SS160 non-legacy TB PPDU, iv) P160 EHT TB PPDU+(S160 non-legacy TB PPDU)+S320 / SS160 non-legacy TB PPDU, and v) P160 HE TB PPDU+S160 EHT TB PPDU+S320 / SS160 non-legacy TB PPDU.

[0335] First, to trigger / indicate a non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a 0 value, B55 may be set to a 1 value, and the A-PPDU Flag subfield may be set to a value of 1. Alternatively, to trigger / indicate a non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a 0 value, B55 may be set to a 0 value, the A-PPDU Flag subfield may be set to a 1 value, and the PHY version identifier subfield in the special user information field (e.g., the non-legacy special user information field) may be set to indicate non-legacy.

[0336] In this regard, the non-legacy TB PPDU bandwidth may be indicated using the UL BW subfield in the non-legacy variant common information field and the UL BW extension subfield and the additional BW subfield (if present) in the non-legacy variant special user information field, i.e., the above-mentioned bandwidth indication method may be used.

[0337] A combination of B39 and B25 in the non-legacy variant user information fields may be used to indicate up to 640 MHz.

[0338] In the following examples, 160 and 320 can respectively mean 160 MHz band / channel and 320 MHz band / channel. Note that low 160 / 320 and high 160 / 320 can respectively mean 160 / 320 existing in a relatively low band in the frequency domain and 160 / 320 existing in a relatively high band in the frequency domain.

[0339] For example, a value of 0 for B25 can indicate P320 (or low 320) and a value of 1 for B25 can indicate S320 (or high 320).

[0340] The combination of a zero value in B25 and a zero value in B39 can indicate P 160. Alternatively, the combination of a zero value in B25 and a zero value in B39 can indicate a low 160 in P320, or a low 160 in low 320, which may not be desirable given unification with other cases.

[0341] The combination of a 0 value for B25 and a 1 value for B39 can indicate S 160. Alternatively, the combination of a 0 value for B25 and a 1 value for B39 can indicate a high 160 in P320, or a high 160 in low 320, which may not be desirable given integration with other cases.

[0342] The combination of a 1 value in B25 and a 0 value in B39 can indicate a 160 in S320, corresponding to the position of P160. Alternatively, the combination of a 1 value in B25 and a 0 value in B39 can indicate a low 160 in S320, or a low 160 in high 320, the latter of which may be less desirable given integration with other cases.

[0343] The combination of a 1 value for B25 and a 1 value for B39 can indicate a 160 in S320, corresponding to the position of S160. Alternatively, the combination of a 1 value for B25 and a 1 value for B39 can indicate a high 160 in S320, or a high 160 in high 320, the latter of which may be less desirable given integration with other cases.

[0344] In addition, when only 480 MHz of P320+SS160 is considered, the following combination of B25 and B39 in the non-legacy variant user information field may be used: Here, SS160 can mean the remaining 160 MHz channel excluding P320 when transmitting at 480 MHz.

[0345] For example, a combination of a 0 value for B25 and a 0 value for B39 can indicate P160. A combination of a 0 value for B25 and a 1 value for B39 can indicate S160. A combination of a 1 value for B25 and a 1 value (or a 0 value) for B39 can indicate SS160. Alternatively, the combination of a 1 value for B25 and a 0 value for B39 can be reserved.

[0346] Alternatively, the following combinations may be used for integration with cases where HE PPDUs are included: As an example, a 0 / 1 value of B25 and a 0 value of B39 can indicate P160. A 0 value of B25 and a 1 value of B39 can indicate S160. A 1 value of B25 and a 1 value of B39 can indicate SS160.

[0347] Note that when only 480 MHz of P160+S320 is considered, the following combination of B25 and B39 of the non-legacy variant user information field may be used:

[0348] For example, a combination of a 0 value for B25 and a 0 value (or a 1 value) for B39 can indicate P160. Alternatively, the combination of a 0 value for B25 and a 1 value for B39 can be reserved. A combination of a 1 value for B25 and a 0 value for B39 can indicate 160 (or a low 160 in S320), which corresponds to the position of P160 in S320. A combination of a 1 value for B25 and a 1 value for B39 can indicate 160 (or a high 160 in S320), which corresponds to the position of S160 in S320.

[0349] Alternatively, the following combinations may be used for integration with cases where a HE TB PPDU is included: As an example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160. A 0 value of B25 and a 1 value of B39 may indicate 160 corresponding to the position of P160 in S320 (or a low 160 in S320). A combination of a 1 value of B25 and a 1 value of B39 may indicate 160 corresponding to the position of S160 in S320 (or a high 160 in S320).

[0350] Then, to trigger / indicate a P160 HE TB PPDU+(S160 non-legacy TB PPDU)+S320 / SS160 non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a 0 value, B55 may be set to a 1 value, and the A-PPDU Flag subfield may be set to a 0 value. Alternatively, to trigger / indicate a P160 HE TB PPDU+(S160 non-legacy TB PPDU)+S320 / SS160 non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a 1 value, B55 may be set to a 0 value, the A-PPDU Flag subfield may be set to a 0 / 1 value, and the PHY version identifier subfield in the special user information field (e.g., non-legacy special user information field) may be set to indicate non-legacy.

[0351] In this regard, the UL BW subfield in the non-legacy variant common information field may indicate 160 MHz.

[0352] The UL BW subfield in the non-legacy variant common information field and the UL BW extension and additional BW subfields (if present) in the non-legacy variant special user information field may be used to indicate the A-PPDU bandwidth and the non-legacy TB PPDU bandwidth, where it is also possible to only indicate one of both.

[0353] Additionally or alternatively, TB A-PPDU at 640 MHz may not be possible. B25 in the HE variant user information field uses 0 / 1 value in the DCM field, and B39 uses 0. That is, channel indication using the combination of B25 value 1 and B39 value 0 is not possible.

[0354] In addition, when only 480 MHz of P320+S160 is considered, the channel, PPDU and user information field variants are differentiated using B39 in the user information field, and when B39 is set to a value of 1, the channel may be differentiated using B25.

[0355] For example, a value of 0 for B39 can indicate P160, an HE variant user information field (B25 is 0 or 1). A value of 1 for B39 can indicate S160 or SS160, an non-legacy variant user information field. A combination of a value of 0 for B25 and a value of 1 for B39 can indicate S160, and a combination of a value of 1 for B25 and a value of 1 for B39 can indicate SS160.

[0356] In addition, when only 480 MHz of P160+S320 is considered, the channel, PPDU and user information field variants are differentiated using B39 in the user information field, and when B39 is set to a value of 1, the channel may be differentiated using B25.

[0357] For example, a 0 value for B39 can indicate P160, indicating an HE variant user information field (B25 is 0 or 1 value). A 1 value for B39 can indicate S320 or SS160, indicating a non-legacy variant user information field. A 0 value for B25 in combination with a 1 value for B39 can indicate 160, which corresponds to the position of P160 in S320 (or a low 160 in S320). A 1 value for B25 in combination with a 1 value for B39 can indicate 160, which corresponds to the position of S160 in S320 (or a high 160 in S320).

[0358] Next, to trigger / indicate a P320 EHT TB PPDU+S320 / SS160 non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a zero value, B55 may be set to a zero value, and the A-PPDU flags subfield may be set to a zero value.

[0359] In connection with this, a 320 MHz indication may be made in the UL BW subfield in the non-legacy variant common information field and the UL BW extension subfield in the special user information field (or the non-legacy variant special user information field).

[0360] The UL BW subfield in the non-legacy variant common information field and the UL BW extension and additional BW subfields (if present) in the non-legacy variant special user information field may be used to indicate the A-PPDU bandwidth and the non-legacy TB PPDU bandwidth, where it is also possible to only indicate one of both.

[0361] Since B25 in the EHT variant user information field is a reserved bit, it may be possible to indicate channel location up to 640 MHz using B25 and B39 in the user information field.

[0362] When up to 640 MHz is considered, the channel, PPDU and user information field variants may be differentiated using a combination of B25 and B39 in the user information field, where EHT STAs use only B39 for decision and non-legacy STAs should only be assigned to S320, so this is not a problem.

[0363] For example, a combination of a 0 value for B25 and a 0 value for B39 can indicate P160, indicating an EHT variant user information field. A combination of a 0 value for B25 and a 1 value for B39 can indicate S160, indicating an EHT variant user information field. A combination of a 1 value for B25 and a 0 value for B39 can indicate 160, which corresponds to the position of P160 in S320 (or a low 160 in S320), indicating a non-legacy variant user information field. A combination of a 1 value for B25 and a 1 value for B39 can indicate 160, which corresponds to the position of S160 in S320 (or a high 160 in S320), indicating a non-legacy variant user information field.

[0364] When only P320+SS160 up to 480 MHz is considered, the channel, PPDU and user information field variants may be differentiated using a combination of B25 and B39 in the user information field. Here, EHT STAs use only B39 for decision, and non-legacy STAs should only be assigned to SS160, so this is not a problem.

[0365] For example, a combination of a 0 value for B25 and a 0 value for B39 may indicate P160, indicating an EHT variant user information field. A combination of a 0 value for B25 and a 1 value for B39 may indicate S160, indicating an EHT variant user information field. A combination of a 1 value for B25 and a 1 value (or a 0 value) for B39 may indicate SS160, indicating a non-legacy variant user information field. Alternatively, the combination of a 1 value for B25 and a 0 value for B39 may be reserved.

[0366] Alternatively, the following combinations may be used for integration with cases where a HE TB PPDU is included: As an example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160 and indicate the EHT variant user information field; a 0 value of B25 and a 1 value of B39 may indicate S160 and indicate the EHT variant user information field; a 1 value of B25 and a 1 value of B39 may indicate SS160 and indicate the non-legacy variant user information field.

[0367] In addition, 480MHz of P160+S320 may be taken into consideration when only P160 below is EHT TB PPDU.

[0368] Next, to trigger / indicate a P160 EHT TB PPDU+(S160 non-legacy TB PPDU)+S320 / SS160 non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a zero value, B55 may be set to a zero value, and the A-PPDU flag subfield may be set to a zero value.

[0369] In relation to this, a 160 MHz indication may be made in the UL BW subfield in the non-legacy variant common information field and the UL BW extension subfield in the special user information field (or the non-legacy variant special user information field).

[0370] The UL BW subfield in the non-legacy variant common information field and the UL BW extension and additional BW subfields (if present) in the non-legacy variant special user information field may be used to indicate the A-PPDU bandwidth and the non-legacy TB PPDU bandwidth, where it is also possible to only indicate one of both.

[0371] Since B25 in the EHT variant user information field is a reserved bit, it may be possible to indicate channel location up to 640 MHz using B25 and B39 in the user information field.

[0372] When up to 640 MHz is considered, the channel, PPDU and user information field variant may be distinguished using a combination of B25 and B39 in the user information field. Here, since EHT STAs use only B39 for decision and non-legacy STAs should be assigned only to S160 and S320, this does not pose a problem.

[0373] For example, a combination of a 0 value for B25 and a 0 value for B39 can indicate P160, indicating an EHT variant user information field. A combination of a 0 value for B25 and a 1 value for B39 can indicate S160, indicating a non-legacy variant user information field. A combination of a 1 value for B25 and a 0 value for B39 can indicate 160, which corresponds to the position of P160 in S320 (or a low 160 in S320), indicating a non-legacy variant user information field. A combination of a 1 value for B25 and a 1 value for B39 can indicate 160, which corresponds to the position of S160 in S320 (or a high 160 in S320), indicating a non-legacy variant user information field.

[0374] When only up to 480 MHz of P320+SS160 is considered, the channel, PPDU and user information field variants may be distinguished using a combination of B25 and B39 in the user information field. Here, since EHT STAs use only B39 for judgment and non-legacy STAs should be assigned only to S160 and SS160, this does not pose a problem.

[0375] For example, a combination of a 0 value for B25 and a 0 value for B39 may indicate P160, indicating an EHT variant user information field. A combination of a 0 value for B25 and a 1 value for B39 may indicate S160, indicating a non-legacy variant user information field. A combination of a 1 value for B25 and a 1 value (or a 0 value) for B39 may indicate SS160, indicating a non-legacy variant user information field. Alternatively, the combination of a 1 value for B25 and a 0 value for B39 may be reserved.

[0376] Alternatively, the following combinations may be used for integration with cases where an HE TB PPDU is included: As an example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160 and indicate an EHT variant user information field; a 0 value of B25 and a 1 value of B39 may indicate S160 and indicate a non-legacy variant user information field; a combination of a 1 value of B25 and a 1 value of B39 may indicate SS160 and indicate a non-legacy variant user information field.

[0377] When only up to 480 MHz of P160+S320 is considered, the channel, PPDU and user information field variants may be differentiated using a combination of B25 and B39 in the user information field. Here, EHT STAs use only B39 for decision, and non-legacy STAs should only be assigned to S320, so this is not a problem.

[0378] For example, a combination of a 0 value for B25 and a 0 value for B39 may indicate P160 and indicate an EHT variant user information field. A combination of a 0 value for B25 and a 1 value for B39 may be reserved and indicate a non-legacy variant user information field. A combination of a 1 value for B25 and a 0 value for B39 may indicate 160 corresponding to the position of P160 in S320 (or a low 160 in S320) and indicate a non-legacy variant user information field. A combination of a 1 value for B25 and a 1 value for B39 may indicate 160 corresponding to the position of S160 in S320 (or a high 160 in S320) and indicate a non-legacy variant user information field.

[0379] Alternatively, the following combinations may be used for integration with cases where an HE TB PPDU is included: As an example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160 and indicate an EHT variant user information field. A 0 value of B25 and a 1 value of B39 may indicate 160 corresponding to the position of P160 in S320 (or a low 160 in S320) and indicate a non-legacy variant user information field. A combination of a 1 value of B25 and a 1 value of B39 may indicate 160 corresponding to the position of S160 in S320 (or a high 160 in S320) and indicate a non-legacy variant user information field.

[0380] Next, to trigger / indicate a P160 HE TB PPDU+S160 EHT TB PPDU+S320 / SS160 non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a 1 value, B55 may be set to a 0 value, and the A-PPDU flags subfield may be set to a 0 value.

[0381] In this regard, the UL BW subfield in the non-legacy variant common information field may indicate 160 MHz.

[0382] A 320 MHz indication or an EHT TB PPDU bandwidth (160 MHz) indication may be made in the UL BW subfield in the non-legacy variant common information field and the UL BW extension subfield in the special user information field (or the non-legacy variant special user information field).

[0383] The UL BW subfield in the non-legacy variant common information field and the UL BW extension and additional BW subfields (if present) in the non-legacy variant special user information field may be used to indicate the A-PPDU bandwidth and the non-legacy TB PPDU bandwidth, where it is also possible to only indicate one of both.

[0384] Additionally or alternatively, TB A-PPDU at 640 MHz may not be possible. B25 in the HE variant user information field uses 0 / 1 value in the DCM field, and B39 uses 0. That is, channel indication using the combination of B25 value 1 and B39 value 0 is not possible.

[0385] When only 480 MHz of P320+SS160 is considered, the channel, PPDU and user information field variants may be differentiated using a combination of B25 and B39 in the user information field. Here, EHT STAs use only B39 for decision, and non-legacy STAs should be assigned only to SS160, so this is not a problem.

[0386] For example, a 0 / 1 value of B25 in combination with a 0 value of B39 can indicate P160, which indicates the HE variant user information field. A 0 value of B25 in combination with a 1 value of B39 can indicate S160, which indicates the EHT variant user information field. A 1 value of B25 in combination with a 1 value of B39 can indicate SS160, which indicates the non-legacy variant user information field.

[0387] Note that 480MHz of P160+S320 does not need to be considered. This case may be the same as the case of P160 HE TB PPDU+S320 non-legacy TB PPDU.

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

[0389] In step S1610, the STA may receive a trigger frame including a common information field from an access point (AP).

[0390] For example, the STA may be a non-AP STA.

[0391] For example, the STA may receive a trigger frame associated with triggering a non-legacy TB PPDU (eg, a TB PPDU of an EHT next version), which may include a non-legacy common information field.

[0392] Here, the common information field may include an aggregated PPDU (A-PPDU) related subfield.

[0393] For example, a value of 0 in the A-PPDU-related subfield may indicate an A-PPDU that includes a non-legacy TB PPDU, and a value of 1 in the A-PPDU-related subfield may indicate at least one of a non-A-PPDU or an A-PPDU that does not include a non-legacy TB PPDU (i.e., an A-PPDU composed only of a legacy TB PPDU).

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

[0395] In this regard, the configuration of one or more TB PPDUs may be indicated based on the A-PPDU-related subfields and at least one other subfield included in the common information field.

[0396] Here, the at least one other subfield may include bits B45 and B55 in the common information field.

[0397] For example, a value of 1 for B54 may indicate that the primary 160 MHz channel is allocated to a high efficiency (HE) TB PPDU, and a value of 0 for B54 may indicate that the primary 160 MHz channel is allocated to an extremely high throughput (EHT) TB PPDU or a non-legacy TB PPDU.

[0398] For example, the 0 and 1 values ​​of B55 may relate to the presence or absence (eg, flag information) of a legacy (eg, EHT) / non-legacy variant special user information field.

[0399] For example, the one or more TB PPDUs may correspond to high efficiency (HE) TB PPDUs when the B54 is set to a value of 1, the B55 is set to a value of 1, and the A-PPDU related subfields are set to a value of 1. That is, in this case, the trigger frame in step S1610 may be a trigger frame that triggers / requests an HE TB PPDU.

[0400] For example, the one or more TB PPDUs may correspond to an extremely high throughput (EHT) TB PPDU when the B54 is set to a value of 0, the B55 is set to a value of 0, and the A-PPDU related subfield is set to a value of 1. That is, in this case, the trigger frame in step S1610 may be a trigger frame that triggers / requests an EHT TB PPDU.

[0401] For example, the one or more TB PPDUs may correspond to an HE TB PPDU and an EHT TB PPDU when the B54 is set to a value of 1, the B55 is set to a value of 0, and the A-PPDU related subfield is set to a value of 1. That is, in this case, the trigger frame in step S1610 may be a trigger frame that triggers / requests an HE TB PPDU and an EHT TB PPDU (e.g., an A-PPDU consisting of a P160 HE TB PPDU+S160 EHT TB PPDU).

[0402] For example, the one or more TB PPDUs may correspond to non-legacy TB PPDUs when the B54 is set to a value of 0, the B55 is set to a value of 1, and the A-PPDU related subfields are set to a value of 1. That is, in this case, the trigger frame in step S1610 may be a trigger frame that triggers / requests a non-legacy TB PPDU (e.g., a TB PPDU of the next version of EHT).

[0403] For example, if the B54 is set to a value of 1, the B55 is set to a value of 1, and the A-PPDU related subfield is set to a value of 0, the one or more TB PPDUs may correspond to an HE TB PPDU and a non-legacy TB PPDU. That is, in this case, the trigger frame in step S1610 may be a trigger frame that triggers / requests an HE TB PPDU and a non-legacy TB PPDU (e.g., an A-PPDU composed of a P160 HE TB PPDU+S160 non-legacy TB PPDU).

[0404] For example, if the B54 is set to a value of 0, the B55 is set to a value of 0, and the A-PPDU related subfields are set to a value of 0, the one or more TB PPDUs may correspond to an EHT TB PPDU and a non-legacy TB PPDU. That is, in this case, the trigger frame in step S1610 may be a trigger frame that triggers / requests an EHT TB PPDU and a non-legacy TB PPDU (e.g., an A-PPDU composed of a P160 EHT TB PPDU+S160 non-legacy TB PPDU).

[0405] Additionally or alternatively, the presence or absence of a non-legacy variant special user information field in the trigger frame in step S1610 may be (implicitly) indicated based on the A-PPDU related subfields and at least one other subfield included in the common information field.

[0406] Additionally or alternatively, the trigger frame in step S1610 may include at least one of a special user information field associated with information about the non-legacy TB PPDU (e.g., a non-legacy variant special user information field) or a user information field associated with information for a STA assigned to transmit the non-legacy TB PPDU (e.g., a non-legacy variant user information field), where the channel indication for the non-legacy TB PPDU may be based on a combination of the values ​​of B25 and B39 in the user information field.

[0407] 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 be configured to receive a trigger frame including a common information field from the AP 200 via one or more transceivers 106, and transmit a TB PPDU corresponding to one of one or more TB PPDUs triggered by the trigger frame to the AP 200. Furthermore, 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 the one or more processors 102.

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

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

[0410] Here, the common information field may include an aggregated PPDU (A-PPDU) related subfield.

[0411] For example, a value of 0 in the A-PPDU-related subfield may indicate an A-PPDU that includes a non-legacy TB PPDU, and a value of 1 in the A-PPDU-related subfield may indicate at least one of a non-A-PPDU or an A-PPDU that does not include a non-legacy TB PPDU (i.e., an A-PPDU composed only of a legacy TB PPDU).

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

[0413] In this regard, the configuration of one or more TB PPDUs may be indicated based on the A-PPDU-related subfields and at least one other subfield included in the common information field.

[0414] The specific contents of at least one other subfield included in the common information field, the trigger / request / instruction for one or more TB PPDU configurations, and the trigger frame are the same as those described above with reference to FIG. 16, and duplicate descriptions thereof will be omitted.

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

[0416] As described above, compared with the trigger frame that triggers the TB PPDU (e.g., HE TB PPDU, EHT TB PPDU) in existing WLAN systems, the trigger frame proposed in this disclosure has a novel feature of further including information for triggering the TB PPDU and merged PPDU (A-PPDU) of a new version (e.g., EHT next version, UHR).

[0417] By using the trigger frame proposed in this disclosure to support triggers / requests for A-PPDUs as well as new version TB PPDUs, throughput and efficiency aspects in a WLAN system can be enhanced.

[0418] The above-described embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to configure the embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some configurations or features of one embodiment may be included in another embodiment, or may be replaced with corresponding configurations or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to configure an embodiment, or may be included as a new claim by amendment after filing.

[0419] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0420] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of the various embodiments, and non-transitory computer-readable media on which such software or instructions or the like can be stored and executed on a device or computer. Instructions available for programming a processing system to perform features described in the present disclosure may be stored on / in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in the present disclosure. The storage medium may include high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but is not limited thereto, and may 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 optionally includes one or more storage devices that are located remotely from the processor. The memory or alternatively the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers. [Industrial Applicability]

[0421] The method proposed in this disclosure has been described mainly as being applied to an IEEE 802.11-based system, but 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 a trigger frame from an access point (AP), the trigger frame including a common information field; transmitting, to the AP, one or more trigger based physical layer protocol data units (TB) PPDUs (PPDUs) triggered by the trigger frame; The common information field includes an aggregated PPDU (A-PPDU) related subfield, A method in which a configuration of the one or more TB PPDUs is indicated based on the A-PPDU-related subfield and at least one other subfield included in the common information field.

2. A value of 0 in the A-PPDU related subfield indicates an A-PPDU that includes a non-legacy TB PPDU; The method of claim 1 , wherein a value of 1 in the A-PPDU-related subfield indicates at least one of a non-A-PPDU or an A-PPDU that does not include a non-legacy TB PPDU.

3. 2. The method of claim 1, wherein the at least one other subfield comprises B54 and B55 in the common information field.

4. A value of 1 in the B54 indicates that the primary 160 MHz channel is assigned to the HE (high efficiency) TB PPDU; 4. The method of claim 3, wherein a value of 0 in the B54 indicates that the primary 160 MHz channel is assigned to an extremely high throughput (EHT) TB PPDU or a non-legacy TB PPDU.

5. 4. The method of claim 3, wherein the 0 and 1 values ​​of B55 relate to the presence or absence of a non-legacy variant special user information field.

6. 4. The method of claim 3, wherein the one or more TB PPDUs correspond to HE TB PPDUs based on the B54 being set to a value of 1, the B55 being set to a value of 1, and the A-PPDU related subfields being set to a value of 1.

7. 4. The method of claim 3, wherein the one or more TB PPDUs correspond to EHT TB PPDUs based on the B54 being set to a value of 0, the B55 being set to a value of 0, and the A-PPDU related subfields being set to a value of 1.

8. 4. The method of claim 3, wherein the one or more TB PPDUs correspond to a HE TB PPDU and an EHT TB PPDU based on the B54 being set to a value of 1, the B55 being set to a value of 0, and the A-PPDU related subfields being set to a value of 1.

9. 4. The method of claim 3, wherein the one or more TB PPDUs correspond to non-legacy TB PPDUs based on the B54 being set to a value of 0, the B55 being set to a value of 1, and the A-PPDU related subfields being set to a value of 1.

10. 4. The method of claim 3, wherein the one or more TB PPDUs correspond to a HE TB PPDU and a non-legacy TB PPDU based on the B54 being set to a value of 1, the B55 being set to a value of 1, and the A-PPDU related subfields being set to a value of 0.

11. 4. The method of claim 3, wherein the one or more TB PPDUs correspond to an EHT TB PPDU and a non-legacy TB PPDU based on the B54 being set to a value of 0, the B55 being set to a value of 0, and the A-PPDU related subfields being set to a value of 0.

12. 2. The method of claim 1, wherein the presence or absence of a non-legacy variant special user information field is indicated based on the A-PPDU related subfield and the at least one other subfield.

13. 2. The method of claim 1, wherein the trigger frame includes at least one of a special user information field associated with information about a non-legacy TB PPDU or a user information field associated with information for a STA assigned to transmit the non-legacy TB PPDU.

14. The method of claim 13 , wherein the channel indication for the non-legacy TB PPDU is based on a combination of a B25 value and a B39 value in the User Information field.

15. 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; The one or more processors: receiving a trigger frame including a common information field from an access point (AP); The AP is configured to transmit a TB (trigger based) PPDU (physical layer protocol data unit) corresponding to one of one or more TB (trigger based) PPDUs triggered by the trigger frame; The common information field includes an aggregated PPDU (A-PPDU) related subfield, A configuration of the one or more TB PPDUs is indicated based on the A-PPDU-related subfield and at least one other subfield included in the common information field.

16. 1. A processing unit configured to control a station (STA) in a wireless LAN system, the processing unit comprising: one or more processors; and one or more computer memories operably coupled to the one or more processors and storing instructions for performing the method of any one of claims 1 to 14 when executed by the one or more processors.

17. 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, and a station (STA) device in a wireless LAN system to perform the method according to any one of claims 1 to 14.

18. A method performed by an access point (AP) in a wireless LAN system, the method comprising: transmitting a trigger frame including a common information field to a station (STA); receiving, from the STA, one or more trigger based physical layer protocol data units (TB) PPDUs (PPDUs) triggered by the trigger frame; The common information field includes an aggregated PPDU (A-PPDU) related subfield, A method in which a configuration of the one or more TB PPDUs is indicated based on the A-PPDU-related subfield and at least one other subfield included in the common information field.

19. 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: Transmitting a trigger frame including a common information field to a station (STA); The STA is configured to receive one of one or more trigger based physical layer protocol data units (TB) PPDUs (PPDUs) triggered by the trigger frame from the STA; The common information field includes an aggregated PPDU (A-PPDU) related subfield, A configuration of the one or more TB PPDUs is indicated based on the A-PPDU-related subfield and at least one other subfield included in the common information field.

Images