Signaling technique of data unit

WO2026168911A1PCT designated stage Publication Date: 2026-08-13LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2026-02-03
Publication Date
2026-08-13

Smart Images

  • Figure KR2026001937_13082026_PF_FP_ABST
    Figure KR2026001937_13082026_PF_FP_ABST
Patent Text Reader

Abstract

The present specification relates to a technology for improving a signal field structure of a physical protocol data unit (PPDU) in a wireless communication system. In one embodiment, a station (STA) generates a DL PPDU for downlink communication, and the DL PPDU includes a first signal field and a second signal field. The second signal field can include a common field and a user specific field. The common field includes control information for orthogonal frequency division multiple access (OFDMA) transmission, and includes first information related to whether at least one resource unit (RU) related to the DL PPDU uses multi-user multiple input multiple output (MU-MIMO). On the basis of the first information, the user specific field can include a user field related to MU-MIMO allocation. Therefore, a receiving STA can clearly recognize whether MU-MIMO is applied to a specific RU or MRU during OFDMA transmission such that transmission errors can be reduced and reception performance can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Signaling techniques for data units

[0001] This specification relates to wireless communication systems, and more specifically, to operations and devices based on improved signal fields in wireless LAN systems.

[0002] Wireless LANs or WLANs (wireless local area networks) 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] One of the various objectives of this specification is to improve the signal field structure of a physical protocol data unit (PPDU) in a wireless communication environment where orthogonal frequency division multiple access (OFDMA) and multi-user multiple input multiple output (MU-MIMO) are mixed, thereby enabling a receiving station (STA) to more clearly recognize the transmission method. In particular, it aims to resolve interpretation errors that occur when the application of MU-MIMO is not clearly conveyed in situations where multiple resource units (RU) or multiple resource units (MRU) are allocated.

[0007] Another objective among the various objectives of this specification is to improve the efficiency of transmitting control information for the interpretation of the PPDU by including information regarding whether MU-MIMO is used in the common field of the second signal field among the first signal field and the second signal field included in the DL PPDU (downlink PPDU). Through this, the purpose is to enable the receiving STA to preemptively identify the transmission structure at a stage prior to interpreting the user-specific field.

[0008] Another objective among the various objectives of this specification is to define first information that clearly indicates when MU-MIMO transmission is performed at a specific RU or MRU, and to provide a signaling structure that optionally includes a user field regarding MU-MIMO allocation in a user-specific field based on said first information. By doing so, the aim is to provide a signal field structure that can flexibly respond to various transmission scenarios.

[0009] The technical features of this specification relate to improving the signal field of a PPDU (physical protocol data unit).

[0010] For example, a STA (station) according to the present specification can generate / configure a PPDU including a signal field of an improved structure. For example, the PPDU may be a DL PPDU for downlink communication.

[0011] For example, the DL PPDU may include a first signal field and a second signal field. For example, the first signal field may include information for interpreting the DL PPDU. For example, the second signal field may include a common field and a user-specific field.

[0012] For example, the common field may include multiple subfields for OFDMA (orthogonal frequency division multiple access) transmission. For example, the user-specific field may include a user field related to OFDMA allocation.

[0013] For example, the common field may include first information regarding whether at least one resource unit (RU) associated with the DL PPDU uses MU-MIMO.

[0014] For example, based on the fact that at least one resource unit (RU) associated with the above DL PPDU uses the multi-user multiple input multiple output (MU-MIMO), the first information may have a first value. For example, based on the fact that the first information has the first value, the user specific field may further include a user field related to MU-MIMO allocation.

[0015] According to the configuration of the present specification, since the common field of the Ultra High Reliability Signal (UHR-SIG) can clearly indicate whether MU-MIMO is applied to a specific RU or MRU during OFDMA transmission, a non-AP STA receiving this can immediately recognize the transmission method of the corresponding RU / MRU in the initial stage of PPDU reception. Accordingly, the possibility of reception failure due to misidentification of the transmission structure is effectively reduced.

[0016] In addition, by including first information regarding whether MU-MIMO is applied in the common field, unnecessary estimation or complex judgment processes can be reduced during the interpretation of the user-specific field. This alleviates the complexity of receiving processing in the STA and provides the effect of reducing the time and computational resources required for interpreting control information.

[0017] Furthermore, the signal field structure according to the present specification can support stable transmission even in high-density AP environments or multi-user environments where OFDMA and MU-MIMO are mixed. Accordingly, technical effects such as reduced transmission errors, improved system processing efficiency, and improved overall wireless communication performance can be achieved.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0032] FIG. 15 is an example of a SIG field configured according to an example of the present specification.

[0033] FIG. 16 is a flowchart of the procedure related to the technical features of the present specification.

[0034] FIG. 17 is another example of a flowchart of a procedure related to the technical features of the present specification.

[0035] 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.”

[0036] 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.”

[0037] 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.”

[0038] 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.”

[0039] 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.”

[0040] 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.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0097] 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}.

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

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

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

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

[0102] 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".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0120] 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 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0156] One example of this specification relates to MU-MIMO (Multi-User Multiple-Input Multiple-Output) and OFDMA (Orthogonal Frequency Division Multiple Access) used in wireless LAN systems.

[0157] For example, the above MU-MIMO is a multi-user transmission technology that utilizes a spatial domain, and may refer to a method in which an AP uses multiple antennas to simultaneously transmit different spatial streams to different users. Specifically, multiple users can receive data through different beams or spatial channels within the same frequency band and the same time interval. For example, the above MU-MIMO may be based on beamforming based on Channel State Information (CSI), and may have the characteristic that transmission efficiency improves as spatial orthogonality between users is secured.

[0158] For example, the above OFDMA is a technology that supports multiple users by dividing the frequency domain, dividing a single channel bandwidth into multiple resource units (RUs), and allocating each RU to different users to perform simultaneous transmission. For example, in OFDMA, when each user (e.g., each non-AP STA) uses a different subcarrier set, interference between users is minimized, which is advantageous for reducing latency and increasing channel utilization in environments where small amounts of data are frequently transmitted and received.

[0159] For example, the above MU-MIMO aims to increase 'transmission speed and capacity' through spatial multiplexing, and the above OFDMA can achieve simultaneous connection efficiency and low latency for multiple devices through frequency division multiplexing.

[0160] For example, the device of this specification (e.g., AP, non-AP STA, AP MLD, non-AP MLD) may adaptively select or combine the MU-MIMO mode and OFDMA mode based on the type of traffic (e.g., UL or DL ​​traffic), the size of the data, and the density information of the connected station.

[0161] Specifically, in UHR systems and / or Next Wi-Fi systems (e.g., systems improved or evolved from UHR systems), signals can be transmitted by applying MU-MIMO to the large-size RU / MRU allocated during OFDMA transmission in order to increase high throughput and spectral efficiency. In order to transmit signals by applying MU-MIMO to the large-size RU / MRU allocated during OFDMA transmission in this manner, a configuration of UHR-SIG is required to efficiently indicate this. This specification may propose an improved configuration of the UHR-SIG field for transmission in which OFDMA and MU-MIMO are applied together.

[0162] The technical features of this specification may be expressed in various terms. For example, if only MU-MIMO is applied to a single PPDU (e.g., UL-PPDU or DL-PPDU), it may be expressed that Full Bandwidth MU-MIMO is applied to that PPDU. For example, if OFDMA is applied together with MU-MIMO to a single PPDU (e.g., UL-PPDU or DL-PPDU), it may be expressed that Partial Bandwidth MU-MIMO is applied to that PPDU. Specifically, when OFDMA is used together with MU-MIMO, various terms such as Partial Bandwidth MU-MIMO may be used, as it can be expressed that MU-MIMO is applied to a specific bandwidth and OFDMA is applied to the remaining bandwidth.

[0163] For example, for transmissions performed in a UHR system or next wi-fi system, MU-MIMO application can be applied to 242 tone RUs or a BW of 20 MHz or more, just as in 11be (or 11ax). Additionally, MU-MIMO applied during OFDMA transmission can also be applied to RU / MRUs of 242 tone RUs or more, just like this. In other words, an example is possible where the RU / MRU for Partial Bandwidth MU-MIMO is limited only to 242 tone RUs or more.

[0164] For example, transmission in which OFDMA and MU-MIMO are applied together is applicable for a bandwidth of 80 MHz or more, and the RU / MRU to which MU-MIMO is applied for each bandwidth can be applied as follows. In addition, for a bandwidth of 80 MHz or more, OFDMA and MU-MIMO can be applied separately for each 80 MHz. In other words, the RU and MRU supported on partial BW DL MU-MIMO and / or partial BW UL MU-MIMO can be defined as follows.

[0165] RU / MRU for MU-MIMO in OFDMA

[0166] For example, for 80 MHz (transmit / receive), the following RU / MRU may be supported / selected for MU-MIMO in OFDMA. In other words, within a PPDU with a bandwidth of 80 MHz, the RUs for partial BW DL MU-MIMO and / or partial BW UL MU-MIMO may be as follows.

[0167] RU / MRU for 80 MHz:

[0168] 484+242-tone MRU (for non-punctured case)

[0169] For example, for 160 MHz (transmit / receive), the following RU / MRU may be supported / selected for MU-MIMO in OFDMA. In other words, within a PPDU with a bandwidth of 160 MHz, the RUs for partial BW DL MU-MIMO and / or partial BW UL MU-MIMO may be as follows.

[0170] RU / MRU for 160 MHz:

[0171] 484+242-tone MRU

[0172] 996+484-tone MRU

[0173] 996+484+242-tone MRU (for non-punctured case)

[0174] For example, for 320 MHz (transmit / receive), the following RU / MRU may be supported / selected for MU-MIMO in OFDMA. In other words, within a PPDU with a bandwidth of 320 MHz, the RUs for partial BW DL MU-MIMO and / or partial BW UL MU-MIMO may be as follows.

[0175] RU / MRU for 320 MHz:

[0176] 484+242-tone MRU

[0177] 996+484-tone MRU

[0178] 996+484+242-tone MRU

[0179] 2×996-tone MRU

[0180] 2×996+484-tone MRU

[0181] 2×996+484-tone MRU

[0182] 3×996-tone MRU

[0183] 3×996+484-tone MRU (for non-punctured case)

[0184] When MU-MIMO is applied to some RU / MRUs during OFDMA using the RU / MRUs defined or selected as above, the UHR-SIG field may be improved as follows. For example, the common field of the UHR-SIG field may be defined as "Common field for OFDMA transmission" as defined in 11be to include RU allocation information. In other words, when Partial BW DL MU-MIMO is applied, RU allocation information for the RU / MRUs used in the Partial BW DL MU-MIMO may be included in the Common field for OFDMA transmission. In this case, to indicate whether MU-MIMO was applied during OFDMA transmission (or whether Partial BW DL MU-MIMO was applied), it may be configured to include the following information.

[0185] Information 1: MU-MIMO support

[0186] The above first information may be referred to by various names. For example, it may be referred to by various names such as N-th information / field / subfield, Partial BW information / field / subfield, Partial BW MU-MIMO information / field / subfield.

[0187] An example in which the first information is included in the UHR-SIG field is described below. However, the name of the UHR-SIG field may also be changed. For example, the UHR-SIG may be called by various names such as the N-th signal field, may be called a signal field including a common field and a User Specific field, and may include RU allocation information for RU / MRU of various sizes.

[0188] The above information (e.g., MU-MIMO support information) included in the common field (for OFDMA transmission) of the UHR-SIG field indicates whether MU-MIMO is applied during OFDMA transmission.

[0189] For example, the first information above can be configured in various ways and can indicate other information other than the MU-MIMO support.

[0190] For example, the first information may have various lengths. For example, the first information may have a length of 1 bit. For example, if the first bit has a first value (e.g., zero), it may indicate that MU-MIMO is included (including RU / MRU related to Partial BW MU-MIMO). For example, if the first bit has a second value (e.g., one), it may indicate that MU-MIMO is not included during OFDMA transmission (including RU / MRU related to Partial BW MU-MIMO).

[0191] The first information may be included in the UHR-SIG field or in various locations / bits of the common field of the UHR-SIG field. For example, the first information may be included in the common field for OFDMA transmission within the UHR-SIG. More specifically, the first information may be included in the Disregards bit defined within the common field for OFDMA transmission included in the UHR-SIG.

[0192] For example, the first information may be assigned / located to any one of the disregard bits (e.g., bits B13 to B15) defined in the Common field for OFDMA transmission. For example, the first information may be included in bit B13 within the Common field for OFDMA transmission.

[0193] The Common field in this specification may be defined for at least two types of transmission. For example, the Common field may be defined for OFDMA transmission, in which case it may be called the Common field for OFDMA transmission. For example, the Common field may be defined for MU-MIMO transmission and / or SU-transmission, in which case it may be called the Common field for non-OFDMA transmission.

[0194] An example of a common field for OFDMA transmission is described below.

[0195] For example, bits B0 through B3 of the Common field for OFDMA transmission may be a subfield for Spatial Reuse. Such subfields may include information regarding whether Spatial Reuse is permitted during the transmission of the associated PPDU.

[0196] For example, bits B4 to B5 of the Common field for OFDMA transmission may be subfields for GI and LTF Size. For example, the subfield may have a value of zero (0) to indicate 2x LTF + 0.8 μs GI, a value of one (1) to indicate 2x LTF + 1.6 μs GI, a value of two (2) to indicate 4x LTF + 0.8 μs GI, and a value of three (3) to indicate 4x LTF + 3.2 μs GI.

[0197] For example, bits B6 through B8 of the Common field for OFDMA transmission may be a subfield indicating the number of LTF symbols.

[0198] For example, the B9 bit of the Common field for OFDMA transmission may be a subfield related to the existence of an LDPC extra symbol segment.

[0199] For example, bits B10 to B11 of the Common field for OFDMA transmission may be subfields indicating pre-FEC padding factors (e.g., 1 / 2 / 3 / 4).

[0200] For example, the B12 bit of the Common field for OFDMA transmission may be a subfield indicating PE (Packet extension) disambiguity.

[0201] For example, the B13 bit of the Common field for OFDMA transmission may be the first information mentioned above.

[0202] For example, bits B14 to B16 of the Common field for OFDMA transmission are Disregard subfields, and all bits can have a value of 1 (1).

[0203] For example, after the B17 bit of the Common field for OFDMA transmission, information related to RU allocation, a 4-bit CRC, a 6-bit Tail, etc. may be included.

[0204] Unnecessary errors can be reduced through the information presented in this specification (e.g., MU-MIMO support information). Specifically, the above embodiment makes it possible to indicate through the common field (of UHR-SIG) that MU-MIMO transmission is performed for a specific RU / MRU during OFDMA transmission. For example, when a non-AP STA receives such information (e.g., MU-MIMO support information), it can accurately determine that MU-MIMO has been applied to a specific RU / MRU during OFDMA transmission, thereby accurately obtaining information about the RU / MRU to which MU-MIMO has been applied. If such information (e.g., MU-MIMO support information) is not provided, the non-AP STA can only confirm that OFDMA is applied based on the received common field; therefore, it cannot prepare for MU-MIMO decoding in advance, which may result in errors in MU-MIMO transmission and reception. In other words, through the explicit information fields mentioned above, non-AP STAs can immediately identify that MU-MIMO has been applied to a specific RU / MRU during OFDMA transmission, thereby reducing transmission errors.

[0205] In addition, as described above, through the indication of whether MU-MIMO is applied in the common field (e.g., MU-MIMO support information), a non-AP STA can determine that the configuration of the user field for OFDMA transmission is not a single format. Specifically, when transmitting OFDMA + MU-MIMO, the user field of the UHR-SIG may be composed of two user field formats (e.g., non-MU-MIMO allocation and an MU-MIMO allocation) mixed together, rather than a single format.

[0206] FIG. 15 is an example of a SIG field configured according to an example of the present specification. As described above, the SIG field may have various names, such as UHR-SIG field. As illustrated, the SIG field according to the present specification may include one Common field and one user-specific field. For example, the B13 bit of the Common field may include the first information described above (e.g., MU-MIMO support information). For example, the Common field may be configured in a format for OFDMA transmission. In other words, the Common field may be a Common field for OFDMA transmission. For example, the user-specific field of FIG. 15 may include a plurality of user fields. Each user field may be configured according to either a first format considering MU-MIMO transmission or a second format considering OFDMA transmission. For example, a user field based on the first format above may be called a user field for a MU-MIMO allocation, and a user field based on the second format above may be called a use field for a non-MU-MIMO allocation.

[0207] As shown in the example in FIG. 15, when MU-MIMO is supported during downlink OFDMA transmission (e.g., when partial BW DL MU-MIMO is applied), two different user field formats may be included within a single user-specific field. For example, user fields may be encoded in units of two. For example, user fields of different formats may be encoded together.

[0208] As described above, when transmitting a signal by applying MU-MIMO to a specific RU / MRU during OFDMA transmission, the common field is configured as a common field for OFDMA transmission and may not include information indicating the number of users assigned to the RU / MRU to which MU-MIMO is applied. In this case, information regarding the number of non-AP STAs / Users receiving the signal via MU-MIMO can be indicated through RU allocation. In other words, information regarding the number of non-AP STAs related to downlink MU-MIMO can be indicated by the 9-bit RU Allocation subfield of the common field.

[0209] For example, when a PPDU (e.g., DL-PPDU) has a bandwidth of 160 MHz and partial BW DL MU-MIMO is applied (e.g., OFDMA + MU-MIMO transmission at 160 MHz), MU-MIMO may be applied to 996+(484+242-tone MRU). In this case, the number of users allocated to the 996-tone RU and the 484+242-tone MRU (e.g., the number of MU-MIMO users) can be determined through the corresponding 9-bit RU allocation. For example, the RU allocation subfield corresponding to the 996 RU may have a value of 80 to 87. Additionally, the corresponding B8 to B0 bits may be represented as 8 bits of 001010y2y1y0. The meaning of 3 bits (e.g., y2, y1, and y0) among the 8 bits can be redefined considering OFDMA+MU-MIMO. For example, as shown in Table 1 below, if the RU allocation subfield corresponding to 996 RU has a value of 80, bits y2 through y0 all have a value of 0, which can indicate that one user is allocated based on MU-MIMO. For example, as shown in Table 1 below, if the RU allocation subfield corresponding to 996 RU has a value of 81, bits y2 and y1 both have a value of 0, and bit y0 can have a value of 1, which can indicate that two users are allocated based on MU-MIMO. According to the above technique, the number of users (e.g., non-AP STA) allocated by MU-MIMO applied to 996+(484+242-tone MRU) (i.e., partial BW is MU-MIMO) can be determined through the corresponding 9-bit RU allocation.

[0210] Value for RA subfield of 996 tone RUNumber of user801812823834845856867878

[0211] For RU / MRU of different sizes defined above, the number of users to whom MU-MIMO is applied can be identified by using the value of the RA field (e.g., the value of the 9-bit RA field) in the same way as defined above.

[0212] For example, the example described above can be modified in various ways. For instance, unlike the method of separately indicating OFDMA+MU-MIMO through separate bits in the common field of UHR-SIG, the indication for OFDMA+MU-MIMO transmission can be indicated through the value of the RA subfield. Specifically, it is possible to indicate information related to OFDMA+MU-MIMO transmission based on the value of the 9-bit RA subfield without defining additional bits in the common field.

[0213] For example, when MU-MIMO is applied to a specific size RU / MRU during OFDMA transmission, the RA subfield for that RU can be set to a different value than the RA subfield value representing a single user as shown in Table 1, thereby simultaneously indicating that MU-MIMO is applied to that RU / MRU and the number of users.

[0214] As described above, through the RA field, the non-AP STA can determine whether OFDMA+MU-MIMO transmission is occurring, and can also recognize that the configuration of the user field is not a single format but rather two user field formats (e.g., a user field format related to non-MU-MIMO allocation and another user field format related to MU-MIMO allocation) are mixed together.

[0215] FIG. 16 is a flowchart of a procedure related to an example of the present specification. The operation of FIG. 16 can be performed by various devices (e.g., AP, AP MLD, non-AP STA, non-AP MLD).

[0216] As in step S1610, the STA (e.g., AP) can generate a DL (downlink) PPDU (physical protocol data unit). For example, the PPDU may be a UHR PPDU or a new PPDU generated based on a PHY version after UHR.

[0217] The above DL-PPDU may include a first signal field and a second signal field. For example, the first signal field may include information for interpreting the DL PPDU. For example, the first signal field may be a U-SIG field. Accordingly, the first signal field may be composed of two symbols and may include various version independent bis, such as a PHY version identifier.

[0218] For example, the second signal field may be a UHR-SIG field or a signal field that is an improved version of the UHR-SIG field. The second signal field may follow the first signal field. Accordingly, the second signal field may be located immediately after the first signal field. Accordingly, additional fields may be defined between the first signal field and the second signal field. For example, the second signal field may include resource allocation information for a STA (station) associated with the DL-PPDU. For example, the second signal field may include allocation information for a RU included in the DL-PPDU (e.g., a 9-bit length RU allocation subfield).

[0219] Additionally or generally, the second signal field may include a common field and a user-specific field. The common field may include an overflow bit that is not included in the first signal field. The overflow bit may be referred to by various names, for example, as a U-SIG overflow bit. For example, the overflow bit may include information common to all STAs associated with the DL-PPDU.

[0220] The above common field may be configured based on two types / formats. For example, the first type / format may include multiple subfields for OFDMA (orthogonal frequency division multiple access) transmission. The common field of the first type / format may be referred to by various names, for example, common field for OFDMA transmission. The common field of the first type / format may include a Spatial Reuse subfield of 4 bits, a GI+LTF Size subfield of 2 bits, a Number Of UHR LTF Symbols subfield of 3 bits, an LDPC Extra Symbol Segment subfield of 1 bit, a Pre-FEC Padding Factor subfield of 1 bit, a PE Disambiguity subfield of 1 bit, a RU Allocation subfield of 9 bits, a CRC subfield of 4 bits, and a Tail subfield of 6 bits. The number of the above 9-bit length RU Allocation subfields can be determined differently depending on the bandwidth of the DL-PPDU.

[0221] For example, the second type / format may include multiple subfields for MU-MIMO transmission. The common field of the second type / format may be referred to by various names, for example, common field for MU-MIMO transmission. The common field of the second type / format may include a Spatial Reuse subfield of 4 bits, a GI+LTF Size subfield of 2 bits, a Number Of UHR LTF Symbols subfield of 3 bits, an LDPC Extra Symbol Segment subfield of 1 bit, a Pre-FEC Padding Factor subfield of 1 bit, and a PE Disambiguity subfield of 1 bit, which is the same as the first type / format. However, unlike the first type / format, the second type / format may include a Number Of Non-OFDMA Users (or Number Of MU-MIMO Users) subfield of 3 bits. In addition, unlike the first type / format, the second type / format may not include a 9-bit length RU Allocation subfield.

[0222] In other words, multiple sub-fields of a common field may be defined / configured differently based on the first / second type / format. In other words, the arrangement or structure of multiple sub-fields of a common field may be defined / configured differently based on the first / second type / format.

[0223] For example, the common field may include multiple subfields for OFDMA (orthogonal frequency division multiple access) transmission, and the user-specific field may include a user field related to OFDMA allocation. In this case, the common field may include first information regarding whether at least one RU (resource unit) related to the DL PPDU uses MU-MIMO. The first information may be the MU-MIMO support information described above. As previously described, the first information may have various names and may be expressed in various ways. For example, the first information may be expressed as information regarding whether Partial BW DL-MU-MIMO is applied. For example, the first information may be located at bit B13 of the common field.

[0224] The first information above may have a first value or a second value. For example, the first information above may have a length of 1 bit.

[0225] For example, based on the fact that at least one resource unit (RU) associated with the DL PPDU uses the MU-MIMO (multi-user multiple input multiple output), the first information may have a first value. For example, based on the fact that the first information has the first value, the user-specific field may further include a user field related to MU-MIMO allocation. Consequently, a second signal field may include both a user field related to OFDMA allocation and a user field related to OFDMA allocation.

[0226] For example, based on the fact that at least one resource unit (RU) associated with the above DL PPDU does not use the above MU-MIMO, the first information has a second value, and the user specific field may not include a user field associated with MU-MIMO allocation.

[0227] When OFDMA transmission and reception for DL-PPDU are applied simultaneously with MU-MIMO, examples of RU / MRUs in which the MU-MIMO is used can vary as previously described. For example, the RU may include 996+484+242-ton MRUs (multiple resource units). In this case, the number of user / non-APs involved in MU-MIMO can be indicated in various ways, as shown in Table 1 previously described.

[0228] For example, at least one RU included in the above DL-PPDU can use OFDMA or MU-MIMO in units of 80 MHz frequency segments. That is, within a single 80 MHz frequency segment, OFDMA and MU-MIMO are not used simultaneously, and it is preferable to select only one of OFDMA and MU-MIMO.

[0229] As in step S1620, the STA can transmit the corresponding PPDU.

[0230] FIG. 17 is another example of a procedure flowchart related to an example of the present specification. The operation of FIG. 17 can be performed by various devices (e.g., AP, AP MLD, non-AP STA, non-AP MLD).

[0231] As in step S1710, the STA can receive a DL-PPDU. The DL-PPDU may be the same as the PPDU described in S1610 and S1620.

[0232] As in step S1720, the STA can interpret the DL-PPDU based on the first signal field and / or the second signal field. Alternatively, the STA can decode the DL-PPDU (or the data field contained in the DL-PPDU) based on the first signal field and / or the second signal field.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0256] 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. Generate a DL (downlink) PPDU (physical protocol data unit), but The above DL PPDU includes a first signal field and a second signal field, and The first signal field above includes information for interpreting the DL PPDU, and The above second signal field includes a common field and a user-specific field, and The above common field includes a plurality of sub-fields for OFDMA (orthogonal frequency division multiple access) transmission, and the above user-specific field includes a user field related to OFDMA allocation, and The above common field includes first information regarding whether at least one resource unit (RU) associated with the DL PPDU uses MU-MIMO, and Based on the fact that at least one RU (resource unit) associated with the above DL PPDU uses the above MU-MIMO (multi-user multiple input multiple output), the first information has a first value, Based on the fact that the first information has the first value, the user specific field further includes a user field related to MU-MIMO allocation; and Step of transmitting the above DL PPDU including method.

2. In Paragraph 1, The above at least one RU uses OFDMA or MU-MIMO in units of 80 MHz frequency segments. method.

3. In Paragraph 1, The first signal field is a U-SIG (universal signal) field containing information for interpreting the DL PPDU, the second signal field follows the first signal field and provides additional signaling added to the U-SIG field, and the second signal field contains resource allocation information for a STA (station) associated with the DL PPDU. method.

4. In Paragraph 1, The above common field includes a U-SIG overflow bit common to all users, and A plurality of sub-fields included in the above common field are defined differently based on whether the common field is for OFDMA transmission or MU-MIMO transmission. method.

5. In Paragraph 1, The above first information is located at bit B13 of the common field. method.

6. In Paragraph 1, Based on the fact that at least one resource unit (RU) associated with the above DL PPDU does not use the above MU-MIMO, the first information has a second value and the user-specific field does not include a user field related to MU-MIMO allocation. method.

7. In Paragraph 1, Based on the fact that the above first information has the above first value, the 9-bit length RU allocation subfield included in the above common field includes information related to the number of users related to the MU-MIMO. method.

8. In Paragraph 7, The above at least one RU comprises a 996+484+242-ton MRU (multiple resource unit), and Information regarding the number of users related to the above MU-MIMO is included within the RU allocation subfield corresponding to the 996-ton RU. method.

9. Regarding STA(station), 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, Generate a DL (downlink) PPDU (physical protocol data unit), but The above DL PPDU includes a first signal field and a second signal field, and The first signal field above includes information for interpreting the DL PPDU, and The above second signal field includes a common field and a user-specific field, and The above common field includes a plurality of sub-fields for OFDMA (orthogonal frequency division multiple access) transmission, and the above user-specific field includes a user field related to OFDMA allocation, and The above common field includes first information regarding whether at least one resource unit (RU) associated with the DL PPDU uses MU-MIMO, and Based on the fact that at least one RU (resource unit) associated with the above DL PPDU uses the above MU-MIMO (multi-user multiple input multiple output), the first information has a first value, Based on the fact that the first information has the first value, the user specific field further includes a user field related to MU-MIMO allocation; and Step of transmitting the above DL PPDU Performing an operation that includes STA.

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

11. Receive a DL (downlink) PPDU (physical protocol data unit), The above DL PPDU includes a first signal field and a second signal field, and The first signal field above includes information for interpreting the DL PPDU, and The above second signal field includes a common field and a user-specific field, and The above common field includes a plurality of sub-fields for OFDMA (orthogonal frequency division multiple access) transmission, and the above user-specific field includes a user field related to OFDMA allocation, and The above common field includes first information regarding whether at least one resource unit (RU) associated with the DL PPDU uses MU-MIMO, and Based on the fact that at least one RU (resource unit) associated with the above DL PPDU uses the above MU-MIMO (multi-user multiple input multiple output), the first information has a first value, Based on the fact that the first information has the first value, the user specific field further includes a user field related to MU-MIMO allocation; and A step of interpreting the DL PPDU based on the first signal field and the second signal field. including method.

12. In the 11th The STA receiving the above DL PPDU performs an operation related to any one of claims 1 to 8. Ice method.

13. Regarding STA(station), 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 DL (downlink) PPDU (physical protocol data unit), The above DL PPDU includes a first signal field and a second signal field, and The first signal field above includes information for interpreting the DL PPDU, and The above second signal field includes a common field and a user-specific field, and The above common field includes a plurality of sub-fields for OFDMA (orthogonal frequency division multiple access) transmission, and the above user-specific field includes a user field related to OFDMA allocation, and The above common field includes first information regarding whether at least one resource unit (RU) associated with the DL PPDU uses MU-MIMO, and Based on the fact that at least one RU (resource unit) associated with the above DL PPDU uses the above MU-MIMO (multi-user multiple input multiple output), the first information has a first value, Based on the fact that the first information has the first value, the user specific field further includes a user field related to MU-MIMO allocation; and A step of interpreting the DL PPDU based on the first signal field and the second signal field. Performing an operation that includes STA.

14. In Paragraph 13 The above-mentioned instruction of at least one computer memory performs an operation related to any one of claims 1 to 8. STA.

15. 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, Generate a DL (downlink) PPDU (physical protocol data unit), but The above DL PPDU includes a first signal field and a second signal field, and The first signal field above includes information for interpreting the DL PPDU, and The above second signal field includes a common field and a user-specific field, and The above common field includes a plurality of sub-fields for OFDMA (orthogonal frequency division multiple access) transmission, and the above user-specific field includes a user field related to OFDMA allocation, and The above common field includes first information regarding whether at least one resource unit (RU) associated with the DL PPDU uses MU-MIMO, and Based on the fact that at least one RU (resource unit) associated with the above DL PPDU uses the above MU-MIMO (multi-user multiple input multiple output), the first information has a first value, Based on the fact that the first information has the first value, the user specific field further includes a user field related to MU-MIMO allocation; and Performing an operation including the step of transmitting the above DL PPDU Recording media.