Configuration of trigger frame

Abstract

The present disclosure relates to a trigger frame structure for supporting a new PHY function in an ultra-high reliability (UHR) or IEEE 802.11bn-based wireless LAN (WLAN) system. Specifically, the trigger frame of the present invention may include a common info field, a special user info field, and a UHR variant user info field. The common info field may include a 4-bit subfield indicating whether a distributed-tone resource unit (DRU) or a regular resource unit (RRU) is requested, and the special user info field may include a PHY version identification subfield indicating whether a trigger-based physical protocol data unit (TB-PPDU) is related to the UHR. In addition, the UHR variant user info field may include a subfield indicating whether unequal modulation (UEQM) is applied to the TB-PPDU. Accordingly, efficient trigger-based transmission control is possible in a system to which various PHY functions are applied.

Description

Configuration of the trigger frame

[0001] This specification relates to a wireless LAN system, and more specifically, to a frame structure related to a trigger frame 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 PPDU (PHY layer protocol data unit) structure, improved sequencing, and the Hybrid Automatic Repeat Request (HARQ) technique. The EHT standard can be referred to as the IEEE 802.11be standard.

[0003] To support high throughput and high data rates, the EHT standard may use wide bandwidth (e.g., 160 / 320 MHz), 16 streams, and / or multi-link (or multi-band) operation.

[0004] In the EHT standard, wide bandwidth (e.g., 160 / 240 / 320 MHz) can be used for high throughput. In addition, preamble puncturing and multiple RU transmission can be used to efficiently utilize bandwidth.

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

[0006] Conventional wireless LAN systems provide trigger frame-based UL-MU communication. A trigger frame includes various fields such as a common info field and a user info field. The common info field contains information common to all STAs receiving the trigger frame, and the user info field may contain user-specific information common to individual STAs among the STAs receiving the trigger frame.

[0007] UHR wireless LAN systems or 11bn wireless LAN systems propose various PHY features. These PHY features may relate to UEQM (Unequal modulation), additional MCS, 2x LDPC, DRU (distributed-tone RU), and / or RRU, etc. To apply these new PHY features to TB-PPDU (trigger-based physical protocol data unit), the structure of the trigger frame must be appropriately improved.

[0008] This present disclosure relates to the structure of an improved trigger frame.

[0009] For example, the trigger frame may include a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field.

[0010] For example, the common information field includes a 4-bit subfield, and the 4-bit subfield may include information regarding whether a distributed-tone resource unit (DRU) is solicited or a regular resource unit (RRU) is solicited by the trigger frame.

[0011] For example, the special user information field includes a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield may include information regarding whether the TB PPDU (solicited trigger-based physical protocol data unit) requested by the trigger frame is related to UHR.

[0012] For example, the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield may include information related to whether unequal modulation (UEQM) is applied to the TB PPDU.

[0013] An example of the present specification may provide a trigger frame structure for the efficient transmission of trigger-based physical protocol data units (TB-PPDU) in an Ultra High Reliability (UHR) or 11bn wireless LAN system that supports various PHY functions (e.g., UEQM, additional MCS, 2ХLDPC, DRU, RRU, etc.).

[0014] A trigger frame according to an example of the present specification includes a common information field, a special user information field, and a UHR variant user information field, thereby clearly distinguishing and displaying transmission setting information corresponding to each PHY function.

[0015] Accordingly, the transmitting and receiving device can efficiently determine whether a request for DRU or RRU resources, PHY version identification information, and UEQM application status based on the trigger frame, and can improve the flexibility and scalability of trigger-based communication procedures throughout the system.

[0016] Accordingly, the present specification can minimize frame format inconsistencies or inefficiencies during TB-PPDU transmission including new PHY functions and increase the flexibility and reliability of trigger-based transmission procedures.

[0017] In addition, by clearly distinguishing the PHY version compatibility between each STA and AP, interoperability between various PHY generations can be guaranteed, and the resource allocation efficiency and processing latency improvement effects of trigger-based multi-user (MU) transmission can be achieved simultaneously.

[0018] Consequently, the present specification enables the coexistence of various PHY functions in next-generation UHR wireless LAN systems and can provide the effect of improving overall system transmission efficiency, reliability, scalability, and standard compatibility.

[0019] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

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

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

[0022] FIG. 4 illustrates an example of a multi-link (ML).

[0023] FIG. 5 illustrates a PPDU transmitted / received in an STA of the present specification.

[0024] Figure 6 is a diagram showing the arrangement of resource units (RU) used for a 20 MHz PPDU.

[0025] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0026] Figure 8 is a diagram showing the arrangement of resource units (RU) used for an 80 MHz PPDU.

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

[0028] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0029] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0030] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

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

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

[0033] FIGS. 15 and 16 show examples of user info fields related when EQM and RRU are applied.

[0034] FIGS. 17 to 21 show examples of user info fields related when EQM and DRU are applied.

[0035] FIGS. 22 to 25 show examples of user info fields related when UEQM and RRU are applied.

[0036] FIGS. 26 to 30 show examples of user info fields related when UEQM and DRU are applied.

[0037] FIGS. 31 and 32 illustrate an example of an Extended user info field related to the present specification.

[0038] FIG. 33 is an example of a procedure flowchart related to the present specification.

[0039] FIG. 34 is another example of a procedure flowchart related to the present specification.

[0040] In this specification, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, in this specification, “A or B” may be interpreted as “A and / or B.” For example, in this specification, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0041] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “A and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B or C.”

[0042] 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 as synonymous with “at least one of A and B.”

[0043] Additionally, parentheses used in this specification may mean “for example.” Specifically, when 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” of this specification is not limited to the “UHR-Signal field,” and the “UHR-Signal field” may be proposed as an example of “control information.” Furthermore, even when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be proposed as an example of “control information.”

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

[0045] Additionally, the expressions “based on,” “on the basis of,” or “according to” as used in this specification mean “based at least in part on,” and do not mean “based only on one.”

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

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

[0048] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0049] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

[0050] 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 this specification may also be referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. The STA (110, 120) of this specification may also be referred to by various names such as network, base station, Node-B, Access Point (AP), repeater, router, relay, etc. The STA (110, 120) of this specification may also be referred to by various names such as receiving apparatus, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.

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

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

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

[0054] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0055] The first STA (110) may include a processor (111), 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.

[0056] The transceiver (113) of the first STA performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0057] 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 transmitted signal, and perform control for transmitting the signal. The memory (112) of the AP can store the signal received through the transceiver (113) (e.g., received signal) and the signal to be transmitted through the transceiver (e.g., transmitted signal).

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

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

[0060] For example, the operation of the device indicated as AP in the following specification may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (111) of the first STA (110), and related signals may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). Additionally, control information related to the operation of the AP or the transmission / reception signals of the AP may be stored in the memory (112) of the first STA (110). Additionally, if the second STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (121) of the second STA (120), and related signals 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 AP or the transmission / reception signals of the AP can be stored in the memory (122) of the second STA (110).

[0061] For example, the operation of a device indicated as non-AP (or User-STA) in the following specification may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is non-AP, the operation of the device indicated as non-AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signals 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 the device marked as non-AP is controlled by the processor (111) of the first STA (110), and the related signal can be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signal of the AP can be stored in the memory (112) of the first STA (110).

[0062] In the following specification, a device referred to as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, a device indicated without specific drawing symbols as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may also refer to the STA (110, 120) of FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPPDU) may be performed by the transceiver (113, 123) of FIG. 1. Additionally, in the following example, 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 to generate a transmission / reception signal or to perform data processing or operations in advance for a transmission / reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of sub-fields (SIG, STF, LTF, Data) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 4) a power control operation and / or power saving operation applied to the STA; and 5) an operation related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (112, 122) of FIG. 1.

[0063] The device / STA of the aforementioned supplementary drawing (a) of FIG. 1 can be modified as shown in supplementary drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of this specification will be described based on supplementary drawing (b) of FIG. 1.

[0064] For example, the transceiver (113, 123) shown in side drawing (b) of FIG. 1 can perform the same function as the transceiver shown in side drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) shown in side 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) shown in side drawing (b) of FIG. 1 can perform the same function as the processor (111, 121) and the memory (112, 122) shown in side drawing (a) of FIG. 1 described above.

[0065] 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, AP (Access Point), 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) shown in side drawings (a) / (b) of FIG. 1, or the processing chip (114, 124) shown in side drawing (b) of FIG. 1. That is, the technical features of the present specification may be performed in the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or only in the processing chip (114, 124) shown in side drawing (b) of FIG. 1. For example, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal generated in the processor (111, 121) shown in side drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) shown in side drawings (a) / (b) of FIG. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal to be transmitted from the processing chip (114, 124) shown in side drawing (b) of FIG. 1 is generated to the transceiver (113, 123).

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

[0067] Referring to side view (b) of FIG. 1, software code (115, 125) may be included in 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.

[0068] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. 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 a processor enhanced therefrom.

[0069] In this specification, an uplink may refer to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted through the uplink. Additionally, in this specification, a downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted through the downlink.

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

[0071] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).

[0072] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter BSS). The BSS (200, 205) is a set of APs and STAs, such as an AP (access point, 225) and STA1 (Station, 200-1), that can communicate with each other by successfully synchronizing, and is not a concept referring to a specific area. The BSS (205) may include one or more STAs (205-1, 205-2) that can be combined with one AP (230).

[0073] The BSS may include at least one STA, an AP (225, 230) that provides a distribution service, and a distribution system (DS, 210) that connects multiple APs.

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

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

[0076] In a BSS like the one at the top 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 between STAs and perform communication without APs (225, 230). A network that establishes a network between STAs and performs communication without APs (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0077] The bottom of Fig. 2 is a conceptual diagram showing IBSS.

[0078] 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 performs management functions centrally. 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 since access to the distributed system is not allowed, they form a self-contained network.

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

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

[0081] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels and transmits a probe request frame to search for nearby APs, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame, whereas in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store the BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (e.g., transmitting and receiving probe requests / responses on channel 2).

[0082] Although not shown in the example of Fig. 3, scanning operations may also be performed using a passive scanning method. An STA performing scanning based on passive scanning can wait for a beacon frame while switching between channels. A beacon frame is one of the management frames in IEEE 802.11, which announces the presence of a wireless network and is periodically transmitted to allow a scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS take turns transmitting beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. An STA that has received a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner.

[0083] The STA that discovered the 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 later. The authentication process of S320 may include the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.

[0084] The authentication frame may include information regarding the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), Finite Cyclic Group, etc.

[0085] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.

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

[0087] Subsequently, 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 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame.

[0088] FIG. 4 illustrates an example of a multi-link (ML).

[0089] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate through a multi-link. The MLDs can be classified into an AP MLD containing multiple AP STAs and a non-AP MLD containing multiple non-AP STAs. That is, the AP MLD may include affiliated APs (e.g., AP STAs), and the non-AP MLD may include affiliated STAs (e.g., non-AP STAs, or user-STAs).

[0090] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be assigned to the first and second links. The first and second multilinks may be identified by 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 link may be configured in different bands.

[0091] The AP MLD of FIG. 4 includes three affiliated APs. In one 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 one 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. Additionally, in one 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. Additionally, in one 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.

[0092] In one example of FIG. 4, AP1 can initiate a multilink setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In one example of FIG. 4, non-AP STA1 can transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) shown in FIG. 4 may be the same as the AP shown in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) shown in FIG. 4 may be the same as the STA shown in FIG. 1 and / or FIG. 2 (e.g., user-STA or non-AP STA).

[0093] 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.

[0094] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.

[0095] The STAs of this specification (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) can transmit and / or receive the PPDU of FIG. 5. The PPDU described in this specification may have the structure of FIG. 5, for example. Additionally, the PPDU described in this specification, the Ultra High Reliability (UHR) PPDU, may be referred to by various names such as transmit PPDU, receive PPDU, first type or N type PPDU. The PPDU described in this specification may be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that improve upon IEEE 802.11bn.

[0096] 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 SU (single-user) mode / type / transmission, MU (multi-user) mode / type / transmission, and NDP (null data packet) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the illustrated Data field may be omitted. If the PPDU of FIG. 5 is used for TB (Trigger-based) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that receives a Trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU in which the UHR-SIG is omitted in the example of FIG. 5.

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

[0098] Each block illustrated in FIG. 5 may be referred to as a field / subfield / signal, etc. As illustrated in FIG. 5, the names of these fields / subfields / signals may be 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.

[0099] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in Fig. 5 can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can 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 can be displayed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be displayed in units of 78.125 kHz.

[0100] The PPDU of Fig. 5, L-LTF and L-STF, may be the same as conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0101] The L-SIG field of FIG. 5 may contain, 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 contain information regarding 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 a UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is an 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, or 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 a UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

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

[0103] For example, the (non-AP and AP) STA can generate an RL-SIG that is identical to the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine that the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the HE PPDU, EHT PPDU, or UHR PPDU if the RL-SIG is present. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the non-HT PPDU, HT PPDU, or VHT PPDU if the RL-SIG is not present. 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.

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

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

[0106] For example, A bit information (e.g., 52 un-coded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bit information (e.g., 26 un-coded bits) of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bit information (e.g., 26 un-coded bits) of the total A bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can generate 52-coded bits by performing convolutional encoding (e.g., BCC encoding) based on a rate of R=1 / 2 and can perform interleaving on the 52-coded bits. The transmitting STA can generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. 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. 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.

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

[0108] A bit information (e.g., 52 un-coded bits) transmitted by 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 may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.

[0109] For example, the version-independent bits of 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 of the 3-bit PHY version identifier (e.g., a value of 000) may indicate that the transmitted and received PPDU is an EHT PPDU. Additionally, a second value of the 3-bit PHY version identifier (e.g., a value of 001) may indicate that the transmitted and received PPDU is a UHR PPDU.

[0110] In other words, when an (AP / non-AP) STA transmits an EHT PPDU, it can set a 3-bit PHY version identifier to a first value. In other words, a 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 a UHR PPDU based on the PHY version identifier having the second value.

[0111] 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 is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.

[0112] For example, the version-independent bits of U-SIG may include information regarding the length of the TXOP and information regarding the BSS color ID.

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

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

[0115] Preamble puncturing may be applied to the PPDU of Fig. 5. Preamble puncturing means applying puncturing to a portion of the total band of the PPDU (e.g., a 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.

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

[0117] 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.

[0118] 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 configured individually in 80 MHz units. 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 (e.g., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information regarding a 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (e.g., information regarding a preamble puncturing pattern). Meanwhile, the UHR-SIG following the first U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (e.g., information regarding a preamble puncturing pattern), and the UHR-SIG following the second U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (e.g., information regarding a preamble puncturing pattern).

[0119] Additionally or generally, 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 (e.g., 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 (e.g., information regarding preamble puncturing patterns).

[0120] 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 may contain different U-SIGs.

[0121] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted through at least one symbol, and one 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.

[0122] UHR-SIG provides additional signals to the U-SIG field, enabling the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that apply commonly to all users. Additionally, the UHR-SIG field contains resource allocation information, making it possible for the STA to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (e.g., UHR modulated fields of an UHR PPDU).

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

[0124] FIG. 6 is a diagram showing the arrangement of resource units (RUs) used for a 20 MHz PPDU. That is, 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.

[0125] As shown at the top of FIG. 6, 26 units (e.g., units corresponding to 26 tones) may be arranged. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Additionally, seven DC tones may be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on the left and right sides of the DC band. Furthermore, 26, 52, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

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

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

[0128] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0129] Just as various sizes of RUs were used in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may also be used in the example of FIG. 7. Additionally, 5 DC tones may be inserted at the center frequency, 12 tones may be used as guard bands in the leftmost band of the 40 MHz band, and 11 tones may be used as guard bands in the rightmost band of the 40 MHz band.

[0130] In addition, as described, 484-RU 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.

[0131] FIG. 8 is a diagram showing the arrangement of resource units (RUs) used for an 80 MHz PPDU. The arrangement of resource units (RUs) used in this specification may be varied. For example, the arrangement of resource units (RUs) used in the 80 MHz band may be varied.

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

[0133] TB PPDUs (941, 942) are transmitted at the same time and may be transmitted from multiple STAs (e.g., User STAs) with an AID indicated within a Trigger frame (930). An ACK frame (950) for a TB PPDU may be implemented in various forms. For example, an ACK frame (950) for a TB PPDU may be implemented in the form of a BA (block ACK).

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

[0135] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0136] The 2.4 GHz band may be referred to by other names, such as the first band (band). Additionally, 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 located between 2.4 and 2.5 GHz) are used / supported / defined.

[0137] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz channels 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 to channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned to channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned to channel index N may be (2.407 + 0.005*N) GHz. Channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of channel indices and center frequencies may change.

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

[0139] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0140] The 5 GHz band may be referred to by other names such as the second band / band. The 5 GHz band may refer to a frequency range in which channels with a center frequency of 5 GHz or higher 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 may be changed.

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

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

[0143] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0144] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with a center frequency of 5.9 GHz or higher are used / supported / defined. The specific figures shown in FIG. 12 are subject to change.

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

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

[0147] The structure and types / subtypes of MAC frames are described below.

[0148] FIG. 13 shows an example of a MAC frame header. As illustrated, the MAC frame may include a frame control field / information of 2 octets, a duration field / information of 2 octets, a Receiver Address (RA) field / information of 6 octets, and a Transmitter Address (TA) field / information of 6 octets. As illustrated in FIG. 13, the four fields may be consecutive. 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.

[0149] The MAC header shown in FIG. 13 may be located at the very beginning of the MAC frame. That is, the MAC frame may include a MAC header such as that in FIG. 13 and a MAC body field / information following the MAC header. The MAC frame containing the MAC header of FIG. 13 is inserted / included in the data field of the PPDU (e.g., UHR PPDU) shown in FIG. 5.

[0150] MAC frames included in the data fields of the PPDU of this specification may be classified into various types. For example, MAC frames of this specification may be classified into control frames, management frames, and data frames.

[0151] For example, a 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 WLANs. For the management frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are set to 00. Additionally, 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).

[0152] For example, the control frame includes the 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 WLANs. For the control frame, the values ​​of the type fields (B3 and B2) in FIG. 13 are 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).

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

[0154] MAC frames / signals 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 may refer to a MAC frame in which the type bits B3 and B2 within the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 within the frame control field are set to 0010. Various MAC frames described in this specification are inserted into / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDU).

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

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

[0157] The processor (610) of FIG. 14 may be the same as the processor (111, 121) of FIG. 1. Or, the processor (610) of FIG. 14 may be the same as the processing chip (114, 124) of FIG. 1.

[0158] 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.

[0159] Referring to FIG. 14, a power management module (611) manages power for 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 associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.

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

[0161] Next Wi-Fi (beyond 11be) aims to support Ultra-High Reliability (UHR) during signal transmission for STAs. To support this UHR, various technologies are being considered to enable high throughput, low latency, and extended range. To achieve this, additional Modulation Control Systems (MCS) may be considered to improve throughput by increasing spectral efficiency during signal transmission and reception. Additionally, Unequal Modulation (UEQM) technology may be considered as a general measure. UEQM is a technique that addresses SNR imbalances for spatial streams (SSs) during MIMO / beamforming transmission using two or more SSs. For example, UEQM can refer to a technique that utilizes different modulation (e.g., different constellation mapping) for each SS.

[0162] The UEQM technology is described below.

[0163] For example, when transmitting MIMO / Beamforming signals, a beamforming matrix formed based on singular value decomposition (SVD) is used to transmit signals. Therefore, when transmitting signals using multiple spatial streams (SS), the MIMO gain or SNR may be concentrated in a limited number of SSs, including the first SS (e.g., 1st SS). In other words, an imbalance may occur where the MIMO gain or SNR is concentrated in only one SS (or some SSs), including the first SS.

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

[0165] For example, the UEQM of this specification may mean 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, the MCS techniques applied to different SSs may be set individually. For example, a plurality of MCS techniques related to the UEQM (e.g., the first MCS technique and the second MCS technique) may be configured / set based on the same code rate. For example, a plurality of MCS techniques related to the UEQM (e.g., the first MCS technique and the second MCS technique) may be based on a constellation mapping technique / technology that is based on the same code rate but is set individually from each other.

[0166] In other words, when applying different modulations for each SS (e.g., applying a first MCS technique to a first SS and a second MCS technique to a second SS), the code rate can be fixed identically as described above in order 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 apply modulations (e.g., constellation mapping technique / technique) that are individually set to each other while based on the same code rate.

[0167] For example, a new set of MCS parameters (or indices / levels) may be defined in relation to (or independently of) the UEQM of this specification. For example, a new combination of code rate and modulation (i.e., constellation mapping) that has not previously been applied may be defined as follows.

[0168] The UEQM technology / transmission in relation to MCS parameters is explained below.

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

[0170] For example, Table 1 below relates to a UEQM that supports up to 4 Nss. For example, if 2 Nss are supported, a modulation (e.g., constellation mapping) denoted by M may be applied to the first SS as shown in the table below. In this case, a modulation (e.g., constellation mapping) denoted by M-1 or M-2 may be applied to the second SS.

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

[0172] For example, if up to 4 Nss are supported, 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 1 below, based on the method described above.

[0173] The specific contents of Table 1 can be modified in various ways.

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

[0175] Applying individual constellations to different SSs as described above can be called UEQM. For example, when UEQM is applied, the constellations (or constellation indices / parameters) applied to different SSs may be identical. However, even when UEQM is applied, it is desirable for the code rates applied to different SSs to be the same.

[0176] For example, if information related to a UEQM pattern is transmitted, a UEQM according to Table 1 may be applied. For example, if a specific N-bit value (e.g., a 2-bit value) is transmitted, a UEQM pattern corresponding to that value may be applied (e.g., a pattern of {M, M-1} in which modulation corresponding to M (e.g., 16-QAM) is applied to the first SS and modulation corresponding to M-1 (e.g., QPSK) is applied to the second SS).

[0177] The above-described UEQM technology may be one of various PHY features related to the UHR system. For example, the UEQM technology may be used in conjunction with additional PHY features such as additional MCS, 2x LDPC, and / or DRU (distributed-tone RU). In order to perform UL transmission using the various features defined in 11bn / UHR, the AP may transmit information about the features to non-AP STAs via a trigger frame.

[0178] The following example may relate to applying an 11bn PHY feature to a frame solicited by a Trigger Frame (e.g., a TB (trigger-based PPDU)). To this end, the following example may relate to including control information related to the 11bn PHY feature within the Trigger Frame.

[0179] For example, the 11bn PHY feature may be related to the aforementioned UEQM technology, additional MCS, 2x LDPC, and / or DRU, etc. For example, control information related to the 11bn PHY feature may be referred to by various names such as first / second control fields, first / second sub-fields, first / second bit information, etc. For example, control information related to the 11bn PHY feature may be included in the common info field, user info field, and / or special user info field of a Trigger frame, etc.

[0180] For example, the above 11bn PHY features may be referred to by various names such as UHR PHY features, UEQM technology, additional MCS technology, 2x LDPC technology, DRU technology, etc.

[0181] First technical feature

[0182] A trigger frame containing control information related to the above 11bn PHY features can be defined in various ways.

[0183] For example, a trigger frame transmitted via an indication for the UHR variant (or 11bn variant) may be indicated based on an 11bn / UHR variant trigger frame. For example, to indicate a UHR variant trigger frame, the first bit information (e.g., 1 bit information) of the common field included within the trigger frame may be used. In this case, the first bit information may be a reserved bit / information within the common info field (e.g., B53 or B63 of the common info field). For example, the first bit information may be bit information that was reserved within the EHT variant common info field (e.g., B22 or B26). For example, the first bit information of the common field may be defined as one of the bits B53 or B63. For example, the corresponding bit may be referred to by various names such as an indication bit, a next variant field, or a non-EHT field.

[0184] For example, when using the B53 bit as described above, the HE / EHT / UHR variant trigger frame can be defined through a 3-bit setting according to the version of the non-AP STA as follows.

[0185] For example, in the case of a Non-AP HE (High Efficiency) STA, it may operate as follows. For example, regardless of the value of the B53 bit of the common info field of the received trigger frame, if both the B54 bit and the B55 bit are set to one (1), the received trigger frame can be identified as a HE variant trigger frame. In this case, a new bit is defined to identify / indicate the UHR variant trigger frame, but the bit may not affect the receiving operation of the non-AP HE STA.

[0186] For example, in the case of a Non-AP EHT (Extremely High Throughput) STA, it may operate as follows. For example, the value of bit B53 of the common info field of the received trigger frame is set to zero (0), and in all cases except for the case where both bits B54 and B55 are one (1), the received trigger frame can be identified as an EHT variant trigger frame as shown in Table 2 below. In this case, since it is the same as the existing identification operation, it may not affect the reception operation of the non-AP EHT STA.

[0187] Common Info field B54Common Info field B55User Info field B39Presence of Special User Info fieldUser Info field variantTB PPDU type110NoHE variantHE000YesEHT variantEHT001YesEHT variantEHT101YesEHT variantEHT100YesHE variantHE

[0188] For example, in the case of a Non-AP UHR STA, it may operate as follows. For example, the value of the B53 bit of the common info field of the received trigger frame is set to one (1), and in all cases except for the case where both the B54 bit and the B55 bit are one (1), the received trigger frame can be identified / recognized as an UHR (ultra-high reliability) variant trigger frame. Specifically, the values ​​for identifying the UHR variant trigger frame can be applied in the same way as the EHT variant shown in Table 2, and in this case, the HE variant in Table 2 can be changed to an EHT variant.

[0189] The indication for the above UHR variant trigger frame can be modified in various ways. For example, as previously described, the indication for the UHR variant trigger frame can be performed through the B63 bit of the common info field instead of the B53 bit of the common info field. Specifically, since the B53 bit of the common info field is used for Doppler indication in the HE variant, the B63 bit of the common info field can be used for the indication for the UHR variant trigger frame to reduce ambiguity regarding HE. Additionally, or generally, the 1-bit information for the indication for the UHR variant trigger frame may be one of the B56 to B62 bits of the common info field, and, for example, it may be preferable to use the B56 bit or the B62 bit.

[0190] As described above, by indicating to the UHR non-AP STA (or next version non-AP STA) that it is a UHR variant trigger frame, 1) a new UHR variant trigger frame can be constructed, or 2) information about new PHY features related to UHR (e.g., information related to UEQM) can be included in the common info, special user info, and / or user info fields of the trigger frame.

[0191] For example, when the B53 / B63 bits of the common info field are defined and used as UHR / next version variant indications, the bits are set to 1, and in cases other than when both the B54 bit and the B55 bit of the common info field are set to 1 (1), the variant of the trigger frame can be identified as a UHR variant trigger frame. In this case, the common info field of the trigger frame may include information about PHY features newly defined in 11bn (e.g., DRU, 2x LDPC, UEQM, new MCS, etc.).

[0192] Based on the above, the indication for the UHR variant trigger frame can be set as follows.

[0193] Common Info field B53 / B63Common Info field B54Common Info field B55100UHR variant101UHR variant110UHR variant

[0194] For example, various indication information may be included within a UHR variant trigger frame. For example, a 4-bit DRU indication indicating whether a DRU is applied within the corresponding bandwidth may be included in the common info field of the UHR variant trigger frame. The DRU indication may indicate whether a DRU is applied in 80 MHz increments or whether a RRU (regular RU) is applied. Accordingly, a non-AP STA that identifies / recognizes that the trigger frame it received is a UHR variant trigger frame through the 3 bits of the common info field (e.g., the B53 / 63 bit, B54 bit, and B55 bit) may support DRU transmission defined by the UHR system based on the 4-bit information (e.g., the DRU indication) included in the common info field.

[0195] For example, as described above, a UHR variant trigger frame can be indicated by using a separate 1 bit within the common info field (e.g., bit B53 / 63 of the common info field). Through this, information included in the UHR variant trigger frame can be newly defined or modified, and a non-AP STA that receives this can distinguish the trigger frame variant through the information and efficiently receive the individual information included therein.

[0196] As described above, when the UHR variant trigger frame is indicated based on the first information bit (e.g., B55 / B63 bit, etc.), the trigger frame may include a special user info field. For example, the special user info field may follow the common info field within the trigger frame and may include information common to all users. For example, some fields included in the special user info field may be as follows.

[0197] Field 1: AID12

[0198] In order to indicate that it is a special user info field, identical to the EHT variant trigger frame, the value of the AID12 field can be set to 2007 or a preset value.

[0199] Second field: PHY version identifier

[0200] The second field above may have a length of 3 bits, and in the case of a UHR variant trigger frame, the corresponding value may be set to one (1). Through the second field above, it may be indicated that it is a UHR variant trigger frame.

[0201] 3rd Field: Extension

[0202] The third field mentioned above may be used to indicate an extension of the UHR special user info field. The UHR system defines various PHY features and can transmit information or indications regarding them through the special user info field. However, since the size of the user info field is limited to 5 bytes, it may be difficult to include all necessary information in a single special user info field. Therefore, additional special user info fields may be included to include indications for newly defined features, and the third field mentioned above may be used as an indication for this purpose.

[0203] For example, the third field may be composed of 1-bit and may have a value of 1. The value of 1 included in the third field may indicate that there is an additional special user info field. For example, if there is one or more user info fields, the third field may be set to zero (0) in the last user info field. This may indicate that there are no more identical user info fields. For example, if the value of the third field is set to 1 to indicate that there is an additional special user info field, the value of the first field (AID12) of the additional special user info field may have a value of 2007 or another value. For example, the value of the first field (e.g., AID12) of the first special user info field may be 2007, and the value of the first field (e.g., AID12) of the second and subsequent special user info fields may be set to one of the values ​​from 2008 to 2044.

[0204] Since the UHR variant trigger frame was indicated through the Common info field (e.g., B53 / B63 or a combination of B53 / B63, B54, B55), the special user info field and user info field have the advantage of being able to be newly configured to include information about UHR features.

[0205] Second technical feature

[0206] For example, it is possible to reuse an EHT trigger frame for a UHR variant trigger frame. Specifically, the common info field of the UHR variant trigger frame can be configured to be identical to the common info field of the EHT variant. In this case, when transmitting the UHR variant trigger frame, bits B54 and B55 of the common info field of the UHR variant trigger frame can be set to be identical to bits B54 and B55 used to indicate that it is an EHT trigger variant. Specifically, when transmitting the UHR variant trigger frame, the values ​​of bits B54 and B55 can be set to be identical to the values ​​in Table 2 used to indicate the EHT variant.

[0207] In this case, since the Common info field of the UHR variant trigger frame is set to be the same as that of the EHT variant trigger frame, the non-AP STA can verify the exact variant (or version) information of the received trigger frame through the special user info field. More specifically, the non-AP STA can identify that the received trigger frame corresponds to a UHR variant trigger frame based on the PHY version identifier included in the special user info field.

[0208] Specifically, a UHR variant trigger frame can be indicated through a PHY version identifier as described above. In other words, the value of the PHY version identifier in the special user info field within the UHR variant trigger frame can have a value of 1 (1) to indicate that it is a UHR variant. In this case, a non-AP STA can determine whether the received trigger frame corresponds to a UHR variant based on the value of the PHY version identifier included in the special user info field.

[0209] As described above, since the receiving STA recognizes information about the trigger variant (or version) through the PHY version identifier included in the special user info, the common info field of the UHR variant trigger frame does not contain information about new features for UHR or 11bn, but instead, information about UHR PHY features may be included in the special user info.

[0210] However, these characteristics may be modified in various ways. For example, even if information regarding the trigger variant (or version) is determined based on special user info (e.g., based on the PHY version identifier above), it is also possible to include information regarding the UHR PHY feature (e.g., the 4-bit DRU indication described above) in the common info field. Such an example may be modified as follows. The DRU indication information included in the UHR variant common info field may be included in the special user info field and transmitted. The information containing the 80MHz DRU indication information consists of 4 bits and may be constructed using some bits of bits B25 to B39 of the special user info field. In this case, the DRU indication may be indicated using bit B36 and at least one of bits B37 to B39, which are set as reserved bits in the EHT variant special user info field. The indication is transmitted through the U-SIG one bit of the 80MHz UHR TB PPDU solicited through the trigger frame, and may be set to the same value. More specifically, when triggering DRU transmission for 320 MHz, the above 4 bits can indicate whether to use DRU per 80 MHz frequency subblock. In this case, values ​​such as [1, 0, 0, 1] can be set.Specifically, the TB PPDU transmitted via solicitation through the trigger frame may have a different U-SIG for each 80MHz frequency subblock, and the value of one bit of the U-SIG (e.g., DRU indication) may be set to be the same using the DRU indication information for each 80MHz indicated through the trigger frame. Specifically, the corresponding indication of the U-SIG in the first 80MHz frequency subblock may be set to one (1), the value of the corresponding one bit of the U-SIG for the second 80MHz frequency subblock may be set to zero (0), the U-SIG of the third 80MHz frequency subblock may be set to zero (0), and the corresponding bit of the U-SIG of the fourth 80MHz frequency subblock may be set to one (1).

[0211] Third technical feature

[0212] The third technical feature described below relates to the improvement of the user info field. The user info field below may follow the special user info field described above within the trigger frame. For example, information regarding the 11bn PHY features described above (e.g., UEQM, new MCS, DRU, 2x LDPC, etc.) may be included in the user info field included within the UHR variant trigger frame. An example of user info that may be included in the user info field above may be as follows.

[0213] 1st user info: UEQM / EQM indication

[0214] The above information consists of 1 bit and can indicate UEQM transmission or EQM transmission.

[0215] User 2 info: UEQM pattern

[0216] The above information can be composed of 2 bits and can represent the modulation pattern used for each SS. For example, the above information can indicate any one of the multiple modulation patterns shown in Table 1 (e.g., {M, M-2}) through a 2-bit value.

[0217] Third user info: Extended MCS

[0218] The above information can be composed of 5 bits by considering the newly added 4 MCSs.

[0219] User 4 info: 2x LDPC

[0220] The above information may be indication information related to an LDPC codeword having 2x length. For example, UHR or 11bn systems consider LDPC codewords having 2x length to increase transmission efficiency and throughput. The above information may be composed of 1 bit for indication regarding this. While the above information may be configured explicitly, it is also possible for 2x LDPC to be implicitly indicated, in which case the above information may be omitted.

[0221] 5th user info: Distributed BW

[0222] The above information may relate to information about the Distributed BW to which the DRU is applied. The above information is information transmitted to the STA assigned the DRU (e.g., non-AP STA) and may have a length of, for example, 2 bits or 3 bits.

[0223] User 6 info: CSD

[0224] The above information may be information for indicating a CSD (Cyclic shift delay or Cyclic shift definition). For example, the above information may be used to indicate the CSD assigned to each STA when transmitting and receiving signals through a DRU. The above information may have a length of, for example, 3 bits.

[0225] Information to support various features considered in 11bn or UHR as described above can be transmitted through the user info field.

[0226] 4th Technical Features

[0227] Some of the first to sixth user infos described above may be omitted. Additionally, the UHR variant user info field of this specification may include additional user info in addition to the first to sixth user infos described above. An example of transmitting information regarding UHR features (e.g., UEQM, new MCS, DRU, and / or 2x LDPC, etc.) based on a single user info field is described below. Additionally, or generally, in the sixth technical feature described below, it is possible to propose an extended user info field that combines two user info fields.

[0228] When transmitting information regarding the UHR features considered above through a single user info field, the user info field of the UHR variant trigger frame may be defined to include the following information. For example, the user info field may include different fields depending on whether UEQM and / or DRU are used. Specifically, the user field of the UHR variant trigger frame may be configured differently depending on the UHR features used (e.g., UEQM, DRU, etc.). The user info field of the UHR variant trigger frame may include different structures (or content) depending on the UHR operation or UHR feature.

[0229] UEQM indication

[0230] For example, UEQM indication information / fields can be configured as follows.

[0231] For example, the User info field of a trigger frame is configured to include UEQM indication information / field, and said UEQM indication information / field may have a length of 1 bit. said information / field may be referred to by various names such as UEQM indication. For example, said UEQM indication may be indicated using information that is not used during UEQM or a reserved field. As another example, since the information configuration and field configuration of the user info field may differ depending on whether UEQM is used, said indication bit may be located after AID12 or RU allocation.

[0232] For example, when transmitting a signal using UEQM, the user info field of the trigger frame can be configured as follows. For instance, since only LDPC can be used for encoding, the coding type indication during UEQM transmission may be used for other feature signaling or reserved. Additionally, an example of the RU allocation field (8 bits) may be as follows. For instance, the field indicates information regarding the RU allocated to the STA for signal transmission and can indicate whether the allocated RU is a RRU (regular RU) or a DRU (distributed tone RU). For instance, the indication for the size of the DRU can utilize the reserved value of the existing RU allocation. For instance, a non-AP STA receiving the trigger frame can verify whether the RU allocated to it is an RRU or a DRU through the allocated RU allocation field.

[0233] SS allocation

[0234] For example, SS allocation (information / field) can be configured as follows.

[0235] For example, SS allocation can be configured differently depending on whether UEQM and / or DRU transmission is used. For instance, the subfields included in SS allocation, such as "starting spatial stream" and "number of spatial streams," can be reconfigured in various ways as follows. For instance, the UEQM technique may not consider MU-MIMO transmission. Consequently, when UEQM is applied, the value of the starting spatial stream is fixed, so the indication for that value can be omitted. Similarly, when using DRU, MU-MIMO may not be considered. Consequently, since the value of the starting spatial stream is fixed, the indication for that value can also be omitted. For instance, the 4 bits of information allocated for the starting spatial stream can be used to indicate other information. Specifically, considering that the max Nss is 8, this information can be reconfigured into 3 bits during EQM transmission. In this case, the remaining 1 bit can be used for indicating other information. For instance, that 1 bit can be allocated for the UEQM indication. As another example, the above 4-bit information can be used to indicate newly defined features in 11bn / UHR, such as UEQM indication / UEQM pattern / DBW (Distributed BW) / CSD / LDPC, etc.

[0236] Number of spatial stream

[0237] For example, the Number of spatial stream information / field may be configured as follows. The above information / field may have various names, such as NSS information or NSS field.

[0238] For example, since the maximum value of NSS supported in UEQM is 4, NSS information can be composed of 2 bits, just like before. As another example, when DRU transmission is indicated through RU allocation, since Max NSS for DRU transmission is 2, the corresponding NSS information can be composed of 1 bit to represent one or two SS (Spatial Streams).

[0239] UEQM pattern

[0240] For example, information / fields regarding a UEQM pattern may be configured as follows. The above information / fields may be indicated by various names such as UEQM pattern.

[0241] For example, the above information may indicate information regarding the modulation order used per SS when applying UEQM. The above information may have a length of, for example, 2 bits. The above information may indicate the modulation order applied per SS according to Nss. For example, the above information / field may be indicated using some 2 bits of the bits allocated for the starting spatial stream of the SS allocation described earlier.

[0242] 2x LDPC

[0243] For example, information / fields regarding 2x LDPC may be configured as follows. The above information / fields may be displayed under various names such as 2x LDPC.

[0244] For example, the above information / field may indicate whether 2x length LDPC is used. For example, the above information / field may be defined as 1 bit. For example, the above information / field may be implicitly indicated, in which case the information / field may be omitted.

[0245] CSD indication

[0246] For example, information / fields regarding CSD indications may be configured as follows. The above information / fields may be indicated by various names such as CSD indication.

[0247] For example, the above information may be information indicating the start of the CSD applied by the STA when transmitting a signal through the DRU. For example, the above information may consist of 3 bits. For example, the CSD used per DRU index can be fixed. In this case, the above information may be omitted as it is determined during DRU allocation by RU allocation.

[0248] Fifth technical feature

[0249] The following example proposes a specific user info field designed based on the aforementioned third technical feature and / or fourth technical feature.

[0250] An example of a user info field related to cases where EQM and RRU are applied is described below.

[0251] FIGS. 15 and 16 illustrate examples of user info fields related to cases where EQM and RRU are applied. The detailed sub-fields included in each figure may be identical to the information / fields described in the third technical feature and / or fourth technical feature described above.

[0252] For example, based on the nine sub-fields and one trigger-dependent user info field shown in Fig. 15, one user info field can be configured.

[0253] Additionally or generally, when considering an explicit indication for 2x LDPC, the UL Target Receive Power field can be defined as 6 bits to secure an indication bit for it, and the remaining 1 bit can be allocated as a 2x LDPC indication. For example, the 2x LDPC bit can be located after Nss. Alternatively, one user info field can be constructed based on the 10 sub-fields and one trigger-dependent user info field shown in FIG. 16.

[0254] An example of a user info field related to the application of EQM and DRU is described below. FIGS. 17 to 21 illustrate an example of a user info field related to the application of EQM and DRU. The detailed information / fields included in each figure may be based on the third technical feature and / or the fourth technical feature described above.

[0255] For example, based on the 10 Western fields and 1 trigger-dependent user info field shown in Fig. 17, one user info field can be configured.

[0256] Additionally or generally, when considering an explicit indication for 2x LDPC, the indication bit for this can be defined by allocating one bit of the reserved bits in the above format. For example, the subfield can be located after the UEQM or before the DBW (Distributed BW). When considering 2x LDPC using reserved bits as proposed above, the user info field can be as shown in FIG. 18. In other words, a single user info field can be constructed based on the 11 subfields and one trigger-dependent user info field shown in FIG. 18.

[0257] Additionally, or generally, to maintain consistency with the example in FIG. 15 and FIG. 16, it may be considered to define the UL Target Receive Power subfield as 6 bits and allocate the remaining one bit to the said field. In this case, the reserved 2 bits may be used as an indication for other features. Such an example can be embodied in FIG. 19. In other words, based on the 11 subfields and one trigger-dependent user info field shown in FIG. 19, one user info field may be constructed.

[0258] Additionally or generally, when considering a CSD indication during DRU transmission, the user info field can be configured as follows, depending on whether an indication for 2x LDPC is included. First, when considering 2x LDPC, the user info field can be configured based on an example in FIG. 19. In this case, to define a 3-bit CSD indication, the size of the UL Target Receive Power field can be defined as 5 bits. Such an example can be concretized through FIG. 20. In other words, a single user info field can be configured based on the 11 sub-fields and 1 trigger-dependent user info field shown in FIG. 20.

[0259] In addition, an example of FIG. 21 may be proposed when 2x LDPC is not considered. Specifically, since there is no need for an indication for 2x LDPC, the bits allocated to 2x LDPC in the example of FIG. 19 proposed above can be reused to construct the user info field. In other words, a single user info field can be constructed based on the 10 sub-fields and 1 trigger-dependent user info field shown in FIG. 21.

[0260] An example of a user info field related to the application of UEQM and RRU is described below. FIGS. 22 through 25 illustrate an example of a user info field related to the application of UEQM and RRU. The detailed information / fields included in each figure may be based on the third technical feature and / or the fourth technical feature described above.

[0261] For example, when transmitting UEQM through RRU, the user field can be configured as follows depending on whether it includes 2x LDPC indication.

[0262] First, in cases where 2x LDPC indications are not included, examples such as those in FIG. 22 are possible. As described above, since UEQM coding uses only LDPC, the UL FEC Coding Type field may be reserved. Alternatively, the UL FEC Coding Type may exist and be set to always 1 to indicate only LDPC. Since UEQM may not support MU-MIMO, in this case, the example in FIG. 15 may be utilized. Specifically, information regarding the Starting spatial stream may be fixed and omitted, and the bits for that information may be reconfigured to indicate new information, such as UEQM indication, UEQM pattern, and 2x LDPC.

[0263] Based on the above description, an example of FIG. 22 can be proposed. In other words, based on the 10 sub-fields and 1 trigger-dependent user info field shown in FIG. 22, one user info field can be configured.

[0264] Meanwhile, in the case of including 2x LDPC indications, examples such as those in FIG. 23 are possible. Specifically, the bit reserved in FIG. 22 can be allocated and used as a 2x LDPC indication. In other words, a single user info field can be configured based on the 10 sub-fields and one trigger-dependent user info field shown in FIG. 23.

[0265] For example, in the example of FIGS. 15 to 23, a 5-bit MCS subfield (e.g., UL UHR MCS) was proposed, but a 4-bit MCS subfield as shown in Table 4 below may be proposed. For example, an STA according to the present specification (e.g., AP, non-AP STA) may define / store individual MCS tables for EQM and UEQM. In this case, the size of each table may be 4 bits or 5 bits. For example, a 4-bit MCS table for UEQM may be configured as shown in Table 4, taking into account the UEQM pattern. The minimum MCS (MCS0) in Table 4 may be defined as QPSK 1 / 2.

[0266] MCS indexModulation and code rateMCS indexModulation and code rate0QPSK, 1 / 28256QAM, 3 / 4116QAM, 1 / 29256QAM, 5 / 6216QAM, 2 / 3101024QAM, 3 / 4316QAM, 3 / 4111024QAM, 5 / 6464QAM, 2 / 3124096QAM, 3 / 4564QAM, 3 / 4134096QAM, 5 / 6664QAM, 5 / 614Reserved7256QAM, 2 / 315Reserved

[0267] As shown in Table 4, when UEQM transmission is performed using a separately defined UEQM MCS 4 bit during UEQM, the configuration of the User info field can be defined as a 4-bit MCS field based on FIGS. 22 and 23. In this case, the remaining one bit is reserved and can be used to indicate a feature. Additionally, or generally, the MCS is defined as 4 bits (e.g., B21~B24), identical to the existing EHT variant user field, and the reserved B25 bit can be defined as a UEQM indication. Considering the above technical characteristics, an example of FIGS. 24 and 25 can be proposed.

[0268] For example, an example of FIG. 24 may be proposed in the case where 2x LDPC indications are not included. Alternatively, based on the 10 sub-fields and 1 trigger-dependent user info field shown in FIG. 24, one user info field may be configured.

[0269] For example, in the case of including 2x LDPC indications, an example of FIG. 25 may be proposed. Alternatively, based on the 11 sub-fields and 1 trigger-dependent user info field shown in FIG. 25, one user info field may be configured.

[0270] An example of a user info field related to the application of UEQM and DRU is described below. FIGS. 26 to 30 illustrate an example of a user info field related to the application of UEQM and DRU. The detailed information / fields included in each figure may be based on the third technical feature and / or the fourth technical feature described above.

[0271] When both UEQM and DRU are used, the user info field can be configured as shown in the example of FIG. 26, taking into account information regarding the UEQM pattern and DBW, and Nss=2 supported during DRU. For example, since UEQM uses only LDPC, the UL FEC Coding Type can be reserved. For example, the UEQM pattern subfield can be configured with 2 bits to ensure commonality with the user info field related to RRU. For example, since the maximum number of Nss supported during DRU transmission is 2, 1 bit can be allocated to the Nss field. Alternatively, considering the DRU transmission capacity, the UEQM pattern and Nss fields can each be configured with 1 bit, and the remaining one bit can be reserved and allocated for other feature indications.

[0272] Considering these technical features, a user info field as shown in FIG. 26 can be proposed. In other words, a single user info field can be constructed based on the 10 sub-fields and 1 trigger-dependent user info field shown in FIG. 26.

[0273] The example in Fig. 26 can be modified in various ways. For example, the UEQM pattern field can be configured to 1 bit and the Nss field can be configured to 2 bits, as in the existing example.

[0274] As another example of FIG. 26, an indication for 2x LDPC can be considered when UEQM and DRU are applied. Based on this, the 2x LDPC indication can be included in one bit reserved in the example of FIG. 26.

[0275] As another example of FIG. 26, considering the signaling commonality with the case where RRU is applied, the UEQM pattern subfield and the Nss subfield can each be configured with 1 bit of information, and the remaining 1 bit can be allocated for 2x LDPC indication.

[0276] In another example of FIG. 26, the NSS subfield applied to UEQM and DRU can be fixed to 2, so the corresponding NSS field can be omitted. In this case, the one bit remaining from the omission of the NSS field can be used for UHR feature indication, such as 2x LDPC.

[0277] An example of FIG. 27 is described below.

[0278] In the case of DRU, the CSD indication considered in the above proposal can be considered. For example, the length of the bit allocated to the UL Target Receive Power for the CSD indication can be reconfigured to 5 / 6. Based on an example in Fig. 26, the CSD indication can be included in the user info field by reducing the size of the UEQM pattern, Nss, and UL Target Receive Power subfield by 1 bit.

[0279] Considering these technical features, a user info field as shown in FIG. 27 can be proposed. In other words, a single user info field can be constructed based on the 11 sub-fields and one trigger-dependent user info field shown in FIG. 27.

[0280] The example in Fig. 27 can be modified in various ways.

[0281] In another example of FIG. 27, the NSS field may be omitted, and the bits allocated to the NSS field are used for CSD indication, and the UL Target Receive Power may be composed of 6 bits.

[0282] An example of Fig. 28 is described below.

[0283] In UEQM, the MCS table can be configured as a UEQM MCS table as described above, and the MCS field can be configured as 4 bits, just like the existing one. When a UEQM MCS table is defined separately and the MCS field is configured as 4 bits, the user info field can be defined based on FIG. 26.

[0284] Considering these technical features, a user info field as shown in FIG. 28 can be proposed. In other words, a single user info field can be constructed based on the 11 sub-fields and 1 trigger-dependent user info field shown in FIG. 28.

[0285] In the example of Fig. 28, the reserved bit can be allocated and used for the corresponding indication when indicating 2x LDPC.

[0286] Meanwhile, based on the example of FIG. 27, when a CSD indication is included during DRU transmission, the user info field for the indication can be configured as shown in FIG. 29. In other words, one user info field can be configured based on the 11 sub-fields and one trigger-dependent user info field shown in FIG. 29.

[0287] In the example of FIG. 29, when considering a 2x LDPC indication, the UL Target Receive Power is composed of 6 bits, and the User info field can be configured as shown in FIG. 30. In other words, one user info field can be configured based on the 12 sub-fields and one trigger-dependent user info field shown in FIG. 30.

[0288] The order of each subfield shown in the above user info field can be changed in various ways.

[0289] 6. Technical Features

[0290] The user info field described above can be modified in various ways. For example, it is possible to combine two user info fields to form an Extended user info field.

[0291] In 11bn / UHR, signaling for the corresponding features via a trigger frame may be required in order for the UL to perform signal transmission using various features defined in 11bn / UHR as described above (e.g., UEQM, 2x LDPC, New MCS, DRU). Considering the bit allocation of the trigger frame for signaling for such various 11bn / UHR features, the 11bn / UHR variant trigger frame may consist of two user info fields per STA. The extended user info field may be referred to by other names. For example, it may be referred to by various names such as the first / second / UHR / enhanced user info field.

[0292] For example, the Extended user info field may include, for example, two user info fields. For example, a UHR / 11bn variant Trigger frame containing the Extended user info field may include at least one of the following technical features.

[0293] For example, since the Extended user info field contains two user info fields, it may include two AID subfields (e.g., a 12-bit AID12 subfield). For example, the two AID subfields may have the same AID (or value).

[0294] For example, among the two user info fields included in a single Extended user info field, the 4-bit starting spatial stream information of the SS allocation subfield included in the first user info field can be reconfigured into 3 bits in the 11bn / UHR variant trigger frame. In this case, the remaining 1 bit can be allocated, for example, for a UEQM / EQM indication. For example, the said 1-bit UEQM / EQM indication can be located after the UHR MCS subfield.

[0295] For example, among the two user info fields included in a single Extended user info field, the second user info field may be configured to include an indication for the 11bn / UHR features considered above. In this case, the second user info field may include at least one of the subfields related to the UEQM pattern, 2x LDPC, CSD indication, and DBW described above. For example, the remaining bit(s) after the indication information for the 11bn / UHR features is allocated may be allocated as reserved bit(s) or used to define additional other features. In this case, the reserved bit(s) may be set to zero (0) or one (1). For example, the reserved bit(s) may be used for an indication of new features defined in the next Wi-Fi (e.g., a new wireless LAN system defined after the UHR system). In this case, the value of the PHY version identifier included in the special user info field of the corresponding Trigger frame may be set to two (2) or higher.

[0296] FIG. 31 illustrates an example of an Extended user info field related to the present specification. An Extended user info field of the present specification, including an example such as FIG. 31, may include two user fields within an 11bn / UHR variant trigger frame. This allows for the configuration of a consistent user info field without being limited to 11bn / UHR features. In other words, implementation complexity can be reduced by configuring a consistent user info field regardless of 11bn / UHR features. Alternatively, since a single Extended user info field is configured based on two user info fields as described above, the user info field can be consistently configured regardless of the triggering transmission feature.

[0297] An example of this specification is not limited to the example of FIG. 31 and can be modified in various ways.

[0298] For example, FIG. 32 illustrates another example of an Extended user info field related to the present specification. For example, among the two user info fields included in a single Extended user info field, the first user info field can indicate whether the user info field is extended (or whether a second user info field exists). For example, the indication information is located in the first user info field and consists of 1 bit to indicate the existence of a second user info field. When the value of the indication information is set to a first value (e.g., 1), a second user info field consecutive to the first user info field may be included. For example, the indication information may be referred to by various names such as Extension bit / field / information, extension presence bit / information / field, control bit / information / field, etc. For example, since the existence of the second user info field is indicated through the Extension bit, when normal transmission is performed without using the new feature defined in 11bn, it can be composed of one user info field, identical to the existing user info field. This allows inheriting existing operations and reducing signaling overhead.

[0299] For example, the 1 bit allocated to indicate the extended / extension presence can be indicated using the 1 bit allocated to indicate the proposal and UEQM. For example, the UEQM indication can be included in the second user info field among the two user info fields included in one Extended user info field.

[0300] The concept of the Extended user info field described above may also be applied to the special user info field of the 11bn / UHR variant trigger frame. In other words, an extended special user info field containing two special user info fields may be included, and information related to 11bn / UHR features (information related to UEQM, additional MCS, 2x LDPC, and / or DRU, etc.) may be included in the second special user info field included within the extended special user info field.

[0301] FIG. 33 is an example of a procedure flowchart related to the present specification.

[0302] As in step S3310, the STA can generate a trigger frame. For example, the STA in step S3310 may be an AP. The trigger frame may be a frame related to UL MU communication and may be a frame soliciting a TB PPDU (trigger-based physical protocol data unit). For example, the trigger frame may be included within the Data field of a downlink PPDU.

[0303] For example, the trigger frame may sequentially include a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field.

[0304] For example, the above common information field may include information related to UHR PHY features. Specifically, information related to UHR PHY features, such as a DRU (distributed-tone resource unit), may be included in the above common information field.

[0305] For example, the common information field may include a 4-bit subfield. For example, the 4-bit subfield may include information regarding whether a distributed-tone resource unit (DRU) is solicited or a regular resource unit (RRU) is solicited by the trigger frame. For example, the 4-bit subfield may include a first bit regarding whether a DRU is applied to a first 80 MHz frequency subblock related to the TB PPDU, a second bit regarding whether a DRU is applied to a second 80 MHz frequency subblock related to the TB PPDU, a third bit regarding whether a DRU is applied to a third 80 MHz frequency subblock related to the TB PPDU, and a fourth bit regarding whether a DRU is applied to a fourth 80 MHz frequency subblock related to the TB PPDU.

[0306] For example, the above common information field may include various features corresponding to the first technical feature described above.

[0307] For example, the special user info field may include a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield may include information regarding whether the TB PPDU (solicited trigger-based physical protocol data unit) requested by the trigger frame is related to UHR. Alternatively, the 3-bit PHY version ID (identifier) ​​subfield may include information regarding whether the Trigger frame (or the common info field) is related to UHR (or UHR Variant). For example, the 3-bit PHY version ID (identifier) ​​subfield may have a value of 1 (1) if the solicited TB PPDU, Trigger frame, and / or common info field is related to UHR (or UHR Variant).

[0308] For example, the special user information field may include various features corresponding to the second technical feature described above. As described above, the special user information field may be consecutive to the common information field, and the special user information field may include a 12-bit subfield having a value of 2007, and the PHY version ID subfield may be consecutive to the 12-bit subfield.

[0309] For example, the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield may include information regarding whether unequal modulation (UEQM) is applied to the TB PPDU. The above UHR variant user information field has been described in this specification using various terms such as user info field.

[0310] The above UHR variant user information field may include various features corresponding to the third to sixth technical features. For example, the above UHR variant user information field may be defined through various user info fields (or extended user info fields) corresponding to FIGS. 15 to 32.

[0311] As in step S3320, the STA can transmit a trigger frame. The user STA that receives the trigger frame can construct a TB-PPDU based on the trigger frame and transmit it over the uplink. The STA may additionally perform the step of receiving the TB-PPDU.

[0312] FIG. 34 is an example of a procedure flowchart related to the present specification.

[0313] As in step S3410, the STA may receive a trigger frame. The STA in step S3410 may be a non-AP STA. The trigger frame in step S3410 may be the trigger frame described in step S3310. For convenience of explanation, redundant descriptions regarding the trigger frame are omitted.

[0314] As in step S3420, the STA may transmit a TB-PPDU based on a received trigger frame. The TB-PPDU is transmitted over the uplink and may be configured based on UHR PHY Features (e.g., UEQM, additional MCS, 2x LDPC, and / or DRU) indicated in the trigger frame.

[0315] The technical features of this specification may be performed by various devices. The device of this specification may be the device described in FIG. 1 / 14. The device of this specification may include at least one processor; and at least one computer memory that is operabably connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor.

[0316] For example, the processor may be the processor described in FIG. 1 and / or FIG. 14. That is, as described above, the processor of this 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 includes computers having various architectures, such as single / multi-processor architectures and sequential (Von Neumann) / parallel architectures, as well as specialized circuits such as FPGAs, ASICs, signal processing units, and other devices. For example, the processor of this 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 enhanced therefrom.

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

[0318] The computer program(s) defined by the above instruction may arrive at the device of this specification (e.g., STA) through 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 manufactured product that tangibly embodies the computer program. The delivery mechanism may be a signal configured to reliably transmit the computer program via a wireless or electrical connection.

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

[0320] For example, the memory described above 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 regarding signals transmitted and received by the STA (e.g., PPDU containing a management / control / data frame).

[0321] The technical features of this specification may be implemented in at least one computer-readable medium (CRM). The CRM includes instructions based on execution by at least one processor described above. Instructions stored in the CRM may be the computer program instructions described above.

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

[0323] The technical features of the present specification described above are applicable to various applications or business models. For example, the technical features described above may be applied for wireless communication in devices supporting Artificial Intelligence (AI).

[0324] Artificial intelligence refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems addressed within the field of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0325] An Artificial Neural Network (ANN) is a model used in machine learning that can refer to any model capable of problem-solving, composed of artificial neurons (nodes) that form a network through the connection of synapses. An artificial neural network can be defined by connection patterns between neurons in different layers, a learning process that updates model parameters, and an activation function that generates output values.

[0326] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer may include one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron may output a function value of an activation function for input signals, weights, and biases input through the synapses.

[0327] Model parameters refer to parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters, on the other hand, refer to parameters that must be set prior to training in a machine learning algorithm, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0328] The objective of training an artificial neural network can be viewed as determining model parameters that minimize the loss function. The loss function can be used as an indicator to determine optimal model parameters during the training process of an artificial neural network.

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

[0330] Supervised learning refers to a method of training an artificial neural network with labels provided for the training data; a label can refer to the correct answer (or result) that the neural network must infer when the training data is input. Unsupervised learning refers to a method of training an artificial neural network without labels provided for the training data. Reinforcement learning refers to a learning method in which an agent defined within an environment is trained to select an action or sequence of actions that maximizes the cumulative reward in each state.

[0331] Machine learning implemented using a Deep Neural Network (DNN) that includes multiple hidden layers among artificial neural networks is also called Deep Learning, and Deep Learning is a part of Machine Learning. Hereinafter, Machine Learning is used in a sense that includes Deep Learning.

[0332] In addition, the aforementioned technical features can be applied to the wireless communication of robots.

[0333] A robot can refer to a machine that automatically processes or operates a given task based on its own capabilities. In particular, a robot that has the ability to perceive its environment, make decisions on its own, and perform actions can be called an intelligent robot.

[0334] Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, and propellers in their drive units, enabling them to drive on the ground or fly in the air.

[0335] In addition, the aforementioned technical features can be applied to devices that support augmented reality.

[0336] Extended Reality is a collective term for Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on real-world images, and MR technology is a computer graphics technology that mixes and combines virtual objects with the real world.

[0337] MR technology is similar to AR technology in that it displays real-world objects and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual objects and real-world objects are used as equals in MR technology.

[0338] XR technology can be applied to HMDs (Head-Mount Displays), HUDs (Head-Up Displays), 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 trigger frame, but, The above trigger frame includes a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field, wherein The above common information field includes a 4-bit subfield, and the 4-bit subfield includes information regarding whether a DRU (distributed-tone resource unit) or a RRU (regular resource unit) is solicited by the trigger frame. The above special user information field includes a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield includes information regarding whether the TB PPDU (solicited trigger-based physical protocol data identity) requested by the trigger frame is related to UHR, and Step, wherein the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield includes information related to whether UEQM (unequal modulation) is applied to the TB PPDU; and Step of transmitting the above trigger frame A method including 2. In Paragraph 1, The above 4-bit subfield comprises a first bit regarding whether a DRU is applied to a first 80MHz frequency subblock related to the TB PPDU, a second bit regarding whether a DRU is applied to a second 80MHz frequency subblock related to the TB PPDU, a third bit regarding whether a DRU is applied to a third 80MHz frequency subblock related to the TB PPDU, and a fourth bit regarding whether a DRU is applied to a fourth 80MHz frequency subblock related to the TB PPDU. Method of including.

3. In Paragraph 1, The above special user information field is continuous with the above common information field, and The above special user information field includes a 12-bit subfield having a value of 2007, and The above PHY version ID subfield is consecutive to the above 12-bit subfield method.

4. In Paragraph 1, The above UHR variant user information field is continuous with the above special user information field, and The above UHR variant user information field includes a 12-bit AID (Association ID) subfield, an 8-bit RU (Resource Unit) allocation subfield, a 1-bit uplink FEC (Forward Error Correction) coding type subfield, a 5-bit uplink MCS (Modulation and Coding Scheme) subfield, a 1-bit 2xLDPC subfield related to the length of the LDPC (low density parity check) codeword, a 7-bit uplink target receive power subfield, and a 1-bit segment subfield indicating a 160 MHz segment of the uplink RU. method.

5. In Paragraph 1, Step of receiving a TB PPDU solicited by the above trigger frame including more method.

6. At least one processor; and It includes at least one computer memory that is operablely connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, Create a trigger frame, but The above trigger frame includes a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field, wherein The above common information field includes a 4-bit subfield, and the 4-bit subfield includes information regarding whether a DRU (distributed-tone resource unit) or a RRU (regular resource unit) is solicited by the trigger frame. The above special user information field includes a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield includes information regarding whether the TB PPDU (solicited trigger-based physical protocol data identity) requested by the trigger frame is related to UHR, and Step, wherein the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield includes information related to whether UEQM (unequal modulation) is applied to the TB PPDU; and Step of transmitting the above trigger frame including STA(station) that performs an operation.

7. In Paragraph 6 The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 1 to 5. STA.

8. Receive a trigger frame via STA, but The above trigger frame includes a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field, wherein The above common information field includes a 4-bit subfield, and the 4-bit subfield includes information regarding whether a DRU (distributed-tone resource unit) or a RRU (regular resource unit) is solicited by the trigger frame. The above special user information field includes a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield includes information regarding whether the TB PPDU (solicited trigger-based physical protocol data identity) requested by the trigger frame is related to UHR, and Step, wherein the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield includes information related to whether UEQM (unequal modulation) is applied to the TB PPDU; and The step of transmitting the TB PPDU based on the trigger frame by the above STA A method including 9. In Paragraph 8 The above STA performs an operation related to any one of claims 1 to 5. method.

10. At least one processor; and It includes at least one computer memory that is operablely connectable to the at least one processor and stores instructions that perform operations based on execution by the at least one processor, The above-mentioned instruction of at least one computer memory is, Receive a trigger frame via STA, The above trigger frame includes a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field, wherein The above common information field includes a 4-bit subfield, and the 4-bit subfield includes information regarding whether a DRU (distributed-tone resource unit) or a RRU (regular resource unit) is solicited by the trigger frame. The above special user information field includes a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield includes information regarding whether the TB PPDU (solicited trigger-based physical protocol data identity) requested by the trigger frame is related to UHR, and Step, wherein the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield includes information related to whether UEQM (unequal modulation) is applied to the TB PPDU; and The step of transmitting the TB PPDU based on the trigger frame by the above STA including STA(station) that performs an operation.

11. In Paragraph 10 The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 1 to 5. STA.

12. In a wireless local area network (WLAN) system, at least one computer-readable medium comprising an instruction based on execution by at least one processor, Create a trigger frame, but The above trigger frame includes a common info field, a special user info field, and an ultra-high reliability (UHR) variant user info field, wherein The above common information field includes a 4-bit subfield, and the 4-bit subfield includes information regarding whether a DRU (distributed-tone resource unit) or a RRU (regular resource unit) is solicited by the trigger frame. The above special user information field includes a 3-bit PHY version ID (identifier) ​​subfield, and the PHY version ID subfield includes information regarding whether the TB PPDU (solicited trigger-based physical protocol data identity) requested by the trigger frame is related to UHR, and Step, wherein the above UHR variant user information field includes a 1-bit subfield, and the 1-bit subfield includes information related to whether UEQM (unequal modulation) is applied to the TB PPDU; and Step of transmitting the above trigger frame Performing an operation that includes Recording media.

Images