Improved modulation technique related to wireless communication system

Abstract

The present disclosure proposes various signaling techniques related to an improved unequal modulation (UEQM) technique. Such a UEQM technique may be related to the generation of a signal (SIG) field including a user field. For example, the user field may include a UEQM information field having the length of 1 bit, and a UEQM pattern field having the length of 2 bits, which is consecutive to the UEQM information field. For example, the UEQM information field may include information related to whether or not UEQM is applied. For example, the UEQM pattern field may include information related to a UEQM pattern applied to at least two spatial streams.

Description

Improved modulation techniques related to wireless communication systems

[0001] This specification relates to a wireless LAN system, and more particularly, to an improved method and device related to modulation of a wireless LAN system.

[0002] Wireless local area networks (WLANs) have been improved in various ways. For example, the Extreme High Throughput (EHT) standard can utilize newly proposed increased bandwidth, an improved PHY layer protocol data unit (PPDU) structure, improved sequences, and Hybrid Automatic Repeat Request (HARQ) techniques. The EHT standard can also be referred to as the IEEE 802.11be standard.

[0003] The EHT specification supports high throughput and high data rates, which may include wide bandwidth (e.g., 160 / 320 MHz), 16 streams, and / or multi-link (or multi-band) operation.

[0004] In the EHT specification, wide bandwidth (e.g., 160 / 240 / 320 MHz) can be used to achieve high throughput. Preamble puncturing and multiple RU transmissions can also be used to efficiently utilize bandwidth.

[0005] WLAN systems can be further improved through the Ultra High Reliability (UHR) standard. The UHR system, also known as the IEEE 802.11bn standard, aims to support ultra-high reliability when transmitting signals to STAs. To achieve this, various technologies are being considered for UHR systems, including high throughput, low latency, and extended range support.

[0006] WLAN systems perform media access based on primary channels. For example, information about a primary channel with a bandwidth of 20 MHz is transmitted to multiple STAs via management frames, and any STA attempting to exchange frames can access the primary channel.

[0007] To improve spectral efficiency in new wireless LAN systems, new MCS levels, indices, and parameters may be considered. If improvements are made to existing MCS techniques, improved technologies may be required for various communications, such as downlink and uplink.

[0008] Additionally, new wireless LAN systems can apply unequal modulation (UEQM) technology to improve the SNR gap between different spatial streams. Applying improved UEQM techniques may require improved technology for various communications, such as downlink and uplink.

[0009] This specification proposes various signaling techniques related to improved MCS techniques and / or UEQM techniques.

[0010] Among the various examples of the present specification, a method related to the UEQM technique may involve generating a signal (SIG) field including a user field. For example, the user field may include a 1-bit long UEQM (unequal modulation) information field and a 2-bit long UEQM pattern field contiguous to the UEQM information field. For example, the UEQM information field may include information related to whether UEQM is applied. For example, the UEQM pattern field may include information related to a UEQM pattern applied to at least two spatial streams (or two or more spatial streams).

[0011] This specification proposes a signaling technique for conveying information about improved MCS techniques and / or improved UEQM patterns when these techniques are applied in uplink or downlink. This allows STAs supporting uplink or downlink to accurately support the improved MCS techniques and / or UEQM techniques.

[0012] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0013] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0014] Figure 3 is a diagram illustrating a general link setup process.

[0015] Figure 4 illustrates one embodiment of a multi-link (ML).

[0016] Figure 5 illustrates a PPDU transmitted / received by an STA of this specification.

[0017] Figure 6 is a diagram showing the layout of resource units (RUs) used for 20MHz PPDU.

[0018] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0019] Figure 8 is a diagram showing the layout of resource units (RUs) used for 80MHz PPDU.

[0020] Figure 9 shows the operation according to UL-MU.

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

[0022] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0023] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0024] Figure 13 shows an example of a header of a MAC frame.

[0025] FIG. 14 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0026] Figures 15 and 16 are drawings illustrating an imbalance that occurs for at least one SS.

[0027] Figures 17 and 18 relate to examples of user info fields proposed in this specification.

[0028] Figures 19 and 20 are examples of user info fields proposed in this specification.

[0029] Figure 21 is an example of the SS allocation field proposed in this specification.

[0030] Figure 22 shows an example of a Trigger Dependent User Info field containing UEQM information.

[0031] Figure 23 is another example of a user info field configured based on the above-described content.

[0032] Figure 24 shows an example of a user field proposed in this specification.

[0033] Figure 25 is another example of a user info field.

[0034] Figure 26 shows an example of a user field proposed in this specification.

[0035] Figure 27 is an example of a procedure flowchart related to this specification.

[0036] Figure 28 is an example of a procedure flowchart related to this specification.

[0037] As used herein, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, as used herein, “A or B” can be interpreted as “A and / or B.” For example, as used herein, “A, B or C” can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0038] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0039] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0040] In addition, parentheses used in this specification may mean “for example”. Specifically, when it is indicated as “control information (UHR-Signal field)”, the “UHR-Signal field” may be proposed as an example of “control information”. In other words, the “control information” in this specification is not limited to the “UHR-Signal field”, and the “UHR-Signal field” may be proposed as an example of “control information”. In addition, even when it is indicated as “control information (UHR-Signal field)”, the “UHR-Signal field” may be proposed as an example of “control information”.

[0041] Additionally, as used herein, “a / an” can mean “at least one” or “one or more.” Additionally, terms ending in “(s)” can mean “at least one” or “one or more.”

[0042] Additionally, the expressions “based on” or “on the basis of” or “according to” used herein mean “based at least in part on” and not “based solely on.”

[0043] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0044] The following examples of this specification can be applied to various wireless communication systems. For example, the following examples of this specification can be applied to wireless local area network (WLAN) systems. For example, the present specification can be applied to the IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification can be applied to the Ultra High Reliability (UHR) standard or the next-generation wireless LAN standard that enhances IEEE 802.11bn. In addition, the examples of this specification can be applied to mobile communication systems. For example, the examples of this specification can be applied to mobile communication systems based on Long Term Evolution (LTE) and its evolution based on the 3rd Generation Partnership Project (3GPP) standard.

[0045] In order to explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0046] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0047] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of the present specification may also be referred to by various names such as a mobile terminal, a wireless device, a Wireless Transmit / Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a Mobile Subscriber Unit, or simply a user. The STA (110, 120) of the present specification may also be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) of the present specification may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

[0048] For example, STA (110, 120) may perform the role of an AP (access point) or a non-AP role. That is, STA (110, 120) of the present specification may perform the functions of an AP and / or a non-AP. In the present specification, AP may also be indicated as an AP STA.

[0049] The STA (110, 120) of this specification can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard). In addition, the STA of this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. In addition, the STA of this specification can support communication for various communication services such as voice calls, video calls, data communications, and autonomous driving (Self-Driving, Autonomous-Driving).

[0050] In this specification, STA (110, 120) may include a medium access control (MAC) and a physical layer interface for a wireless medium that follow the provisions of the IEEE 802.11 standard.

[0051] Based on the sub-drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0052] The first STA (110) may include a processor (111), a memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.

[0053] 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.).

[0054] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (112) of the AP can store a signal received through the transceiver (113) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

[0055] For example, the second STA (120) can perform the intended operation of a non-AP STA. For example, the transceiver (123) of the non-AP 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.).

[0056] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (122) of the Non-AP STA can store a signal received through the transceiver (123) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

[0057] For example, in the specification below, the operation of a device indicated as AP may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is an AP, the operation of the device indicated as AP may be controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). In addition, control information related to the operation of the AP or a transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110). In addition, when the second STA (110) is an AP, the operation of the device indicated as an AP is controlled by the processor (121) of the second STA (120), and a related signal can be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signal of the AP can be stored in the memory (122) of the second STA (110).

[0058] For example, in the specification below, the operation of a device indicated as a non-AP (or User-STA) may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is a non-AP, the operation of the device indicated as a non-AP may be controlled by the processor (121) of the second STA (120), and a related signal may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of a device indicated as a non-AP is controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110).

[0059] In the following specification, devices called (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. without specific drawing symbols may also refer to the STA (110, 120) of FIG. 1. For example, in the example below, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. In addition, in the example below, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processor (111, 121) of FIG. 1.For example, an example of an operation for generating a transmission / reception signal or performing data processing or operation in advance for a transmission / reception signal may include 1) an operation for determining / obtaining / configuring / computing / decoding / encoding bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU, 2) an operation for determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 3) an operation for determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (112, 122) of FIG. 1.

[0060] The device / STA of the sub-drawing (a) of the above-described FIG. 1 can be modified as in the sub-drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of the present specification will be described based on the sub-drawing (b) of FIG. 1.

[0061] For example, the transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the transceiver illustrated in sub-drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) illustrated in sub-drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (a) of FIG. 1 described above.

[0062] The 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 described below may refer to the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.

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

[0064] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.

[0065] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or an enhanced processor thereof.

[0066] In this specification, uplink may mean a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packet / signal, etc. may be transmitted through the uplink. In addition, in this specification, downlink may mean a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packet / signal, etc. may be transmitted through the downlink.

[0067] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0068] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0069] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter, BSS). The BSSs (200, 205) are a collection of APs and STAs, such as an access point (AP) 225 and a station (STA1, 200-1), that have successfully synchronized and can communicate with each other, and are not a concept that designates a specific area. The BSS (205) may also include one or more STAs (205-1, 205-2) that can be associated with one AP (230).

[0070] The BSS may include at least one STA, an AP (225, 230) providing a distribution service, and a distribution system (DS, 210) connecting multiple APs.

[0071] A distributed system (210) can connect multiple BSSs (200, 205) to implement an extended service set (ESS) 240. An ESS (240) can be used as a term to indicate a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) can have the same SSID (service set identification).

[0072] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0073] In a BSS such as the upper part of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network and perform communication between STAs without an AP (225, 230). A network that establishes a network and performs communication between STAs without an AP (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0074] The bottom of Figure 2 is a conceptual diagram showing IBSS.

[0075] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and access to the distributed system is not permitted, forming a self-contained network.

[0076] Figure 3 is a diagram illustrating a general link setup process.

[0077] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning by the STA. That is, for the STA to access the network, it must find a network it can join. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0078] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover which APs exist in the vicinity while moving between channels and waits for a response. A responder transmits a probe response frame to the STA that transmitted the probe request frame in response to the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In a BSS, the AP transmits the beacon frame, so the AP becomes the responder. In an IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not constant. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0079] Although not shown in the example of FIG. 3, the scanning operation can also be performed in a passive scanning manner. An STA performing scanning based on passive scanning can wait for a beacon frame while moving between channels. A beacon frame is one of the management frames in IEEE 802.11. It announces the presence of a wireless network and is periodically transmitted so that the scanning STA can find the wireless network and participate in the wireless network. In the BSS, the AP periodically transmits the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. An STA that receives a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.

[0080] An STA that discovers a network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and the AP responds by transmitting an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

[0081] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group.

[0082] An STA can transmit an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

[0083] A successfully authenticated STA may perform an association process based on step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and the AP transmits an association response frame to the STA in response. For example, the association request frame may include information related to various capabilities, such as a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, and interworking service capabilities. For example, the association response frame may contain information related to various capabilities, status codes, Association ID (AID), supported rates, Enhanced Distributed Channel Access (EDCA) parameter sets, Received Channel Power Indicator (RCPI), Received Signal to Noise Indicator (RSNI), mobility domains, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS maps, etc.

[0084] In step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame.

[0085] Figure 4 illustrates one embodiment of a multi-link (ML).

[0086] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate over a remote link. The MLDs can be categorized into AP MLDs including multiple AP STAs and non-AP MLDs including multiple non-AP STAs. That is, the AP MLD can include affiliated APs (i.e., AP STAs), and the non-AP MLD can include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0087] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be allocated to the first and second links. The first and second multilinks may be identified through a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the second link may be configured in different bands.

[0088] The AP MLD of FIG. 4 includes three affiliated APs. In the example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In the example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Furthermore, in the example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Furthermore, in the example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.

[0089] In the example of FIG. 4, AP1 may initiate a multi-link setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In the example of FIG. 4, non-AP STA1 may transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the AP illustrated in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the STA (i.e., user-STA or non-AP STA) illustrated in FIG. 1 and / or FIG. 2.

[0090] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.

[0091] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0092] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) of the present specification can transmit and / or receive the PPDU of FIG. 5. The PPDU described in the present specification may have, for example, the structure of FIG. 5. In addition, the PPDU described in the present specification may be called by various names such as a transmission PPDU, a reception PPDU, a first type PPDU, or an Nth type PPDU, etc. The PPDU described in the present specification can be used in a WLAN system defined according to IEEE 802.11bn and / or a next-generation WLAN system that improves IEEE 802.11bn.

[0093] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of a single-user (SU) mode / type / transmission, a multi-user (MU) mode / type / transmission, and a null data packet (NDP) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the Data field illustrated may be omitted. If the PPDU of FIG. 5 is used for a trigger-based (TB) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU with the UHR-SIG omitted in the example of FIG. 5.

[0094] In FIG. 5, L-STF or UHR-LTF may be called a preamble or physical preamble, and may be generated / transmitted / received / acquired / decoded in the physical layer (included in the transmitting / receiving STA).

[0095] Each block illustrated in Fig. 5 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 5, L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.

[0096] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in FIG. 5 may be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields may be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields may be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields may be expressed in units of 78.125 kHz.

[0097] In the PPDU of Fig. 5, L-LTF and L-STF may be identical to conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0098] The L-SIG field of FIG. 5 may include, for example, 24 bits of bit information. For example, the 24 bits of information may 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 may include information about the length or time duration of the PPDU. For example, the value of the 12 bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU or UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is a HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in an UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0099] For example, (non-AP and AP) STAs can apply BCC encoding based on a code rate of 1 / 2 to the 24 bits of information in the L-SIG field. Then, the transmitting STA can obtain 48 BCC coded bits. BPSK modulation can be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarriers {subcarrier index -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols can be 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 additionally map the signal {-1, -1, -1, 1} to the subcarrier indices {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0100] For example, (non-AP and AP) STA can generate RL-SIG, which is generated in the same manner as L-SIG. BPSK modulation can be applied to RL-SIG. Receiving (non-AP and AP) STA can determine whether the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of RL-SIG. In other words, if RL-SIG is present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of HE PPDU, EHT PPDU, or UHR PPDU. In other words, if RL-SIG is not present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.

[0101] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be called by various names such as the first SIG field, the first SIG, the first type SIG, the control signal, the control signal field, the first (type) control signal, the common control field, and the common control signal.

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

[0103] For example, A bit information (e.g., 52 uncoded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bits of information (e.g., 26 uncoded bits) out of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bits of information (e.g., 26 uncoded bits) out of the total A bit information. For example, the transmitting STA can obtain 26 uncoded bits included 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 allocated to each U-SIG symbol. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) excluding the pilot tones -21, -7, +7, and +21.

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

[0105] The A bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) 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 can be assigned only to the first symbol of the U-SIG, or the version-independent bits can be assigned to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.

[0106] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.

[0107] In other words, when the (AP / non-AP) STA transmits an EHT PPDU, it can set the 3-bit PHY version identifier to the first value. In other words, the receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is an UHR PPDU based on the PHY version identifier having the second value.

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

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

[0110] For example, if a UHR PPDU is classified into various types (e.g., a type related to SU transmission (performed based on UL or DL), a type related to DL transmission, a type related to NDP transmission, a type related to DL non-MU-MIMO, a type related to DL MU-MIMO, a type related to Multi-AP operation, a type related to CBF (Coordinated beamforming), SR (Spatial Reuse), a type related to C-OFDMA (Coordinated OFDMA), a type related to C-TDMA (Coordinated TDMA)), information about the type of the EHT PPDU (e.g., 2-bit or 3-bit information) can be included in the version-dependent bits of the U-SIG.

[0111] For example, U-SIG may include 1) a bandwidth field including information about bandwidth, 2) a field including information about a Modulation and Coding Scheme (MCS) technique applied to UHR-SIG, 3) an indication field including information about whether a dual subcarrier modulation (DCM) technique is applied to UHR-SIG, 4) a field including information about the number of symbols used for UHR-SIG, 5) a field including information about whether UHR-SIG is generated over the entire band, 6) a field including information about the type of UHR-LTF / STF, and 7) a field indicating the length of UHR-LTF and the CP length.

[0112] Preamble puncturing may be applied to the PPDU of FIG. 5. Preamble puncturing refers to applying puncturing to a portion of the entire bandwidth of the PPDU (e.g., the secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0113] For example, the pattern of preamble puncturing can be preset. For example, when the first puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when the second puncturing pattern is applied, puncturing can be applied only to one of the two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when the third puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, a primary 40 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band) may be present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.

[0114] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.

[0115] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for 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 may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information about a 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern). Meanwhile, the UHR-SIG consecutive to the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern), and the UHR-SIG consecutive to the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about a preamble puncturing pattern).

[0116] Additionally or alternatively, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).

[0117] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth can contain different U-SIGs.

[0118] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted via at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.

[0119] UHR-SIG provides additional signals to the U-SIG field to enable STAs to interpret / decode UHR PPDUs. The UHR-SIG field may contain U-SIG overflow bits that are common to all users. The UHR-SIG field also contains resource allocation information, allowing STAs to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

[0120] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on RUs (resource units) defined by multiple subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through RUs (resource units) defined by multiple subcarriers / tones.

[0121] FIG. 6 is a diagram illustrating the layout of resource units (RUs) used for a 20 MHz PPDU. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.

[0122] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for a receiving station, i.e., a user.

[0123] Meanwhile, the RU arrangement of FIG. 6 is utilized not only in a situation for multiple users (MUs) but also in a situation for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of FIG. 4, in which case three DC tones can be inserted.

[0124] In the example of Fig. 6, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are proposed. Since the specific sizes of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be represented as N-tone RU, etc. For example, 26-RU may be represented as 26-tone RU.

[0125] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0126] As in the example of Fig. 6 where RUs of various sizes were used, the example of Fig. 7 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0127] Additionally, as illustrated, 484 RUs may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.

[0128] Figure 8 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of resource units (RUs) used in this specification may vary. For example, the layout of resource units (RUs) used in the 80MHz band may vary.

[0129] Figure 9 illustrates an operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can acquire a TXOP (925) by performing channel access through contending (i.e., backoff operation) and transmit a trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU including a trigger frame (930). When a PPDU including a trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

[0130] TB PPDUs (941, 942) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (930). The ACK frame (950) for the TB PPDU can be implemented in various forms. For example, the ACK frame (950) for the TB PPDU can be implemented in the form of a BA (block ACK).

[0131] In FIG. 9, transmission(s) of a Trigger Frame (930), TB PPDU (941, 942) and / or ACK frame (950) can be performed within a TXOP (925).

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

[0133] The 2.4 GHz band may be referred to by other names, such as the first band (band). Furthermore, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency between 2.4 and 2.5 GHz) are used / supported / defined.

[0134] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned channel index N may be (2.407 + 0.005*N) GHz. The channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of the channel indices and center frequencies may change.

[0135] Figure 10 exemplarily illustrates four channels within the 2.4 GHz band. The illustrated first frequency region (1010) to fourth frequency region (1040) may each include one channel. For example, the first frequency region (1010) may include channel 1 (a 20 MHz channel having an index of 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency region (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency region (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0136] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0137] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with center frequencies greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 are subject to change.

[0138] Multiple channels within the 5 GHz band include Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency ranges called UNII Mid and UNII-2Extended. UNII-3 may be referred to as UNII-Upper.

[0139] Within the 5 GHz band, multiple channels can be configured, and the bandwidth of each channel can be variously configured, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range can be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range can be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range can be divided into one channel through a 160 MHz frequency domain.

[0140] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0141] The 6 GHz band may also be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, or defined. The specific figures shown in Figure 12 are subject to change.

[0142] For example, the 20 MHz channel of FIG. 12 can be defined from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 can have an index of 1 (or channel index, channel number, etc.), and a center frequency of 5.945 GHz can be assigned. That is, the center frequency of the indexed channel N can be determined as (5.940 + 0.005*N) GHz.

[0143] Accordingly, the indexes (or channel numbers) of the 20 MHz channels of FIG. 12 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, It can be 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule mentioned above, the indices of the 40 MHz channels in Fig. 12 can be 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, 227.

[0144] Below, the structure and types / subtypes of MAC frames are described.

[0145] Fig. 13 illustrates an example of a header of a MAC frame. As illustrated, the MAC frame may include a frame control field / information of 2 octets in length, a duration field / information of 2 octets in length, a RA (Receiver Address) field / information of 6 octets in length, and a TA (Transmitter Address) field / information of 6 octets in length. As illustrated in Fig. 13, the four fields may be consecutive to each other. The MAC header of Fig. 13 may be modified in various ways, and a new field may be inserted between the four illustrated fields, or at least one of the illustrated fields may be omitted.

[0146] The MAC header illustrated in Fig. 13 may be positioned at the very front of a MAC frame. That is, the MAC frame may include a MAC header as illustrated in Fig. 13 and MAC body fields / information subsequent to the MAC header. The MAC frame including the MAC header of Fig. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) illustrated in Fig. 5.

[0147] The MAC frames included in the data field of the PPDU of this specification can be classified into various types. For example, the MAC frames of this specification can be classified into control frames, management frames, and data frames.

[0148] For example, the management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLAN. For the management frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are set to 00. In addition, the values ​​of the subtype fields (B7, B6, B5, B4) in FIG. 13 are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).

[0149] For example, the control frame includes Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLAN. For the control frame, the value of the type field (B3 and B2) in FIG. 13 is set to 01. Also, the values ​​of the subtype fields (B7, B6, B5, B4) of FIG. 13 are as follows: Trigger (0010), Beamforming Report Poll (0100), NDP Announcement (0101), Control Frame Extension (0110), Control Wrapper (0111), BlockAckReq (1000), BlockAck (1001), PS-Poll (1010), RTS (1011), CTS (1100), Ack (1101), CF-End (1110).

[0150] For example, the data frame includes (QoS) Data, (QoS) Null, etc. defined in conventional WLAN. For the management frame, the value of the type field (B3 and B2) of Fig. 13 is set to 10.

[0151] The MAC frame / signal used in this specification can be identified through the type field / information and subtype field / information described above. For example, the “trigger frame” in this specification can mean a MAC frame in which the type bits B3 and B2 bits in the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, B4 bits in the frame control field are also set to 0010. Various MAC frames described in this specification are inserted / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDUs).

[0152] FIG. 14 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0153] The devices (e.g., AP STA, non-AP STA) illustrated in FIGS. 1 to 4 may be modified as illustrated in FIG. 14. The transceiver (630) of FIG. 14 may be identical to the transceivers (113, 123) of FIG. 1. The transceiver (630) of FIG. 14 may include a receiver and a transmitter.

[0154] The processor (610) of FIG. 14 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (610) of FIG. 14 may be identical to the processing chip (114, 124) of FIG. 1.

[0155] The memory (150) of FIG. 14 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (150) of FIG. 14 may be a separate external memory different from the memory (112, 122) of FIG. 1.

[0156] Referring to FIG. 14, a power management module (611) manages power to a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0157] Referring to FIG. 14, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related input to be used by the processor (610).

[0158] Next Wi-Fi (beyond 11be) aims to support ultra-high reliability (UHR) when transmitting signals to STAs. To support this UHR, various technologies are being considered, including high throughput, low latency, and extended range. To achieve this, additional MCS may be considered to improve throughput by increasing spectral efficiency during signal transmission and reception. Additionally or alternatively, unequal modulation (UEQM) technology may be considered. UEQM technology is a technology that considers SNR imbalance across two or more spatial streams (SSs) during MIMO / beamforming transmission. For example, UEQM technology can refer to a technique that utilizes different modulations (e.g., different constellation mappings) for each SS.

[0159] For example, this specification may propose various technical features related to UEQM technology. Such UEQM technology may be used together with an enhanced / improved MCS set proposed in this specification. Additionally or alternatively, the MCS set proposed in this specification may be used independently of the UEQM technology. That is, the technical operations related to the MCS set of this specification may operate independently of the UEQM technology, and the operations related to the UEQM technology of this specification may operate independently of the MCS set proposed in this specification.

[0160] Below, UEQM technology is described.

[0161] For example, in MIMO / Beamforming transmission, since a signal is transmitted using a beamforming matrix formed based on singular value decomposition (SVD), when transmitting a signal using multiple spatial streams (SS), the MIMO gain or SNR may be concentrated on a limited number of SSs, including the first SS (e.g., the 1st SS). In other words, an imbalance may occur in which the MIMO gain or SNR is concentrated only on at least one SS (or some SSs) including the first SS.

[0162] Below, we explain the imbalance that occurs for a specific SS (e.g., some SS including the first SS) based on channel information formed based on SVD.

[0163]

[0164] The singular values ​​(e.g., singular values) of the diagonal matrix of mathematical expression 1 are arranged in descending order of non-zero values. Therefore, when using multiple spatial streams (SS) in this way, a difference in SNR occurs between the SS (spatial streams).

[0165] Figures 15 and 16 are diagrams illustrating an imbalance occurring for at least one SS. The examples in Figures 15 and 16 relate to the SNR difference between the first SS (1st SS) and the remaining SSs (e.g., 2nd / 3rd / 4th SS) when using two SSs or four SSs at 80 MHz.

[0166] For example, as illustrated in Fig. 15, when Nss (i.e., Number of SS) is 2, the range of the SNR gap between the first SS and the second SS is 7 to 15 dB, and the median value is approximately 10 dB. For example, as illustrated in Fig. 16, when Nss is 4, it can be seen that the second SS has a difference of approximately 5 dB, the third SS has a difference of 11 dB, and the fourth SS has a difference of 18 dB based on the median value.

[0167] As described above, when MIMO / beamforming transmission is performed based on multiple SSs, it can be confirmed that an SNR gap occurs between SSs (spatial streams). Since each SS has a different SNR, when transmitting a signal by applying the same MCS during MIMO / beamforming transmission, the signal transmission efficiency may decrease due to the SNR gap. Therefore, it is technically advantageous to consider the SNR gap for each SS during MIMO or beamforming transmission and apply different modulations suitable for the SNR of each SS. In other words, by applying UEQM, it is possible to apply modulations suitable for the individual SNRs of SSs (spatial streams), and based on this, signal transmission efficiency and throughput can be improved.

[0168] For example, UEQM in this specification means applying a first MCS technique to a first SS and applying a second MCS technique to a second SS. For example, the first MCS technique may be the same as or different from the second MCS technique. In other words, MCS techniques applied to different SSs can be individually set. For example, a plurality of MCS techniques related to UEQM (e.g., the first MCS technique and the second MCS technique) can be configured / set based on the same code rate. For example, a plurality of MCS techniques related to UEQM (e.g., the first MCS technique and the second MCS technique) can be based on a constellation mapping technique / technology that is based on the same code rate, but is individually set.

[0169] In other words, when applying different modulations to different SSs (e.g., applying the first MCS technique to the first SS and the second MCS technique to the second SS), the code rate can be fixed to the same value as described above to reduce implementation complexity without requiring an additional encoder. Accordingly, multiple MCS techniques (e.g., the first MCS technique and the second MCS technique) can be based on the same code rate, but can apply modulations (i.e., constellation mapping techniques / techniques) that are individually set.

[0170] For example, the UEQM described below can be used for SU / MU transmission (or reception), SU-MIMO / MU-MIMO / non-MU-MIMO transmission (or reception), and OFDMA / non-OFDMA transmission (or reception). Additionally or alternatively, the UEQM described below can be applied to RUs of various sizes (e.g., 26 / 52 / 106 / 242 / 484 / 996 / n*996-tone RUs). For example, the UEQM described below can be applied to RRUs (regular RUs), DRUs (distributed RUs), and / or MRUs (e.g., small / large size MRUs).

[0171] For example, a new set of MCS parameters (or indices / levels) can be defined with respect to the UEQM of this specification (or independently of the UEQM). For example, a new combination of code rate and modulation (i.e., constellation mapping) that was not previously applied can be defined, as follows.

[0172] For example, with respect to the UEQM of this specification, the MCS parameter set based on code rate 1 / 2 may be at least one of the following MCS parameters.

[0173] 1A parameter: 1 / 2 + 64 QAM

[0174] 2A parameter: 1 / 2 + 256 QAM

[0175] 3A parameter: 1 / 2 + 1024 QAM

[0176] 4A parameter: 1 / 2 + 4096 QAM

[0177] For example, with respect to the UEQM of this specification, a set of MCS parameters based on code rate 2 / 3 may be at least one of the following MCS parameters.

[0178] 1B parameter: 2 / 3 + QPSK

[0179] 2B parameter: 2 / 3 + 16 QAM

[0180] 3B parameter: 2 / 3 + 256 QAM

[0181] 4B parameter: 2 / 3 + 1024 QAM

[0182] Parameter 5B: 2 / 3 + 4096 QAM

[0183] For example, with respect to the UEQM of this specification, the MCS parameter set based on code rate 5 / 6 may be at least one of the following MCS parameters.

[0184] 1C parameter: 5 / 6 + 16 QAM

[0185] The various parameters described above can be used for UEQM. Additionally or alternatively, the various parameters described above can be used independently of UEQM. For example, at least one of the various MCS parameters described above can be allocated / used for a single SS (spatial stream) in relation to SU / OFDMA transmission / reception.

[0186] Among the various MCS parameters described above, it is also possible to utilize only some of the MCS parameters considering throughput gain and spectral efficiency. For example, the following four MCS parameters can be additionally used in the IEEE 802.11bn system (or UHR system). Additionally or alternatively, the following four MCS parameters can also be additionally used in the next-generation WLAN / WIFI system that further improves the IEEE 802.11bn system. The following four MCS parameters can be called by various names such as extended / enhanced / improved / UHR-MCS parameter / index, etc. The number of extended MCS parameters can be four or more.

[0187] Additionally or alternatively, examples of Extended MCS parameters proposed in the present specification may be QPSK-2 / 3, 16QAM-2 / 3, 16QAM-5 / 6, 256QAM-2 / 3. In addition to the 16 MCS parameters (MCS0 to MCS15 in Table 1 below) proposed in conventional wireless LAN standards, four Extended MCS parameters of the present specification are represented in a table as follows. Additionally or alternatively, Modulation related to MCS parameters / indexes / levels in Table 1 below and the present specification may mean constellation mapping, and may mean, for example, BPSK, QPSK, 16QAM, 64QAM, 256QAM, 1024QAM, and / or 4096QAM. Additionally or alternatively, in Table 1 below and in the present specification, code rate represents the ratio of the actual information bit length k to the encoded codeword length n, and may be expressed as, for example, k / n, and may mean, for example, 1 / 2, 3 / 4, 2 / 3, and / or 5 / 6.

[0188] MCS indexModulationCode rateMCS0BPSK1 / 2MCS1QPSK1 / 2MCS2QPSK3 / 4MCS316QAM1 / 2MCS416QAM3 / 4MCS564QAM2 / 3MCS664QAM3 / 4MCS764QAM5 / 6MCS8256QAM3 / 4MCS9256QAM5 / 6MCS101024QAM 3 / 4MCS111024QAM5 / 6MCS124096QAM3 / 4MCS134096QAM5 / 6MCS14BPSK-DCM+DUP1 / 2MCS15BPSK-DCM1 / 2MCS16QPSK2 / 3MCS1716QAM2 / 3MCS1816QAM5 / 6MCS19256QAM2 / 3

[0189] The four newly proposed MCS parameters compared to the conventional ones are expressed as MCS16 to MCS19 in Table 1. The order of the various MCS parameters expressed in Table 1 may be changed in consideration of various factors such as data rate and / or throughput.

[0190] Below, UEQM technology / transmission is described in relation to MCS parameters.

[0191] For example, UEQM transmission can be considered when NSS is 1, 2, 3, or 4. Additionally, the number of NSS can be varied in general. UEQM transmission can support different numbers of NSS for DL ​​transmission and UL transmission. For example, UEQM related to DL can support up to 4 NSS, UEQM related to UL can support up to 2 / 3 / 4 NSS. For example, UEQM related to DL can support up to 5 / 6 / 7 / 8 NSS, UEQM related to UL can support up to 2 / 3 / 4 / 5 / 6 / 7 / 8 NSS.

[0192] For example, Table 2 below relates to UEQM supporting up to 4 NSSs. For example, if 2 NSSs are supported, a modulation (i.e., constellation mapping) indicated by M may be applied to the first SS as shown in the table below. In this case, a modulation (i.e., constellation mapping) indicated by M-1 or M-2 may be applied to the second SS.

[0193] For example, if three NSSs are supported, the modulation indicated by M (i.e., constellation mapping) may be applied to the first SS, as shown in the table below. In this case, the modulation indicated by M or M-1 (i.e., constellation mapping) may be applied to the second SS. In this case, the modulation indicated by M-1 or M-2 (i.e., constellation mapping) may be applied to the third SS.

[0194] For example, if up to 4 Nss are supported, the modulation for the 1st / 2nd / 3rd / 4th SS can be set / configured based on M, M-1, and M-2 in the manner shown in Table 2 below based on the above-described method.

[0195] Total Nss1st ss2nd ss3rd ss4th ss2ssMM-1 MM-2 3ssMMM-1 MMM-2 MM-1M-2 4ssMMMM-1MMMM-2MMM-1M-2

[0196] In the above Table 2 and the following specification, the variable / index / parameter / level M is determined based on the modulation (i.e., constellation mapping) indicated by the 4 or 5-bit MCS field included in the UHR-SIG field (or a field included in various frames such as a trigger frame). For example, if 64QAM-3 / 4 is indicated by the 5-bit MCS included in the user field (e.g., MU-MIMO user field or non-MU-MIMO user field) of the UHR-SIG field, M in the present specification may mean 64QAM. In this case, M-1 may mean a modulation (i.e., constellation mapping) that is one level lower than M. For example, if M is 64QAM, M-1 may mean 16QAM, M-2 may mean QPSK, and M-3 may mean BPSK.

[0197] In the above Table 2 and the specification below, N (where N is a natural number greater than or equal to 1) lower level modulation (i.e., constellation mapping) may mean the following. For example, if M is 4096QAM, M-1 may mean 1024QAM, M-2 may mean 256QAM, M-3 may mean 64QAM, M-4 may mean 16QAM, M-5 may mean QPSK, and M-6 may mean BPSK. For example, if M is 1024QAM, M-1 may mean 256QAM, M-2 may mean 64QAM, M-3 may mean 16QAM, M-4 may mean QPSK, and M-5 may mean BPSK. For example, if M is 256QAM, M-1 may mean 64QAM, M-2 may mean 16QAM, M-3 may mean QPSK, and M-4 may mean BPSK. For example, M could mean 16QAM, M-1 could mean QPSK, and M-2 could mean BPSK. For example, if M is QPSK, M-1 could mean BPSK.

[0198] Additionally, generally, the above M can be defined as 16QAM or higher. Accordingly, the above M can be set only to 16QAM, 64QAM, 256QAM, 1024QAM, and 4096 QAM.

[0199] As described above, the variable / index / parameter M can be determined / set / indicated based on various sizes of MCS information / fields / subfields described below (e.g., 5-bit MCS information, or 4-bit MCS information combined with MCS extension 1 bit, or 4 / 5-bit UL MCS information, etc.).

[0200] Technical Feature 1 - MCS Extension

[0201] Below, we propose a technique for signaling newly defined MCS parameters in relation to (or independent of) UEQM.

[0202] Considering the four newly added MCS levels / parameters / indexes (e.g., QPSK-2 / 3, 16QAM-2 / 3, 16QAM-5 / 6, 256QAM-2 / 3) as described above, the MCS field can be configured with 5 bits. Additionally or alternatively, the user field of the UHR-SIG field and / or the user info field of the Trigger frame for indicating information related to MCS can be configured as follows.

[0203] Technical Features 1.1

[0204] Hereinafter, an example of a User field included in a UHR SIG field will be described. For example, the UHR SIG field may be a field that is continuous with the U-SIG field and may include a common info field and a user-specific field. The user field may be included in the user-specific field. For example, the user-specific field may include at least one user encoding block, and each user encoding block may include one or two user fields. The user field described below may be a user field for non-MU-MIMO communication or a user field for MU-MIMO communication.

[0205] For example, the MCS field included in the UHR-SIG field may consist of 5 bits. Additionally, alternatively, the MCS field may be defined using B11 to B15 of the UHR-SIG field. For example, considering the conventional EHT-SIG field, the MCS field may be extended using B15, which is a reserved bit of the EHT-SIG field, to indicate a newly added MCS.

[0206] For example, as shown in Table 3 below, B11 to B14 of the user field are 4-bit information for identifying conventional MCS parameters / indexes / levels (e.g., including MCS0 to MCS15 described in Table 1), and B15 of the user field may be composed of 1-bit MCS extension information / field / subfield.

[0207] BitSubfieldNumber of bitsB0-B10STA-ID11B11-B14MCS4B15MCS extension1

[0208] Additionally or alternatively, for MCS indication in new wireless LAN systems (e.g., UHR system or next wi-fi), the MCS field is defined using B11-B15 and can be defined as follows.

[0209] BitSubfieldNumber of bitsB0-B10STA-ID11B11-B15MCS5

[0210] For example, if the MCS indication is extended using B15 as in Table 3 above, or if the MCS field is defined using 5 bits as in Table 4, the indication for the MCS table can be defined as follows.

[0211] B15~B11MCS index00000MCS000001MCS100010MCS200011MCS300100MCS400101MCS500110MCS600111MCS701000MCS801001MCS901010 MCS1001011MCS1101100MCS1201101MCS1301110MCS1401111MCS1510000MCS1610001MCS1710010MCS1810011MCS1910100 ~11111Reserved

[0212] That is, as described above, it can be used to indicate an MCS set including a new MCS set using 5 bits. As another example, when using a new MCS set, B15 (for example, when used as an MCS extension bit) is set to 1 to indicate that the MCS indication represents a new MCS. Conversely, when indicating an existing MCS, B15 is set to 0.

[0213] Based on the above, when applied to Table 5, the following is obtained. That is, there is no change in the 5-bit configuration related to MCS0 to MCS15 in Table 5. However, in Table 5, for MCS16 (QPSK-2 / 3), the MSB (e.g., B15 bit) of the 5 bits may be configured as 1, and the remaining 4 bits of the 5 bits may be configured as the same value as QPSK-1 / 2 (e.g., '1' or 0001). In addition, in Table 5, for MCS17 (16QAM-2 / 3), the MSB (e.g., B15 bit) of the 5 bits may be configured as 1, and the remaining 4 bits of the 5 bits may be configured as '3' or 0011. Also, in Table 5, for MCS18 (16QAM-5 / 6), the MSB (e.g., B15 bit) of the 5 bits may be configured as 1, and the remaining 4 bits of the 5 bits may be configured as '4' or 0100. Also, in Table 5, for MCS19 (256QAM-2 / 3), the MSB (e.g., B15 bit) of the 5 bits may be configured as 1, and the remaining 4 bits of the 5 bits may be configured as '7' or 0111.

[0214] Technical Features 1.2

[0215] The above-described technical feature may be applied to at least one of the user field for MU-MIMO (allocation) and the user field for non-MU-MIMO (allocation). For example, an example of technical feature 1.2 described below may be applied only to the user field for MU-MIMO (allocation).

[0216] For example, newly added MCS parameters / indexes / levels (e.g., the four MCS parameters described above) can be used during MU-MIMO transmission. For example, the added MCS parameters can be classified as an extended MCS set, and such an extended MCS set can be identified / indicated by various techniques as follows.

[0217] For example, in a UHR system, the total Nss (number of SS) supported in MU-MIMO can be up to 8, in which case the bit size of the Spatial Configuration field included in the User field can be 4 bits. For example, the Spatial Configuration field consisting of 4 bits can be configured in the same way as the Spatial Configuration field defined in the HE-SIG use field of the conventional IEEE 802.11ax. In this case, 2 bits can be secured as available bits in the User field. One bit of the 2 bits secured in this way can be used to indicate the extended MCS set. In this case, the information consisting of 1 bit can be used to identify / indicate the extended MCS set (QPSK-2 / 3, 16QAM-2 / 3, 16QAM-5 / 6, and 256QAM-2 / 3) as described above. Additionally or alternatively, all MCS parameters / indexes / levels can be identified / indicated based on the 5-bit MCS field rather than the 1-bit extended information.

[0218] For example, among the two bits secured as described above, the remaining one bit can be reserved. By using the above method, the size of the user field can be used without changing when indicating the extend MCS set, thereby reducing signaling overhead. Additionally or alternatively, the reserved one bit can be allocated for an indication of a future feature defined in UHR or next Wi-Fi.

[0219] Additionally, in general, the 1-bit reserved information secured in the User field may include information regarding whether long codeword LDPC (e.g., 2x LDPC) is supported / applied. For example, the 1-bit information regarding 2x LDPC may be commonly included in the user field for MU-MIMO (allocation) as well as the user field for non-MU-MIMO (allocation).

[0220] At least one of the above examples can be explained based on Table 6 below. That is, the Spatial Configuration field, which is composed of 6 bits in the user field of the existing EHT-SIG field, is configured as 4 bits, and the 1 bit secured through this can be used for future feature indication (or indication of a feature newly defined in next wi-fi or UHR) as described above.

[0221] Additionally, among the additionally secured 2 bits, the remaining 1 bit can be used as a bit for the Incorporated MCS field or MCS extension indication. Alternatively, the 1 bit can be used for MCS, and based on this, the MCS field can have a total length of 5 bits.

[0222] BitSubfieldB0-B10STA-IDB11-B15MCSB16CodingB17-B20Spatial ConfigurationB21Reserved / future feature indication

[0223] Meanwhile, although not included in Table 6, as described above, the user field may include 1-bit information regarding whether 2x LDPC is applied / supported, and this 1-bit information regarding 2x LDPC may be included in bit B22 of the user field. In addition, the 1-bit information regarding 2x LDPC may be commonly included in the user field for non-MU-MIMO (allocation) as well as the user field for MU-MIMO (allocation).

[0224] The bit order of the above user format is an example, and the order according to size may be configured differently from the above. That is, the position of the above field may be configured differently from the above.

[0225] Technical Features 1.3

[0226] Technical feature 1.3 below is an example of modifying technical feature 1.2. For example, the user field for MU-MIMO (allocation) included in the conventional EHT-SIG field is composed of a 6-bit (B5 to B0 bit) Spatial Configuration field as shown in Table 7 below. Technical feature 1.3 below can reuse any one bit (e.g., MSB bit, LSB bit, B5 bit) of the 6-bit (B5 to B0 bit) information as shown in Table 7 as information related to MCS, and allocate the remaining 5 bits of information for Spatial Configuration.

[0227] The example in Table 7 pertains to the case where N_user is 2, but the 6-bit Spatial Configuration field according to the EHT specification has a specific bit (e.g., MSB bit, LSB bit, or B5 bit) always set to 0. Based on this, any one bit of the 6-bit Spatial Configuration field according to the EHT specification (the MSB bit, LSB bit, or B5 bit of the 6-bit Spatial Configuration field) can be used as a bit for MCS indication (e.g., extended MCS indication 1 bit or MCS bit extension information). Based on this, the size of the existing MCS field can be increased to 5 bits, or an extended MCS indication 1 bit (or MCS bit extension) used together with the existing 4-bit MCS field can be defined.

[0228] N_UserB5.B0N_SS [1]N_SS [2]N_SS [3]N_SS [4]N_SS [5]N_SS [6]N_SS [7]N_SS [8]TotalN_SSTotal entries2000000-0000111-412-510000100-0001102-424-6000111-0010003-436-7001001448

[0229] The MCS bit extension of the above UHR-SIG can be defined when the 3-bit PHY Version Identifier included in the U-SIG field is set to a value other than 0. For example, the MCS bit extension can be applied when the PHY Version Identifier has a value of 1 or greater.

[0230] Technical Features 1.4

[0231] Technical feature 1.4 described below relates to the User info field included in the Trigger frame. The Trigger frame may include a Common info field, a Special User info field, and / or an EHT / UHR variant user info field. The EHT / UHR variant user info field may include user-specific information related to an EHT user STA and a UHR user STA.

[0232] Figures 17 and 18 relate to examples of user info fields proposed in this specification.

[0233] For example, the user info field of a UHR variant trigger frame or an EHT variant trigger frame supporting a newly defined MCS may include a 5-bit MCS field for indication of a newly defined MCS table. For example, in the case of a UHR variant user info field, the MCS field may be defined using B21 to B25, as illustrated in FIG. 18. Additionally or alternatively, in the case of an EHT variant user info field, the MCS field may be extended to 5 bits by combining a 4-bit MCS field and the B25 bit, as illustrated in FIG. 17.

[0234] Additionally or alternatively, in the case of the UHR variant user info field, it may be defined if the 3-bit PHY Version Identifier included in the special user info field is set to a value other than 0. For example, if a UHR system is applied, the PHY Version Identifier may be set to 1. Additionally or alternatively, a 5-bit long MCS field, as illustrated in FIG. 18, etc., may be configured if the PHY Version Identifier included in the special user info field is defined to a value greater than or equal to 1.

[0235] Additionally or alternatively, the 4-bit MCS field and 1-bit MCS extension bit illustrated in FIG. 17 may be configured identically to the combination of the 4-bit MCS field (bits B21 to B24 of FIG. 17) and the 1-bit MCS extension bit (B25 of FIG. 17) described in the technical feature 1.1 described above (e.g., the MCS 4-bit and MCS extension 1-bit of Table 3).

[0236] Additionally or alternatively, the 5-bit MCS field illustrated in FIG. 18 (bits B21 to B25 of FIG. 18) may be configured identically to the 5-bit MCS field illustrated in Technical Feature 1.1 described above (e.g., MCS 5 bits of Table 4).

[0237] Technical Feature 2 - UEQM

[0238] Below, various technical features related to UEQM are described. For example, more specific technical features related to UEQM, as described in Table 2, are disclosed below.

[0239] Technical Features 2.1

[0240] Hereinafter, an example of a User field included in a UHR-SIG field is described. For example, the UHR-SIG field may be called by various names such as a SIG field, a first or second SIG field, an EHT-SIG field, etc. For example, technical features related to UEQM related to modulation (i.e., constellation mapping / index) indicated by a 5-bit MCS field included in the User field are described. As described above, the UHR SIG field may be a field continuous to the U-SIG field and may include a common info field and a user-specific field. The user field may be included in the user-specific field. For example, the user-specific field may include at least one user encoding block, and each user encoding block may include one or two user fields. For example, the UHR SIG field may include a common field and a user-specific field. The user-specific field may be continuous to the common field. For example, the user field may be related to various communication techniques. Specifically, the user field may be a user field for non-MU-MIMO communication or a user field for MU-MIMO communication.

[0241] Technical Features 2.1.1

[0242] Technical feature 2.1.1 relates to the UEQM indication field. The UEQM indication field may be called by various names, such as the first UEQM field, UEQM information field, UEQM control field, UEQM control info field, UEQM info field, UEQM field, etc.

[0243] The UEQM indication field may indicate whether UEQM is applied. In other words, information regarding whether UEQM is applied / supported to a PPDU including the UEQM indication field (e.g., (UHR) PPDU transmitted to a non-AP STA via DL) may be included in the UEQM indication field. In other words, the UEQM indication field may include information regarding whether UEQM is applied over a different spatial stream. In other words, the UEQM indication field may include information regarding whether UEQM is applied over a plurality of spatial streams (or two, three, or four spatial streams) related to a SIG including the user field (or a PPDU including the user field, or a Data field related to the user field, or a Resource Unit related to the user field). In other words, the UEQM indication field may include information about whether UEQM is applied over multiple spatial streams (or two, three, or four spatial streams) applied to a Data field decoded / interpreted based on the user field.

[0244] The UEQM indication field may have a length of 1 bit. If the UEQM is applied / supported (i.e., if the UEQM is applied to the corresponding PPDU), the UEQM indication field may have a first value (e.g., 1 or 0). If the UEQM is not applied / supported (i.e., if the EQM is applied to the corresponding PPDU), the UEQM indication field may have a second value (e.g., 0 or 1). For example, the UEQM indication field may be located at bit B19 of the User field. Additional descriptions regarding this are provided below based on Tables 12 and 13.

[0245] Additionally or alternatively, the UEQM indication field can be defined using 1 bit of the Nss field defined as 4 bits in the EHT user field. That is, the Max Nss supported in UHR transmission can be limited to 8. Therefore, the NSS field (4 bits) defined in the existing EHT-SIG user field can be reconfigured and defined as the UEQM field (1 bit) and the NSS field (3 bits). In this case, since no new additional bit is used for the signaling, the same user field size as the existing user field can be maintained. For example, the bit allocated for the UEQM indication field can be composed of 1 bit of MBS or LSB among the 4 bits of the NSS field of 11be. For example, the bit allocated for the UEQM indication field can be defined as B16 or B19.

[0246] Technical Features 2.1.2

[0247] Technical feature 2.1.2 relates to the UEQM (Unequal Modulation) configuration field. The UEQM configuration field may be referred to by various names, such as the first / second configuration field, the UEQM (modulation) pattern(s) field, the UEQM (modulation) pattern(s) control field, etc. The UEQM configuration field may have various lengths. For example, it may consist of 2 bits or 3 bits.

[0248] For example, Table 8 relates to the case where the UEQM configuration field has a length of 2 bits and Nss is 2. For example, the technical features related to Table 2 described above can be applied to Tables 8 to 10 below. In other words, M shown in Tables 8 to 10 is determined based on the modulation (i.e., constellation (mapping) or constellation index / parameter) indicated by the 5-bit MCS field included in the UHR-SIG field. For example, if 64QAM-3 / 4 is indicated by a 5-bit MCS (e.g., bits B11 to B15 shown in Table 12 or Table 13) included in a user field of a UHR-SIG field (e.g., MU-MIMO user field or non-MU-MIMO user field), M in the present specification may mean 64QAM. In this case, M-1 may mean a modulation (i.e., constellation mapping) that is one level lower than M. For example, if M is 64QAM, M-1 may mean 16QAM, M-2 may mean QPSK, and M-3 may mean BPSK. Additionally, alternatively, M may be defined as a specific modulation level (e.g., 16QAM) or higher. In other words, M may be a constellation index indicated by the MCS field (e.g., a 5-bit field). In addition, M-1 may be a constellation index indicated by the MCS field (e.g., a 5-bit field). In addition, M-1 may be a constellation index indicated by the MCS field (e.g., a 5-bit field). It is a constellation that is one order lower than M. Also, M-2 can be a constellation that is two orders lower than M.

[0249] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss2ss0MM-11MM-22~3Reserved

[0250] In other words, the UEQM configuration field may include information related to constellation indices applied to two spatial streams. For example, based on the value of the UEQM configuration field being 0, the constellation index related to the first spatial stream may be M, and the constellation index related to the second spatial stream may be M-1. For example, based on the value of the UEQM configuration field being 1, the constellation index related to the first spatial stream may be M, and the constellation index related to the second spatial stream may be M-2.

[0251] In this specification, the method by which the value of the UEQM configuration field is determined as 0 (0) may vary. For example, if each bit value constituting the UEQM configuration field is set to 0, the value of the UEQM configuration field may be interpreted as 0 (0). In addition, in this specification, the method by which the value of the UEQM configuration field is determined as one (1) may vary. For example, if one of the two bits constituting the UEQM configuration field (e.g., bit B20 or bit B21 of the user field) has a value of 1 and the other one (e.g., bit B21 or bit B20 of the user field) has a value of 0, the value of the UEQM configuration field may be interpreted as one (1). In addition, in this specification, the method by which the value of the UEQM configuration field is determined as two (2) may vary. For example, if one of the two bits constituting the UEQM configuration field (e.g., the B21 bit or the B20 bit of the user field) has a value of 1 and the other one (e.g., the B20 bit or the B21 bit of the user field) has a value of 0, the value of the UEQM configuration field can be interpreted as two (2). In addition, in the present specification, the method by which the value of the UEQM configuration field is determined as three (3) may vary. For example, if both bits constituting the UEQM configuration field are set to one (1), the value of the UEQM configuration field can be interpreted as three (3).

[0252] For example, Table 9 relates to the case where the UEQM configuration field has a length of 2 bits and Nss is 3.

[0253] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss3 rd SS3ss0MMM-11MMM-22MM-1M-23Reserved

[0254] In other words, Table 9 may include information related to constellation indices applied to three spatial streams. For example, based on the value of the UEQM configuration field being 0, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, and the constellation index related to the third spatial stream may be M-1. In addition, based on the value of the UEQM configuration field being 1, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, and the constellation index related to the third spatial stream may be M-2. In addition, based on the value of the UEQM configuration field being (2), the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M-1, and the constellation index related to the third spatial stream may be M-2.

[0255] For example, Table 10 relates to the case where the UEQM configuration field has a length of 2 bits and Nss is 4.

[0256] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss3rd ss4th ss4ss0MMMM-11MMMM-22MMM-1M-23Reserved

[0257] In other words, Table 10 may include information related to constellation indices applied to four spatial streams. For example, based on the value of the UEQM configuration field being 0, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M, and the constellation index related to the fourth spatial stream may be M-1. In addition, based on the value of the UEQM configuration field being 1, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M, and the constellation index related to the fourth spatial stream may be M-2. In addition, based on the value of the UEQM configuration field being (2), the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M-1, and the constellation index related to the fourth spatial stream may be M-2.

[0258] The examples of Tables 8 to 10 described above can be modified in various ways. For example, the modulation for the first SS can be omitted because it is indicated through the MCS. In the case where the modulation order used for each SS in a specific NSS during UEQM, i.e. the UEQM pattern, is configured as 2 bits, an STA receiving a PPDU including a UHR-SIG field can determine the modulation information used for each SS through the UEQM indication field, NSS, MCS, and UEQM pattern information.

[0259] Hereinafter, an example in which the UEQM configuration field has a length of 3 bits is described. For example, the 3-bit field is configured to include all information on modulation application when applying UEQM according to NSS, and can be configured as follows. In this case, the 3-bit field can include both information related to NSS and information related to UEQM patterns. This can produce a technical effect of reducing the number of bits by omitting the NSS field.

[0260] Value of unequal Modulation configuration fieldContents01 st ss = M, 2 nd ss = M-111 st ss = M, 2 nd ss = M-221 st ss = M, 2 nd ss = M, 3 rd ss = M-131 st ss = M, 2 nd ss = M, 3 rd ss = M-241 st ss = M, 2 nd ss = M-1, 3 rd ss = M-251 stss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-161 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-271 st ss = M, 2 nd ss = M, 3 rd ss = M-1, 4 th ss = M-2

[0261] For example, in Table 11, modulation for the first SS can be omitted because it is indicated through MCS. For example, the 3-bit field above is an example and can be defined as another field. The 3-bit field related to the UEQM pattern can be reserved when the UEQM indication field is set to 0 (i.e., when UEQM is not applied). In addition, the 3-bit Table can be transformed into various sizes, such as 4 bits.

[0262] Technical Features 2.1.3

[0263] Technical feature 2.1.3 relates to additional technical features applicable to the user field included in the UHR-SIG field (either the user field for non-MU-MIMO communication or the user field for MU-MIMO communication).

[0264] The user field of this specification may have various bit lengths, and may have any of various lengths such as 22 bits, 23 bits, 24 bits, 25 bits, 26 bits, etc. For example, the user field of this specification may be configured with 22 bits, the same as the existing EHT. In order to maintain the existing length, the Nss subfield / information (i.e., information related to the number of SSs) included in the user field may be set to 3 bits. Additionally or alternatively, the remaining available 1 bit is used for the UEQM indication field described above.

[0265] Additionally or alternatively, it is preferable that the position of the above-described 2-bit or 3-bit UEQM configuration field on the user field be determined by considering the following. For example, the UEQM configuration field may consider an existing field that can be omitted when UEQM is applied / supported. For example, the B20 bit of the user field may include 1-bit information on whether beamforming is applied. However, since the application of UEQM means the use of two or more SSs, separately indicating that beamforming is applied may result in signaling overhead. Accordingly, it is preferable that the UEQM configuration field be located on the B20 bit of the user field. In addition, the B21 bit of the user field may include 1-bit information on the coding type (e.g., LDPC or BCC). However, the application of UEQM may mean transmission and reception in a relatively high-end device, in which case it may be preferable to use LDPC, which has superior performance compared to BCC. Accordingly, when UEQM is applied, 1-bit information about the coding type is omitted, and when UEQM is applied, LDPC can be used instead of BCC. Accordingly, it is preferable that the UEQM configuration field is located on the B21 bit of the user field. In summary, it is preferable that the UEQM configuration field has a length of 2 bits and is located on the B20 and B21 bits of the user field.

[0266] In other words, since it is expressed that UEQM is applied when the UEQM indication field has the first value (e.g., 1), it is preferable that the B20 bit and the B21 bit of the user field are defined as the UEQM configuration field. Additionally or alternatively, since it is expressed that UEQM is not applied and EQM is applied instead when the UEQM indication field has the second value (e.g., 0), the B20 bit of the user field may be defined as 1-bit information about whether beamforming is applied, and the B21 bit of the user field may be defined as 1-bit information about coding type (e.g., LDPC or BCC).

[0267] In other words, it is preferable that the user field includes a UEQM configuration field on B20 and B21 bits when the UEQM indication field (e.g., B19 bit) has the first value, but excludes a 1-bit long Beamformed field and a 1-bit long coding field. For example, the 1-bit long Beamformed field is information that can be located at B20 bits and may include information on whether a beamforming steering matrix is ​​applied. For example, the 1-bit long coding field is information that can be located at B21 bits and may include information on whether a BCC (binary convolutional code) or LDPC (Low Density Parity Check) is applied to a Data field (or Resource Unit) related to the user field.

[0268] Additionally or alternatively, the UEQM configuration field can be defined as 2 bits using 1 bit of the beamformed field (e.g., B20 bits) and the Nss field. Consequently, the Nss field can be transformed from 3 bits to 2 bits.

[0269] To summarize the above, the user field format for non-MU MIMO allocation can be expressed as shown in Table 12 below. Specifically, when applied to UEQM, the UEQM configuration field can be located at bits B20 and B21.

[0270] BitSubfieldB0-B10STA-IDB11-B15MCSB16-B18NSSB19UEQMB20-21Unequal modulation configuration field

[0271] The above example can be modified in various ways. For example, the size of the existing bits can be modified, or additional bits not shown in Table 12 can be included. For example, the UEQM configuration field can be configured to consider a maximum of 4 SS, and accordingly, the NSS field can have a length of 2 bits. In this case, 1 bit newly secured from the existing 3-bit NSS field (e.g., bit B18 in Table 13) can be used for an indication of a new feature defined in UHR. The user field format for non-MU MIMO allocation as described above can be expressed as shown in Table 13 below.

[0272] BitSubfieldB0-B10STA-IDB11-B15MCSB16-B17NSSB18Reserved or new feature indicationB19UEQMB20-21Unequal modulation configuration field

[0273] Technical Features 2.1.4

[0274] Technical feature 2.1.4 relates to the operation of an STA that receives a UHR-SIG related to UEQM (e.g., a non-AP STA that receives a DL-PPDU including a UHR-SIG field). For example, when transmitting or receiving a signal using UEQM, the STA can use the information contained in the user field of UHR-SIG or next SIG to determine information about the modulation applied to the signal transmitted to itself for each SS. For example, when an AP applies UEQM during MIMO transmission using two SSs to an STA, the information in the user field of the SIG field (e.g., UHR-SIG field) is set as follows.

[0275] Nss= 2, MCS = 5, UEQM = 1, Unequal modulation configuration (if 2 bit) = 0.

[0276] The STA receiving the user field of the above SIG field (e.g., UHR-SIG field) recognizes that UEQM has been applied through the UEQM field. It also recognizes that the signal has been transmitted through two SSs through Nss. It also confirms that the MCS applied to the 1st SS is 64QAM (2 / 3 rate) through the MCS field. In addition, based on the 2-bit value of the UEQM configuration field (for example, if the 2-bit value indicates 0 as shown in Table 8, the 1st SS is encoded based on M and the 2nd SS is encoded based on M-1), it can know that the modulation applied to the 2nd SS is 16QAM (2 / 3 rate). The STA that has confirmed the information on the modulation applied to each SS as described above uses the information to decode the received signal.

[0277] Technical Features 2.1.5

[0278] Technical Features 2.1.5 describes various variations on the technical features described above.

[0279] Additionally or alternatively, information regarding whether the UEQM is applied may be included in the U-SIG or UHR-SIG field. For example, the indication regarding the UEQM may be composed of 1-bit information. For example, the 1-bit information may be defined using one of the validate or disregard bits of the U-SIG field. For example, if the 1-bit information is included in the UHR-SIG field, the field may be defined by being included in the common field or the user info field of the UHR-SIG field.

[0280] When UEQM transmission / application is indicated through the UEQM field defined as above (e.g., UEQM (indication) field = 1), indication for modulation by SS according to UEQM can be defined in the following way.

[0281] Option 1 of Technical Feature 2.1.5 described below relates to indication using the Nss field.

[0282] When UEQM is applied, information about the UEQM pattern can be identified as follows. For example, when UEQM is applied, the MCS used in the first SS (1st SS) can be indicated through the MCS field newly proposed in this specification. For example, when UEQM is applied (e.g., UEQM = 1), the NSS field can be configured differently from EQM transmission. For example, when UEQM is applied, the NSS field can be defined to include NSS information used for transmission and modulation configuration information for each SS. In this case, the configuration of the NSS field proposed in this specification can be as shown in Table 14 below.

[0283] Value of NSS fieldcontent0Nss=2, 1 st ss = M, 2 nd ss = M-11Nss=2, 1 st ss = M, 2 nd ss = M-22Nss=3, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-13Nss=3, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-24Nss=3, 1 st ss = M, 2 nd ss = M-1, 3 rd ss = M-25Nss=4, 1st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-16Nss=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-27Nss=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-1, 4 th ss = M-28~15Reserved

[0284] As another example, information about UEQM and modulation by SS during UEQM can be transmitted through the user field of UHR-SIG, and at this time, the user field can be configured to include a UEQM field (1 bit) and an Nss field (3 bit field). In UHR transmission, the supported Max Nss can be limited to 8. Therefore, the NSS field (4 bits) defined in the existing EHT-SIG user field can be reconfigured and defined as a UEQM field (1 bit) and an NSS field (3 bits), and at this time, since no new additional bits are used for the signaling, the same user field size as the existing user field can be maintained. The bit allocated for the UEQM field above can be configured as 1 bit of MBS or LSB among the 4 bits of the NSS field of 11be. For example, the bit allocated for the UEQM field can be defined as B16 or B19. For example, if the UEQM field is set to 1 above, the NSS field is configured as shown in Table 14 above to indicate information about Nss and modulation transmitted by SS according to UEQM.

[0285] The operation of the receiving STA may be as follows. For example, when transmitting a signal using UEQM, the receiving STA can identify UEQM transmission information through the UEQM field, MCS field, and NSS field included in the received PPDU. For example, the receiving STA can recognize that the received PPDU was transmitted using UEQM through the setting of the UEQM field. In this case, for example, the receiving STA that recognizes that the UEQM field is set to 1 and that it is UEQM transmission can identify information about the MCS for the 1st stream during beamforming / MIMO transmission or the code rate and modulation (i.e. M) used in UEQM through the MCS field. For example, based on the identified MCS or M information and the information about the number of SS (spatial streams) and the corresponding modulation setting through the NSS field, the STA identifies the MCS or code rate and modulation order used for each received stream and decodes the received signal. For example, if UEQM is not applied (or the UEQM field is set to 0), EQM is applied, and in this case, the NSS field can indicate the number of SS (spatial streams) used for transmission as before.

[0286] Option 1 of Technical Feature 2.1.5 described above can be further modified as follows. The following modification can be indicated as Option 1-1. Specifically, Option 1-1 of Technical Feature 2.1.5 described below indicates UEQM using the Nss field, but is an example where UEQM indication is possible without configuring a separate field.

[0287] For example, when the value of the PHY identifier of the U-SIG included in the UHR PPDU is set to a non-0 value, for example, set to 1, the Nss of the User field for non-MU-MIMO transmission of the UHR-SIG is defined as follows. For example, the NSS field of the user field of the UHR-SIG is configured with 4 bits, the same as the NSS field defined in the user field of the EHT-SIG field. At this time, the NSS field is configured with B16 to B19, and when EQM is applied, values ​​0 to 7 are used to indicate Nss, and the remaining values ​​are reserved. Conversely, when UEQM is applied, values ​​8 to 15 of the Nss field can be used to indicate that UEQM is applied. For example, the value of the above can be indicated by setting B16 or B19 to 1. Therefore, when B16 or B19, which is the MSB or LSB of the Nss field, is 1, the application of UEQM can be indicated. For example, if the value of the NSS field is 8 or more, information about the UEQM configuration / pattern can be indicated simultaneously with the application of UEQM, and can be configured as in Table 15.

[0288] Value of NSS fieldcontent0~7Reserved8Nss=2, 1 st ss = M, 2 nd ss = M-19Nss=2, 1 st ss = M, 2 nd ss = M-210Nss=3, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-111Nss=3, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-212Nss=3, 1 st ss = M, 2nd ss = M-1, 3 rd ss = M-213Nss=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-114Nss=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-215Nss=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-1, 4 th ss = M-2

[0289] Options 1 and 1-1 of Technical Feature 2.1.5 described above may be further modified as follows. The following modifications may be indicated as Options 1-2 of Technical Feature 2.1.5.

[0290] In the following example, when UEQM application is indicated through the UEQM (indication) field, the user field of the UHR-SIG field may be configured to include the UEQM configuration field. For example, since the UEQM configuration field includes information on NSS and UEQM patterns, the user field of the UHR-SIG may not include the NSS field. For example, the UEQM configuration field may be configured with 3 / 4 bits as suggested above and may include information on modulation order for each SS in NSS. For example, the UEQM configuration field may be configured with NSS and modulation order applied for each SS according to value as suggested in the 3-bit configuration above.

[0291] The above-described technical feature 2.1.5 can be further modified as follows. The following modifications can be indicated as Option 2 of technical feature 2.1.5. Option 2 can transmit information about the UEQM pattern via the MCS field.

[0292] For example, when UEQM transmission is indicated through the UEQM (indication) field included in the U-SIG or UHR-SIG field (UEQM = 1), information about modulation transmitted per SS during UEQM transmission can be transmitted through the MCS field. At this time, the information about the MCS field can be configured with different information depending on whether UEQM is set. For example, in the case of non-UEQM transmission (i.e., when UEQM = 0), the MCS field is used to indicate MCS including newly added MCS as defined above. For example, in the case of UEQM transmission (i.e., when UEQM = 1), the MCS field can be configured with information including information about modulation applied per SS using UEQM to indicate the corresponding information. At this time, the information constituting the MCS field can be configured differently depending on Nss, and for example, can be configured as follows depending on Nss. For example, when UEQM is applied, the modulation order applied to the first SS may be limited to 16QAM or more and 1024QAM or less.

[0293] Table 16 relates to the case where NSS=2.

[0294] MCS indexcontents0R=1 / 2 stream1 =16QAM, stream2= QPSK1R=1 / 2 stream1 =16QAM, stream2= BPSK2R=2 / 3 stream1 =16QAM, stream2= QPSK3R=2 / 3 stream1 =64QAM, stream2= 16QAM4R=2 / 3 stream1 =256QAM, stream2= 64QAM5R=2 / 3 stream1 =64QAM, stream2= QPSK6R=2 / 3 stream1 =256QAM, stream2= 16QAM7R=3 / 4 stream1 =16QAM, stream2= QPSK8R=3 / 4 stream1 =64QAM, stream2= 16QAM9R=3 / 4 stream1 =256QAM, stream2= 64QAM10R=3 / 4 stream1 =1024QAM, stream2= 256QAM11R=3 / 4 stream1 =64QAM, stream2= QPSK12R=3 / 4 stream1 =256QAM, stream2= 16QAM13R=3 / 4 stream1 =1024QAM, stream2= 64QAM14R=5 / 6 stream1 =64QAM, stream2= 16QAM15R=5 / 6 stream1 =256QAM, stream2= 64QAM16R=5 / 6 stream1 =1024QAM, stream2= 256QAM17R=5 / 6 stream1 =256QAM, stream2= 16QAM18R=5 / 6 stream1 =1024QAM, stream2= 64QAM

[0295] 표 17은 NSS=3인 경우에 관련된다.

[0296] MCS indexcontents0R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= QPSK1R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= BPSK2R=2 / 3 stream1 =16QAM, stream2 =16QAM, stream3= QPSK3R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3= 16QAM4R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3= 64QAM5R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3= QPSK6R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3= 16QAM7R=2 / 3 stream1 =64QAM, stream2 =16QAM, stream3= QPSK8R=2 / 3 stream1 =256QAM, stream2 =64QAM, stream3= 16QAM9R=3 / 4 stream1 =16QAM, stream2 =16QAM, stream3= QPSK10R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3= 16QAM11R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3= 64QAM12R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3= 256QAM13R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3= QPSK14R=3 / 4 stream1 =256QAM, stream2 =256QAM,stream3= 16QAM15R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3= 64QAM16R=3 / 4 stream1 =64QAM, stream2 =16QAM, stream3= QPSK17R=3 / 4 stream1 =256QAM, stream2 =64QAM,stream3= 16QAM18R=3 / 4 stream1 =1024QAM, stream2 =256QAM, stream3= 64QAM19R=5 / 6 stream1 =64QAM, stream2 =64QAM, stream3= 16QAM20R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3= 64QAM21R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3= 256QAM22R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3= 16QAM23R=5 / 6 stream1 =1024QAM, stream2 =1024QAMstream3= 64QAM24R=5 / 6 stream1 =256QAM, stream2 =64QAM, stream3= 16QAM25R=5 / 6 stream1 =1024QAM, stream2 =256QAMstream3= 64QAM,

[0297] 표 18은 NSS=4인 경우에 관련된다.

[0298] MCS indexcontents0R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= 16QAM, stream4= QPSK1R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= 16QAM, stream4= BPSK2R=2 / 3 stream1 =16QAM, stream2 =16QAM, stream3 =16QAM, stream4= QPSK3R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM, stream4= 16QAM4R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 64QAM5R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM,stream4= QPSK6R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 16QAM7R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3 =16QAM, stream4= QPSK8R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3 =64QAM, stream4= 16QAM9R=3 / 4 stream1 =16QAM, stream2 =16QAM, stream3 =16QAM, stream4= QPSK10R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM, stream4= 16QAM11R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 64QAM12R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 256QAM13R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM,stream4= QPSK14R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 16QAM15R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 64QAM16R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3 =16QAM, stream4= QPSK17R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3 =64QAM,stream4= 16QAM18R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3 =256QAM, stream4= 64QAM19R=5 / 6 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM, stream4= 16QAM20R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 64QAM21R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 256QAM22R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 16QAM23R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 64QAM24R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3 =64QAM, stream4= 16QAM25R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3 =256QAM, stream4= 64QAM,

[0299] 기술적 특징 2.2 - Trigger frame을 통한 indication

[0300] Hereinafter, an example related to a UEQM technique based on a Trigger frame related to UL-MU communication and / or TB-PPDU is described. For example, the Trigger frame may include a common info field, a special user info field, a user info field (e.g., HE variant user info field, EHT variant user info field, UHR variant user info field), etc. In addition, the user info field may include various fields such as a trigger dependent user info field. The following example relates to an example of information related to UEQM included in the various fields described above.

[0301] For example, for UL MIMO / beamforming transmission, an indication of UEQM application can be indicated for each STA through the user (info) field of the Trigger frame. For example, the user (info) field can be composed of 6 bytes, excluding the size of the trigger dependent user info field, and can include UEQM indication information.

[0302] For example, information about the size of the user info field may be related to the value of the PHY identifier of the special user info field. For example, if the PHY identifier value of the special user info field is set to a non-zero value (e.g., a natural number greater than or equal to 1 or 2), the user info field excluding the size of the trigger dependent user info field may be configured with 6 bytes. In other words, it may be identified that the size of the user info field is 6 bytes based on the PHY identifier value.

[0303] Below, various examples of UEQM indication fields / information are proposed. The UEQM indication field may be called by various names such as UEQM control field, UEQM control info field, UEQM info field, etc.

[0304] For example, the UEQM (indication) field may have the following technical characteristics. For example, the UEQM (indication) field may include information regarding whether UEQM is applied. For example, the UEQM (indication) field may be composed of 1 bit, and a first value (e.g., 1) of the 1 bit indicates that a signal is transmitted using UEQM, and a second value (e.g., 0) of the 1 bit indicates that a signal is transmitted using EQM (i.e., UEQM is not set). In other words, the UEQM (indication) field may include information regarding whether UEQM (or EQM) is applied to a UL PPDU (e.g., TB PPDU) related to the Trigger frame.

[0305] Below, an example related to the UEQM configuration field is described. The UEQM configuration field may be called by various names such as configuration field, UEQM (modulation) patterns field, UEQM (modulation) patterns control field, etc.

[0306] The above UEQM configuration field indicates configuration information for modulation applied to each SS when UEQM is applied, and may have a length of 2 or 3 bits.

[0307] For example, Table 19 relates to the case where the UEQM configuration field has a length of 2 bits and Nss is 2. For example, the technical features related to Table 2 described above can be applied directly to Tables 19 to 21 below. In other words, M shown in Tables 19 to 21 is determined based on the modulation (i.e., constellation mapping) indicated by the MCS field (e.g., a field with a length of 5 bits) included in the user info field of the Trigger frame. For example, when 64QAM-3 / 4 is indicated by the information / field related to MCS included in the user info field of the Trigger frame, M in the present specification may mean 64QAM. In this case, M-1 may mean a modulation (i.e., constellation mapping) that is one level lower than M. For example, if M is 64QAM, M-1 can mean 16QAM, M-2 can mean QPSK, and M-3 can mean BPSK. Additionally, in general, M can be defined as a specific modulation level (e.g., 16QAM). For example, if M is 4096QAM, M-1 can mean 1024QAM, M-2 can mean 256QAM, M-3 can mean 64QAM, M-4 can mean 16QAM, M-5 can mean QPSK, and M-6 can mean BPSK. For example, if M is 1024QAM, M-1 can mean 256QAM, M-2 can mean 64QAM, M-3 can mean 16QAM, M-4 can mean QPSK, and M-5 can mean BPSK. For example, if M is 256QAM, M-1 can mean 64QAM, M-2 can mean 16QAM, M-3 can mean QPSK, and M-4 can mean BPSK. For example, if M is 16QAM, M-1 can mean QPSK, and M-2 can mean BPSK. For example, if M is QPSK, M-1 can mean BPSK.

[0308] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss2ss0MM-11MM-22~3Reserved

[0309] For example, Table 20 relates to the case where the UEQM configuration field has a length of 2 bits and Nss is 3.

[0310] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss3 rd SS3ss0MMM-11MMM-22MM-1M-23Reserved

[0311] For example, Table 21 relates to the case where the UEQM configuration field has a length of 2 bits and Nss is 4.

[0312] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss3rd ss4th ss4ss0MMMM-11MMMM-22MMM-1M-23Reserved

[0313] Additionally or alternatively, the modulation and code rate for the first SS (specifically, the 1st ss) described in Tables 19 to 21 may be omitted since they are indicated through the MCS field (e.g., 5-bit information in the user info field).

[0314] An example in Table 22 below is an example in which the length of the UEQM configuration field is 3 bits.

[0315] The 3-bit information in Table 22 below can include all information on modulation application when applying UEQM according to Nss, as follows.

[0316] Value of unequal Modulation configuration fieldContents01 st ss = M, 2 nd ss = M-111 st ss = M, 2 nd ss = M-221 st ss = M, 2 nd ss = M, 3 rd ss = M-131 st ss = M, 2 nd ss = M, 3 rd ss = M-241 st ss = M, 2 nd ss = M-1, 3 rd ss = M-251 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-161 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-271 st ss = M, 2 nd ss = M, 3 rd ss = M-1, 4 th ss = M-2

[0317] Additionally or alternatively, the modulation and code rate for the first SS (specifically, the 1st ss) described in Table 22 may be omitted since they are indicated through the MCS field (e.g., 5 bits of information in the user info field).

[0318] For example, the above 2-bit or 3-bit long UEQM configuration field is an example and may be defined as another field. Additionally, alternatively, the UEQM configuration field may be reserved when the UEQM (indication) field is set to a second value (e.g., 0) (e.g., when UEQM is not applied).

[0319] Figures 19 and 20 are examples of user info fields proposed in the present specification. The illustrated user info fields may be included in the trigger frame. The above-described 1-bit long UEQM (indication) field and / or the 2- or 3-bit long UEQM configuration field are included in Figures 19 and / or 20. For example, as illustrated in Figures 19 / 20, the above-described 1-bit long UEQM (indication) field and / or the 2- or 3-bit long UEQM configuration field may be continuous with each other, and the UEQM (indication) field may be continuous with the PS160 field in the user info field. For example, the user info field may be composed of a combination of 4-bit MCS bits and 1-bit extension bit (e.g., 4-bit MCS bits and 1-bit MCS extension bit as described in Technical Feature 1 or Table 3), or may be composed of 5-bit MCS bits (e.g., 5-bit MCS bits as described in Technical Feature 1 or Table 4).

[0320] For example, the reserved bits (e.g., 1 consecutive bit in the UEQM configuration field) illustrated in FIG. 19 / 20 can be used to indicate a new feature newly defined in 11bn or next wi-fi.

[0321] For example, in addition to or alternatively to the features described in FIGS. 19 / 20, a bit (e.g., bit 25) that was reserved in the user info field can be used to indicate UEQM. Additionally or alternatively, the UEQM (indication) field can be positioned after or consecutively to the MCS field of FIGS. 19 / 20. This allows for early indication of UEQM. In this case, for indication of an extended MCS set, the MCS extension bit (e.g., the 1-bit MCS extension bit of FIG. 19) can be positioned after or consecutively to the PS 160 field illustrated in FIG. 19. In addition, when the UEQM (indication) field is set to the first value (e.g., 1), the STA can recognize that UEQM configuration information exists.

[0322] Technical Features 2.2.1

[0323] The following example is an example of modifying the example of FIG. 19 and / or FIG. 20. The 6-bit long SS allocation field / information illustrated in FIG. 19 / 20 can be modified in various ways as follows. For example, based on the SS allocation field / information proposed below, information about the modulation applied to each SS when UEQM is applied can be indicated. For example, whether UEQM is applied can be indicated by the UEQM (indication) field included in the user (info) field. For example, when UEQM is applied (e.g., when UEQM (indication) field = 1), the content of the 6-bit SS allocation field can be reconfigured.

[0324] Figure 21 illustrates an example of the SS allocation field proposed in this specification. As illustrated, for example, a 3-bit Starting SS (spatial stream) bit / information and a 3-bit Number Of SSs and modulation configuration bit / information may be configured. The specific names of the 3-bit information / bits may vary.

[0325] The first 3-bit information of FIG. 21 (e.g., Starting SS information) may include information about the SS (spatial stream) from which the SS (spatial stream) allocated to the STA starts.

[0326] The second 3-bit information of FIG. 21 (e.g., Number of SSs and modulation configuration information) may include configuration information on the NSS allocated to the STA and modulation per SS. A specific example of the second 3-bit information of FIG. 21 may be as shown in Table 23 below.

[0327] Value of Number Of Spatial Streams and modulation configurationContents0NSS=2, 1 st ss = M, 2 nd ss = M-11NSS=2, 1 st ss = M, 2 nd ss = M-22NSS=3, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-13NSS=3, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-24NSS=3, 1 st ss = M, 2 nd ss = M-1, 3 rd ss = M-25NSS=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-16NSS=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M, 4 th ss = M-27NSS=4, 1 st ss = M, 2 nd ss = M, 3 rd ss = M-1, 4 th ss = M-2

[0328] The above example can be further modified. For example, unlike indicating information about modulation by SS during UEQM using the SS allocation field / information, information about modulation and code rate by SS during UEQM transmission can be indicated using the MCS field. For example, when the UEQM (indication) field included in the trigger frame is set to the first value (e.g., 1) to solicit UEQM transmission, the MCS field can be configured differently according to the NSS as suggested in option 2 (e.g., examples of Tables 16 and 17). Specifically, the NSS allocated to the STA is indicated through the SS allocation field. In this case, for example, the MCS field can be configured with different contents according to the NSS value of the SS allocation field during UEQM. For example, an example of the configuration of the MCS field configured individually for each NSS is as follows.

[0329] For example, an example of the MCS field configured when Nss = 2 may be as shown in Table 24 below.

[0330] MCS indexcontents0R=1 / 2 stream1 =16QAM, stream2= QPSK1R=1 / 2 stream1 =16QAM, stream2= BPSK2R=2 / 3 stream1 =16QAM, stream2= QPSK3R=2 / 3 stream1 =64QAM, stream2= 16QAM4R=2 / 3 stream1 =256QAM, stream2= 64QAM5R=2 / 3 stream1 =64QAM, stream2= QPSK6R=2 / 3 stream1 =256QAM, stream2= 16QAM7R=3 / 4 stream1 =16QAM, stream2= QPSK8R=3 / 4 stream1 =64QAM, stream2= 16QAM9R=3 / 4 stream1 =256QAM, stream2= 64QAM10R=3 / 4 stream1 =1024QAM, stream2= 256QAM11R=3 / 4 stream1 =64QAM, stream2= QPSK12R=3 / 4 stream1 =256QAM, stream2= 16QAM13R=3 / 4 stream1 =1024QAM, stream2= 64QAM14R=5 / 6 stream1 =64QAM, stream2= 16QAM15R=5 / 6 stream1 =256QAM, stream2= 64QAM16R=5 / 6 stream1 =1024QAM, stream2= 256QAM17R=5 / 6 stream1 =256QAM, stream2= 16QAM18R=5 / 6 stream1 =1024QAM, stream2= 64QAM

[0331] 예를 들어, Nss =3 인 경우 구성되는 MCS 필드의 일례는 이하 표 25와 같을 수 있다.

[0332] MCS indexcontents0R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= QPSK1R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= BPSK2R=2 / 3 stream1 =16QAM, stream2 =16QAM, stream3= QPSK3R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3= 16QAM4R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3= 64QAM5R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3= QPSK6R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3= 16QAM7R=2 / 3 stream1 =64QAM, stream2 =16QAM, stream3= QPSK8R=2 / 3 stream1 =256QAM, stream2 =64QAM, stream3= 16QAM9R=3 / 4 stream1 =16QAM, stream2 =16QAM, stream3= QPSK10R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3= 16QAM11R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3= 64QAM12R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3= 256QAM13R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3= QPSK14R=3 / 4 stream1 =256QAM, stream2 =256QAM,stream3= 16QAM15R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3= 64QAM16R=3 / 4 stream1 =64QAM, stream2 =16QAM, stream3= QPSK17R=3 / 4 stream1 =256QAM, stream2 =64QAM,stream3= 16QAM18R=3 / 4 stream1 =1024QAM, stream2 =256QAM, stream3= 64QAM19R=5 / 6 stream1 =64QAM, stream2 =64QAM, stream3= 16QAM20R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3= 64QAM21R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3= 256QAM22R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3= 16QAM23R=5 / 6 stream1 =1024QAM, stream2 =1024QAMstream3= 64QAM24R=5 / 6 stream1 =256QAM, stream2 =64QAM, stream3= 16QAM25R=5 / 6 stream1 =1024QAM, stream2 =256QAMstream3=64QAM,

[0333] For example, an example of the MCS field configured when Nss = 4 may be as shown in Table 26 below.

[0334] MCS indexcontents0R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= 16QAM, stream4= QPSK1R=1 / 2 stream1 =16QAM, stream2 =16QAM, stream3= 16QAM, stream4= BPSK2R=2 / 3 stream1 =16QAM, stream2 =16QAM, stream3 =16QAM, stream4= QPSK3R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM, stream4= 16QAM4R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 64QAM5R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM,stream4= QPSK6R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 16QAM7R=2 / 3 stream1 =64QAM, stream2 =64QAM, stream3 =16QAM, stream4= QPSK8R=2 / 3 stream1 =256QAM, stream2 =256QAM, stream3 =64QAM, stream4= 16QAM9R=3 / 4 stream1 =16QAM, stream2 =16QAM, stream3 =16QAM, stream4= QPSK10R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM, stream4= 16QAM11R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 64QAM12R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 256QAM13R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM,stream4= QPSK14R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 16QAM15R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 64QAM16R=3 / 4 stream1 =64QAM, stream2 =64QAM, stream3 =16QAM, stream4= QPSK17R=3 / 4 stream1 =256QAM, stream2 =256QAM, stream3 =64QAM,stream4= 16QAM18R=3 / 4 stream1 =1024QAM, stream2 =1024QAM, stream3 =256QAM, stream4= 64QAM19R=5 / 6 stream1 =64QAM, stream2 =64QAM, stream3 =64QAM, stream4= 16QAM20R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 64QAM21R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 256QAM22R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3 =256QAM, stream4= 16QAM23R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3 =1024QAM, stream4= 64QAM24R=5 / 6 stream1 =256QAM, stream2 =256QAM, stream3 =64QAM, stream4= 16QAM25R=5 / 6 stream1 =1024QAM, stream2 =1024QAM, stream3 =256QAM, stream4= 64QAM,

[0335] 기술적 특징 2.3

[0336] The following example is an example in which the UEQM indication field / information and the UEQM configuration field / information described in Technical Feature 2.2 are included in the Trigger Dependent User Info. Specifically, in the above-described Technical Feature 2.2, the UEQM indication field / information and the UEQM configuration field / information are included in the user info field (e.g., HE variant user info field, EHT variant user info field, UHR variant user info field) rather than the Trigger Dependent User Info. The following example describes an example in which the UEQM indication field / information and the UEQM configuration field / information are included in the Trigger Dependent User Info included in the user info field.

[0337] Additionally or alternatively, if the value of the PHY version identifier in the Special user info field of the Trigger frame is 1 or greater, the user field of the trigger frame may include the following Trigger Dependent User Info field. In this case, the Trigger Dependent User Info field may include the above-described UEQM indication field and / or UEQM configuration field.

[0338] For example, the UEQM information (e.g., UEQM indication field and / or UEQM configuration field) included in the Trigger Dependent User Info field may be configured and included identically to the information included in the user field of the defined trigger frame (e.g., the user info field illustrated in FIG. 19 / 20 or the user info field described in Technical Feature 2.2).

[0339] Figure 22 shows an example of a Trigger Dependent User Info field containing UEQM information.

[0340] For example, when transmitting and receiving a UL signal, the AP uses the information included in the user info field of the trigger frame to instruct the STA to transmit a signal using UEQM in order to transmit and receive a signal. At this time, the STA can determine, based on the information of the trigger frame transmitted to it, whether UEQM is applied for PPDU (e.g., TB-PPDU) transmission performed by the STA in the future and information about the modulation applied to each SS. An example of the STA's behavior in this regard is as follows.

[0341] For example, when an AP transmits UL MIMO to an STA using two SSs, the information in the user info field of the trigger frame soliciting signal transmission (e.g., transmission of TB-PPDU) using UEQM may be as follows.

[0342] Nss= 2, MCS = 5, UEQM (indication)= 1, UEQM configuration (e.g. 2 bit) = 0

[0343] An STA that receives the above information through the user info field of the Trigger frame recognizes that a signal is transmitted using UEQM through the UEQM (indication) field of the user info field. In addition, it recognizes that the allocated Nss is 2SS through SS allocation, and confirms that the MCS to be applied to the first SS (1st SS) is 64QAM (2 / 3 rate) through the MCS field. In addition, it can know that the modulation to be applied to the second SS (2ss) is 16QAM (2 / 3) through the indication of the UEQM configuration field (value 0 indicates that M is allocated for the 1st SS and M-1 is allocated for the 2nd SS). The STA that confirms the information on the modulation applied to each SS as described above configures a PPDU using the above information and transmits a signal to the AP.

[0344] Technical Features 2.4

[0345] The following examples relate to various information related to UEQM included in the trigger frame. In the examples below, MCS field / information, UEQM (indication) field information, and UEQM configuration field / information related to UEQM can be transmitted through the user (info) field of the trigger frame. For example, in the examples below, the same size as the user field of the conventional 11be trigger frame can be used.

[0346] For example, the user (info) field of the trigger frame may include an MCS field / information. The MCS field / information may include at least four new MCS parameters / indices added (e.g., MCS parameters / indices related to QPSK-2 / 3, 16QAM-2 / 3, 16QAM-5 / 6, 256QAM-2 / 3). For example, the MCS field / information may have a length of 5 bits.

[0347] Additionally or alternatively, the user (info) field of the trigger frame may include a UEQM (indication) field / information. The UEQM (indication) field / information is used to indicate whether UEQM is present and may consist of 1 bit. For example, a first value of the 1 bit (e.g., 0) may be related to EQM, and a second value of the 1 bit (e.g., 1) may be related to UEQM.

[0348] Additionally or alternatively, the user (info) field of the trigger frame may include a UEQM configuration field / information. For example, the UEQM configuration field / information may be composed of 2 bits to indicate a modulation order for UEQM. For example, the UEQM configuration field / information may be composed as in Table 27 for Nss=2.

[0349] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss2ss0MM-11MM-22~3Reserved

[0350] For example, the UEQM configuration field / information can be configured as in Table 27 for Nss=3.

[0351] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss3 rd SS3ss0MMM-11MMM-22MM-1M-23Reserved

[0352] For example, the UEQM configuration field / information can be configured as in Table 27 for Nss=4.

[0353] Total NssValue of unequal Modulation configuration fieldContents1st ss2nd ss3rd ss4th ss4ss0MMMM-11MMMM-22MMM-1M-23Reserved

[0354] Technical Features 2.4.1

[0355] The following example proposes an additional example regarding the user info field of the trigger frame. In the following example, in order to indicate the above information while maintaining the same size as the user field of the existing trigger frame (i.e. 11ax / 11be), the user info field of the trigger frame of a UHR system (e.g., IEEE 802.11bn system) can be configured as follows.

[0356] For example, the MCS field included in the user info field may be expanded from 4 bits to 5 bits. In this case, the 1 bit required for the expansion may be defined using B15, which is reserved in the user field. For example, the UEQM (indication) field / information and the UEQM configuration field / information may be configured in a way that reconstructs the SS Allocation field (e.g., 6 bits).

[0357] Figure 23 shows an example of the SS Allocation field proposed below.

[0358] For example, in the UHR system, Max Nss is considered to be 8. Accordingly, as shown in Fig. 23, the 4 bits (B0-B3) previously allocated to indicate the starting SS (spatial stream) can be reconfigured into 3 bits. In this case, 1 bit of MSB / LSB can be defined as the UEQM indication field. For example, considering the bit sequence decoding order, B3 can be defined as the UEQM indication within the 6-bit SS allocation.

[0359] As described above, B0 or ​​B3 can be defined as a UEQM indication field, and for example, when the UEQM indication field is set to the first value (e.g., 1) to indicate UEQM transmission, the remaining 3 bits can be defined as follows. For example, when the UEQM indication field is set to the second value (e.g., 0), the remaining 3 bits (e.g., B0-B2 or B1-B3 in bit 6 of FIG. 23) can include information about the Starting SS (spatial stream) of the STA in the same manner as before.

[0360] For example, when the UEQM indication field is set to the first value (e.g., 1), the remaining 3 bits can be configured as follows. For example, the value of Starting SS (spatial stream) is always set to 0 if it is not MU-MIMO transmission. And since UEQM is not applied in MU-MIMO, the above information can always be fixed to 0 in UEQM, so it can be omitted because it is eventually always set to a fixed value in UEQM. Therefore, it can be reconstructed as follows. For example, 2 bits out of 3 bits can be used to indicate the UEQM configuration field / information. For example, the UEQM configuration information (e.g., Tables 27 to 29) can be configured using B0-B1 or B1-B2. The remaining 1 bit ( B0 or ​​B2 ) can be used for other feature indications of next or UHR.

[0361] Additionally, since only LDPC coding is used for UEQM transmission, the UL FEC coding type field can be reserved or used to indicate other features.

[0362] Figure 24 is an example of a user info field configured based on the above-described content.

[0363] For example, in the example of Fig. 24, an indication for 2x LDPC can be considered, and at this time, the indication for 2x LDPC can be indicated using a reserved 1 bit. For example, the UL FEC coding type in UEQM can be reserved or always set to 1.

[0364] For example, when configuring a trigger frame related to a UHR system, the contents or fields included in the user field may be configured differently depending on the UEQM. Accordingly, to provide early indication of configuration differences for the user field, the user field may be reconfigured as shown in Fig. 25.

[0365] Figure 25 is another example of a user info field configured based on the above-described content.

[0366] In the example of FIG. 25, when the UEQM (indication field) is set to a first value (e.g., 1) to indicate UEQM transmission, the UL FEC coding type field and the 1-bit long reserved field / information of FIG. 25 can be used to indicate other information. For example, the UL FEC coding type field and / or the 1-bit long reserved field / information can be used to indicate 2x LDPC and / or Distributed BW, etc.

[0367] Figure 26 shows an example of a user field proposed in this specification.

[0368] An example of FIG. 26 is an example that combines the contents described in Technical Feature 1.1, Table 4, Technical Feature 2.1.2, Tables 8 to 10, and Technical Feature 2.1.3 described above. Each feature illustrated in FIG. 26 does not necessarily need to be implemented simultaneously, and some fields in FIG. 26 may be omitted.

[0369] This specification relates to a signal (SIG) field including a user field. For example, the SIG field may be called by various names such as UHR / EHT / first / second SIG field. For example, the SIG field may be included in a physical protocol data unit (PPDU) of various PHY versions, and may be included in the PPDU illustrated in FIG. 5, for example. For example, the PPDU may further include a universal (U-SIG) field. For example, as illustrated in FIG. 5, the signal (SIG) field (e.g., UHR-SIG field) may be continuous with the U-SIG field. For example, the signal (SIG) field (e.g., UHR-SIG field) may include additional control information for interpreting the PPDU (or data field or RU). For example, the signal (SIG) field (e.g., UHR-SIG field) may include a common field and a user specific field. For example, the user specific field may include one or two user fields.

[0370] Additionally or alternatively, a user specific field may include one or two user fields of FIG. 26.

[0371] Additionally or alternatively, the user field of the present specification may be a non-MU-MIMO (multi-user multiple input multiple output) user field.

[0372] Additionally or alternatively, the user field of the present specification may include a 1-bit long unequal modulation (UEQM) information field, and a 2-bit long UEQM pattern field consecutive to the UEQM information field. Additionally or alternatively, the UEQM information field may include information related to whether UEQM is applied. In other words, information regarding whether UEQM is applied / supported to a PPDU including the UEQM information field (e.g., an (UHR) PPDU transmitted to a non-AP STA via DL) may be included in the UEQM information field. In other words, the UEQM information field may include information regarding whether UEQM is applied over a different spatial stream. In other words, the UEQM information field may include information regarding whether UEQM is applied over a plurality of spatial streams (or two, three, or four spatial streams) related to a SIG including the user field (or a PPDU including the user field, or a Data field related to the user field, or a Resource Unit related to the user field). In other words, the UEQM information field may include information regarding whether UEQM is applied over a plurality of spatial streams (or two, three, or four spatial streams) applied to a Data field decoded / interpreted based on the user field. Additionally or alternatively, the UEQM information field may have a first value based on whether UEQM is applied over different spatial streams.

[0373] Additionally or alternatively, the UEQM pattern field may include information related to a UEQM pattern applied to at least two spatial streams. In other words, the information related to the UEQM pattern may express information related to a UEQM pattern applied to at least two (e.g., at least one of two to four) or more than two (e.g., at least one of two to four) spatial streams. For example, the UEQM information field may be identical to the UEQM indication field described above (e.g., the UEQM indication field described in Technical Feature 2.1.1, Technical Feature 2.1.3, etc.). For example, the UEQM pattern field may be the same as the UEQM configuration field described above (e.g., the UEQM configuration field described in Technical Feature 2.1.2, Technical Feature 2.1.3, etc.). Additionally or alternatively, the user field of the present specification may further include an STA (station) ID field having a length of 11 bits, and an MCS field that is continuous to the STA ID field and has a length of 5 bits. Specifically, the user field of the present specification may include an STA-ID field having a length of 11 bits and an MCS field having a length of 5 bits, as illustrated in FIG. 26.

[0374] Additionally or alternatively, the UEQM pattern field may include information related to constellation indices applied to two spatial streams. For example, based on the value of the UEQM pattern field being 0, the constellation index related to the first spatial stream may be M, and the constellation index related to the second spatial stream may be M-1. For example, based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream may be M, and the constellation index related to the second spatial stream may be M-2. In other words, the UEQM pattern field may be configured based on the technique of Table 8 described above.

[0375] Additionally or alternatively, the UEQM pattern field may include information related to constellation indices applied to three spatial streams. For example, based on the value of the UEQM pattern field being 0, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, and the constellation index related to the third spatial stream may be M-1. For example, based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, and the constellation index related to the third spatial stream may be M-2. For example, based on the value of the UEQM pattern field being 2, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M-1, and the constellation index related to the third spatial stream may be M-2. In other words, the UEQM pattern field may be configured based on the technique of Table 9 described above.

[0376] Additionally or alternatively, the UEQM pattern field may include information related to constellation indices applied to four spatial streams. For example, based on the value of the UEQM pattern field being 0, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M, and the constellation index related to the fourth spatial stream may be M-1. For example, based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M, and the constellation index related to the fourth spatial stream may be M-2. For example, based on the value of the UEQM pattern field being (2), the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M-1, and the constellation index related to the fourth spatial stream may be M-2. In other words, the UEQM pattern field may be configured based on the technique of Table 10 described above.

[0377] With respect to the UEQM pattern field, M is a constellation index related to the MCS field, M-1 may be a constellation that is one order lower than M, and M-2 may be a constellation that is two orders lower than M. For example, if M is 4096QAM, M-1 may mean 1024QAM and M-2 may mean 256QAM. For example, if M is 1024QAM, M-1 may mean 256QAM and M-2 may mean 64QAM. For example, if M is 256QAM, M-1 may mean 64QAM and M-2 may mean 16QAM. For example, M may mean 16QAM, M-1 may mean QPSK, and M-2 may mean BPSK. For example, if M is QPSK, M-1 could mean BPSK.

[0378] Additionally or alternatively, the user field of the present specification may further include a 3-bit long NSS field (e.g., B16 to B18 of FIG. 26) consecutive to the MCS field, wherein the NSS field may include information regarding the number of spatial streams. Additionally or alternatively, the UEQM information field (e.g., B19 of FIG. 26) may be consecutive to the NSS field (e.g., B16 to B18 of FIG. 26).

[0379] Additionally or alternatively, the STA ID field may be included in B0 to B10 of the user field, the MCS field may be included in B11 to B15 of the user field, the NSS field may be included in B16 to B18 of the user field, the UEQM information field may be included in B19 of the user field, and the UEQM pattern field may be included in B20 to B21 of the user field.

[0380] Additionally or alternatively, when the UEQM information field (e.g., B19 of FIG. 26) is set to a first value (e.g., 1), the user field may include a 2-bit long UEQM pattern field (e.g., B20 and B21 of FIG. 26) consecutive to the UEQM information field.

[0381] Additionally or alternatively, when the UEQM information field (e.g., B19 of FIG. 26) is set to the second value (e.g., 0), the user field may not include a 2-bit long UEQM pattern field (e.g., B20 and B21 of FIG. 26), but may include a 1-bit long Beamformed field (e.g., B20 of FIG. 26) and a 1-bit long coding field (e.g., B21 of FIG. 26). In other words, the user field of the present specification may exclude a 1-bit long Beamformed field (e.g., B20 of FIG. 26) and a 1-bit long coding field (e.g., B21 of FIG. 26) from the user field based on the UEQM information field (e.g., B19 of FIG. 26) having the first value (e.g., 1).

[0382] For example, the Beamformed field may include information regarding whether a beamforming steering matrix is ​​applied. For example, the coding field may include information regarding whether a binary convolutional code (BCC) or a low density parity check (LDPC) is applied to a data field (or resource unit) related to the user field.

[0383] Figure 27 is an example of a procedure flowchart related to this specification. The illustrated procedure may be performed by an Access Point (AP), a non-AP, an AP Multi-link Device (AP MLD), or a non-AP MLD.

[0384] As illustrated, a SIG field may be generated according to step S2710. In other words, the SIG field may be encoded / defined / set / configured according to an example of the present specification.

[0385] Since the SIG field associated with step S2710 can be included in various PPDUs, step S2710 can also be expressed as a step of generating / encoding / define / setting / configuring a PPDU (or preamble or UHR preamble) containing the corresponding SIG field.

[0386] The SIG field associated with step S2710 may be any one of the various SIG fields described above (e.g., the SIG field illustrated in FIG. 26). For example, the SIG field associated with step S2710 may be called by various names such as UHR / EHT / first / second SIG field. For example, the SIG field may be included in a PPDU (Physical Protocol Data Unit) of various PHY versions, for example, the PPDU illustrated in FIG. 5. For example, the PPDU may further include a U-SIG (Universal) field. For example, as illustrated in FIG. 5, the SIG (signal) field (e.g., UHR-SIG field) may be continuous with the U-SIG field. For example, the SIG (signal) field (e.g., UHR-SIG field) may include additional control information for interpreting the PPDU (or Data field or RU). For example, the SIG (signal) field (e.g., UHR-SIG field) may include a common field and a user specific field. For example, the user specific field may include one or two user fields.

[0387] Additionally or alternatively, the SIG field associated with step S2710 may include a user field as described in FIG. 26.

[0388] Additionally or alternatively, the SIG field associated with step S2710 may include at least one user field. For example, a user specific field may include one or two user fields associated with S2710.

[0389] Additionally or alternatively, the user field may include a 1-bit unequal modulation (UEQM) information field and a 2-bit UEQM pattern field. Additionally or alternatively, the UEQM pattern field may be continuous with the UEQM information field.

[0390] Additionally or alternatively, the UEQM information field may include information regarding whether UEQM is applied. In other words, information regarding whether UEQM is applied / supported to a PPDU including the UEQM information field (e.g., an (UHR) PPDU transmitted to a non-AP STA via DL) may be included in the UEQM information field. In other words, the UEQM information field may include information regarding whether UEQM is applied over a different spatial stream. In other words, the UEQM information field may include information regarding whether UEQM is applied over a plurality of spatial streams (or two, three, or four spatial streams) associated with a SIG including the user field (or a PPDU including the user field, or a Data field associated with the user field, or a Resource Unit associated with the user field). In other words, the UEQM information field may include information regarding whether UEQM is applied over multiple spatial streams (or two, three, or four spatial streams) that are applied to a Data field that is decoded / interpreted based on the user field. Additionally or alternatively, the UEQM information field may have a first value based on whether UEQM is applied over different spatial streams.

[0391] Additionally or alternatively, the UEQM pattern field may include information related to a UEQM pattern applied to at least two spatial streams. In other words, the information related to the UEQM pattern may express information related to a UEQM pattern applied to at least two (e.g., at least one of two to four) or more than two (e.g., at least one of two to four) spatial streams. For example, the UEQM information field may be identical to the UEQM indication field described above (e.g., the UEQM indication field described in Technical Feature 2.1.1, Technical Feature 2.1.3, etc.). For example, the UEQM pattern field may be identical to the UEQM configuration field described above (e.g., the UEQM configuration field described in Technical Feature 2.1.2, Technical Feature 2.1.3, etc.).

[0392] Additionally or alternatively, the SIG field or the user field may be included in a Physical Protocol Data Unit (PPDU). The PPDU may be a PPDU of various PHY versions, as described above, and may be, for example, a PPDU as illustrated in FIG. 5.

[0393] Additionally or alternatively, the user field related to step S2710 may further include an STA (station) ID field having an 11-bit length and an MCS field having a 5-bit length that is continuous with the STA ID field. Specifically, the user field related to step S2710 may include an STA-ID field having an 11-bit length and an MCS field having a 5-bit length, as illustrated in FIG. 26.

[0394] Additionally or alternatively, the UEQM pattern field may include information related to constellation indices applied to two spatial streams. For example, based on the value of the UEQM pattern field being 0, the constellation index related to the first spatial stream may be M, and the constellation index related to the second spatial stream may be M-1. For example, based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream may be M, and the constellation index related to the second spatial stream may be M-2. In other words, the UEQM pattern field may be configured based on the technique of Table 8 described above.

[0395] Additionally or alternatively, the UEQM pattern field may include information related to constellation indices applied to three spatial streams. For example, based on the value of the UEQM pattern field being 0, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, and the constellation index related to the third spatial stream may be M-1. For example, based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, and the constellation index related to the third spatial stream may be M-2. For example, based on the value of the UEQM pattern field being 2, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M-1, and the constellation index related to the third spatial stream may be M-2. In other words, the UEQM pattern field may be configured based on the technique of Table 9 described above.

[0396] Additionally or alternatively, the UEQM pattern field may include information related to constellation indices applied to four spatial streams. For example, based on the value of the UEQM pattern field being 0, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M, and the constellation index related to the fourth spatial stream may be M-1. For example, based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M, and the constellation index related to the fourth spatial stream may be M-2. For example, based on the value of the UEQM pattern field being (2), the constellation index related to the first spatial stream may be M, the constellation index related to the second spatial stream may be M, the constellation index related to the third spatial stream may be M-1, and the constellation index related to the fourth spatial stream may be M-2. In other words, the UEQM pattern field may be configured based on the technique of Table 10 described above.

[0397] With respect to the UEQM pattern field, M is a constellation index related to the MCS field, M-1 may be a constellation that is one order lower than M, and M-2 may be a constellation that is two orders lower than M. For example, if M is 4096QAM, M-1 may mean 1024QAM and M-2 may mean 256QAM. For example, if M is 1024QAM, M-1 may mean 256QAM and M-2 may mean 64QAM. For example, if M is 256QAM, M-1 may mean 64QAM and M-2 may mean 16QAM. For example, M may mean 16QAM, M-1 may mean QPSK, and M-2 may mean BPSK. For example, if M is QPSK, M-1 could mean BPSK.

[0398] Additionally or alternatively, the user field associated with step S2710 may further include a 3-bit long NSS field contiguous to the MCS field, wherein the NSS field may include information regarding the number of spatial streams.

[0399] Additionally or alternatively, the UEQM information field associated with step S2710 may be continuous with the NSS field.

[0400] Additionally or alternatively, the STA ID field may be included in B0 to B10 of the user field. Additionally or alternatively, the MCS field may be included in B11 to B15 of the user field. Additionally or alternatively, the NSS field may be included in B16 to B18 of the user field. Additionally or alternatively, the UEQM information field may be included in B19 of the user field. Additionally or alternatively, the UEQM pattern field may be included in B20 to B21 of the user field.

[0401] Additionally or alternatively, if the UEQM information field has a first value based on that UEQM is applied over a different spatial stream, the user field may exclude a 1-bit long Beamformed field and a 1-bit long coding field from the user field based on the UEQM information field having the first value. Specifically, as described in the example of FIG. 26, if the UEQM information field (e.g., B19 of FIG. 26) is set to a second value (e.g., 0), the user field may not include a 2-bit long UEQM pattern field (e.g., B20 and B21 of FIG. 26), but may include a 1-bit long Beamformed field (e.g., B20 of FIG. 26) and a 1-bit long coding field (e.g., B21 of FIG. 26).

[0402] Additionally or alternatively, the user field may be a non-MU-MIMO (multi-user multiple input multiple output) user field.

[0403] As illustrated, the SIG field may be transmitted according to step S2720.

[0404] Since the SIG field related to step S2720 can be included in various PPDUs, step S2720 can also be expressed as a step of transmitting / forwarding / sending a PPDU (or preamble or UHR preamble) containing the corresponding SIG field.

[0405] Figure 28 is an example of a procedure flowchart related to this specification. The illustrated procedure may be performed by an Access Point (AP), a non-AP, an AP Multi-link Device (MLD), or a non-AP MLD.

[0406] As illustrated, a SIG field may be received according to step S2810. For example, the SIG field may include at least one user field. For example, the SIG field or the user field of step S2810 may be identical to the SIG field or the user field described in step S2710 and / or FIG. 26.

[0407] Since the SIG field associated with step S2810 can be included in various PPDUs, step S2810 can also be expressed as a step of receiving a PPDU (or preamble or UHR preamble) containing the corresponding SIG field.

[0408] As illustrated, the PPDU may be interpreted based on the SIG field according to step S2820. For example, the process of performing step S2820 may include a process of interpreting / decoding the data field of the PPDU and a process of interpreting / decoding at least one RU (resource unit) included in the PPDU (or data field). Accordingly, step S2820 may be expressed as a process of interpreting / decoding the PPDU, the data field, and / or the RU based on the SIG field.

[0409] The technical features of the present disclosure may be implemented by various devices. The devices of the present disclosure may be the devices described in FIG. 1 / FIG. 14. The devices of the present disclosure may include at least one processor; and at least one computer memory operably connectable to the at least one processor, the computer memory storing instructions for performing operations based on execution by the at least one processor.

[0410] For example, the processor may be a processor described in FIG. 1 and / or FIG. 14. That is, as described above, the processor of the present specification may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). The processor may include not only computers having various architectures such as single / multiprocessor architecture, sequential (Von Neumann) / parallel architecture, but also specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices. For example, the processor of the present specification may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by INTEL®, or a processor that enhances the same.

[0411] For example, the instructions may refer to computer program instructions executed by the at least one processor. The (computer program) instructions provide logic and / or routines that enable the technical features of the present specification to be performed by the processor. The at least one processor can load and execute a computer program by reading the at least one memory.

[0412] The computer program(s) defined by the above instructions may be delivered to the device (e.g., STA) of the present specification via an appropriate delivery mechanism. The delivery mechanism may be, for example, a computer-readable storage medium, a computer program product, a memory device, a recording medium such as a CD-ROM or DVD, or a product tangibly embodying the computer program. The delivery mechanism may be a signal configured to reliably transmit the computer program via a wireless or electrical connection.

[0413] The above (computer program) instructions may include software or firmware for a programmable processor (e.g., programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device, etc.).

[0414] For example, the memory may be the memory described in FIG. 1 and / or FIG. 14. That is, as described above, the memory of the present specification may store control information related to the operation of the STA of the present specification or information about signals transmitted and received by the STA (e.g., PPDU including management / control / data frames).

[0415] The technical features of this specification may be implemented in at least one computer-readable recording medium (CRM). The CRM includes instructions that are executed by at least one processor as described above. The instructions stored in the CRM may be computer program instructions as described above.

[0416] The device of the present disclosure may further include a transceiver. The transceiver may be operably connectable to the memory / processor, etc. The transceiver may be the transceiver illustrated in FIG. 1 and / or FIG. 14.

[0417] The technical features of this specification described above are applicable to various applications and business models. For example, the technical features described above can be applied to wireless communication in devices that support artificial intelligence (AI).

[0418] Artificial intelligence (AI) is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0419] An artificial neural network (ANN) is a model used in machine learning. It can refer to a model with problem-solving capabilities, consisting of artificial neurons (nodes) formed by the connection of synapses to form a network. An ANN can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.

[0420] An artificial neural network may 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 may include synapses connecting neurons. In an artificial neural network, each neuron can output a function value of an activation function based on input signals, weights, and biases received through the synapses.

[0421] Model parameters are parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters are parameters that must be set before learning in machine learning algorithms, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0422] The goal of artificial neural network training can be seen as determining model parameters that minimize a loss function. The loss function can be used as an indicator for determining optimal model parameters during the artificial neural network training process.

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

[0424] Supervised learning refers to a method for training an artificial neural network when given labels for the training data. The labels can refer to the correct answer (or output value) that the artificial neural network must infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method for training an artificial neural network when the training data is not given labels. Reinforcement learning can refer to a learning method in which an agent defined within a given environment is trained to select actions or action sequences that maximize the cumulative reward in each state.

[0425] Machine learning implemented with a deep neural network (DNN) containing multiple hidden layers among artificial neural networks is also called deep learning, and deep learning is a subset of machine learning. Hereinafter, the term "machine learning" is used to encompass deep learning.

[0426] Additionally, the above-described technical features can be applied to wireless communication of robots.

[0427] A robot can be defined as a machine that automatically performs or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making independent judgments, and performing actions can be called an intelligent robot.

[0428] Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with actuators or motors, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots incorporate wheels, brakes, and propellers into their actuators, enabling them to move on the ground or fly in the air.

[0429] Additionally, the above-described technical features can be applied to devices that support extended reality.

[0430] Extended reality is a general term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology presents real-world objects and backgrounds as CG images only, AR technology presents virtual CG images over images of real objects, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.

[0431] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.

[0432] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

Claims

1. Create a SIG (signal) field that contains a user field, The above user field includes a 1-bit long UEQM (unequal modulation) information field, and a 2-bit long UEQM pattern field consecutive to the UEQM information field, The above UEQM information field contains information related to whether UEQM is applied, The above UEQM pattern field includes information related to a UEQM pattern applied to at least two spatial streams; and Step of transmitting the above SIG field How to include.

2. In paragraph 1, the SIG field is included in a PPDU (Physical Protocol Data Unit), The above PPDU further includes a U-SIG (Universal) field containing control information for interpreting the above PPDU, The SIG field is continuous with the U-SIG field and contains additional control information for interpreting the PPDU, The above SIG field includes common fields and user specific fields, The above user field is included in the above user specific field. method.

3. In paragraph 1, The above user field further includes an STA (station) ID field of 11 bits in length, and an MCS field that is continuous to the STA ID field and has a length of 5 bits, The above UEQM information field has a first value based on whether UEQM is applied over a different spatial stream. method.

4. In paragraph 3, The above UEQM pattern field contains information related to the constellation index applied to two spatial streams, Based on the value of the above UEQM pattern field being 0, the constellation index related to the first spatial stream is M, and the constellation index related to the second spatial stream is M-1. Based on the value of the above UEQM pattern field being 1, the constellation index related to the first spatial stream is M, and the constellation index related to the second spatial stream is M-2. The above M is a constellation index related to the above MCS field, The above M-1 is a constellation that is one order lower than M, The above M-2 is a constellation that is two orders lower than M. method.

5. In paragraph 3, The above UEQM pattern field contains information related to the constellation index applied to three spatial streams, Based on the value of the above UEQM pattern field being 0, the constellation index related to the first spatial stream is M, the constellation index related to the second spatial stream is M, and the constellation index related to the third spatial stream is M-1. Based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream is M, the constellation index related to the second spatial stream is M, and the constellation index related to the third spatial stream is M-2. Based on the value of the above UEQM pattern field being 2, the constellation index related to the first spatial stream is M, the constellation index related to the second spatial stream is M-1, and the constellation index related to the third spatial stream is M-2. The above M is a constellation index related to the information contained in the above MCS field, The above M-1 is a constellation that is one order lower than M, The above M-2 is a constellation that is two orders lower than M. method.

6. In paragraph 3, The above UEQM pattern field contains information related to the constellation index applied to four spatial streams, Based on the value of the above UEQM pattern field being 0, the constellation index related to the first spatial stream is M, the constellation index related to the second spatial stream is M, the constellation index related to the third spatial stream is M, and the constellation index related to the fourth spatial stream is M-1. Based on the value of the UEQM pattern field being 1, the constellation index related to the first spatial stream is M, the constellation index related to the second spatial stream is M, the constellation index related to the third spatial stream is M, and the constellation index related to the fourth spatial stream is M-2. Based on the value of the UEQM pattern field being (2), the constellation index related to the first spatial stream is M, the constellation index related to the second spatial stream is M, the constellation index related to the third spatial stream is M-1, and the constellation index related to the fourth spatial stream is M-2. The above M is a constellation index related to the information contained in the above MCS field, The above M-1 is a constellation that is one order lower than M, The above M-2 is a constellation that is two orders lower than M. method.

7. In paragraph 3, The above user field further includes a 3-bit long NSS field consecutive to the above MCS field, wherein the NSS field includes information about the number of spatial streams, The above UEQM information field is continuous with the above NSS field. method.

8. In paragraph 7, The above STA ID field is included in B0 to B10 of the above user field, The above MCS field is included in B11 to B15 of the above user field, The above NSS field is included in B16 to B18 of the above user field, The above UEQM information field is included in B19 of the above user field, The above UEQM pattern field is included in B20 to B21 of the above user field, 9. In paragraph 1, The above UEQM information field has a first value based on whether UEQM is applied over a different spatial stream, The user field, based on the UEQM information field having the first value, excludes a 1-bit long Beamformed field and a 1-bit long coding field from the user field. The above Beamformed field contains information on whether a beamforming steering matrix is ​​applied, The above coding field contains information on whether BCC (binary convolutional code) or LDPC (Low Density Parity Check) is applied. method.

10. In paragraph 1, The above user field is a non MU-MIMO (multi-user multiple input multiple output) user field. method.

11. In paragraph 1, The above SIG field is transmitted by an AP (Access Point), non-AP, AP MLD (AP Multi-link Device), or non-AP MLD. method.

12. At least one processor; and At least one computer memory operable to said at least one processor, said memory storing instructions for performing operations based on being executed by said at least one processor, The instructions of at least one computer memory are: Create a SIG (signal) field containing a user field, The above user field includes a 1-bit long UEQM (unequal modulation) information field, and a 2-bit long UEQM pattern field consecutive to the UEQM information field, The above UEQM information field contains information related to whether UEQM is applied, The above UEQM pattern field contains information related to a UEQM pattern applied to at least two spatial streams, Transmitting the above SIG field Performing an action STA.

13. In the 12th paragraph, the command of at least one computer memory performs an operation related to any one of the 2nd to 11th paragraphs. STA.

14. Receive a SIG (signal) field containing a user field by STA (station), The above SIG field is included in the PPDU (Physical Protocol Data Unit), The above user field includes a 1-bit long UEQM (unequal modulation) information field, and a 2-bit long UEQM pattern field consecutive to the UEQM information field, The above UEQM information field contains information related to whether UEQM is applied, The above UEQM pattern field includes information related to a UEQM pattern applied to at least two spatial streams; and A step of interpreting the PPDU based on the SIG field by the STA; How to include.

15. In the 14th paragraph, the STA performs an operation related to any one of the 2nd to 11th paragraphs. method.

16. At least one processor included in the STA (station); and At least one computer memory operable to said at least one processor, said memory storing instructions for performing operations based on being executed by said at least one processor, The instructions of at least one computer memory are: Receive a SIG (signal) field containing a user field, The above SIG field is included in the PPDU (Physical Protocol Data Unit), The above user field includes a 1-bit long UEQM (unequal modulation) information field, and a 2-bit long UEQM pattern field consecutive to the UEQM information field, The above UEQM information field contains information related to whether UEQM is applied, The above UEQM pattern field contains information related to a UEQM pattern applied to at least two spatial streams, Interpreting the PPDU based on the above SIG field Performing an action STA.

17. In the 16th paragraph, the STA performs an operation related to any one of the 2nd to 11th paragraphs. method.

18. In a wireless local area network (WLAN) system, at least one computer-readable recording medium including instructions based on being executed by at least one processor, Create a SIG (signal) field containing a user field, The above user field includes a 1-bit long UEQM (unequal modulation) information field, and a 2-bit long UEQM pattern field consecutive to the UEQM information field, The above UEQM information field contains information related to whether UEQM is applied, The above UEQM pattern field includes information related to a UEQM pattern applied to at least two spatial streams; and Step of transmitting the above SIG field Performing an operation that includes Recording medium.

19. In the 18th paragraph, the recording medium performs an operation related to any one of the 2nd to 11th paragraphs. Recording medium.

Images