Method and apparatus for receiving PPDU via multiplexed RU in a wireless LAN system

Abstract

To propose a method and a device for receiving a physical layer protocol data unit (PPDU) in a wireless LAN system.SOLUTION: Specifically, a receiving station (STA) receives a physical layer protocol data unit (PPDU) from a transmitting STA via a wideband and decodes the PPDU. The PPDU includes a control field and a data field. When the wideband is a 320 / 160+160 MHz band including a primary 160 MHz channel and a secondary 160 MHz channel, the data field is received via a first multiple resource unit (RU) in which a 996 RU and a 484 RU are aggregated. The first multiple RU is assigned within the primary 160 MHz channel or the secondary 160 MHz channel.SELECTED DRAWING: Figure 26

Description

Technical Field

[0001] This specification relates to a technique for receiving a PPDU via multiple RUs in a wireless LAN system. More specifically, it relates to a method and apparatus for transmitting and receiving a PPDU in an OFDMA scheme via multiple RUs aggregated in a combination of large-RUs.

Background Art

[0002] WLAN (wireless local area network) has been improved in various ways. For example, the IEEE802.11ax standard proposed an improved communication environment using OFDMA (orthogonal frequency division multiple access) and DL MU MIMO (downlink multi-user multiple input, multiple output) technologies.

[0003] This specification proposes technical features that can be utilized in new communication standards. For example, the new communication standard is the recently discussed EHT (Extreme high throughput) standard. The EHT standard can use newly proposed increased bandwidth, improved PPDU (PHY layer protocol data unit) structure, improved sequence, HARQ (Hybrid automatic repeat request) technology, etc. The EHT standard can be called the IEEE802.11be standard.

[0004] In the new wireless LAN standard, an increased number of spatial streams are used. In this case, it is necessary to improve the signaling technology in the wireless LAN system in order to appropriately use the increased number of spatial streams.

Summary of the Invention

Problems to be Solved by the Invention

[0005] This specification proposes a method and apparatus for receiving PPDU via multiple RUs in a wireless LAN system. [Means for solving the problem]

[0006] One example in this specification proposes a method for receiving PPDU via multiple RUs.

[0007] This embodiment can be implemented in a network environment that supports a next-generation wireless LAN system (IEEE 802.11be or EHT wireless LAN system). The next-generation wireless LAN system, as an improved version of the 802.11ax system, can satisfy backward compatibility with the 802.11ax system.

[0008] This embodiment proposes a method and apparatus for transmitting and receiving PPDUs based on multiple RUs configured in combinations of large-RUs. In this case, a large-RU refers to a resource unit with 242 or more tones. In particular, this embodiment proposes a method for configuring multiple RUs used to transmit PPDUs using the OFDMA scheme.

[0009] The receiving STA (station) receives PPDU (Physical Protocol Data Unit) from the transmitting STA via broadband.

[0010] The receiving STA decodes the PPDU.

[0011] The PPDU includes a control field and a data field.

[0012] If the broadband is a 320 / 160+160MHz band including a primary 160MHz channel and a secondary 160MHz channel, the data field is received via a first multiple RU aggregated from 996 RUs and 484 RUs. In this case, the first multiple RU is allocated within the primary 160MHz channel or the secondary 160MHz channel. The 996 RU is an RU composed of 996 tones, and the 484 RU is an RU composed of 484 tones. [Effects of the Invention]

[0013] The embodiments proposed herein offer novel advantages in OFDMA, such as support for preamble puncturing and aggregation of large-RUs of various sizes, resulting in increased transmission efficiency and throughput. [Brief explanation of the drawing]

[0014] [Figure 1] An example of a transmitting and / or receiving device as described herein is shown. [Figure 2] This is a conceptual diagram illustrating the structure of a wireless LAN (WLAN). [Figure 3] This is a diagram illustrating the normal link setup process. [Figure 4] This is a diagram showing an example of a PPDU used in IEEE standards. [Figure 5] This diagram shows the arrangement of resource units (RUs) used in the 20MHz bandwidth. [Figure 6] This diagram shows the arrangement of resource units (RUs) used in the 40MHz bandwidth. [Figure 7] This diagram shows the arrangement of resource units (RUs) used in the 80MHz bandwidth. [Figure 8]Shows the structure of the HE-SIG-B field. [Figure 9] Shows an example where multiple User STAs are assigned to the same RU via MU-MIMO technology. [Figure 10] Shows the operation related to UL-MU. [Figure 11] Shows an example of a trigger frame. [Figure 12] Shows an example of the common information field of the trigger frame. [Figure 13] Shows an example of a subfield included in the per user information field. [Figure 14] Explains the technical features of the UORA technology. [Figure 15] Shows an example of a channel used / supported / defined within the 2.4 GHz band. [Figure 16] Shows an example of a channel used / supported / defined within the 5 GHz band. [Figure 17] Shows an example of a channel used / supported / defined within the 6 GHz band. [Figure 18] Shows an example of a PPDU used in this specification. [Figure 19] Shows a modified example of the transmission device and / or reception device in this specification. [Figure 20] Shows an example of a PHY transmission procedure for the HE SU PPDU. [Figure 21] Shows an example of a transmission device block diagram for generating each field of the HE PPDU. [Figure 22] Shows an example of the EHT PPDU format. [Figure 23] Shows an example of the U-SIG format. [Figure 24] It is a procedure flowchart showing the operation of the transmission device according to this embodiment. [Figure 25] It is a procedure flowchart showing the operation of the reception device according to this embodiment. [Figure 26]This flowchart shows the procedure for the transmitting STA in this embodiment to transmit a PPDU. [Figure 27] This flowchart shows the procedure for the receiving STA in this embodiment to receive the PPDU. [Modes for carrying out the invention]

[0015] In this specification, "A or B" may mean "just A," "just B," or "both A and B." Furthermore, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "just A," "just B," "just C," or "any combination of A, B and C."

[0016] In this specification, slashes ( / ) and commas can mean "and / or". For example, "A / B" can mean "A and / or B". Thus, "A / B" can mean "just A", "just B", or "both A and B". For example, "A, B, C" can mean "A, B or C".

[0017] In this specification, "at least one of A and B" can mean "just A," "just B," or "both A and B." Furthermore, in this specification, the expressions "at least one of A or B" and "at least one of A and / or B" can be interpreted in the same way as "at least one of A and B."

[0018] Furthermore, in this specification, "at least one of A, B and C" may mean "just A," "just B," "just C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0019] Furthermore, parentheses used in this specification can mean "for example." Specifically, when "control information (PDCCH)" is shown, "PDCCH" is proposed as an example of "control information." Also, "control information" in this specification is not limited to "PDCCH," and "PDDCH" is proposed as an example of "control information." Furthermore, when "control information (i.e., PDCCH)" is shown, "PDCCH" is proposed as an example of "control information."

[0020] In this specification, technical features described individually within a single drawing may be represented individually or simultaneously.

[0021] The following examples in this specification apply to various wireless communication systems. For example, the following examples in this specification apply to wireless LAN (wireless local area network, WLAN) systems. For example, this specification applies to the IEEE 802.11a / g / n / ac standards and the IEEE 802.11ax standard. This specification also applies to newly proposed EHT standards or IEEE 802.11be standards. Furthermore, the examples in this specification also apply to new wireless LAN standards that improve upon the EHT standards or IEEE 802.11be. In addition, the examples in this specification apply to mobile communication systems. For example, this specification applies to mobile communication systems based on LTE (Long Term Evolution) and its evolution based on 3GPP® (3rd Generation Partnership Project) standards. Furthermore, the examples in this specification apply to 5GNR standard communication systems based on 3GPP standards.

[0022] The following describes the technical features to which this specification applies in order to explain the technical features of this specification.

[0023] Figure 1 shows an example of a transmitting and / or receiving device as described herein.

[0024] An example in Figure 1 can perform various technical features described below. Figure 1 relates to at least one STA (station). For example, STA (110, 120) in this specification is referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. STA (110, 120) in this specification is referred to by various names such as network, base station, node-B, access point (AP), repeater, router, relay. STA (110, 120) in this specification is referred to by various names such as receiving device, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device.

[0025] For example, an STA(110, 120) can perform either an AP (Access Point) role or a non-AP role. That is, an STA(110, 120) as described herein can perform AP and / or non-AP functions. In this specification, AP may also be referred to as AP STA.

[0026] The STA(110, 120) described herein can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards related to 3GPP standards (e.g., LTE, LTE-A, 5GNR standards). Furthermore, the STA described herein can be implemented in various devices such as mobile phones, vehicles, and personal computers. In addition, the STA described herein can support communication for various communication services such as voice calls, video calls, data communication, and autonomous driving.

[0027] In this specification, STA(110, 120) may include medium access control (MAC) and a physical layer interface to the wireless medium in accordance with the IEEE 802.11 standard.

[0028] Based on Figure 1(a), STA(110, 120) can be explained as follows.

[0029] The first STA(110) includes a processor (111), memory (112), and transceiver (113). The indicated processor, memory, and transceiver may each be implemented as separate chips, or at least two or more blocks / functions may be implemented via a single chip.

[0030] The transceiver (113) of the first STA performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0031] For example, the first STA (110) can perform the intended operation of the AP. For example, the AP's processor (111) can receive signals via the transceiver (113), process the received signals, generate transmit signals, and perform control for signal transmission. The AP's memory (112) can store signals received via the transceiver (113) (i.e., received signals) and signals transmitted via the transceiver (i.e., transmitted signals).

[0032] For example, the second STA (120) can perform the intended operation of a Non-AP STA. For example, a non-AP transceiver (123) can perform signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0033] For example, the Non-AP STA processor (121) can receive signals via the transceiver (123), process the received signals, generate transmit signals, and perform control for signal transmission. The Non-AP STA memory (122) can store signals received via the transceiver (123) (i.e., received signals) and signals transmitted via the transceiver (i.e., transmitted signals).

[0034] For example, in the following specification, the operation of the device indicated as AP is performed in the first STA(110) or the second STA(120). For example, if the first STA(110) is AP, the operation of the device indicated as AP is controlled by the processor(111) of the first STA(110), and the relevant signals are transmitted or received via a transceiver(113) controlled by the processor(111) of the first STA(110). In addition, control information related to the operation of AP and the AP's transmit / receive signals are stored in the memory(112) of the first STA(110). In addition, if the second STA(110) is AP, the operation of the device indicated as AP is controlled by the processor(121) of the second STA(120), and the relevant signals are transmitted or received via a transceiver(123) controlled by the processor(121) of the second STA(120). In addition, control information related to the operation of AP and the AP's transmit / receive signals are stored in the memory(122) of the second STA(110).

[0035] For example, in the following specification, the operation of a device indicated as non-AP (or User-STA) is performed in the first STA (110) or the second STA (120). For example, if the second STA (120) is non-AP, the operation of the device indicated as non-AP is controlled by the processor (121) of the second STA (120), and the relevant signals are transmitted or received via a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of non-AP and AP transmit / receive signals are stored in the memory (122) of the second STA (120). For example, if the first STA (110) is non-AP, the operation of the device indicated as non-AP is controlled by the processor (111) of the first STA (110), and the relevant signals are transmitted or received via a transceiver (113) controlled by the processor (111) of the first STA (120). Furthermore, control information related to the operation of the non-AP and the AP's transmit / receive signals are stored in the memory (112) of the first STA (110).

[0036] In the following specification, devices referred to as (transmit / receive)STA, 1stSTA, 2ndSTA, STA1, STA2, AP, 1stAP, 2ndAP, AP1, AP2, (transmit / receive)Terminal, (transmit / receive)Device, (transmit / receive)apparatus, network, etc., mean the STA(110, 120) in Figure 1. For example, devices referred to as (transmit / receive)STA, 1stSTA, 2ndSTA, STA1, STA2, AP, 1stAP, 2ndAP, AP1, AP2, (transmit / receive)Terminal, (transmit / receive)Device, (transmit / receive)apparatus, network, etc., without specific designations, also mean the STA(110, 120) in Figure 1. For example, in the following example, the operation of various STAs sending and receiving signals (e.g., PPPDU) may be performed in the transceiver(113, 123) in Figure 1. Furthermore, in the following example, the operation of various STAs generating transmit / receive signals or performing data processing or calculations in advance for transmit / receive signals may be performed by the processor (111, 121) in Figure 1. For example, an example of the operation of generating transmit / receive signals or performing data processing or calculations in advance for transmit / receive signals may include: 1) the operation of determining / acquiring / composing / calculating / decoding / encoding bit information of subfields (SIG, STF, LTF, Data) contained within the PPDU; 2) the operation of determining / composing / acquiring time resources and frequency resources (e.g., subcarrier resources) used for subfields (SIG, STF, LTF, Data) contained within the PPDU; 3) the operation of determining / composing / acquiring specific sequences (e.g., pilot sequences, STF / LTF sequences, extra sequences applied to SIG) used for subfields (SIG, STF, LTF, Data) contained within the PPDU; 4) power control operations and / or power saving operations applied to the STA; and 5) operations related to determining / acquiring / composing / calculating / decoding / encoding ACK signals.Furthermore, in the following example, various pieces of information used by various STAs for determining / acquiring / composing / calculating / decoding / encoding the transmit / receive signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) are stored in the memory (112, 122) shown in Figure 1.

[0037] The apparatus / STA shown in Figure 1(a) above is modified as shown in Figure 1(b). The STA(110, 120) described herein will be explained based on Figure 1(b) below.

[0038] For example, the transceivers (113, 123) shown in Figure 1(b) can perform the same functions as the transceivers shown in Figure 1(a) described above. For example, the processing chip (114, 124) shown in Figure 1(b) can include processors (111, 121) and memory (112, 122). The processors (111, 121) and memory (112, 122) shown in Figure 1(b) can perform the same functions as the processors (111, 121) and memory (112, 122) shown in Figure 1(a) described above.

[0039] In the following, mobile terminal, wireless device, wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, user STA, network, base station, Node-B, access point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, receiving apparatus, and / or transmitting apparatus mean the STA (110, 120) shown in Figure 1(a) / (b) or the processing chip (114, 124) shown in Figure 1(b). That is, the technical features of this specification may be implemented on the STA (110, 120) shown in Figure 1(a) / (b) or only on the processing chip (114, 124) shown in Figure 1(b). For example, the technical characteristic of the transmitting STA transmitting control signals can be understood as the technical characteristic that the control signals generated in the processor (111, 121) shown in Figure 1(a) / (b) are transmitted via the transceivers (113, 123) shown in Figure 1(a) / (b). Alternatively, the technical characteristic of the transmitting STA transmitting control signals can be understood as the technical characteristic that the control signals to be transmitted to the transceivers (113, 123) are generated in the processing chip (114, 124) shown in Figure 1(b).

[0040] For example, the technical feature of a receiving STA receiving a control signal can be understood as the technical feature of the control signal being received by the transceiver (113, 123) shown in Figure 1(a). Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceiver (113, 123) shown in Figure 1(a) being acquired by the processor (111, 121) shown in Figure 1(a). Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceiver (113, 123) shown in Figure 1(b) being acquired by the processing chip (114, 124) shown in Figure 1(b).

[0041] Referring to Figure 1(b), the memory (112, 122) contains software code (115, 125). The software code (115, 125) contains instructions that control the operation of the processor (111, 121). The software code (115, 125) is contained in various programming languages.

[0042] The processors (111, 121) or processing chips (114, 124) shown in Figure 1 may include ASICs (application-specific integrated circuits), other chipsets, logic circuits, and / or data processing devices. The processor is an AP (application processor). For example, the processors (111, 121) or processing chips (114, 124) shown in Figure 1 may include at least one of the following: DSP (digital signal processor), CPU (central processing unit), GPU (graphics processing unit), or modem (modulator and demodulator). For example, the processors (111, 121) or processing chips (114, 124) shown in Figure 1 are manufactured by Qualcomm®. TMEXYNOS series processor, manufactured by Samsung®. TM Series processors, A-series processors manufactured by Apple®, HELIO manufactured by MediaTek® TM ATOM series processors, manufactured by INTEL®. TM This refers to a series processor or an improved (enhanced) version thereof.

[0043] In this specification, "uplink" refers to a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packets / signals, etc., are transmitted via the uplink. Similarly, in this specification, "downlink" refers to a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packets / signals, etc., are transmitted via the downlink.

[0044] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0045] The upper part of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 Infrastructure BSS (Basic Service Set).

[0046] Referring to the top of Figure 2, a wireless LAN system can include one or more infrastructure BSS(200, 205) (hereinafter, BSS). BSS(200, 205) is not a concept that refers to a specific area, but rather a set of APs (access points, 225) and STAs such as STA1 (Station, 200-1) that can synchronize and communicate with each other. A BSS(205) can include one or more connectable STAs (205-1, 205-2) in a single AP(230).

[0047] A BSS may include at least one STA, APs (225, 230) that provide distribution services, and a distribution system (DS, 210) that connects multiple APs.

[0048] The distribution system (210) can connect multiple BSSs (200, 205) to implement an extended service set (ESS, 240). ESS (240) is a term used to refer to a network formed by one or more APs connected via the distribution system (210). APs included in a single ESS (240) share the same SSID (service set identification).

[0049] The portal (portal,220) can act as a bridge to connect a wireless LAN network (IEEE802.11) with other networks (e.g., 802.X).

[0050] In a BSS like the one shown at the top of Figure 2, networks are implemented between APs (225, 230) and between APs (225, 230) and STAs (200-1, 205-1, 205-2). However, it is also possible to configure a network and communicate between STAs without APs (225, 230). A network that enables communication between STAs without APs (225, 230) is defined as an ad-hoc network or an independent BSS (independent basic service set, IBSS).

[0051] The lower part of Figure 2 is a conceptual diagram showing IBSS.

[0052] Referring to the bottom of Figure 2, IBSS is a BSS that operates in ad-hoc mode. Since IBSS does not include APs, there is no centralized management entity that performs management functions in a central location. That is, in IBSS, STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) are configured as mobile STAs and are not allowed to connect to the distribution system, thus forming a self-contained network.

[0053] Figure 3 is a diagram illustrating the normal link setup process.

[0054] In the S310 step shown, the STA can perform an operation to find a network. The operation to find a network may include the STA's scanning operation. That is, in order for the STA to access a network, it needs to find a network that it can join. Before the STA can join a wireless network, it needs to identify compatible networks, and the process of identifying networks that exist in a particular area is called scanning. There are two scanning methods: active scanning and passive scanning.

[0055] Figure 3 illustrates the process of finding a network, including the active scanning process. In active scanning, the STA performing the scanning moves to a different channel and sends a probe request frame to search for nearby APs, and waits for a response. The responder sends a probe response frame to the STA that sent the probe request frame. Here, the responder is the STA that last sent a beacon frame in the BSS of the channel being scanned. In BSS, APs send beacon frames, so APs become the responders, while in IBSS, STAs within IBSS return and send beacon frames, so the responder is not constant. For example, an STA that sent a probe request frame on channel 1 and received a probe response frame on channel 1 can store the BSS-related information contained in the received probe response frame and move to the next channel (e.g., channel 2) and perform scanning in the same way (i.e., sending and receiving probe requests / responses on channel 2).

[0056] Although not shown as an example in Figure 3, scanning operations can also be performed using the pass-sip scan method. An STA performing scanning based on pass-sip scans can wait for beacon frames while moving between channels. In IEEE 802.11, beacon frames are one of the management frames, used to announce the presence of a wireless network and are periodically transmitted to the scanning STA to find the wireless network and join it. In BSS, APs perform the role of periodically transmitting beacon frames, and in IBSS, STAs within IBSS return and transmit beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS contained in the beacon frame and records the beacon frame information on each channel while moving to other channels. An STA that receives a beacon frame stores the BSS-related information contained in the received beacon frame and can move to the next channel and perform scanning on the next channel in the same way.

[0057] Once the STA discovers the network, it can perform an authentication process via step S320. This authentication process is referred to as the first authentication process to clearly distinguish it from the security configuration operation in step S340, which will be described later. The authentication process in S320 may include a process in which the STA sends an authentication request frame to the AP, and in response, the AP sends an authentication response frame to the STA. The authentication frame used in the authentication request / response corresponds to the management frame.

[0058] The authentication frame may include information such as the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), and finite cyclic group.

[0059] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can decide whether or not to grant authentication to the STA. The AP can provide the result of the authentication process to the STA via an authentication response frame.

[0060] A successfully authenticated STA can perform the connection process based on step S330. The connection process involves the STA sending an association request frame to the AP, and the AP responding by sending an association response frame to the STA. For example, the association request frame may include information related to various capabilities, such as the listen interval, SSID (service set identifier), supported rates, supported channels, RSN, mobile domain, supported operating classes, Traffic Indication Map Broadcast request, and interworking service capabilities. For example, a connection response frame may include information related to various capabilities, such as status code, AID (Association ID), support rate, EDCA (Enhanced Distributed Channel Access) parameter set, RCPI (Received Channel Power Indicator), RSNI (Received Signal to Noise Indicator), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, and QoS map.

[0061] Thereafter, in step S340, the STA can execute the security configuration process. The security configuration process in step S340 may include, for example, a process of private key setup via a four-way handshake using an EAPOL (Extesible Authentication Protocol over LAN) frame.

[0062] Figure 4 is a diagram showing an example of a PPDU used in IEEE standards.

[0063] As shown, various forms of PPDU (PHY protocol data unit) are used in standards such as IEEEa / g / n / ac. Specifically, the LTF and STF fields contain training signals, SIG-A and SIG-B contain control information for the receiving station, and the data field contains user data corresponding to the PSDU (MAC PDU / Aggregated MAC PDU).

[0064] Figure 4 also includes an example of an HE PPDU according to the IEEE 802.11ax standard. The HE PPDU in Figure 4 is an example of a PPDU for multiple users, and HE-SIG-B is included only for multiple users; HE-SIG-B is omitted in PPDUs for single users.

[0065] As indicated, the HE-PPDU for Multiple User (MU) may include L-STF (legacy-short training field), L-LTF (legacy-long training field), L-SIG (legacy-signal), HE-SIG-A (high efficiency-signal A), HE-SIG-B (high efficiency-signal B), HE-STF (high efficiency-short training field), HE-LTF (high efficiency-long training field), data field (or MAC payload), and PE (Packet Extension) field. Each field is transmitted during the indicated time interval (i.e., 4 or 8 μs, etc.).

[0066] The resource unit (RU) used in PPDU is described below. A resource unit can contain multiple subcarriers (or tones). Resource units are used when transmitting signals to multiple STAs based on OFDMA technology. Resource units are also defined when transmitting signals to a single STA. Resource units are used for STF, LTF, data fields, etc.

[0067] Figure 5 is a diagram showing the arrangement of resource units (RUs) used in the 20MHz bandwidth.

[0068] As shown in Figure 5, Resource Units (RUs), each corresponding to a different number of tones (i.e., subcarriers), can be used to constitute some fields of the HE-PPDU. For example, resources are allocated in the RU units shown for the HE-STF, HE-LTF, and data fields.

[0069] As shown at the top of Figure 5, 26 units (i.e., units corresponding to 26 tones) are arranged. Six tones are used as guard bands in the leftmost band of the 20MHz bandwidth, and five tones are used as guard bands in the rightmost band of the 20MHz bandwidth. In addition, seven DC tones are inserted in the center band, i.e., the DC band, and there may be 26 units corresponding to 13 tones on each side of the DC band. Furthermore, 26, 52, and 106 units are allocated to the other bands. Each unit is allocated for the receiving station, i.e., the user.

[0070] On the other hand, the RU configuration in Figure 5 can be used not only for situations involving multiple users (MU) but also for situations involving a single user (SU), in which case it is possible to use one 242 unit as shown at the bottom of Figure 5, in which case three DC tones are inserted.

[0071] As shown in the example in Figure 5, various sizes of RUs, namely 26RU, 52RU, 106RU, 242RU, etc., are proposed, the specific sizes of such RUs may be expanded or increased, so this embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones).

[0072] Figure 6 is a diagram showing the arrangement of resource units (RUs) used in the 40 MHz bandwidth.

[0073] Similar to how various sizes of RU were used in the example in Figure 5, the example in Figure 6 also uses 26RU, 52RU, 106RU, 242RU, 484RU, etc. In addition, five DC tones are inserted at the center frequency, twelve tones are used as guard bands in the leftmost band of the 40MHz bandwidth, and eleven tones are used as guard bands in the rightmost band of the 40MHz bandwidth.

[0074] Furthermore, as shown, 484 RUs can be used when used for a single user. On the other hand, the specific number of RUs can be changed, as in the example in Figure 4.

[0075] Figure 7 is a diagram showing the arrangement of resource units (RUs) used in the 80MHz bandwidth.

[0076] Similar to how various RU sizes were used in the examples in Figures 5 and 6, the example in Figure 7 can also use 26RU, 52RU, 106RU, 242RU, 484RU, 996RU, etc. Additionally, seven DC tones are inserted at the center frequency, 12 tones are used as guard bands in the leftmost band of the 80MHz bandwidth, and 11 tones are used as guard bands in the rightmost band of the 80MHz bandwidth. Furthermore, a 26RU configuration can be used, utilizing 13 tones on each side of the DC bandwidth.

[0077] Also, as shown, when used for a single user, the 996RU can be used, in which case five DC tones are inserted.

[0078] The RUs described herein are used in UL (Uplink) and DL (Downlink) communications. For example, when UL-MU communication is solicited by a trigger frame, the transmitting STA (e.g., AP) can assign a first RU (e.g., 26 / 52 / 106 / 242RU, etc.) to the first STA and a second RU (e.g., 26 / 52 / 106 / 242RU, etc.) to the second STA via the trigger frame. Thereafter, the first STA can transmit a first trigger-based PPDU based on the first RU, and the second STA can transmit a second trigger-based PPDU based on the second RU. The first and second trigger-based PPDUs are transmitted to the AP in the same time interval.

[0079] For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) can assign the first RU (e.g., 26 / 52 / 106 / 242RU) to the first STA and the second RU (e.g., 26 / 52 / 106 / 242RU) to the second STA. That is, within a single MU PPDU, the transmitting STA (e.g., AP) can transmit the HE-STF, HE-LTF, and Data fields for the first STA via the first RU, and the HE-STF, HE-LTF, and Data fields for the second STA via the second RU.

[0080] Information regarding the RU's placement is signaled via HE-SIG-B.

[0081] Figure 8 shows the structure of the HE-SIG-B field.

[0082] As shown, the HE-SIG-B field (810) includes a common field (820) and a user-specific field (830). The common field (820) may contain information that applies in common to all users receiving the SIG-B (i.e., user STA). The user-specific field (830) can be called a user-specific control field. If the SIG-B is transmitted to multiple users, the user-specific field (830) may apply to only some of those users.

[0083] As shown in Figure 8, the common field (820) and the user-specific field (830) can be encoded separately.

[0084] The common field (820) can contain N*8 bits of RU allocation information. For example, the RU allocation information can contain information about the location of the RUs. For instance, if a 20MHz channel is used as shown in Figure 5, the RU allocation information can contain information about which RUs (26RU / 52RU / 106RU) are placed in which frequency band.

[0085] An example of a case where RU allocation information consists of 8 bits is as follows:

[0086] [Table 1]

[0087] As shown in the example in Figure 5, a maximum of nine 26RUs can be allocated to a 20MHz channel. When the RU allocation information for the common field (820) is set to "00000000" as shown in Table 1, nine 26RUs are allocated to the corresponding channel (i.e., 20MHz). Also, when the RU allocation information for the common field (820) is set to "00000001" as shown in Table 1, seven 26RUs and one 52RU are allocated to the corresponding channel. In other words, in the example in Figure 5, a 52RU is allocated on the far right, and seven 26RUs are allocated to its left.

[0088] Table 1 shows only a portion of the RU locations for which RU allocation information can be displayed.

[0089] For example, RU allocation information may further include the example shown in Table 2 below.

[0090] [Table 2]

[0091] "01000y2y1y0" relates to an example where 106RU is assigned to the leftmost end of a 20MHz channel, and five 26RU are assigned to its right. In this case, a large number of STAs (e.g., User-STAs) are assigned to the 106RU based on MU-MIMO technology. Specifically, up to eight STAs (e.g., User-STAs) are assigned to the 106RU, and the number of STAs (e.g., User-STAs) assigned to the 106RU is determined based on 3-bit information (y2y1y0). For example, if the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., User-STAs) assigned to the 106RU based on MU-MIMO technology is N+1.

[0092] Typically, multiple RUs are assigned multiple distinct STAs (e.g., User STAs). However, for a single RU exceeding a certain size (e.g., 10⁶ subcarriers), multiple STAs (e.g., User STAs) are assigned based on MU-MIMO technology.

[0093] As shown in Figure 8, a user-specific field (830) can contain multiple user fields. As described above, the number of STAs (e.g., User STAs) assigned to a particular channel is determined based on the RU allocation information in the common field (820). For example, if the RU allocation information in the common field (820) is "00000000", then one User STA is assigned to each of the nine 26RUs (i.e., a total of nine User STAs are assigned). In other words, a maximum of nine User STAs can be assigned to a particular channel via OFDMA technology. Also, a maximum of nine User STAs can be assigned to a particular channel via non-MU-MIMO technology.

[0094] For example, if the RU allocation is set to "01000y2y1y0", the 106 RU located on the far left will be allocated multiple User STAs via MU-MIMO technology, and the five 26 RU located to its right will be allocated five User STAs via non-MU-MIMO technology. This case is illustrated in the example shown in Figure 9.

[0095] Figure 9 shows an example where multiple User STAs are assigned to the same RU via MU-MIMO technology.

[0096] For example, if the RU allocation is set to "01000010" as shown in Figure 9, then, based on Table 2, 106 RUs are allocated to the leftmost end of a particular channel, and five 26 RUs are allocated to its right. Additionally, a total of three User STAs are allocated to the 106 RUs via MU-MIMO technology. As a result, a total of eight User STAs are allocated, allowing the HE-SIG-B user-specific field (830) to contain eight User fields.

[0097] The eight User fields are included in the order shown in Figure 9. Also, as shown in Figure 8, two User fields are implemented within one User block field.

[0098] The User fields shown in Figures 8 and 9 are constructed based on two formats. Specifically, User fields related to MU-MIMO technology are constructed using the first format, while User fields related to non-MU-MIMO technology are constructed using the second format. Referring to an example in Figure 9, User fields 1 through 3 are based on the first format, and User fields 4 through 8 are based on the second format. Either the first or second format can contain the same length (e.g., 21 bits) of bit information.

[0099] Each User field can have the same size (e.g., 21 bits). For example, the User field in the first format (MU-MIMO technology format) is structured as follows:

[0100] For example, the first bit (e.g., B0-B10) within the User field (i.e., 21 bits) can contain identification information for the User STA to which the User field is assigned (e.g., STA-ID, partial AID, etc.). Additionally, the second bit (e.g., B11-B14) within the User field (i.e., 21 bits) can contain information regarding the spatial configuration. Specifically, an example of the second bit (i.e., B11-B14) may be the same as those shown in Tables 3 and 4 below.

[0101] [Table 3]

[0102] [Table 4]

[0103] As shown in Table 3 and / or Table 4, the second bits (i.e., B11-B14) can contain information about the number of Spatial Streams allocated to multiple User STAs allocated by MU-MIMO technology. For example, if three User STAs are allocated to 106RU based on MU-MIMO technology as shown in Figure 9, N_user is set to "3", which determines the values ​​of N_STS[1], N_STS[2], and N_STS[3] as shown in Table 3. For example, if the value of the second bits (B11-B14) is "0011", then N_STS[1]=4, N_STS[2]=1, and N_STS[3]=1. That is, in the example in Figure 9, four Spatial Streams are allocated to User field 1, one Spatial Stream is allocated to User field 2, and one Spatial Stream is allocated to User field 3.

[0104] As shown in the example in Table 3 and / or Table 4, the information regarding the number of spatial streams for a user station (User STA) (i.e., the second bits, B11-B14) consists of 4 bits. Furthermore, the information regarding the number of spatial streams for a user station (User STA) (i.e., the second bits, B11-B14) can support up to 8 spatial streams. Also, the information regarding the number of spatial streams (i.e., the second bits, B11-B14) can support up to 4 spatial streams for a single User STA.

[0105] Additionally, the third bit (i.e., B15-18) within the User field (i.e., 21 bits) can contain MCS (Modulation and Coding Scheme) information. The MCS information is applied to the data field within the PPDU containing the relevant SIG-B.

[0106] In this specification, MCS, MCS information, MCS index, MCS field, etc., can be represented by specific index values. For example, MCS information can be represented by index 0 to index 11. MCS information may include information about the constellation modulation type (e.g., BPSK, QPSK, 16_QAM, 64_QAM, 256_QAM, 1024_QAM, etc.) and information about the code rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). MCS information may exclude information about the channel coding type (e.g., BSS or LDPC).

[0107] Additionally, the fourth bit (i.e., B19) within the User field (i.e., 21 bits) is the Reserved field.

[0108] Additionally, the fifth bit (i.e., B20) within the User field (i.e., 21 bits) can contain information about the coding type (e.g., BSS or LDPC). That is, the fifth bit (i.e., B20) can contain information about the type of channel coding (e.g., BSS or LDPC) applied to the data field in the PPDU containing the relevant SIG-B.

[0109] The example above relates to the User field in the first format (the format for MU-MIMO technology). An example of the User field in the second format (the format for non-MU-MIMO technology) is as follows:

[0110] The first bit in the User field of the second format (e.g., B0-B10) can contain User STA identification information. The second bit in the User field of the second format (e.g., B11-B13) can contain information about the number of spatial streams applied to the corresponding RU. The third bit in the User field of the second format (e.g., B14) contains information about whether a beamforming steering matrix is ​​applied. The fourth bit in the User field of the second format (e.g., B15-B18) can contain MCS (Modulation and coding scheme) information. The fifth bit in the User field of the second format (e.g., B19) can contain information about whether DCM (Dual Carrier Modulation) is applied. The sixth bit in the User field of the second format (i.e., B20) can contain information about the coding type (e.g., BSS or LDPC).

[0111] Figure 10 illustrates the operation related to UL-MU. As shown, the transmitting STA (e.g., AP) can establish a channel connection via contending (i.e., backoff operation) and transmit a trigger frame (1030). That is, the transmitting STA (e.g., AP) can transmit a PPDU containing the trigger frame (1330). Once the PPDU containing the trigger frame is received, a trigger-based (TB) PPDU is transmitted after a delay equal to the SIFS.

[0112] TB PPDUs (1041, 1042) are sent during the same time period and originate from multiple STAs (e.g., User STAs) whose AIDs are displayed in the Trigger frame (1030). The ACK frame (1050) for the TB PPDU is implemented in various forms.

[0113] The specific characteristics of the trigger frame are explained through Figures 11 to 13. When UL-MU communication is used, OFDMA (orthogonal frequency division multiple access) technology or MU MIMO technology is used, or OFDMA and MU MIMO technology are used simultaneously.

[0114] Figure 11 shows an example of a trigger frame. The trigger frame in Figure 11 allocates resources for uplink MU transmission (Uplink Multiple-User transmission) and is sent, for example, from an AP. The trigger frame consists of a MAC frame and is included in the PPDU.

[0115] Each of the fields shown in Figure 11 may be partially omitted, and other fields may be added. Furthermore, the length of each field may change from what is shown.

[0116] The frame control field (1110) in Figure 11 contains information about the MAC protocol version and other additional control information, while the duration field (1120) contains time information for NAV configuration and information about the STA identifier (e.g., AID).

[0117] The RA field (1130) contains the address information of the receiving STA for the trigger frame and may be omitted if necessary. The TA field (1140) contains the address information of the STA (e.g., AP) that transmits the trigger frame, and the common information field (1150) contains common control information applicable to the receiving STA that receives the trigger frame. For example, it may include a field that indicates the length of the L-SIG field of the up PPDU transmitted in response to the trigger frame, and information that controls the content of the SIG-A field (i.e., the HE-SIG-A field) of the up PPDU transmitted in response to the trigger frame. In addition, common control information may include information regarding the length of the CP and the length of the LTF field of the up PPDU transmitted in response to the trigger frame.

[0118] Furthermore, it is desirable to include individual user information fields (1160#1 to 1160#N) corresponding to the number of receiving STAs that receive the trigger frame in Figure 11. These individual user information fields are also called "assignment fields."

[0119] Furthermore, the trigger frame in Figure 11 may include a padding field (1170) and a frame check sequence field (1180).

[0120] As shown in Figure 11, each of the individual user information fields (1160#1 to 1160#N) can again contain a number of subfields.

[0121] Figure 12 shows an example of the common information field in a trigger frame. Some of the subfields in Figure 12 may be omitted, and other subfields may be added. Also, the length of each subfield shown may be modified.

[0122] The indicated length field (1210) has the same value as the length field of the L-SIG field of the up PPDU transmitted in response to the trigger frame, and the length field of the L-SIG field of the up PPDU indicates the length of the up PPDU. Consequently, the length field (1210) of the trigger frame is used to indicate the length of the corresponding uplink PPDU.

[0123] Furthermore, the cascade indicator field (1220) indicates whether or not a cascade operation will be performed. Cascade operation means that both downlink MU transmission and uplink MU transmission are performed within the same TXOP. That is, it means that after a downlink MU transmission is performed, an uplink MU transmission will be performed after a previously set time (e.g., SIFS). In a cascade operation, there may be only one transmitting device (e.g., AP) performing downlink communication, and multiple transmitting devices (e.g., non-AP) performing uplink communication.

[0124] The CS request field (1230) indicates whether the receiving device that received the trigger frame needs to consider the status of the wireless medium, NAV, etc., when transmitting the corresponding uplink PPDU.

[0125] The HE-SIG-A information field (1240) contains information that controls the content of the SIG-A field (i.e., the HE-SIG-A field) of the up PPDU transmitted in response to the trigger frame.

[0126] The CP and LTF type fields (1250) may include information regarding the LTF length and CP length of the up PPDU transmitted in response to the trigger frame. The trigger type field (1060) may indicate the purpose for which the trigger frame is used, such as a normal trigger, a trigger for beamforming, or a request for Block ACK / NACK.

[0127] In this specification, it can be assumed that the trigger type field (1260) of a trigger frame indicates a trigger frame of type Basic for a normal trigger. For example, a trigger frame of type Basic can be called a basic trigger frame.

[0128] Figure 13 shows an example of subfields included in a per-user information field. The per-user information field (1300) in Figure 13 can be understood as one of the individual per-user information fields (1160#1 to 1160#N) mentioned in Figure 11. Some of the subfields included in the per-user information field (1300) in Figure 13 may be omitted, and other subfields may be added. Also, the length of each subfield shown may be changed.

[0129] The User Identifier field (1310) in Figure 13 indicates the identifier of the STA (i.e., the receiving STA) corresponding to the individual user information. An example of an identifier is that it may be all or part of the AID (Association Identifier) ​​value of the receiving STA.

[0130] The RU allocation field (1320) is also included. That is, when a receiving STA identified in the user identifier field (1310) transmits a TB PPDU in response to a trigger frame, it transmits the TB PPDU via the RU indicated by the RU allocation field (1320). In this case, the RU indicated by the RU allocation field (1320) is the RU shown in Figures 5, 6, and 7.

[0131] The subfield in Figure 13 may include a coding type field (1330). The coding type field (1330) can indicate the coding type of the TB PPDU. For example, if BCC coding is applied to the TB PPDU, the coding type field (1330) is set to "1", and if LDPC coding is applied, the coding type field (1330) is set to "0".

[0132] Furthermore, the subfield in Figure 13 may include an MCS field (1340). The MCS field (1340) can indicate the MCS technology to be applied to the TB PPDU. For example, if BCC coding is applied to the TB PPDU, the coding type field (1330) is set to "1", and if LDPC coding is applied, the coding type field (1330) is set to "0".

[0133] The following explains UORA (UL OFDMA-based Random Access) technology.

[0134] Figure 14 illustrates the technical characteristics of UORA technology.

[0135] A transmitting STA (e.g., AP) can allocate six RU resources via a trigger frame, as shown in Figure 14. Specifically, the AP can allocate the first RU resource (AID 0, RU1), the second RU resource (AID 0, RU2), the third RU resource (AID 0, RU3), the fourth RU resource (AID 2045, RU4), the fifth RU resource (AID 2045, RU5), and the sixth RU resource (AID 3, RU6). Information regarding AID 0, AID 3, or AID 2045 is included, for example, in the user identification field (1310) in Figure 13. Information regarding RU1 through RU6 is included, for example, in the RU allocation field (1320) in Figure 13. AID=0 signifies a UORA resource for an associated STA, and AID=2045 signifies a UORA resource for an unassociated STA. As a result, the first to third RU resources in Figure 14 are used as UORA resources for associated STAs, the fourth to fifth RU resources in Figure 14 are used as UORA resources for unassociated STAs, and the sixth RU resource in Figure 14 is used as a resource for a regular ULMU.

[0136] In the example shown in Figure 14, STA1's OBO (OFDMA random access backoff) counter decreases to 0, and STA1 randomly selects the second RU resource (AID 0, RU2). Also, since STA2 / 3's OBO counters are greater than 0, no uplink resources are assigned to STA2 / 3. Furthermore, in Figure 14, STA4's AID (i.e., AID=3) is included in the trigger frame, so the RU6 resource is assigned without backoff.

[0137] Specifically, in Figure 14, STA1 is an associated STA, so there are a total of 3 eligible RA RUs for STA1 (RU1, RU2, RU3), which reduces STA1's OBO counter by 3 until it reaches 0. Similarly, in Figure 14, STA2 is an associated STA, so there are a total of 3 eligible RA RUs for STA2 (RU1, RU2, RU3), which reduces STA2's OBO counter by 3, but the OBO counter remains greater than 0. Furthermore, in Figure 14, STA3 is an unassociated STA, so there are a total of 2 eligible RA RUs for STA3 (RU4, RU5), which reduces STA3's OBO counter by 2, but the OBO counter remains greater than 0.

[0138] Figure 15 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0139] The 2.4GHz band can be referred to by other names, such as the first band. Furthermore, the 2.4GHz band refers to the frequency range in which channels adjacent to 2.4GHz (for example, channels with center frequencies between 2.4 and 2.5GHz) are used / supported / defined.

[0140] The 2.4GHz band contains numerous 20MHz channels. Within the 2.4GHz band, 20MHz channels can have multiple channel indices (e.g., index 1 to index 14). For example, the center frequency of a 20MHz channel assigned channel index 1 is 2.412GHz, the center frequency of a 20MHz channel assigned channel index 2 is 2.417GHz, and the center frequency of a 20MHz channel assigned channel index N is (2.407 + 0.005 * N)GHz. Channel indices are referred to by various names, such as channel numbers. Specific numerical values ​​for channel indices and center frequencies may change.

[0141] Figure 15 shows four channels within the 2.4 GHz band as an example. Each of the first to fourth frequency domains (1510 to 1540) can contain one channel. For example, the first frequency domain (1510) can contain channel 1 (a 20 MHz channel with index 1). In this case, the center frequency of channel 1 is set to 2412 MHz. The second frequency domain (1520) can contain channel 6. In this case, the center frequency of channel 6 is set to 2437 MHz. The third frequency domain (1530) can contain channel 11. In this case, the center frequency of channel 11 is set to 2462 MHz. The fourth frequency domain (1540) can contain channel 14. In this case, the center frequency of channel 14 is set to 2484 MHz.

[0142] Figure 16 shows an example of channels used / supported / defined within the 5GHz band.

[0143] The 5GHz band can be referred to by other names such as the second band / band. The 5GHz band refers to the frequency domain in which channels with a center frequency between 5GHz and 6GHz (or less than 5.9GHz) are used / supported / defined. Alternatively, the 5GHz band can include multiple channels between 4.5GHz and 5.5GHz. The specific figures shown in Figure 16 are subject to change.

[0144] Multiple channels within the 5GHz band include UNII (Unlicesed National Information Infrastructure)-1, UNII-2, UNII-3, and ISM. UNII-1 can be called UNII Low. UNII-2 can include frequency domains called UNII Mid and UNII-2 Extended. UNII-3 can be called UNII-Upper.

[0145] Within the 5GHz band, multiple channels are configured, and the bandwidth of each channel can be set in various ways, such as 20MHz, 40MHz, 80MHz, or 160MHz. For example, the 5170MHz to 5330MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20MHz channels. At 5170MHz, the 5330MHz frequency domain / range can be divided into four channels via a 40MHz frequency domain. At 5170MHz, the 5330MHz frequency domain / range can be divided into two channels via an 80MHz frequency domain. Alternatively, at 5170MHz, the 5330MHz frequency domain / range can be divided into one channel via a 160MHz frequency domain.

[0146] Figure 17 shows an example of channels used / supported / defined within the 6GHz band.

[0147] The 6GHz band can be referred to by other names, such as the third band / band. The 6GHz band refers to the frequency domain in which channels with a center frequency of 5.9GHz or higher are used / supported / defined. The specific figures shown in Figure 17 are subject to change.

[0148] For example, the 20MHz channel in Figure 17 is defined starting from 5.940GHz. Specifically, the leftmost channel among the 20MHz channels in Figure 17 can have index 1 (or channel index, channel number, etc.), and its center frequency is assigned to 5.945GHz. That is, the center frequency of index N channel is determined to be (5.940 + 0.005 * N)GHz.

[0149] Therefore, the indices (or channel numbers) for the 20MHz channels in Figure 17 are 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, and 233. Furthermore, according to the (5.940 + 0.005 * N) GHz rule mentioned above, the indices for the 40 MHz channels in Figure 17 are 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, and 227.

[0150] Figure 17 shows an example with 20, 40, 80, and 160 MHz channels, but 240 MHz and 320 MHz channels will be added.

[0151] The following describes the PPDUs transmitted / received in the STA of this specification.

[0152] Figure 18 shows an example of a PPDU used in this specification.

[0153] The PPDU in Figure 18 is referred to by various names, such as EHT PPDU, transmit PPDU, receive PPDU, first type, or nth type PPDU. For example, in this specification, PPDU or EHT PPDU is referred to by various names, such as transmit PPDU, receive PPDU, first type, or nth type PPDU. Furthermore, EHT PPUs are used in EHT systems and / or new wireless LAN systems that improve upon EHT systems.

[0154] The PPDU in Figure 18 can represent some or all of the PPDU types used in an EHT system. For example, the example in Figure 18 is used for both SU (single-user) mode and MU (multi-user) mode. Also, the PPDU in Figure 18 is for one receiving STA or multiple receiving STAs. When the PPDU in Figure 18 is used for TB (Trigger-Based) mode, the EHT-SIG in Figure 18 is omitted. Furthermore, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication can transmit a PPDU in the example in Figure 18 with the EHT-SIG omitted.

[0155] In Figure 18, the L-STF to EHT-LTF sequence is called a preamble or physical preamble, and is generated, transmitted, received, acquired, and decoded in the physical layer.

[0156] In Figure 18, the subcarrier spacing for the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields is determined to be 312.5 kHz, while the subcarrier spacing for the EHT-STF, EHT-LTF, and Data fields is determined to be 78.125 kHz. That is, the tone index (or subcarrier index) for the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields can be displayed in units of 312.5 kHz, and the tone index (or subcarrier index) for the EHT-STF, EHT-LTF, and Data fields can be displayed in units of 78.125 kHz.

[0157] In Figure 18, the PPDU for L-LTF and L-STF is the same as in the conventional field.

[0158] The L-SIG field in Figure 18 can contain, for example, 24 bits of bit information. For example, the 24 bits of information can include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit ParitY bit, and a 6-bit Tail bit. For example, the 12-bit Length field can contain information about the length or time duration of the PPDU. For example, the value of the 12-bit Length field is determined based on the type of PPDU. For example, if the PPDU is a non-HT, HT, VHT PPDU or an EHT PPDU, the value of the Length field can be determined as a multiple of 3. For example, if the PPDU is an HE PPDU, the value of the Length field is determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0159] For example, the transmitting STA can apply BCC encoding based on a code rate of 1 / 2 to the 24 bits of information in the L-SIG field. Subsequently, the transmitting STA can obtain 48 bits of BCC encoded data. BPSK modulation is applied to these 48 bits to generate 48 BPSK symbols. The transmitting STA can map these 48 BPSK symbols to positions excluding the pilot subcarriers {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols are mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can further map the signals {-1,-1,-1,1} to subcarrier indices {-28, -27, +27, 28}. The above signal is used for channel estimation for the frequency domains corresponding to {-28, -27, +27, 28}.

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

[0161] After the RL-SIG in Figure 18, a U-SIG (Universal SIG) is inserted. The U-SIG can be called by various names such as the first SIG field, first SIG, first type SIG, control signal, control signal field, and first (type) control signal.

[0162] A U-SIG can contain N bits of information and may include information to identify the type of EHT PPDU. For example, a U-SIG is composed of two symbols (e.g., two consecutive OFDM symbols). Each symbol for the U-SIG (e.g., an OFDM symbol) can have a duration of 4 us. Each symbol of the U-SIG is used to transmit 26 bits of information. For example, each symbol of the U-SIG is transmitted and received based on 52 data tones and 4 pilot tones.

[0163] Through a U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 uncoded bits) can be transmitted, with the first symbol of the U-SIG transmitting the first X bits of the total A-bit information (e.g., 26 uncoded bits), and the second symbol of the U-SIG transmitting the remaining Y bits of the total A-bit information (e.g., 26 uncoded bits). For example, a transmitting STA can obtain the 26 uncoded bits contained in each U-SIG symbol. The transmitting STA can perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52-coded bits and perform interleaving on the 52-coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols to be assigned to each U-SIG symbol. A single U-SIG symbol is transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA are transmitted based on the remaining tones (subcarriers), excluding the pilot tones -21, -7, +7, and +21.

[0164] For example, the A-bit information transmitted by the U-SIG (e.g., 52 uncoded bits) may include a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit field). The CRC field and tail field are transmitted via a second symbol of the U-SIG. The CRC field is generated based on the 26 bits assigned to the first symbol of the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and is generated based on a conventional CRC calculation algorithm. The tail field is used to terminate the trellis of the convolutional decoder and is set to, for example, "000000".

[0165] The A-bit information transmitted by a U-SIG (or U-SIG field) (e.g., 52 uncoded bits) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of the U-SIG, or they may be assigned to both the first and second symbols of the U-SIG. For example, the version-independent bits and version-dependent bits can be referred to by various names, such as the first control bits and the second control bits.

[0166] For example, the version-independent bits of the U-SIG can contain a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier can contain information related to the PHY version of the transmitted and received PPDUs. For example, the first value of the 3-bit PHY version identifier can indicate that the transmitted and received PPDUs are EHT PPDUs. Also, when a transmitting STA transmits an EHT PPDU, it can set the 3-bit PHY version identifier to the first value. Also, a receiving STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier with the first value.

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

[0168] For example, the version-independent bits of the U-SIG can contain information about the length of the TXOP and information about the BSS color ID.

[0169] For example, if an EHT PPDU can be divided into various types (e.g., EHT PPDUs related to SU mode, EHT PPDUs related to MU mode, EHT PPDUs related to TB mode, EHT PPDUs related to Extended Range transmission, etc.), then information regarding the type of EHT PPDU is included in the version-dependent bits of the U-SIG.

[0170] For example, a U-SIG may include information about: 1) a bandwidth field containing information about bandwidth; 2) a field containing information about the MCS technology applied to the EHT-SIG; 3) an indicator field containing information related to whether or not dual subcarrier modulation (DCM) technology is applied to the EHT-SIG; 4) a field containing information about the number of symbols used for the EHT-SIG; 5) a field containing information about whether or not the EHT-SIG is generated across the entire bandwidth; 6) a field containing information about the type of EHT-LTF / STF; and 7) fields indicating the length of the EHT-LTF and the CP length.

[0171] Preamble puncturing is applied to the PPDU in Figure 18. Preamble puncturing means that puncturing is applied to a portion of the PPDU's overall bandwidth (for example, a secondary 20MHz bandwidth). For example, if an 80MHz PPDU is transmitted, the STA will apply puncturing to the secondary 20MHz bandwidth of the 80MHz band, allowing the PPDU to be transmitted only through the primary 20MHz bandwidth and the secondary 40MHz bandwidth.

[0172] For example, preamble puncturing patterns are pre-set. For example, if the first puncturing pattern is applied, puncturing is applied only to the secondary 20MHz band within the 80MHz band. For example, if the second puncturing pattern is applied, puncturing is applied to only one of the two secondary 20MHz bands included in the secondary 40MHz band within the 80MHz band. For example, if the third puncturing pattern is applied, puncturing is applied only to the secondary 20MHz band included in the primary 80MHz band within the 160MHz band (or 80+80MHz band). For example, if the fourth puncturing pattern is applied, the primary 40MHz band included in the primary 80MHz band within the 160MHz band (or 80+80MHz band) is present, and puncturing is applied to at least one 20MHz channel that does not belong to the primary 40MHz band.

[0173] Information regarding preamble puncturing applied to the PPDU is included in the U-SIG and / or EHT-SIG. For example, the first field of the U-SIG may contain information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may contain information regarding preamble puncturing applied to the PPDU.

[0174] For example, U-SIGs and EHT-SIGs can include information about preamble puncturing based on the following method: If the bandwidth of the PPDU exceeds 80 MHz, the U-SIGs are configured individually in 80 MHz units. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU includes a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG contains information about the 160 MHz bandwidth, and the second field of the first U-SIG can contain information about preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern). Also, the first field of the second U-SIG contains information about the 160 MHz bandwidth, and the second field of the second U-SIG can contain information about preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern). On the other hand, an EHT-SIG following the first U-SIG may contain information about preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern), and an EHT-SIG following the second U-SIG may contain information about preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern).

[0175] Furthermore, or more generally, U-SIG and EHT-SIG can include information about preamble puncturing based on the following methods: U-SIG can include information about preamble puncturing for all bandwidths (i.e., information about preamble puncturing patterns). That is, EHT-SIG does not include information about preamble puncturing, and only U-SIG can include information about preamble puncturing (i.e., information about preamble puncturing patterns).

[0176] U-SIGs are configured in 20MHz units. For example, when an 80MHz PPDU is configured, the U-SIGs are duplicated; that is, the 80MHz PPDU contains four identical U-SIGs. PPDUs with a bandwidth exceeding 80MHz can contain different U-SIGs.

[0177] U-SIGs are configured in 20MHz units. For example, when an 80MHz PPDU is configured, the U-SIGs are duplicated; that is, the 80MHz PPDU contains four identical U-SIGs. PPDUs with a bandwidth exceeding 80MHz can contain different U-SIGs.

[0178] The EHT-SIG in Figure 18 may contain control information for the receiving STA. The EHT-SIG is transmitted via at least one symbol, which may have a length of 4 us. Information regarding the number of symbols used for the EHT-SIG is included in the U-SIG.

[0179] EHT-SIG incorporates the technical features of HE-SIG-B as described in Figures 8 and 9. For example, EHT-SIG can include common fields and user-specific fields, similar to the example in Figure 8. Common fields in EHT-SIG are omitted, and the number of user-specific fields is determined based on the number of users.

[0180] Similar to the example in Figure 8, the common fields and user-specific fields of the EHT-SIG are coded separately. A single user block field within a user-specific field can contain information for two users, while the last user block field within a user-specific field can contain information for one user. In other words, a single user block field in an EHT-SIG can contain a maximum of two user fields. Similar to the example in Figure 9, each user field is either related to MU-MIMO assignment or non-MU-MIMO assignment.

[0181] Similar to the example in Figure 8, the common field of the EHT-SIG can include a CRC bit and a Tail bit, with the length of the CRC bit determined to be 4 bits and the length of the Tail bit determined to be 6 bits and set to "000000".

[0182] Similar to the example in Figure 8, the common fields of the EHT-SIG can include RU allocation information. RU allocation information refers to information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are allocated. RU allocation information is composed of 8-bit (or N-bit) units, as in Table 1.

[0183] Tables 5 through 7 show examples of 8-bit (or N-bit) information for various RU allocations. Each table and the displayed index can be modified, and some entries may be omitted from Tables 5 through 7, while others may be added that are not displayed.

[0184] Tables 5 through 7 provide examples related to information about the location of RUs allocated in the 20MHz band. For example, "Index 0" in Table 5 is used in a situation where nine 26RUs are allocated individually (for example, the situation shown in Figure 5 where nine 26RUs are allocated individually).

[0185] On the other hand, in the EHT system, multiple RUs can be assigned to a single STA. For example, in "Index 60" in Table 6, one 26RU is assigned to one user (i.e., a receiving STA) at the left end of the 20MHz band, one 26RU and one 52RU are assigned to another user (i.e., a receiving STA) to its right, and five 26RUs are individually assigned to the right of those.

[0186] [Table 5]

[0187] [Table 6]

[0188] [Table 7]

[0189] A mode in which the common field of the EHT-SIG is omitted is supported. This mode in which the common field of the EHT-SIG is omitted can be called compressed mode. When compressed mode is used, multiple users of the EHT PPDU (i.e., multiple receiving STAs) can decode the PPDU (e.g., the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) received over the same frequency band. On the other hand, when non-compressed mode is used, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU can receive the PPDU (e.g., the data field of the PPDU) over different frequency bands.

[0190] The EHT-SIG is constructed based on various MCS techniques. As mentioned above, information related to the MCS techniques applied to the EHT-SIG is included in the U-SIG. The EHT-SIG is constructed based on DCM techniques. For example, of the N data tones allocated for the EHT-SIG (e.g., 52 data tones), the first modulation technique is applied to half of the consecutive tones, and the second modulation technique is applied to the remaining half of the consecutive tones. That is, the transmitting STA can modulate specific control information to a first symbol based on the first modulation technique and assign it to half of the consecutive tones, and modulate the same control information to a second symbol based on the second modulation technique and assign it to the remaining half of the consecutive tones. As mentioned above, information related to whether or not DCM techniques are applied to the EHT-SIG (e.g., a 1-bit field) is included in the U-SIG. The EHT-STF in Figure 18 is used to improve automatic gain control estimation in MIMO (multiple input multiple output) or OFDMA environments. The EHT-LTF in Figure 18 is used to estimate the channel in a MIMO or OFDMA environment.

[0191] The EHT-STF in Figure 18 can be configured in various types. For example, the first type of STF (i.e., 1x STF) is generated based on a first-type STF sequence in which non-zero coefficients are placed in 16 subcarrier intervals. The STF signal generated based on the first-type STF sequence can have a period of 0.8 μs, and a 0.8 μs periodic signal repeats 5 times to become a first-type STF with a length of 4 μs. For example, the second type of STF (i.e., 2x STF) is generated based on a second-type STF sequence in which non-zero coefficients are placed in 8 subcarrier intervals. The STF signal generated based on the second-type STF sequence can have a period of 1.6 μs, and a 1.6 μs periodic signal repeats 5 times to become a second-type EHT-STF with a length of 8 μs. Below, an example of a sequence for constructing an EHT-STF (i.e., an EHT-STF sequence) is presented. The following sequence can be modified in various ways.

[0192] EHT-STF is constructed based on the following M sequence.

[0193] [Mathematics 1] M={-1,-1,-1,1,1,1,-1,1,1,1,-1,1,1,-1,1}

[0194] The EHT-STF for a 20MHz PPDU is constructed based on the following formula. The following example is a first-type (i.e., 1x STF) sequence. For example, a first-type sequence is included in an EHT-PPDU that is not a TB (trigger-based) PPDU. In the following formula, (a:b:c) means an interval defined as b tone interval (i.e., subcarrier interval) from a tone index (i.e., subcarrier index) to c tone index. For example, formula 2 below can represent a sequence defined as a 16-tone interval from tone index -112 to index 112. Since a subcarrier spacing of 78.125kHz is applied to the EHT-STF, a 16-tone interval means that the EHT-STF coefficient (or element) is placed in a 78.125*16=1250kHz interval. Also, * means multiplication and sqrt() means square root.

[0195] [Math 2] EHT-STF(-112:16:112)={M}*(1+j) / sqrt(2) EHT-STF(0)=0

[0196] The EHT-STF for a 40MHz PPDU is constructed based on the following formula. The following example is a first-type (i.e., 1x STF) sequence.

[0197] [Math 3] EHT-STF(-240:16:240)={M,0,-M}*(1+j) / sqrt(2)

[0198] The EHT-STF for an 80MHz PPDU is constructed based on the following formula. The following example is a first-type (i.e., 1x STF) sequence.

[0199] [Math 4] EHT-STF(-496:16:496)={M,1,-M,0,-M,1,-M}*(1+j) / sqrt(2)

[0200] The EHT-STF for a 160MHz PPDU is constructed based on the following formula. The following example is a first-type (i.e., 1x STF) sequence.

[0201] [Number 5] EHT-STF(-1008:16:1008)={M,1,-M,0,-M,1,-M,0,-M,-1,M,0,-M,1,-M}*(1+j) / sqrt(2)

[0202] For an 80+80MHz PPDU, the sequence for the lower 80MHz of the EHT-STF is the same as in Equation 4. For an 80+80MHz PPDU, the sequence for the upper 80MHz of the EHT-STF is constructed based on the following formula.

[0203] [Number 6] EHT-STF(-496:16:496)={-M,-1,M,0,-M,1,-M}*(1+j) / sqrt(2)

[0204] Equations 7 through 11 below relate to an example of a second-type (i.e., 2x STF) sequence.

[0205] [Number 7] EHT-STF(-120:8:120)={M,0,-M}*(1+j) / sqrt(2)

[0206] The EHT-STF for 40MHz PPDU is constructed based on the following formula.

[0207] [Number 8] EHT-STF(-248:8:248)={M,-1,-M,0,M,-1,M}*(1+j) / sqrt(2) EHT-STF(-248)=0 EHT-STF(248)=0

[0208] The EHT-STF for 80MHz PPDU is constructed based on the following formula.

[0209] [Number 9] EHT-STF(-504:8:504)={M,-1, M,-1,-M,-1, M,0,-M,1,M,1,-M,1,-M}*(1+j) / sqrt(2)

[0210] The EHT-STF for 160MHz PPDU is constructed based on the following formula.

[0211] [Number 10] EHT-STF(-1016:16:1016)={M,-1,M,-1,-M,-1,M,0,-M,1,M,1,-M,1,-M,0,-M,1,-M,1,M,1,-M,0,-M,1,M,1,-M,1,-M}*(1+j) / sqrt(2) EHT-STF(-8)=0, EHT-STF(8)=0, EHT-STF(-1016)=0,EHT-STF(1016)=0

[0212] For an 80+80MHz PPDU, the sequence for the lower 80MHz of the EHT-STF is the same as in equation 9. For an 80+80MHz PPDU, the sequence for the upper 80MHz of the EHT-STF is constructed based on the following equation.

[0213] [Number 11] EHT-STF(-504:8:504)={-M,1,-M,1,M,1,-M,0,-M,1,M,1,-M,1,-M}*(1+j) / sqrt(2) EHT-STF(-504)=0, EHT-STF(504)=0

[0214] EHT-LTFs can have first, second, and third types (i.e., 1x, 2x, and 4x LTFs). For example, first / second / third type LTFs are generated based on LTF sequences in which non-zero coefficients are placed in 4 / 2 / 1 subcarrier intervals. First / second / third type LTFs can have time lengths of 3.2 / 6.4 / 12.8 μs. In addition, various lengths of GI (e.g., 0.8 / 1 / 6 / 3.2 μs) can be applied to first / second / third type LTFs.

[0215] Information regarding the type of STF and / or LTF (including information regarding GI applicable to the LTF) is contained in the SIG A field and / or SIG B field in Figure 18, etc.

[0216] The PPDU in Figure 18 (i.e., EHT-PPDU) is constructed based on the examples in Figures 5 and 6.

[0217] For example, an EHT PPDU transmitted over a 20MHz bandwidth, i.e., a 20MHz EHT PPDU, is constructed based on the RUs shown in Figure 5. That is, the locations of the RUs for the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU are determined as shown in Figure 5.

[0218] An EHT PPDU transmitted over the 40MHz bandwidth, i.e., a 40MHz EHT PPDU, is constructed based on the RUs shown in Figure 6. That is, the location of the RUs for the EHT-STF, EHT-LTF, and data field included in the EHT PPDU is determined as shown in Figure 6.

[0219] Since the RU position in Figure 6 corresponds to 40MHz, repeating the pattern in Figure 6 twice will determine the tone plan for 80MHz. In other words, the 80MHz EHT PPDU is transmitted based on a new tone plan in which the RU in Figure 6 (which is not the RU in Figure 7) is repeated twice.

[0220] If the pattern in Figure 6 is repeated twice, the DC region will consist of 23 tones (i.e., 11 guard tones + 12 guard tones). That is, a tone plan for an 80MHz EHT PPDU allocated based on OFDMA can have 23 DC tones. On the other hand, an 80MHz EHT PPDU allocated based on Non-OFDMA (i.e., a non-OFDMA full bandwidth 80MHz PPDU) can be configured based on 996RU and may include 5 DC tones, 12 left-side guard tones, and 11 right-side guard tones.

[0221] The tone plan for 160 / 240 / 320MHz consists of the pattern shown in Figure 6 repeated many times.

[0222] The PPDU in Figure 18 is identified as an EHT PPDU based on the following method.

[0223] The receiving STA can determine the type of the received PPDU to be an EHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) an RL-SIG (where the L-SIG is repeated) is detected in the received PPDU, and 3) applying "modulo3" to the value of the Length field of the L-SIG of the received PPDU results in "0", then the received PPDU is determined to be an EHT PPDU. If the received PPDU is determined to be an EHT PPDU, the receiving STA can detect the type of the EHT PPDU (e.g., SU / MU / Trigger-Based / Extended Range type) based on the bit information contained in the symbols after the RL-SIG in Figure 18. Furthermore, the receiving STA can determine that the received PPDU is an EHT PPDU based on 1) the first symbol after the L-LTF signal which is BSPK, 2) the RL-SIG which is consecutive to the L-SIG field and is the same as the L-SIG, and 3) the L-SIG which includes the Length field where the result of applying "modulo3" is set to "0".

[0224] For example, a receiving STA can determine the type of the received PPDU to be an HE PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, 2) an RL-SIG (where L-SIG is repeated) is detected, and 3) the result of applying "modulo3" to the Length value of L-SIG is detected as "1" or "2", then the received PPDU is determined to be an HE PPDU.

[0225] For example, the receiving STA can determine the type of the received PPDU as non-HT, HT, or VHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, and 2) no RL-SIG (where L-SIG is repeated) is detected, the received PPDU is determined to be non-HT, HT, or VHT PPDU. Also, even if the receiving STA detects a repetition of RL-SIG, if the result of applying "modulo3" to the Length value of L-SIG is detected as "0", the received PPDU is determined to be non-HT, HT, or VHT PPDU.

[0226] In the following example, signals referred to as (transmit / receive / up / down) signals, (transmit / receive / up / down) frames, (transmit / receive / up / down) packets, (transmit / receive / up / down) data units, (transmit / receive / up / down) data, etc., are signals transmitted and received based on the PPDU in Figure 18. The PPDU in Figure 18 is used to transmit and receive various types of frames. For example, the PPDU in Figure 18 is used for control frames. An example of a control frame may include RTS (request to send), CTS (clear to send), PS-Poll (Power Save-Poll), Block ACK Req, Block ACK, NDP (Null Data Packet) announcement, and Trigger frame. For example, the PPDU in Figure 18 is used for management frames. An example of a management frame may include Beacon frames, (Re-)Association request frames, (Re-)Association response frames, Probe request frames, and Probe response frames. For example, the PPDU in Figure 18 is used for data frames. For example, the PPDU in Figure 18 may be used to transmit at least two or more of the following simultaneously: control frames, management frames, and data frames.

[0227] Figure 19 shows a modified example of the transmitting and / or receiving apparatus described herein.

[0228] Each device / STA in Figures 1(a) / (b) is modified as shown in Figure 19. The transceiver (630) in Figure 19 is the same as the transceivers (113, 123) in Figure 1. The transceiver (630) in Figure 19 may include a receiver and a transmitter.

[0229] The processor (610) in Figure 19 is the same as the processors (111, 121) in Figure 1. Alternatively, the processor (610) in Figure 19 is the same as the processing chips (114, 124) in Figure 1.

[0230] The memory (150) in Figure 19 is the same as the memory (112, 122) in Figure 1. Alternatively, the memory (150) in Figure 19 is a different external memory than the memory (112, 122) in Figure 1.

[0231] Referring to Figure 19, the power management module (611) manages power to the processor (610) and / or transceiver (630). The battery (612) supplies power to the power management module (611). The display (613) outputs the results processed by the processor (610). The keypad (614) receives inputs used by the processor (610). The keypad (614) can display on the display (613). The SIM card (615) is an integrated circuit used to securely store IMSI (international mobile subscriber identity) and associated keys used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers.

[0232] Referring to Figure 19, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related inputs used by the processor (610).

[0233] 1.802.11ax Wireless LAN System Tone Plan

[0234] In this specification, "tone plan" refers to the rules that determine the size and / or location of a Resource Unit (RU). Below, we describe the tone plan applicable to PPDUs under the IEEE 802.11ax standard, i.e., HE PPDUs. We also describe the RU size and location applicable to HE PPDUs, and the control information related to RUs applicable to HE PPDUs.

[0235] In this specification, control information related to a RU (or control information related to a tone plan) may include control information regarding the size of the RU, its location, information about the User STA assigned to a particular RU, the frequency bandwidth for the PPDU containing the RU, and / or the modulation technique applied to a particular RU. The control information related to the RU is contained in the SIG field. For example, in the IEEE 802.11ax standard, the control information related to the RU is contained in the HE-SIG-B field. That is, in the process of generating a transmitted PPDU, a transmitting STA can include control information for the RU contained in the PPDU in the HE-SIG-B field. A receiving STA can also receive the HE-SIG-B contained in a received PPDU, obtain the control information contained in the HE-SIG-B, determine if there is an RU assigned to the receiving STA, and decode the assigned RU based on the HE-SIG-B.

[0236] In the IEEE 802.11ax standard, the HE-STF, HE-LTF, and Data fields are configured in units of RU (Routing Unit). That is, when a first RU is configured for a first receiving STA, the STF / LTF / Data fields for the first receiving STA are transmitted and received via the first RU.

[0237] The IEEE 802.11ax standard defines separate PPDUs for a single receiving STA (i.e., SU PPDU) and for multiple receiving STAs (i.e., MU PPDU), and each has its own defined tone plan. The specific details are explained below.

[0238] A RU defined as 11ax can contain multiple subcarriers. For example, if a RU contains N subcarriers, it can be expressed as an N-tone RU or NRU. The location of a particular RU can be expressed as a subcarrier index. A subcarrier index is defined as a subcarrier frequency spacing unit. In the 11ax standard, the subcarrier frequency spacing is 312.5 kHz or 78.125 kHz, and the subcarrier frequency spacing for a RU is 78.125 kHz. That is, subcarrier index +1 for a RU means a location 78.125 kHz higher than the DC tone, and subcarrier index -1 for a RU means a location 78.125 kHz lower than the DC tone. For example, if the location of a particular RU is expressed as [-121:-96], the RU is located in the region from subcarrier index -121 to subcarrier index -96, and consequently, the RU can contain 26 subcarriers.

[0239] The N-tone RU can include a pre-set pilot tone.

[0240] 2. Null subcarrier and pilot subcarrier

[0241] This section explains subcarriers and resource allocation in 802.11ax systems.

[0242] OFDM symbols are composed of subcarriers, and the number of subcarriers can function as the bandwidth of the PPDU. In wireless LAN 802.11 systems, data subcarriers used for data transmission, pilot subcarriers used for phase information and parameter tracking, and unused subcarriers not used for data transmission or pilot transmission are defined.

[0243] HE MU PPDUs using OFDMA transmission are transmitted as a mixture of 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, and 996-tone RU.

[0244] Here, a 26-tone RU consists of 24 data subcarriers and 2 pilot subcarriers. A 52-tone RU consists of 48 data subcarriers and 4 pilot subcarriers. A 106-tone RU consists of 102 data subcarriers and 4 pilot subcarriers. A 242-tone RU consists of 234 data subcarriers and 8 pilot subcarriers. A 484-tone RU consists of 468 data subcarriers and 16 pilot subcarriers. A 996-tone RU consists of 980 data subcarriers and 16 pilot subcarriers.

[0245] 1) Null subcarrier

[0246] As shown in Figures 5 to 7, null subcarriers are located between the 26-tone RU, 52-tone RU, and 106-tone RU positions. Null subcarriers are located around DC or edge tones to protect against transmit center frequency leakage, receiver DC offset, and interference from adjacent RUs. Null subcarriers have zero energy. The indices of null subcarriers are listed below.

[0247] [Table 8]

[0248] The null subcarrier position for each 80MHz frequency segment of an 80+80MHz HE PPDU must follow the position of the 80MHz HE PPDU.

[0249] 2) Pilot subcarrier

[0250] If a pilot subcarrier exists in the HE-LTF field of HE SU PPDU, HE MU PPDU, HE ER SU PPDU, or HE TB PPDU, the position of the pilot sequence within the HE-LTF field and data field is the same as the position in 4x HE-LTF. In 1x HE-LTF, the position of the pilot sequence within HE-LTF consists of the pilot subcarrier for the data field multiplied by 4. If a pilot subcarrier exists in 2x HE-LTF, the position of the pilot subcarrier must be the same as the position of the pilot within 4x data symbols. All pilot subcarriers are located in the even-numbered indices listed below.

[0251] [Table 9]

[0252] [Table 10]

[0253] At 160MHz or 80+80MHz, the pilot subcarrier must use the same 80MHz position relative to both sides of 80MHz.

[0254] 3. HE transmission procedure and phase rotation

[0255] In the 802.11ax wireless LAN system, the transmission procedures at the PHY (physical) layer include the transmission procedures for HE SU (Single User) PPDU, the transmission procedures for HE ER (Extended Range) SU PPDU, the transmission procedures for HE MU (Multi User) PPDU, and the transmission procedures for HE TB (trigger-Based) PPDU. The FORMAT field of the PHY-TXSTART.request (TXVECTOR) is the same as HE_SU, HE_MU, HE_ER_SU, or HE_TB. The above-mentioned transmission procedures do not describe the operation of optional features such as DCM (Dual Carrier Modulation). Among the various transmission procedures, FIG. 21 shows only the PHY transmission procedure for the HE SU PPDU.

[0256] FIG. 20 shows an example of the PHY transmission procedure for the HE SU PPDU.

[0257] To transmit data, the MAC generates a PHY-TXSTART.request primitive that causes the PHY entity to enter the transmission state. Also, the PHY is set to operate at an appropriate frequency via station management through the PLME. Other transmission parameters such as HE-MCS, coding type, and transmission power are set via the PHY-SAP using the PHY-TXSTART.request (TXVECTOR) primitive. After transmitting a PPDU that conveys a trigger frame, the MAC sublayer can issue a PHY-TRIGGER.request together with a TRIGVECTOR parameter that provides the information necessary for the PHY entity to demodulate the expected HE TB PPDU response.

[0258] The PHY indicates the state of the primary channel and other channels via PHY-CCA.indication. PPDU transmission must be initiated by the PHY after receiving PHY-TXSTART.request(TXVECTOR)primitive.

[0259] After the PHY preamble transmission begins, the PHY entity immediately starts data scrambling and data encoding. The encoding method for data fields is based on the TXVECTOR's FEC_CODING, CH_BANDWIDTH, NUM_STS, STBC, MCS, and NUM_USERS parameters.

[0260] The SERVICE field and PSDU are encoded in the transmitter block diagram described later. Data must be exchanged between the MAC and the PHY via a series of PHY-DATA.request(DATA) primitives issued by the MAC and PHY-DATA.confirm primitives issued by the PHY. PHY padding bits are appended to the PSDU to make the number of bits in the coded PSDU an integer multiple of the number of bits coded for each OFDM symbol.

[0261] Transmission is terminated early by MAC via the PHY-TXEND.request primitive. PSDU transmission is terminated upon receiving the PHY-TXEND.request primitive. Each PHY-TXEND.request primitive can indicate that it was received from the PHY along with the PHY-TXEND.confirm primitive.

[0262] Packet extensions and / or signal extensions can exist in a PPDU. The PHY-TXEND.confirm primitive is generated at the actual end time, packet extension end time, and signal extension end time of the most recent PPDU.

[0263] In PHY, the GI (Guard Interval) specified by the TXVECTOR's GI_TYPE parameter along with the GI duration is inserted into all data OFDM symbols as a countermeasure against delay spread.

[0264] Once the PPDU transmission is complete, the PHY entity will enter the receiving state.

[0265] Figure 21 shows an example of a transmitter block diagram that generates each field of the HE PPDU.

[0266] The following block diagram is used to generate each field of the HE PPDU.

[0267] a) Pre-fecpy padding

[0268] b) Scrambler

[0269] c) FEC (BCC or LDPC) encoders

[0270] d) post-FECPHY padding

[0271] e) Streamparser

[0272] f) Segment parser (for continuous 160MHz and non-contiguous 80+80MHz transmission)

[0273] g) BCC interleaver

[0274] h)星座映射器

[0275] i)DCM音调映射器

[0276] j)导频插入

[0277] k)在多个20MHz上进行复制(针对带宽>20MHz)

[0278] l)乘以1 st P的列 HE-LTF

[0279] m)LDPC音调映射器

[0280] n)段解复用器

[0281] o)单空间流的空时分组码(STBC)编码器

[0282] p)每个STS插入的循环移位分集(CSD)

[0283] q)空间映射器

[0284] r)频率映射

[0285] s)离散傅里叶逆变换(IDFT)

[0286] f)每个链插入的循环移位分集(CSD)

[0287] u)保护间隔(GI)插入

[0288] v) Windowing

[0289] Figure 21 shows a transmitter block diagram used to generate the data field of an HE SU (Single User) PPDU transmitted in the 160 MHz band using LDPC encoding. If the transmitter block diagram is used to generate the data field of an HE SU PPDU transmitted in the 80+80 MHz band, the segment deparser is not performed as shown in Figure 21. That is, if the segment parser is divided into an 80 MHz band and another 80 MHz band, a transmitter block diagram is used for each 80 MHz band.

[0290] Referring to Figure 21, the data field (or data bit sequence) is encoded into an LDPC encoder. The data bit sequence input to the LDPC encoder is scrambled by a scrambler.

[0291] The data bit sequence encoded by the LDPC encoder is divided into multiple spatial streams by a stream parser. At this point, the encoded data bit sequence divided into each spatial stream can be called a spatial block. The number of spatial blocks is determined by the number of spatial streams used for transmission by the PPDU, and is set in the same way as the number of spatial streams.

[0292] Each spatial block is divided into at least one data fragment by a segment parser. When a data field is transmitted in a 160 MHz band as shown in Figure 22, the 160 MHz band is divided into two 80 MHz bands, and each 80 MHz band is divided into a first data fragment and a second data fragment. Thereafter, the first and second data fragments are constellation mapped to the respective 80 MHz bands, resulting in an LDPC mapping.

[0293] In HE MU transmission, the PPDU encoding processor runs independently in each Resource Unit (RU) for each user up to the input of the spatial mapping block, except that CSD (cyclic shift diversity) is performed with knowledge of the spatial-temporal stream start index for the relevant user. All user data in the RU is combined and mapped into the transmission chain of the spatial mapping block.

[0294] In 802.11ax, phase rotation is applied to the fields from the legacy preamble to just before the HE-STF, and the phase rotation value is defined in 20MHz increments. That is, among the HE PPDU fields defined in 802.11ax, phase rotation is applied to L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B.

[0295] The L-STF of HE PPDU is configured as follows:

[0296] [Table 11]

[0297] [Table 12]

[0298] The L-LTF of HE PPDU is structured as follows:

[0299] [Table 13]

[0300] The L-SIG of the HE PPDU is configured as follows:

[0301] [Table 14]

[0302] [Table 15]

[0303] The RL-SIG of the HE PPDU is configured as follows:

[0304] [Table 16]

[0305] [Table 17]

[0306] 4. Examples applicable to this specification

[0307] Wireless LAN 802.11 systems consider using wider bandwidth than existing 11ax or transmitting increased streams using more antennas to increase peak throughput. This specification also considers methods of aggregating multiple links or aggregating multiple RUs and assigning them to a single STA for transmission.

[0308] This specification considers a method for assigning and transmitting multiple RUs to a single STA, and proposes methods for aggregating RUs across various bandwidths. In particular, this specification focuses on proposing a method for aggregating large-sized RUs (large-RUs) in OFDMA transmission.

[0309] In existing 802.11ax, when performing OFDMA transmission, each STA was assigned to only one RU, which meant that RUs of other sizes besides the defined RU could not be considered, resulting in shortcomings in terms of efficiency and channel availability. 802.11be overcomes these shortcomings by considering a method of assigning multiple RUs to a single STA for transmission, and this specification proposes several principles and various combinations for RU aggregation during OFDMA transmission.

[0310] The various sizes of RU proposed in 802.11ax are as follows:

[0311] 26 / 52 / 106 / 242 / 484 / 996 / 2x996RU

[0312] In this specification, RUs with fewer than 242 tones are assumed to be small-RUs, and RUs with 242 or more tones are assumed to be large-RUs. Furthermore, since there is no significant benefit in combining small-RUs and large-RUs from an efficiency standpoint, when RU aggregation, only combinations between small-RUs and combinations between large-RUs are considered, and this specification proposes combinations between large-RUs. In addition, preamble puncturing situations are also taken into consideration. However, in each 80MHz subchannel of various bandwidths, in order to minimize interference during preamble puncturing, the tone plan of the adjacent 20MHz channel can be replaced with a 20MHz tone plan, or a tone plan in which only the corresponding 20MHz portion of the 80MHz tone plan has been partially shifted can be used. Of course, it is also possible to transmit using the remaining channel excluding the preamble-punctured 20MHz by using hardware / filters that can effectively control interference, without changing the tone plan of the adjacent 20MHz channel, i.e., by using the conventional 80MHz tone plan as is. Alternatively, when using a 242-tone RU on a preamble-punctured 20MHz adjacent channel, the encoding is applied using the 802.11ax 242-tone RU method, but during transmission, some adjacent tones of the punctured channel within the 242-tone RU can be forcibly punctured or transmitted with reduced power. Here, when each 80MHz subchannel is divided into lower 40MHz and higher 40MHz, if a preamble-punctured 20MHz channel exists in each 40MHz subchannel, it refers to the other 20MHz channels.Furthermore, at lower 40MHz or higher 40MHz that are not preamble puncturing, the 484-tone RU (the 484-tone RU located at the corresponding 40MHz in the 80MHz tone plan) can be used during transmission, and at 20MHz adjacent to a preamble punctured 20MHz, the 242-tone RU (the 242-tone RU located at the corresponding 20MHz in the 80MHz tone plan, or the 242-tone RU located at the corresponding 20MHz in a tone plan modified to reduce interference) can be used during transmission. This method applies as is to all of the following preamble puncturing situations.

[0313] 4.1. Principles

[0314] In PPDU transmissions with a bandwidth of 160 / 80MHz or higher, if there are two or more 80MHz subchannels and RUs are combined to create a specific bandwidth, the combination of RUs that can create the maximum bandwidth for each 80MHz subchannel is utilized, and the combination of RUs that creates a large bandwidth is given priority for allocation. For example, when transmitting with a 160 / 80MHz bandwidth, if each 80MHz subchannel is not preamble puncturing, a 996-tone RU (80MHz) can be used, and if preamble puncturing is performed, various combinations such as 242+484-tone RU (60MHz), 484 / 242+242-tone RU (40MHz), and 242-tone RU (20MHz) can be considered. Assuming that the first 80MHz subchannel has a maximum of 60MHz available and the second 80MHz subchannel has a maximum of 40MHz available, it is possible to assign an 80MHz bandwidth to a specific STA and 20MHz to another STA to transmit an OFDMA PPDU. In this case, the only RU combinations to create the 80MHz bandwidth are the 242+484-tone RU in the first 80MHz subchannel and the 242-tone RU in the second 80MHz subchannel. The combination of the 484 / 242+242-tone RU in the first 80MHz subchannel and the 484 / 242+242-tone RU in the second 80MHz subchannel are not considered.

[0315] 4.2. Combinations

[0316] We propose various RU combinations for PPDU transmission at the following bandwidths.

[0317] 4.2.1.80MHz

[0318] To consider OFDMA transmission, at least two STAs are assigned to PPDU transmission, and since large RU combinations are considered, a maximum bandwidth of 60MHz can be assigned to one STA. In this case, a 242+484-tone RU combination can be considered. Alternatively, a 40MHz bandwidth can be assigned, in which case a 242+242-tone RU combination can be considered, but it is preferable to assign it to a 484-tone RU rather than transmitting via a 242+242-tone RU combination. The reason for this is that in OFDMA transmission where a 40MHz bandwidth is assigned to one STA, at least 20MHz can be assigned to another STA. In this case, a minimum bandwidth of 60MHz is available (with only 20MHz preamble puncturing), which is either a continuous 60MHz or a discontinuous 40+20MHz, and in both cases, a 484-tone RU is always available, so it is preferable to utilize the existing 484-tone RU rather than deliberately considering a 242+242-tone RU combination.

[0319] 4.2.2.160 / 80+80MHz

[0320] The 160 / 80+80MHz tone plan consists of two repetitions of the 80MHz tone plan.

[0321] The RU combinations in 4.2.1 can be considered, and further combinations of two 80MHz subchannels can be considered as follows. Since OFDMA transmission is considered, at least two or more STAs are assigned to PPDU transmission, and large RU combinations are considered, so a maximum bandwidth of 140MHz can be assigned to one STA. The following bandwidth combinations can be considered for each 80MHz subchannel.

[0322] 140MHz: 80+60

[0323] The meaning of 80+60 is that 80MHz is allocated to one 80MHz subchannel and 60MHz to the other 80MHz subchannel, so that these two combine to form 140MHz. The RU for 80 is 996-tone RU and the RU for 60 is 484+242-tone RU. This will also be used in the following proposal.

[0324] A 120MHz bandwidth can also be allocated, and the following combinations are possible.

[0325] 120MHz: 80+40

[0326] The RU for 40 is a 484-tone RU, and a combination of 242+242-tone RUs can also be considered, but since it is OFDMA transmission, there is at least a 20MHz channel for another STA, and therefore a 484-tone RU will always exist within the 80MHz subchannel to which 40 is allocated. Therefore, it is preferable to assign and transmit to the existing 484-tone RU rather than transmitting via the 242+242-tone RU combination. Unless otherwise specified for 40, the same applies to the following proposals. The 60+60 combination at 120MHz is not considered because it violates the principle of 4.1. The reason is that since it is OFDMA transmission, there is a 20MHz for another STA, and in this case, one 80MHz subchannel is fully utilized. That is, when allocating 120MHz in accordance with the principle, it is necessary to allocate the entire fully utilized 80MHz subchannel.

[0327] A 100MHz bandwidth can also be allocated, and the following combinations are possible.

[0328] 100MHz: 80+20, 60+40

[0329] The RU for 20 is a 242-tone RU, which is also used in the following proposal. The RU for 40 is a 484-tone RU, and a combination of 242 + 242-tone RUs can also be considered but is avoided. The reason 60 can be allocated is when 20MHz preamble puncturing occurs within an 80MHz subchannel, and only a maximum bandwidth of 60MHz is used. In this case, the 80MHz subchannel to which 40 is allocated also cannot use a bandwidth exceeding 60MHz due to preamble puncturing. In the following proposal as well, except for the 80MHz subchannel to which the minimum bandwidth is allocated, the 80MHz subchannels to which 60 or 40 is allocated will similarly be subject to preamble puncturing, meaning that the maximum allocatable bandwidth will be 60MHz or 40MHz. In this case, the 80MHz subchannel to which the minimum bandwidth is allocated will also be subject to preamble puncturing, and the maximum allocatable bandwidth will not exceed 60MHz or 40MHz.

[0330] An 80MHz bandwidth can also be allocated, and the following combinations are possible.

[0331] 80MHz: 60+20

[0332] In this case, 40 + 40 is not considered according to principle 4.1.

[0333] A 60MHz bandwidth can also be allocated, and the following combinations are possible.

[0334] 60MHz: 40+20

[0335] The reason why 40 can be assigned is that, as explained in the 100MHz combination above, if 40MHz preamble puncturing occurs within the 80MHz subchannel, only a maximum bandwidth of 40MHz is used. In this case, the 80MHz subchannel to which 20 is assigned also cannot use a bandwidth exceeding 40MHz due to preamble puncturing. The RU for 40 is a 484 / 242+242-tone RU. The reason why a 242+242-tone RU is possible is that, due to preamble puncturing, the 80MHz subchannel to which 40 is assigned can only use 40MHz, and in this case, the puncturing pattern only allows the use of a 484-tone RU or a 242+242-tone RU.

[0336] The 20+20 combination for 40MHz is not considered as it violates the principle. Additional combinations below 40MHz are not considered.

[0337] 4.2.3.240 / 160+80MHz

[0338] The 240 / 160+80MHz tone plan consists of three repetitions of the 80MHz tone plan.

[0339] The RU combinations in 4.2.1 and 4.2.2 can be considered, and further combinations of three 80MHz subchannels can be considered as follows. To consider OFDMA transmission, at least two or more STAs are assigned to PPDU transmission, and since large RU combinations are considered, a maximum bandwidth of 220MHz can be assigned to one STA. The following bandwidth combinations can be considered for each 80MHz subchannel.

[0340] 220MHz: 80+80+60

[0341] 80 + 80 is 2 x 996-tone RU, which is simply 996-tone RU each, and this also applies to the following proposal.

[0342] A 200MHz bandwidth can also be allocated, and the following combinations are possible.

[0343] 200MHz: 80+80+40

[0344] 80+60+60 is not considered because it violates the principle.

[0345] A 180MHz bandwidth can also be allocated, and the following combinations are possible.

[0346] 180MHz: 80+80+20, 80+60+40

[0347] 60+60+60 is not considered because it violates the principle.

[0348] A 160MHz bandwidth can also be allocated, and the following combinations are possible.

[0349] 160MHz: 80+60+20, 60+60+40

[0350] 80+40+40 is not considered because it violates the principle.

[0351] A 140MHz bandwidth can also be allocated, and the following combinations are possible.

[0352] 140MHz: 80+40+20, 60+60+20

[0353] The RU for the aforementioned 40 is a 484 / 242+242-tone RU. The reason a 242+242-tone RU is possible is that the 80MHz subchannel to which 40 is assigned by preamble puncturing is only usable at 40MHz, and in this case, the puncturing pattern only allows the use of a 484-tone RU or a 242+242-tone RU. 60+40+40 is not considered because it goes against the principle.

[0354] A 120MHz bandwidth can also be allocated, and the following combinations are possible.

[0355] 120MHz: 60+40+20

[0356] The RU for the aforementioned 40 is 484 / 242+242-tone RU. 80+20+20 / 40+40+40 is not considered as it contradicts the principle.

[0357] A 100MHz bandwidth can also be allocated, and the following combinations are possible.

[0358] 100MHz: 40+40+20

[0359] The RU for the aforementioned 40 is 484 / 242+242-tone RU. 60+20+20 is not considered as it contradicts the principle.

[0360] The 40+20+20 combination for 80MHz is not considered as it violates the principle. Additional combinations below 80MHz are not considered.

[0361] 4.2.4.320 / 160+160MHz

[0362] The 320 / 160+160MHz tone plan consists of four repetitions of the 80MHz tone plan.

[0363] The RU combinations in 4.2.1, 4.2.2, and 4.2.3 can be considered, and further combinations of four 80MHz subchannels can be considered as follows. To consider OFDMA transmission, at least two or more STAs are assigned to PPDU transmission, and since large RU combinations are considered, a maximum bandwidth of 300MHz can be assigned to one STA. The following bandwidth combinations can be considered for each 80MHz subchannel.

[0364] 300MHz: 80+80+80+60

[0365] 80+80+80 is 3 x 996-tone RU, which can simply be 996-tone RU each, or a combination of 2 x 996-tone RU and 996-tone RU. This also applies to the following proposal.

[0366] A 280MHz bandwidth can also be allocated, and the following combinations are possible.

[0367] 280MHz: 80+80+80+40

[0368] 80+80+60+60 is not considered because it violates the principle.

[0369] A 260MHz bandwidth can also be allocated, and the following combinations are possible.

[0370] 260MHz: 80+80+80+2, 80+80+60+40

[0371] 80+60+60+60 is not considered because it violates the principle.

[0372] A 240MHz bandwidth can also be allocated, and the following combinations are possible.

[0373] 240MHz:80+80+60+20,80+60+60+40

[0374] 80+80+40+40 / 60+60+60+60 is not considered because it violates the principle.

[0375] A 220MHz bandwidth can also be allocated, and the following combinations are possible.

[0376] 220MHz:80+80+40+20,80+60+60+20,60+60+60+40

[0377] The RU for 40 in the first combination mentioned above is 484 / 242+242-tone RU. 80+60+40+40 is not considered as it contradicts the principle.

[0378] A 200MHz bandwidth can also be allocated, and the following combinations are possible.

[0379] 200MHz:80+60+40+20,60+60+60+20

[0380] The RU for 40 in the first combination mentioned above is 484 / 242+242-tone RU. 80+80+20+20 / 80+40+40+40 / 60+60+40+40 are not considered as they contradict the principle.

[0381] A 180MHz bandwidth can also be allocated, and the following combinations are possible.

[0382] 180MHz:80+40+40+20,60+60+40+20

[0383] The RU for 40 in the two combinations mentioned above is 484 / 242+242-tone RU. 80+60+20+20 / 60+40+40+40 is not considered as it contradicts the principle.

[0384] A 160MHz bandwidth can also be allocated, and the following combinations are possible.

[0385] 160MHz: 60+40+40+20

[0386] The RU for the aforementioned 40 is 484 / 242+242-tone RU. 80+40+20+20 / 60+60+20+20 / 40+40+40+40 are not considered as they contradict the principle.

[0387] A 140MHz bandwidth can also be allocated, and the following combinations are possible.

[0388] 140MHz: 40+40+40+20

[0389] The RU for the aforementioned 40 is 484 / 242+242-tone RU. 60+40+20+20 is not considered as it contradicts the principle.

[0390] The 60+20+20+20 / 40+40+20+20 combination for 120MHz is not considered as it violates the principle. Additional combinations below 120MHz are not considered.

[0391] 4.3. Restriction

[0392] For bandwidths exceeding 80MHz, the RU combination can be restricted as follows. The reason for this restriction is to reduce scheduling complexity and signaling overhead.

[0393] In the 160 / 80+80MHz bandwidth, when considering non-contiguous structures, the combination of multiple RU aggregations can be limited in 80MHz units. That is, STAs can be divided into those allocated by RU combinations within the Primary 80MHz and those allocated by RU combinations within the Secondary 80MHz. The RU combinations within each 80MHz can be those described in 4.2.1, and the allocation of 996-tone RUs is also possible. In addition, 242-tone RUs are also considered, and the combination of 242+242-tone RUs is also used. In summary, they are used as follows within each 80MHz.

[0394] 242-tone RU for 20MHz

[0395] 484 / 242+242-tone RU for 40MHz

[0396] 484+242-toenRU for 60MHz

[0397] 996-tone RU for 80MHz

[0398] In a 240 / 160+80MHz bandwidth, when considering a non-contiguous structure, the combination of multiple RU aggregations can be limited to 160MHz and 80MHz units, where 160MHz and 80MHz are the contiguous 160MHz and contiguous 80MHz portions in a non-contiguous situation. In a contiguous 240MHz, a primary 160MHz and the remaining 80MHz can be considered, or it can be divided into a primary 80MHz and the remaining 160MHz, but the former form is preferable because there are cases where the 160MHz portion is not continuous. Alternatively, in a contiguous 240MHz, it is possible to divide it into a 160MHz portion formed by combining the primary 80MHz with a specific adjacent 80MHz, and the remaining 80MHz portion. This is advantageous in situations where there is no secondary 80MHz. That is, it can be divided into STAs assigned by RU combinations within 160MHz and STAs assigned by RU combinations within the remaining 80MHz. Alternatively, in a contiguous 240MHz, two adjacent 80MHz channels can always be designed to be able to combine by 160MHz, in which case the central 80MHz is always combined with the 80MHz segments on either side. The RU combinations within 80MHz are the same as those proposed when limiting multiple RU aggregation combinations in 80MHz units above. The RU combinations within 160MHz include the following combinations, which are created by combining these again, along with the combinations proposed when limiting multiple RU aggregation combinations in 80MHz units in the 160 / 80+80MHz bandwidth above. In the notation, -tone RU is omitted and the meaning of () is that it is the RU within each 80MHz segment within 160MHz.

[0399] (242)+(242), (242)+(484), (242)+(242+242), (242)+(484+242), (242)+(996), (484)+(484), (484)+(242+242), (484)+(484+242), (484)+(996), (242+242)+(242+242), (242+242)+(484+242), (242+242)+(996), (484+242)+(484+242), (484+242)+(996), (996)+(996) or 2x996

[0400] The above combinations are not always possible, and if there are no additional RUs available on each 80MHz channel due to preamble puncturing or other STA allocation, we suggest combining with the RUs of adjacent 80MHz channels. For example, the fact that (242)+(242) is possible with two 80MHz channels means that only 242-tone RUs are available on both channels due to preamble puncturing. If a 484-tone RU is available on one channel, then you can simply use a 242 / 484-tone RU or (484)+(242). However, of the two 80MHz channels, the 80MHz channel using the smaller RU may have remaining RUs (allocated to another STA), and the available bandwidth including these may be larger or smaller than the available bandwidth of the channel using the larger RU. For example, if both channels are preamble puncturing and 60MHz is available, the combination (484+242)+(484) is possible, and one 242 RU is allocated to the other STA.

[0401] In the 320 / 160+160MHz bandwidth, when considering non-contiguous structures, the multiple RU aggregation combinations can be limited in 160MHz units. That is, they can be divided into STAs allocated by RU combinations within the Primary 160MHz and STAs allocated by RU combinations within the Secondary 160MHz, and the RU combinations within each 160MHz are the same as those proposed when limiting the multiple RU aggregation combinations in 160MHz units in the 240 / 160+80MHz bandwidth mentioned above.

[0402] Furthermore, we propose limiting the multiple RU aggregation combinations in 80MHz units for the 240 / 160+80MHz bandwidth and the 320 / 160+160MHz bandwidth, as shown in Figure 1. Each 80MHz corresponds to a lower / higher 80MHz or primary / secondary 80MHz within the primary 80MHz, secondary 80MHz, and secondary 160MHz.

[0403] 4.4. Signaling Methods

[0404] Figure 22 shows an example of the EHT PPDU format.

[0405] Figure 23 shows an example of the U-SIG format.

[0406] The indicators related to the RU aggregation described above are transmitted within the EHT-SIG of the EHT PPDU in Figure 22 or the U-SIG in Figure 23.

[0407] The Version-independent field in Figure 23 contains a 3-bit version identifier indicating the 802.11be and later Wi-Fi versions, a 1-bit DL / UL field, BSS color, TXOP duration, etc., while the Version-dependent field in Figure 23 contains information such as PPDU type and Bandwidth.

[0408] U-SIG is a jointly encoded signal consisting of two symbols, each with 52 data tones and 4 pilot tones at 20MHz intervals. Furthermore, U-SIG is modulated in the same way as HE-SIG-A; that is, U-SIG is modulated at the BPSK1 / 2 code rate.

[0409] The EHT-SIG is divided into a Common field and a user-specific field, which are encoded into a variable MCS. The Common field can specify the exact puncturing pattern and RU aggregation information used for transmission. Additionally, when applying preamble puncturing, one bit of information can be transmitted in the U-SIG's version-dependent field or the EHT-SIG's common field to indicate whether to apply a shifted tone plan in an adjacent 20MHz channel, change to a 20MHz tone plan, use the tone plan as is but puncture some tones, or transmit some tones at a lower power.

[0410] Figure 24 is a procedure flowchart showing the operation of the transmitting device according to this embodiment.

[0411] An example in Figure 24 is performed by a transmitting device (AP and / or non-AP STA). For example, an example in Figure 24 is performed by an AP that transmits EHT SU PPDU, EHT ER SU PPDU, and EHT MU PPDU. An example in Figure 24 is performed by a non-AP that transmits EHT SU PPDU, EHT ER SU PPDU, and EHT MU PPDU.

[0412] Some of the steps (or detailed sub-steps described later) in the example in Figure 24 may be omitted or modified.

[0413] In step S2410, the transmitting device (i.e., the transmitting STA) configures the Bandwidth (BW) and RU allocation, and can assign multiple RUs to a specific user or STA by the Multiple RU aggregation combination described in paragraph 4.2 of the specification above. The transmitting device can also perform Channel Access operations.

[0414] In step S2420, the transmitting STA can constitute a PPDU. For example, the PPDUs are EHT SU PPDU, EHT ER SU PPDU, and EHT MU PPDU. As shown in Figure 18, the PPDU can include EHT-SIG.

[0415] The transmitting STA can execute step S2420 based on the BW, RU allocation, and Multiple RU aggregation determined via step S2410.

[0416] In other words, as described above, the common field of the EHT-SIG contains specific (RU allocation) n-bit (e.g., 8-bit) information, and the user-specific field can contain information for multiple RU aggregation.

[0417] In step S2430, the transmitting device can transmit the PPDU configured via step S2420 to the receiving device based on step S2430.

[0418] While step S2430 is being executed, the transmitter performs at least one of the following operations: CSD, Spatial Mapping, IDFT / IFFT operation, or GI insertion (insert).

[0419] The signals / fields / sequences configured herein are transmitted in the form shown in Figure 18.

[0420] For example, the EHT-SIG mentioned above is transmitted based on multiple OFDM symbols. For example, one OFDM symbol can contain 26 bits of information. This 26-bit information can contain the 4 bits of BW information mentioned above. In some cases, arbitrary m-bit information may be used instead of 26 bits of information.

[0421] For 26 bits of information, BCC encoding with a 1 / 2 code rate is applied. Interbilling by an interleaver is applied to the BCC encoded bits (i.e., 52 bits). Constellation mapping is performed by a Constellation mapper on the interleaved 52 bits. Specifically, the BPSK module is applied, and 52 BPSK symbols are generated. The 52 BPSK symbols are matched to the remaining frequency range (-28 to +28) excluding the DC tone and pilot tone (-21, -7, +7, +21). Subsequently, it is transmitted to the receiving STA via Phase rotation, CSD, Spatial Mapping, IDFT / IFFT operation, etc.

[0422] The PPDU described above is transmitted based on the device shown in Figure 1.

[0423] An example in Figure 1 relates to an example of a transmitting device (AP and / or non-AP STA).

[0424] As shown in Figure 1, the transmitting device may include a memory (112), a processor (111), and a transceiver (113).

[0425] The memory (112) can store information relating to a number of BW / Tone-Plan / RUs as described herein.

[0426] The processor (111) can generate various RUs based on the information stored in the memory (112) and configure a PPDU. An example of a PPDU generated by the processor (111) is the same as in Figure 1.

[0427] The aforementioned processor (111) can perform all or part of the operations shown in Figure 24.

[0428] The transceiver (113) shown includes an antenna and is capable of performing analog signal processing. Specifically, the processor (111) controls the transceiver (113) and can transmit the PPDU generated by the processor (111).

[0429] Alternatively, the processor (111) generates a transmit PPDU and causes the memory (112) to store information regarding the transmit PPDU.

[0430] Figure 25 is a procedure flowchart showing the operation of the receiving device according to this embodiment.

[0431] The example shown in Figure 25 is performed in a receiving device (AP and / or non-AP STA).

[0432] An example in Figure 25 is performed at a receiving STA or receiving device (AP and / or non-AP STA). For example, an example in Figure 3 is performed by a non-AP that receives EHT SU PPDU, EHT ER SU PPDU, and EHT MU PPDU. An example in Figure 25 is performed by an AP that transmits EHT SU PPDU and EHT ER SU PPDU.

[0433] Some of the steps (or detailed sub-steps described later) in the example shown in Figure 25 are omitted.

[0434] In step S2510, the receiving device (receiving STA) can receive all or part of the PPDU via step S2510. The received signal is in the form shown in Figure 18.

[0435] The sub-step of step S2510 is determined based on step S2430 in Figure 24. That is, step S2510 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion (insert) operation applied in step S2430.

[0436] In step S2520, the receiving STA can decode the information contained in the U-SIG or EHT-SIG to obtain information regarding the BW, RU allocation, and Multiple RU aggregation of the EHT PPDU.

[0437] Through this, the receiving STA can complete decoding of other fields / symbols of the received PPDU.

[0438] As a result, the receiving STA can decode the data field contained within the PPDU via the S2520 step. Subsequently, the receiving STA can perform processing operations to transmit the decoded data from the data field to a higher layer (e.g., the MAC layer). Furthermore, if the higher layer instructs the PHY layer to generate a signal in response to the data transmitted to the higher layer, it can perform subsequent operations.

[0439] The PPDU mentioned above is received based on the device shown in Figure 1.

[0440] As shown in Figure 1, the receiving device may include a memory (1220), a processor (121), and a transceiver (123).

[0441] The transceiver (123) can receive PPDUs based on the control of the processor (121). For example, the transceiver (123) may include a number of detailed units (not shown). For example, the transceiver (123) may include at least one receiving antenna and a filter for that receiving antenna.

[0442] The PPDU received via the transceiver (123) is stored in memory (122). The processor (121) can process the decoding of the received PPDU via memory (122). The processor (121) can acquire control information (e.g., EHT-SIG) related to BW / Tone-Plan / RU contained in the PPDU and store the acquired control information in memory (122).

[0443] The processor (121) can decode the received PPDU. Specifically, it can perform operations to restore the results of CSD, Spatial Mapping, IDFT / IFFT operations, and GI insertions applied to the PPDU. These operations are performed via numerous processing units (not shown) individually implemented within the processor (121).

[0444] Furthermore, the processor (121) can decode the data fields of the PPDU received via the transceiver (123).

[0445] Furthermore, the processor (121) can process the decoded data. For example, the processor (121) can perform processing operations to transmit information about the decoded data field to a higher layer (e.g., the MAC layer). Also, if the higher layer instructs the PHY layer to generate a signal in response to the data transmitted to the higher layer, the processor (121) can perform subsequent operations.

[0446] The above-described embodiment will be explained below with reference to Figures 1 to 25.

[0447] Figure 26 is a flowchart showing the procedure for transmitting a PPDU using the transmitting STA in this embodiment.

[0448] An example shown in Figure 26 is executed in a network environment that supports a next-generation wireless LAN system (IEEE 802.11be or EHT wireless LAN system). This next-generation wireless LAN system is an improved version of the 802.11ax system and can satisfy backward compatibility with the 802.11ax system.

[0449] An example shown in Figure 26 is performed in a transmitting STA, which can be an AP (Access Point). The receiving STA in Figure 26 can be an STA that supports an EHT (Extremely High Throughput) wireless LAN system.

[0450] This embodiment proposes a method and apparatus for transmitting and receiving PPDUs based on multiple RUs configured in combinations of large-RUs. In this case, a large-RU refers to a resource unit with 242 or more tones. In particular, this embodiment proposes a method for configuring multiple RUs used to transmit PPDUs using the OFDMA scheme.

[0451] In step S2610, the transmitting STA (station) generates a PPDU (Physical Protocol Data Unit).

[0452] In step S2620, the transmitting STA transmits the PPDU to the receiving STA via broadband.

[0453] The PPDU includes a control field and a data field.

[0454] If the broadband is a 320 / 160+160MHz band including a primary 160MHz channel and a secondary 160MHz channel, the data field is received via a first multiple RU aggregated from 996 RUs and 484 RUs. In this case, the first multiple RU is allocated within the primary 160MHz channel or the secondary 160MHz channel. The 996 RU is an RU composed of 996 tones, and the 484 RU is an RU composed of 484 tones.

[0455] The PPDU is transmitted using the OFDMA (orthogonal frequency division multiple access) method. Therefore, the first multiplexed RU is assigned to a specific receiving STA among a plurality of receiving STAs. This embodiment proposes that when OFDMA PPDU transmission occurs, the first multiplexed RU is assigned to either the primary 160MHz channel or the secondary 160MHz channel. That is, the combination of the 996RU and the 484RU is assigned to either the primary 160MHz channel or the secondary 160MHz channel (both the primary and secondary 160MHz channels are also possible).

[0456] In the 320 / 160+160MHz band, other RUs or other multiplexed RUs, excluding the first multiplexed RU, are either punctured or allocated to other receiving STAs that are not the aforementioned receiving STA. Since the PPDU is transmitted based on the OFDMA scheme, puncturing does not always need to be considered, and the first multiplexed RU is scheduled or allocated via allocation information (RU allocation information) relating to the first multiplexed RU, which will be described later.

[0457] The control field may include assignment information relating to the first multiplexed RU. The receiving STA can decode the assignment information relating to the first multiplexed RU and confirm that the first multiplexed RU is the RU assigned to it.

[0458] Furthermore, when considering puncture in the OFDMA PPDU transmission method for the 320 / 160+160MHz band, the primary 20MHz channel must always transmit (it must not be punctured), and at least one 20MHz channel among the secondary 160MHz channels must always transmit (it must not be punctured). For example, if the first channel is punctured in the 320 / 160+160MHz band, the second channel, excluding the first channel, is at least one 20MHz channel among the primary 20MHz and the secondary 160MHz channels.

[0459] As another example, if the broadband is a 320 / 160+160MHz band including first to fourth 80MHz subchannels, the data field is received via a second multiplexed RU, which is an aggregate of 484RUs and 242RUs. In this case, the second multiplexed RU is allocated within the first, second, third, or fourth 80MHz channel. The 484RU is a RU composed of 484 tones, and the 242RU is a RU composed of 242 tones.

[0460] Similarly, the PPDU is transmitted based on the OFDMA scheme. Therefore, the second multiplexed RU is assigned to a specific receiving STA among a plurality of receiving STAs. This embodiment proposes that when OFDMA PPDU transmission occurs, the second multiplexed RU may be assigned to the first 80MHz channel, the second 80MHz channel, the 380MHz channel, or the fourth 80MHz channel. That is, the combination of the 484RU and the 242RU may be assigned to the first 80MHz channel, the second 80MHz channel, the third 80MHz channel, or the fourth 80MHz channel (it may also be assigned to all of the first to fourth 80MHz channels).

[0461] The control field may include assignment information relating to the second multiplexed RU. The receiving STA can decode the assignment information relating to the second multiplexed RU and confirm that the second multiplexed RU is the RU assigned to it.

[0462] Of the first to fourth 80MHz subchannels, one is the primary 80MHz channel, and the remaining three subchannels are secondary 80MHz channels (specifically, the secondary 80MHz channel, the secondary 160MHz lower 80MHz channel, and the secondary 160MHz higher 80MHz channel). The primary 80MHz channel and the secondary 80MHz channels are set regardless of their frequency size.

[0463] In this embodiment, the transmitting STA transmits the PPDU using the OFDMA method, so it can transmit the PPDU to multiple receiving STAs, and as a result the multiplexed RUs described above are assigned to each of the multiple receiving STAs.

[0464] For example, if the receiving STA includes a first and a second STA, and the second multiplexed RU is allocated only within the first and third 80MHz channels (i.e., if the multiplexed RU is allocated in units of 80MHz subchannels in the 320 / 160+160MHz band), the first STA can receive the data field via the second multiplexed RU allocated within the first 80MHz channel, and the second STA can receive the data field via the second multiplexed RU allocated within the third 80MHz channel.

[0465] As another example, if the receiving STA includes a first and a second STA, and the first multiplexed RU is allocated within the primary 160MHz channel and the secondary 160MHz channel (where the multiplexed RU is allocated in units of 160MHz subchannels in the 320 / 160+160MHz band), then the first STA can receive the data field via the first multiplexed RU allocated within the primary 160MHz channel, and the second STA can receive the data field via the first multiplexed RU allocated within the secondary 160MHz channel.

[0466] This embodiment proposes a method for configuring multiple RUs (combinations between large and RUs) used to transmit PPDUs using the OFDMA method in the 320 / 160+160MHz band. Furthermore, this embodiment can propose a method for configuring multiple RUs (combinations between large and RUs) used to transmit PPDUs using the OFDMA method in the 160 / 80+80MHz band.

[0467] Similarly, the 160 / 80+80MHz bandwidth is allocated multiplexed RUs on a 160MHz subchannel basis or on an 80MHz subchannel basis. As a result, the data field is received via 996+484 RUs allocated per 160MHz subchannel or via 484+242 RUs allocated per 80MHz subchannel.

[0468] The control field includes a first control field that supports legacy wireless LAN systems and a second control field that supports 802.11be wireless LAN systems. The second control field may include a U-SIG (Universal-Signal) or an EHT-SIG (Extremely High Throughput-Signal). The second control field may include allocation information relating to the RU to which the data field is transmitted. This embodiment describes the case where the RU to which the data field is transmitted is a multiple RU, where multiple RUs are aggregated together. The RU means the resource unit to which the data field is transmitted.

[0469] The EHT-SIG may include EHT-SIG-A and EHT-SIG-B (or EHT-SIG-C fields). The EHT-SIG-B may include Resource Unit (RU) information. The transmitting STA can provide information for the broadband tone plan via the EHT-SIG-B. In addition, the EHT-STF, EHT-LTF included in the second control field and the data field are transmitted and received in the multiplexed RU included in the broadband tone plan.

[0470] Figure 27 is a flowchart illustrating the procedure for receiving a PPDU in this embodiment.

[0471] An example shown in Figure 27 is executed in a network environment that supports a next-generation wireless LAN system (IEEE 802.11be or EHT wireless LAN system). This next-generation wireless LAN system is an improved version of the 802.11ax system and can satisfy backward compatibility with the 802.11ax system.

[0472] The example in Figure 27 is performed in a receiving STA and can be used with STAs that support EHT (Extremely High Throughput) wireless LAN systems. The transmitting STA in Figure 27 can be used with APs (Access Points).

[0473] This embodiment proposes a method and apparatus for transmitting and receiving PPDUs based on multiple RUs configured in combinations of large-RUs. In this case, a large-RU refers to a resource unit with 242 or more tones. In particular, this embodiment proposes a method for configuring multiple RUs used to transmit PPDUs using the OFDMA scheme.

[0474] In step S2710, the receiving STA (station) receives a PPDU (Physical Protocol Data Unit) from the transmitting STA via broadband.

[0475] In step S2720, the receiving STA decodes the PPDU.

[0476] The PPDU includes a control field and a data field.

[0477] If the broadband is a 320 / 160+160MHz band including a primary 160MHz channel and a secondary 160MHz channel, the data field is received via a first multiple RU aggregated from 996 RUs and 484 RUs. In this case, the first multiple RU is allocated within the primary 160MHz channel or the secondary 160MHz channel. The 996 RU is an RU composed of 996 tones, and the 484 RU is an RU composed of 484 tones.

[0478] The PPDU is transmitted using the OFDMA (orthogonal frequency division multiple access) method. Therefore, the first multiplexed RU is assigned to a specific receiving STA among a plurality of receiving STAs. This embodiment proposes that when OFDMA PPDU transmission occurs, the first multiplexed RU is assigned to either the primary 160MHz channel or the secondary 160MHz channel. That is, the combination of the 996RU and the 484RU is assigned to either the primary 160MHz channel or the secondary 160MHz channel (both the primary and secondary 160MHz channels are also possible).

[0479] In the 320 / 160+160MHz band, other RUs or other multiplexed RUs, excluding the first multiplexed RU, are either punctured or allocated to other receiving STAs that are not the receiving STA. Since the PPDU is transmitted based on OFDMA, puncturing does not always need to be considered, and the first multiplexed RU is scheduled or allocated via allocation information (RU allocation information) for the first multiplexed RU, which will be described later.

[0480] The control field may include assignment information relating to the first multiplexed RU. The receiving STA can decode the assignment information relating to the first multiplexed RU and confirm that the first multiplexed RU is the RU assigned to it.

[0481] Furthermore, when considering puncture in the OFDMA PPDU transmission method for the 320 / 160+160MHz band, the primary 20MHz channel must always transmit (it must not be punctured), and at least one 20MHz channel among the secondary 160MHz channels must always transmit (it must not be punctured). For example, if the first channel is punctured in the 320 / 160+160MHz band, the second channel, excluding the first channel, is at least one 20MHz channel among the primary 20MHz and the secondary 160MHz channels.

[0482] As another example, if the broadband is a 320 / 160+160MHz band including first to fourth 80MHz subchannels, the data field is received via a second multiplexed RU, which is an aggregate of 484RUs and 242RUs. In this case, the second multiplexed RU is allocated within the first, second, third, or fourth 80MHz channel. The 484RU is a RU composed of 484 tones, and the 242RU is a RU composed of 242 tones.

[0483] Similarly, the PPDU is transmitted based on the OFDMA scheme. Therefore, the second multiplexed RU is assigned to a specific receiving STA among a plurality of receiving STAs. This embodiment proposes that when OFDMA PPDU transmission occurs, the second multiplexed RU may be assigned to the first 80MHz channel, the second 80MHz channel, the third 80MHz channel, or the fourth 80MHz channel. That is, the combination of the 484RU and the 242RU may be assigned to the first 80MHz channel, the second 80MHz channel, the third 80MHz channel, or the fourth 80MHz channel (it may also be assigned to all of the first to fourth 80MHz channels).

[0484] The control field may include assignment information relating to the second multiplexed RU. The receiving STA can decode the assignment information relating to the second multiplexed RU and confirm that the second multiplexed RU is the RU assigned to it.

[0485] Of the first to fourth 80MHz subchannels, one is the primary 80MHz channel, and the remaining three subchannels are secondary 80MHz channels (specifically, the secondary 80MHz channel, the secondary 160MHz lower 80MHz channel, and the secondary 160MHz higher 80MHz channel). The primary 80MHz channel and the secondary 80MHz channels are set regardless of their frequency size.

[0486] In this embodiment, the transmitting STA transmits the PPDU using the OFDMA method, so it can transmit the PPDU to multiple receiving STAs, and as a result the multiplexed RUs described above are assigned to each of the multiple receiving STAs.

[0487] For example, if the receiving STA includes a first and a second STA, and the second multiplexed RU is allocated only within the first and third 80MHz channels (i.e., if the multiplexed RU is allocated in units of 80MHz subchannels in the 320 / 160+160MHz band), the first STA can receive the data field via the second multiplexed RU allocated within the first 80MHz channel, and the second STA can receive the data field via the second multiplexed RU allocated within the third 80MHz channel.

[0488] As another example, if the receiving STA includes a first and a second STA, and the first multiplexed RU is allocated within the primary 160MHz channel and the secondary 160MHz channel (where the multiplexed RU is allocated in units of 160MHz subchannels in the 320 / 160+160MHz band), then the first STA can receive the data field via the first multiplexed RU allocated within the primary 160MHz channel, and the second STA can receive the data field via the first multiplexed RU allocated within the secondary 160MHz channel.

[0489] This embodiment proposes a method for configuring multiple RUs (combinations between large and RUs) used to transmit PPDUs using the OFDMA method in the 320 / 160+160MHz band. Furthermore, this embodiment can propose a method for configuring multiple RUs (combinations between large and RUs) used to transmit PPDUs using the OFDMA method in the 160 / 80+80MHz band.

[0490] Similarly, the 160 / 80+80MHz bandwidth is allocated multiplexed RUs on a 160MHz subchannel basis or on an 80MHz subchannel basis. As a result, the data field is received via 996+484 RUs allocated per 160MHz subchannel or via 484+242 RUs allocated per 80MHz subchannel.

[0491] The control field includes a first control field that supports legacy wireless LAN systems and a second control field that supports 802.11be wireless LAN systems. The second control field may include a U-SIG (Universal-Signal) or an EHT-SIG (Extremely High Throughput-Signal). The second control field may include allocation information relating to the RU to which the data field is transmitted. This embodiment describes the case where the RU to which the data field is transmitted is a multiple RU, where multiple RUs are aggregated together. The RU means the resource unit to which the data field is transmitted.

[0492] The EHT-SIG may include EHT-SIG-A and EHT-SIG-B (or EHT-SIG-C fields). The EHT-SIG-B may include Resource Unit (RU) information. The transmitting STA can provide information for the broadband tone plan via the EHT-SIG-B. In addition, the EHT-STF, EHT-LTF included in the second control field and the data field are transmitted and received in the multiplexed RU included in the broadband tone plan.

[0493] 5.Device configuration

[0494] The technical features of this specification described above are applicable to various devices and methods. For example, the technical features of this specification described above are implemented / supported through the device in Figure 1 and / or Figure 19. For example, the technical features of this specification described above are applicable to only a portion of Figure 1 and / or Figure 19. For example, the technical features of this specification described above are implemented based on the processing chip (114, 124) in Figure 1, or based on the processor (111, 121) and memory (112, 122) in Figure 1, or based on the processor (610) and memory (620) in Figure 19. For example, the device of this specification receives a PPDU (Physical Protocol Data Unit) from a transmitting STA via broadband and decodes the PPDU.

[0495] The technical features of this specification are implemented based on a CRM (computer-readable medium). For example, the CRM proposed herein is at least one computer-readable medium containing instructions that are executed by at least one processor.

[0496] The CRM can store instructions for performing operations that include receiving a Physical Protocol Data Unit (PPDU) from a transmitting STA over broadband, and decoding the PPDU. Instructions stored in the CRM according to this specification are executed by at least one processor. The at least one processor associated with the CRM according to this specification is the processor (111, 121) or processing chip (114, 124) in Figure 1, or the processor (610) in Figure 19. On the other hand, the CRM according to this specification is the memory (112, 122) in Figure 1, the memory (620) in Figure 19, or another external memory / storage medium / disk, etc.

[0497] The technical features described herein are applicable to a variety of applications and business models. For example, these technical features are applicable to wireless communication in devices that support artificial intelligence (AI).

[0498] Artificial intelligence refers to the field of studying artificial intelligence or methodologies for creating it, while machine learning refers to the field of defining various problems dealt with in the field of artificial intelligence and studying methodologies for solving them. Machine learning can also be defined as an algorithm that improves its performance for a particular task through continuous experience.

[0499] An artificial neural network (ANN) is a model used in machine learning that consists of artificial neurons (nodes) that form a network of synaptic connections, and is generally considered to have problem-solving capabilities. An artificial neural network is defined by the connection patterns between neurons in other layers, the learning process that updates the model parameters, and the activation function that generates the output values.

[0500] An artificial neural network can include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network can include synapses connecting neurons. In an artificial neural network, each neuron can output an input signal, a weighted value, and a function value of the activation function for the bias received via the synapse.

[0501] Model parameters refer to parameters determined through learning, including synaptic connection weights and neuron bias. Hyperparameters, on the other hand, refer to parameters that need to be set before learning in a machine learning algorithm, including the learning rate, iteration count, mini-batch size, and initialization function.

[0502] The goal of training an artificial neural network is to determine the model parameters that minimize the loss function. The loss function is used as an indicator to determine the optimal model parameters during the training process of the artificial neural network.

[0503] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning based on the learning method.

[0504] Supervised learning refers to a method of training an artificial neural network when labels are provided for the training data. When labels are input to the artificial neural network, they represent the correct answer (or result value) that the artificial neural network needs to infer. Unsupervised learning refers to a method of training an artificial neural network when labels are not provided for the training data. Reinforcement learning refers to a learning method in which a defined agent is trained to select the action or sequence of actions that maximizes the cumulative reward in each state within a given environment.

[0505] Machine learning implemented as a deep neural network (DNN), which includes multiple hidden layers, is also called deep learning, and deep learning is a part of machine learning. In the following, machine learning will be used to include deep learning.

[0506] Furthermore, the technical features described above can be applied to wireless communication for robots.

[0507] A robot is a machine that automatically processes or operates tasks assigned to it using its own capabilities. In particular, a robot that has the ability to perceive its environment, make decisions on its own, and perform actions is called an intelligent robot.

[0508] Robots can be classified into industrial, medical, household, and military categories depending on their intended use and field. Robots are equipped with drive units, including actuators or motors, and can perform various physical actions, such as moving robotic joints. Mobile robots also include drive units with wheels, brakes, propellers, etc., and can travel on the ground or fly through the air via these drive units.

[0509] Furthermore, the technical features described above apply to devices that support augmented reality.

[0510] Augmented reality is a general term encompassing virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology provides real-world objects and backgrounds solely as computer graphics (CG) images, AR technology provides virtual CG images alongside images of real objects, and MR technology is a computer graphics technology that mixes and combines virtual objects with the real world.

[0511] Mixed Reality (MR) technology is similar to augmented reality (AR) technology in that it displays virtual objects together. However, while AR uses virtual objects to complement other virtual objects, MR uses virtual objects in a way that they are equivalent in nature.

[0512] XR technology is applied to HMDs (Head-Mount Displays), HUDs (Head-Up Displays), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, and other devices, and devices that utilize XR technology can be called XR devices.

[0513] The claims described herein can be combined in various ways. For example, the technical features of the method claims herein can be combined and implemented in an apparatus, and the technical features of the apparatus claims herein can be combined and implemented in a method. Furthermore, the technical features of the method claims herein and the technical features of the apparatus claims herein can be combined and implemented in an apparatus, and the technical features of the method claims herein and the technical features of the apparatus claims herein can be combined and implemented in a method.

Claims

1. In a method for a wireless LAN (Local Area Network) system, The receiving STA (station) receives an EHT (extreme high throughput) PPDU (Physical Protocol Data Unit) from the transmitting STA, The receiving STA includes the step of decoding the EHT PPDU, The EHT PPDU includes a control field and a data field, By combining a 996-tone RU and a 484-tone RU within an adjacent 80MHz frequency subblock of a 160MHz channel, a 996+484-tone MRU (Multiple Resource Unit) is obtained. The data subcarrier of the 996+484 tone MRU in the data field is composed of a combination of the data subcarriers of the 996 tone RU and the 484 tone RU that constitute the 996+484 tone MRU. A method in which the 996+484 tone MRU defined within an OFDMA (Orthogonal Frequency Division Multiple Access) 160 MHz EHT PPDU is permitted within the primary 160 MHz channel or secondary 160 MHz channel of OFDMA transmission at 320 MHz.

2. The control field includes allocation information relating to the 996+484 tone MRU permitted at 320 MHz, Any RU or MRU other than the 996+484 tone MRU permitted at 320 MHz is punctured or assigned for a receiving STA other than the receiving STA. The aforementioned 996-tone RU is an RU composed of 996 tones, The method according to claim 1, wherein the 484-tone RU is an RU composed of 484 tones.

3. The method according to claim 1, wherein, based on the fact that the first channel at 320 MHz is punctured, the second channel excluding the first channel is at least one 20 MHz channel from the primary 20 MHz channel and the secondary 160 MHz channel.

4. Based on the fact that the 320 MHz includes the first to fourth 80 MHz subchannels, the data field is received via the 484 + 242 tone MRU. The aforementioned 484+242 tone MRU is obtained by combining the 484 tone RU and the 242 tone RU within the 80MHz frequency subblock. The data subcarrier of the 484+242 tone MRU is composed of a combination of the data subcarriers of the 484 tone RU and the 242 tone RU that constitute the 484+242 tone MRU. The aforementioned 484+242 tone MRU is allocated within the first 80MHz subchannel. The aforementioned 484+242 tone MRU is allocated within the second 80MHz subchannel. The aforementioned 484+242 tone MRU is allocated within the third 80MHz subchannel. The method according to claim 1, wherein the 484+242 tone MRU is allocated within the fourth 80 MHz subchannel.

5. The control field includes allocation information relating to the 484+242 tone MRU permitted at 320 MHz, Any RU or multiplex RU other than the 484+242 tone MRU permitted at 320 MHz is punctured or allocated for a receiving STA other than the receiving STA. The aforementioned 484-tone RU is an RU composed of 484 tones, The method according to claim 4, wherein the 242-tone RU is an RU composed of 242 tones.

6. The method according to claim 4, wherein one of the first to fourth 80 MHz subchannels is a primary 80 MHz channel, and the remaining three subchannels, excluding the primary 80 MHz channel, are secondary 80 MHz channels.

7. Based on the fact that the receiving STA includes the first and second STAs, and that the 484+242 tone MRU is allocated only within the first and third 80MHz channels, The first STA receives the data field via the 484+242 tone MRU allocated within the first 80MHz channel. The method according to claim 4, wherein the second STA receives the data field via the 484+242 tone MRU allocated within the third 80 MHz channel.

8. Based on the fact that the receiving STA includes the first and second STAs, The first STA receives the data field via the 996+484 tone MRU assigned within the primary 160MHz channel, The method according to claim 1, wherein the second STA receives the data field via the 996+484 tone MRU allocated within the secondary 160 MHz channel.

9. In a receiving STA (station) in a wireless LAN (Local Area Network), Memory and Transceiver and, The system comprises a processor coupled to the memory and the transceiver, The aforementioned processor, Receive an EHT (extreme high throughput) PPDU (Physical Protocol Data Unit) from the transmitting STA. It is configured to decode the aforementioned EHT PPDU, The EHT PPDU includes a control field and a data field, By combining a 996-tone RU and a 484-tone RU within an adjacent 80MHz frequency subblock of a 160MHz channel, a 996+484-tone MRU (Multiple Resource Unit) is obtained. The data subcarrier of the 996+484 tone MRU in the data field is composed of a combination of the data subcarriers of the 996 tone RU and the 484 tone RU that constitute the 996+484 tone MRU. The 996+484 tone MRU defined within the OFDMA (Orthogonal Frequency Division Multiple Access) 160 MHz EHT PPDU is permitted within the primary 160 MHz channel or secondary 160 MHz channel of OFDMA transmission at 320 MHz, receiving STA.

10. In the method for wireless LAN (Local Area Network), The transmitting STA (station) generates an EHT (extreme high throughput) PPDU (Physical Protocol Data Unit), The transmitting STA includes the step of transmitting the EHT PPDU to the receiving STA, The EHT PPDU includes a control field and a data field, By combining a 996-tone RU and a 484-tone RU within an adjacent 80MHz frequency subblock of a 160MHz channel, a 996+484-tone MRU (Multiple Resource Unit) is obtained. The data subcarrier of the 996+484 tone MRU in the data field is composed of a combination of the data subcarriers of the 996 tone RU and the 484 tone RU that constitute the 996+484 tone MRU. A method in which the 996+484 tone MRU defined within an OFDMA (Orthogonal Frequency Division Multiple Access) 160 MHz EHT PPDU is permitted within the primary 160 MHz channel or secondary 160 MHz channel of OFDMA transmission at 320 MHz.

11. The control field includes allocation information relating to the 996+484 tone MRU permitted at 320 MHz, Any RU or MRU other than the 996+484 tone MRU permitted at 320 MHz is punctured or assigned for a receiving STA other than the receiving STA. The aforementioned 996-tone RU is an RU composed of 996 tones, The method according to claim 10, wherein the 484-tone RU is an RU composed of 484 tones.

12. The method according to claim 10, wherein, based on the fact that the first channel at 320 MHz is punctured, the second channel excluding the first channel is at least one 20 MHz channel from the primary 20 MHz channel and the secondary 160 MHz channel.

13. Based on the fact that the 320 MHz includes the first to fourth 80 MHz subchannels, the data field is received via the 484 + 242 tone MRU. The aforementioned 484+242 tone MRU is obtained by combining the 484 tone RU and the 242 tone RU within the 80MHz frequency subblock. The data subcarrier of the 484+242 tone MRU is composed of a combination of the data subcarriers of the 484 tone RU and the 242 tone RU that constitute the 484+242 tone MRU. The aforementioned 484+242 tone MRU is allocated within the first 80MHz subchannel. The aforementioned 484+242 tone MRU is allocated within the second 80MHz subchannel. The aforementioned 484+242 tone MRU is allocated within the third 80MHz subchannel. The method according to claim 10, wherein the 484+242 tone MRU is allocated within the fourth 80 MHz subchannel.

14. The control field includes allocation information relating to the 484+242 tone MRU permitted at 320 MHz, Any RU or multiplex RU other than the 484+242 tone MRU permitted at 320 MHz is punctured or allocated for a receiving STA other than the receiving STA. The aforementioned 484-tone RU is an RU composed of 484 tones, The method according to claim 13, wherein the 242-tone RU is an RU composed of 242 tones.

15. The method according to claim 13, wherein one of the first to fourth 80 MHz subchannels is a primary 80 MHz channel, and the remaining three subchannels, excluding the primary 80 MHz channel, are secondary 80 MHz channels.

16. In a wireless LAN (Local Area Network), at the transmitting STA (station), Memory and Transceiver and, The system comprises a processor coupled to the memory and the transceiver, The aforementioned processor, EHT (extreme high throughput) PPDU (Physical Protocol Data Unit) is generated, The system is configured to transmit the EHT PPDU to the receiving STA. The EHT PPDU includes a control field and a data field, By combining a 996-tone RU and a 484-tone RU within an adjacent 80MHz frequency subblock of a 160MHz channel, a 996+484-tone MRU (Multiple Resource Unit) is obtained. The data subcarrier of the 996+484 tone MRU in the data field is composed of a combination of the data subcarriers of the 996 tone RU and the 484 tone RU that constitute the 996+484 tone MRU. The 996+484 tone MRU defined within the OFDMA (Orthogonal Frequency Division Multiple Access) 160 MHz EHT PPDU is permitted within the primary 160 MHz channel or secondary 160 MHz channel of OFDMA transmission at 320 MHz, as a transmit STA.

Images