Method and apparatus for aggregated ppdu transmission and reception in wireless lan system

Abstract

A method and apparatus for aggregated PPDU transmission and reception in a wireless LAN system are disclosed. The method according to an embodiment of the disclosure can include the steps of: receiving, by a STA, a trigger frame from an AP, the trigger frame being for triggering transmission of an A-PPDU in which a first type of PPDU and a second type of PPDU are aggregated in a frequency domain; and transmitting, by the STA, the A-PPDU to the AP.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for transmitting and receiving Polymer Protocol Data Units (A-PPDUs) in a Wireless Local Area Network (WLAN) system. Background Technology

[0002] New technologies have been introduced for Wireless LANs (WLANs) to improve transmission rates, increase bandwidth, enhance reliability, reduce errors, and decrease latency. Within WLAN technology, the IEEE 802.11 series of standards can be referred to as Wi-Fi. For example, recent technologies introduced into WLAN include the Ultra High Throughput (VHT) enhancement of the 802.11 ac standard and the High Efficiency (HE) enhancement of the IEEE 802.11 ax standard.

[0003] To provide a more advanced wireless communication environment, improved techniques for Extremely High Throughput (EHT) are being discussed. For example, techniques for MIMO and multiple access point (AP) coordination that support increased bandwidth, efficient use of multiple frequency bands, and increased spatial flow are being investigated. Specifically, various techniques are being explored to support low-latency or real-time services. Furthermore, new technologies to support Ultra-High Reliability (UHR), including improvements or extensions to EHT techniques, are being discussed. Summary of the Invention

[0004] Technical issues

[0005] The technical objective of this disclosure is to provide a method and apparatus for transmitting and receiving A-PPDUs, which are generated by aggregating PPDUs of different versions / types / formats in the frequency domain.

[0006] The technical objectives to be achieved by this disclosure are not limited to those described above, and other technical objectives not described herein will be clearly understood by those skilled in the art from the following description.

[0007] Technical solution

[0008] A method according to one aspect of this disclosure may include: a station (STA) receiving a trigger frame from an access point (AP) that triggers the transmission of aggregated Protocol Data Units (A-PPDUs), wherein a first type of PPDU and a second type of PPDU are aggregated in the A-PPDU in the frequency domain; and the STA transmitting the A-PPDU to the AP. The trigger frame may separately include a first special user information field and a second special user information field, the first special user information field including information for the first type of PPDU, and the second special user information field including information for the second type of PPDU.

[0009] The method according to an additional aspect of this disclosure may include: sending a trigger frame from an access point (AP) to a station (STA) that triggers the transmission of aggregated Protocol Data Units (A-PPDUs), wherein a first type of PPDU and a second type of PPDU are aggregated in the A-PPDU in the frequency domain; and receiving the A-PPDU from the STA by the AP. The trigger frame may separately include a first special user information field and a second special user information field, the first special user information field including information for the first type of PPDU, and the second special user information field including information for the second type of PPDU.

[0010] Beneficial effects

[0011] According to embodiments of this disclosure, by transmitting and receiving A-PPDUs generated by aggregating different versions / types / formats of PPDUs in the frequency domain, latency can be reduced, thereby improving the efficiency of wireless communication.

[0012] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand other effects not described herein through the following description. Attached Figure Description

[0013] The accompanying drawings, which are included as part of the detailed description of this disclosure, provide embodiments of the disclosure and, together with the detailed description, describe the technical features of the disclosure.

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

[0015] Figure 2 This is a diagram illustrating an exemplary structure of a WLAN system to which this disclosure can be applied.

[0016] Figure 3 This is a diagram used to illustrate the link establishment process that can be applied to this disclosure.

[0017] Figure 4 This is a diagram used to illustrate the backoff processing that can be applied to this disclosure.

[0018] Figure 5 This is a diagram illustrating the CSMA / CA-based frame transmission operation that can be applied to this disclosure.

[0019] Figure 6 This is a diagram illustrating an example of a frame structure that can be used in a WLAN system to which this disclosure may be applied.

[0020] Figure 7 This is a diagram illustrating an example of a PPDU as defined in the IEEE 802.11 standard of this disclosure.

[0021] Figure 8 This is a diagram illustrating an exemplary format of the trigger frame to which the present disclosure may be applied.

[0022] Figure 9 This is a diagram illustrating the format of a common information field in a trigger frame to which this disclosure may be applied.

[0023] Figure 10 The special user information field for the trigger frame to which this disclosure can be applied is shown.

[0024] Figure 11 This is a diagram illustrating an example of a resource unit applicable to a wireless LAN system according to the present disclosure.

[0025] Figure 12 This is a diagram illustrating an example of a resource unit applicable to a wireless LAN system according to the present disclosure.

[0026] Figure 13 This is a diagram illustrating an example of a resource unit applicable to a wireless LAN system according to the present disclosure.

[0027] Figure 14 This is a diagram illustrating a polymerized PPDU according to an embodiment of the present disclosure.

[0028] Figure 15 The UHR PPDU format according to an embodiment of the present disclosure is shown.

[0029] Figure 16 Operation of a non-APSTA apparatus for a method of aggregating PPDU transmission and reception according to one embodiment of the present disclosure is shown.

[0030] Figure 17 Operation of an AP device for a method of aggregating PPDU transmission and reception according to one embodiment of the present disclosure is shown. Detailed Implementation

[0031] In the following, embodiments according to this disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of this disclosure and not to represent the only embodiments in which this disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will recognize that this disclosure can be implemented without these specific details.

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

[0033] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0034] In this disclosure, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0035] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of 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” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this disclosure has the same meaning as “and / or”.

[0036] The examples disclosed herein can be applied to various wireless communication systems. For example, the examples disclosed herein can be applied to wireless LAN systems. For example, the examples disclosed herein can be applied to wireless LANs based on the IEEE 802.11a / g / n / ac / ax standards. Furthermore, the examples disclosed herein can be applied to wireless LANs based on the newly proposed IEEE 802.11be (or EHT) standard. The examples disclosed herein can be applied to wireless LANs based on the IEEE 802.11be version 2 standard, corresponding to the additional enhancements of the IEEE 802.11be version 1 standard. Additionally, the examples disclosed herein can be applied to wireless LANs based on next-generation standards following IEEE 802.11be. Furthermore, the examples disclosed herein can be applied to cellular wireless communication systems. For example, it can be applied to cellular wireless communication systems based on 3GPP standards using Long Term Evolution (LTE) technology and 5G New Radio (NR) technology.

[0037] The technical features that can be applied to examples of this disclosure will be described below.

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

[0039] Figure 1 The first device 100 and the second device 200 illustrated herein can be replaced by various terms such as terminal, wireless device, wireless transceiver 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 simply user. Furthermore, the first device 100 and the second device 200 include access point (AP), base station (BS), fixed station, node B, base transceiver system (BTS), and network. It can be replaced by various terms such as artificial intelligence (AI) system, roadside unit (RSU), repeater, router, relay, and gateway.

[0040] Figure 1 The devices 100 and 200 illustrated herein may be referred to as stations (STAs). For example, Figure 1 The devices 100 and 200 illustrated herein may be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA. For example, STA 110 and 200 may perform an access point (AP) role or a non-AP role. That is, in this disclosure, STA 110 and 200 may perform AP and / or non-AP functions. When STA 110 and 200 perform AP functions, they may simply be referred to as APs, and when STA 110 and 200 perform non-AP functions, they may simply be referred to as STAs. Alternatively, in this disclosure, AP may also be referred to as AP STA.

[0041] Reference Figure 1 The first device 100 and the second device 200 can transmit and receive radio signals via various wireless LAN technologies (e.g., IEEE 802.11 series). The first device 100 and the second device 200 may include interfaces for the Media Access Control (MAC) layer and Physical Layer (PHY) conforming to the IEEE 802.11 standard.

[0042] In addition to wireless LAN technology, the first device 100 and the second device 200 can also support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.). Furthermore, the devices disclosed herein can be implemented in various devices such as mobile phones, vehicles, personal computers, augmented reality (AR) devices, and virtual reality (VR) devices. Additionally, the STA of this specification can support various communication services such as voice calls, video calls, data communication, autonomous driving, machine-type communication (MTC), machine-to-machine (M2M), device-to-device (D2D), and IoT (Internet of Things).

[0043] The first device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceivers 106 after generating first information / signal by processing information in the memories 104. Additionally, the processor 102 may receive a wireless signal including second information / signal via the transceivers 106, and then store information obtained through signal processing of the second information / signal in the memories 104. The memories 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memories 104 may store software code including instructions for performing all or part of the processing controlled by the processor 102 or for performing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., IEEE 802.11 series). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0044] The second device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. For example, the processors 202 may generate third information / signals by processing information in the memories 204, and then transmit a wireless signal including the third information / signals via the transceivers 206. Additionally, the processors 202 may receive wireless signals including fourth information / signals via the transceivers 206, and then store information obtained through signal processing of the fourth information / signals in the memories 204. The memories 204 may be connected to the processors 202 and may store various information related to the operation of the processors 202. For example, the memories 204 may store software code including instructions for performing all or part of the processing controlled by the processors 202 or for performing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., IEEE 802.11 series). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, apparatus may refer to a communication modem / circuit / chip.

[0045] The hardware elements of devices 100 and 200 will be described in more detail below. Not limited thereto, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY and MAC). One or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 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 this disclosure to provide them to one or more transceivers 106 and 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data or information, in accordance with the description, functions, processes, suggestions, methods and / or operation flowcharts included in this disclosure.

[0046] 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 operation flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this 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 operation flowcharts included in this disclosure may be implemented using firmware or software in the form of code, instructions and / or instruction sets.

[0047] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, 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.

[0048] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure, via one or more antennas 108, 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc., from RF band signals into baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals into RF band signals. Therefore, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0049] For example, one of STAs 100 and 200 can perform the expected operation of an AP, and the other of STAs 100 and 200 can perform the expected operation of a non-AP STA. For example, Figure 1 Transceivers 106 and 206 can perform transmission and reception operations of signals (e.g., packet or physical layer protocol data units (PPDUs) conforming to IEEE 802.11a / b / g / n / ac / ax / be / bn). Additionally, in this disclosure, the various STAs can generate transmit / receive signals or perform data processing or calculations on the transmit / receive signals in advance by [the relevant entity / component]. Figure 1Processors 102 and 202 perform the following operations: For example, examples of generating transmit / receive signals or performing data processing or computations on transmit / receive signals in advance may include: 1) determining / acquiring / configuring / computing / decoding / encoding bit information of fields (signals (SIG), short training field (STF), long training field (LTF), data, etc.) included in the PPDU; 2) determining / configuring / acquiring time or frequency resources (e.g., subcarrier resources) for the fields (SIG, STF, LTF, data, etc.) included in the PPDU; 3) determining / configuring / acquiring specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for the fields (SIG, STF, LTF, data, etc.) included in the PPDU action; 4) power control operations and / or power saving operations applied to the STA; 5) operations related to determining / acquiring / configuring / computing / decoding / encoding of the ACK signal. Additionally, in the example below, various information used by different STAs to determine / acquire / configure / calculate / decode / encode transmitted and received signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) can be stored. Figure 1 In memory 104 and 204.

[0050] In the following text, downlink (DL) can refer to a link used for communication from an AP STA to a non-AP STA, and DL PPDU / packets / signals can be sent and received via DL. In DL communication, the transmitter can be part of an AP STA, and the receiver can be part of a non-AP STA. Uplink (UL) can refer to a link used for communication from a non-AP STA to an AP STA, and UL PPDU / packets / signals can be sent and received via UL. In UL communication, the transmitter can be part of a non-AP STA, and the receiver can be part of an AP STA.

[0051] Figure 2 This is a diagram illustrating an exemplary structure of a wireless LAN system to which this disclosure can be applied.

[0052] A wireless LAN system can be structured by multiple components. These components interact to provide STA mobility support that is transparent to upper layers. The Basic Service Set (BSS) corresponds to the basic building blocks of a wireless LAN. Figure 2 An example is shown where there are two BSSs (BSS1 and BSS2), and two STAs included as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). Figure 2The ellipse representing the BSS can also be interpreted as representing the coverage area within the corresponding BSS where STAs maintain communication. This area can be called the Basic Service Area (BSA). When a STA moves outside the BSA, it cannot communicate directly with other STAs within the BSA.

[0053] If we do not consider Figure 2 The DS shown in the diagram represents the most basic BSS type in a wireless LAN: the Independent BSS (IBSS). For example, an IBSS can have a minimal form containing only two STAs. For instance, assuming other components are omitted, BSS1 containing only STA1 and STA2, or BSS2 containing only STA3 and STA4, can respectively correspond to representative examples of IBSS. This configuration is possible when STAs can communicate directly without an AP. Furthermore, in this type of wireless LAN, it is not pre-configured but can be configured as needed, and this can be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In an IBSS, all STAs can consist of mobile STAs and are not allowed to access the Distributed System (DS), thus forming a self-contained network.

[0054] Membership of an STA in a BSS can be dynamically changed by opening or closing an STA, or by entering or leaving a BSS zone. To become a member of a BSS, an STA can join the BSS using a synchronization process. To access all services of the BSS infrastructure, an STA must be associated with the BSS. This association can be dynamically established and may include the use of Distributed System Services (DSS).

[0055] 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 others, longer distances between STAs may be required for communication. Distributed systems (DS) can be configured to support extended coverage.

[0056] DS refers to the structure of BSS interconnection. Specifically, such as... Figure 2As shown, a BSS can exist as an extension of a network composed of multiple BSSs. A DS is a logical concept and can be specified through the characteristics of the Distributed System Medium (DSM). At this point, the Wireless Medium (WM) and the DSM can be logically separated. Each logical medium is used for a different purpose and 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 a wireless LAN architecture (DS architecture or other network architectures) can be interpreted as multiple media being logically different. That is, a wireless LAN architecture can be implemented in various ways, and the corresponding wireless LAN architecture can be independently specified by the physical characteristics of each implementation.

[0057] The DS can support mobile devices by providing seamless integration of multiple BSSs and offering the logical services necessary for addressing to the destination. Additionally, the DS may include a component called a portal, which acts as a bridge between the wireless LAN and other networks, such as IEEE 802.X.

[0058] AP enables access to DS via WM for associated non-AP STAs, and refers to entities that also have STA functionality. Data movement between BSS and DS can be performed through AP. For example, Figure 2 STA2 and STA3, shown in the diagram, have the functionality of STAs and provide the ability for associated non-AP STAs (STA1 and STA4) to access the DS. Furthermore, since all APs essentially correspond to STAs, all APs are addressable entities. The address used by an AP for communication on the WM is not necessarily the same as the address used by the AP for communication on the DSM. A BSS consisting of APs and one or more STAs can be referred to as an infrastructure BSS.

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

[0060] In addition to the DS structure described above, Extended Service Sets (ESS) can also be configured to provide wide coverage.

[0061] An ESS (Service Set Identity) refers to a network of arbitrary size and complexity consisting of DS (Service Controller) and BSS (Service Set Service). An ESS can correspond to a set of BSSs connected to a DS. However, an ESS does not include the DS. An ESS network is characterized as an IBSS (Integrated Service Set Service) within the Logical Link Control (LLC) layer. STAs included in an ESS can communicate with each other, and a moving STA can transparently move from one BSS to another (within the same ESS) to the LLC. APs included in an ESS can have the same Service Set Identity (SSID). The SSID is distinguished from the BSSID, which serves as the identifier for the BSS.

[0062] Wireless LAN systems make no assumptions about the relative physical locations of BSSs, and all of the following forms are possible. BSSs can partially overlap, a form commonly used to provide continuous coverage. Additionally, BSSs may not be physically connected, and logically, there is no limit to the distance between BSSs. Furthermore, BSSs can be physically located in the same location, which can be used to provide redundancy. Additionally, one (or more) IBSS or ESS networks can physically exist in the same space as one (or more) ESS networks. This can correspond to the form of ESS networks 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, etc.

[0063] Figure 3 This is a diagram illustrating the link establishment process that can be applied to this disclosure.

[0064] In order for a STA to establish a link with the network and send / receive data, it first discovers the network, performs authentication, establishes an association, and performs authentication processing for security. The link establishment process can also be called session initiation processing or session establishment processing. Furthermore, the discovery, authentication, association, and security establishment processes of the link establishment process can be collectively referred to as association processing.

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

[0066] Scanning schemes include active scanning and passive scanning. Figure 3An exemplary network discovery operation including active scanning processing is illustrated. In active scanning, the STA performing the scan sends a probe request frame to discover which APs are present around it as the channel moves and awaits a response. The responder sends a probe response frame as a response to the probe request frame to the STA that sent the probe request frame. Here, the responder may be the STA that last sent a beacon frame in the BSS of the channel being scanned. In the BSS, the AP becomes the responder because it sends a beacon frame, and in the IBSS, the STAs in the IBSS rotate to send beacon frames, so the responder is not constant. For example, an 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 a scan in the same manner (i.e., sending and receiving probe requests / responses on channel 2).

[0067] Although not in Figure 3 As shown, scanning can be performed passively. In passive scanning, the STA performing the scan waits for beacon frames while moving through the channel. Beacon frames are one of the management frames defined in IEEE 802.11 and are sent periodically to notify of the existence of a wireless network and allow the STA performing the scan to find and participate in the wireless network. In the BSS, the AP periodically sends beacon frames, and in the IBSS, the STA within the IBSS rotates to send beacon frames. When the STA performing the scan receives a beacon frame, it stores the BSS information included in the beacon frame and records the beacon frame information for 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 and passive scanning, active scanning has the advantages of less latency and less power consumption.

[0068] After the STA discovers the network, an authentication process can be performed in step S320. To clearly distinguish it from the security establishment operation in step S340, which will be described later, this authentication process can be referred to as the first authentication process.

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

[0070] An authentication frame includes the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust security network (RSN), and finite circular group. These correspond 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 may be included.

[0071] A STA can send an authentication request frame to an AP. The AP can determine whether to allow the corresponding STA's authentication based on the information included in the received authentication request frame. The AP can then provide the STA with the authentication processing result via an authentication response frame.

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

[0073] For example, an association request frame may include information related to various capabilities, beacon listening intervals, service set identifiers (SSIDs), supported rates, supported channels, RSNs, mobile domains, supported operation classes, service indication mapping broadcast requests (TIM broadcast requests), interoperability capabilities, etc. Similarly, an association response frame may include information related to various capabilities, status codes, association IDs (AIDs), supported rates, enhanced distributed channel access (EDCA) parameter sets, received channel power indicators (RCPIs), received signal-to-noise ratio indicators (RSNIs), mobile domains, timeout intervals (e.g., association recovery time), overlapping BSS scan parameters, TIM broadcast responses, quality of service (QoS) mappings, etc. These correspond to some examples of information that can be included in association request / response frames and may be replaced with other information, or additional information may be included.

[0074] After the STA successfully associates with the network, a security establishment process can be performed in step S340. The security establishment process in step S340 can be referred to as the authentication process via a Robust Secure Network Association (RSNA) request / response, the authentication process in step S320 is referred to as the first authentication process, and the security establishment process in step S340 can also be simply referred to as the authentication process.

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

[0076] Figure 4 This is a diagram illustrating the fallback process that can be applied to this disclosure.

[0077] In wireless LAN systems, the basic access mechanism for Media Access Control (MAC) is Carrier Sensing Multiple Access with Collision Avoidance (CSMA / CA). Also known as the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, CSMA / CA essentially employs a "listen-before-talk" access mechanism. Under this type of access mechanism, before commencing transmission, the AP and / or STA can perform explicit channel assessment (CCA) of the sensing radio channel or medium during a predetermined time interval (e.g., the DCF inter-frame interval (DIFS)). As a result of the sensing, if it is determined that the medium is idle, frame transmission begins via the corresponding medium. Conversely, if the medium is detected to be occupied or busy, the corresponding AP and / or STA does not begin its own transmission and can set a delay period for medium access (e.g., a random backoff period) and attempt frame transmission after waiting. By applying a random backoff period, collisions can be minimized because multiple STAs are expected to attempt frame transmission after waiting for different time periods.

[0078] 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 polling-based synchronous access method, meaning that all receiving APs and / or STAs periodically poll to receive data frames. Furthermore, HCF includes Enhanced Distributed Channel Access (EDCA) and HCF Control Channel Access (HCCA). EDCA is a contention-based access method that provides data frames to multiple users, while HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. Additionally, HCF includes a media access mechanism for improving the QoS (Quality of Service) of wireless LANs and can transmit QoS data during contention periods (CP) and contention-free periods (CFP).

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

[0080] When random backoff processing begins, the STA continuously monitors the medium during the backoff time slot countdown based on the determined backoff count value. When monitoring the medium for occupancy, it stops the countdown and waits, and restarts the remainder of the countdown when the medium becomes idle.

[0081] exist Figure 4 In the example, when the packet to be sent arrives at STA 3's MAC, STA 3 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. Meanwhile, the data to be sent can also occur in each of STA 1, STA 2, and STA 5, and when the medium is detected as idle, each STA waits for up to DIFS, and then performs a countdown for the backoff slot based on a random backoff count value chosen by each STA. Assume STA 2 chooses the minimum backoff count value, and STA 1 chooses the maximum backoff count value. That is, the example illustrates the case where STA 5's remaining backoff time is shorter than STA 1's remaining backoff time when STA 2 completes its backoff count and begins frame transmission. STA 1 and STA 5 temporarily stop the countdown and wait while STA 2 occupies the medium. When STA 2's occupancy ends and the medium becomes idle again, STA 1 and STA 5 wait for DIFS and restart the stopped backoff count. In other words, frame transmission can begin after a countdown for the remaining backoff slot based on the remaining backoff time. Since STA5 has a shorter remaining backoff time than STA1, STA5 begins frame transmission. Data to be transmitted can also occur in STA4 while STA2 is occupying the medium. From STA4's perspective, when the medium becomes idle, STA4 can wait for DIFS, then execute a countdown based on a random backoff count value selected by STA4, and begin transmitting frames. Figure 4 The example illustrates a scenario where the remaining backoff time of STA5 accidentally conflicts 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 situation, STA4 and STA5 can double the CW value, select a random backoff count value, and begin a countdown. While the medium is occupied due to the transmissions of STA4 and STA5, STA1 waits; when the medium becomes idle, STA1 waits for DIFS, and then begins frame transmission after the remaining backoff time has elapsed.

[0082] As in Figure 4In the example, data frames are frames used to send data forwarded to higher layers and can be sent after a backoff performed after DIFS, starting from when the medium becomes idle. Additionally, management frames are frames used to exchange management information that is not forwarded to higher layers and are sent after a backoff performed after an IFS such as DIFS or Point Coordination Function IFS (PIFS). Subtypes of management frames include beacons, association requests / responses, reassociation requests / responses, probe requests / responses, authentication requests / responses, etc. Control frames are frames used to control access to the medium. Subtypes of control frames include request-to-transmit (RTS), clear-to-transmit (CTS), acknowledgment (ACK), power-saving polling (PS-Poll), block ACK (BlockAck), block ACK request (BlockACKReq), empty data packet announcement (NDP announcement), and triggering, etc. If a control frame is not a response frame to the previous frame, it is sent after a backoff performed after DIFS; if it is a response frame to the previous frame, it is sent without a backoff performed after short IFS (SIFS). The type and subtype of a frame can be identified by the type field and subtype field in the Frame Control (FC) field.

[0083] The Quality of Service (QoS) ST can perform a backoff following the Arbitration IFS (AIFS) for the Access Class (AC) to which the frame belongs (i.e., AIFS where i is a value determined by the AC) before the frame can be transmitted. Here, the frame that can use AIFS can be a data frame, management frame, or control frame, rather than a response frame.

[0084] Figure 5 This is a diagram illustrating the CSMA / CA-based frame transmission operation that can be applied to this disclosure.

[0085] As mentioned above, in addition to physical carrier sensing of the medium directly sensed by the STA, the CSMA / CA mechanism also includes virtual carrier sensing. Virtual carrier sensing aims to compensate for problems such as hidden node issues that may occur during medium access. For virtual carrier sensing, the STA's MAC can use the Network Allocation Vector (NAV). The NAV is a value that indicates to other STAs the remaining time until the medium is available for current use or for STAs authorized to use the medium. Therefore, a 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, STAs receiving the NAV value are prohibited from accessing the medium. For example, the NAV can be configured based on the value of the "Duration" field in the frame's MAC header.

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

[0087] To reduce the likelihood of transmission conflicts among multiple STAs in CSMA / CA-based frame transmission operations, a mechanism using RTS / CTS frames can be applied. Figure 5 In the example, when STA1 is transmitting, as a result of carrier sensing by STA3, it can be determined that the medium is in an idle state. That is, STA1 can correspond to a hidden node with respect to STA3. Alternatively, in Figure 5 In the example, it can be determined that while STA2 is transmitting, the carrier sensing result medium of STA3 is in an idle state. That is, STA2 can 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 either STA1 or STA2, or STAs outside the carrier sensing range of transmissions from STA1 or STA3, can avoid attempting to occupy the channel during data transmission and reception between STA1 and STA2.

[0088] Specifically, STA1 can determine whether a channel is in use through carrier sensing. Regarding physical carrier sensing, STA1 can determine the channel occupancy / idle status based on the energy level or signal correlation detected in the channel. Alternatively, regarding virtual carrier sensing, STA1 can use a Network Allocation Vector (NAV) timer to determine the channel occupancy status.

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

[0090] If STA3 cannot eavesdrop on CTS frames from STA2 but can eavesdrop on RTS frames from STA1, STA3 can use the duration information included in the RTS frame to set the NAV timer for the subsequent consecutive frame transmission period (e.g., SIFS+CTS frame+SIFS+data frame+SIFS+ACK frame). Alternatively, if STA3 can eavesdrop on CTS frames from STA2, STA3 can also use the duration information included in the CTS frame to set the NAV timer for the subsequent consecutive frame transmission period (e.g., SIFS+data frame+SIFS+ACK frame) even though STA3 cannot eavesdrop on RTS frames from STA1. That is, if STA3 can eavesdrop on one or more RTS frames or CTS frames from 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.

[0091] When STA1 receives a CTS frame from STA2, STA1 can send a data frame to STA2 after SIFS, starting from the time point when the CTS frame reception is complete. When STA2 successfully receives the data frame, STA2 can send an ACK frame to STA1 after SIFS as a response to the data frame. When the NAV timer expires, STA3 can determine whether the channel is in use through carrier sensing. If STA3 determines that the channel is not in use by other terminals during DIFS after the NAV timer expires, STA3 can attempt channel access after the contention window (CW) for random backoff has passed.

[0092] Figure 6 This is a diagram illustrating an example of a frame structure that can be used in a WLAN system to which this disclosure may be applied.

[0093] Using instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare the MAC PDU (MPDU) to be transmitted. For example, when the PHY layer receives a command from the MAC layer requesting the start of transmission, it switches to transmit mode, configures the information (e.g., data) provided by the MAC layer in the form of a frame, and transmits it. Additionally, when the PHY layer detects a valid preamble in a received frame, it monitors the preamble header and sends a command to the MAC layer notifying the PHY layer of the start of reception.

[0094] In this way, information transmission / reception in a wireless LAN system is performed in the form of frames, and for this purpose, the PHY layer Protocol Data Unit (PPDU) format is defined.

[0095] A basic PPDU can include a Short Training Field (STF), a Long Training Field (LTF), a Signal (SIG) field, and a Data field. The most basic PPDU format (e.g., Figure 7 The non-HT (High Throughput) fields shown can consist solely of a Traditional-STF (L-STF), Traditional-LTF (L-LTF), Traditional-SIG (L-SIG) field, and a data field. Additionally, depending on the PPDU format type (e.g., HT mixed format PPDU, HT green format PPDU, VHT (Very High Throughput) PPDU, etc.), additional (or different types) RL-SIG, U-SIG, non-traditional SIG fields, non-traditional STF, non-traditional LTF (i.e., xx-SIG, xx-STF, xx-LTF (e.g., xx is HT, VHT, HE, EHT, etc.)) can be included between the L-SIG field and the data field.

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

[0097] The SIG field can include various information related to PPDU transmission and reception. For example, the L-SIG field consists of 24 bits and can include a 4-bit rate field, a 1-bit reserved bit, a 12-bit length field, a 1-bit parity field, and a 6-bit tail field. The RATE field can include information about the modulation and coding rate of the data. For example, the 12-bit length field can include information about the length or duration of the PPDU. For example, the value of the 12-bit length field can be determined based on the type of PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the length field can be determined to be a multiple of 3. For example, for HEPPDUs, the value of the length field can be determined to be a multiple of 3+1 or 3+2.

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

[0099] MAC PDUs are 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). MAC frames can be composed of MAC PDUs and transmitted / received via PSDUs in the data portion of the PPDU format.

[0100] The MAC header includes a frame control field, a duration / ID field, and an address field. The frame control field can include control information required for frame transmission / reception. The duration / ID field can be set to the time used to transmit the corresponding frame, etc. For details on the sequence control, QoS control, and HT control subfields of the MAC header, refer to the IEEE 802.11 standard document.

[0101] The Narrow Data PPDU (NDP) format refers to a PPDU format that does not include the data field. In other words, NDP is a frame format that includes the PPDU preamble of the general PPDU format (i.e., the L-STF, L-LTF, L-SIG fields and other non-traditional SIG, non-traditional STF, and non-traditional LTF (if present)) and does not include the remaining part (i.e., the data field).

[0102] Figure 7 This is a diagram illustrating an example of a PPDU as defined in the IEEE 802.11 standard of this disclosure.

[0103] Various types of PPDUs have been used in standards such as IEEE 802.11a / g / n / ac / ax. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and a data field. The basic PPDU format can also be referred to as a non-HT PPDU format (such as...). Figure 7 (as shown in (a)).

[0104] Compared to the basic PPDU format, the HT PPDU format (IEEE 802.11n) additionally includes the HT-SIG, HT-STF, and HT-LFT fields. Figure 7 The HT PPDU format shown in (b) can be referred to as the HT hybrid format. Furthermore, an HT green format PPDU can be defined, and this corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs and data fields, excluding L-STF, L-LTF, and L-SIG (not shown).

[0105] Compared to the basic PPDU format, examples of the VHT PPDU format (IEEE 802.11ac) additionally include VHTSIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields (such as...). Figure 7 (as shown in (c)).

[0106] Compared to the basic PPDU format, examples of the HE PPDU format (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 (such as...). Figure 7 (as shown in (d)). Some fields can be excluded, or their lengths can vary depending on the detailed examples of the HE PPDU format. For example, the HE-SIG-B field is included in the HE PPDU format for multi-user (MU), but not in the HE PPDU format for single-user (SU). Furthermore, the HE-Trigger-Based (TB) PPDU format does not include HE-SIG-B, and the length of the HE-STF field can vary up to 8 μs. 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 can vary up to 16 μs. For example, RL-SIG can be configured to be the same as L-SIG. Based on the presence of RL-SIG, the receiving STA can determine whether the received PPDU is an HE PPDU or an EHT PPDU, which will be described later.

[0107] EHT PPDU format can include Figure 7 EHT MU (Multi-user) in (e) and Figure 7 The EHT TB (trigger-based) PPDU in (f). The EHT PPDU format is similar to the HE PPDU format in that it includes RL-SIG following L-SIG, but it can include U (generic)-SIG, EHT-SIG, EHT-STF and EHT-LTF following RL-SIG.

[0108] Figure 7 In (e), 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 both SU and MU transmissions. For example, the EHT MU PPDU can correspond to a PPDU for one or more receiving STAs.

[0109] Compared to EHT MU PPDU, Figure 7 In (f), the EHT-SIG is omitted from the EHT TB PPDU. The STA that receives the trigger for UL MU transmission (e.g., trigger frame or trigger response schedule (TRS)) can perform UL transmission based on the EHT TB PPDU format.

[0110] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (general signal), and EHT-SIG fields can be encoded and modulated so that even conventional STAs can attempt demodulation and decoding, and can be mapped based on a determined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, data, and PE fields can be encoded and modulated to be demodulated and decoded by an STA that has successfully decoded a non-conventional SIG (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in that field, and can be mapped based on a determined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

[0111] Similarly, in the HE PPDU format, the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields can be referred to as pre-HE modulation fields, and the HE-STF, HE-LTF, data, and PE fields can be referred to as HE modulation fields. Additionally, in the VHT PPDU format, the L-STF, L-LTF, L-SIG, and VHT-SIG-A fields can be referred to as non-VHT modulation fields, and the VHT STF, VHT-LTF, VHT-SIG-B, and data fields can be referred to as VHT modulation fields.

[0112] Included Figure 7 In the EHT PPDU format, U-SIG can be configured based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol used for U-SIG (e.g., an OFDM symbol) can have a duration of 4 μs, and U-SIG can have a total duration of 8 μs. Each symbol of U-SIG can be used to transmit 26 bits of information. For example, each symbol of U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0113] U-SIGs can be constructed in 20 MHz units. For example, if an 80 MHz PPDU is constructed, U-SIGs can be replicated. That is, the same four U-SIGs can be included in an 80 MHz PPDU. PPDUs with bandwidths exceeding 80 MHz can include different U-SIGs.

[0114] For example, A uncoded bits can be sent via U-SIG. The first symbol of U-SIG (e.g., U-SIG-1 symbol) can send the first X bits of the total A bits, and the second symbol of U-SIG (e.g., U-SIG-2 symbol) can send the remaining Y bits of the total A bits. The A bits (e.g., 52 uncoded bits) can include a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit field). For example, the tail field can be used to terminate the lattice structure of the convolutional decoder and can be set to 0.

[0115] Bit information sent via U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG can be included in... Figure 7 The new PPDU format (e.g., UHR PPDU format) not shown in the figure, and can be included in the format of the U-SIG field included in the EHT PPDU format and the format of the U-SIG field included in the UHR PPDU format, the version-independent bits can be the same, and some or all of the version-related bits can be different.

[0116] For example, the size of the version-independent bits in U-SIG can be fixed or variable. Version-independent bits can be assigned only to the U-SIG-1 symbol, or to both the U-SIG-1 and U-SIG-2 symbols. Version-independent and version-dependent bits can be referred to by various names, such as first control bit and second control bit.

[0117] For example, the version-independent bits of U-SIG may include a 3-bit Physical Layer Version Identifier (PHY Version Identifier), which can indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted / received PPDU. The version-independent bits of U-SIG may include a 1-bit UL / DL Flag field. The first value of the 1-bit UL / DL Flag field is related to UL communication, and the second value is related to DL communication. The version-independent bits of U-SIG may include information about the length of the Transmission Opportunity (TXOP) and information about the BSS color ID.

[0118] For example, the version-related bits of U-SIG may include information that directly or indirectly indicates the type of PPDU (e.g., SU PPDU, MU PPDU, TB PPDU, etc.).

[0119] Information required for PPDU transmission and reception can be included in the U-SIG. For example, the U-SIG may also include information about bandwidth, information about the MCS technique applied to non-traditional SIGs (e.g., EHT-SIG or UHR-SIG), information indicating whether DCM (dual-carrier modulation) techniques (e.g., techniques used to achieve effects similar to frequency diversity by reusing the same signal on two subcarriers) are applied to non-traditional SIGs, information about the number of symbols used for non-traditional SIGs, and information about whether non-traditional SIGs are generated across the entire frequency band.

[0120] Some of the information required for PPDU transmission and reception may be included in U-SIG and / or non-traditional SIG (e.g., EHT-SIG or UHR-SIG). For example, information about the type of non-traditional LTF / STF (e.g., EHT-LTF / EHT-STF or UHR-LTF / UHR-STF), the length of the non-traditional LTF and the CP (cyclic prefix) length, the GI (guard interval) applicable to the non-traditional LTF, the preamble punching information applicable to the PPDU, and the resource unit (RU) allocation may be included only in U-SIG, only in non-traditional SIG, or may be indicated by a combination of information included in U-SIG and information included in non-traditional SIG.

[0121] Preamble puncturing can represent the transmission of a PPDU where no signal is present in one or more frequency units within the bandwidth of the PPDU. For example, the size of the frequency unit (or the resolution of the preamble puncturing) can be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing can be applied to PPDU bandwidths of a predetermined size or larger.

[0122] exist Figure 7 In the examples, non-traditional SIGs such as HE-SIG-B and EHT-SIG can include control information for receiving STAs. Non-traditional SIGs can be transmitted on at least one symbol, and a symbol can have a length of 4 μs. Information regarding the number of symbols used for EHT-SIGs can be included in previous SIGs (e.g., HE-SIG-A, U-SIG, etc.).

[0123] Non-traditional SIGs such as HE-SIG-B and EHT-SIG can include both public and user-specific fields. These public and user-specific fields can be encoded separately.

[0124] In some cases, the common field can be omitted. For example, in compressed mode using non-OFDMA (Orthogonal Frequency Division Multiple Access), the common field can be omitted, and multiple STAs can receive PPDUs (e.g., the data field of the PPDU) through the same frequency band. In uncompressed mode using OFDMA, multiple users can receive PPDUs (e.g., the data field of the PPDU) through different frequency bands.

[0125] The number of user-specific fields can be determined based on the number of users. A user block field can include up to two user fields. Each user field can be associated with either a MU-MIMO allocation or a non-MU-MIMO allocation.

[0126] The common fields may include CRC bits and a tail bit, where the length of the CRC bits can be determined to be 4 bits, and the length of the tail bit can be determined to be 6 bits and set to 000000. The common fields may include RU allocation information. RU allocation information may include information about the locations of RUs assigned to multiple users (i.e., multiple receiving STAs).

[0127] An RU can include multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA technology. Additionally, RUs can be defined even when transmitting signals to a single STA. Resources can be allocated in units of RUs for non-traditional STFs, non-traditional LTFs, and data fields.

[0128] The appropriate RU size can be defined based on the PPDU bandwidth. RUs can be defined the same or different for the applied PPDU format (e.g., HEPPDU, EHT PPDU, UHR PPDU, etc.). For example, in the case of an 80 MHz PPDU, the RU layout for HEPPDU and EHT PPDU can be different. The appropriate RU size, number and location of RUs, DC (direct current) subcarrier locations and numbers, empty subcarrier locations and numbers, guard subcarrier locations and numbers, etc., for each PPDU bandwidth can be referred to as the tone scheme. For example, a tone scheme for high bandwidth can be defined as multiple iterations of a low-bandwidth tone scheme.

[0129] RUs of various sizes can be defined as 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, 996-tone RUs, 2×996-tone RUs, 3×996-tone RUs, etc. MRUs (Multiple RUs) differ from multiple individual RUs and correspond to a group of subcarriers composed of multiple RUs. For example, an MRU can be defined as 52+26-tone, 106+26-tone, 484+242-tone, 996+484-tone, 996+484+242-tone, 2×996+484-tone, 3×996-tone, or 3×996+484-tone. Furthermore, the multiple RUs constituting an MRU can be consecutive or non-consecutive in the frequency domain.

[0130] The specific size of the RU can be reduced or expanded. Therefore, the specific size of each RU in this disclosure (i.e., the number of corresponding tones) is not limiting but illustrative. In addition, in this disclosure, the number of RUs can vary depending on the RU size within a predetermined bandwidth (e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz...).

[0131] Figure 7 The names of each field in the PPDU format are exemplary, and the scope of this disclosure is not limited to these names. Furthermore, the examples in this disclosure can be applied to… Figure 7 The PPDU format shown and based on Figure 7 A new PPDU format that excludes some fields and / or adds some fields, based on the PPDU format.

[0132] Trigger Frame

[0133] Figure 8 This is a diagram illustrating an exemplary format of the trigger frame to which the present disclosure may be applied.

[0134] A trigger frame can allocate resources and request the transmission of one or more TB PPDUs. The trigger frame may also include additional information required by the STA in response to the transmission of the TB PPDU. The trigger frame may include public information and user information list fields in the frame body.

[0135] The common information field may include information that is commonly used by one or more TB PPDUs sent by the trigger frame request, such as trigger type, UL length, whether there are subsequent trigger frames (e.g., more TFs), whether CS (channel sensing) is required, UL BW (bandwidth), etc.

[0136] The user information list includes zero or more user information fields. Figure 8An example is provided illustrating the EHT variant user information field format.

[0137] The AID12 subfield essentially indicates that it is a user information field for a STA with the corresponding AID. Furthermore, if the AID12 field has a predetermined specific value, it can be used for other purposes, such as allocating Random Access (RA)-RUs, or configured as a special user information field. A special user information field is a user information field that does not include user-specific information but includes extended public information not provided in the public information field. For example, a special user information field can be identified by an AID12 value of 2007, and the special user information field flag subfield in the public information field can indicate whether a special user information field is included.

[0138] The RU allocation subfield can indicate the size and location of the RU / MRU. Therefore, the RU allocation subfield can be interpreted together with the PS160 (primary / secondary 160 MHz) subfield of the user information field, the UL BW subfield of the public information field, etc. For example, the mapping of B7-B1 of the RU allocation subfield can be defined together with the settings of B0 and PS160 subfields of the RU allocation subfield, as shown in Table 1 below. Table 1 shows an example of the encoding of the PS160 subfield and RU allocation subfield of the EHT variant user information field.

[0139] [Table 1]

[0140] If the PS160 subfield is 0 and the RU / MRU size is 996 tones or less, setting B0 of the RU allocation subfield to 0 indicates that the RU / MRU allocation is applied to the primary 80 MHz channel, and setting its value to 1 indicates that the RU allocation is applied to the secondary 80 MHz channel of the primary 160 MHz channel. Conversely, if the PS160 subfield is 1 and the RU / MRU size is 996 tones or less, setting B0 of the RU allocation subfield to 0 indicates that the RU / MRU allocation is applied to the lower 80 MHz of the secondary 160 MHz channel, and setting its value to 1 indicates that the RU allocation is applied to the higher 80 MHz of the secondary 160 MHz channel.

[0141] In the trigger frame RU allocation table in Table 1, the parameter N can be based on N=2. The formula X1+X0 is used for calculation. For bandwidths of 80 MHz or less, the values ​​of PS160, B0, X0, and X1 can be set to 0. For bandwidths of 160 MHz and 320 MHz, the values ​​of PS160, B0, X0, and X1 can be set as shown in Table 2. These settings represent the absolute frequency order of the primary and secondary 80 MHz and 160 MHz channels. The order from left to right indicates the order from low frequency to high frequency. The primary 80 MHz channel is denoted as P80, the secondary 80 MHz channel as S80, and the secondary 160 MHz channel as S160.

[0142] [Table 2]

[0143] Figure 9 This is a diagram illustrating the format of a common information field in a trigger frame to which this disclosure may be applied.

[0144] refer to Figure 9 The EHT variant public information field may include information that is public to one or more TBPPDUs sent by the trigger frame request.

[0145] The EHT variant public information field includes a trigger type subfield that identifies the trigger frame variant.

[0146] Table 3 illustrates the encoding of the trigger type subfield.

[0147] [Table 3]

[0148] Additionally, the EHT variant public information fields include: a UL length subfield indicating the L-SIG length field of the solicited TB PPDU; a more TF subfield indicating whether a subsequent trigger frame (TF) is scheduled; a HE / EHT-LTF symbol quantity subfield indicating the number of EHT-LTF symbols; an LDPC extra symbol segment subfield indicating the status of LDPC (low-density parity) symbol segments; an AP Tx power subfield indicating the combined transmit power of the AP at the transmit antenna connectors of all antennas used to trigger PPDU transmission; a pre-FEC (forward error correction) padding factor subfield; a PE (packet spread) disambiguation subfield; an uplink space reuse subfield; a HE / EHT P160 subfield; a special user information field flag subfield; and trigger-related public information subfields.

[0149] The user information field of the trigger frame includes three variations: i) special user information field (see Figure 10 ), ii) HE variant user information field, and iii) EHT variant user information field (see Figure 9 ).

[0150] The user information field addressed to a non-AP STA corresponds to either the HE variant or the EHT variant. If B39 of the user information field is set to 0 and B54 of the common information field is set to 1 in the trigger frame, then the user information field is the HE variant addressed to a non-AP STA. Otherwise, it is the EHT variant. B39 of the HE variant user information field is reserved for non-EHT HE STAs. For the HE variant user information field, B39 is set to 0 by the EHT AP, and for the EHT variant user information field, B39 is the PS160 subfield.

[0151] Table 4 shows the valid combinations of public information fields B54 and B55, user information field B39, and the requested TB PPDU.

[0152] [Table 4]

[0153] Referring to Table 4, B54 and B55 of the public information field, B39 of the user information field, the existence of special user information fields in the trigger frame, variations of user information fields, and valid combinations for the corresponding TB PPDU type are defined.

[0154] Figure 10 The special user information field that can be applied to the trigger frame of this disclosure is illustrated.

[0155] refer to Figure 10 The Special User Information field does not carry user-specific information, but rather extended public information not provided in the Public Information field. The Special User Information field is identified by the AID12 value 2007 and may optionally exist in the trigger frame generated by the EHT AP.

[0156] If a special user information field exists, it is placed immediately after the common information field of the trigger frame and carries information about the U-SIG field of the requested EHT TB PPDU.

[0157] Special user information fields can be configured to include: AID12 subfield, PHY version identifier subfield, UL bandwidth extension subfield, EHT space reuse 1 subfield, EHT space reuse 2 subfield, U-SIG ignore and verification subfield, reserved bit, and trigger related user information subfield.

[0158] The PHY Version Identifier subfield indicates the PHY version of the requested TB PPDU (not HE TB PPPDU). For EHT, the PHY Version Identifier subfield is set to 0. Values ​​1 through 7 are reserved.

[0159] The uplink bandwidth extension subfield, together with the UL BW subfield of the public information field, indicates the bandwidth of the TBPPDU being solicited (i.e., the bandwidth within the U-SIG field of the EHT TBPPDU).

[0160] Table 5 shows the encoding of the uplink bandwidth extension subfield.

[0161] [Table 5]

[0162] Resource Units (RUs) and Resource Allocation

[0163] Figures 11 to 13 This is a diagram illustrating an example of a resource unit for a wireless LAN system to which the present disclosure can be applied.

[0164] Reference Figures 11 to 13 This describes a Resource Unit (RU) defined in a wireless LAN system. An RU can include multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA technology. RUs can also be defined when transmitting signals to a single STA. RUs can be used for the STF, LTF, and data fields of a PPDU.

[0165] like Figures 11 to 13 As shown, RUs corresponding to different numbers of tones (i.e., subcarriers) can be used to configure some fields of 20MHz, 40MHz, or 80MHz X-PPDUs (where X represents HE, EHT, etc.). For example, resources can be allocated in units of RUs as shown for the X-STF, X-LTF, and data fields.

[0166] Figure 11 This is a diagram illustrating an example of a resource unit applicable to a wireless LAN system according to the present disclosure.

[0167] like Figure 11 As shown at the top, 26 units (i.e., units corresponding to 26 tones) can be allocated. Six tones can be used as guard bands in the leftmost band of the 20 MHz band, and five tones can be used as guard bands in the rightmost band of the 20 MHz band. Furthermore, seven DC tones can be inserted in the center band (i.e., the DC band), and 26 units corresponding to 13 tones can exist on the left and right sides of the DC band, respectively. Alternatively, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated to a STA or a user.

[0168] Figure 11 The RU layout is used not only for multi-user (MU) scenarios but also for single-user (SU) scenarios, in which case a 242-unit configuration can be used, such as... Figure 9 As shown at the bottom. In this case, three DC tones can be inserted.

[0169] exist Figure 11 The examples illustrate various sizes of RUs, namely 26-RU, 52-RU, 106-RU, 242-RU, etc., but the specific size of these RUs can be reduced or expanded. Therefore, the specific size of each RU in this disclosure (i.e., the number of corresponding tones) is exemplary and not limiting. Furthermore, within a given bandwidth in this disclosure (e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, ...), the number of RUs can vary depending on the RU size. The following description... Figure 12 and / or Figure 13 Examples and Figure 11 The example is the same, because the size and / or number of RUs can be changed.

[0170] Figure 12 This is a diagram illustrating an example of a resource unit applicable to a wireless LAN system according to the present disclosure.

[0171] For example, when using RUs of various sizes Figure 11 In the example, Figure 12 Examples can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as guard bands in the leftmost band of the 40MHz band, and 11 tones can be used as guard bands in the rightmost band of the 40MHz band.

[0172] Additionally, as shown in the figure, the 484-RU can be used for a single user.

[0173] Figure 13 This is a diagram illustrating an example of a resource unit applicable to a wireless LAN system according to the present disclosure.

[0174] For example, using RUs of various sizes Figure 11 and Figure 12 In the example, Figure 13 Examples can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. Furthermore, in the case of an 80 MHz PPDU, the RU layout of the HE PPDU and EHTPPDU can be different, and... Figure 13 The example shows an example of a RU layout for an 80 MHz EHT PPDU. Figure 13In the example, 12 tones are used as guard bands in the leftmost band of the 80 MHz band, and 11 tones are used as guard bands in the rightmost band of the 80 MHz band, which is the same for both HE PPDU and EHT PPDU. Unlike the HE PPDU, which inserts 7 DC tones in the DC band and has one 26-RU corresponding to 13 tones on each of the left and right sides of the DC band, the EHT PPDU inserts 23 DC tones in the DC band and has one 26-RU on each of the left and right sides of the DC band. Unlike the HE PPDU, which has one empty subcarrier between the 242-RUs excluding the center band, the EHT PPDU has five empty subcarriers. In the HE PPDU, a 484-RU does not contain any empty subcarriers, while in the EHT PPDU, a 484-RU contains five empty subcarriers.

[0175] Furthermore, as shown in the figure, when used for a single user, the 996-RU can be used, in which case the insertion of 5 DC tones is common to both the HE PPDU and EHT PPDU.

[0176] EHT PPDUs of 160 MHz or higher can be configured with Figure 13 Multiple 80 MHz sub-blocks. The RU layout of each 80 MHz sub-block can be... Figure 13 The RU layout is the same for both 80 MHz EHT PPDUs. If the 80 MHz sub-block of a 160 MHz or 320 MHz EHT PPDU is not punched and the entire 80 MHz sub-block is used as part of an RU or MRU (multiple RUs), then the 80 MHz sub-block can be used. Figure 13 996-RU.

[0177] Here, an MRU corresponds to a group of subcarriers (or tones) composed of multiple RUs, and the multiple RUs constituting an MRU can be RUs of the same size or RUs of different sizes. For example, a single MRU can 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. The multiple RUs constituting an MRU can correspond to small-sized RUs (e.g., 26, 52, 106) or large-sized RUs (e.g., 242, 484, 996, etc.). That is, a single MRU including both small-sized and large-sized RUs may not be configured / defined. Furthermore, the multiple RUs constituting a single MRU may or may not be consecutive in the frequency domain.

[0178] If the 80 MHz subblock includes RUs with fewer than 996 tones, or if the 80 MHz subblock's location is punched, then the 80 MHz subblock can use an RU placement other than the 996-tone RUs. The RU locations can be fixed according to the bandwidth of each PPDU as defined in Tables 6 through 10 below.

[0179] Table 6 illustrates the index of RUs in a 20 MHz PPDU, as well as the data and pilot subcarrier indexes (range) for each RU.

[0180] [Table 6]

[0181] Table 7 illustrates the index of RUs within a 40 MHz PPDU, as well as the data and pilot subcarrier indexes (range) for each RU.

[0182] [Table 7]

[0183] Table 8 illustrates the index of RUs within an 80 MHz PPDU, as well as the data and pilot subcarrier indexes (range) for each RU.

[0184] [Table 8]

[0185] Table 9 illustrates the index of RUs within a 160 MHz PPDU, as well as the data and pilot subcarrier indexes (range) for each RU.

[0186] [Table 9]

[0187] Table 10 illustrates the index of RUs within a 320 MHz PPDU, as well as the data and pilot subcarrier indexes (range) for each RU.

[0188] [Table 10]

[0189] In Table 6, RU5 corresponds to the middle 26-tone RU.

[0190] Referring to Tables 6 through 10, subcarrier index 0 corresponds to the DC tone. A negative subcarrier index corresponds to a subcarrier with a frequency lower than the DC tone. A positive subcarrier index corresponds to a subcarrier with a frequency higher than the DC tone. A DC subcarrier can refer to a subcarrier with zero energy, including both the DC tone and subcarrier indices adjacent to subcarrier index 0 (i.e., the DC tone). A guard subcarrier can refer to a subcarrier located at the edge of an OFDM symbol in the frequency domain and having zero energy. Empty subcarriers are located near the DC or edge tones to prevent transmission center frequency leakage, receiver DC offset, and interference from adjacent RUs or MRUs, and have zero energy.

[0191] Reference Figures 11 to 13 And Tables 6 to 10 show that for each RU, the RU index can be assigned in order from low frequency to high frequency.

[0192] A PPDU in the 160 MHz or higher range can consist of multiple 80 MHz frequency subblocks. The tone scheme and RU allocation for each 80 MHz frequency subblock can be the same as those for the 80 MHz PPDU. If the 80 MHz frequency subblock of a 160 MHz or 320 MHz PPDU is not punched and the entire 80 MHz frequency subblock is used as an RU or part of an RU / MRU, then the 80 MHz frequency subblock can be used. Figure 13 The 996-tone RU is shown. If the 80 MHz frequency subblock includes RUs with fewer than 996 tones or a portion of the 80 MHz frequency subblock is punched, the 80 MHz frequency subblock can use tone schemes and RU allocations other than 996-tone RUs, such as... Figure 13 As shown.

[0193] Multiple RUs (MRUs) can be assigned to a STA. The subcarrier index of an MRU can be formed by the indices of the corresponding RUs that make up the MRU.

[0194] The RU disclosed herein can be used for uplink (UL) and / or downlink (DL) communication. For example, when performing trigger-based UL-MU communication, the STA that sends the trigger (e.g., AP) can assign a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA via trigger information (e.g., trigger frame or TRS (Trigger Response Scheduler)). The first STA can then send a first trigger-based (TB) PPDU based on the first RU, and the second STA can send a second TB PPDU based on the second RU. The first TB PPDU / second TB PPDU can be sent to the AP at the same time interval.

[0195] For example, when DL MU PPDU is configured, the STA (e.g., AP) that sends DL MU PPDU can assign the first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA and assign the second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA.

[0196] EHT-SIG field

[0197] The EHT-SIG field of a 20 MHz EHT MU PPDU includes one EHT-SIG content channel. For multi-user OFDMA and non-OFDMA transmissions, the EHT-SIG field of a 40 MHz or 80 MHz EHT MU PPDU includes two EHT-SIG content channels. For multi-user OFDMA and non-OFDMA transmissions, the EHT-SIG field of a 160 MHz or larger EHT MU PPDU contains two EHT-SIG content channels per 80 MHz frequency sub-block. When the bandwidth of the EHT MU PPDU used for OFDMA transmission is wider than 80 MHz, the EHT-SIG content channels per 80 MHz frequency sub-block can carry different information.

[0198] Each EHT-SIG content channel may include a common field and a user-specific field, wherein, depending on the PPDU frequency bandwidth, the common field may include one or two RU allocation subfields.

[0199] For OFDMA transmission, the common field of the EHT-SIG content channel can include information for RU allocation, such as the RU allocation to be used in the EHT modulation field of the PPDU, the RUs allocated to MU-MIMO, and the number of users in the MU-MIMO allocation. When the bandwidth is 20 / 30 / 80 MHz, the common field can consist of one common coding block, and the common coding block can include one or two RU allocation-A subfields. When the bandwidth is 160 MHz, the common field can consist of two common coding blocks, and the first common coding block can include two RU allocation-A subfields, and the second common coding block can include two RU allocation-B subfields. When the bandwidth is 320 MHz, the common field can consist of two common coding blocks, and the first common coding block can include two RU allocation-A subfields, and the second common coding block can include six RU allocation-B subfields.

[0200] In non-OFDMA transmissions, the common fields of the EHT-SIG content channel may not include the RU allocation subfield.

[0201] The RU allocation-A subfield of the EHT-SIG content channel corresponding to the 20 MHz frequency subchannel can indicate the RU or MRU allocation, including the size of the RU / MRU and its arrangement in the frequency domain. The RU allocation-A subfield can also indicate the information necessary to calculate the number of users allocated to each RU / MRU.

[0202] The RU allocation-B subfield of the EHT-SIG content channel corresponding to the 20 MHz frequency subchannel can indicate the RU or MRU allocation, including the size of the RU / MRU and its arrangement in the frequency domain. The RU allocation-B subfield can also indicate the information necessary to calculate the number of users allocated to each RU / MRU.

[0203] The RU allocation-A subfield and the RU allocation-B subfield can both be referred to as RU allocation subfields located in different common coding blocks.

[0204] For OFDMA transmissions wider than 80 MHz, the RU allocation subfield for each 80 MHz frequency subblock can convey consistent RU or MRU size and arrangement information for the entire PPDU.

[0205] Table 11 illustrates the number of user fields per RU or MRU associated with user-specific fields within the same EHT SIG content channel, and the mapping from the 9-bit RU allocation subfield to RU allocation.

[0206] [Table 11]

[0207] Referring to Table 11, for RU allocation subfields with a value greater than or equal to 64, y2y1y0 = 000-111 indicates the number of user fields in the EHT-SIG content channel including the corresponding 9-bit RU allocation subfield. The binary vector y2y1y0 indicates N in the EHT-SIG content channel containing the corresponding 9-bit RU allocation subfield. user (r,c)=2 2 × y² + 2 1 × y1+y0+ 1 user field.

[0208] In Table 11, the number of entries can represent the number of RU allocation subfield values ​​referring to the same RU allocation used in the frequency domain. However, due to different RU allocation subfield values, different numbers of user fields can be included in the user-specific fields of the same EHT-SIG content channel as that RU allocation subfield.

[0209] If the RU allocation subfield in Table 11 has a value that is specified as ignored, then STA can skip the N indicated by the subfield value. user (r, c) user fields and continue processing the EHT-SIG field.

[0210] Table 12 illustrates the RU or MRU associated with each RU allocation subfield and PPDU bandwidth for each EHT-SIG content channel.

[0211] [Table 12]

[0212] Table 13 shows an example of the index for empty subcarriers of each RU size when the channel bandwidth is 20 MHz and 40 MHz.

[0213] [Table 13]

[0214] Table 14 shows examples of the indexes for empty subcarriers of each RU size when the channel bandwidth is 80 MHz, 160 MHz, and 320 MHz.

[0215] [Table 14]

[0216] Triggered-based (TB) aggregated PPDU (A-PPDU) transmission and reception method .

[0217] In wireless LAN systems (802.11), TB PPDU transmission as a UL multi-user (MU) can be initiated via trigger frames. Based on the trigger frames defined in existing 802.11be frameworks, various instructions within the trigger frames can be considered for TB PPDU transmission in the UHR. Furthermore, TB A-PPDUs, which simultaneously transmit different versions of PPDUs, can be introduced to improve throughput and efficiency, and this transmission can be considered when designing trigger frames. Here, "version" can refer to the above. Figure 7 The examples show the types of PPDU formats (e.g., HT Hybrid PPDU, HT Green PPDU, VHT PPDU, HE PPDU, EHT PPDU, UHR (Ultra-High Reliability) PPDU, etc.).

[0218] This disclosure proposes a method for guiding (e.g., specific combination of bits) / signaling notification in a trigger frame that solicits a TB A-PPDU (aggregated PPDU) that aggregates two or more PPDUs with different versions (or formats, types) (e.g., {HE TB PPDU and UHR TB PPDU}, {HE TB PPDU, EHT TB PPDU and UHR TBPPDU}).

[0219] This disclosure also proposes a method for triggering different TB PPDU / TB A-PPDUs for EHT STA decoding errors.

[0220] As mentioned above, the transmission of TB PPDU can be achieved through trigger frames, and the transmission of UHR TB PPDU can also be achieved through trigger frames.

[0221] At the same time, the trigger frame can also be used to trigger the transmission of TB aggregated PPDU (A-PPDU).

[0222] Figure 14 This is a diagram illustrating a polymerized PPDU according to an embodiment of the present disclosure.

[0223] refer to Figure 14 An A-PPDU can be configured to include two or more sub-PPDUs (S-PPDUs), where each S-PPDU can be a PPDU of a different wireless LAN version (i.e., a different format). That is, each S-PPDU can correspond to any one of an HE PPDU, an EHT PPDU, or a UHR PPDU.

[0224] Figure 14 The example illustrates the configuration of sub-PPDU 1, sub-PPDU 2, and sub-PPDU 3 in the frequency domain, arranged in ascending order for 160MHz, 80MHz, and 80MHz respectively. However, this is an example, and the number of S-PPDUs constituting the A-PPDU, the bandwidth of each S-PPDU, etc., can be configured differently.

[0225] Implementation Method 1

[0226] In this embodiment, a method is proposed to indicate / signal / trigger a TB A-PPDU within a trigger frame (e.g., an enhanced trigger frame that improves upon an existing trigger frame), where the TB A-PPDU is an aggregated HE TB PPDU and UHRTB PPDU. Additionally, a method is proposed to extend the application of this method to triggering other TB PPDUs / TB A-PPDUs.

[0227] For example, in the case where the aggregated HE TB PPDU and UHR TB PPDU are TB A-PPDUs, the HE TB PPDU can be located at the primary 160MHz, and the UHR TB PPDU can be located at the secondary 160MHz.

[0228] To trigger a TB A-PPDU, bits within the common information field of the trigger frame can be used. For example, to trigger a TB A-PPDU that aggregates HE TB PPDU and UHR TB PPDU, one or more bits (e.g., B54 and B55) of the EHT variant common information field of the trigger frame can be used. As another example, in an enhanced trigger frame, the field name can be changed from the EHT variant common information field to the UHR variant common information field. In this case, one or more bits (e.g., B54 and B55) of the UHR variant common information field can be used to trigger a TB A-PPDU that aggregates HE TB PPDU and UHR TBPPDU.

[0229] Additionally, for example, the values ​​of corresponding bits in public information fields (e.g., EHT variant public information fields or UHR variant public information fields) can also be set to previously defined values. In other words, previously defined values ​​can be used to trigger TBA-PPDUs. For example, referring to Table 4, B54 can be set to 1 and B55 can be set to 0. This corresponds to the method of triggering TB A-PPDUs, where the HE TB PPDU is located within the primary 160MHz and the EHT TB PPDU is located within the secondary 160MHz. Furthermore, by setting the value of the PHY version identifier subfield within the special user information field to a value indicating the UHR version (e.g., value 1), it is possible to indicate the triggering of a non-EHT UHR TB PPDU in the secondary 160MHz. Additionally, subfields within the corresponding special user information fields can convey information for UHR TB PPDUs. Each subfield can be the same as the definition of an existing special user information field (see [link to table]). Figure 10 Provided that the EHT space reuse 1 / 2 subfield is changed to the UHR space reuse 1 / 2 subfield and all subfields can convey information for the UHR TB PPDU) or different (e.g., the order or configuration of the subfields can be different, and / or new subfields can be added), and can indicate information for the UHR TB PPDU.

[0230] However, in the above scenario, an EHT STA (without UHR capability) can attempt to decode the special user information field by identifying it as an EHT version. Since the PHY version identifier subfield is not set to an EHT version value, a decoding error may occur. In this case, the main 160MHz HE TB PPDU portion may be unable to be allocated to the STA.

[0231] Therefore, to eliminate this error, B54 and B55 of the UHR variant public information fields can be set as is (B54 set to 1 and B55 set to 0), and the value of the AID12 subfield of the special user information field can be set to a value other than 2007 (e.g., 2006). Additionally, the value of the PHY version identifier subfield of the special user information field can be set to a value indicating the UHR version. By doing so, it prevents EHT STAs (EHT STAs without UHR capabilities) from attempting to decode the special user information field of the UHR version by distinguishing it from the EHT version.

[0232] Alternatively, an additional UHR variant special user information field can be defined and positioned (e.g., it can be positioned immediately after the special user information field) without separately setting the values ​​of the AID12 subfield and the PHY version identifier subfield within the special user information field (i.e., the AID12 subfield is set to 2007, the PHY version identifier subfield indicates the EHT version, and the values ​​of other subfields within the special user information field can be set to arbitrary values). In other words, the UHR variant special user information field for UHR STA can be defined separately from the existing special user information field for EHT STA. In this case, the AID12 subfield in the UHR variant special user information field can be set to 2007 or another value (e.g., 2006), the PHY version identifier subfield can be set to indicate the UHR version, and the remaining subfields can be defined the same as the existing special user information field (see [link to special user information field]). Figure 10 Provided that the EHT space reuse 1 / 2 subfield is changed to the UHR space reuse 1 / 2 subfield and all subfields can send information for UHR TB PPDU) or different (e.g., the order or configuration of the subfields can be different, and / or new subfields can be added), and can indicate the information for UHR TB PPDU.

[0233] Alternatively, without separately setting the values ​​of the AID12 subfield and the PHY version identifier subfield within the special user information field (i.e., the AID12 subfield is set to 2007, the PHY version identifier subfield indicates the EHT version, and the values ​​of other subfields within the special user information field indicate information for the UHR TB PPDU), one of bits B56 to B62 within the UHR variant common information field can be used to indicate that the secondary 160MHz PPDU triggered in the corresponding trigger frame is a UHR TB PPDU, not an EHT TB PPDU. Since the existing default value for bits B56 to B62 is 1, one of the bit values ​​can be set to 0 to indicate this. Here, the setting of the bit in the UHR variant common information field indicating that the PPDU used for the secondary band is a UHR TB PPDU can be applied in the same manner to the other methods described above.

[0234] The above method can be extended to the case where only a UHR TB PPDU is triggered. That is, just as B54 and B55 of the EHT variant public information field in the existing trigger frame are both set to 0 to trigger an EHT TB PPDU (see Table 4), B54 and B55 of the UHR variant public information field can also be set to 0 to trigger a UHR TB PPDU. In this case, the PHY version identifier subfield in the special user information field can be set by default to a value indicating the UHR version. In addition, to address the decoding errors that may occur with EHT STAs that do not have UHR capability in this case, the methods proposed above (i. indicating the UHR version in the AID12 subfield and / or PHY version identifier subfield of the special user information field, ii. defining an additional UHR variant special user information field, or iii. using 1 bit in the UHR variant public information field) can be applied in the same way.

[0235] Implementation Method 2

[0236] In this embodiment, a method is proposed to indicate / signal / trigger a TB A-PPDU within a trigger frame (e.g., an enhanced trigger frame as an enhanced version of an existing trigger frame), the TB A-PPDU being used to trigger a TB A-PPDU in which an EHTTB PPDU and a UHR TB PPDU are aggregated.

[0237] For example, in the case of a TB A-PPDU that aggregates EHT TB PPDU and UHR TB PPDU, the EHT TB PPDU can be located at the primary 160MHz, and the UHR TB PPDU can be located at the secondary 160MHz.

[0238] To trigger a TB A-PPDU, bits within the common information field of the trigger frame can be used. For example, to trigger a TB A-PPDU that aggregates an EHT TB PPDU and a UHR TB PPDU, one or more bits (e.g., B54 and B55) of the UHR variant common information field of the trigger frame can be used. For example, both B54 and B55 of the UHR variant common information field within the trigger frame can be set to 0, and the following additional methods can be applied.

[0239] The AID12 subfield of the Special User Information field is set to 2007, and the PHY Version Identifier subfield can indicate the EHT version. Furthermore, the UL Bandwidth Extension subfield and the EHT Space Reuse 1 / 2 subfield can indicate information for the EHT TBPPDU, and the U-SIG Ignore and Verify subfield and Reserved subfield can indicate information for the UHR TB PPDU. Here, the information for the UHR TB PPDU may include i) bandwidth information for the UHR TB PPDU (i.e., the bandwidth of the S-PPDU of the UHR version) and / or bandwidth information for the A-PPDU, and ii) information on the space reuse of the channel through which the UHR TB PPDU is transmitted. In this case, to indicate the transmission of information for the UHR TB PPDU in the Special User Information field, one of bits B56 to B62 in the UHR Variant Common Information field can be used, and one bit can be set to 0.

[0240] Alternatively, the special user information field can be sent for the EHT TB PPDU in the same manner as before. Additionally, an additional UHR variant special user information field can be defined and positioned in the trigger frame. For example, the UHR variant special user information field can be positioned immediately after the special user information field. In this case, the AID12 subfield in the UHR variant special user information field can be set to 2007 or another value (e.g., 2006), and / or the PHY version identifier subfield can be set to a value indicating the UHR version. The remaining subfields can be the same as the existing special user information field definition (however, the EHT space reuse 1 / 2 subfield can be changed to the UHR space reuse 1 / 2 subfield, and information for the UHR TB PPDU can be sent in all subfields) or different (e.g., the order or configuration of the subfields can be different, and new subfields can be added), and can indicate information for the UHR TB PPDU. To indicate that the UHR variant special user information field is included in the trigger frame, one bit from the UHR variant common information field can be used. For example, one of the bits B56 to B62 in the UHR variant public information field can be used, and it can be indicated by setting it to 0.

[0241] Meanwhile, the value of the AID12 subfield used in the special user information field or the special user information field of the UHR variant (e.g., a value other than 2007 (e.g., 2006)) may not be assigned as an AID to a specific STA within the BSS of the UHR AP.

[0242] Implementation Method 3

[0243] In this embodiment, a method is proposed to indicate / signal / trigger a TB A-PPDU within a trigger frame (e.g., an enhanced trigger frame that improves upon an existing trigger frame), the TB A-PPDU being an aggregation of HE TB PPDU, EHT TB PPDU, and UHR TB PPDU.

[0244] In this scenario, for example, the HE TB PPDU can be located at the primary 160MHz, the EHT TB PPDU can be located at a specific 80MHz within the secondary 160MHz, and the UHR TB PPDU can be located at another 80MHz within the secondary 160MHz.

[0245] To trigger a TB A-PPDU, bits within the common information field of the trigger frame can be used. For example, to trigger a TB A-PPDU that aggregates an HE TB PPDU, an EHT TB PPDU, and a UHR TB PPDU, one or more bits (e.g., B54 and B55) of the UHR variant common information field of the trigger frame can be used. For example, B54 of the UHR variant common information field in the trigger frame can be set to 1 and B55 can be set to 0. Referring to existing methods, if an A-PPDU is triggered by such bit settings, a TB A-PPDU in which the HE TB PPDU is located within the primary 160MHz and the EHT TB PPDU is located within the secondary 160MHz can be triggered. However, this disclosure additionally proposes the introduction of various subfields to indicate a specific 80MHz EHT TB PPDU for the secondary 160MHz and a UHR TB PPDU for another 80MHz.

[0246] For example, the following subfields can be defined using reserved subfields of the UHR variant common information field within the trigger frame or using B56 to B62. For ease of explanation, the following description assumes that subfields are defined using B56 to B62 of the UHR variant common information field. Additionally, each bit has a default value of 1, so a specific instruction can be executed by setting that bit to a value of 0. Using one or more of the following examples A to E, an HE TB PPDU within the primary 160MHz, an EHT TB PPDU for a specific 80MHz in the secondary 160MHz, and a UHR TB PPDU for another 80MHz can be indicated.

[0247] A. Definition of A-PPDU Flag Subfield

[0248] B. Definition of UHR Variant Special User Information Field Flag Subfield

[0249] C. Definitions of UHR P160 subfields and UHR variant special user information field flags subfields

[0250] D. Use of the UHR P160 subfield and A-PPDU flag subfield

[0251] E. Use of the UHR trigger flag subfield

[0252] In the above example, in methods A, B, and E, each subfield can consist of 1 bit, and the transmission of the A-PPDU can be triggered by setting the bit value of each subfield to 0.

[0253] Additionally, in methods C and D, each subfield can consist of one bit. In case C, the transmission of an A-PPDU can be triggered by setting the UHRP160 subfield to 1 and the UHR variant special user information field flag subfield to 0. In case D, the transmission of an A-PPDU can be triggered by setting the UHR P160 subfield to 1 and the A-PPDU flag subfield to 0.

[0254] In addition, special user information fields and special user information fields for UHR variants are proposed as follows.

[0255] As before, the Special User Information field can be placed immediately after the UHR variant common information field in the trigger frame. This field is primarily used for the EHT TB PPDU. That is, as before, the AID12 subfield in the Special User Information field can indicate 2007, the PHY version identifier subfield can indicate the EHT version, and the UL bandwidth extension subfield and the EHT space reuse 1 / 2 subfield can indicate information used for the EHT TB PPDU.

[0256] The following two methods can be considered to convey information for the UHR TB PPDU.

[0257] The U-SIG ignore and verification subfields and reserved subfields in the aforementioned special user information fields can be used to indicate information for the UHR TB PPDU. Information for the UHR TB PPDU may include i) bandwidth information for the UHR TB PPDU (i.e., the bandwidth of the S-PPDU of the UHR version) and / or bandwidth information for the A-PPDU, and ii) spatial reuse information for the channel through which the UHR TB PPDU is transmitted. Additionally, information for the UHR TB PPDU may also include the PHY version ID. This is applicable to all methods A through E described above, but the following methods may be preferred, particularly for methods B and C.

[0258] The special user information field is sent for the EHT TB PPDU as before (i.e., the U-SIG ignore and validate subfields and the reserved subfields are also configured as previously defined), and additional UHR variant special user information fields can be defined and positioned within the trigger frame. For example, the UHR variant special user information field can be positioned immediately after the special user information field. In this case, the AID12 subfield in the UHR variant special user information field can be set to 2007 or another value (e.g., 2006), and the PHY version identifier subfield can be set to a value indicating the UHR version. The remaining subfields can be the same as the existing special user information field definitions (however, the EHT space reuse 1 / 2 subfield can be changed to the UHR space reuse 1 / 2 subfield, and information for the UHR TB PPDU can be sent in all subfields) or different (e.g., the order or configuration of the subfields can be changed, and new subfields can be added), and can indicate information for the UHR TB PPDU. This can apply to all methods A through E described above.

[0259] At the same time, the value used in the AID12 subfield in the special user information field or the special user information field of the UHR variant (e.g., a value different from 2007 (e.g., 2006)) may not be assigned as an AID to a specific STA within the BSS of the UHR AP.

[0260] Additionally, in the case of triggering an 80MHz EHT TB PPDU + 80MHz UHR TB PPDU (i.e., the TB A-PPDU can be located in the main 160MHz; for example, although it is desirable for the EHT TB PPDU to be located in the main 80MHz, each TB PPDU can be located at any 80MHz in the main 160MHz), the method described above can be applied as is, except for the differences described below.

[0261] Unlike the above description, B54 and B55 of the UHR variant public information fields can both be set to 0. Additionally, unlike the above description, the UHR P160 subfield can be used as the name of the UHR P160 / P80 subfield, and if the UHR TBPPDU is located in P80, the corresponding subfield can be set to 0.

[0262] Figure 15 The UHR PPDU format according to an embodiment of the present disclosure is shown.

[0263] As can be Figure 15 This is an example of a UHR PPDU used in a UHR system, which may include some format features of the HE PPDU or EHT PPDU mentioned above. (Reference) Figure 15 RL-SIG (repeated L-SIG) is included after L-LTF, L-STF and L-SIG, followed by the UHR-SIG field, UHR-STF and UHR-LTF (1, ..., N), followed by the data field and FCS.

[0264] Figure 15 All or part of all the parts (i.e., fields) illustrated in the example can be divided into multiple subparts / subfields. Each field (and its subfields) can be divided into 4µs. The transmission unit is N (where N is an integer). Additionally, it can include the guard interval (GI) (or short GI) of a standard wireless LAN standard. The common subcarrier frequency spacing value is delta_f = 312.5 kHz / N or 312.5 kHz. N (N = integer) can be applied to all the fields in the instantiation, or the first delta_f can be applied to the first part (e.g., all / part of L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-SIG), and the second delta_f (e.g., a value less than the first delta_f) can be applied to all / part of the remaining parts.

[0265] Some of the fields described may be omitted, and the order of the fields is illustrative and can be changed in various ways. For example, the U-SIG field may be placed before UHR-STF, and the UHR-SIG field may be placed after UHR-STF.

[0266] The U-SIG and UHR-SIG fields can include various control information for the transmitted PPDU. For example, they can include control information for decoding UHR-STF, UHR-LTF, and data. For example, they can include all or part of the information included in the previously described HE-SIG-A information, the HE-SIG-B information, the U-SIG information, and the EHT-SIG information.

[0267] UHR-STF can include STF sequences.

[0268] UHR-LTF can include training fields (i.e., LTF sequences) for channel estimation.

[0269] The data field includes user data and may include grouping for higher-level processing. That is, it can contain MPDUs (MAC frames).

[0270] Figure 16 Operation of a non-APSTA apparatus for a method of aggregating PPDU transmission and reception according to one embodiment of the present disclosure is shown.

[0271] Figure 16 This is based on the operation of non-AP STA devices using previously proposed methods. Figure 16 The examples are provided for ease of explanation and are not intended to limit the scope of this disclosure. Figure 16 Some steps illustrated in the examples may be omitted depending on the circumstances and / or configuration.

[0272] refer to Figure 16 The non-AP STA device receives a trigger frame from the AP device, which triggers the transmission of the A-PPDU (S1601).

[0273] Here, A-PPDU can refer to PPDUs of different types / versions / formats (i.e., S-PPDUs) aggregated in the frequency domain (see [link to relevant documentation]). Figure 14 ).

[0274] Here, PPDUs of the first type and the second type that are aggregated in the frequency domain can be aggregated into A-PPDU.

[0275] In this scenario, the first type of PPDU can be located in the primary channel, and the second type of PPDU can be located in the secondary channel. Alternatively, the first type of PPDU can be located in a specific bandwidth of the primary channel, and the second type of PPDU can be located in a different bandwidth of the primary channel.

[0276] For example, the first type of PPDU could be an EHT (Extremely High Throughput) based trigger (TB) PPDU, and the second type of PPDU could be a UHR (Ultra-High Reliability) TB PPDU. In this case, both B54 and B55 of the common information field in the trigger frame are set to 0, and one or more bits in the common information field can be used to indicate that the EHT TB PPDU and the UHR TB PPDU have been aggregated in the frequency domain.

[0277] In addition to the first type of PPDU and the second type of PPDU, the third type of PPDU can be further aggregated into the A-PPDU in the frequency domain.

[0278] In this scenario, the third type of PPDU can be located in the primary channel, the first type of PPDU can be located in a specific bandwidth in the secondary channel, and the second type of PPDU can be located in different bandwidths in the secondary channel.

[0279] For example, the first type of PPDU could be an EHT (Extremely High Throughput) triggered (TB) PPDU, the second type of PPDU could be an UHR (Ultra-High Reliability) TB PPDU, and the third type of PPDU could be an HE (High Efficiency) TB PPDU. In this case, B54 of the common information field in the trigger frame could be set to 1 and B55 could be set to 0, and one or more bits in the common information field could be used to indicate that the EHT TB PPDU, UHR TB PPDU, and HE third type PPDU have been aggregated in the frequency domain.

[0280] In addition, the trigger frame may separately include a first special user information field and a second special user information field. The first special user information field includes information for a first type of PPDU, and the second special user information field includes information for a second type of PPDU.

[0281] Here, the Affiliation Identifier (AID) 12 (AID12) subfield within the second special user information field can be set to a value different from 2007, and the Physical Version Identifier (PHY Version Identifier) ​​subfield can be set to a value indicating the physical version used for the second type of PPDU.

[0282] In addition, regarding the remaining subfields besides the AID12 subfield and the Physical Version Identifier (PHY Version Identifier) ​​subfield, the second special user information field may have the same or different structure as the first special user information field.

[0283] In addition, the second special user information field can be positioned immediately after the first special user information field.

[0284] The non-AP STA device sends an A-PPDU (S1602) to the AP device.

[0285] Non-AP STA devices can obtain the aforementioned tone plan information. As mentioned above, the information regarding the tone plan may include the size and location of the RU, control information related to the RU, information about the frequency band including the RU, and information about the STA receiving the RU, etc. Additionally, this information can be obtained through a trigger frame when a TB PPDU is transmitted.

[0286] Furthermore, non-AP STA devices can construct / generate PPDUs based on the obtained control information. The steps of constructing / generating a PPDU may include constructing / generating each field of the PPDU. That is, step S1602 may include constructing one or more fields (e.g., U-SIG and UHR-SIG-A / B fields) that include control information regarding the tone plan. For example, step S1602 may include constructing a field that includes control information indicating the bandwidth of the PPDU and / or constructing a field that includes control information indicating the size / location of the RU / MRU (e.g., an N-bitmap) and / or constructing a field that includes the identifier (e.g., AID) of the STA receiving the RU / MRU. In the case of a TB PPDU, only a portion of this information may be included.

[0287] Additionally, step S1602 may include generating an STF / LTF sequence transmitted via a specific RU / MRU. The STF / LTF sequence may be generated based on a pre-configured STF generation sequence / LTF generation sequence. Furthermore, step S1602 may include determining the number of symbols in the LTF based on spatial modulation information.

[0288] Additionally, step S1602 may include the step of generating a data field (i.e., MPDU) sent through a specific RU.

[0289] In addition, for S1602 operation, non-AP STA devices can perform at least one of the following operations: cyclic shift diversity (CSD), spatial mapping, inverse discrete Fourier transform (IDFT) / inverse fast Fourier transform (IFFT) operation, guard interval (GI) insertion, etc.

[0290] Figure 16 The methods described in the examples can be derived from... Figure 1 The first device (100) is executed. For example, Figure 1 One or more processors (102) of the first device (100) can be configured to receive trigger frames via a transceiver (106) and generate and send A-PPDUs. Furthermore, one or more memories (104) of the first device (100) can store instructions that are executed when performed by one or more processors (102). Figure 16 The methods described in the examples or the examples above.

[0291] Figure 17 Operation of an AP device for a method of aggregating PPDU transmission and reception according to one embodiment of the present disclosure is shown.

[0292] Figure 17 This is the operation of the AP device based on the previously proposed method. Figure 17 The examples are provided for ease of explanation and are not intended to limit the scope of this disclosure. Figure 17 Some steps illustrated in the examples may be omitted depending on the circumstances and / or configuration.

[0293] refer to Figure 17 The AP device sends a trigger frame to the non-AP STA device to trigger the transmission of A-PPDU (S1701).

[0294] Here, A-PPDU can refer to PPDUs of different types / versions / formats (i.e., S-PPDUs) aggregated in the frequency domain (see [link to relevant documentation]). Figure 14 ).

[0295] Here, PPDUs of the first type and the second type that are aggregated in the frequency domain can be aggregated into A-PPDU.

[0296] In this scenario, the first type of PPDU can be located in the primary channel, and the second type of PPDU can be located in the secondary channel. Alternatively, the first type of PPDU can be located in a specific bandwidth of the primary channel, and the second type of PPDU can be located in a different bandwidth of the primary channel.

[0297] For example, the first type of PPDU could be an EHT (Extremely High Throughput) based trigger (TB) PPDU, and the second type of PPDU could be a UHR (Ultra-High Reliability) TB PPDU. In this case, both B54 and B55 of the common information field in the trigger frame are set to 0, and one or more bits in the common information field can be used to indicate that the EHT TB PPDU and the UHR TB PPDU have been aggregated in the frequency domain.

[0298] In addition to the first type of PPDU and the second type of PPDU, the third type of PPDU can be further aggregated into the A-PPDU in the frequency domain.

[0299] In this scenario, the third type of PPDU can be located in the primary channel, the first type of PPDU can be located in a specific bandwidth in the secondary channel, and the second type of PPDU can be located in different bandwidths in the secondary channel.

[0300] For example, the first type of PPDU could be an EHT (Extremely High Throughput) based trigger (TB) PPDU, the second type of PPDU could be an UHR (Ultra-High Reliability) TB PPDU, and the third type of PPDU could be an HE (High Efficiency) TB PPDU. In this case, B54 of the common information field in the trigger frame can be set to 1 and B55 can be set to 0, and one or more bits in the common information field can be used to indicate that the EHT TB PPDU, UHR TB PPDU, and the third type of HE PPDU have been aggregated in the frequency domain.

[0301] In addition, the trigger frame may separately include a first special user information field and a second special user information field. The first special user information field includes information for a first type of PPDU, and the second special user information field includes information for a second type of PPDU.

[0302] Here, the Affiliation Identifier (AID) 12 (AID12) subfield within the second special user information field can be set to a value different from 2007, and the Physical Version Identifier (PHY Version Identifier) ​​subfield can be set to a value indicating the physical version used for the second type of PPDU.

[0303] In addition, regarding the remaining subfields besides the AID12 subfield and the Physical Version Identifier (PHY Version Identifier) ​​subfield, the second special user information field may have the same or different structure as the first special user information field.

[0304] In addition, the second special user information field can be positioned immediately after the first special user information field.

[0305] The AP device receives A-PPDU (S1702) from a non-AP STA device.

[0306] For the operation in step S1701, the AP device may perform operations to recover the results of the CSD, spatial mapping, IDFT / IFFT operations and GI insertion operations applied by the transmitting device (e.g., those applied in step S1402 above).

[0307] Furthermore, the AP device can perform decoding of all or part of the PPDU. Additionally, the AP device can obtain control information related to the tone plan (i.e., RU) from the decoded PPDU.

[0308] More specifically, the AP device can decode the x-SIG field of the PPDU based on a conventional STF / LTF and obtain the information contained in the x-SIG field. For example, the information about various tone schemes (i.e., RUs) proposed in this disclosure can be included in the x-SIG field, and the AP device can obtain information about tone schemes (i.e., RUs) through the x-SIG field.

[0309] Furthermore, the AP device can decode the rest of the PPDU based on information about the obtained tone plan (i.e., RU). For example, the AP device can decode the STF / LTF field of the PPDU based on information about the tone plan (i.e., RU). Additionally, the AP device can decode the data field of the PPDU based on information about the tone plan (i.e., RU) and obtain the MPDU included in the data field.

[0310] Additionally, the AP device can perform processing operations to send the decoded data to a higher layer (e.g., the MAC layer). Furthermore, if a generation signal is indicated from the higher layer to the PHY layer in response to the data sent to the higher layer, subsequent operations can be performed.

[0311] Figure 17 The methods described in the examples can be derived from... Figure 1 The second device (200) performs the operation. For example, Figure 1 One or more processors (202) of the second device (200) can be configured to send trigger frames via transceiver (206) and receive and process A-PPDUs. Furthermore, Figure 1 One or more memories (204) of the second device (200) may store instructions that are executed when executed by one or more processors (202). Figure 17 The methods described in the examples or the examples above.

[0312] Unlike existing wireless LAN systems, different versions / types / formats of PPDUs are not defined as A-PPDUs aggregated in the frequency domain. However, according to examples in this disclosure, the transmission of various TB A-PPDUs and TB A-PPDUs can be triggered. Therefore, it is possible to reduce latency and improve the efficiency of wireless communication.

[0313] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature may be implemented without being combined with other elements or features. Furthermore, embodiments of this disclosure may include combinations of some elements and / or features. The order of operations described in embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, embodiments may include claims that are not explicitly referenced in the claims, or may be included as new claims after the application has been amended.

[0314] It will be apparent to those skilled in the art that this disclosure may be implemented in other specific forms without departing from its essential characteristics. Therefore, the above detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within its scope.

[0315] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, as well as non-transitory computer-readable media that cause software or commands to be stored and executable in a device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented by using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor. The memory, or alternatively, the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results of 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.

[0316] Industrial applicability

[0317] The method presented in this disclosure is primarily described based on examples applied to IEEE 802.11-based systems (5G systems), but can be applied to various WLAN or wireless communication systems other than IEEE 802.11-based systems.

Claims

1. A method, the method comprising: The station (STA) receives a trigger frame from the access point (AP), which triggers the transmission of a Polymer Protocol Data Unit (A-PPDU), wherein a first type of PPDU and a second type of PPDU are aggregated in the A-PPDU in the frequency domain; and The STA sends the A-PPDU to the AP. The trigger frame includes a first special user information field and a second special user information field. The first special user information field includes information for the PPDU of the first type, and the second special user information field includes information for the PPDU of the second type.

2. The method according to claim 1, wherein, The PPDU of the first type is located in the main channel, and the PPDU of the second type is located in the secondary channel.

3. The method according to claim 1, wherein, The first type of PPDU is located in a specific bandwidth in the main channel, and the second type of PPDU is located in a different bandwidth in the main channel.

4. The method according to claim 1, wherein, The first type of PPDU is an ultra-high throughput EHT-based trigger-based TB PPDU, and the second type of PPDU is an ultra-high reliability UHR TB PPDU.

5. The method according to claim 4, wherein, In the trigger frame, both B54 and B55 of the public information field are set to 0, and One or more bits in the public information field are used to indicate that the EHT TB PPDU and the UHRTB PPDU are aggregated in the frequency domain.

6. The method according to claim 1, wherein, The third type of PPDU, together with the first type of PPDU and the second type of PPDU, are further aggregated in the frequency domain into the A-PPDU.

7. The method according to claim 1, wherein, The third type of PPDU is located in the main channel, the first type of PPDU is located in a specific bandwidth in the secondary channel, and the second type of PPDU is located in a different bandwidth in the secondary channel.

8. The method according to claim 1, wherein, The first type of PPDU is an ultra-high throughput EHT-based trigger-based TB PPDU, the second type of PPDU is an ultra-high reliability UHR TB PPDU, and the third type of PPDU is a high-efficiency HE TB PPDU.

9. The method according to claim 8, wherein, The B54 and B55 fields of the public information field in the trigger frame are set to 1 and 0, respectively, and One or more bits in the public information field are used to indicate that the EHT TB PPDU, the UHR TB PPDU, and the third type of HE PPDU are aggregated in the frequency domain.

10. The method according to claim 1, wherein, In the second special user information field, the association identifier AID12 subfield is set to a value different from 2007, and the physical version identifier PHY version identifier subfield is set to a value indicating the physical version of the PPDU used for the second type.

11. The method according to claim 10, wherein, For the remaining subfields other than the AID12 subfield and the PHY version identifier subfield, the second special user information field has the same or different structure as the first special user information field.

12. The method according to claim 1, wherein, The second special user information field is located immediately after the first special user information field.

13. A station STA device, the STA device comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: A trigger frame is received from the access point (AP), which triggers the transmission of a polymerizable protocol data unit (A-PPDU), wherein a first type of PPDU and a second type of PPDU are aggregated in the A-PPDU in the frequency domain; and Send the A-PPDU to the AP. The trigger frame includes a first special user information field and a second special user information field. The first special user information field includes information for the PPDU of the first type, and the second special user information field includes information for the PPDU of the second type.

14. A method comprising: Access point (AP) sends a trigger frame to station (STA), which triggers the transmission of Aggregate Protocol Data Unit (A-PPDU), wherein a first type of PPDU and a second type of PPDU are aggregated in the A-PPDU in the frequency domain; and The AP receives the A-PPDU from the STA. The trigger frame includes a first special user information field and a second special user information field. The first special user information field includes information for the PPDU of the first type, and the second special user information field includes information for the PPDU of the second type.

15. An access point (AP) device, the AP device comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: A trigger frame is sent to the station STA, which triggers the transmission of a Polymer Protocol Data Unit (A-PPDU), wherein a first type of PPDU and a second type of PPDU are aggregated in the A-PPDU in the frequency domain; and Receive the A-PPDU from the STA. The trigger frame includes a first special user information field and a second special user information field. The first special user information field includes information for the PPDU of the first type, and the second special user information field includes information for the PPDU of the second type.

16. A processing apparatus configured to control a station (STA) in a wireless local area network (WLAN) system, the processing apparatus comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor, and storing instructions that, based on execution by the at least one processor, perform the method according to any one of claims 1 to 12.

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

Images