Method and apparatus for transmitting / receiving PPDU based on trigger frame in wireless LAN system

Abstract

Disclosed are a trigger frame-based PPDU transmission / reception method and apparatus in a wireless LAN system. According to one embodiment of the present disclosure, a method performed by means of a station (STA) in a wireless LAN system may comprise the steps of: receiving a trigger frame including a common info field from an access point (AP); and transmitting, to the AP, a trigger-based physical layer protocol data unit (TB PPDU) corresponding to one of the one or more TB PPDUs triggered by means of the trigger frame. The common information field includes an aggregated PPDU (A-PPDU) related subfield, and a configuration of 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 Art

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

[0003] In order to provide a further improved wireless communication environment, improved technologies for extremely high throughput (EHT) are being discussed. For example, technologies supporting multiple-input multiple-output (MIMO) and multiple access point (AP) coordination of increased bandwidth, efficient use of multiple frequency bands, and increased spatial streams are being studied, and specifically, various technologies for supporting services with low latency or real-time characteristics are being studied. In addition, new technologies are being discussed to support ultra-high reliability (UHR), including improvements or extensions to EHT technologies. Summary of the invention

[0004] Technical issues

[0005] The technical object 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.

[0006] The technical objective of the present disclosure is to provide a method and apparatus for performing transmission or reception of a merged PPDU for PPDUs of different versions based on a trigger frame.

[0007] The technical objectives to be achieved by the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the art can clearly understand other technical objectives not described herein through the following description.

[0008] Technical Solution

[0009] According to an aspect of the present disclosure, a method performed by a station (STA) in a wireless LAN system may include: receiving a trigger frame including a common information field from an access point (AP); and sending 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. In this document, the common information field may include an aggregated PPDU (A-PPDU) related subfield, and the configuration of 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.

[0010] According to an additional aspect of the present disclosure, a method performed by an access point (AP) in a wireless LAN system may include: sending a trigger frame including a common information field to a station (STA); and receiving a TBPPDU corresponding to one of one or more trigger-based physical layer protocol data units (TB PPDUs) triggered by the trigger frame from the STA. In this article, the common information field may include an aggregated PPDU (A-PPDU) related subfield, and the configuration of 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.

[0011] Beneficial Effects

[0012] According to the present disclosure, a method and apparatus for allocating resource units in a wireless LAN system may be provided.

[0013] According to the present disclosure, a method and apparatus for performing transmission or reception of a merged PPDU for PPDUs of different versions based on a trigger frame may be provided.

[0014] According to the present disclosure, since a new version PPDU based on a trigger frame and / or merged PPDU transmission and reception are supported, there is an effect of reducing delay and improving throughput and efficiency.

[0015] Effects achievable by the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those skilled in the relevant art through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are included as a part of the detailed description to assist in understanding the present disclosure, provide embodiments of the present disclosure and describe technical features of the present disclosure together with the detailed description.

[0017] Figure 1 A configuration block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0018] Figure 2 is a diagram illustrating an exemplary structure of a WLAN system to which the present disclosure can be applied.

[0019] Figure 3 It is a diagram for explaining a link establishment process to which the present disclosure can be applied.

[0020] Figure 4 This is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0021] Figure 5 It is a diagram for explaining a frame transmission operation based on CSMA / CA to which the present disclosure can be applied.

[0022] Figure 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.

[0023] Figure 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.

[0024] Figures 8 to 10 is a diagram for explaining an example of a resource unit of a WLAN system to which the present disclosure can be applied.

[0025] Fig.11 An example structure of the HE-SIG-B field is illustrated.

[0026] Fig.12 It is a diagram for explaining the MU-MIMO method in which multiple users / STAs are assigned to one RU.

[0027] Fig.13 An example of a PPDU format to which the present disclosure can be applied is illustrated.

[0028] Fig.14 is a diagram showing an example format of a trigger frame to which the present disclosure may be applied.

[0029] Fig.15 An A-PPDU structure to which the present disclosure can be applied is illustrated.

[0030] Fig.16 is a flowchart for illustrating the operation of a STA based on a trigger frame according to the present disclosure.

[0031] Fig.17 is a flowchart for illustrating the operation of an AP based on a trigger frame according to the present disclosure. DETAILED DESCRIPTION

[0032] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed by the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, rather than to represent the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art know that the present disclosure can be implemented without these specific details.

[0033] In some cases, well-known structures and devices may be omitted, or may be shown in the form of a block diagram based on the core functions of each structure and device in order to prevent ambiguity of the concepts of the present disclosure.

[0034] In the present disclosure, when an element is referred to as being "connected", "combined" or "linked" to another element, it may include an indirect connection relationship between another element and a direct connection relationship. In addition, in the present disclosure, the term "comprising" or "having" specifies the presence of the mentioned features, steps, operations, components and / or elements, but does not exclude the presence or addition of one or more other features, stages, operations, components, elements and / or groups thereof.

[0035] In the present disclosure, terms such as "first", "second", etc. are only used to distinguish one element from another element and are not used to limit the elements, and unless otherwise specified, they do not limit the order or importance between elements, etc. Therefore, within the scope of the present disclosure, the first element in an embodiment may be referred to as the second element in another embodiment, and similarly, the second element in an embodiment may be referred to as the first element in another embodiment.

[0036] The terms used in this disclosure are intended to describe specific embodiments, rather than to limit 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 clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the related enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise stated, the " / " between words in this disclosure has the same meaning as "and / or".

[0037] Examples of the present disclosure can be applied to various wireless communication systems. For example, examples of the present disclosure can be applied to wireless LAN systems. For example, examples of the present disclosure can be applied to wireless LANs based on IEEE 802.11a / g / n / ac / ax standards. In addition, examples of the present disclosure can be applied to wireless LANs based on the newly proposed IEEE 802.11be (or EHT) standard. Examples of the present disclosure can be applied to wireless LANs based on the IEEE802.11be version 2 standard corresponding to the additional enhanced technology of the IEEE 802.11be version 1 standard. In addition, examples of the present disclosure can be applied to wireless LANs based on next-generation standards after IEEE 802.11be. In addition, examples of the present disclosure can be applied to cellular wireless communication systems. For example, it can be applied to cellular wireless communication systems based on long term evolution (LTE) technology and 5G new radio (NR) technology based on the third generation partnership project (3GPP) standard.

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

[0039] Figure 1 A block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0040] Figure 1 The first device 100 and the second device 200 illustrated in the figure may be replaced with various terms such as terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), mobile subscriber unit (MSU), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT) or simple user, etc. In addition, the first device 100 and the second device 200 include an access point (AP), a base station (BS), a fixed station, a node B, a base transceiver system (BTS), a network. It may be replaced with various terms such as an artificial intelligence (AI) system, a roadside unit (RSU), a repeater, a router, a relay and a gateway.

[0041] Figure 1 The devices 100 and 200 illustrated in the example may be referred to as stations (STAs). Figure 1The devices 100 and 200 illustrated in the figure may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, and a receiving STA. For example, STA110 and 200 may perform an access point (AP) role or a non-AP role. That is, in the present disclosure, STA110 and 200 may perform the functions of an AP and / or a non-AP. When STA110 and 200 perform an AP function, they may be simply referred to as an AP, and when STA110 and 200 perform a non-AP function, they may be simply referred to as a STA. In addition, in the present disclosure, an AP may also be indicated as an APSTA.

[0042] Reference Figure 1 , the first device 100 and the second device 200 can send and receive radio signals through various wireless LAN technologies (e.g., IEEE802.11 series). The first device 100 and the second device 200 may include interfaces for a media access control (MAC) layer and a physical layer (PHY) that conform to the IEEE802.11 standard.

[0043] In addition, in addition to the wireless LAN technology, 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.) technologies. In addition, the device of the present disclosure may be implemented in various devices such as mobile phones, vehicles, personal computers, augmented reality (AR) devices, and virtual reality (VR) devices. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, machine type communications (MTC), machine to machine (M2M), device to device (D2D), IoT (Internet of Things), etc.

[0044] The first device 100 may include 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 control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. For example, the processor 102 may send a wireless signal including the first information / signal through the transceiver 106 after generating the first information / signal by processing the information in the memory 104. In addition, the processor 102 may receive a wireless signal including the second information / signal through the transceiver 106, and then store the information obtained by the signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including instructions for executing all or part of the processing controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included 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 connected to the processor 102 and may send and / or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0045] The second device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in the present disclosure. For example, the processor 202 may generate third information / signals by processing the information in the memory 204, and then send a wireless signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signals through the transceiver 206, and then store information obtained by signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing all or part of the processing controlled by the processor 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included 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 connected to the processor 202 and may send and / or receive wireless signals through one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a device may refer to a communication modem / circuit / chip.

[0046] In the following, the hardware elements of the apparatus 100, 200 will be described in more detail. Without limitation thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, suggestions, and / or methods disclosed in the present disclosure to provide them to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 according to the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure and obtain a PDU, SDU, message, control information, data, or information.

[0047] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, and the like. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operational flow charts included in the present disclosure may be implemented using firmware or software in the form of codes, instructions and / or instruction sets.

[0048] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0049] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the method and / or operation flow chart of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the description, function, process, suggestion, method and / or operation flow chart, etc. included in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may send and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, one or more processors 102, 202 may control 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 connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to send and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, suggestions, methods and / or operation flow charts, etc. included in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be multiple physical antennas or more logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals into baseband signals to process received user data, control information, wireless signals / channels, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals into RF band signals. Thus, one or more of the transceivers 106 , 206 may include (analog) oscillators and / or filters.

[0050] For example, one of the STAs 100 and 200 may perform the expected operation of an AP, and the other of the STAs 100 and 200 may perform the expected operation of a non-AP STA. Figure 1 The transceivers 106 and 206 of the present invention may perform transmission and reception operations of signals (e.g., packets or physical layer protocol data units (PPDUs) compliant with IEEE 802.11a / b / g / n / ac / ax / be). In addition, in the present disclosure, operations of various STAs generating transmission / reception signals or performing data processing or calculations on transmission / reception signals in advance may be performed by Figure 1The processors 102 and 202 are executed. For example, examples of operations of generating a transmit / receive signal or performing data processing or calculation for a transmit / receive signal in advance may include: 1) determining / obtaining / configuring / calculating / decoding / encoding bit information of fields (signal (SIG), short training field (STF), long training field (LTF), data, etc.) included in the PPDU; 2) determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) for fields (SIG, STF, LTF, data, etc.) included in the PPDU; 3) determining / configuring / obtaining a specific sequence (e.g., pilot sequence, STF / LTF sequence, additional sequence applied to SIG) for fields (SIG, STF, LTF, data, etc.) included in the PPDU action; 4) power control operations and / or power saving operations applied to STAs; 5) operations related to ACK signal determination / obtaining / configuring / calculating / decoding / encoding, etc. In addition, in the following example, various information used by various STAs to determine / acquire / configure / calculate / decode / encode transmission signals and reception signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) may be stored in Figure 1 in the memories 104 and 204.

[0051] Hereinafter, a downlink (DL) may mean a link for communication from an AP STA to a non-AP STA, and a DL PPDU / packet / signal may be transmitted and received through the DL. In DL communication, a transmitter may be a part of an AP STA, and a receiver may be a part of a non-AP STA. An uplink (UL) may mean a link for communication from a non-AP STA to an AP STA, and a UL PPDU / packet / signal may be transmitted and received through the UL. In UL communication, a transmitter may be a part of a non-AP STA, and a receiver may be a part of an AP STA.

[0052] Figure 2 is a diagram illustrating an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

[0053] The structure of the wireless LAN system may be composed of a plurality of components. A wireless LAN supporting STA mobility transparent to an upper layer may be provided through the interaction of the plurality of components. A basic service set (BSS) corresponds to a basic building block of a wireless LAN. Figure 2 It is exemplarily shown that two BSSs (BSS1 and BSS2) exist, and two STAs (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2) are included as members of each BSS. Figure 2The ellipse representing the BSS in the figure can also be understood as representing the coverage area in which the STAs included in the corresponding BSS maintain communication. This area can be called a basic service area (BSA). When a STA moves outside the BSA, it cannot communicate directly with other STAs in the BSA.

[0054] If you don't consider Figure 2 , the most basic BSS type in the wireless LAN is an independent BSS (IBSS), if the DS is shown in FIG. 1 . For example, an IBSS may have a minimum form containing only two STAs. For example, assuming that other components are omitted, a BSS1 containing only STA1 and STA2 or a BSS2 containing only STA3 and STA4 may correspond to representative examples of IBSSs, respectively. This configuration is possible when STAs can communicate directly without an AP. In addition, in this type of wireless LAN, it is not pre-configured but can be configured when a LAN is needed, and this may be referred to as an ad-hoc network. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, STAs are managed in a distributed manner. In the IBSS, all STAs may be composed of mobile STAs, and access to the distributed system (DS) is not allowed, thereby forming a self-contained network.

[0055] The membership of a STA in a BSS can be changed dynamically by turning the STA on or off, entering or exiting a BSS region, etc. In order to become a member of a BSS, a STA can join the BSS using a synchronization process. In order to access all services of the BSS infrastructure, a STA should associate with the BSS. This association can be established dynamically and can include the use of a distributed system service (DSS).

[0056] The direct STA-to-STA distance in a wireless LAN may be limited by PHY performance. In some cases, this distance limitation may be sufficient, but in some cases, communication between STAs at longer distances may be required. A distributed system (DS) can be configured to support extended coverage.

[0057] DS refers to the structure of BSS interconnection. Specifically, Figure 2As shown, the BSS can exist as an extended form of a network composed of multiple BSSs. DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM). In this regard, the wireless medium (WM) and the DSM can be logically separated. Each logical medium is used for different purposes and is used by different components. These media are not limited to being the same, nor are they limited to being different. In this way, the flexibility of the wireless LAN structure (DS structure or other network structure) can be interpreted as multiple media being logically different. That is, the wireless LAN structure can be implemented in various ways, and the corresponding wireless LAN structure can be independently specified by the physical characteristics of each implementation.

[0058] DS can support mobile devices by providing seamless integration of multiple BSSs and providing logical services necessary to address the address leading to the destination. In addition, DS can also include a component called a portal, which is used as a bridge for connection between wireless LAN and other networks (e.g., IEEE 802.X).

[0059] The AP enables access to the DS through the WM for associated non-AP STAs and means an entity that also has STA functionality. Data movement between the BSS and the DS can be performed through the AP. For example, Figure 2 STA2 and STA3 shown in the figure have the function of STA and provide the function of allowing the associated non-AP STA (STA1 and STA4) to access the DS. In addition, since all APs basically correspond to STAs, all APs are addressable entities. The address used by the AP to communicate on the WM is not necessarily the same as the address used by the AP to communicate on the DSM. A BSS composed of an AP and one or more STAs may be referred to as an infrastructure BSS.

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

[0061] In addition to the above-mentioned structure of the DS, an extended service set (ESS) may also be configured to provide wide coverage.

[0062] ESS means a network with arbitrary size and complexity consisting of DS and BSS. ESS may correspond to a set of BSSs connected to one DS. However, ESS does not include DS. The ESS network is characterized by being regarded as an IBSS in the logical link control (LLC) layer. The STAs included in the ESS can communicate with each other, and the mobile STA can move from one BSS to another (within the same ESS) transparently for LLC. The APs included in one ESS may have the same service set identifier (SSID). SSID is distinguished from BSSID, which is an identifier of BSS.

[0063] The wireless LAN system does not assume anything about the relative physical location of the BSS, and all of the following forms are possible. BSSs may partially overlap, which is a form commonly used to provide continuous coverage. In addition, the BSSs may not be physically connected, and logically, there is no limit on the distance between the BSSs. In addition, the BSSs may be physically located in the same location, which can be used to provide redundancy. In addition, one (or more than one) IBSS or ESS network may physically exist in the same space as one (or more than one) ESS network. When an ad hoc network operates in a location where an ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required in the same location, this may correspond to the form of an ESS network, etc.

[0064] Figure 3 is a diagram for explaining a link establishment process to which the present disclosure can be applied.

[0065] In order for a STA to establish a link with respect to a network and send / receive data, it first discovers the network, performs authentication, establishes association, and needs to perform authentication processing for security. The link establishment processing may also be referred to as a session initiation processing or a session establishment processing. In addition, the discovery, authentication, association, and security establishment processing of the link establishment processing may be collectively referred to as an association processing.

[0066] 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, it needs to find a network that it can participate in. The STA should identify compatible networks before participating in a wireless network, and the process of identifying networks present in a specific area is called scanning.

[0067] Scanning schemes include active scanning and passive scanning. Figure 3The network discovery operation including active scanning processing is exemplarily illustrated. In active scanning, the STA performing the scan sends a probe request frame to discover which APs exist around it while the channel moves and waits for a response thereto. The responder sends a probe response frame as a response to the probe request frame to the STA that has sent the probe request frame. Here, the responder may be the STA that last sent a beacon frame in the BSS of the channel being scanned. In the BSS, since the AP sends a beacon frame, the AP becomes the responder, and in the IBSS, the STAs in the IBSS rotate to send beacon frames, so the responder is not constant. For example, a STA that sends a probe request frame on channel 1 and receives a probe response frame on channel 1 may store the BSS-related information included in the received probe response frame, and may move to the next channel (e.g., channel 2), and perform scanning in the same manner (i.e., sending and receiving probe requests / responses on channel 2).

[0068] Although not in Figure 3 , but the scanning operation can be performed in a passive scanning manner. In passive scanning, the STA performing the scan waits for a beacon frame while the channel moves. The beacon frame is one of the management frames defined in IEEE 802.11, and is periodically sent to notify the existence of a wireless network and allow the STA performing the scan to find the wireless network and participate in the wireless network. In the BSS, the AP is used to periodically send beacon frames, and in the IBSS, the STAs within the IBSS rotate to send beacon frames. When the STA performing the scan receives the beacon frame, the STA stores the information of the BSS included in the beacon frame, and records the beacon frame information in each channel while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner. Comparing active scanning with passive scanning, the advantage of active scanning is that it has less delay and less power consumption than passive scanning.

[0069] After the STA discovers the network, an authentication process may be performed at step S320. In order to clearly distinguish from the security establishment operation of step S340 to be described later, this authentication process may be referred to as a first authentication process.

[0070] The authentication process includes the following process: the STA sends an authentication request frame to the AP, and in response thereto, the AP sends an authentication response frame to the STA. The authentication frame for authentication request / response corresponds to a management frame.

[0071] The authentication frame includes an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), a limited cycle group, etc. This corresponds to some examples of information that can be included in the authentication request / response frame, and can be replaced with other information, or additional information can also be included.

[0072] The STA may send an authentication request frame to the AP. The AP may determine whether to allow authentication of the corresponding STA based on the information included in the received authentication request frame. The AP may provide the result of the authentication process to the STA via an authentication response frame.

[0073] After the STA is successfully authenticated, an association process may be performed at step S330. The association process includes the following processes: the STA sends an association request frame to the AP, and in response, the AP sends an association response frame to the STA.

[0074] For example, the association request frame may include information related to various capabilities, a beacon listening interval, a service set identifier (SSID), supported rates, supported channels, RSN, a mobile domain, supported operation categories, a traffic indication map broadcast request (TIM broadcast request), interworking service capabilities, etc. For example, the association response frame may include information related to 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 ratio indicator (RSNI), a mobile domain, a timeout interval (e.g., an association recovery time), an overlapping BSS scanning parameter, a TIM broadcast response, a quality of service (QoS) map, etc. This corresponds to some examples of information that may be included in an association request / response frame, and may be replaced with other information, or additional information may also be included.

[0075] After the STA successfully associates with the network, a security establishment process may be performed at step S340. The security establishment process at step S340 may be referred to as an authentication process through a robust security network association (RSNA) request / response, the authentication process at step S320 may be referred to as a first authentication process, and the security establishment process at step S340 may also be referred to simply as an authentication process.

[0076] The security establishment process of step S340 may include, for example, a process of establishing a private key through an Extensible Authentication Protocol over LAN (EAPOL) frame using a four-way handshake. In addition, the security establishment process may be performed according to a security scheme not defined in the IEEE 802.11 standard.

[0077] Figure 4 It is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0078] In a wireless LAN system, the basic access mechanism of the medium access control (MAC) is a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism is also known as 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, before starting to send, the AP and / or STA may perform a clear channel assessment (CCA) of sensing the radio channel or medium during a predetermined time interval (e.g., DCF interframe space (DIFS)). As a result of the sensing, if it is determined that the medium is in an idle state, frame transmission is started through the corresponding medium. On the other hand, if it is detected that the medium is occupied or busy, the corresponding AP and / or STA does not start its own transmission, and a delay period (e.g., a random backoff period) for medium access may be set and frame transmission may be attempted after waiting. By applying a random backoff period, since multiple STAs are expected to attempt frame transmission after waiting for different time periods, conflicts can be minimized.

[0079] In addition, the IEEE 802.11 MAC protocol provides a hybrid coordination function (HCF). HCF is based on DCF and point coordination function (PCF). PCF is a synchronous access method based on polling, and refers to a method in which all receiving APs and / or STAs periodically poll to receive data frames. In addition, HCF has enhanced distributed channel access (EDCA) and HCF controlled channel access (HCCA). EDCA is a contention-based access method that provides data frames to multiple users in a direction, and HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. In addition, HCF includes a medium access mechanism for improving the QoS (quality of service) of a wireless LAN, and QoS data can be sent during a contention period (CP) and a contention-free period (CFP).

[0080] Reference Figure 4, the operation based on the random backoff period will be described. When the occupied / busy medium becomes idle, multiple STAs may attempt to send data (or frames). As a method of minimizing conflicts, each of the STAs may select a random backoff count respectively and attempt to send after waiting for the corresponding time slot time. The random backoff count has a pseudo-random integer value and may be determined as one of the values ​​ranging from 0 to CW. Here, CW is a contention window parameter value. The CW parameter is assigned CWmin as an initial value, but may take a value twice as large in the event of a transmission failure (e.g., when an ACK for a transmitted frame is not received). When the CW parameter value reaches CWmax, data transmission may be attempted while maintaining the CWmax value until data transmission is successful, and when data transmission is successful, the CWmin value is reset. The values ​​of CW, CWmin, and CWmax are preferably set to 2n-1 (n=0, 1, 2, ...).

[0081] When the random backoff process starts, the STA continuously monitors the medium in the backoff slot countdown according to the determined backoff count value. When the medium is monitored for occupancy, it stops the countdown and waits, and restarts the remaining part of the countdown when the medium becomes idle.

[0082] exist Figure 4 In the example of , when the packet to be sent arrives at the MAC of STA 3, STA3 can send the frame immediately after confirming that the medium has been idle for up to DIFS. The remaining STAs monitor and wait for the medium to be occupied / busy. At the same time, the data to be sent can also occur in each of STA1, STA2 and STA5, and when the medium is monitored as idle, each STA waits for up to DIFS, and then the countdown of the backoff slot can be performed according to the random backoff count value selected by each STA. Assume that STA2 selects the minimum backoff count value and STA1 selects the maximum backoff count value. That is, the example illustrates the case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 completes the backoff count and starts frame transmission. STA1 and STA5 temporarily stop the countdown and wait when STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and restart the stopped backoff count. That is, frame transmission can start after counting down the remaining backoff slot for the remaining backoff time. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. The data to be transmitted may also occur in STA4 while STA2 occupies the medium. From the perspective of STA4, when the medium becomes idle, STA4 may wait for DIFS, and then may perform a countdown according to a random backoff count value selected by STA4, and start transmitting frames. Figure 4The example shows a case where the remaining backoff time of STA5 accidentally collides with the random backoff count value of STA4. In this case, a collision may occur between STA4 and STA5. When a collision occurs, neither STA4 nor STA5 receives an ACK, so data transmission fails. In this case, STA4 and STA5 can double the CW value, select a random backoff count value, and perform a countdown. While the medium is occupied due to the transmission of STA4 and STA5, STA1 waits, and when the medium becomes idle, STA1 waits DIFS, and then starts frame transmission after the remaining backoff time has passed.

[0083] As in Figure 4 In the example of , a data frame is a frame for sending data forwarded to a higher layer, and may be sent after a backoff performed after DIFS has passed since the medium became idle. In addition, a management frame is a frame for exchanging management information that is not forwarded to a higher layer, and is sent after a backoff is performed after an IFS such as DIFS or a point coordination function IFS (PIFS). As subtype frames of the management frame, there are beacons, association requests / responses, reassociation requests / responses, probe requests / responses, authentication requests / responses, and the like. A control frame is a frame for controlling access to a medium. As subtype frames of the control frame, there are request to send (RTS), clear to send (CTS), acknowledgement (ACK), power save poll (PS-Poll), block ACK (BlockAck), block ACK request (BlockACKReq), empty data packet announcement (NDP announcement), and trigger, and the like. If the control frame is not a response frame of the previous frame, it is sent after a backoff is performed after DIFS has passed, and if it is a response frame of the previous frame, it is sent without performing a backoff after a short IFS (SIFS). The type and subtype of a frame may be identified by the type field and subtype field in the frame control (FC) field.

[0084] Quality of Service (QoS) STA can perform a backoff performed after arbitration IFS (AIFS) (i.e., AIFS (where i is a value determined by AC)) for the access category (AC) to which the frame belongs, and then can send the frame. Here, the frame that can use AIFS may be a data frame, a management frame, or a control frame instead of a response frame.

[0085] Figure 5 is a diagram for explaining a frame transmission operation based on CSMA / CA to which the present disclosure can be applied.

[0086] As described above, in addition to the physical carrier sensing in which the STA directly senses the medium, the CSMA / CA mechanism also includes virtual carrier sensing. Virtual carrier sensing is intended to compensate for problems such as hidden node problems that may occur in medium access. For virtual carrier sensing, the MAC of the STA can use a network allocation vector (NAV). NAV is a value that indicates to other STAs the remaining time until the medium is available for use by the STA that is currently using or has the right to use the medium. Therefore, the value set to NAV corresponds to the period during which the STA sending the frame plans to use the medium, and during the corresponding period, the STA receiving the NAV value is prohibited from accessing the medium. For example, the NAV can be configured based on the value of the "Duration" field of the MAC header of the frame.

[0087] exist Figure 5 In the example of FIG. 1 , it is assumed that STA1 intends to send data to STA2, and STA3 is in a position to be able to eavesdrop on some or all frames sent and received between STA1 and STA2.

[0088] In order to reduce the possibility of transmission conflicts among multiple STAs in the CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames can be applied. Figure 5 In the example of , when STA1's transmission is being performed, as a result of STA3's carrier sensing, it can be determined that the medium is in an idle state. That is, STA1 may correspond to a hidden node with respect to STA3. Alternatively, in Figure 5 In the example of , it can be determined that the carrier sensing result medium of STA3 is in an idle state while the transmission of STA2 is being performed. That is, STA2 may correspond to a hidden node with respect to STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of one of STA1 or STA2 or STAs outside the carrier sensing range of the transmission from STA1 or STA3 may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0089] Specifically, STA1 can determine whether the channel is being used by carrier sensing. In terms of physical carrier sensing, STA1 can determine the channel occupancy idle state based on the energy level or signal correlation detected in the channel. In addition, in terms of virtual carrier sensing, STA1 can use the network allocation vector (NAV) timer to determine the channel occupancy state.

[0090] When the channel is in an idle state during DIFS, STA1 may send an RTS frame to STA2 after performing backoff. When STA2 receives the RTS frame, STA2 may send a CTS frame to STA1 as a response to the RTS frame after SIFS.

[0091] If STA3 cannot eavesdrop on the CTS frame from STA2 but can eavesdrop on the RTS frame from STA1, STA3 can set the NAV timer for the frame transmission period (e.g., SIFS+CTS frame+SIFS+data frame+SIFS+ACK frame) that is continuously transmitted thereafter using the duration information included in the RTS frame. Alternatively, if STA3 can eavesdrop on the CTS frame from STA2, STA3 can set the NAV timer for the frame transmission period (e.g., SIFS+data frame+SIFS+ACK frame) that is continuously transmitted thereafter using the duration information included in the CTS frame even though STA3 cannot eavesdrop on the RTS frame from STA1. That is, if STA3 can eavesdrop on one or more of the RTS frame or the CTS frame from one or more of STA1 or STA2, STA3 can set the NAV accordingly. When STA3 receives a new frame before the NAV timer expires, STA3 can update the NAV timer using the duration information included in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0092] When STA1 receives a CTS frame from STA2, STA1 may send a data frame to STA2 after SIFS, starting from the time point when reception of the CTS frame is completed. When STA2 successfully receives the data frame, STA2 may send an ACK frame to STA1 after SIFS as a response to the data frame. When the NAV timer expires, STA3 may determine whether the channel is being used by carrier sensing. When STA3 determines that the channel is not being used by other terminals during the DIFS period after the NAV timer expires, STA3 may attempt channel access after the contention window (CW) according to the random backoff has passed.

[0093] Figure 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.

[0094] With the help of instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare a MAC PDU (MPDU) to be transmitted. For example, when a command requesting the PHY layer to start transmitting is received from the MAC layer, the PHY layer switches to a transmission mode, and configures information (e.g., data) provided from the MAC layer in the form of a frame and transmits it. In addition, when the PHY layer detects a valid preamble of a received frame, the PHY layer monitors the header of the preamble and transmits a command notifying the start of reception of the PHY layer to the MAC layer.

[0095] In this manner, information transmission / reception in the wireless LAN system is performed in the form of frames, and for this purpose, a PHY layer protocol data unit (PPDU) frame format is defined.

[0096] The 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 consist of only L-STF (legacy STF), L-LTF (legacy-LTF), a SIG field, and a data field. In addition, depending on the type of PPDU frame format (e.g., HT mixed format PPDU, HT greenfield format PPDU, VHT (very high throughput) PPDU, etc.), additional (or different types of) STF, LTF, and SIG fields may be included between the SIG field and the data field (to be referred to later). Figure 7 Describe this).

[0097] STF is a signal used for signal detection, automatic gain control (AGC), diversity selection, precise time synchronization, etc., and LTF is a signal used for channel estimation and frequency error estimation. STF and LTF can be called signals for synchronization and channel estimation of the OFDM physical layer.

[0098] 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. In addition, the SIG field may include a parity bit, a SIG tail bit, etc.

[0099] The data field may include a service (SERVICE) field, a physical layer service data unit (PSDU) and a PPDU tail bit, and may also include padding bits if necessary. Some bits of the service field may be used for synchronization of the descrambler at the receiving end. The PSDU corresponds to the MAC PDU defined in the MAC layer and may include data generated / used in the upper layer. The PPDU tail bit may be used to return the encoder to the 0 state. The padding bit may be used to adjust the length of the data field in predetermined units.

[0100] MAC PDU is defined according to 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 may consist of a MAC PDU and be transmitted / received through a PSDU of a data portion of a PPDU frame format.

[0101] 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 corresponding frame, etc. For details of the sequence control, QoS control, and HT control subfields of the MAC header, refer to the IEEE 802.11 standard document.

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

[0103] Figure 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.

[0104] In standards such as IEEE 802.11a / g / n / ac / ax, various types of PPDUs have been used. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and data fields. The basic PPDU format may also be referred to as a non-HT PPDU format.

[0105] The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT fields with respect to the basic PPDU format. Figure 7 The HT PPDU format shown in the figure may be referred to as an HT mixed format. In addition, an HT greenfield format PPDU may be defined, and this corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and a data field, excluding L-STF, L-LTF, and L-SIG (not shown).

[0106] An example of a VHT PPDU format (IEEE 802.11ac) additionally includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields for the basic PPDU format.

[0107] Examples of HE PPDU formats (IEEE 802.11ax) additionally include repeated L-SIG (RL-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF, and packet extension (PE) fields with respect to the basic PPDU format. According to the detailed examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-user (MU), while the HE-SIG-B is not included in the HE PPDU format for single user (SU). In addition, the PPDU format based on HE trigger (TB) does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8us. The extended range (HE ER) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us.

[0108] Figures 8 to 10 is a diagram for explaining an example of a resource unit of a WLAN system to which the present disclosure can be applied.

[0109] Reference Figures 8 to 10 , a resource unit (RU) defined in a wireless LAN system will be described. A RU may include multiple subcarriers (or tones). When a signal is transmitted to multiple STAs based on an OFDMA scheme, an RU may be used. In addition, an RU may be defined even when a signal is transmitted to one STA. An RU may be used for a data field, an STF, an LTF, etc. of a PPDU.

[0110] like Figures 8 to 10 As shown in , RUs corresponding to different numbers of tones (i.e., subcarriers) are used to construct some fields of a 20 MHz, 40 MHz, or 80 MHz X-PPDU (X is HE, EHT, etc.). For example, resources may be allocated in RU units as shown for the X-STF, X-LTF, and data fields.

[0111] Figure 8 is a diagram illustrating exemplary allocation of resource units (RUs) used on a 20 MHz frequency band.

[0112] like Figure 8As shown at the top of , 26-units (i.e., units corresponding to 26 tones) may be allocated. 6 tones may be used as a guard band in the leftmost band of the 20 MHz band, and 5 tones may be used as a guard band in the rightmost band of the 20 MHz band. In addition, 7 DC tones are inserted into the center band (that is, the DC band), and 26-units corresponding to each of the 13 tones may exist on the left and right sides of the DC band. In addition, 26-units, 52-units, and 106-units may be allocated to other bands. Each unit may be allocated for STA or user.

[0113] Figure 8 The RU allocation is used not only for the multi-user (MU) case but also for the single-user (SU) case, and in this case, a 242-unit can be used, such as Figure 8 In this case, three DC tones can be inserted.

[0114] exist Figure 8 In the examples, various sizes of RUs are illustrated, that is, 26-RU, 52-RU, 106-RU, 242-RU, etc., but the specific sizes of these RUs can be reduced or expanded. Therefore, in the present disclosure, the specific size of each RU (i.e., the number of corresponding tones) is exemplary and not restrictive. In addition, within a predetermined bandwidth (e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, ...) in the present disclosure, the number of RUs can vary according to the size of the RU. In the following description, Fig. 9 and / or Fig.10 The fact that the size and / or number of RUs can vary is related to Figure 8 The same example.

[0115] Fig. 9 is a diagram illustrating exemplary allocation of resource units (RUs) used on a 40 MHz frequency band.

[0116] As in Figure 8 As in the example using various RU sizes, you can also Fig. 9 In the example of , 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. are used. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0117] Additionally, as shown, when used for a single user, a 484-RU may be used.

[0118] Fig.10 is a diagram illustrating exemplary allocation of resource units (RUs) used on an 80 MHz frequency band.

[0119] As in Figure 8 and Fig. 9 As in the example using various RU sizes, you can also Fig.10 In the example of 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. are used. In addition, in the case of 80MHz PPDU, the RU allocation of HE PPDU and EHT PPDU can be different, and Fig.10 The example of FIG. 4 shows an example of RU allocation for an 80 MHz EHT PPDU. Fig.10 The scheme in which 12 tones in the example 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 is the same as in the HE PPDU and the EHT PPDU. Unlike the HE PPDU in which 7 DC tones are inserted in the DC band and there is a 26-RU corresponding to each of the 13 tones on the left and right sides of the DC band, in the EHT PPDU, 23 DC tones are inserted in the DC band and there is a 26-RU on the left and right sides of the DC band. Unlike the HE PPDU in which one empty subcarrier exists between the 242-RUs instead of the center band, there are five empty subcarriers in the EHT PPDU. In the HE PPDU, one 484-RU does not include an empty subcarrier, but in the EHT PPDU, one 484-RU includes 5 empty subcarriers.

[0120] Additionally, as shown, when used for a single user, 996-RU may be used, and in this case, 5 DC tones are inserted as with HEPPDU and EHT PPDU.

[0121] exist Fig.10 In the example, the EHT PPDU on 160MHz can be configured with multiple 80MHz sub-blocks. The RU allocation for each 80MHz sub-block can be the same as Fig.10 If the 80 MHz sub-block of a 160 MHz or 320 MHz EHT PPDU is not punctured and the entire 80 MHz sub-block is used as a RU or part of more than one RU (MRU), the 80 MHz sub-block can be used. Fig.10 The 996-RU.

[0122] Here, the MRU corresponds to a group of subcarriers (or tones) consisting of multiple RUs, and the multiple RUs constituting the MRU may be RUs of the same size or 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 a small size (e.g., 26, 52, or 106) RU or a large size (e.g., 242, 484, or 996) RU. That is, one MRU including a small size RU and a large size RU may not be configured / defined. In addition, the multiple RUs constituting one MRU may be continuous in the frequency domain, or may not be continuous.

[0123] When an 80 MHz sub-block includes RUs less than 996-tones or a portion of the 80 MHz sub-block is punctured, the 80 MHz sub-block may use RU allocations other than the 996-tone RUs.

[0124] The RU of the present disclosure may be used for uplink (UL) and / or downlink (DL) communication. For example, when trigger-based UL-MU communication is performed, the STA (e.g., AP) that sends the trigger may allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA through trigger information (e.g., a trigger frame or a trigger response schedule (TRS)), and allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. Thereafter, the first STA may send a first trigger-based (TB) PPDU based on the first RU, and the second STA may send a second TB PPDU based on the second RU. The first / second TB PPDU may be sent to the AP in the same time period.

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

[0126] Information about the allocation of RUs may be signaled in HE PPDU format through HE-SIG-B.

[0127] Fig.11 An example structure of the HE-SIG-B field is illustrated.

[0128] As shown, the HE-SIG-B field 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.

[0129] The common field may include information about RU allocation (eg, RU assignment, RUs allocated for MU-MIMO, the number of MU-MIMO users (STAs), etc.).

[0130] The common field may include N*8 RU allocation subfields. Here, N is the number of subfields, N=1 in the case of 20 or 40MHz MU PPDU, N=2 in the case of 80MHz MU PPDU, N=4 in the case of 160MHz or 80+80MHz MU PPDU, and so on. An 8-bit RU allocation subfield may indicate the size (26, 52, 106, etc.) and frequency position (or RU index) of the RU included in the 20MHz band.

[0131] For example, if the value of the 8-bit RU Allocation subfield is 00000000, this may indicate that Figure 8 In the example, nine 26-RUs are allocated in sequence from the leftmost side to the rightmost side, if the value is 00000001, this may indicate that seven 26-RUs and one 52-RU are allocated in sequence from the leftmost side to the rightmost side, and if the value is 00000010, this may indicate that five 26-RUs, one 52-RU, and two 26-RUs are allocated in sequence from the leftmost side to the rightmost side.

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

[0133] Basically, one user / STA can be assigned to each of multiple RUs, and different users / STAs can be assigned to different RUs. For RUs larger than a predetermined size (e.g., 106, 242, 484, 996-tones, ...), multiple users / STAs can be assigned to one RU, and the MU-MIMO scheme can be applied to multiple users / STAs.

[0134] The set of user-specific fields includes information about how all users (STAs) of the corresponding PPDU decode their payloads. The user-specific field may contain zero or more user block fields. The non-end-user block field includes two user fields (ie, information to be used for decoding in two STAs). The end-user block field contains one or two user fields. The number of user fields may be indicated by the RU allocation subfield of the HE-SIG-B, the number of symbols of the HE-SIG-B, or the MU-MIMO user field of the HE-SIG-A. The user-specific field may be encoded separately from the common field or independently of the common field.

[0135] Fig.12 is a diagram for explaining a MU-MIMO method in which multiple users / STAs are assigned to one RU.

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

[0137] The user field may be constructed based on two formats. The user field for MU-MIMO allocation may be constructed in a first format, and the user field for non-MU-MIMO allocation may be constructed in a second format. Fig.12 For example, user fields 1 to 3 may be based on a first format, and user fields 4 to 8 may be based on a second format. The first format and the second format may contain bit information of the same length (eg, 21 bits).

[0138] The user field of the first format (i.e., the format allocated for MU-MIMO) may be constructed as follows. For example, among all 21 bits of a user field, B0-B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11-B14 include spatial configuration information such as the number of spatial streams of the corresponding user, B15-B18 include modulation and coding scheme (MCS) information applied to the data field of the corresponding PPDU, B19 is defined as a reserved field, and B20 may include information about the coding type (e.g., binary convolutional coding (BCC) or low-density parity check (LDPC)) applied to the data field of the corresponding PPDU.

[0139] The user field of the second format (i.e., the format for non-MU-MIMO allocation) can be constructed as follows. For example, among all 21 bits of a user field, B0-B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11-B13 include information about the number of spatial streams (NSTS) applied to the corresponding RU, B14 includes information indicating whether beamforming is performed (or whether a beamforming control matrix is ​​applied), B15-B18 include modulation and coding scheme (MCS) information applied to the data field of the corresponding PPDU, B19 includes information indicating whether DCM (dual carrier modulation) is applied, and B20 may include information about the coding type (e.g., BCC or LDPC) applied to the data field of the corresponding PPDU.

[0140] The MCS, MCS information, MCS index, MCS field, etc. used in the present disclosure may be indicated by a specific index value. For example, the MCS information may be indicated as index 0 to index 11. The MCS information includes information about the constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and the coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). Information about the channel coding type (e.g., BCC or LDPC) may be excluded from the MCS information.

[0141] Fig.13 An example of a PPDU format to which the present disclosure can be applied is illustrated.

[0142] Fig.13The PPDU of the present disclosure may be referred to as various names such as EHT PPDU, transmitted PPDU, received PPDU, first type or Nth type PPDU. For example, the PPDU or EHT PPDU of the present disclosure may be referred to as various names such as transmitted PPDU, received PPDU, first type or Nth type PPDU. In addition, the EHT PPU may be used in an EHT system and / or a new wireless LAN system in which the EHT system is improved.

[0143] Fig.13 The EHT MU PPDU corresponds to a PPDU carrying one or more data (or PSDU) for one or more users. That is, the EHT MU PPDU can be used for SU transmission and MU transmission. For example, the EHT MU PPDU can correspond to a PPDU for one receiving STA or more receiving STAs.

[0144] exist Fig.13 In the EHT TB PPDU, the EHT-SIG is omitted compared to the EHT MU PPDU. Upon receiving a trigger for ULMU transmission (eg, a trigger frame or TRS), the STA may perform UL transmission based on the EHT TB PPDU format.

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

[0146] The subcarrier frequency spacing of the L-STF, L-LTF, L-SIG, RL-SIG, Universal Signal (U-SIG), EHT-SIG fields (these are called pre-EHT modulation fields) can be set to 312.5kHz. The subcarrier frequency spacing of the EHT-STF, EHT-LTF, data and PE fields (these are called EHT modulation fields) can be set to 78.125kHz. That is, the tone / subcarrier index of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG and EHT-SIG fields can be indicated in units of 312.5kHz, and the tone / subcarrier index of the EHT-STF, EHT-LTF, data and PE fields can be indicated in units of 78.125kHz.

[0147] Fig.13 The L-LTF and L-STF can be used with Figure 6 to Figure 7 The corresponding fields of the PPDU described in are constructed identically.

[0148] Fig.13The L-SIG field may consist of 24 bits and may be used to transmit rate and length information. For example, the L-SIG field includes a 4-bit rate field, a 1-bit reserved bit, a 12-bit length field, a 1-bit parity field, and a 6-bit tail field. For example, the 12-bit length field may include information about the duration or length of the PPDU. For example, the value of the 12-bit length field may be determined based on the type of the PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the length field may be determined as a multiple of 3. For example, for HE PPDUs, the value of the length field may be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0149] For example, the transmitting STA may apply BCC encoding based on the coding rate of 1 / 2 to 24 bits of information of the L-SIG field. Thereafter, 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 any position except the pilot subcarrier (e.g., {subcarrier index -21, -7, +7, +21}) and the DC subcarrier (e.g., {subcarrier index 0}). As a result, the 48 BPSK symbols may be mapped to subcarrier indexes -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map the signal of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

[0150] The transmitting STA can construct the RL-SIG with the same structure as the L-SIG. BPSK modulation is applied to the RL-SIG. Based on the existence of the RL-SIG, the receiving STA can identify whether the received PPDU is a HE PPDU or an EHT PPDU.

[0151] exist Fig.13 After the RL-SIG, a universal SIG (U-SIG) may be inserted. The U-SIG may be referred to by various names such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, and a first (type) control signal.

[0152] The U-SIG may include N bits of information and may include information for identifying the EHT PPDU type. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol of the U-SIG (e.g., OFDM symbol) 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 send 26 bits of information. For example, each symbol of the U-SIG may be sent and received based on 52 data tones and 4 pilot tones.

[0153] For example, through U-SIG (or U-SIG field), A-bit information (e.g., 52 uncoded bits) may be transmitted, the first symbol of U-SIG (e.g., U-SIG-1) may transmit the first X-bit information (e.g., 26 uncoded bits) of the total A-bit information, and the second symbol of U-SIG (e.g., U-SIG-2) may transmit the remaining Y-bit information (e.g., 26 uncoded bits) of the total A-bit information. For example, the transmitting STA may obtain the 26 uncoded bits included in each U-SIG symbol. The transmitting STA may generate 52 coded bits by performing convolution encoding (e.g., BCC encoding) based on a rate of R=1 / 2, and perform interleaving on the 52 coded bits. The transmitting STA may generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52 coded bits. Except for DC index 0, one U-SIG symbol may be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) except for the pilot tones -21, -7, +7, and +21.

[0154] For example, the A-bit information (e.g., 52 uncoded bits) sent by the U-SIG includes a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit length field). The CRC field and the tail field may be sent through the second symbol of the U-SIG. The CRC field may be constructed based on the 26 bits of the first symbol allocated to the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and may be constructed based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of the convolutional decoder, and, for example, the tail field may be set to 0.

[0155] The bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-dependent bits and version-independent 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 the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to as various names such as the first control bit and the second control bit.

[0156] For example, the version-independent bit of the U-SIG may include a 3-bit physical layer version identifier (PHY version identifier). For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted / received PPDU. For example, the first value of the 3-bit PHY version identifier may indicate that the transmitted / received PPDU is an EHT PPDU. In other words, when transmitting an EHT PPDU, the transmitting STA may set the 3-bit PHY 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 PHY version identifier having the first value.

[0157] For example, the version-independent bits of the U-SIG may include a 1-bit UL / DL flag field. A first value of the 1-bit UL / DL flag field is associated with UL communication, and a second value of the UL / DL flag field is associated with DL communication.

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

[0159] For example, if the EHT PPDU is classified into various types (e.g., EHT PPDU associated with SU mode, EHT PPDU associated with MU mode, EHT PPDU associated with TB mode, EHT PPDU associated with extended range transmission, etc.), information about the EHT PPDU type may be included in the version-related bit of the U-SIG.

[0160] For example, U-SIG may include information about the following items: 1) a bandwidth field containing information about the bandwidth, 2) a field containing information about the MCS scheme applied to the EHT-SIG, 3) an indication field containing information related to whether the DCM technology is applied to the EHT-SIG, 4) a field containing information about the number of symbols used for the EHT-SIG, 5) a field containing information about whether the EHT-SIG is constructed on all frequency bands, 6) a field containing information about the type of EHT-LTF / STF, and 7) a field indicating the EHT-LTF length and the CP length.

[0161] Can Fig.13 Preamble puncturing may be applied to a PPDU that is sent to one or more users. Preamble puncturing may mean the transmission of a PPDU in which no signal exists in one or more 20 MHz subchannels in the bandwidth of the PPDU. Preamble puncturing may be applied to a PPDU that is sent to one or more users. For example, for an EHT MU PPDU in OFDMA transmission with a bandwidth greater than 40 MHz and a non-OFDMA transmission with a bandwidth of 80 MHz and 160 MHz, the resolution of preamble puncturing may be 20 MHz. That is, in the above case, puncturing on a subchannel smaller than 242-tone RUs may not be allowed. In addition, for an EHT MU PPDU in a non-OFDMA transmission with a bandwidth of 320 MHz, the resolution of preamble puncturing may be 40 MHz. That is, puncturing of a subchannel smaller than 484-tone RUs in a 320 MHz bandwidth may not be allowed. In addition, preamble puncturing may not be applied to the primary 20 MHz channel in the EHT MU PPDU.

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

[0163] For example, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be independently constructed in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG includes information about the 160 MHz bandwidth, and the second field of the first U-SIG includes information about the preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern). In addition, the first field of the second U-SIG includes information about the 160 MHz bandwidth, and the second field of the second U-SIG includes information about the preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern). The EHT-SIG after the first U-SIG may include information about preamble puncturing applied to the second 80 MHz frequency band (i.e., information about the preamble puncturing pattern), and the EHT-SIG after the second U-SIG may include information about preamble puncturing applied to the first 80 MHz frequency band (i.e., information about the preamble puncturing pattern).

[0164] Additionally or alternatively, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. The U-SIG may include information about preamble puncturing of all bands (i.e., information about preamble puncturing patterns). That is, the EHT-SIG does not include information about preamble puncturing, and only the U-SIG may include information about preamble puncturing (i.e., information about preamble puncturing patterns).

[0165] The U-SIG can be constructed in units of 20MHz. For example, if an 80MHz PPDU is constructed, the U-SIG can be duplicated. That is, the same 4 U-SIGs can be included in the 80MHz PPDU. PPDUs with bandwidths exceeding 80MHz can include different U-SIGs.

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

[0167] EHT-SIG may include Fig.11 and Fig.12 The technical features of HE-SIG-B are described. For example, Figure 8 As in the example of , the EHT-SIG may include a common field and a user-specific field. 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.

[0168] As in Fig.11 As in the example of , the common field of EHT-SIG and the user-specific field of EHT-SIG can be encoded separately. One user block field included in the user-specific field can contain information for two user fields, but the last user block field included in the user-specific field can contain one or two user fields. That is, one user block field of EHT-SIG can contain up to two user fields. As in Fig.12 As in the example of , each user field may be associated with a MU-MIMO allocation or a non-MU-MIMO allocation.

[0169] With Fig.11 In the same manner as in the example of , the common field of the EHT-SIG may include a CRC bit and a tail bit. The length of the CRC bit may be determined as 4 bits, and the length of the tail bit may be determined as 6 bits and may be set to 000000.

[0170] As in Fig.11As in the example of , the common field of the EHT-SIG may include RU allocation information. The RU allocation information may be information about the locations of the RUs to which multiple users (ie, multiple receiving STAs) are allocated. The RU allocation information may be configured in units of 9 bits (or N bits).

[0171] A mode in which the common field of the EHT-SIG is omitted may be supported. A mode in which the common field of the EHT-SIG is omitted may be referred to as a compressed mode. When the compressed mode is used, multiple users of the EHT PPDU (ie, multiple receiving STAs) may decode the PPDU (eg, the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) received via the same frequency band. When the non-compressed mode is used, multiple users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU may receive the PPDU (eg, the data field of the PPDU) via different frequency bands.

[0172] The EHT-SIG may be constructed 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 constructed based on the DCM scheme. The DCM scheme may reuse the same signal on two subcarriers to provide an effect similar to frequency diversity, reduce interference, and improve coverage. For example, modulation symbols applying the same modulation scheme may be repeatedly mapped on available tones / subcarriers. For example, a modulation symbol (e.g., a BPSK modulation symbol) applying a specific modulation scheme may be mapped to the first continuous half tone (e.g., the 1st to the 26th tone) among the N data tones (e.g., 52 data tones) allocated for the EHT-SIG, and a modulation symbol (e.g., a BPSK modulation symbol) applying the same specific modulation scheme may be mapped to the remaining continuous half tones (e.g., the 27th to the 52nd tone). 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 related to whether the DCM scheme is applied to the EHT-SIG (eg, a 1-bit field) may be included in the U-SIG. Fig.13 The EHT-STF can be used to enhance automatic gain control (AGC) estimation in a MIMO environment or an OFDMA environment. Fig.13 The EHT-LTF can be used to estimate channels in a MIMO environment or an OFDMA environment.

[0173] Information about the type of STF and / or LTF (including information about a guard interval (GI) applied to LTF) may be included in Fig.13The U-SIG field and / or EHT-SIG field of the RFID tag may be used.

[0174] Can be based on Figures 8 to 10 Example construction of RU allocation Fig.13 PPDU (ie, EHT PPDU).

[0175] For example, based on Figure 8 The RU constructs an EHT PPDU to be sent on the 20 MHz band, that is, a 20 MHz EHT PPDU. Figure 8 As shown in , the RU positions of the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU can be determined. Fig. 9 The RU constructs an EHT PPDU to be sent on the 40 MHz band, that is, a 40 MHz EHT PPDU. Fig. 9 As shown in , RU positions of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined.

[0176] Can be based on Fig.10 The RU constructs an EHT PPDU to be sent on the 80 MHz band, that is, an 80 MHz EHT PPDU. Fig.10 As shown in , RU positions of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined. Fig.10 The tone plan for 80 MHz in may correspond to Fig. 9 Two repetitions of the tone plan for 40 MHz.

[0177] The tone plan for 160 / 240 / 320MHz can be repeated multiple times Fig. 9 or Fig.10 The mode is configured in the form of.

[0178] Fig.13 A PPDU can be identified as an EHT PPDU based on the following method.

[0179] The receiving STA may determine the type of the received PPDU as an EHT PPDU based on the following. For example, when 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) the RL-SIG that repeats the L-SIG of the received PPDU is detected, and 3) the result of applying the modulo 3 calculation to the value of the length field of the L-SIG of the received PPDU (i.e., the remainder after division by 3) is detected as 0, the received PPDU may be determined to be an EHT PPDU. When the received PPDU is determined to be an EHT PPDU, the receiving STA may determine the type of the received PPDU as an EHT PPDU based on Fig.13 In other words, the receiving STA can determine that the received PPDU is an EHT PPDU based on 1) the first symbol (BSPK) after the L-LTF signal, 2) the RL-SIG that is adjacent to the L-SIG field and is the same as the L-SIG, and 3) the L-SIG including the length field in which the result of applying modulo 3 is set to 0.

[0180] For example, the receiving STA may determine the type of the received PPDU as the HE PPDU based on the following: For example, when 1) the first symbol after the L-LTF signal is BPSK, 2) the RL-SIG repeating the L-SIG 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 as the HE PPDU.

[0181] For example, the receiving STA may determine the type of the received PPDU as non-HT, HT, and VHT PPDU based on the following: For example, when 1) the first symbol after the L-LTF signal is BPSK and 2) the RL-SIG repeating the L-SIG is not detected, the received PPDU may be determined as non-HT, HT, and VHT PPDU.

[0182] In addition, when the receiving STA detects the RL-SIG that repeats the L-SIG in the received PPDU, it can be determined whether the received PPDU is a HE PPDU or an EHT PPDU. In this case, if the rate (6Mbps) check fails, the received PPDU can be determined as a non-HT, HT, or VHT PPDU. If the rate (6Mbps) check and parity check pass, when the result of applying modulo 3 to the length value of the L-SIG is detected as 0, the received PPDU can be determined as an EHT PPDU, and when the result of length mod 3 is not 0, it can be determined as an HE PPDU.

[0183] Fig.13 The PPDU can be used to send and receive various types of frames. For example, Fig.13 The PPDU can be used to (simultaneously) send and receive one or more of control frames, management frames, or data frames.

[0184] Fig.14 is a diagram showing an example format of a trigger frame to which the present disclosure may be applied.

[0185] The trigger frame may allocate resources for at least one TB PPDU transmission and request TB PPDU transmission. The trigger frame may also include other information required by the STA, in response to which the STA transmits the TB PPDU. The trigger frame may include common information and user information list fields in the frame body.

[0186] The common information field may include information commonly used for at least one TBPPDU sent for a triggered frame request, such as trigger type, UL length, whether there are subsequent trigger frames (e.g., more TFs), whether channel sensing (CS) is required, UL bandwidth (BW), etc. Fig.14 The EHT variant common information field format is exemplarily shown.

[0187] The 4-bit Trigger Type subfield may have a value from 0 to 15. Among them, the values ​​0, 1, 2, 3, 4, 5, 6, and 7 of the Trigger Type subfield are defined to correspond to Basic, Beamforming Report Poll (BFRP), Multi-User Block Acknowledgement Request (MU-BAR), Multi-User Request to Send (MU-RTS), Buffer Status Report Poll (BSRP), Multicast with Retry (GCR) MU-BAR, Bandwidth Query Report Poll (BQRP), and NDP Feedback Report Poll (NFRP), and values ​​8-15 are defined to be reserved.

[0188] In the common information, the trigger-related common information subfield may include information selectively included based on the trigger type.

[0189] A special user information field may be included in the trigger frame. The special user information field does not include user-specific information, but includes extended common information that is not provided in the common information field.

[0190] The user information list includes at least 0 user information fields. Fig.14 The EHT variant user information field format is exemplarily shown.

[0191] It indicates that the AID12 subfield is basically a user information field of the STA with the corresponding AID. In addition, when the AID12 field has a predetermined specific value, it can be used for other purposes, including allocating a random access (RA)-RU or configuring in the form of a special user information field. The special user information field is a user information field that does not include user-specific information but includes extended public information that is not provided in the public information field. For example, the special user information field can be identified by the AID12 value 2007, and the special user information field flag subfield in the public information field can indicate whether the special user information field is included.

[0192] The RU allocation subfield may indicate the size and location of the RU / MRU. For this purpose, the RU allocation subfield may be interpreted with the PS160 (primary / secondary 160 MHz) subfield of the user information field, the UL BW subfield of the common information field, and the like.

[0193] In addition, in the present disclosure, a tone plan may be associated with a rule for determining the size and / or location of a resource unit (RU). In the following, a tone plan applied to a HE PPDU (i.e., a PPDU according to the IEEE 802.11ax standard) is described as an example. Specifically, the RU size / location applied to the HE PPDU and control information related to the RU applied to the HE PPDU are described.

[0194] In the present disclosure, the control information related to the RU (or the control information related to the tone plan) may include control information about the size and position of the RU, information about the user STA assigned to a specific RU, the frequency bandwidth of the PPDU including the RU, and / or the modulation scheme applied to the specific RU. The control information related to the RU may be included in the SIG field. For example, the control information related to the RU may be included in the HE-SIG-B field. That is, in the process of generating a transmitted PPDU, the transmitting STA may include control information about 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, obtain the control information included in the HE-SIG-B, determine whether there is an RU assigned to the corresponding receiving STA, and decode the allocated RU based on the HE-SIG-B.

[0195] In an existing wireless LAN system (e.g., IEEE 802.11ax standard), 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 sent and received through the first RU.

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

[0197] Specifically, the RU may include multiple subcarriers. For example, if the RU includes N subcarriers, it may be represented as an N-tone RU or N RU. The location of a specific RU may be indicated by a subcarrier index. Here, the subcarrier index may be defined in units of subcarrier frequency intervals. For example, in a wireless LAN system, the subcarrier frequency interval may be 312.5kHz or 78.125kHz, and the subcarrier frequency interval for the RU may be 78.125kHz. That is, the subcarrier index "+1" for the RU may represent a position where 78.125kHz is added to the DC tone, and the subcarrier index "-1" for the RU may represent a position where 78.125kHz is reduced from the DC tone. For example, if the location of a specific RU is represented as [-121:-96], the RU is located in the region from subcarrier index -121 to subcarrier index -96, and as a result, the RU may include 26 subcarriers. In addition, the N-tone RU may include a preconfigured pilot tone.

[0198] Trigger frame for non-legacy PPDU and / or aggregated PPDU

[0199] In a wireless LAN system, TB PPDU transmission corresponding to UL multi-user (MU) transmission may be possible through a trigger frame.

[0200] In this regard, the present disclosure is based on the above (for example, with Fig.14 A trigger frame for TB PPDU transmission and reception in a next generation wireless LAN system (eg, next 11be, UHR, etc.) is proposed.

[0201] In addition, the present disclosure proposes a trigger frame considering a TB A-PPDU (aggregated PPDU) in which PPDUs of different wireless LAN versions can be simultaneously transmitted to improve efficiency and throughput.

[0202] That is, the trigger frame proposed in the present disclosure can be used to trigger / request (soligate) the transmission of TB PPDU in the next generation wireless LAN system. Additionally or alternatively, the trigger frame proposed in the present disclosure can be used to trigger / request the transmission of TB A-PPDU.

[0203] Fig.15 An A-PPDU structure to which the present disclosure can be applied is illustrated.

[0204] Reference Fig.15 , the A-PPDU can be constructed using the first sub-PPDU, the second sub-PPDU and the third sub-PPDU.

[0205] For example, the first sub-PPDU may support a bandwidth of 160 MHz, the second sub-PPDU may support a bandwidth of 80 MHz, and the third sub-PPDU may support a bandwidth of 80 MHz.

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

[0207] In the present disclosure, it is proposed to improve the existing (for example, Fig.14 Related) trigger frame to trigger / request TB PPDU and enhanced trigger frames of various TB A-PPDUs in the next generation wireless LAN system.

[0208] The enhanced trigger frame may correspond to a next version trigger frame considered in a next generation wireless LAN system.

[0209] For the sake of clarity of explanation, the enhanced trigger frame proposed in the present disclosure is referred to as a non-traditional trigger frame. For example, a traditional trigger frame may include a trigger frame for triggering / requesting a HE version of a PPDU and a trigger frame for triggering / requesting an EHT version of a PPDU (e.g., Fig.14 ).

[0210] In the description of the present disclosure, "non-traditional" may mean a subsequent version after a previous version / variation.

[0211] As a detailed example, “non-traditional” in the present disclosure can be applied by replacing it with a version / variant expression (e.g., UHR) after the EHT version / variant.

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

[0213] Here, the non-traditional variant common information field, the non-traditional variant special user information field and the non-traditional user information field can respectively represent the variant common information field, the variant special user information field and the user information field used for the next version (e.g., the next 11be, UHR, etc.) in the next generation wireless LAN system.

[0214] If the non-legacy trigger frame triggers the A-PPDU, it may include a (legacy) special user information field, a legacy variant user information field (eg, HE variant user information field, EHT variant user information field).

[0215] In the present disclosure, a trigger frame for a case where a wireless LAN system is defined as having a bandwidth of only 320 MHz (hereinafter, embodiment 1) and a trigger frame for a case where a wireless LAN system is defined as having a bandwidth of 480 MHz / 640 MHz (hereinafter, embodiment 2) are described.

[0216] Implementation Method 1

[0217] This embodiment targets non-legacy trigger frames defined for up to 320 MHz bandwidth / channel width.

[0218] (Non-traditional variant common information field)

[0219] It can be based on traditional variant common information fields (e.g. Fig.14 The EHT variant public information field in is used to define the non-traditional variant public information field.

[0220] The non-legacy variant common information field may be used to indicate information of a non-legacy (ie, next version) TB PPDU. In addition, when an A-PPDU is transmitted, that is, when the A-PPDU transmission is triggered / requested by a corresponding non-legacy trigger frame, the non-legacy variant common information field may also indicate information of a legacy TB PPDU (eg, HE TB PPDU / EHT TB PPDU).

[0221] Each subfield of the non-legacy variant common information field may be as follows.

[0222] The Trigger Type subfield can be Fig.14 and can be set to value 0 (i.e., basic trigger type) for triggers such as TB PPDU.

[0223] In addition, the UL Length subfield, More TF subfield, CS Required subfield, and UL BW subfield may be as follows: Fig.14 As defined in .

[0224] In addition, the GI and HE / EHT-LTF type / triggered TXOP sharing mode subfield may include a non-legacy (ie, next version) LTF type indication, and the name of the subfield may be changed accordingly. For example, the subfield may be changed to the GI and HE / EHT / next version-LTF type / triggered TXOP sharing mode subfield, and a different name may be used. The definition of the value of the subfield may be as follows: Fig.14 shown.

[0225] In addition, the HE / EHT-LTF Symbol Quantity subfield may contain the number of non-legacy (i.e., next version) LTF symbols, and the name of the subfield may be changed accordingly. For example, the subfield may be changed to the HE / EHT / Next Version-LTF Symbol Quantity subfield, and a different name may be used. The definition of the value of the subfield may be as follows: Fig.14 or may otherwise be indicated as up to 16.

[0226] In addition, B23 to B25 and B22 or B26 may be additionally utilized / used with respect to the definition of the corresponding subfield values. In this regard, when a non-legacy trigger frame triggers an A-PPDU, the corresponding subfield may only be indicated as up to 8, in which case B22 / B26 may be reserved or used for parameter indication defined in a legacy variant common information field (e.g., HE variant common information field).

[0227] In addition, the LDPC additional symbol segment subfield, AP Tx power subfield, pre-FEC fill factor subfield, PE disambiguation subfield, and UL spatial reuse subfield may be as follows: Fig.14 As defined in .

[0228] In this regard, when a non-legacy (ie, next version) TB PPDU is triggered, 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. 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 a legacy TB PPDU (eg, EHT TB PPDU) is triggered.

[0229] Alternatively, B53 can be Fig.14 Reserved subfields like those in .

[0230] In the present disclosure, B54 and B55 in the non-legacy variant common information field can be used to distinguish which TB PPDU the corresponding non-legacy trigger frame triggers / requests. In this regard, in the legacy variant common information field (e.g., the EHT variant common information field), B54 can correspond to the HE / EHT P160 subfield, and B55 can be a special user information field flag subfield.

[0231] In addition, at least one specific bit included in the non-traditional variant common information field can be defined as an A-PPDU flag subfield, and the subfield can be used to indicate the A-PPDU. In addition, the subfield can be named a non-traditional (ie, next version) P160 subfield, or another name can be used.

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

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

[0234] Regarding the setting / definition of the above-mentioned A-PPDU related subfields, as an example of another reserved bit, one of the bits B22, B26, and B53 may be used. However, considering the A-PPDU case, in terms of information transmission errors that may occur in legacy STAs (e.g., HE STAs), it may be desirable not to use B22, B26, and B53.

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

[0236] In addition, B63 within the non-legacy variant common information field may be a reserved field.

[0237] In the following embodiments, a method for distinguishing various TB PPDUs is specifically proposed.

[0238] [Table 1]

[0239]

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

[0241] Referring to Table 1, Fig.14 The trigger frame defined in the TB PPDU is used to trigger / request various TB PPDUs.

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

[0243] The non-legacy trigger frame (i.e., the next version trigger frame) proposed in the present disclosure may be defined / configured to trigger / request not only the HE TB PPDU, EHT TB PPDU, and P160 HE TB PPDU+S160 EHT TB PPDU in the above examples, but also 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 this regard, the bandwidth actually used in P160 and S160 may be less than or equal to 160 MHz.

[0244] As described above, B54, B55 and A-PPDU flag subfields can be used to distinguish and trigger / request different TBPPDUs through non-legacy trigger frames. In addition, B39 of the user information field can be used to distinguish user information field variants and allocated PPDUs.

[0245] In the present disclosure, when a TB PPDU / TB A-PPDU is triggered based on a non-legacy trigger frame, a bit setting method for each TB PPDU configuration is proposed.

[0246] Hereinafter, specific bit setting methods 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 are proposed.

[0247] First, to trigger / indicate HE TBPPDU, 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 1.

[0248] Next, to trigger / indicate the EHT TBPPDU, B54 may be set to 0, B55 may be set to 0, and the A-PPDU Flag subfield may be set to 1. In addition, the PHY Version Identifier subfield in the Special User Information field (e.g., the EHT Variant Special User Information field) may indicate EHT.

[0249] Next, to trigger / indicate P160 HE TB PPDU+S160 EHT TB PPDU, B54 is set to a value of 1, B55 is set to a value of 0, and the A-PPDU Flag subfield may be set to a value of 1 or a value of 0. In addition, the PHY Version Identifier subfield in the Special User Information field (e.g., the EHT Variant Special User Information field) may indicate EHT.

[0250] In this regard, it may be desirable that the A-PPDU Flag subfield be defined as a value of 1. In addition, B39 of the User Information field may be used to distinguish variants of the User Information field, and B39 set to a value of 0 may indicate a HE variant, and B39 set to a value of 1 may indicate an EHT variant.

[0251] With respect to the aforementioned TBPPDU configuration, when decoding the trigger frame, (any) non-legacy (ie, next version) STA may interpret it as a legacy trigger frame (eg, Fig.14 In this case, the above TB PPDU configuration may not be a problem because it is not related to non-legacy TB PPDU.

[0252] Next, to trigger / indicate a non-legacy TB PPDU, B54 may be set to 0, B55 may be set to 1, and the A-PPDU Flag subfield may be set to 1.

[0253] This setting is not used in legacy trigger frames. Therefore, when decoding such a trigger frame, (any) non-legacy STA may interpret it as a non-legacy trigger frame (ie, an enhanced trigger frame).

[0254] This approach may be desirable from a power saving perspective for legacy STAs (eg, EHT STAs).

[0255] Additionally, there may be non-legacy variant special user information fields.

[0256] 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 Flag subfield may be set to a value of 1. Additionally, the PHY Version Identifier subfield within the Special User Information field (e.g., Non-Legacy Variant Special User Information field) may indicate non-legacy (i.e., next version).

[0257] This setting is the same as the method of triggering the EHT TB PPDU described above, but the PHY version identifier subfield of the special user information field can be used to distinguish.

[0258] This method may require additional time for the non-legacy STA to recognize that the non-legacy TB PPDU is a trigger frame, but has the advantage of reducing complexity because it maintains the existing design method. From the perspective of power saving of the legacy STA (eg, EHT STA), this method may be undesirable.

[0259] Additionally, there may be non-legacy variant special user information fields.

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

[0261] This setting is not used in legacy trigger frames. Therefore, when decoding such a trigger frame, (any) non-legacy STA may interpret it as a non-legacy trigger frame (ie, an enhanced trigger frame).

[0262] In this setting, EHT STAs cannot be assigned to HE TB PPDUs, which may result in low channel utilization.

[0263] For HE STA, B54, B55 and A-PPDU flag subfields are bits corresponding to the ULHE-SIG-A2 reserved subfield, so HE STA can ignore the corresponding settings, and it may be possible to allocate HE TB PPDU to HE STA.

[0264] The variants of the user information field may be distinguished by using B39 of the user information field, and B39 set to a value of 0 may indicate an HE variant, and B39 set to a value of 1 may indicate a non-legacy variant.

[0265] Additionally, there may be non-legacy variant special user information fields.

[0266] Alternatively, for HE TB PPDU allocation to EHT STA, in order to trigger / indicate 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 1, and the A-PPDU Flag subfield may be set to a value of 0.

[0267] Since the A-PPDU Flag subfield is set to a value of 0 in the corresponding setting, when decoding the corresponding trigger frame, (all) non-legacy STAs may interpret it as a non-legacy trigger frame (ie, an enhanced trigger frame).

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

[0269] The variants of the user information field may be distinguished by using B39 of the user information field, and B39 set to a value of 0 may indicate an HE variant, and B39 set to a value of 1 may indicate a non-legacy variant.

[0270] Additionally, there may be non-legacy variant special user information fields.

[0271] Alternatively, to trigger / indicate 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 Flag subfield may be set to a value of 0 or 1. In addition, the PHY Version Identifier subfield in the Special User Information field (e.g., Non-Legacy Variant Special User Information field) may indicate non-legacy (i.e., next version).

[0272] This setting is the same as the method of triggering the above-mentioned P160 HE TB PPDU+S160 EHT TB PPDU, but can be distinguished using the PHY version identifier subfield of the special user information field.

[0273] This method may require additional time for the non-legacy STA to recognize that the P160 HE TB PPDU+S160 non-legacy TB PPDU is a trigger frame, but has the advantage of reducing complexity while maintaining the existing design method. In the case of this method, the EHT STA can be assigned to the HE TB PPDU and perform transmission, but errors may occur depending on the implementation because there is no EHT variant special user information field.

[0274] Additionally, there may be non-legacy variant special user information fields.

[0275] Next, to trigger / indicate P160 EHT TB PPDU+S160 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 Flag subfield may be set to a value of 0.

[0276] Since the A-PPDU Flag subfield is set to a value of 0 in the corresponding setting, when decoding the corresponding trigger frame, (all) non-legacy STAs may interpret it as a non-legacy trigger frame (ie, an enhanced trigger frame).

[0277] The EHT STA may interpret the trigger frame to trigger an EHT TB PPDU on all channels. In this regard, since only non-legacy STAs will be allocated for S160, this interpretation may not be a problem.

[0278] The variants of the user information field may be distinguished by using B39 of the user information field, and B39 set to a value of 0 may indicate an EHT variant, and B39 set to a value of 1 may indicate a non-legacy variant.

[0279] Additionally, there may be non-legacy variant special user information fields.

[0280] Regarding the bit settings for triggering / indicating each TB PPDU configuration described above, the bit settings in Table 2 below may be a preferred method.

[0281] [Table 2]

[0282] TB PPDU Configuration Bit Setting HE TB PPDU B54:1,B55:1,A-PPDU flag:1 EHT TB PPDU B54:0,B55:0,A-PPDU flag:1 P160HE TB PPDU+S160 EHT TB PPDU B54:1,B55:0,A-PPDU flag:1 Non-traditional TB PPDU B54:0,B55:1,A-PPDU flag:1 P160HE TB PPDU+S160 non-traditional TB PPDU B54:1,B55:1,A-PPDU flag:0 P160EHT TB PPDU+S160 non-traditional TB PPDU B54:0,B55:0,A-PPDU flag:0

[0283] Regarding Table 2, B54 set to a value of 1 may indicate that the HE TB PPDU is located at the primary 160 MHz, and B54 set to a value of 0 may indicate that the EHT TB PPDU or the non-legacy (ie, next version) TB PPDU is located at the primary 160 MHz. That is, the meaning of B54 in the next generation wireless LAN system (eg, next version WiFi system) may be modified as described above.

[0284] In addition, B55 set to a value of 1 may indicate that there is no EHT variant special user information field, and B55 set to a value of 0 may indicate that there is an EHT variant special user information field. B55 may not be related to the presence of a non-legacy variant special user information field (e.g., a UHR variant special user information field). That is, in a next-generation wireless LAN system (e.g., a next-generation WiFi system), the meaning of B55 may be the same as in EHT.

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

[0286] Additionally, in this regard, even if the non-legacy variant special user information field flag subfield does not exist, the presence of the non-legacy variant special user information field (eg, UHR variant special user information field) may be implicitly indicated.

[0287] Information for triggering a non-legacy TB PPDU or an A-PPDU including a non-legacy TB PPDU may be sent in the non-legacy variant common information field and the non-legacy variant special user information field. In addition, whether the non-legacy variant special user information field exists may be indicated in the non-legacy variant common information field.

[0288] In this regard, a non-legacy variant special user information field flag subfield may be defined / used for this indication.

[0289] For example, this subfield may consist of one bit (e.g., B57) excluding the A-PPDU flag subfield from B56 to B62 of the non-legacy variant common information field. This subfield set to a value of 0 may indicate that the non-legacy variant special user information field exists, and this subfield set to a value of 1 may indicate that the non-legacy variant special user information field does not exist. As examples of other reserved bits, B22, B26, or B53 may be used, but when considering A-PPDU, the HE STA may have an information transmission error, and therefore it may be desirable not to use B22, B26, or B53.

[0290] Alternatively, as described above, the non-legacy variant special user information field flag subfield may be unnecessary. Since the non-legacy STA can distinguish between TB PPDUs triggered by B54, B55, and A-PPDU flag subfields, it can only use this information to determine the presence of the non-legacy variant special user information field (i.e., an implicit indication).

[0291] (Non-traditional variant special user information field)

[0292] It can be based on traditional special user information fields (for example, Fig.14 Special user information fields in the definition of non-traditional variant special user information fields.

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

[0294] If there is a non-legacy variant special user information field, the field may be located after the non-legacy common information field. If there is a legacy special user information field (e.g., an EHT variant special user information field) in the trigger frame, the legacy special user information field may be located after the non-legacy common information field, and then the non-legacy variant special user information field may be located thereafter.

[0295] Each subfield of the non-legacy variant special user information field may be as follows.

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

[0297] Additionally, the PHY version identifier subfield may indicate non-legacy (ie, next version).

[0298] Additionally, the UL bandwidth extension subfield may indicate up to 320 MHz bandwidth together with the UL BW subfield, and a reserved value may also be used to indicate additional bandwidth.

[0299] In addition, the EHT spatial reuse 1 / 2 subfield may be renamed as a non-legacy spatial reuse 1 / 2 subfield and defined in the same manner as before.

[0300] In addition, the U-SIG Ignore and Verify subfields may be set to the value of the setting applied to the value of the U-SIG Ignore / Verify field of the non-legacy TB PPDU. Depending on the Ignore / Verify field defined in the (actual) non-legacy TB PPDU, only some bits may be used, or some or all bits of the reserved subfields of B37 to B39 may be used in addition.

[0301] When triggering / requesting 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 exist. Alternatively, if the contents are almost the same, only the non-legacy variant special user information field may exist.

[0302] In this case, the AID12 subfield should be set to 2007, and the EHT STA can interpret the non-legacy variant special user information field as if it is an EHT variant special user information field based on the legacy definition. On the other hand, the non-legacy STA can interpret the non-legacy variant special user information field based on the new definition.

[0303] In this regard, the PHY version identifier subfield needs to be set to EHT, but non-legacy STAs may interpret it based on the new definition. However, since non-legacy STAs may be assigned to the EHT TB PPDU part, the implementation complexity may be high because both interpretations should be possible.

[0304] (Non-traditional variant user information field)

[0305] It can be based on traditional user information fields (e.g. Fig.14 The EHT variant user information field in is used to define the non-traditional variant user information field.

[0306] The non-legacy variant user information field may be used to indicate information of users assigned to non-legacy TB PPDU transmissions.

[0307] The non-legacy variant user information field may be located after the non-legacy variant special user information field. If the legacy user information field (e.g., HE / EHT variant user information field) is present in the trigger frame, the legacy user information field (e.g., HE / EHT variant user information field) may be located after the non-legacy variant special user information field, and the non-legacy variant user information field may be located thereafter.

[0308] Each subfield of the non-legacy variant user information field may be as follows.

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

[0310] In addition, the RU allocation subfield indicates RU allocation information, and the definition of the existing RU allocation subfield may be used as it is, or some RU allocation information may be changed / added / excluded.

[0311] Additionally, the UL FEC Coding Type subfield may be defined in the same manner as before.

[0312] In addition, the UL EHT-MCS subfield may be renamed as the UL non-legacy MCS subfield (a different name may be used), may be defined in the same manner as before, or some MCSs may be changed / added / excluded.

[0313] Additionally, the reserved subfields may be maintained in the same manner as before.

[0314] Additionally, the SS allocation subfield may be defined in the same manner as before, or alternatively, up to 16 additional streams may be indicated.

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

[0316] In addition, the PS160 subfield can be used together with the RU allocation subfield to indicate RU allocation information. Specifically, this subfield can indicate information about whether the RU is in P160 or S160. Thus, the variant information of the user information field can be indicated in the case of A-PPDU.

[0317] Implementation Method 2

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

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

[0320] (Bandwidth indication method)

[0321] In the existing wireless LAN system, a method of indicating a bandwidth up to 320 MHz is defined using a UL BW subfield of an EHT variant common information field and a UL BW extension subfield of a special user information field, and some combinations of values ​​therein are reserved.

[0322] In the trigger frame of the next generation wireless LAN system (ie, the above non-legacy trigger frame), the same method as above can be used to indicate a bandwidth up to 320 MHz. In addition, a specific reserved value can be used to indicate a wider bandwidth.

[0323] That is, a bandwidth of up to 320 MHz can be indicated by using the same combination of values ​​as before, 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 can be indicated by the following combination of various reserved bits.

[0324] Depending on channelization, there may be only one 480MHz / 640MHz, or there may be various types such as 320-1MHz / 320-2MHz. The method proposed in the present disclosure is explained on the assumption that a specific channel type is defined.

[0325] Hereinafter, a method for indicating a 480 MHz / 640 MHz bandwidth according to a proposal of the present disclosure is exemplified.

[0326] 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 an example, other combinations of these values ​​may follow existing indication methods.

[0327] 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 an example, other combinations of these values ​​may follow the existing indication method.

[0328] 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 an example, other combinations of these values ​​may follow the existing indication method.

[0329] 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 an example, other combinations of these values ​​may follow existing indication methods.

[0330] 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 an example, other combinations of these values ​​may follow existing indication methods.

[0331] 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 ULBW 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 ULBW extension subfield may be set to a value of 2. To indicate a 640-3 MHz bandwidth, the ULBW subfield may be set to a value of 1 / 2, and the ULBW extension subfield may be set to a value of 3. In an example, other combinations of these values ​​may follow the existing indication method.

[0332] For example, to indicate a 480-1 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 480-2 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 2. 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 an example, other combinations of these values ​​may follow existing indication methods.

[0333] For example, to indicate a 480-1 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 480-2 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 2. 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 an example, other combinations of these values ​​may follow the existing indication method.

[0334] For example, to indicate a 480-1 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 480-2 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 2. 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 combinations of these values ​​may follow existing indications.

[0335] For example, to indicate a 480-1 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 480-2 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 2. To indicate a 480-3 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 3. 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 an example, other combinations of these values ​​may follow the existing indication method.

[0336] For example, to indicate a 480-1 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 480-2 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 2. To indicate a 480-3 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 3. 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 combinations of these values ​​may follow existing indications.

[0337] For example, to indicate a 480-1 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 480-2 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 2. To indicate a 480-3 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 3. 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 combinations of these values ​​may follow the existing indication method.

[0338] 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 combinations of these values ​​may follow the existing indication method.

[0339] 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 combinations of these values ​​may follow the existing indication method.

[0340] For example, to indicate a 480-1 MHz bandwidth, the ULBW subfield may be set to a value of 0 / 1 / 2, and the ULBW extension subfield may be set to a value of 1. To indicate a 480-2 MHz bandwidth, the ULBW 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 480-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 an example, other combinations of these values ​​may follow existing indication methods.

[0341] 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 combinations of these values ​​may follow the existing indication method.

[0342] 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 combinations of these values ​​may follow the existing indication method.

[0343] 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 an example, other combinations of these values ​​may follow existing indication methods.

[0344] Regarding the above-mentioned proposed method, when triggering the TB A-PPDU of the EHT TB PPDU and the non-legacy TB PPDU, not only the non-legacy special user information field must exist, but also the legacy special user information field (specifically, the ULBW extension subfield within the field) must exist. This is because it is necessary to indicate not only the bandwidth of the non-legacy TB PPDU but also the bandwidth of the EHT TB PPDU, and the combination of values ​​in the above-mentioned proposed method may not indicate the bandwidth to the EHT TB PPDU.

[0345] Additionally or alternatively, for bandwidth indication, the method may be considered to indicate the additional bandwidth by using one or more bits (e.g., B37 to B39) corresponding to the reserved subfield of the existing special user information field in the non-legacy variant special user information field. 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 may use the existing indication method.

[0346] When the bandwidth is indicated using corresponding bits (eg, B37 to B39), the bandwidth may be indicated independently. Alternatively, in this case, the additional bandwidth may be indicated using a combination of the value of the UL BW subfield, the value of the UL BW extension subfield, and the corresponding bit value as in the existing method.

[0347] When the additional bit as described above is used, when triggering the TB A-PPDU of the EHT TB PPDU and the non-legacy TB PPDU, only the non-legacy special user information field may exist. In this case, the EHT STA may interpret the non-legacy special user information field as the existing special user information field. On the other hand, the non-legacy STA may interpret the non-legacy special user information field according to the newly defined method.

[0348] Therefore, this method can indicate the bandwidth of both the EHT TB PPDU and the non-legacy TB PPDU. In this case, the PHY version identifier subfield needs to be set to EHT, but the non-legacy STA can interpret it based on the new definition. However, since the non-legacy STA may be assigned to the EHT TB PPDU part, both interpretations need to be possible, which may increase the implementation complexity.

[0349] (Various TB PPDU differentiation methods)

[0350] In order to distinguish between TB PPDUs of 480 MHz / 640 MHz bandwidth, the method of triggering / indicating TB PPDU configuration in the above-mentioned embodiment 1 (eg, the bit setting method) may be used.

[0351] Additionally, the various bit combinations described below may be considered to indicate specific channels in various situations considering a wider bandwidth (ie, 480 MHz / 640 MHz bandwidth).

[0352] In this regard, it can be assumed that the RU allocation subfield of the non-legacy variant user information field can indicate RU allocation information within a 160MHz unit. In this case, the subfield can exceptionally indicate some large RU / MRU corresponding to channels exceeding 160MHz. Therefore, with respect to specific channel indication, a method of indicating at least a 160MHz channel can be considered.

[0353] In the following, detailed bit setting methods 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) P160EHT TB PPDU+(S160 non-legacy TB PPDU)+S320 / SS160 non-legacy TB PPDU, and v) P160 HETB PPDU+S160 EHT TB PPDU+S320 / SS160 non-legacy TB PPDU are proposed.

[0354] First, to trigger / indicate a non-legacy TB PPDU, B54 of the non-legacy variant common information field may be set to a value of 0, B55 may be set to a value of 1, 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 value of 0, B55 may be set to a value of 0, the A-PPDU flag subfield may be set to a value of 1, and the PHY version identifier subfield in a special user information field (e.g., a non-legacy special user information field) may be set to indicate non-legacy.

[0355] In this regard, the non-legacy TBPPDU bandwidth indication may be performed 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. That is, the above-mentioned bandwidth indication method may be used.

[0356] Using a combination of B39 and B25 of the non-legacy variant user information field, indicating up to 640 MHz may be possible.

[0357] In the following example, 160 and 320 may represent 160 MHz band / channel and 320 MHz band / channel, respectively. In addition, lower 160 / 320 and upper 160 / 320 may represent 160 / 320 in a relatively low frequency band in the frequency domain and 160 / 320 in a relatively high frequency band in the frequency domain, respectively.

[0358] For example, a value of 0 in B25 may indicate P 320 (or lower 320 ), and a value of 1 in B25 may indicate S 320 (or upper 320 ).

[0359] The combination of a value of 0 for B25 and a value of 0 for B39 may indicate P160. Alternatively, a value of 0 for B25 and a value of 0 for B39 may indicate a lower 160 at P320, or a lower 160 at lower 320, which may not be desirable when considering unification with other situations.

[0360] The combination of a B25 value of 0 and a B39 value of 1 may indicate S 160. Alternatively, a B25 value of 0 and a B39 value of 1 may indicate a higher 160 at P320, or a lower 320 to a higher 160, which may not be desirable when considering integration with other situations.

[0361] The combination of a 1 value of B25 and a 0 value of B39 may indicate a 160 corresponding to the position of P160 in S320. Alternatively, the combination of a 1 value of B25 and a 0 value of B39 may indicate a lower 160 in S320 or a lower 160 in a higher 320, the latter of which may be undesirable when considering integration with other situations.

[0362] The combination of a value of 1 for B25 and a value of 1 for B39 may indicate a 160 corresponding to the position of S160 in S320. Alternatively, a value of 1 for B25 and a value of 1 for B39 may indicate a higher 160 in S320, or a higher 160 in a higher 320, the latter of which may be undesirable when considering integration with other situations.

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

[0364] For example, a combination of a 0 value of B25 and a 0 value of B39 may indicate P160. A combination of a 0 value of B25 and a 1 value of B39 may indicate S160. A combination of a 1 value of B25 and a 1 value (or a 0 value) of B39 may indicate SS160. Alternatively, a combination of a 1 value of B25 and a 0 value of B39 may be retained.

[0365] Alternatively, the following combinations may be used for integration with the case of including HE PPDU. For 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 S160. A 1 value of B25 and a 1 value of B39 may indicate SS160.

[0366] In addition, if only 480MHz of P160+S320 is considered, the following non-legacy variant user information field combination of B25 and B39 can be utilized.

[0367] For example, a combination of a 0 value of B25 and a 0 value (or a 1 value) of B39 may indicate P160. Alternatively, a combination of a 0 value of B25 and a 1 value of B39 may be retained. A combination of a 1 value of B25 and a 0 value of B39 may indicate 160 corresponding to the position of P160 in S320 (or a lower 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 higher 160 in S320).

[0368] Alternatively, the following combinations may be used for integration with the case where the HE TB PPDU is included. For 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 lower 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 higher 160 in S320).

[0369] Next, to trigger / indicate 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 0, B55 may be set to 1, and the A-PPDU flag subfield may be set to 0. Alternatively, to trigger / indicate 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., the non-legacy special user information field) may be set to indicate non-legacy.

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

[0371] 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 can be used to perform A-PPDU bandwidth and non-legacy TB PPDU bandwidth indication. Here, indication can also be performed on only one of the two.

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

[0373] In addition, when only 480MHz of P320+S160 is considered, B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants, and when B39 is set to a value of 1, B25 can be used to distinguish channels.

[0374] For example, a value of 0 in B39 may indicate P160, which may indicate a HE variant user information field (B25 may be a value of 0 or a value of 1). A value of 1 in B39 may indicate S160 or SS160, which may indicate a non-legacy variant user information field. A value of 0 in B25 combined with a value of 1 in B39 may indicate S160, and a value of 1 in B25 combined with a value of 1 in B39 may indicate SS160.

[0375] In addition, when only 480MHz of P160+S320 is considered, B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants, and when B39 is set to a value of 1, B25 can be used to distinguish channels.

[0376] For example, a value of 0 for B39 may indicate P160, which may indicate an HE variant user information field (B25 may be a value of 0 or a value of 1). A value of 1 for B39 may indicate S320 or SS160, which may indicate a non-legacy variant user information field. A combination of a value of 0 for B25 and a value of 1 for B39 may indicate 160 corresponding to the position of P160 in S320 (or a lower 160 in S320). A combination of a value of 1 for B25 and a value of 1 for B39 may indicate 160 corresponding to the position of S160 in S320 (or a higher 160 in S320).

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

[0378] In this regard, the 320 MHz indication may be performed in a UL BW subfield within the non-legacy variant common information field and a UL BW extension subfield within the special user information field (or the non-legacy variant special user information field).

[0379] 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 can be used to perform A-PPDU bandwidth and non-legacy TB PPDU bandwidth indication. Here, indication can also be performed on only one of the two.

[0380] Since B25 in the EHT variant user information field is a reserved bit, it is possible to use B25 and B39 in the user information field to indicate channel locations up to 640 MHz.

[0381] When considering up to 640MHz, a combination of B25 and B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants. Here, EHT STA can be determined using only B39, and non-legacy STA will only be allocated to S320, so there may be no problem.

[0382] For example, a combination of a 0 value of B25 and a 0 value of B39 indicates P160, which may indicate an EHT variant user information field. A combination of a 0 value of B25 and a 1 value of B39 indicates S160, which may indicate an EHT variant user information field. A combination of a 1 value of B25 and a 0 value of B39 indicates 160 corresponding to the position of P160 in S320 (or a lower 160 in S320), which may indicate a non-traditional variant user information field. A combination of a 1 value of B25 and a 1 value of B39 indicates 160 corresponding to the position of S160 in S320 (or a higher 160 in S320), which may indicate a non-traditional variant user information field.

[0383] If only 480MHz up to P320+SS160 is considered, a combination of B25 and B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants. Here, EHT STA can be determined using only B39, and non-legacy STA will only be allocated to SS160, so there may be no problem.

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

[0385] Alternatively, the following combinations may be used for integration with the case of including the HE TBPPDU. For example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160, which may indicate an EHT variant user information field. A 0 value of B25 and a 1 value of B39 may indicate S160, which may indicate an EHT variant user information field. A combination of a 1 value of B25 and a 1 value of B39 may indicate SS160, which may indicate a non-legacy variant user information field.

[0386] In addition, in the following case where only P160 is an EHT TB PPDU, 480 MHz of P160+S320 may be considered.

[0387] Next, to trigger / indicate 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 0 value, B55 may be set to 0 value, and the A-PPDU Flag subfield may be set to 0 value.

[0388] In this regard, the 160 MHz indication may be performed in a UL BW subfield within a non-legacy variant common information field and a UL BW extension subfield within a special user information field (or a non-legacy variant special user information field).

[0389] 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 can be used to perform A-PPDU bandwidth and non-legacy TB PPDU bandwidth indication. Here, indication can also be performed on only one of the two.

[0390] Since B25 in the EHT variant user information field is a reserved bit, it is possible to use B25 and B39 in the user information field to indicate channel locations up to 640 MHz.

[0391] When considering up to 640MHz, a combination of B25 and B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants. Here, EHT STA can be determined using only B39, and non-legacy STA will only be allocated to S160 and S320, so there may be no problem.

[0392] For example, a combination of a 0 value of B25 and a 0 value of B39 may indicate P160, which may indicate an EHT variant user information field. A combination of a 0 value of B25 and a 1 value of B39 may indicate S160, which may indicate a non-traditional variant user information field. A combination of a 1 value of B25 and a 0 value of B39 may indicate 160 corresponding to the position of P160 in S320 (or a lower 160 in S320), which may indicate a non-traditional 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 higher 160 in S320), which may indicate a non-traditional variant user information field.

[0393] If only 480MHz up to P320+SS160 is considered, a combination of B25 and B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants. Here, EHT STA can be determined using only B39, and non-legacy STA will only be allocated to S160, SS160, so there may be no problem.

[0394] For example, a combination of a 0 value of B25 and a 0 value of B39 may indicate P160, which may indicate an EHT variant user information field. A combination of a 0 value of B25 and a 1 value of B39 may indicate S160, which may indicate a non-traditional variant user information field. A combination of a 1 value of B25 and a 1 value (or a 0 value) of B39 may indicate SS160, which may indicate a non-traditional variant user information field. Alternatively, a combination of a 1 value of B25 and a 0 value of B39 may be retained.

[0395] Alternatively, the following combinations may be used for integration with the case of including an HE TB PPDU. For example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160, which may indicate an EHT variant user information field. A 0 value of B25 and a 1 value of B39 may indicate S160, which may 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, which may indicate a non-legacy variant user information field.

[0396] If only 480MHz up to P160+S320 is considered, a combination of B25 and B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variants. Here, EHT STA can be determined using only B39, and non-legacy STA will only be allocated to S320, so there may be no problem.

[0397] For example, a combination of a 0 value of B25 and a 0 value of B39 indicates P160, which may indicate an EHT variant user information field. A combination of a 0 value of B25 and a 1 value of B39 is reserved and may indicate a non-traditional variant user information field. A combination of a 1 value of B25 and a 0 value of B39 indicates 160 corresponding to the position of P160 in S320 (or a lower 160 in S320), and may indicate a non-traditional variant user information field. A combination of a 1 value of B25 and a 1 value of B39 indicates 160 corresponding to the position of S160 in S320 (or a higher 160 in S320), and may indicate a non-traditional variant user information field.

[0398] Alternatively, the following combinations may be used for integration with the case where the HE TB PPDU is included. For example, a 0 / 1 value of B25 and a 0 value of B39 may indicate P160, which may 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 lower 160 in S320), which may 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 higher 160 in S320), which may indicate a non-legacy variant user information field.

[0399] Next, to trigger / indicate 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 1, B55 may be set to 0, and the A-PPDU flag subfield may be set to 0.

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

[0401] The 320 MHz indication or the EHT TB PPDU bandwidth (160 MHz) indication may be performed 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).

[0402] 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 can be used to perform A-PPDU bandwidth and non-legacy TB PPDU bandwidth indication. Here, indication can also be performed on only one of the two.

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

[0404] If only 480MHz of P320+SS160 is considered, a combination of B25 and B39 of the user information field can be used to distinguish channels, PPDUs, and user information field variations. Here, EHT STA can be determined using only B39, and non-legacy STA will only be allocated to SS160, so there may be no problem.

[0405] For example, a combination of a 0 / 1 value of B25 and a 0 value of B39 may indicate P160, which may indicate an HE variant user information field. A combination of a 0 value of B25 and a 1 value of B39 may indicate S160, which may indicate an EHT variant user information field. A combination of a 1 value of B25 and a 1 value of B39 may indicate SS160, which may indicate a non-legacy variant user information field.

[0406] In addition, the 480MHz of P160+S320 may not be considered. This case may be the same as the P160 HE TB PPDU+S320 non-legacy TB PPDU case.

[0407] Fig.16 is a flowchart for illustrating the operation of a STA based on a trigger frame according to the present disclosure.

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

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

[0410] For example, the STA may receive a trigger frame associated with a trigger of a non-legacy TB PPDU (eg, a TB PPDU of a subsequent version of EHT). The trigger frame may include a non-legacy common information field.

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

[0412] For example, a value of 0 in the A-PPDU-related subfield indicates an A-PPDU containing a non-legacy TB PPDU, and a value of 1 in the A-PPDU-related subfield may include at least one of a non-A-PPDU or an A-PPDU that does not contain a non-legacy TB PPDU (i.e., an A-PPDU constructed only with a legacy TB PPDU).

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

[0414] In this regard, the configuration of 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.

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

[0416] For example, a value of 1 for B54 may indicate that the primary 160 MHz channel is allocated to HE (High Efficiency) TB PPDU, and a value of 0 for B54 may indicate that the primary 160 MHz channel is allocated to EHT (Extremely High Throughput) TB PPDU or non-legacy TB PPDU.

[0417] For example, the above-mentioned 0 value and 1 value of B55 can be associated with the existence of a non-legacy variant special user information field (e.g., flag information).

[0418] For example, if B54 is set to a value of 1, B55 is set to a value of 1, and the A-PPDU related subfield is set to a value of 1, one or more TB PPDUs may correspond to HE (High Efficiency) TB PPDUs. That is, in this case, the trigger frame in step S1610 may be a trigger frame for triggering / requesting HE TB PPDUs.

[0419] For example, if B54 is set to a value of 0, B55 is set to a value of 0, and the A-PPDU related subfield is set to a value of 1, one or more TB PPDUs may correspond to EHT (Extremely High Throughput) TB PPDUs. That is, in this case, the trigger frame in step S1610 may be a trigger frame for triggering / requesting an EHT TB PPDU.

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

[0421] For example, if B54 is set to a value of 0, B55 is set to a value of 1, and the A-PPDU related subfield is set to a value of 1, one or more TB PPDUs may correspond to non-legacy TB PPDUs. 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 a version after EHT).

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

[0423] For example, if B54 is set to a value of 0, B55 is set to a value of 0, and the A-PPDU related subfield is set to a value of 0, 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 constructed with a P160 EHT TB PPDU + an S160 non-legacy TB PPDU).

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

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

[0426] Fig.16 The method performed by the STA described in the example of Figure 1 The first device (100) performs. For example, Figure 1 The one or more processors (102) of the first device (100) may be configured to: receive a trigger frame including a common information field from the AP (200) through one or more transceivers (106); and send a TB PPDU corresponding to one of the one or more TB PPDUs triggered by the trigger frame to the AP (200). In addition, the one or more memories (104) of the first device (100) may store instructions for executing when executed by the one or more processors (102). Fig.16 The examples describe the methods in the commands.

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

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

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

[0430] For example, a value of 0 in the A-PPDU-related subfield indicates an A-PPDU containing a non-legacy TB PPDU, and a value of 1 in the A-PPDU-related subfield may include at least one of a non-A-PPDU or an A-PPDU that does not contain a non-legacy TB PPDU (i.e., an A-PPDU constructed only with a legacy TB PPDU).

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

[0432] In this regard, the configuration of 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.

[0433] The specific details of at least one other subfield included in the common information field, the trigger / request / indication for one or more TB PPDU configurations, and the trigger frame are the same as those described above with reference to Fig.16 Those described are the same, so redundant description is omitted.

[0434] Depend on Fig.17 The method performed by the AP described in the example may be performed by Figure 1 The second device (200) is executed. For example, Figure 1 The one or more processors (202) of the second device (200) may be configured to send a trigger frame including a common information field to the STA (100) through the one or more transceivers (206), and receive a TB PPDU corresponding to one of the one or more TB PPDUs triggered by the trigger frame from the STA (100). In addition, the one or more memories (204) of the second device (200) may store a method for executing the method when executed by the one or more processors (202). Fig.17 The examples describe the methods in the commands.

[0435] As described above, compared with the trigger frame for triggering TB PPDU (e.g., HE TB PPDU, EHT TB PPDU) in the existing wireless LAN system, the trigger frame proposed in the present disclosure has new features, which also include information for triggering a new version (e.g., the next version of EHT, UHR) of TB PPDU and an aggregated PPDU (A-PPDU).

[0436] By supporting triggering / requesting for A-PPDU as well as the new version of TB PPDU via the trigger frame proposed in the present disclosure, throughput and efficiency aspects in a wireless LAN system may be enhanced.

[0437] The above-mentioned embodiments are to combine the elements and features of the present disclosure in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be considered as optional. Each element or feature can be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure may include combined partial elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, the embodiments may include claims that do not have a clear reference relationship in the combined claims, or may be included as new claims by modification after application.

[0438] It is clear to those skilled in the relevant art that the present disclosure can be implemented in other specific forms within the scope of the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present disclosure should be determined by the reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0439] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in a device or computer according to the methods of various embodiments, and non-transitory computer-readable media that enable software or commands, etc. to be stored and executable in a device or computer. Commands that can be used to program a processing system that performs the features described in the present disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in the present disclosure can be implemented by using a computer program product that includes such a storage medium. The storage medium may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, but is not limited thereto, and it 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 located away from the processor. The memory, or alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system, and may be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results from the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0440] Industrial Applicability

[0441] The method proposed in the present disclosure is mainly described based on an example applied to a system based on IEEE 802.11 (5G system), but can be applied to various WLAN or wireless communication systems other than the system based on IEEE 802.11.

Claims

1. A method performed by a station (STA) in a wireless LAN system, the method The following steps are involved: receiving a trigger frame including a common information field from an access point (AP); as well as sending, to the AP, a trigger-based physical layer protocol data unit (TB PPDU) corresponding to one of the one or more TB PPDUs triggered by the trigger frame, The common information field includes an aggregated PPDU (A-PPDU) related subfield, and The 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. The method according to claim 1, in, A value of 0 in the A-PPDU-related subfield indicates an A-PPDU containing a non-legacy TB PPDU, and The value 1 of 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. The method according to claim 1, in, The at least one other subfield includes B54 and B55 within the common information field.

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

5. The method according to claim 3, in, The B55 values ​​of 0 and 1 are associated with the presence of a non-legacy variant special user information field.

6. The method according to claim 3, in, 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 subfield being set to a value of 1, the one or more TB PPDUs correspond to a HE TB PPDU.

7. The method according to claim 3, in, 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 subfield being set to a value of 1, the one or more TB PPDUs correspond to an EHT TB PPDU.

8. The method according to claim 3, in, 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 subfield being set to a value of 1, the one or more TB PPDUs correspond to a HE TB PPDU and an EHT TB PPDU.

9. The method according to claim 3, in, 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 subfield being set to a value of 1, the one or more TB PPDUs correspond to non-legacy TB PPDUs.

10. The method according to claim 3, in, 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 subfield being set to a value of 0, the one or more TB PPDUs correspond to a HE TB PPDU and a non-legacy TB PPDU.

11. The method according to claim 3, in, 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 subfield being set to a value of 0, the one or more TB PPDUs correspond to an EHT TB PPDU and a non-legacy TB PPDU.

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

13. The method according to claim 1, in, The trigger frame includes at least one of a special user information field related to information on a non-legacy TB PPDU or a user information field related to information on a STA assigned to transmission of the non-legacy TB PPDU.

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

15. A station (STA) device operating in a wireless local area network (WLAN) system, the device include: at least one transceiver; as well as at least one processor coupled to the at least one transceiver, Wherein, the at least one processor is configured to: receiving a trigger frame including a common information field from an access point (AP); and sending, to the AP, a trigger-based physical layer protocol data unit (TB PPDU) corresponding to one of the one or more TB PPDUs triggered by the trigger frame, The common information field includes an aggregated PPDU (A-PPDU) related subfield, and The 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. A processing unit configured to control a station (STA) in a wireless local area network (WLAN) system, the processing unit include: at least one processor; as well as At least one computer memory, the at least one computer memory being operatively connected to the at least one processor and storing instructions for executing the method according to any one of claims 1 to 12 upon being executed by the at least one processor.

17. At least one non-transitory computer readable medium storing at least one instruction, in, The at least one instruction is executed by at least one processor to control a station (STA) device to perform the method according to any one of claims 1 to 12 in a wireless local area network (WLAN) system.

18. A method performed by an access point (AP) in a wireless LAN system, the method The following steps are involved: Sending a trigger frame including a common information field to a station (STA); as well as receiving, from the STA, a trigger-based physical layer protocol data unit (TB PPDU) corresponding to one of the one or more TB PPDUs triggered by the trigger frame, The common information field includes an aggregated PPDU (A-PPDU) related subfield, and The 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 local area network (WLAN) system, the device include: at least one transceiver; as well as at least one processor coupled to the at least one transceiver, Wherein, the at least one processor is configured to: sending a trigger frame including a common information field to a station (STA); and receiving, from the STA, a trigger-based physical layer protocol data unit (TB PPDU) corresponding to one of the one or more TB PPDUs triggered by the trigger frame, The common information field includes an aggregated PPDU (A-PPDU) related subfield, and The 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