Devices and methods for signaling extension in wireless local area network systems

Abstract

Devices and methods for signaling extension in a wireless local area network system are provided. A method for communicating between a first device (e.g., an AP) and each of a traditional device and a non-traditional device (e.g., a STA) includes: at the first device, generating a first information field for the traditional device; generating a second information field for the non-traditional device; generating a frame including the first information field and the second information field; and transmitting the frame, wherein the first information field includes a first value, by which the traditional device identifies the first information field as valid, and wherein the second information field includes a second value, by which the traditional device identifies the second information field as invalid.

Description

[0001] Cross-reference to related applications

[0002] This application is based on and claims priority to Korean Patent Application No. 10-2020-0066702 filed on June 2, 2020, Korean Patent Application No. 10-2020-0115513 filed on September 9, 2020, and Korean Patent Application No. 10-2021-0033456 filed on March 15, 2021, the disclosures of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to wireless communications, and more specifically, to devices and methods for signaling extension in wireless local area network (WLAN) systems. Background Technology

[0004] WLAN systems connect two or more devices to each other in localized environments such as homes, buildings, or campuses, and typically connect these devices to the Internet. The latest WLAN technology is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The 802.11 standard has evolved into versions 802.11b, 802.11a, 802.11g, 802.11n, 802.11ac, and 802.11ax, with the most recent versions supporting transmission rates up to 1 Gbyte / s using current Orthogonal Frequency Division Multiplexing (OFDM) technology. In a typical WLAN, an access point (AP) acts as a gateway to connect user devices such as laptops and smartphones to the Internet. Each user device can use a set of assigned OFDM subcarriers across the entire frequency band of the WLAN to communicate with the AP and / or another user device.

[0005] In the WLAN standard (version) 802.11ac, data can be sent to multiple users simultaneously using Multi-User Multiple-Input Multiple-Output (MU-MIMO) technology. However, WLAN systems using 802.11ac only allow uplink signals to be sent from one user device to one access point at a time, which may slow down data communication in areas with a high concentration of users.

[0006] Version 802.11ax (also known as High Efficiency (HE)) addresses the congested user problem by using Orthogonal Frequency Division Multiple Access (OFDMA) technology to enable simultaneous uplink communication from multiple user equipments (UEs) to the access point (AP). OFDMA assigns a Resource Unit (RU) to each UE, which comprises a set of OFDM subcarriers. RUs are used for both uplink and downlink, enabling WLAN systems using 802.11ax (which also uses MU-MIMO) to effectively support communication in densely populated local areas and outdoor areas.

[0007] Furthermore, the next-generation WLAN standard 802.11be (also known as Ultra High Throughput (EHT)) is expected to support 6 GHz unlicensed bands, bandwidth up to 320 MHz per channel, introduce Hybrid Automatic Repeat Request (HARQ), and support up to 16x16 MIMO. Leveraging these capabilities, next-generation WLAN systems are expected to effectively support low latency and ultra-high-speed transmission with performance metrics similar to New Radio (NR) 5G technology. Summary of the Invention

[0008] Embodiments of this disclosure provide an apparatus and method for extending signaling in a wireless local area network (WLAN) system while maintaining backward compatibility.

[0009] According to one aspect of this disclosure, a method for communicating between a first device (e.g., an AP) and each of a traditional device and a non-traditional device (e.g., a site STA) includes: generating a first information field for the traditional device; generating a second information field for the non-traditional device; generating a frame including the first information field and the second information field; and transmitting the frame. The first information field includes a first value that allows the traditional device to recognize the first information field as valid. The second information field includes a second value that allows the traditional device to recognize the second information field as invalid.

[0010] According to another aspect of this disclosure, a first apparatus for communicating with conventional and non-conventional devices includes: a transceiver configured to generate a first information field for the conventional device, generate a second information field for the non-conventional device, generate a frame including the first information field and the second information field, and transmit the frame; and a processor configured to control the transceiver. The first information field includes a first value that allows the first information field to be recognized as valid by the conventional device, and the second information field includes a second value that allows the second information field to be recognized as invalid by the conventional device.

[0011] According to another aspect of this disclosure, a method for communication between a non-traditional device and a first device, the first device communicating with a conventional device, the method comprising: at the non-traditional device: receiving a frame from the first device; extracting a first information field and a second information field from the frame; ignoring the first information field based on a first value included in the first information field; and identifying first information from the second information field based on a second value included in the second information field. The conventional device is capable of identifying the first information field as valid based on the first value, and the conventional device is capable of identifying the second information field as invalid based on the second value.

[0012] Additionally, according to one aspect of this disclosure, a method for communicating with both conventional and non-conventional devices includes: generating a first information field for the conventional device; generating a second information field for the non-conventional device; generating a frame including the first information field and the second information field; and transmitting the frame, wherein generating the frame includes sequentially arranging the first information field and the second information field in an interval in which a variable number of information fields of the frame are arranged.

[0013] According to another aspect of this disclosure, a receiving device for a WLAN system includes: a transceiver configured to receive a PPDU including a preamble and a payload from a transmitting device, and to decode the payload based on the preamble; and a processor configured to control the transceiver, wherein a data field of the payload includes a first trigger frame and a second trigger frame, the first trigger frame and the second trigger frame being aggregated in the form of an A-MPDU to support different first and second standards, respectively, wherein an uplink transmission of the receiving device is triggered by either the first trigger frame or the second trigger frame.

[0014] According to another aspect of this disclosure, a receiving device for a WLAN system includes: a transceiver configured to receive a PPDU including a preamble and a payload from a transmitting device, and to decode the payload based on the preamble; and a processor configured to control the transceiver, wherein the data field of the payload includes a trigger frame in the form of an S-MPDU, wherein the trigger frame includes a MAC header and a frame body, wherein the frame body includes a common information field and a plurality of user information fields, wherein the common information field includes common control information applied to a second receiving device, the second receiving device supporting a different standard than the standard supported by the receiving device, wherein a first user information field among the plurality of user information fields includes user-specific control information applied to the second receiving device, and wherein the second user information field and a third user information field among the plurality of user information fields are respectively used as the common information field and the user information field applied to the receiving device.

[0015] Additionally, according to another aspect of this disclosure, a receiving device for a WLAN system includes: a transceiver configured to receive a PPDU including a preamble and a payload from a transmitting device, and to decode the payload based on the preamble; and a processor configured to control the transceiver, wherein the data field of the payload includes a trigger frame in the form of an S-MPDU, wherein the trigger frame includes a MAC header and a frame body, wherein the frame body includes a common information field and a user information field applied to the receiving device, and a common information field, a user information field, and a padding field applied to a second receiving device, wherein the standard supported by the second receiving device is different from the standard supported by the receiving device, wherein the common information field and the user information field applied to the second receiving device are assigned before the padding field, and wherein the common information field and the user information field applied to the receiving device are assigned after the padding field.

[0016] In addition, according to another aspect of this disclosure, a wireless communication method for a receiving device in a WLAN system includes: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble, wherein the data field of the payload includes a first trigger frame and a second trigger frame, the first trigger frame and the second trigger frame being aggregated in the form of an A-MPDU to support different first and second standards respectively, wherein the uplink transmission of the receiving device is triggered by either the first trigger frame or the second trigger frame.

[0017] Furthermore, according to another aspect of this disclosure, a wireless communication method for a first receiving device in a WLAN system includes: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble, wherein the data field of the payload includes a trigger frame in the form of an S-MPDU, wherein the trigger frame includes a MAC header and a frame body, wherein the frame body includes a common information field and a plurality of user information fields, wherein the common information field includes common control information applied to a second receiving device, the standard supported by the second receiving device being different from the standard supported by the first receiving device, wherein the first user information field among the plurality of user information fields includes user-specific control information applied to the second receiving device, and wherein the second user information field and the third user information field among the plurality of user information fields are respectively used as the common information field and the user information field applied to the first receiving device.

[0018] Furthermore, according to another aspect of this disclosure, a wireless communication method for a receiving device in a WLAN system includes: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble, wherein the data field of the payload includes a trigger frame in the form of an S-MPDU, the trigger frame including a MAC header and a frame body, wherein the frame body includes a common information field and a user information field applied to the receiving device, and a common information field, a user information field, and a padding field applied to a second receiving device, wherein the standard supported by the second receiving device is different from the standard supported by the receiving device, wherein the common information field and the user information field applied to the second receiving device are assigned before the padding field, and wherein the common information field and the user information field applied to the receiving device are assigned after the padding field.

[0019] Additionally, according to another aspect of this disclosure, a non-transitory computer-readable storage medium stores instructions executed by a processor included in a receiving device of a WLAN system, the method comprising: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble, wherein the data field of the payload includes a first trigger frame and a second trigger frame, the first trigger frame and the second trigger frame being aggregated in the form of an A-MPDU to support different first and second standards, respectively, wherein an uplink transmission of the receiving device is triggered by either the first trigger frame or the second trigger frame.

[0020] Additionally, according to another aspect of this disclosure, a non-transitory computer-readable storage medium stores instructions executed by a processor included in a receiving device of a WLAN system, the method comprising: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble, wherein the data field of the payload includes a trigger frame in the form of an S-MPDU, wherein the trigger frame includes a MAC header and a frame body, wherein the frame body includes a common information field and a plurality of user information fields, wherein the common information field includes common control information applied to a second receiving device, the second receiving device supporting a different standard than the standard supported by the receiving device, wherein a first user information field among the plurality of user information fields includes user-specific control information applied to the second receiving device, wherein a second user information field and a third user information field among the plurality of user information fields are respectively used as the common information field and the user information field applied to the receiving device.

[0021] Additionally, according to another aspect of this disclosure, a non-transitory computer-readable storage medium stores instructions executed by a processor included in a receiving device of a WLAN system, the method comprising: receiving a PPDU including a preamble and a payload; and decoding the payload based on the preamble, wherein the data field of the payload includes a trigger frame in the form of an S-MPDU, wherein the trigger frame includes a MAC header and a frame body, wherein the frame body includes a common information field and a user information field applied to the receiving device, and a common information field, a user information field, and a padding field applied to a second receiving device, wherein the standard supported by the second receiving device is different from the standard supported by the receiving device, wherein the common information field and the user information field applied to the second receiving device are assigned before the padding field, and wherein the common information field and the user information field applied to the receiving device are assigned after the padding field. Attached Figure Description

[0022] Embodiments of the inventive concept will become clearer from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0023] Figure 1 This is a diagram illustrating a wireless local area network (WLAN) system;

[0024] Figure 2 This is a block diagram illustrating a wireless communication device for transmitting or receiving PPDUs;

[0025] Figure 3 yes Figure 2 A schematic block diagram of a wireless communication device;

[0026] Figure 4This is a diagram illustrating the structure of a HE-triggered response (TB) PPDU as defined in 802.11ax;

[0027] Figure 5 This is a diagram illustrating the structure of a trigger frame as defined in 802.11ax;

[0028] Figure 6 It is a diagram. Figure 5 A diagram showing the structure of the public information fields;

[0029] Figure 7 It is a diagram. Figure 6 A graph of the trigger type subfield;

[0030] Figure 8 It is a diagram. Figure 6 A graph of the uplink bandwidth subfield;

[0031] Figure 9 It is a diagram. Figure 5 A diagram showing the structure of the user information fields;

[0032] Figure 10 It is a diagram. Figure 9 A diagram of the association identifier 12 (AID12) subfield;

[0033] Figure 11 It is a diagram. Figure 9 A graph of the RU allocation subfield;

[0034] Figure 12 This is a schematic diagram illustrating the uplink transmission process of an FD A-PPDU via a trigger frame according to an embodiment of the present disclosure;

[0035] Figure 13 This is a diagram illustrating an example of a trigger frame according to an embodiment of the present disclosure;

[0036] Figure 14 This is a diagram illustrating another example of a trigger frame according to an embodiment of the present disclosure;

[0037] Figure 15 It is a diagram. Figure 14 A diagram illustrating an example structure of the EHT user information field;

[0038] Figure 16 This is a diagram illustrating another example of a trigger frame according to an embodiment of the present disclosure;

[0039] Figure 17 This is a flowchart illustrating a wireless communication method of a transmitting device in a WLAN system according to an embodiment of the present disclosure;

[0040] Figure 18 This is a flowchart illustrating a wireless communication method of a receiving device in a WLAN system according to an embodiment of the present disclosure;

[0041] Figure 19 This is a message diagram illustrating a wireless communication method of a WLAN system according to an embodiment of the present disclosure;

[0042] Figure 20 This is a diagram illustrating frames according to an embodiment of the present disclosure;

[0043] Figure 21 This is a timing diagram illustrating the channel detection process in a WLAN system.

[0044] Figure 22 This is a diagram illustrating the structure of an NDP advertisement frame as defined in 802.11ax;

[0045] Figure 23A and Figure 23B It is a diagram. Figure 22 A diagram showing the structure of the STA information fields;

[0046] Figure 24 This is a diagram illustrating an NDP notification frame according to an embodiment of the present disclosure;

[0047] Figure 25 This is a signaling diagram illustrating a wireless communication method of a WLAN system according to an embodiment of the present disclosure;

[0048] Figure 26 It is a diagram illustrating frames according to exemplary embodiments of the present disclosure; and

[0049] Figure 27 This is a diagram illustrating a trigger frame according to an embodiment of the present disclosure. Detailed Implementation

[0050] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings, in which the same reference numerals refer to the same elements or features.

[0051] The terminology used herein is for describing embodiments and not for limiting the inventive concept. In this document, the singular forms include the plural forms unless specifically described. The described components, processes, operations, and / or elements do not exclude the presence or addition of one or more other components, processes, operations, and / or elements.

[0052] Unless otherwise defined, all terms used herein (including technical and scientific terms) may be used in the sense that would be commonly understood by one skilled in the art. Furthermore, unless specifically defined, terms as defined in commonly used dictionaries are not interpreted ideally or excessively.

[0053] Furthermore, in specifically describing embodiments of the inventive concept, orthogonal frequency division multiplexing (OFDM) or OFDM-based wireless communication systems, particularly the IEEE 802.11 standard, will be described primarily. However, the essential points of the inventive concept can be slightly modified by those skilled in the art without significantly departing from its scope and applied to other communication systems with similar technical backgrounds and channel types (e.g., cellular communication systems such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), New Radio (NR), WiBro, or Global System for Mobile Communications (GSM), or long-range communication systems such as Bluetooth or Near Field Communication (NFC)).

[0054] In this document, “connection (combination)” and its derivatives refer to direct or indirect communication between two or more components that are physically in contact or not physically in contact. The terms “send,” “receive,” and “communicate,” and their derivatives, include all direct and indirect communication. The terms “include” and / or “contain” as used herein mean to include without limitation. “Or” refers to the collective term “and / or.” “Related to” and its derivatives mean to include, to be included in, to be connected to, to be implied, to be contained in, to be connected to, to be combined with, to be able to communicate with, to cooperate with, to be inserted, to be placed in parallel, to be near, to be bound to, to have, to have the characteristics of, and to be related to. “Controller” means a device, system, or part thereof that controls at least one operation. A controller may be implemented by hardware or a combination of hardware and software and / or firmware. Functionality associated with a particular controller may be centralized or distributed, either locally or remotely.

[0055] In this document, "traditional device" refers to a device that can meet the specifications of an older version of the standard (e.g., version 802.11) but not all the specifications of a newer version of the standard. In this document, "non-traditional device" or the interchangeable "next-generation device" is a relative term for a device that can meet the specifications of a newer version of the standard compared to a traditional device. A "next-generation device," compared to a traditional device, can be a device that can meet the specifications of the immediately following version or at least two subsequent versions.

[0056] In this article, a specific 802.11 standard may sometimes be referred to as a "version" of the 802.11 standard. For example, the "802.11ax" standard may sometimes be referred to as the 802.11ax version of the 802.11 standard.

[0057] For the sake of brevity, once an element is introduced with both a name and a label for the first time, it can be referred to using only the label thereafter. For example, “First STA STA1” can be referred to simply as “STA1”; “Third Trigger Frame 3” can be referred to as “Trigger Frame 3”; “First Receiver HE STA” can be referred to as “HESTA”; and so on.

[0058] Figure 1 This is a diagram illustrating a wireless local area network (WLAN) system. Figure 2 This is a block diagram illustrating a wireless communication device for transmitting or receiving Protocol Data Units (PPDUs). Figure 3 yes Figure 2 A schematic block diagram of a wireless communication device.

[0059] First, such as Figure 1 As shown, the WLAN system 100 may include access points (APs) 101 and 103.

[0060] For example, APs 101 and 103 can communicate with at least one network 130, such as the Internet, Internet Protocol (IP) networks, or other data networks.

[0061] APs 101 and 103 provide wireless connectivity to network 130 for multiple stations (STAs) 111 to 114 in their coverage areas 120 and 125. APs 101 and 103 can communicate with each other using Wi-Fi or other WLAN communication technologies. APs 101 and 103 can communicate with STAs 111 to 114 using Wi-Fi or other WLAN communication technologies. In this document, the AP may be referred to as a first device and the STA as a second device. Therefore, the first device can communicate with at least one second device.

[0062] For example, depending on the network type, other well-known terms such as "router" and "gateway" can be used instead of "AP". Additionally, in WLANs, APs are used for wireless channels. Furthermore, when a first AP communicates with a second AP, the first AP can act as a STA.

[0063] Additionally, depending on the network type, "STA" may be used in place of other well-known terms such as "mobile station," "user station," "remote terminal," "user equipment," "wireless terminal," "user device," or "user." For ease of description, in this document, "STA" is used to refer to a remote wireless device that is wirelessly connected to an AP or a wireless channel in a WLAN. In this document, STA is primarily described as a mobile device (e.g., a mobile phone or smartphone). However, STA can also be a fixed device (e.g., a desktop computer, AP, media player, fixed sensor, or television set).

[0064] The approximate extents of coverage areas 120 and 125 are marked with dashed lines. For ease of illustration, coverage areas 120 and 125 are depicted as circular. However, coverage areas 120 and 125 associated with APs 101 and 103 may have other shapes reflecting different variations in the wireless environment related to natural or man-made obstacles, or may have other irregular shapes as configured for APs 101 and 103.

[0065] As described in detail later, APs 101 and 103 may include circuitry and / or procedures for managing uplink multi-user (ULMU) or downlink multi-user (DLMU) transmissions in the WLAN system 100.

[0066] although Figure 1 An example of a WLAN system 100 is illustrated, but embodiments of the inventive concept are not limited thereto. That is, it is possible to... Figure 1 Make various changes.

[0067] For example, WLAN system 100 may include any number of appropriately arranged APs and any number of STAs. Additionally, AP 101 can communicate directly with any number of STAs. AP 101 can provide wireless broadband access to multiple STAs 111 to 114 via network 130.

[0068] Similarly, both APs 101 and 103 can communicate directly with network 130 and provide wireless broadband access to multiple STAs 111 to 114 via network 130. Additionally, APs 101 and 103 can be configured to connect to different external networks, such as external telephone networks or data networks.

[0069] exist Figure 2 The image illustrates a wireless communication device for transmitting or receiving PPDUs. For example, it can be... Figure 2 The wireless communication device 200 is included in a transmitting device (e.g., AP) or a receiving device (e.g., STA). That is, Figure 2 Wireless communication devices may be included Figure 1In any of AP 101 and 103 and STA 111 to 114 shown, and for example, Figure 2 Wireless communication devices can be used in computers, smartphones, portable electronic devices, tablets, wearable devices, sensors for Internet of Things (IoT) devices, etc.

[0070] For example, wireless communication device 200 may include antenna 190, front-end module (FEM) 205, radio frequency integrated circuit (RFIC) 210, and baseband circuitry 220. For instance, FEM 205 and RFIC 210 may be implemented as a single component on a single chip. In this case, the functions of FEM 205 and RFIC 210, which will be described later, can be implemented together on a single chip. However, for ease of illustration, embodiments of this disclosure are described as examples where FEM 205 and RFIC 210 are separate components.

[0071] Antenna 190 can be connected to FEM 205 and can transmit signals provided from FEM 205 to another wireless communication device (terminal or base station), or provide signals received from another wireless communication device to FEM 205. Additionally, FEM 205 is connected to antenna 190 to separate the transmit and receive frequencies. That is, FEM 205 can separate the signals provided from RFIC 210 for each frequency band and provide the separated signals to the corresponding antenna 190. Furthermore, FEM 205 can provide signals received from antenna 190 to RFIC 210.

[0072] In this way, antenna 190 can transmit signals whose frequencies have been separated by FEM 205 to available space or can provide signals received wirelessly from an external source to FEM 205.

[0073] For example, antenna 190 may include, for example, an array antenna, but is not limited thereto. Additionally, antenna 190 may include one or more antennas. Therefore, in some embodiments, wireless communication device 200 may use multiple antennas to support phased array, multiple-input multiple-output (MIMO), etc. However, in Figure 2 For ease of explanation, an antenna is shown in the diagram.

[0074] Additionally, FEM 205 may include an antenna tuner (not shown). The antenna tuner (not shown) is connected to antenna 190 to adjust the impedance of the connected antenna 190.

[0075] RFIC 210 can generate an RF signal by performing a frequency up-conversion on the baseband signal provided from baseband circuit 220. Alternatively, RFIC 210 can generate a baseband signal by performing a frequency down-conversion on the RF signal provided from FEM 205.

[0076] For example, RFIC 210 may include a transmitting circuit 212 for up-conversion, a receiving circuit 214 for down-conversion, and a local oscillator 216.

[0077] For example, although not shown in the figures, the transmitting circuit 212 may include a first analog baseband filter, a first mixer, and a power amplifier. Additionally, the receiving circuit 214 may include a second analog baseband filter, a second mixer, and a low-noise amplifier.

[0078] Here, the first analog baseband filter filters the baseband signal received from the baseband circuit 220 and provides the filtered baseband signal to the first mixer. Furthermore, the first mixer can perform up-conversion of the baseband signal's frequency from baseband to a higher frequency band using a frequency signal provided by the local oscillator 216. This up-conversion allows the baseband signal to be provided as an RF signal to the power amplifier, which then amplifies the RF signal and provides the amplified RF signal to the FEM 205.

[0079] Additionally, the low-noise amplifier amplifies the RF signal provided from FEM 205 and provides the amplified RF signal to the second mixer. Furthermore, using the frequency signal provided by the local oscillator 216, the second mixer performs a down-conversion of the RF signal from the high-frequency band to the baseband. This down-conversion allows the RF signal to be provided as a baseband signal to the second analog baseband filter, which then filters the baseband signal and provides the filtered baseband signal to the baseband circuit 220.

[0080] Meanwhile, the baseband circuit 220 can receive and process baseband signals from the RFIC 210, or generate baseband signals and provide them to the RFIC 210.

[0081] Additionally, the baseband circuit 220 may include a controller 222, a memory 224, and a signal processor 225.

[0082] For example, controller 222 can control the overall operation of RFIC 210 and baseband circuitry 220. Additionally, controller 222 can write or read data from memory 224. For this purpose, controller 222 may include at least one processor, microprocessor, or microcontroller, or may be part of a processor. More specifically, controller 222 may include, for example, a central processing unit (CPU), digital signal processor (DSP), etc.

[0083] Storage 224 may store data such as basic programs, application programs, and setting information for the operation of wireless communication device 200. For example, storage 224 may store instructions and / or data related to controller 222, signal processor 225, or RFIC 210. In addition, storage 224 may store trigger frame format, PPDU format, and RU allocation information.

[0084] The storage device 224 may include various storage media, such as volatile memory and / or non-volatile memory; random access memory (RAM) (e.g., DRAM, PRAM, MRAM, SRAM, etc.); and / or flash memory (e.g., NAND flash memory, NOR flash memory, ONE NAND flash memory, etc.).

[0085] Memory 224 can store various processor-executable instructions. Furthermore, these processor-executable instructions can be executed by controller 222.

[0086] Signal processor 225 can process baseband signals provided from RFIC 210 and can process baseband signals to be provided to RFIC 210. For example, signal processor 225 can use information stored in storage 224 to generate PPDUs or decode PPDUs received from external wireless communication devices (i.e., PPDUs received from external wireless communication devices via antenna 190, FEM 205, and RFIC 210).

[0087] For ease of description, the signal processor 225 will be described based on the components in the receiving path. Similar components may be applied to the transmitting path.

[0088] For example, signal processor 225 may include a demodulator, an RxFilter and a cell searcher, and other components.

[0089] First, the demodulator may include a channel estimator, a data deallocation unit, an interference whitening unit, a symbol detector, a channel state information (CSI) generator, a mobility measurement unit, an automatic gain control unit, an automatic frequency control unit, a symbol timing recovery unit, a delay spread estimation unit, a time correlator, etc., and can perform the function of each component.

[0090] Here, the mobility measurement unit is a unit that measures the signal quality of the serving cell and / or neighboring cells to support mobility, and can measure the cell's Received Signal Strength Indicator (RSSI), Reference Received Power (RSRP), Reference Received Quality (RSRQ), Reference Signal (RS) - Signal-to-Interference-Noise Ratio (SINR), etc.

[0091] For example, although not shown in the accompanying drawings, a demodulator may include multiple sub-demodulators that perform the above functions independently or jointly for each despread signal or signal in each frequency band of a 2G, 3G, 4G, and 5G communication system.

[0092] Subsequently, the RxFilter and cell searcher may include an RxFilter, a cell searcher, a Fast Fourier Transform (FFT) unit, a Time-Duplex Automatic Gain Control (TD-AGC) unit, and a Time-Duplex Automatic Frequency Control (TD-AFC) unit.

[0093] Here, the RxFilter (also known as the Rx front end) performs operations such as sampling, interference cancellation, and amplification on the baseband signal received from the RFIC 210. Additionally, because the cell searcher includes a primary synchronization signal (PSS) detector and a secondary synchronization signal (SSS) detector, it can measure the magnitude and quality of neighboring cell signals.

[0094] Meanwhile, other components may include symbol processors, channel decoders, and other components in the transmission path.

[0095] Here, the symbol processor can perform channel deinterleaving, demultiplexing, rate matching, etc., enabling decoding of the demodulated signal for each channel. Additionally, the channel decoder can decode the demodulated signal in blocks. Furthermore, the symbol processor and channel decoder may include a Hybrid Automatic Repeat Request (HARQ) processing unit, a turbo decoder, a CRC checker, a Viterbi decoder, and a turbo encoder.

[0096] In addition, other parts of the transmission path may include transmit first-in-first-out (TX FIFO), encoder, scrambler, interleaver, constellation mapper, inverse discrete Fourier transform (IDFT), guard interval and windowing insertion module, etc.

[0097] Therefore, in Figure 2 In the diagram, the baseband circuit 220 is shown as including a controller 222, a memory 224, and a signal processor 225.

[0098] However, in baseband circuit 220, two or more of the controller 222, memory 224, and signal processor 225 can be integrated into one. Additionally, baseband circuit 220 may include additional components other than those described above, or may not include some components. Furthermore, signal processor 225 may also include additional components other than those described above, or may not include some components.

[0099] However, in the embodiments of this disclosure, for ease of description, the baseband circuit 220 including the above configuration will be used as an example for description.

[0100] In some embodiments, the controller 222, storage 224, and signal processor 225 may be included in a single device. In other embodiments, the controller 222, storage 224, and signal processor 225 may be distributed and included in different devices (e.g., a distributed architecture).

[0101] Additionally, RFIC 210 and baseband circuitry 220 may include components known to those skilled in the art as shown in the accompanying drawings. Furthermore, the components may be implemented in a manner known to those skilled in the art, and may be implemented using hardware, firmware, software, or a combination thereof.

[0102] However, Figure 2 An example of a wireless communication device is illustrated, and embodiments of this disclosure are not limited thereto. That is, [the following can be done / implemented]... Figure 2 Make various changes (additions or deletions to various parts).

[0103] Here, for reference Figure 3 , showed Figure 2 An example of a wireless communication device 200 whose configuration has been partially altered (i.e. simplified).

[0104] For example, Figure 2 The wireless communication device 200 can be configured to include a processor 250, a transceiver 260, a memory 270, and an antenna 280, such as Figure 3 As shown.

[0105] Processor 250 can control the overall operation of transceiver 260 and can write or read data from memory 270. That is, processor 250 may include, for example... Figure 2 Configuration of the functions of controller 222.

[0106] Transceiver 260 can transmit and receive radio signals and can be controlled by processor 250. That is, transceiver 260 can include, for example... Figure 2 The components that enable the functions of FEM 205, RFIC 210 and signal processor 225.

[0107] Therefore, when the wireless communication device 200 is included in the transmitting device (that is, when the wireless communication device 200 performs the transmitting function), the transceiver 260 can generate a Physical Layer Convergence Protocol (PLCP) PPDU including a preamble and a payload, and send the generated PPDU to the receiving device.

[0108] On the other hand, when the wireless communication device 200 is included in the receiving device (i.e., when the wireless communication device 200 performs the receiving function), the transceiver 260 can receive a PPDU including a preamble and a payload from the transmitting device. Furthermore, the transceiver 260 can decode the payload based on the preamble of the received PPDU. That is, the transceiver 260 can decode the payload using an internal decoder (e.g., Figure 2 The signal processor 225 decoder decodes the preamble of the PPDU and decodes the payload of the PPDU based on the decoding result.

[0109] The memory 270 may store data such as basic programs, application programs, and setting information for the operation of the wireless communication device 200. Therefore, the memory 270 may store instructions and / or data related to the processor 250 and the transceiver 260. That is, the memory 270 may include, for example... Figure 2 The configuration of the functions of the storage 224.

[0110] Antenna 280 can be connected to transceiver 260 and can transmit signals received from transceiver 260 to another wireless communication device (terminal or base station), or provide signals received from another wireless communication device to transceiver 260. That is, antenna 280 can include, for example... Figure 2 The configuration of the antenna 190's functions.

[0111] In this manner, in embodiments of this disclosure, the wireless communication device 200 has the aforementioned features and configuration, and in the following, reference will be made to... Figures 4 to 11 This describes the HE trigger-based (TB) PPDU and trigger frame used in the IEEE standard (i.e., 802.11ax). Furthermore, it is based on reference... Figures 5 to 11 The described trigger frames will also include trigger frames supporting next-generation standards (e.g., 802.11be and subsequent standards) according to embodiments of this disclosure. For example, refer to... Figures 4 to 11 The described HE TB PPDU and trigger frames (including trigger frames according to embodiments of this disclosure) can be derived from... Figure 2 or Figure 3 The wireless communication device 200 is generated.

[0112] Figure 4This is a diagram illustrating the structure of a HE-triggered response (TB) PPDU as defined in 802.11ax. Figure 5 This is a diagram illustrating the structure of a trigger frame as defined in 802.11ax. Figure 6 It is a diagram. Figure 5 A diagram showing the structure of the public information fields. Figure 7 It is a diagram. Figure 6 A diagram of the trigger type subfield. Figure 8 It is a diagram. Figure 6 A graph of the uplink bandwidth subfield. Figure 9 It is a diagram. Figure 5 A diagram showing the structure of the user information fields. Figure 10 It is a diagram. Figure 9 A graph of the AID12 subfield. Figure 11 It is a diagram. Figure 9 A diagram of the RU allocation subfield.

[0113] First, refer to Figure 4 The HE TB PPDU may include a preamble and a payload. The preamble includes multiple training fields and multiple signaling fields, and the payload includes a data field and a packet extension.

[0114] For example, an HE TB PPDU may include a conventional short training field (L-STF) (8μs length), a conventional long training field (L-LTF) (8μs length), a conventional signal (L-SIG) (4μs length), a repetitive L-SIG (RL-SIG) (4μs length), a high-efficiency signal A (HE-SIG-A) (8μs length), a high-efficiency STF (HE-STF) (8μs length), a high-efficiency LTF (HE-LTF), DATA (i.e., the data field), and PE (i.e., the grouped extended field).

[0115] Here is a brief description of each field included in the preamble.

[0116] L-STF can include short training OFDM symbols and can be used for frame detection, automatic gain control (AGC), diversity detection, and coarse frequency / time synchronization.

[0117] L-LTF can include long-trained OFDM symbols and can be used for fine-grained frequency / time synchronization and channel prediction.

[0118] L-SIG can be used to send control information and can include information about the data rate and data length. For example, L-SIG can be sent repeatedly, and the format of repeating L-SIG is called RL-SIG.

[0119] HE-SIG-A may include control information common to the receiving device, such as the following.

[0120] 1) Downlink (DL) / Uplink (UL) Indicators

[0121] 2) BSS color field as an identifier for the Basic Service Set (BSS)

[0122] 3) A field indicating the remaining time of the current Transmission Opportunity (TXOP) period.

[0123] 4) Indicates whether it is a bandwidth field of 20 / 40 / 80 / 160 / 80+80MHz.

[0124] 5) Field indicating the number of signs in HE-LTF

[0125] 6) Fields indicating the length of the HE-LTF and the length of the Cyclic Prefix (CP).

[0126] 7) Indicates whether there is a field with additional OFDM symbols for low-density parity-check (LDPC) coding.

[0127] 8) Fields indicating control information regarding group expansion

[0128] 9) Field indicating information about the Cyclic Redundancy Check (CRC) field of HE-SIG-A

[0129] HE-SIG-A may also include various information in addition to 1) through 9) mentioned above, and in other examples, some of the information in 1) through 9) may be omitted.

[0130] HE-STF can be used to improve automatic gain control estimation in multiple-input multiple-output (MIMO) or OFDMA environments.

[0131] In addition, HE-LTF can be used to estimate channels in MIMO or OFDMA environments.

[0132] For example, the sizes of the FFT / IFFT applied to fields after HE-STF and the FFT / IFFT applied to fields before HE-STF can be different from each other. For example, the sizes of the FFT / IFFT applied to fields after HE-STF can be larger than the sizes of the FFT / IFFT applied to fields before HE-STF.

[0133] For this reason, the frequency bands used by fields preceding HE-STF and the frequency bands used by fields following HE-STF and HE-STF may not precisely match the boundary surface. However, for ease of explanation, in Figure 4 In this context, the frequency bands used by fields preceding HE-STF and the frequency bands used by fields following HE-STF and HE-STF are represented as identical.

[0134] Next, each field included in the net load will be briefly described.

[0135] The data field may include data specific to at least one user in the Physical Layer Service Data Unit (PSDU) for at least one user.

[0136] In the frequency domain of the data field, at least one RU including different numbers of tones (i.e., subcarriers) can be arranged based on the RU allocation information included in the signaling field of the preamble.

[0137] Packet extensions have durations of 4μs, 8μs, 12μs, or 16μs and can provide additional receive processing time at the end of the HE TB PPDU.

[0138] In this way, each field of the preamble and payload of the HE TB PPDU can be configured.

[0139] For example, for an uplink (UL) transmission operation to be performed in the frequency domain by each of one or more STAs (e.g., non-AP STAs), the AP may allocate different frequency resources as uplink transmission resources for each of the one or more STAs based on OFDMA. Here, frequency resources may refer to resource units (RUs), and this frequency resource may be indicated by a trigger frame sent from the AP to the STA prior to the uplink transmission operation.

[0140] Therefore, the trigger frame is used Figure 4 HE TB PPDU sent. Figure 5 The diagram illustrates such a trigger frame, which can be sent from the AP to the STA. The trigger frame may include RU allocation information indicating the RU allocated for uplink multi-user (MU) transmission. The trigger frame may be a Media Access Control (MAC) frame included in the PPDU. For example, the trigger frame may be included in the data field of the PPDU.

[0141] The trigger frame may include a MAC header, a frame body, and a Frame Check Sequence (FCS) field (with 4 or more octets). Here, the MAC header may include a frame control field (2 octets), a duration field (2 octets), a receiver address (RA) field (6 octets), and a transmitter address (TA) field (6 octets). The frame body may include a Common Info field (8 or more octets), a User InfoList field (with multiple user information fields, each including UserInfo with 5 or more octets), and a Padding field (with variable octets).

[0142] Briefly, the frame control field includes information about the MAC protocol version and other additional control information. The duration field may include time information for setting the network allocation vector (NAV) or information about the terminal's identifier (e.g., association ID (AID)). The RA field includes the address information of the receiving device (e.g., STA) corresponding to the trigger frame (this field may be omitted). The TA field may include the address information of the device that sent the trigger frame (e.g., AP), and the Common Info field may include common control information applicable to the receiving device receiving the corresponding trigger frame.

[0143] The trigger frame may include a User Info field corresponding to the number of receiving devices receiving the trigger frame. For example, the user information field may be referred to as the "RU allocation field". In addition, the trigger frame may include a padding field and a Frame Check Sequence (FCS) field.

[0144] In other examples, some fields of the trigger frame may be omitted, and other fields may be added. Additionally, the length of each field may differ from the lengths shown in other examples.

[0145] Figure 6 Illustration Figure 5The following is an example structure for the Common Info field. Here, the Common Info field may include various subfields such as: "Trigger Type," "UL Length," "More TF," "CS Required," "UL BW," "GI And HE-LTF Type," and "MU-MIMO HE-LTF mode," etc., where each subfield can be a subfield defined in the 802.11ax standard. In other examples, some subfields in the Common Info field may be omitted, and other subfields may be added. Additionally, the length of each subfield may differ from the length shown.

[0146] For example, refer to Figure 7 , showed Figure 6 The specific table for the Trigger Type subfield. For example... Figure 7 As shown, the TriggerType subfield can indicate the type of the corresponding trigger frame using any value from 0 to 15. For example, if the value of the TriggerType subfield is "0", the corresponding trigger frame can be indicated as a "basic trigger frame (e.g., a trigger frame that supports the 802.11ax standard)".

[0147] For example, values ​​8 to 15 in the Trigger Type subfield are reserved values ​​and do not indicate the type of trigger frame. However, in embodiments of this disclosure, although... Figure 7 Not shown, but any value from 8 to 15 (e.g., 8) of the “Trigger Type” subfield can be assigned and used as a value indicating a trigger frame that supports a next-generation standard (e.g., the 802.11be standard as the next generation of 802.11ax). Similarly, in embodiments of this disclosure, any one of 9 to 15 of the “Trigger Type” subfield can be assigned and used as a value (e.g., 9) indicating a trigger frame that supports a newer, non-traditional standard (e.g., the next-generation standard “802.11be+” of the 802.11be standard), the details of which will be described later.

[0148] In some embodiments, the Trigger Type subfield may have a predefined value for next-generation standards. For example, the value "8" in the "Trigger Type" subfield is not... Figure 7The values ​​shown are reserved values, but can be predefined values ​​that are valid for devices based on any next-generation standard, and can represent trigger frames used for next-generation standards. Therefore, devices based on legacy standards (e.g., 802.11be) can recognize that a trigger frame with a "Trigger Type" subfield of "8" is based on a next-generation standard (e.g., a standard after 802.11be) and will not use the information included in the trigger frame.

[0149] refer to Figure 8 , showed Figure 6 The specific table for the "UL BW" subfield among the above subfields. The "UL BW" subfield may have an indication Figure 4 The corresponding bandwidth information (i.e., the total bandwidth information to be used for uplink transmission of the HE TBPPDU) included in the HE-SIG-A of the HE TBPPDU shown is 0 to 3.

[0150] For example, when the value of the “UL BW” subfield is “0”, it indicates that the total bandwidth to be used for uplink transmission of the HE TB PPDU is “20MHz”. Conversely, when the value of the “UL BW” subfield is “1”, it indicates that the total bandwidth to be used for uplink transmission of the HE TB PPDU is “40MHz”.

[0151] For example, the trigger frame according to embodiments of this disclosure may support the 802.11be standard and newer standards (e.g., the 802.11be+ standard), the 802.11be standard being a next-generation standard relative to 802.11ax and earlier standards. Therefore, although not shown in the figures, in embodiments of this disclosure, the “UL BW” subfield may have an indication of, in addition to, Figure 8 Two or more bits of bandwidth other than the bandwidth shown (e.g., 320MHz). As stated above, in this document, a device that supports a previous rather than the latest standard (e.g., HE) may be referred to as a legacy device, and a device that supports a newer standard (e.g., the current or “next-generation” standard (e.g., EHT or later)) may be referred to as a non-legacy device or a next-generation device.

[0152] At least one trigger frame according to an embodiment of this disclosure will be described later, taking into account such characteristics.

[0153] Here, for reference Figure 9 , showed Figure 5 The structure of the User Info field for user information.

[0154] For example, user information fields may include various subfields such as the following: “AID12” subfield, “RUAllocation” subfield, “UL FEC Coding Type” subfield, “UL HE-MCS” subfield, “UL DCM” subfield, “SS Allocation / RA-RU Information” subfield, “UL Target RSSI” subfield, etc., and each subfield may be a subfield defined in the 802.11ax standard.

[0155] In other examples, some subfields of the user information field may be omitted, and other subfields may be added. Additionally, the length of each subfield may differ from the lengths shown in other examples.

[0156] For example, refer to Figure 10 This shows the specific table for the "AID12" subfield among the above subfields, and refers to... Figure 11 This shows the specific table for the "RU Allocation" subfield among the above subfields.

[0157] For example, such as Figure 10 As shown, the "AID12" subfield indicates the identifier of the STA used to transmit the uplink. The value of the "AID12" subfield can indicate different content for each interval.

[0158] For example, if the value of the "AID12" subfield is "0", it indicates that "the User Info field assigns one or more consecutive RA-RUs to the associated STA". When the value of the "AID12" subfield is any one of 1 to 2007, it indicates that "the User Info field is addressed to the associated STA whose AID is equal to the value in the AID12 subfield".

[0159] Here, values ​​2008 to 2044 and 2047 to 4094 in the “AID12” subfield are reserved values ​​and do not indicate the STA's identifier. However, in embodiments of this disclosure, although not shown in the figures, when any of 2008 to 2044 and 2047 to 4094 (e.g., 2008) is assigned as a value of the “AID12” subfield, the EHT STA may interpret the information following the “AID12” subfield as an EHT public information field. In this case, the remaining 28 bits in the user information field excluding the “AID12” subfield can be configured to include the EHT public information field. For example, the newly configured EHT public information field may include a UL BW subfield supporting 320MHz bandwidth.

[0160] For example, 28 bits may not be enough to configure the actual EHT public information field. In this case, the AP can configure a separate user information field in the same way as described above (i.e., assign 2008 to the "AID12" subfield, and the remaining 28 bits constitute the EHT public information field), and allocate the remaining 28 bits to the EHT STA.

[0161] Similarly, in embodiments of this disclosure, when another value among 2008 to 2044 and 2047 to 4094 (e.g., 2010) is assigned as the value of the “AID12” subfield, the EHT STA can interpret the information following the “AID12” subfield as the EHT user information field. In this case, the remaining 28 bits of the user information field, excluding the “AID12” subfield, can be configured to include the EHT user information field. That is, for example, the first 12 bits of the 28 bits can be used as a new AID subfield to indicate the AID of the actual EHT STA, and the remaining 16 bits can be configured to include the EHT STA's user information.

[0162] For example, 28 bits may not be enough to configure the actual EHT user information field. In this case, the AP can configure a separate user information field in the same way as described above (i.e., assign 2010 to the "AID12" subfield, and the remaining 28 bits constitute the EHT user information field), and allocate the remaining 28 bits to the EHT STA.

[0163] At least one trigger frame according to an embodiment of this disclosure will be described later, taking into account such characteristics.

[0164] In some embodiments, the "AID12" subfield may have a predefined value for next-generation standards. For example, the value "2047" in the "AID12" subfield is not... Figure 10 The values ​​shown are reserved values, but can be predefined values ​​valid for devices based on any next-generation standard, and can indicate fields used in the next-generation standard. Therefore, devices based on legacy standards (e.g., 802.11be) can identify fields where the "AID12" subfield is "2047" (e.g., public information fields or user information fields) are based on any next-generation standard (e.g., standards after 802.11be) and will not use the information included in this field. Similarly, the value "2007" in the "AID12" subfield is not... Figure 10 The value addressed to the STA can be a predefined value that is valid for any device based on a next-generation standard, and can indicate the field used for the next-generation standard.

[0165] Meanwhile, in the value of the "AID12" subfield, 4095 is the value indicating "Start of Padding field" and indicates the start of the padding field. However, in embodiments of this disclosure, although in Figure 10 Not shown, but if 4095 is assigned as the value of the "AID12" subfield, then the EHT STA (or EHT+STA (i.e., STA supporting standards following EHT)) can interpret the information following the corresponding user information field (i.e., the user information field where the value of the "AID12" subfield is "4095") as the EHT public information field and the EHT user information field. In this case, since it is not necessary to utilize the existing user information field, the EHT public information field and the EHT user information field can be redefined without limiting the number of bits.

[0166] For example, if needed or necessary, a fill field for EHT STA can be added after the EHT user information field, and the start of the added fill field can be indicated by assigning a reserved value (e.g., 4094) in the value of the “AID12” subfield.

[0167] At the same time, such as Figure 11 As shown, the "RU Allocation" subfield indicates the RU information allocated to the STA for uplink transmission. For example, the "RU Allocation" subfield may include 8 bits, one of which can have a different purpose depending on the value of the "UL BW" subfield in the common information field. For instance, when "UL BW" is 80+80MHz or 160MHz and this bit is "0", the "RU Allocation" subfield may indicate the primary 80MHz. On the other hand, when "UL BW" is 80+80MHz or 160MHz and this bit is "1", the "RU Allocation" subfield may indicate the secondary 80MHz. In other cases, this bit can always be set to 0. Additionally, the remaining 7 bits of the "RU Allocation" subfield can be used together with the "ULBW" subfield to specify the RU index.

[0168] For example, the trigger frames according to embodiments of this disclosure may support the 802.11be standard and standards following 802.11be, which are examples of next-generation (non-traditional) standards relative to 802.11ax. Therefore, although in Figure 11 Not shown in the diagram, but in embodiments of this disclosure, the “RU Allocation” subfield may have eight or more bits, which, in addition to indicating… Figure 11In addition to the bandwidth information shown, RU allocation information based on a bandwidth such as 320MHz is also indicated. At least one trigger frame according to an embodiment of this disclosure will be described later, taking into account such characteristics.

[0169] In this way, the trigger frames according to embodiments of the present disclosure can support next-generation standards (e.g., 802.11be) and subsequent standards, and can be configured as described above. Furthermore, the trigger frames according to embodiments of the present disclosure can trigger uplink transmissions of FD A-PPDUs (Frequency Division Aggregated PPDUs) including multiple PPDUs supporting the same or different standards based on the above configuration.

[0170] For example, the embodiments of this disclosure are applicable not only to the case where the AP sends a trigger frame to the STA, but also to the case where the STA sends a trigger frame to another STA.

[0171] Based on the characteristics of the trigger frame, in the following text, refer to Figure 12 The process of transmitting FD A-PPDU via an uplink through a trigger frame according to embodiments of the present disclosure will be described.

[0172] Figure 12 This is a schematic diagram illustrating the uplink transmission process of an FD A-PPDU via a trigger frame according to an embodiment of the present disclosure. First, a transmitting device (e.g., an AP) can generate a PPDU including a trigger frame according to an embodiment of the present disclosure and transmit the generated PPDU to multiple receiving devices, each of which may support the same or different standards. Figure 12 The following discussion uses STA1, STA2, and STA3 as examples of receiving devices.

[0173] Here, the trigger frame may include information about STA1 to STA3 to which the transmitting device (e.g., AP) intends to trigger uplink transmission, as well as allocation information of the RU to be used by the corresponding receiving device when transmitting signals via the uplink.

[0174] Upon receiving the trigger frame, each of STA1 to STA3 can check whether the RU for uplink transmission has been assigned to it. When an uplink transmission is assigned to any of STA1 to STA3, the uplink transmission can be performed using the RU assigned to that STA based on the information included in the trigger frame. The PPDU type used for this uplink transmission can be a TBPPDU, and the TB PPDUs (Sub-PPDU-1 to Sub-PPDU-3) transmitted via the uplink by STA1 to STA3 respectively can differ from each other depending on the supported standards. Furthermore, STA1 to STA3 can send TB PPDUs (Sub-PPDU-1 to Sub-PPDU-3) in the form of FD A-PPDUs to simultaneously transmit TB PPDUs (Sub-PPDU-1 to Sub-PPDU-3) supporting different standards via the uplink on the time axis without overlapping on the frequency axis.

[0175] For example, the trigger frame according to an embodiment of the present disclosure has a configuration that can simultaneously support different standards (e.g., 802.11ax, 802.11be and later standards), enabling the transmission of TB PPDUs (Sub-PPDU-1 to Sub-PPDU-3) supporting different standards in the form of FD A-PPDUs.

[0176] Additionally, when the uplink transmission of each of the receiving devices (STA1 to STA3) is completed, the transmitting device AP may send a PPDU including a block acknowledgment (Ack) frame (Multi-STA Block ACK) to the receiving device (at least one of STA1 to STA3) that performed the corresponding transmission for the successfully received uplink transmission.

[0177] In this manner, FD A-PPDU is transmitted via the uplink through a trigger frame according to an embodiment of the present disclosure, and hereinafter, reference is made to... Figures 13 to 16 Various examples of trigger frames according to embodiments of the present disclosure will be described in detail.

[0178] Figure 13 This is a diagram illustrating an example of a trigger frame according to an embodiment of the present disclosure. Figure 14 This is a diagram illustrating another example of a trigger frame according to an embodiment of the present disclosure. Figure 15 It is a diagram. Figure 14 A diagram illustrating an example structure of the EHT user information field. Figure 16 This is a diagram illustrating another example of a trigger frame according to an embodiment of the present disclosure.

[0179] For example, refer to Figures 13 to 16 The described trigger frame can be generated by Figure 2 and Figure 3The wireless communication device 200 shown in the diagram is generated. Furthermore, for ease of explanation, in... Figures 13 to 16 In this paper, it is assumed and described that three receiving devices (e.g., HE(802.11ax)STA generating HE TBPPDU, EHT(802.11be)STA generating EHT TBPPDU, and EHT+(standard after 802.11be)STA generating EHT+TBPPDU) receive trigger frames, and 80MHz, 80MHz and 160MHz are respectively allocated to the three receiving devices (HE STA, EHT STA and EHT+STA) (e.g., the primary 80MHz is allocated to HE STA, the secondary 80MHz is allocated to EHT STA and the secondary 160MHz is allocated to EHT+STA).

[0180] First, refer to Figure 13 An example of a trigger frame TF1 according to an embodiment of this disclosure is shown. Figure 13 In this case, to trigger the first receiving device HE STA, the second receiving device EHT STA, and the third receiving device EHT+STA using a single PPDU, the transmitting device AP can use trigger frame TF1 in the form of an aggregated MAC protocol data unit (A-MPDU). In this case, although not shown in the accompanying drawings, the reference can be reflected in the second trigger frame 2 and the third trigger frame 3. Figures 5 to 11 The characteristics of the next-generation standards (802.11be and 802.11be+ standards) described below (e.g., the ability to indicate a "UL BW" subfield at 320MHz) will be discussed in detail below.

[0181] For example, trigger frame TF1 may be included in the data field of the PPDU payload. In addition, trigger frame TF1 may include different first trigger frames Trigger Frame 1, second trigger frame 2, and third trigger frame 3, which are respectively aggregated in the form of aggregated MAC protocol data units (A-MPDU).

[0182] Trigger Frame 1 can trigger uplink transmission of the first receiving device HE STA, while Trigger Frame 2 can trigger uplink transmission of the second receiving device ETH STA. Trigger Frame 3 can trigger uplink transmission of the third receiving device EHT+STA.

[0183] Here, Trigger Frame 1 includes a first Media Access Control (MAC) header, a first frame body, and a first FCS field; Trigger Frame 2 may include a second MAC header, a second frame body, and a second FCS field; and Trigger Frame 3 may include a third MAC header, a third frame body, and a third FCS field.

[0184] In addition, the public information field of the first frame body (i.e., Figure 5 The trigger type subfield in the Common Info (i.e., Figure 6 The value of the “Trigger Type” subfield can be different from the value of the trigger type subfield in the common information field of each of the second and third frame bodies.

[0185] For example, the value of the trigger type subfield of each of the second frame body and the third frame body can be assigned in various ways, and there can be exemplary assignment methods as follows.

[0186] For example, given that the trigger type subfield consists of 4 bits, the most significant bit (MSB) of those 4 bits can be used to indicate each standard (EHT standard and EHT+ standard). That is, when the trigger frame type is "HEBasic", the 4 bits can be "0000", while when the trigger frame type is "EHT+Basic", the 4 bits can be "1000".

[0187] Additionally, for example, specific values ​​in the trigger type subfield can be used to indicate each standard (EHT standard and EHT+ standard). That is, in 802.11ax, one of the reserved values ​​(i.e., 8 to 15) (e.g., 8) can be used to indicate that the corresponding trigger frame supports the EHT standard. Conversely, another reserved value (i.e., 8 to 15) in 802.11ax (e.g., 9) can be used to indicate that the corresponding trigger frame supports the EHT+ standard. In this case, Figure 7 The value "10 to 15" of the "Trigger Type" subfield can be used to indicate retention.

[0188] For example, for ease of description, in the embodiments of this disclosure, the second assignment method (i.e., a specific value in the trigger type subfield is used to indicate each standard (EHT standard and EHT+ standard)) will be used as an example for description.

[0189] If this second assignment method is used, the value of the trigger type subfield of the second frame body may include a value (e.g., 8) corresponding to any of the values ​​indicated as reserved in the trigger type subfield of the first frame body (i.e., values ​​indicated as reserved in 802.11ax (e.g., 8 to 15)), and indicates that Trigger Frame 2 is a trigger frame supporting the EHT standard. The value of the trigger type subfield of the third frame body may include a value (e.g., 9) corresponding to another value indicated as reserved in the trigger type subfield of the first frame body (i.e., values ​​indicated as reserved in 802.11ax (e.g., 8 to 15)), and indicates that Trigger Frame 3 is a trigger frame supporting the EHT+ standard.

[0190] For example, Trigger Frame 2 and Trigger Frame 3 (supporting the EHT and EHT+ standards respectively) can support higher versions of the standard than Trigger Frame 1 (supporting the HE standard). Therefore, even if Trigger Frame TF1 is received, the HE STA will only interpret the trigger type subfield values ​​(e.g., 8 and 9) of the second and third frame bodies as reserved, and not as values ​​indicating that the trigger frames support the EHT and EHT+ standards respectively. Therefore, upon receiving Trigger Frame TF1, the HE STA may only interpret Trigger Frame 1 as the trigger frame assigned to itself, and interpret Trigger Frame 2 and Trigger Frame 3 as invalid.

[0191] Therefore, when the value of the trigger type subfield of the second frame body is 8, the HE STA can interpret this value (i.e., 8) as reserved, while the EHT+STA can interpret the corresponding value (i.e., 8) as either reserved or as a trigger frame that supports the EHT standard. The EHT STA can interpret the corresponding value (i.e., 8) as a trigger frame that supports the EHT standard.

[0192] Following the same principle, if the value of the trigger type subfield of the third frame body is 9, then the HE STA can interpret this value (i.e., 9) as reserved, while the EHT STA can interpret the corresponding value (i.e., 9) as either reserved or as a trigger frame supporting the EHT+ standard. The EHT+ STA can interpret the corresponding value (i.e., 9) as a trigger frame supporting the EHT+ standard.

[0193] Therefore, when the transmitting device (e.g., AP) sends data to three receiving devices, HE STA, EHT STA, and EHT+STA... Figure 13When trigger frame TF1 is shown, the receiving devices HE STA, EHT STA, and EHT+STA can all interpret the trigger frame based on the standard supported by each receiving device and transmit each TB PPDU uplink to the AP.

[0194] In other examples, as an alternative, the trigger frame TF1 can be configured in other ways. For instance, a separate subfield (e.g., a protocol subfield) for distinguishing between the EHT standard and the EHT+ standard can be added to the common information field of each of TriggerFrame 2 and Trigger Frame 3. Alternatively, a 0 for the EHT standard or a 1 for the EHT+ standard can be assigned to the corresponding subfield (i.e., the protocol subfield).

[0195] For example, when the value of the "Protocol Subfield" in the public information field of Trigger Frame 2 is 0, this value (i.e., 0) indicates that Trigger Frame 2 is a trigger frame that supports the EHT standard. On the other hand, when the value of the "Protocol Subfield" in the public information field of Trigger Frame 2 is 1, the corresponding value (i.e., 1) indicates that Trigger Frame 2 is a trigger frame that supports the EHT+ standard.

[0196] In some embodiments, even in this case, the value of the trigger type subfield in the public information field of the first frame body may differ from the value of the trigger type subfield in the public information field of each of the second and third frame bodies. In some embodiments, the value of the trigger type subfield in the public information field of each of the second and third frame bodies may be the same. That is, the value of the trigger type subfield of each of the second and third frame bodies may include a value (e.g., 8) corresponding to any of the values ​​indicating a reserved value in the trigger type subfield of the first frame body (i.e., values ​​indicating a reserved value in the trigger type subfield of the first frame body (e.g., 8 to 15)).

[0197] Therefore, when the value of the trigger type subfield in the second frame body is 8 and the value of the protocol subfield is 0, HESTA can interpret the value of the trigger type subfield (i.e., 8) as reserved. Additionally, both EHT+STA and EHT STA can interpret the combination of the trigger type subfield value (i.e., 8) and the protocol subfield value (i.e., 0) as a trigger frame supporting the EHT standard.

[0198] Based on the same principle, when the value of the trigger type subfield in the third frame body is 8 and the value of the protocol subfield is 1, HE STA can interpret the value of the trigger type subfield (i.e., 8) as reserved. Furthermore, both EHT+ STA and EHT STA can interpret the combination of the trigger type subfield value (i.e., 8) and the protocol subfield value (i.e., 1) as a trigger frame supporting the EHT+ standard.

[0199] Therefore, when the AP sends data to the three receiving devices HE STA, EHT STA, and EHT+STA... Figure 13 When trigger frame TF1 is shown, each receiving device can perform uplink transmission of each TBPPDU to the AP based on the standard interpretation trigger frame supported by each receiving device.

[0200] Next, refer to Figure 14 This illustrates another example of a trigger frame TF2 according to an embodiment of the present disclosure. Figure 14 In the case where a single PPDU is used to trigger the first receiving device HE STA, the second receiving device EHT STA, and the third receiving device EHT+STA, the trigger frame is configured in the form of a single MAC Protocol Data Unit (S-MPDU) by extending the common information field and the user information field by indicating the value of the reserved "AID12" subfield. That is, to indicate the common information field and the user information field for the second receiving device EHT STA and the third receiving device EHT+STA respectively, a specific value (e.g., an indicated reserved value) from the "AID12" subfield can be used. Similarly, in a different manner, the common information field and the user information field for the second receiving device EHT STA and the third receiving device EHT+STA may each include protocol subfields, the details of which will be described below.

[0201] For example, trigger frame TF2 can be included in the payload of the PPDU (i.e., the data field of the payload). Alternatively, trigger frame TF2 can include a trigger frame in the form of a Single MAC Protocol Data Unit (S-MPDU).

[0202] For example, trigger frame TF2 can trigger uplink transmission of the first receiving device HE STA, the second receiving device EHT STA, and the third receiving device EHT+STA.

[0203] Here, the trigger frame TF2 may include the MAC header, frame body, and FCS field.

[0204] Specifically, the frame body may include a public information field, multiple user information fields (e.g., UIF1 to UIF5), and a padding field.

[0205] For example, the Common Info field may include common control information applied to the first receiving device HE STA. Additionally, the first user information field UIF1 among the multiple user information fields UIF1 to UIF5 may include user-specific control information (User Info) applied to the first receiving device HE STA. Furthermore, among the multiple user information fields UIF1 to UIF5, the second user information field UIF2 and the third user information field UIF3 can be used as a common information field (i.e., EHT Common Info) and a user information field (i.e., EHT User Info) applied to the second receiving device EHT STA, respectively. Furthermore, among the multiple user information fields UIF1 to UIF5, the fourth user information field UIF4 and the fifth user information field UIF5 can be used as a common information field (i.e., EHT+Common Info) and a user information field (i.e., EHT+User Info) applied to the third receiving device EHT+STA, respectively.

[0206] For example, the order of the common information field (i.e., EHT CommonInfo) and user information field (i.e., EHT User Info) applied to the second receiving device EHT STA and the common information field (i.e., EHT+Common Info) and user information field (i.e., EHT+User Info) applied to the third receiving device EHT+STA can be changed. However, for the sake of explanation, the order will be... Figure 14 The order shown is used as an example for description.

[0207] In addition, although Figure 14 The example shown has five user information fields, but other examples use more or fewer. Therefore, when there are additional receiving devices besides the three, there could also be user information fields for each additional receiving device. The case with five user information fields will be described as an example to illustrate the principles of the inventive concept.

[0208] The value of the identifier subfield in the second user information field UIF2 includes the value of the identifier subfield in the first user information field UIF1 (i.e., indicating...). Figure 9 The "AID12" subfield indicates the value to be retained (e.g., Figure 10 The value corresponding to any one of the values ​​in 2008 to 2044 and 2047 to 4094 (e.g., 2008) and may indicate that the second user information field UIF2 includes a common information field (i.e., EHT common Info) applied to the second receiving device EHT STA.

[0209] Here, the second user information field UIF2 is configured using the existing user information field format (i.e., the user information field format of the 802.11ax trigger frame), and the length of the second user information field UIF2 can be the same as the length of the existing user information field. Therefore, the second user information field UIF2 includes 40 bits (i.e., 5 bytes), and 12 bits of the second user information field UIF2 can constitute an identifier subfield, and the remaining 28 bits of the second user information field UIF2 can constitute a common information field (i.e., EHT Common Info) applied to the second receiving device EHT STA.

[0210] However, when the remaining 28 bits of the second user information field UIF2 are less than the number of bits required to include the common information field applied to the second receiving device EHT STA, an additional user information field (not shown) among the multiple user information fields, in addition to the second user information field UIF2, may also be used as a common information field applied to the second receiving device EHT STA.

[0211] For example, the second user information field UIF2 and the additional user information field (not shown) each comprise 40 bits, and 12 bits of each of the second user information field UIF2 and the additional user information field may each comprise an identifier subfield with the same value (e.g., 2008). Additionally, the remaining 28 bits of each of the second user information field UIF2 and the additional user information field can be configured by partitioning the common information field applied to the second receiving device EHT STA.

[0212] For example, in the accompanying drawings, for ease of description, the second user information field UIF2 is shown without being divided into a 12-bit identifier subfield and a 28-bit public information field.

[0213] Subsequently, the value of the identifier subfield in the third user information field UIF3 includes the value indicated as reserved in the identifier subfield of the first user information field UIF1 (e.g., Figure 10 The value corresponding to any one of the values ​​in 2008 to 2044 and 2047 to 4094 (e.g., 2010, which is an unused value in the second user information field UIF2) and may indicate that the third user information field UIF3 includes the user information field (i.e., EHT UserInfo) applied to the second receiving device EHT STA.

[0214] Here, the third user information field UIF3 is also configured using the existing user information field format (i.e., the user information field format of the 802.11ax trigger frame), and the length of the third user information field UIF3 can be the same as the length of the existing user information field. Therefore, the third user information field UIF3 can include 40 bits (i.e., 5 bytes). And, as... Figure 15 As shown, the first 12 bits of the third user information field UIF3 can constitute the first identifier subfield, the next 12 bits of the third user information field UIF3 can constitute the second identifier subfield, and the remaining 16 bits of the third user information field UIF3 can constitute the user information field applied to the second receiving device EHT STA (i.e., Figure 14 (EHT User Info).

[0215] More specifically, the first identifier subfield (i.e., AID 2010) may be an identifier subfield used to indicate that the third user information field UIF3 includes a user information field (i.e., EHT User Info) applied to the second receiving device EHT STA. Additionally, the second identifier subfield (i.e., (ETH)AID) may be an identifier subfield used to indicate the identifier of the actual second receiving device EHT STA.

[0216] However, if the remaining 16 bits of the third user information field UIF3 are less than the number of bits required to include the user information field applied to the second receiving device EHT STA, then an additional user information field (not shown) among the multiple user information fields, in addition to the third user information field UIF3, may also be used as the user information field applied to the second receiving device EHT STA.

[0217] For example, the third user information field UIF3 and the additional user information field (not shown) each comprise 40 bits, and the first 12 bits of each of the third user information field UIF3 and the additional user information field can each be configured with a first identifier subfield having the same value (e.g., 2010). Furthermore, the next 12 bits of each of the third user information field UIF3 and the additional user information field (not shown) can include a second identifier subfield having the same value, and the remaining 16 bits of each of the third user information field UIF3 and the additional user information field (not shown) can be configured by dividing the user information field applied to the second receiving device EHT STA.

[0218] The first identifier subfield of each of the third user information field UIF3 and the additional user information field (not shown) may indicate that each of the third user information field UIF3 and the additional user information field includes a user information field applicable to the second receiving device EHT STA. Additionally, the second identifier subfield of each of the third user information field UIF3 and the additional user information field may indicate the identifier of the actual second receiving device EHT STA.

[0219] For example, in Figure 14 For the sake of convenience, the text is not as... Figure 15 The image shows the third user information field, UIF3.

[0220] Meanwhile, the fourth user information field UIF4 is configured in the same manner as the second user information field UIF2 described above, and is used as a common information field (i.e., EHT+Common Info) applied to the third receiving device EHT+STA. The value of the identifier subfield of the fourth user information field UIF4 may include a value indicated by the reserved value in the identifier subfield of the first user information field UIF1 (e.g., Figure 10 The values ​​in 2008 to 2044 and 2047 to 4094 that are different from the values ​​used in the second user information field UIF2 and the third user information field UIF3 (e.g., 2012) indicate that the fourth user information field UIF4 includes a common information field (i.e., EHT+Common Info) applied to the third receiving device EHT+STA.

[0221] Furthermore, the fifth user information field UIF5 can be configured in the same manner as the third user information field UIF3 described above and used as a user information field applied to the third receiving device EHT+STA (i.e., EHT+User Info). The value of the identifier subfield of the fifth user information field UIF5 may include a value indicated by the reserved value in the identifier subfield of the first user information field UIF1 (e.g., Figure 10 The values ​​in 2008 to 2044 and 2047 to 4094 that are different from the values ​​used in the second user information fields UIF2 to the fourth user information fields UIF4 (e.g., 2014) indicate that the fifth user information field UIF5 includes the user information field applied to the third receiving device EHT+STA (i.e., EHT+User Info).

[0222] As mentioned above, due to the configuration Figure 14Because of the trigger frame TF2, the HE STA must interpret the second user information fields UIF2 through UIF5 as the 802.11ax standard. Therefore, even if the HE STA receives the trigger frame TF2, the identifier subfield values ​​(e.g., 2008, 2010, 2012, and 2014) of the second user information fields UIF2 through UIF5 are only interpreted as reserved and cannot be interpreted as identifiers indicating the common information fields and user information fields respectively applied to the second receiving device EHT STA and the third receiving device EHT+STA. Therefore, upon receiving the trigger frame TF2, the HE STA can interpret the Common Info field after the MAC header and the first user information field UIF1 as fields relevant to themselves, and interpret the second user information fields UIF2 through UIF5 as reserved.

[0223] Therefore, for example, if the value of the identifier subfield in the user information field is 2008, the HE STA can interpret that value (i.e., 2008) as reserved, while the EHT+STA can interpret the corresponding value (i.e., 2008) as reserved or as an identifier indicating a public information field for the EHT STA. The EHT STA can interpret the value (i.e., 2008) as an identifier indicating a public information field for the EHT STA.

[0224] Similarly, for example, if the value of the identifier subfield in the user information field is 2012, the HE STA can interpret that value (i.e., 2012) as reserved, while the EHT STA can interpret the corresponding value (i.e., 2012) as reserved or as an identifier indicating a public information field for the EHT+STA. The EHT+STA can interpret the corresponding value (i.e., 2012) as an identifier indicating a public information field for the EHT+STA.

[0225] Using the same principle, for example, if the value of the identifier subfield in the user information field is 2010, then HE STA can interpret this value (i.e., 2010) as reserved, while EHT+STA can interpret the corresponding value (i.e., 2010) as either reserved or as an identifier indicating the user information field used by EHT STA. Note that EHT STA can interpret the corresponding value (i.e., 2010) as an identifier indicating the user information field used by EHT STA.

[0226] Similarly, for example, if the value of the identifier subfield in the user information field is 2014, the HE STA can interpret that value (i.e., 2014) as reserved, while the EHT STA can interpret the corresponding value (i.e., 2014) as either reserved or as an identifier indicating the user information field used by the EHT+STA. The EHT+STA can interpret the corresponding value (i.e., 2014) as an identifier indicating the user information field used by the EHT+STA.

[0227] Therefore, when the AP sends data to the three receiving devices HE STA, EHT STA, and EHT+STA... Figure 14 When trigger frame TF2 is shown, the receiving devices HE STA, EHT STA, and EHT+STA can all transmit each TB PPDU uplink to the AP based on the value of the standard interpretation identifier subfield supported by each receiving device.

[0228] In other examples, the trigger frame TF2 can be configured in other ways. For instance, when the value of the identifier subfield in a particular user information field among multiple user information fields is any one of the reserved values ​​(i.e., 2008) indicated in 802.11ax (i.e., 2008 to 2044 and 2047 to 4094), the trigger frame TF2 can be configured such that both the second receiving device EHT STA and the third receiving device EHT+STA interpret the corresponding particular user information field as their own common information field. That is, any one of the values ​​of the identifier subfield (i.e., 2008) can be used collectively as the value of the common information field indicating the receiving devices (e.g., EHT STA and EHT+STA) that support different standards.

[0229] Additionally, separate subfields (e.g., protocol subfields) can be added to specific user information fields to separate the EHT standard and the EHT+ standard. Furthermore, 0s for the EHT standard or 1s for the EHT+ standard can be assigned to the corresponding subfields (i.e., protocol subfields).

[0230] For example, when the value of a protocol subfield in a specific user information field is 0, the corresponding value (i.e., 0) indicates that the specific user information field is used as a public information field for EHT STA. On the other hand, when the value of a protocol subfield in a specific user information field is 1, the corresponding value (i.e., 1) indicates that the specific user information field is used as a public information field for EHT+STA.

[0231] Therefore, if the value of the identifier subfield in the user information field is 2008 and the value of the protocol subfield is 0, then HE STA can interpret the value of the identifier subfield (i.e., 2008) as reserved. Additionally, both EHT+STA and EHT STA can interpret the combination of the value of the identifier subfield (i.e., 2008) and the value of the protocol subfield (i.e., 0) as an indication of the combination of public information fields used by EHT STA.

[0232] Similarly, if the value of the identifier subfield in a particular user information field is 2008 and the value of the protocol subfield is 1, then HE STA may interpret the value of the identifier subfield (i.e., 2008) as reserved. Additionally, both EHT+STA and EHT STA may interpret the combination of the value of the identifier subfield (i.e., 2008) and the value of the protocol subfield (i.e., 1) as an indication of a combination of public information fields used by EHT+STA.

[0233] Based on the same principle, if the value of the identifier subfield in a specific user information field is 2010 and the value of the protocol subfield is 0, then HE STA can interpret the value of the identifier subfield (i.e., 2010) as reserved. Additionally, both EHT+STA and EHT STA can interpret the combination of the value of the identifier subfield (i.e., 2010) and the value of the protocol subfield (i.e., 0) as an indication of the combination of user information fields used by EHT STA.

[0234] Similarly, if the value of the identifier subfield in a particular user information field is 2010 and the value of the protocol subfield is 1, then HE STA may interpret the value of the identifier subfield (i.e., 2010) as reserved. Additionally, both EHT+STA and EHTSTA may interpret the combination of the value of the identifier subfield (i.e., 2010) and the value of the protocol subfield (i.e., 1) as an indication of the combination of user information fields used by EHT+STA.

[0235] Therefore, when the AP sends data to the three receiving devices HE STA, EHT STA, and EHT+STA... Figure 14 When trigger frame TF2 is shown, the receiving devices HE STA, EHT STA, and EHT+STA can transmit each TB PPDU uplink to the AP based on the values ​​of the standard interpretation identifier subfield and protocol subfield supported by each receiving device.

[0236] For example, EHT STA and EHT+STA can be explained Figure 14The common information field is the EHT STA common information field (i.e., the 802.11ax standard common information field). Therefore, in order to reduce the number of bits required for the EHT STA common information field (i.e., EHT Common Info) and the EHT+STA common information field (i.e., EHT+Common Info), the EHT STA common information field (i.e., EHT Common Info) and the EHT+STA common information field (i.e., EHT+Common Info) can be combined with the EHT STA common information field Common Info, respectively.

[0237] For example, Figure 6 The “More TF” subfield may not be included in the EHT STA common information field (i.e., EHTCommon Info) and the EHT+STA common information field (i.e., EHT+Common Info), respectively. Alternatively, EHT STA and EHT+STA may use the “More TF” subfield of the Common Info field used for HE STA as their “More TF” subfield.

[0238] The above combination method can be modified in other examples. For example, the EHT STA common information field (i.e., EHT Common Info) and the EHT+STA common information field (i.e., EHT+Common Info) can be combined with the HE STA common information field Common Info in various ways.

[0239] Next, refer to Figure 16 This illustrates another example of a trigger frame, TF3, according to an embodiment of the present disclosure.

[0240] exist Figure 16In the case of triggering the first receiving device HE STA, the second receiving device EHT STA, and the third receiving device EHT+STA with a single PPDU, the trigger frame is configured in the form of a single MAC Protocol Data Unit (S-MPDU) by extending the common information field and user information field with the value "4095" in the "AID12" subfield. That is, to indicate the presence of the common information field and user information field for the second receiving device EHT STA and the third receiving device EHT+STA, the value of the "AID12" subfield can be 4095 (i.e., the value of the "Startof padding field" in 802.11ax). Similarly, the common information field and user information field for the second receiving device EHT STA and the third receiving device EHT+STA can each include protocol subfields in different ways, and their details will be described below.

[0241] For example, trigger frame TF3 can be included in the payload of the PPDU (i.e., the data field of the payload). Alternatively, trigger frame TF3 can include a trigger frame in the form of a Single MAC Protocol Data Unit (S-MPDU).

[0242] For example, trigger frame TF3 can trigger uplink transmission of the first receiving device HE STA, the second receiving device EHT STA, and the third receiving device EHT+STA.

[0243] Here, the trigger frame TF3 may include the MAC header, frame body, and FCS field.

[0244] Specifically, the frame body may include multiple common information fields (Common Info, EHT Common Info and EHT+Common Info), multiple user information fields (i.e., User Info, EHT User Info and EHT+User Info), and multiple padding fields (i.e., User Info (Padding 1) with AID 4095 and User Info (Padding 2) with AID 4094).

[0245] For example, the frame body may include: a Common Info field, a User Info field, and a padding field (i.e., Padding 1) applied to the first receiving device HE STA; a Common Info field (i.e., EHT Common Info) and a User Info field (EHT User Info) applied to the second receiving device EHT STA; and a Common Info field (EHT+Common Info) and a User Info field (EHT+User Info) applied to the third receiving device EHT+STA. In some cases (e.g., when the second receiving device EHT STA and the third receiving device EHT+STA require padding fields), the frame body may also include padding fields (i.e., Padding 2) for the second receiving device EHT STA and the third receiving device EHT+STA.

[0246] The Common Info field and UserInfo field applied to the first receiving device HE STA may each include common control information and user-specific control information applied to the first receiving device HE STA, and may be assigned before the padding field (i.e., Padding 1). Additionally, the Common Info field and UserInfo field applied to the second receiving device EHT STA may each include common control information and user-specific control information applied to the second receiving device EHT STA. Furthermore, the Common Info field and UserInfo field applied to the third receiving device EHT+STA may each include common control information and user-specific control information applied to the third receiving device EHT+STA.

[0247] In other embodiments, the common information fields (i.e., EHT Common Info and EHT+Common Info) and user information fields (i.e., EHT User Info and EHT+User Info) for each of the second receiving device EHT STA and the third receiving device EHT+STA may be assigned after the padding field (i.e., Padding 1). Additionally, in other embodiments, the padding field (i.e., Padding 2) for the second receiving device EHT STA and the third receiving device EHT+STA may be assigned after the user information field (i.e., EHT+User Info) of the third receiving device EHT+STA.

[0248] For example, the order of the common information field (i.e., EHT CommonInfo) and user information field (i.e., EHT User Info) applied to the second receiving device EHT STA, and the common information field (i.e., EHT+Common Info) and user information field (i.e., EHT+User Info) applied to the third receiving device EHT+STA, can be changed. Furthermore, when there are other receiving devices besides the first receiving device HE STA, the second receiving device EHT STA, and the third receiving device EHT+STA, the trigger frame TF3 may also include additional common information fields and additional user information fields corresponding to each additional receiving device.

[0249] However, for the sake of clarity, it will be referred to as Figure 16 The order and number of the receiving devices shown are used as an example for description.

[0250] Furthermore, the value (i.e., 4095) of the identifier subfield in the padding field (i.e., Padding 1) for the first receiving device HE STA can indicate that the corresponding padding field (i.e., Padding 1) is a padding field for the first receiving device HE STA, and the common information fields (i.e., EHT Common Info and EHT+Common Info) and user information fields (i.e., EHT User Info and EHT+UserInfo) applied to the second receiving device EHT STA and the third receiving device EHT+STA, respectively, are assigned after the corresponding padding field (i.e., Padding 1).

[0251] Here, the padding field (i.e., Padding 1) for the first receiving device HE STA can be a field configured by using an existing user information field (i.e., one of the user information fields of the 802.11ax trigger frame).

[0252] For example, in the common information fields (i.e., EHT Common Info and EHT+Common Info) and user information fields (i.e., EHT User Info and EHT+User Info) applied respectively to the second receiving device EHT STA and the third receiving device EHT+STA, based on Figure 14The reserved identifier (i.e., the value of the reserved identifier subfield) can be used without applying the method of using existing user information fields. Therefore, in the case of the common information fields (i.e., EHT Common Info and EHT+Common Info) and user information fields (i.e., EHT User Info and EHT+User Info) applied to the second receiving device EHT STA and the third receiving device EHT+STA respectively, the field configuration can be redefined without limiting the number of bits.

[0253] Furthermore, as described above, in some cases, a padding field (i.e., Padding 2) for the second receiving device EHT STA and the third receiving device EHT+STA can be added to the frame body. Similarly, if a padding field (i.e., Padding 2) is added, the value of the identifier subfield indicating the start of the corresponding padding field (i.e., Padding 2) can be a value corresponding to any of the reserved values ​​(e.g., 2008 to 2044 and 2047 to 4094) indicated in the identifier subfield applied to the user information field of the first receiving device HE STA (e.g., 4094).

[0254] In other words, the value of the identifier subfield (i.e., 4094) in the padding field (i.e., Padding 2) for the second receiving device EHT STA and the third receiving device EHT+STA may include a value (e.g., 4094) corresponding to any of the values ​​(e.g., 2008 to 2044 and 2047 to 4094) indicated as reserved in the identifier subfield of the user information field applied to the first receiving device EHT STA, and may indicate that the corresponding padding field (i.e., Padding 2) is a padding field for the second receiving device EHT STA and the third receiving device EHT+STA.

[0255] As described above, configured Figure 16 The HE STA receives the trigger frame TF3, and the frame body must be interpreted as the 802.11ax standard. Therefore, if the HE STA finds a User Information field with a value of 4095 in the Identifier subfield when receiving and processing the trigger frame TF3, then the padding fields following the corresponding User Information field can be interpreted as assigned, and processing can be stopped (e.g., decoding). Therefore, upon receiving the trigger frame TF3, the HE STA can interpret the CommonInfo field and the User Info field following the MAC header as fields relevant to themselves, and will not process the fields assigned after the User Info field with an Identifier subfield value of 4095 (i.e., User Info with AID 4095).

[0256] Therefore, if the value of the identifier subfield in the user information field is 4095, then the HE STA interpretable fill field is assigned after the corresponding value (i.e., 4095), and interprets the assignment of its own public information fields (i.e., EHT Common Info and EHT+Common Info) and user information fields (i.e., EHT User Info and EHT+User Info) after the corresponding value (i.e., 4095).

[0257] In other words, the common information field and user information field used for EHT STA and EHT+STA can be assigned after the user information field with a value of 4095 in the "AID12" subfield. Therefore, HE STA will not perform decoding operations on fields following the corresponding user information field (the user information field with a value of 4095 in the "AID12" subfield). On the other hand, in the case of EHTSTA and EHT+STA, their specific information is assigned to fields following the corresponding user information field (the user information field with a value of 4095 in the "AID12" subfield), and decoding can also be performed on fields following the corresponding user information field.

[0258] Furthermore, for example, when the value of the identifier subfield in the user information field is 4094, the EHT STA and EHT+STA interpretable fill fields are assigned after the corresponding value (i.e., 4094).

[0259] For example, there may be various methods for the second receiving device EHT STA and the third receiving device EHT+STA to distinguish the common information field (i.e., EHT Common Info) and user information field (i.e., EHT User Info) applied to the second receiving device EHT STA from the common information field (i.e., EHT+Common Info) and user information field (i.e., EHT+User Info) applied to the third receiving device EHT+STA.

[0260] For example, as referenced above Figure 14 and Figure 15 The description suggests that values ​​for reserved identifier subfields may exist, as indicated in the 802.11ax standard (e.g., Figure 10 Methods for distinguishing “EHT Common Info and EHT+Common Info” from “EHT User Info and EHT+User Info” (2008 to 2044 and 2047 to 4094 in the original text).

[0261] Alternatively, a separate subfield (e.g., a protocol subfield) can be added to each of the fields (i.e., EHT Common Info, EHT User Info, EHT+Common Info, and EHT+User Info) to distinguish between the EHT standard and the EHT+ standard.

[0262] Furthermore, when using the method of adding a separate subfield (e.g., a protocol subfield) to each of the fields (i.e., EHT Common Info, EHT User Info, EHT+Common Info, and EHT+User Info), the method of using the identifier subfield as an auxiliary field can also be used.

[0263] The method of distinguishing the common information field (i.e., EHT Common Info) and user information field (i.e., EHT User Info) applied to the second receiving device EHT STA from the common information field (i.e., EHT+Common Info) and user information field (i.e., EHT+User Info) applied to the third receiving device EHT+STA is not limited to the method described above, and other methods may also exist.

[0264] In this way, when the AP sends data to three receiving devices: HE STA, EHT STA, and EHT+STA... Figure 16 When trigger frame TF3 is shown, the receiving devices HE STA, EHT STA, and EHT+STA can all transmit each TB PPDU uplink to the AP based on the value "4095" of the standard interpretation identifier subfield supported by each receiving device.

[0265] For example, EHT STA and EHT+STA can be explained Figure 16 The Common Info field (i.e., the 802.11ax standard common information field) is used for EHT STA. Therefore, in order to reduce the number of bits required for the common information field (i.e., EHT Common Info) for EHT STA and the common information field (i.e., EHT+Common Info) for EHT+STA, the common information field (i.e., EHT Common Info) for EHT STA and the common information field (i.e., EHT+Common Info) for EHT+STA can be combined with the Common Info field for EHT STA, respectively.

[0266] For example, it is possible not to include Figure 6The “More TF” subfield is included in the EHT STA common information field (i.e., EHTCommon Info) and the EHT+STA common information field (i.e., EHT+Common Info), respectively. Alternatively, EHT STA and EHT+STA may use the “More TF” subfield of the Common Info field used for HE STA as their “More TF” subfield.

[0267] The combination method is not limited to this, and the common information field for EHT STA (i.e., EHTCommon Info) and the common information field for EHT+STA (i.e., EHT+Common Info) can be combined with the HE STA common information field Common Info in various ways.

[0268] Therefore, in the embodiments of this disclosure, the above configuration is used to implement a trigger frame for triggering uplink FD A-PPDU transmission, and in the following, reference will be made to Figure 17 and Figure 18 Describe the wireless communication methods in a WLAN system.

[0269] Figure 17 This is a flowchart illustrating the wireless communication method of the transmitting device in a WLAN system. Figure 18 This is a flowchart illustrating the wireless communication method of the receiving device in a WLAN system.

[0270] For example, when describing Figure 17 and Figure 18 At that time, will refer to Figure 3 Provide a description, and describe them in sequence. Figure 17 and Figure 18 .

[0271] refer to Figure 3 and Figure 17 The diagram illustrates the wireless communication method of the transmitting device in a WLAN system. Therefore, it is assumed that... Figure 3 The wireless communication device 200 is a transmitting device (e.g., an AP).

[0272] First, generate a PPDU (S100) including the preamble and payload.

[0273] For example, transceiver 260 can use the trigger frame format, PPDU format, and RU allocation information stored in memory 270 to generate a PPDU including a preamble and payload.

[0274] Here, the preamble may include multiple training fields and multiple signaling fields, and the payload may include data fields and packet extensions.

[0275] In addition, data fields may include the above. Figures 13 to 16 Any of the trigger frames TF1 to TF3.

[0276] Transceiver 260 can be configured via a trigger frame configuration method according to embodiments of the present disclosure (i.e., as described above). Figures 13 to 16 The method described in the document (configuring trigger frames) configures trigger frames to generate PPDUs.

[0277] When a PPDU is generated (S100), the generated PPDU is sent to at least one receiving device (S200).

[0278] For example, transceiver 260 can transmit the generated PPDU to at least one external receiving device (e.g., STA) via antenna 280.

[0279] Therefore, at least one external receiving device (e.g., STA) can receive PPDU from each transmitting device (e.g., AP) and perform uplink transmission of TB PPDU based on the trigger frame in the received PPDU.

[0280] For example, at least one external receiving device may support the same or different standards (e.g., at least one of HE, EHT, and EHT+ standards). In this case, a PPDU sent from the transmitting device to the receiving device (i.e., a PPDU including any of the trigger frames TF1 to TF3 described above) may trigger uplink transmission of FD A-PPDUs including multiple PPDUs supporting the same or different standards.

[0281] Next, refer to Figure 3 and Figure 18 This illustrates a method for wireless communication of a receiving device in a WLAN system. Therefore, it is assumed that... Figure 3 The wireless communication device 200 is a receiving device (e.g., STA).

[0282] First, receive the PPDU (S300) including the preamble and payload.

[0283] For example, transceiver 260 can receive a PPDU including a preamble and payload from an external transmitting device (e.g., AP or STA) via antenna 280.

[0284] Here, the preamble may include multiple training fields and multiple signaling fields, and the payload may include data fields and packet extensions.

[0285] In addition, data fields may include the above. Figures 13 to 16The trigger frames (e.g., TF1 to TF3) received by transceiver 260 may include the trigger frame configuration method according to embodiments of this disclosure (i.e., as described above). Figures 13 to 16 The trigger frame is configured using the trigger frame configuration method described in [the document].

[0286] Upon receiving the PPDU (S300), the payload is decoded based on the preamble (S400).

[0287] For example, transceiver 260 can decode the payload based on the preamble in the received PPDU.

[0288] Therefore, the receiving device (e.g., STA) can perform uplink transmission of a standard TB PPDU supported by the receiving device (e.g., STA) based on the decoding result.

[0289] For example, the receiving device can be one of multiple receiving devices (i.e., receiving devices supporting the same or different standards) that receive a PPDU including a trigger frame from the transmitting device. Multiple receiving devices are triggered by the PPDU (i.e., a PPDU including any one of trigger frames TF1 to TF3), enabling uplink transmission of FD A-PPDUs including multiple PPDUs supporting the same or different standards.

[0290] As described above, embodiments of this disclosure efficiently configure trigger frames for initiating uplink FD A-PPDU transmission through apparatus and methods for supporting uplink FD A-PPDU transmission in a WLAN system, enabling backward compatibility, forward compatibility, and uplink transmission of A-PPDUs including various standard PPDUs.

[0291] Figure 19 This is a signaling diagram illustrating an example wireless communication method of a WLAN system according to an embodiment of the present disclosure. Figure 19 The example illustrates the operation of AP 19, which is capable of communicating with both conventional and non-conventional devices (e.g., a first STA STA1 as a conventional device and a second STA STA2 as a non-conventional device). The example wireless communication method includes operations S01 to S04 performed by AP 19, operations S11 to S13 performed by STA1, and operations S21 to S22 performed by STA2.

[0292] AP 19 may generate a first information field (S01), which includes information to be provided to STA1 and recognized by STA1. For example, the first information field may include a first value, and STA1 may recognize the first information field as valid based on the first value.

[0293] AP 19 may generate a second information field (S02), which includes information to be provided to STA2 and recognized as valid by STA2 but invalid by STA1. For example, the second information field may include a second value, and STA1 may recognize the second information field as invalid based on the second value.

[0294] AP 19 can generate a frame including a first information field and a second information field (S03). For example, AP 19 can generate a frame including a MAC header and a frame body, and can include the first information field generated in S01 and the second information field generated in S02 in the frame body.

[0295] AP 19 can send frames to STA1 and STA2 (S04). For example, AP 19 can send PPDUs that include the frames generated in S03 to STA1 and STA2, and STA1 and STA2 can jointly receive PPDUs from AP 19.

[0296] STA1 can extract a first information field and a second information field from a frame (S11). For example, STA1 can extract a frame from a PPDU received from AP 19, and extract a first information field and a second information field with the same length (i.e., number of bits) from the extracted frame.

[0297] STA1 can identify information from the first information field (S12). For example, as described above, the first information field may include a first value, and STA1 can identify the first information field as valid based on the first value, and identify the information included in the first information field. (See later...) Figure 20 As described, the first information field may include a subfield having a first value, wherein the first value may be a valid value of the corresponding subfield in a standard supported by STA1 (e.g., HE).

[0298] STA1 may ignore the second information field (S13). For example, as described above, the second information field may include a second value, and STA1 may identify the second information field as invalid based on the second value, and may ignore the second information field after identifying the second value, that is, the information included in the second information field. (See later...) Figure 20 As described, the second information field may include a subfield having a second value, and the second value may be one of the reserved values ​​of the corresponding subfield in a standard supported by STA1 (e.g., HE).

[0299] STA2 can extract a first information field and a second information field from a frame (S21). For example, STA2 can extract a frame from a PPDU received from AP 19, and extract a first information field and a second information field of the same length from the extracted frame.

[0300] STA2 can identify information from the second information field (S22). For example, as described above, the second information field may include a second value, and STA2 can identify the second information field as valid based on the second value, and can identify the information included in the second information field. (See later...) Figure 20 As described, the second information field may include a subfield having a second value, and the second value may be a valid value of the corresponding subfield in a standard supported by STA2 (e.g., EHT or EHT+).

[0301] Figure 20 This is a diagram illustrating frames according to embodiments of the present disclosure. For example, Figure 20 Shown by Figure 19 AP 19 provides examples of frames for the first STA STA1, which is a conventional device, and the second STA STA2, which is a non-conventional device. Reference will be made below. Figure 19 describe Figure 20 .

[0302] refer to Figure 20 A frame may include a MAC header, frame body, and FCS. (See above reference.) Figure 5 As described, the MAC header may include a frame control field, a duration field, an RA field, and a TA field. The frame body may include a first information field IF1 and a second information field IF2. (See above reference.) Figure 19 As described, IF1 may include information to be provided to a conventional device (e.g., STA1), and IF2 may include information to be provided to a non-traditional device (e.g., STA2). IF1 and IF2 may be included in a frame section in which a variable number of information fields may be arranged (e.g., Figure 5 User information list fields or Figure 22 (in the STA information field range).

[0303] like Figure 20 As shown, IF1 and IF2 can have the same length (i.e., number of bits). IF1 may include a first subfield SF1 with a first value, while IF2 may include a second subfield SF2 with a second value. Figure 20 As shown, SF1 in IF1 and SF2 in IF2 can have the same bit index (i.e., SF1 and SF2 can start at the same position (e.g., the start position) in IF1 and IF2, respectively). Therefore, the conventional STA (STA1) can recognize the second value SF2 included in IF2 and ignore IF2 based on the second value.

[0304] In some embodiments, IF1 and IF2 may have different structures, in addition to SF1 and SF2. For example, at least one subfield 201 in IF1 other than SF1 may differ from at least one subfield 202 in IF2 other than SF2 in terms of length and / or bit index. Thus, AP 19 and STA2 may use a second information field IF2 with a structure (i.e., subfield configuration) designed to include additional information or to provide more efficient encoding and / or decoding independent of the conventional STA (STA1). For example, for extended signaling such as extended bandwidth, extended spatial stream number, etc., IF2 may have a different structure than IF1.

[0305] In some embodiments, Figure 20 The frames can be those mentioned above. Figure 5 The description refers to the trigger frame, and IF1 and IF2 can be user information fields of the trigger frame. Additionally, SF1 and SF2 can each be a "AID12" subfield of the user information field, as referenced above. Figure 10 As described, the second value of SF2 can be one of the reserved values ​​of the "AID12" subfield (i.e., 2008 to 2044 and 2047 to 4094). References will be made below. Figures 21 to 24 The null data packet (NDP) announcement frame is used as... Figure 20 The example of a frame is used to describe this.

[0306] Figure 21 This is a timing diagram illustrating the channel detection process in a WLAN system. Figure 21 The timing diagram illustrates an example of a probe protocol with multiple beamformers, which are receiving devices that receive an antenna beam formed by the antenna element of a beamformer (transmitting device). Figure 21 The beamformer can be an AP, and the n beamformers can be n STAs (n is an integer greater than 0).

[0307] From time t1 to time t2, the beamformer may send an NDP announcement frame to the beamreceiver. The NDP announcement frame may correspond to a control frame used to notify the start of channel sensing and the transmission scheduling of NDP frames. The beamreceiver may prepare feedback on the channel state based on the NDP announcement frame before receiving the NDP frame. See later... Figure 22 Example describing an NDP announcement frame.

[0308] From time t3 to time t4, the beamformer can send NDP frames to the beamformed receiver. For example, as... Figure 21As shown, when the transmission of the NDP announcement frame is complete, the beamformer can send NDP frames starting from time t3 after a short interframe space (SIFS) from time t2. The NDP frame may include training symbols.

[0309] Starting at time t5, the receiving beamformer can feed back the channel state to the beamformer. For example, the receiving beamformer can generate a feedback matrix by detecting the training symbols included in the NDP frame and can provide the feedback matrix to the beamformer.

[0310] Figure 22 This is a diagram illustrating the structure of an NDP advertisement frame as defined in 802.11ax. (See above reference.) Figure 21 As described, Figure 22 The NDP announcement frame can be provided to the beamformer by the beamformer during the channel probing process.

[0311] refer to Figure 22 The NDP advertisement frame may include a MAC header, a frame body, and an FCS field (with 4 or more octets). The MAC header may include a frame control field (2 octets), a duration field (2 octets), an RA field (6 octets), and a TA field (6 octets). The frame body may include a Sounding DialogToken field (1 octet) and at least one STA information field (STA Info 1, ..., STA Info n) (4 octets each). The STA information field provides information related to channel feedback to the STA (i.e., the beamformer). Figure 22 As shown, an NDP announcement frame may include STA information fields corresponding to the number of STAs, and therefore, an NDP announcement frame may include a variable number of STA information fields. The following will refer to... Figure 23A and Figure 23B Example describing STA information fields.

[0312] Figure 23A and Figure 23B It is a diagram. Figure 22 A diagram illustrating the example structure of the STA information field. For example, Figure 23A This shows the structure of the STA information field when the value of the "AID11" subfield included in the STA information field is not 2047. Figure 23B This shows the structure of the STA information field when the value of the AID11 subfield included in the STA information field is 2047.

[0313] refer to Figure 23AThe STA information field may include the AID11 subfield. If the value of the AID11 subfield is not 2047, the STA information field may include the "Partial BW Info" subfield, the "Feedback Type And Ng" subfield, the "Disambiguation" subfield, the "Codebook Size" subfield, and the "Nc" subfield. Figure 23A The subfields can each correspond to the subfields defined in the 802.11ax standard, and Figure 23A The STA Information field can provide channel feedback-related information to the STA corresponding to the value of the AID11 subfield.

[0314] Additionally, refer to Figure 23B The STA information field may include the AID11 subfield. When the value of the AID11 subfield is 2047, the STA information field may include the "Disallowed Subchannel Bitmap" subfield and the "Disambiguation" subfield, and may include reserved bits. Figure 23B The subfields can correspond to the subfields defined in the 802.11ax standard. Figure 23B The STA information field provides information about the 20MHz sub-channels to be included in the feedback report within the 160MHz bandwidth, and the STAs can collectively identify the corresponding information.

[0315] like Figure 23A and Figure 23B As shown, the AID11 subfield can have a specific length (11 bits) and a specific bit index (i.e., B0 to B10) in the STA information field. HE STA can be interpreted based on the value of the AID11 subfield. Figure 23A STA information field or Figure 23B STA information field.

[0316] Similar to the above references Figure 10 The "AID12" subfield of the described trigger frame may contain values ​​2008 to 2046 from the AID11 subfield in the 802.11ax standard. Therefore, the HE STA can identify STA information fields that include an AID11 subfield with one of 2008 to 2046 as invalid. Alternatively, at least one value from 2008 to 2046 of the AID11 subfield in next-generation standards can be used (e.g., ...). Figure 19(The second value). For example, when the value of the AID11 subfield is 2008, the EHT STA can recognize that the STA information field including the corresponding AID11 subfield includes information for the EHT STA. In some embodiments, when the value of the AID11 subfield is 2008, the EHT STA can recognize that the STA information field including the corresponding AID11 subfield and subsequent STA information fields include information for the EHT STA. In some embodiments, when the value of the AID11 subfield is 2008, the STA information field may have other values ​​besides the AID11 subfield that are related to... Figure 23A and Figure 23B The structures are different. Therefore, in the NDP announcement frame that includes the STA information field, the signaling for EHTSTA can be extended while maintaining backward compatibility.

[0317] Figure 24 This is a diagram illustrating an NDP notification frame according to an embodiment of the present disclosure. For example, Figure 24 Examples of NDP announcement frames provided to HESTA, EHT STA, and EHT+STA are shown.

[0318] like Figure 24 As shown, the NDP announcement frame may include a MAC header, a frame body, and an FCS. The frame body may include a Sounding Dialog Token field, at least one HE STA Info field, at least one EHT STA Info field, and at least one EHT+STA Info field. The HE STA Info field may include information for HE STA; the EHT STA Info field may include information for EHT STA; and the EHT+STA Info field may include information for EHT+STA. In other embodiments, at least one of the HE STA Info field, EHT STA Info field, and EHT+STA Info field may be omitted.

[0319] As referenced above Figure 23A and Figure 23B As described, the HE STA information field, EHT STA information field, and EHT+STA information field may each include an AID11 subfield. For example, such as Figure 24As shown, the AID11 subfield in each of these information fields can have a value other than those reserved values ​​of 802.11ax, i.e., one of the values ​​from 0 to 2007 and 2047. Additionally, as an EHT STA information field, the second STA information field SIF2 can include the AID11 subfield, where the AID11 subfield can have one of the reserved values ​​of 802.11ax (e.g., 2008). Furthermore, as an EHT+STA information field, the third STA information field SIF3 can include the AID11 subfield, and this AID11 subfield can have one of the reserved values ​​of 802.11ax that is not used in the EHT STA, i.e., one of the reserved values ​​of 802.11be (e.g., 2009). Therefore, HE STA can ignore the second STA information field SIF2 and the third STA information field SIF3, and EHT STA can ignore the third STA information field SIF3.

[0320] As referenced above Figure 10 As described, because public or user fields are valid for next-generation standards, AID11 subfields can have predefined values. For example, the value "2008" of the AID11 subfield included in the second STA information field SIF2 can be a value predefined as valid for any next-generation standard (e.g., EHT and EHT+) in HE. Therefore, an HE STA can recognize that the second information field SIF2 is used by an STA supporting next-generation standards and can ignore the second STA information field SIF2. Similarly, the value "2009" of the AID11 subfield included in the third STA information field SIF3 can be a value predefined as valid for any next-generation standard (i.e., EHT+) in EHT. Therefore, an EHT STA can recognize that the third information field SIF3 is used by an STA supporting next-generation standards and can ignore the third STA information field SIF3.

[0321] Figure 25 This is a signaling diagram illustrating a wireless communication method of a WLAN system according to an embodiment of the present disclosure. For example, Figure 25 The message diagram illustrates the operation of AP 25, which is capable of communicating with both traditional and non-traditional devices (STA 1 as a traditional device and STA 2 and STA 3 as non-traditional devices). Figure 25 As shown, the wireless communication method may include operations S01' to S05' performed by AP 25, operations S11' to S14' performed by STA1, operations S21' to S24' performed by STA2, and operations S31' to S34' performed by STA3.

[0322] refer to Figure 25 In operation S01', AP 25 may generate a first information field. The first information field may include information to be provided to STA1, and AP 25 may generate a first information field to be recognized by STA1. For example, the first information field may include a first value, and STA1 may recognize the first information field as valid based on the first value.

[0323] In operation S02', AP 25 may generate a second information field. This second information field may include information to be provided to STA2 and STA3, and AP 25 may generate a second information field that will be recognized as valid by the second STA STA2 and the third STA STA3, but will be recognized as invalid by the first STA STA1. For example, the second information field may include a second value, and STA1 may recognize the second information field as invalid based on the second value.

[0324] In operation S03', AP 25 can generate at least one third information field. This third information field can correspond to a non-traditional STA, and therefore, in Figure 25 In the example, AP 25 can generate two third information fields for STA2 and STA3.

[0325] In operation S04', AP 25 can generate a frame including a first information field, a second information field, and at least one third information field. For example, AP 25 can generate a frame including a MAC header and a frame body, and the first information field generated in operation S01', the second information field generated in operation S02', and at least one third information field generated in operation S03' can be sequentially arranged in the frame body.

[0326] In operation S05', AP 25 can send frames to STA1, STA2, and STA3. For example, AP 25 can send PPDUs that include the frames generated in operation S04' to STA1, STA2, and STA3. STA1, STA2, and STA3 can collectively receive PPDUs from AP 25.

[0327] In operation S11', STA1 can extract information fields from the frame. For example, STA1 can extract the frame from the PPDU received from AP 25, and extract a first information field, a second information field, and at least one third information field with the same length (i.e., number of bits) from the extracted frame.

[0328] In operation S12', STA1 can identify information from the first information field. For example, STA1 can identify the first information field as valid based on a first value included in the first information field, and can identify the information included in the first information field. (See later...) Figure 25As described, the first information field may include a subfield having a first value, and the first value may be one of the valid values ​​of the corresponding subfield in a standard supported by STA1 (e.g., HE).

[0329] In operation S13', STA1 may identify the start of the padding field from the second information field. For example, the second information field may include a subfield with a second value, and the second value may indicate the start of the padding field in a standard (e.g., HE) supported by STA1.

[0330] In operation S14', STA1 may ignore the second information field and the third information field. For example, STA1 may identify other subfields of the second information field as invalid based on the start of the fill field identified in operation S13', and may identify information fields after the second information field (i.e., at least one third information field) as invalid. Therefore, STA1 may ignore information fields from the second information field to the information fields before the FCS field.

[0331] In operation S21', STA2 can extract information fields from the frame. For example, STA2 can extract the frame from the PPDU received from AP 25, and extract a first information field, a second information field, and at least one third information field with the same length (i.e., number of bits) from the extracted frame.

[0332] In operation S22', STA2 can identify the first information from the second information field. For example, STA2 can identify the second information field as valid based on a second value included in the second information field, and can identify the first information included in the second information field. As described later, STA3 can also identify the first information from the second information field, and therefore, the second information field can include common information for non-traditional STAs (i.e., the second STA STA2 and the third STA STA3). Moreover, STA2 can identify that at least one third information field follows the second information field based on the second value included in the second information field.

[0333] In operation S23', STA2 can identify the second information from the third information field. For example, STA2 can identify the third information field for itself in the third information field following the second information field, and can identify the second information from the identified third information field.

[0334] In operation S24', STA2 can combine the first information and the second information. For example, STA2 combines the first information, which is public information included in the second information field, and the second information, which is personal information included in the third information field, to identify the information provided by AP 25.

[0335] In operation S31', STA3 can extract information fields from a frame. For example, STA3 can extract a frame from a PPDU received from AP 25, and extract a first information field, a second information field, and at least one third information field with the same length (i.e., number of bits) from the extracted frame.

[0336] In operation S32', STA3 can identify the first information from the second information field. For example, STA3 can identify the second information field as valid based on the second value included in the second information field, and can identify the first information included in the second information field. Moreover, STA3 can identify that at least one third information field follows the second information field based on the second value included in the second information field.

[0337] In operation S33', STA3 can identify third information from the third information field. For example, STA3 can identify a third information field for itself in the third information field following the second information field, and can identify third information from the identified third information field.

[0338] In operation S34', STA3 can combine the first information and the third information. For example, STA3 combines the first information, which is public information included in the second information field, and the third information, which is personal information included in the third information field, to identify the information provided by AP 25.

[0339] In some embodiments, STA2 and STA3 may omit the first information field. For example, the first value included in the first information field may be one of the values ​​representing a legacy standard in the standard supported by STA2 and STA3 (e.g., EHT or EHT+). In some embodiments, the second STA STA2 and the third STA STA3 may identify common information from the first information field. For example, STA2 and STA3 may identify, based on the first value included in the first information field, that the first information field includes common information about STA1, STA2, and STA3, and may identify common information from the first information field.

[0340] Figure 26 This is a diagram illustrating frames according to exemplary embodiments of the present disclosure. For example, Figure 26 Shown by Figure 25 AP 25 provides examples of frames for STA1 as a conventional device and STA2 and STA3 as non-conventional devices. Reference will be made below. Figure 25 describe Figure 26 .

[0341] refer to Figure 26 A frame may include a MAC header, frame body, and FCS. (See above reference.) Figure 5As described, the MAC header may include a frame control field, a duration field, an RA field, and a TA field. The frame body may include a first information field (IF1), a second information field (IF2), and a third information field (IF3). (See above reference.) Figure 20 As described, the first information field IF1 may include information to be provided to STA1, which is a conventional device; the second information field IF2 may include information to be jointly provided to STA2 and STA3, which are non-conventional devices; and the third information field IF3 may include information to be provided to one of the second STA2 and the third STA3. In some embodiments, the first information field IF1, the second information field IF2, and the third information field IF3 may be included in a range in which a variable number of information fields can be arranged in a frame (e.g., Figure 5 User information list fields and Figure 22 (in the STA information field range).

[0342] like Figure 26 As shown, the first information field IF1, the second information field IF2, and the third information field IF3 can have the same length (i.e., the number of bits). The first information field IF1 may include a first subfield SF1, and the first subfield SF1 may have a first value. Additionally, the second information field IF2 may include a second subfield SF2, and the second subfield SF2 may have a second value. Figure 26 As shown, the first subfield SF1 in the first information field IF1 and the second subfield SF2 in the second information field IF2 not only have the same length (i.e., number of bits) but also the same bit index. Therefore, the conventional STA (i.e., STA1) can identify the second value of the second subfield SF2 included in the second information field IF2 and ignore the second information field IF2 based on the second value.

[0343] In some embodiments, Figure 20 The frames can be those mentioned above. Figure 5 The described trigger frame, and the first information field IF1 and the second information field IF2 can be user information fields of the trigger frame. Additionally, the first subfield SF1 and the second subfield SF2 can be the "AID12" subfield of the user information field, as referenced above. Figure 10 As described, the second value of the second subfield SF2 can be 4095, which indicates the start of the fill field in the subfield "AID12".

[0344] In some embodiments, the third information field IF3 may have a different structure (e.g., configuration of subfields) than the first information field IF1 and the second information field IF2. For example, as Figure 26As shown, the third information field IF3 may include a third subfield SF3 having a different length and / or bit index than the first subfield SF1 and the second subfield SF2. (See above reference.) Figure 25 As described, the conventional STA (STA1) can identify the second information field IF2 as the start of the fill field based on the second value of the second subfield SF2 of the second information field IF2, and accordingly, the third information field IF3 is identified as invalid regardless of the structure of the third information field IF3 following the second information field IF2. Therefore, AP 25, STA2, and STA3 can use the third information field IF3, which has a structure that is advantageously defined independently of the conventional STA (i.e., STA1).

[0345] Figure 27 This is a diagram illustrating a trigger frame according to an embodiment of the present disclosure. For example, Figure 27 Examples of trigger frames provided to HE STA, EHT STA, and EHT+STA are shown.

[0346] refer to Figure 27 The trigger frame may include a MAC header, a frame body, and an FCS. The frame body may include a HE Common Info field, at least one HE User Info field, an EHT Common Info field, at least one EHT User Info field, an EHT+ Common Info field, and at least one EHT+ User Info field. The HE User Info field may include information for HE STA, the EHT Common Info field and the EHT User Info field may include information for EHT STA, and the EHT+ Common Info field and the EHT+ User Info field may include information for EHT+STA. In other embodiments, this may be omitted. Figure 27 The frame body includes at least one of the fields.

[0347] The HE user information field, EHT public information field, and EHT+ public information field can each include an "AID12" subfield. For example, such as Figure 27As shown, as an HE user information field, the first information field IF1 may include a "AID12" subfield, and the "AID12" subfield may have a value other than the reserved values ​​of 802.11ax, namely, one of 0 to 2007, 2045, and 2046. Additionally, as an EHT public information field, the second information field IF2 may include the "AID12" subfield, and the "AID12" subfield may have a value of 4095 in 802.11ax indicating the start of the fill field. Therefore, HE STA can ignore the information field between the second information field IF2 and the FCS field. Furthermore, as an EHT+ public information field, the third information field IF3 may include the "AID12" subfield, and the "AID12" subfield may have a value of 4095 in 802.11ax indicating the start of the fill field. Therefore, in other embodiments, the trigger frame includes only information for HE STA and information for EHT+STA, and even if the information for EHT STA is omitted, HE STA can ignore the information field between the EHT common information field and the FCS field.

[0348] In some embodiments, in addition to the “AID12” subfield, the EHT public information field and the EHT+ public information field may also include additional subfields (e.g., protocol subfields). The added subfields may have values ​​that indicate the EHT public information field or the EHT+ public information field, and the EHT STA and EHT+STA may identify their own public information fields based on the values ​​of the corresponding subfields.

[0349] The various functions described above can be implemented or supported by one or more computer programs, all of which are formed of computer-readable program code and executed on a computer-readable storage medium. "Application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, associated data, or portions thereof suitable for implementing multiple lines of computer-readable program code. "Computer-readable program code" includes all types of computer code, including source code, object code, and executable code. "Computer-readable medium" includes media accessible by a computer, such as all types of media including read-only memory (ROM), random access memory (RAM), hard disk drives, compact disks (CDs), digital video discs (DVDs), and other types of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit temporary electrical or other signals. Non-transitory computer-readable media includes media that permanently store data and media that store data and subsequently overwrite it, such as rewritable optical discs or removable storage devices.

[0350] Although embodiments of the inventive concept have been specifically shown and described, it should be understood that various changes in form and detail may be made therein without departing from the spirit and scope of the appended claims and their equivalents.

Claims

1. A first receiving device for a wireless local area network system, the first receiving device comprising: A transceiver configured to receive a protocol data unit including a preamble and a payload from a transmitting device, and to decode the payload based on the preamble; as well as A processor configured to control the transceiver. The payload's data fields include trigger frames in the form of Single Media Access Control (MAC) protocol data units. The trigger frame includes a MAC header and a frame body. The frame body includes a common information field and a user information field applied to the first receiving device, and also includes a common information field, a user information field, and a padding field applied to the second receiving device. The standard supported by the second receiving device is different from the standard supported by the first receiving device. The public information field and the user information field applied to the second receiving device are assigned before the fill field, and The public information field and the user information field applied to the first receiving device are assigned after the fill field.

2. The first receiving device according to claim 1, wherein, The index of the identifier subfield in the fill field indicates that the fill field is a fill field for the second receiving device, and indicates that the public information field and user information field applied to the first receiving device are assigned after the fill field.

3. The first receiving device according to claim 1, wherein, The frame body also includes additional padding fields for the first receiving device. The index of the identifier subfield in the additional padding field includes an index corresponding to any of the indexes that indicate a reserved index in the identifier subfield of the user information field applied to the second receiving device, and indicates that the additional padding field is a padding field for the first receiving device.

4. A wireless communication method for a first receiving device in a wireless local area network system, the wireless communication method comprising: Receive protocol data units including preamble and payload; as well as The payload is decoded based on the preamble. The payload's data fields include trigger frames in the form of Single Media Access Control (MAC) protocol data units. The trigger frame includes a MAC header and a frame body. The frame body includes a common information field and a user information field applied to the first receiving device, and also includes a common information field, a user information field, and a padding field applied to the second receiving device. The standard supported by the second receiving device is different from the standard supported by the first receiving device. The public information field and the user information field applied to the second receiving device are assigned before the fill field, and The public information field and the user information field applied to the first receiving device are assigned after the fill field.

5. The wireless communication method according to claim 4, wherein, The index of the identifier subfield in the fill field indicates that the fill field is a fill field for the second receiving device, and indicates that the public information field and user information field applied to the first receiving device are assigned after the fill field.

6. The wireless communication method according to claim 4, wherein, The frame body also includes additional padding fields for the first receiving device. The index of the identifier subfield in the additional padding field includes an index corresponding to any of the indexes that indicate a reserved index in the identifier subfield of the user information field applied to the second receiving device, and indicates that the additional padding field is a padding field for the first receiving device.

Images