Method and apparatus for transmitting scheduling information for performing channel access of specific non-AP sta operating in millimeter wave band through management frame in wireless LAN system

Abstract

Proposed are a method and apparatus for transmitting scheduling information for performing channel access of a specific non-AP STA operating in a millimeter wave band through a management frame in a wireless LAN system. Specifically, a first non-AP STA belonging to a non-AP MLD receives the management frame from a first AP belonging to an AP MLD. The first non-AP STA decodes the management frame. The management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD. The first non-AP STA and the first AP operate on a first link supporting a sub 7 GHz band. The second non-AP STA and a second AP belonging to the AP MLD operate on a second link supporting a millimeter wave band. The information related to the channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band.

Description

Method and device for transmitting scheduling information for performing channel access of a specific NON-AP STA operating in a millimeter wave band through a management frame in a wireless LAN system

[0001] The present specification relates to a technique for transmitting scheduling information for performing channel access of a specific non-AP STA operating in a millimeter wave band through a management frame in a wireless LAN system, and more specifically, to a method and device for defining scheduling information required for performing channel access in a specific link in the millimeter wave band.

[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs. To achieve this, various technologies are being considered to support high throughput, low latency, and extended range. For example, the procedures required to perform channel access in MLD supporting millimeter wave bands can be defined.

[0003] The present specification proposes a method and device for transmitting scheduling information for performing channel access of a specific non-AP STA operating in a millimeter wave band through a management frame in a wireless LAN system.

[0004] An example of this specification proposes a method for conveying scheduling information for performing channel access of a specific non-AP STA operating in a millimeter wave band via a management frame.

[0005] The present embodiment can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system, 802.11bn or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0006] The present embodiment proposes a method for transmitting scheduling information for performing channel access of a specific non-AP STA (or a specific link supporting the millimeter wave band) operating in the millimeter wave band through a management frame. Specifically, the present embodiment proposes a method for defining scheduling information required for performing channel access on a specific link in the millimeter wave band. In addition, the present embodiment proposes a method for transmitting or scheduling the scheduling information based on an RNR IE, a Basic Multi-Link element, or a newly defined IE.

[0007] The first non-AP STA (station) belonging to a non-AP (non-access point) MLD (multi-link device) receives a management frame from the first AP belonging to the AP MLD.

[0008] The above first non-AP STA decodes the management frame.

[0009] The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD.

[0010] The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band. In contrast, the second non-AP STA and the second AP belonging to the AP MLD operate on a second link supporting a millimeter wave (mmWave) band. That is, the AP MLD and the non-AP MLD may be MLDs supporting the millimeter wave band. In this case, the first AP may be referred to as a rAP (reporting AP), and the second AP may be referred to as a mAP (mmWave AP).

[0011] The above sub-7 GHz band may be a band between 2.4 GHz and 7.25 GHz, which is used as an existing Wi-Fi band. The above millimeter wave band may be an unlicensed band between 42 GHz and 71 GHz (i.e., ultra-high frequency).

[0012] Information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band.

[0013] That is, the present embodiment proposes a method for transmitting scheduling information for channel access of a non-AP STA operating in a millimeter wave band (or a link supporting a millimeter wave band) through a management frame transmitted from an AP MLD. At this time, the management frame can be exchanged in a sub 7 GHz band (or a link supporting a sub 7 GHz band), and the scheduling information can include information about a time interval, a channel access type, a bandwidth, etc. so as to perform channel access in the millimeter wave band.

[0014] According to the method proposed by this embodiment, non-AP STAs operating in the millimeter wave band can successfully perform channel access and frame exchange, thereby bringing about an overall performance improvement in terms of throughput / latency utilizing the millimeter wave band.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0029] Figure 15 illustrates an example of an AP MLD and a Non-AP MLD supporting the mmWave band.

[0030] Figure 16 illustrates an example of an RNR element, a Neighbor AP Information field, a TBTT Information Header subfield, and a TBTT Information field.

[0031] Figure 17 illustrates an example of a Basic Multi-Link element, a Link Info field, a STA Control field, and a STA Info field.

[0032] Figure 18 illustrates an example of transmitting channel access-related information for STAs operating in the mmWave band in a Beacon frame transmitted by an AP MLD operating in Sub-7 GHz.

[0033] Fig. 19 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0034] Fig. 20 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0035] FIG. 21 is a flowchart illustrating a procedure for transmitting scheduling information for channel access of a non-AP STA operating in a millimeter wave band by an AP MLD according to the present embodiment.

[0036] FIG. 22 is a flowchart illustrating a procedure for a non-AP MLD according to the present embodiment to receive scheduling information for channel access of a non-AP STA operating in a millimeter wave band.

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

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

[0039] In this specification, “at least one of A and B” can 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” can be interpreted identically to “at least one of A and B.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0062] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, user STA, network, Base Station, Node-B, Access Point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] For example, the version-independent bits of U-SIG may include information about the length of a transmission opportunity (TXOP) and information about the BSS color ID.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] 1. AP MLD and Non-AP MLD supporting mmWave band

[0159] The multi-link device (MLD) defined in 802.11be consists of affiliated APs operating on one or more different channels, and has achieved significant improvements in terms of aggregate / average throughput / latency. While existing MLDs primarily target the 2.4 to 7.25 GHz (sub-7 GHz) band, research is underway to enable affiliated APs to include MLD affiliated APs operating in the mmWave band, the unlicensed bands between 42 and 71 GHz, as the need for mmWave (millimeter wave) has emerged, despite its relatively limited coverage. Therefore, it is essential to address the issues that arise when MLD affiliated APs operate in the mmWave band.

[0160] Figure 15 illustrates an example of an AP MLD and a Non-AP MLD supporting the mmWave band.

[0161] Figure 15 is an example of an MLD supporting the mmWave band. AP 1 of the AP MLD operates a channel in the Sub-7 GHz band, AP 3 operates a channel in the mmWave band, non-AP STA 1 of the Non-AP MLD supports the Sub-7 GHz band, and non-AP STA 2 supports the mmWave band. Therefore, the Non-AP MLD can request the AP MLD to establish a multi-link setup so that non-AP STA 1 can associate with AP 1 (Link 1) and non-AP STA2 can associate with AP 3 (Link 2).

[0162] To achieve this, a non-AP MLD supporting the mmWave band must be able to recognize the presence of an AP operating in the mmWave band and its associated information. Once the non-AP MLD recognizes this information, it can successfully establish a multi-link setup with the AP MLD, depending on its capabilities. Furthermore, this specification proposes a method for transmitting or announcing channel access-related scheduling information required for actual frame exchange based on channel access after a non-AP MLD operating in the mmWave band has associated.

[0163] The references (names) in this specification may change, and STA may include AP STA or non-AP STA.

[0164] 2. Information configuration for scheduled channel access procedures in links operating in the mmWave band.

[0165] Non-AP MLD STAs operating in the mmWave band can perform channel access and frame exchange based on channel access information scheduled by the AP MLD. The AP MLD may include at least one of the following information for scheduled channel access procedures on links operating in the mmWave band.

[0166] Basically, in the mmWave band, the channel access scheduled by the AP MLD may have a contention-based access period (CBAP) that operates on a contention basis, including the idle channel, through CCA (Clear Channel Assessment) after PIFS (Point Coordination Function (PCF) Interframe Space) for the secondary channel before the back-off counter value becomes 0 by performing back-off on the primary channel. In addition, in the mmWave band, the channel access scheduled by the AP MLD may have a service period (SP) that guarantees channel access to a specific STA, since it operates on a contention-free basis.

[0167] During the CBAP period, multiple devices attempt to access the channel simultaneously, and a competition is used to determine who will use it first using random backoff and the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism.

[0168] During the SP period, the AP explicitly grants communication opportunities to specific STAs, eliminating contention and allowing only specific STAs access to resources during that time. This is typically used in conjunction with a trigger frame or Target Wake Time (TWT).

[0169] Specifically, the information for the scheduled channel access procedure in a link operating in the mmWave band is as follows.

[0170] i) Number of Allocation: Indicates how many Channel Allocation fields exist.

[0171] -> When the above Number of Allocation has a value of 4 bits, if there are 8 Channel Allocation fields for scheduling, it has a value of 1000.

[0172] ii) Channel Allocation: Contains various information that STAs actually need for channel access.

[0173] The field may contain at least one of the following pieces of information:

[0174] a. Allocation Type: Indicates the type of channel access method of the corresponding Channel Allocation.

[0175] -> When the Allocation Type field has a 2-bit value, it can indicate the Service Period (SP) of the TDMA method if it is 0, and can indicate the Contention Based Access Period (CBAP) if it is 1.

[0176] When Allocation Type is 1 (CBAP), it operates on a contention-based basis, following the EDCA rule based on a specific channel (primary channel). For example, multiple STAs perform contention and backoff based on the EDCA rule based on the primary channel allocated within the BSS.

[0177] Additionally or alternatively, a CBAP allocated in the mmWave band may define a Backoff Channel that can perform back-off based on a secondary channel other than the primary channel to which the EDCA rule is applied.

[0178] -> When Allocation Type has an 8-bit value, it can be expressed as a bitmap. If it is 0000 0001, it can mean that back-off is performed according to the EDCA rule based on the 8th 20MHz channel when the frequencies are sorted in ascending order.

[0179] -> Additionally or alternatively, in the mmWave band, upclocking of the bandwidth defined in sub 7 GHz may be considered, or the defined minimum bandwidth may be defined differently from the existing sub 7 GHz. For example, if 4x upclocking is considered, the defined minimum bandwidth may be 80 MHz (20 MHz * 4). In this case, when it has an 8-bit value, if it is expressed as a bitmap as 0000 0001, it may mean that back-off is performed according to the EDCA rule based on the 8th 80 MHz channel when the frequencies are sorted in ascending order.

[0180] -> Additionally or alternatively, Allocation Type can be used for indexing. For example, 0 could indicate the primary channel, and 1 could indicate the first 20MHz channel when sorted in ascending frequency order.

[0181] -> Additionally or alternatively, the Allocation Type can be indicated by a channel number. For example, a specific 20MHz channel could be indicated by 36, 40, 44, or 48.

[0182] b. Allocation ID: This refers to an identifier that can distinguish each SP or CBAP Allocation.

[0183] c. Source AID: Indicates the AID of the STA that can initiate channel access during the SP or CBAP section. In the case of CBAP that operates based on contention, setting the Source AID to a broadcast AID indicates that all STAs can contention during the corresponding CBAP section.

[0184] d. Destination AID: This can indicate the AID of the STA targeted by the Source STA during the SP or CBAP section, and can be set as a broadcast AID if the Source AID is to be transmitted to multiple STAs.

[0185] e. Allocation Start: May contain information on the TSF (Time Synchronization Function) where the SP or CBAP section begins.

[0186] -> When it has a value of 4 octets, it can have a lower 4 octet value of TSF. TSF is a function that allows all STAs to share a synchronized time from the AP, and the TSF timer is a 64-bit counter with 1 us units, and all STAs coordinate their operation schedules based on the TSF value.

[0187] f. Allocation Block Duration: This refers to the duration of the SP or CBAP section.

[0188] -> The time unit can be expressed in microseconds (us).

[0189] -> If frame exchange cannot be completed during the corresponding Allocation Block Duration, frame exchange will not start as it may affect other allocations.

[0190] g. BW: Indicates the size of the BW to which the channel allocation is allocated and channel information.

[0191] -> When the BW field has an 8-bit value, when the defined minimum bandwidth size is 20MHz as in sub 7GHz, when the BSS operating bandwidth is 160MHz, it means that the 80MHz at the back in frequency order is allocated in ascending order in the case of 0000 1111.

[0192] -> Additionally or alternatively, the size of the BW and channel information can be conveyed by conveying the channel number of the center frequency information.

[0193] For example, the channel number of center frequency information can have an 8-bit value. For example, in the case of a BSS operating at 160 MHz, setting this field to 38 would mean allocating 40 MHz as the primary, setting it to 42 would mean allocating 80 MHz as the primary, and setting it to 58 would mean allocating 80 MHz as the secondary.

[0194] -> The primary channel of a Sub-7GHz AP can be 20MHz, but in the mmWave band, it can be defined differently from that of Sub-7GHz, depending on how upclocking is applied or how the minimum bandwidth is defined in mmWave. For example, considering 4x upclocking based on 20MHz of Sub-7GHz, the minimum bandwidth defined in mmWave can be defined as 80MHz (20MHz * 4).

[0195] For example, when the BW field has an 8-bit value, considering that the defined minimum bandwidth in mAP (mmWave AP) is 4x upclocking, and the BSS operating bandwidth in the mmWave band is 640 MHz, if the BW field has a value of 0000 1111, it means that 320 MHz, which is the last in frequency order, is allocated in ascending order.

[0196] -> If the Allocation Type is CBAP and there is no Backoff Channel field, the channel bit corresponding to the Primary channel must be set to 1.

[0197] For example, if the Primary channel is the first 4x upclocked 80MHz, the B0 bit in the BW field must be set to 1 when allocating CBAP.

[0198] -> Additionally or alternatively, if a Backoff Channel is defined, backoff can be performed based on the announced Backoff Channel rather than the PCH (Primary Channel).

[0199] -> Additionally or alternatively, if the Backoff Channel field exists, the channel bit corresponding to the Backoff Channel must be set to 1.

[0200] For example, if the Backoff Channel field is the second 4x upclocked 80MHz, the B1 bit of the BW field must be set to 1 when allocating CBAP.

[0201] If CBAP is allocated based on a channel other than the primary channel based on the Backoff Channel field and BW field, the EDCA rule can be applied as follows. For example, if the Backoff Channel field is the second 4x upclocked 80MHz and the BW field is 0111 0000, backoff is performed based on the Backoff Channel field, and CCA is performed on the third and fourth 4x upclocked 80MHz during the PIFS before the Backoff counter value becomes 0, and the frame can be transmitted including the corresponding channel if it is IDLE, and not including the corresponding channel if it is BUSY.

[0202] -> Additionally or alternatively, for CBAP, backoff is performed based on PCH within the allocated BW, and CCA is performed on SCH (Secondary Channel) within the BW during PIFS before the backoff counter value becomes 0, and frame exchange is performed when idle.

[0203] 3. Transmission method example (Beacon frame, Probe Response frame, or Multi-link probe response frame)

[0204] Basically, the fields described in 2. can be transmitted in at least the following frames.

[0205] Some essential information about affiliated APs within an AP MLD can be communicated via the Beacon frame. For example, this can be announced by defining the multi-link element, UHR operation element, Reduced Neighbor Report (RNR) element, or new element in the Beacon frame.

[0206] Additionally or alternatively, it can be transmitted via a Probe Response frame or a Multi-link probe response frame. For example, it can be announced by defining a multi-link element or UHR operation element of a Multi-link probe response frame, or a new element.

[0207] Additionally or alternatively, you can define a new action frame to announce the information.

[0208] 1) When indicated in RNR IE (Information Element)

[0209] Figure 16 illustrates an example of an RNR element, a Neighbor AP Information field, a TBTT Information Header subfield, and a TBTT Information field.

[0210] Referring to FIG. 16, the RNR element includes at least one Neighbor AP Information field, and the Neighbor AP Information field includes a TBTT (Target Beacon Transmission Time) Information Header subfield and a TBTT Information Set. The TBTT Information Header subfield includes a TBTT Information Field Type field and a TBTT Information Length field. The TBTT Information Set includes a TBTT Information field including information selected based on the TBTT Information Field Type field and the TBTT Information Length field.

[0211] Basically, in RNR, the TBTT Information Field Type (0-3) and the TBTT Information Length (in octets) can be determined to indicate information. Therefore, combinations of TBTT Information Field Type and TBTT Information Length need to be considered to indicate one or more pieces of information for mAP. Basically, at least one of the following can be considered. In particular, since the length according to one or more of the information combinations presented above can be changed, at least one of the following can be considered.

[0212] i) The reserved value of TBTT Information Length according to each TBTT Information Field Type (e.g., 0-1) can be used.

[0213] -> Additionally, when TBTT Information Type = 0, if a length is already in use, a different Type value can be used.

[0214] -> Additionally or alternatively, to inform the non-AP MLD that the AP is operating in the mmWave band, the Length excluding 3 octets from TBTT Information Field Type = 1 can be used when there is no additional rule. If 3 octets are used without an additional rule, it cannot be distinguished from an AP operating on the non-primary link of the NSTR AP MLD.

[0215] ii) A new TBTT Information Field Type (i.e., 2, 3) can be used. This can also be used to indicate that the AP is operating in the mmWave band. In particular, legacy STAs or non-AP MLDs that do not have STAs supporting the mmWave band do not need to check this unnecessarily.

[0216] iii) For example, MLD Parameters and Neighbor TBTT offset can be considered as an example of a combination.

[0217] In this case, it can be assumed that BSSID (Basic Service Set Identification) and reachability-related information (e.g., X MHz PSD (Power Spectral Density, transmission power per unit frequency)) (PSD based on X MHz band) should be obtained using Multi-link Probe Request / Response.

[0218] -> Basically, the combination of these pieces of information can have 4 octets or more.

[0219] -> Additionally, in case of 4 octets, since TBTT Information Length = 4 octets is reserved for all TBTT Information Field Types as shown in Table 1, it can be indicated using this. That is, when TBTT Information Length = 4, it can have the Neighbor TBTT offset subfield and the MLD Parameters subfield (this is just an example). When TBTT Information Field Type = 1 is used, legacy STAs do not need to unnecessarily check this, and when TBTT Information Field Type = 2,3 is used, non-AP MLDs that do not have legacy STAs or STAs that support the mmWave band do not need to unnecessarily check this.

[0220] Value of TBTT Information Length subfieldTBTT Information field contents… … 4The Neighbor AP TBTT Offset subfield and the MLD Parameters subfield… …

[0221] -> Additionally or alternatively, if it is assumed that the timestamp (TSF) of mAP and rAP (reporting AP or regular AP) are always the same, then the Neighbor AP TBTT offset may not be needed, so when only the MLD Parameter is indicated, TBTT Information field Type = 2 or 3 can be used. If there are additional other subfields as above, they can be indicated with a length greater than that in the reserved value of the length field according to the TBTT Information field Type. Additionally or alternatively, if the Non-AP MLD recognizes that the Operating channel is in the mmWave band and the AP MLD ID = 0, TBTT Information field Type = 1 with length = 3 can be used. That is, the previously used length value may be interpreted differently due to these additional rules.

[0222] 2) When directed in the Basic Multi-Link element (Basic ML IE)

[0223] Figure 17 illustrates an example of a Basic Multi-Link element, a Link Info field, a STA Control field, and a STA Info field.

[0224] Referring to FIG. 17, the Basic Multi-Link element includes a Common Info field and a Link Info field. The Common Info field includes an MLD MAC address subfield and an MLD Capabilities And Operations subfield (or an Extended MLD Capabilities And Operations subfield) (not shown). The Link Info field includes an STA Control field and an STA Info field. The STA Control field includes a Link ID subfield.

[0225] By default, AP MLD announces the MLD MAC address, essential MLD capabilities, etc. in the Basic ML IE, which is always transmitted by each affiliated AP. Therefore, rAPs can always include one or more pieces of information about mAPs in the Basic ML IE. For this purpose, at least one of the following methods can be considered.

[0226] -> Information about each mAP can be included in the Per-STA Profile subelement of the Link Info field in the Basic ML IE.

[0227] -> The Link ID of the Per-STA Profile subelement indicates the link ID for each mAP. As mentioned above, additional link IDs can be included if required (e.g., STA Control, STA Info fields). Additionally, if the same Additional Link ID applies to all mAPs, it can be included in Common Info.

[0228] -> Information may be included in the STA Profile field of the Per-STA Profile subelement. Additionally, whether information is included in the STA Profile field may be indicated in the STA Control field.

[0229] -> The Common Info of the Basic ML IE may indicate whether the rAP, mAP, and TSF are identical. If they are identical, the Neighbor TBTT offset (or TSF offset) may not be indicated in the Per-STA Profile subelement.

[0230] -> Additionally or alternatively, a new type of ML IE (e.g., defining a new Type of Multi-Link Control) or a new Per-STA Profile subelement (e.g., IMMW Per-STA Profile) can be defined instead of the Basic Multi-link ML IE (see Table 2). For example, a reserved value (e.g., 1) other than subelement ID = 0 can be used to indicate that this Per-STA Profile is a Profile for APs operating in the mmWAVE band. In this case, for example, for link ID, only Additional Link ID can be indicated or the existing Link ID size can be adjusted. This can be determined depending on how to interpret / indicate Link ID as mentioned in the RNR IE above. As another example, one or more pieces of information about mAP can be indicated in STA Info or STA profile. Additionally, one or more pieces of information that exist in STA Info of the existing Per-STA Profile can be included.

[0231] Subelement IDName0Per-STA Profile1IMMW Per-STA Profile2-220Vendor Specific222-253Reserved254Fragement255Reserved

[0232] 3) If directed by a new IE

[0233] A separate new IE may be defined that contains one or more pieces of information for each mAP.

[0234] -> Additionally, each mAP can be distinguished by its Link ID.

[0235] 4) Practical example (transmitting channel access information for STAs operating in the mmWave band in a beacon frame)

[0236] Meanwhile, an rAP can proactively notify the presence of an mAP within its own AP MLD. This allows non-AP MLDs to proactively identify and check for RNR IEs, ML IEs, or new IEs containing the information described above. This can be indicated using a reserved bit in the Capability Information And Status Indication field transmitted in a Beacon or Probe Response frame, or a reserved bit in the Extended Capabilities element.

[0237] Figure 18 illustrates an example of transmitting channel access-related information for STAs operating in the mmWave band in a Beacon frame transmitted by an AP MLD operating in Sub-7 GHz.

[0238] Figure 18 assumes two non-AP MLDs connected to AP1, AP2, and AP3 affiliated to an AP MLD. The two non-AP MLDs are composed of three affiliated non-AP STAs. Figure 18 assumes that link1 and link2 are links operating in the sub-7 GHz band, and link3 is a link operating in the mmWave band. AP1 operating in the sub-7 GHz band can transmit information about AP3 operating in the mmWave band by including it in a frame such as a beacon (i.e., a management frame). The management frame can be transmitted including the scheduling information related to channel access described above so that non-AP STAs associated with AP3 can perform channel access.

[0239] Channel access scheduling information for non-AP STAs operating in the mmWave band is as follows.

[0240] Figure 18 is an example of allocating three channel accesses. The first Allocation (Allocation #1) is allocated to CBAP, and the Source AID is set to broadcast and the Destination AID is set to the AID of AP3 in the AP MLD, so that all non-AP STAs can perform contention and transmit frames to AP3 affiliated with the AP MLD. The starting point of Allocation #1 is indicated through Allocation Start based on the TSF, so that channel access for Allocation #1 can be started at that point. The CBAP section of Allocation #1 is notified through Allocation Block Duration so that it can be performed for 100us based on the TSF. If the frame exchange is not completed during the Allocation Block Duration, the frame exchange may not be performed. This is because it may affect other allocations of channel access allocated by the AP.

[0241] The second Allocation (Allocation #2) is an Allocation assigned to SP, and the Source AID is set to non-AP STA3 affiliated with non-AP STA MLD1, and the Destination AID is set to non-AP STA3 of non-AP STA MLD2, so that frame exchange between the two non-AP STAs can be guaranteed for 100us based on the Allocation Start when Allocation #2 starts, and is instructed through the Allocation Block Duration. The SP section of the Allocation #2 can perform frame exchange through the second 20MHz channel in the frequency sorted in ascending order by setting the BW to 01.

[0242] The third Allocation (Allocation #3) is an Allocation assigned to CBAP. It sets the Source AID to Broadcast and the Destination AID to AP 3 affiliated with the AP MLD. Starting from the Allocation Start (2000us) when Allocation #3 begins, all non-AP STAs perform contention for 100us, allowing the non-AP STA whose backoff counter value becomes 0 first during contention to exchange frames during the Allocation Block Duration. The CBAP section of Allocation #3 sets the BW to 11, performing backoff based on the primary channel. During the PIFS before the backoff counter value becomes 0, it performs CCA on the second channel. If it is IDLE, it includes the secondary channel, and if it is BUSY, it does not include the secondary channel and performs frame exchange (only on the primary channel).

[0243] <STA의 정보 전송과 관련된 동작과정>

[0244] - STA can be a non-AP STA or an AP.

[0245] Transmission process

[0246] In the present disclosure, a STA may transmit one or more pieces of information described above to one or more STAs supporting mmWave bands within the MLD to which the STA belongs via one or more PPDUs.

[0247] Additionally, one or more PPDUs may contain a Beacon frame and a Probe Response frame.

[0248] => Additionally or alternatively, a bit may be indicated indicating that there is an STA that supports the mmWave band.

[0249] Additionally, one or more pieces of information may be information related to channel access schedules for STAs operating in the mmWave band, such as Number of Allocation, Channel Allocation, Allocation Type, Allocation ID, Source AID, Destination AID, Allocation Start, Allocation Block Duration, and BW, but is not limited thereto.

[0250] Additionally or alternatively, information about the STA may be indicated in the TBTT Information field of the Reduced neighbor report element (RNR IE).

[0251] Additionally or alternatively, information about the STA may be indicated in the Multi-link IE.

[0252] => Additionally or alternatively, a new type of Multi-link IE or a new ID (IMMW) Per-STA subelement may be indicated.

[0253] Additionally or alternatively, information about the STA may be indicated in a newly defined IE.

[0254] <Receiving Process>

[0255] In the present disclosure, an STA that receives a frame containing one or more pieces of information about one or more STAs supporting the mmWave band within an MLD to which the STA belongs from one or more STAs can perform frame detection and obtain information about each STA through the frame detection. Through the obtained information, the STA can obtain information necessary for an STA in the MLD to which the STA belongs to support the mmWave band to perform channel access and determine whether the STA can perform channel access based on the information. For example, it can determine whether channel access is performed based on contention or contention-free based on scheduled channel access information.

[0256] As shown in FIG. 5, the PPDU in which the signal of this specification is transmitted / received may include a data field.

[0257] The above data field contains user data and may contain packets for upper layers, i.e., may contain MPDU (MAC Frame).

[0258] For example, a frame included in an MPDU may be a frame containing one or more pieces of information about an STA operating in the mmWave band within a single MLD. For example, a frame included in an MPDU may be a Beacon or Probe Response frame.

[0259] Additionally, as shown in the above drawing 1, the transmitting device and the receiving device may each include a memory, a processor, and a transceiver.

[0260] The above memory can store one or more pieces of information about an STA operating in the mmWave band within the MLD described herein.

[0261] The processor may perform back-off based on information stored in the memory, generate various RUs, and construct PPDUs. An example of a PPDU generated by the processor may be as shown in FIG. 5.

[0262] The above processor is described in this specification<STA의 정보 전송과 관련된 동작과정> Can be set to do all / some.

[0263] In particular, the transceiver (113) of the transmitting device includes an antenna and can perform analog signal processing. Specifically, the processor (111) can control the transceiver (113) to transmit a PPDU generated by the processor (111).

[0264] Alternatively, the processor (111) may generate a transmission PPDU and store information about the transmission PPDU in the memory (112).

[0265] For example, the processor (111) of the transmitting device may be configured to perform operations of a transmitting STA according to an example of the present disclosure. For example, the processor (111) may be configured to transmit, via the transceiver (113), a frame including one or more pieces of information about an STA operating in the mmWave band within an MLD.

[0266] Additionally, the transceiver (123) of the receiving device can receive a PPDU based on the control of the processor (121). For example, the transceiver (123) can include a plurality of detailed units (not shown). For example, the transceiver (123) can include at least one receiving antenna and a filter for the corresponding receiving antenna.

[0267] A PPDU received through a transceiver (123) may be stored in a memory (122). A processor (121) may process decoding of the received PPDU through the memory (122). The processor (121) may obtain control information (e.g., SIG) regarding BW / Tone-Plan / RU included in the PPDU and store the obtained control information in the memory (122).

[0268] The above memory (122) can store one or more pieces of information about an STA operating in the mmWave band within the MLD described herein.

[0269] The processor (121) can perform decoding on the received PPDU. In addition, the processor (121) can process the decoded data. For example, the processor (121) can perform a processing operation to transmit information about the decoded data field to a higher layer (e.g., MAC layer). In addition, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, a subsequent operation can be performed.

[0270] For example, the processor parses a MAC PDU obtained through PHY decoding of the DATA field of a PPDU received through a transceiver.

[0271] In addition, the processor (121) described in this specification<STA의 정보 전송과 관련된 동작과정> Can be set to do all / some.

[0272] For example, the processor (121) of the receiving device may be configured to perform the operations of the receiving STA according to the examples of the present disclosure. For example, the processor (121) may attempt frame detection through the transceiver (123). The processor (121) may be configured to decode / parse a frame addressed to it based on the received frame. In addition, the processor (121) may be configured to set / reset the NAV according to the value of the duration / ID field of a frame not addressed to it.

[0273] Fig. 19 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0274] An example of FIG. 19 may be performed at a transmitting STA or transmitting device (AP and / or non-AP STA).

[0275] Some of the steps (or detailed sub-steps described below) in the example of Fig. 19 may be omitted or changed.

[0276] Through step S1910, the transmitting device (transmitting STA) can obtain information regarding the aforementioned Tone Plan. As described above, the information regarding the Tone Plan includes the size and location of the RU, control information related to the RU, information regarding the frequency band in which the RU is included, information regarding the STA receiving the RU, etc.

[0277] Through step S1920, the transmitting device can configure / generate a PPDU based on the acquired control information. The step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, step S1920 may include a step of configuring an EHT-SIG field including control information regarding a Tone Plan. That is, step S1920 may include a step of configuring a field including control information indicating the size / position of an RU (e.g., an N bitmap) and / or a step of configuring a field including an identifier (e.g., an AID) of an STA receiving the RU.

[0278] Additionally, step S1920 may include a step of generating an STF / LTF sequence to be transmitted through a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0279] Additionally, step S1920 may include a step of generating a data field (i.e., MPDU) to be transmitted via a specific RU.

[0280] The transmitting device can transmit the PPDU configured through step S1920 to the receiving device based on step S1930.

[0281] While performing step S1930, the transmitting device may perform at least one of operations such as CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion.

[0282] A signal / field / sequence configured according to this specification can be transmitted in the form of FIG. 5.

[0283] Fig. 20 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0284] The above-described PPDU can be received according to an example of FIG. 20.

[0285] An example of FIG. 20 may be performed at a receiving STA or receiving device (AP and / or non-AP STA).

[0286] Some of the steps (or detailed sub-steps described below) in the example of Fig. 20 may be omitted.

[0287] A receiving device (receiving STA) may receive all or part of a PPDU through step S2010. The received signal may have the form of FIG. 5.

[0288] The sub-step of step S2010 can be determined based on step S1930 of Fig. 19. That is, step S2010 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operations, and GI insert operations applied in step S1930.

[0289] At step S2020, the receiving device can decode all or part of the PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.

[0290] More specifically, the receiving device can decode the L-SIG and EHT-SIG of the PPDU based on the Legacy STF / LTF and obtain information included in the L-SIG and EHT SIG fields. Information regarding various Tone Plans (i.e., RUs) described herein can be included in the EHT-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the EHT-SIG.

[0291] In step S2030, the receiving device can decode the remaining portion of the PPDU based on the information about the Tone Plan (i.e., RU) acquired through step S2020. For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about one Plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the Tone Plan (i.e., RU) and acquire the MPDU included in the data field.

[0292] Additionally, the receiving device may perform a processing operation to transmit the decoded data to a higher layer (e.g., MAC layer) through step S2030. Additionally, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, a subsequent operation may be performed.

[0293] Hereinafter, the above-described embodiment will be described with reference to FIGS. 1 to 20.

[0294] FIG. 21 is a flowchart illustrating a procedure for transmitting scheduling information for channel access of a non-AP STA operating in a millimeter wave band by an AP MLD according to the present embodiment.

[0295] An example of FIG. 21 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system, 802.11bn or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0296] The present embodiment proposes a method for transmitting scheduling information for performing channel access of a specific non-AP STA (or a specific link supporting the millimeter wave band) operating in the millimeter wave band through a management frame. Specifically, the present embodiment proposes a method for defining scheduling information required for performing channel access on a specific link in the millimeter wave band. In addition, the present embodiment proposes a method for transmitting or scheduling the scheduling information based on an RNR IE, a Basic Multi-Link element, or a newly defined IE.

[0297] At step S2110, the first AP belonging to the AP (access point) MLD (multi-link device) generates a management frame.

[0298] In step S2120, the first AP transmits the management frame to the first non-AP STA (station) belonging to the non-AP MLD.

[0299] The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD.

[0300] The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band. In contrast, the second non-AP STA and the second AP belonging to the AP MLD operate on a second link supporting a millimeter wave (mmWave) band. That is, the AP MLD and the non-AP MLD may be MLDs supporting the millimeter wave band. In this case, the first AP may be referred to as a rAP (reporting AP), and the second AP may be referred to as a mAP (mmWave AP).

[0301] The above sub-7 GHz band may be a band between 2.4 GHz and 7.25 GHz, which is used as an existing Wi-Fi band. The above millimeter wave band may be an unlicensed band between 42 GHz and 71 GHz (i.e., ultra-high frequency).

[0302] Information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band.

[0303] That is, the present embodiment proposes a method for transmitting scheduling information for channel access of non-AP STAs operating in a millimeter wave band (or a link supporting a millimeter wave band) through a management frame transmitted from an AP MLD. At this time, the management frame can be exchanged in a sub 7 GHz band (or a link supporting a sub 7 GHz band), and the scheduling information can include information about a time interval, a channel access type, a bandwidth, etc. so as to perform channel access in the millimeter wave band. Accordingly, non-AP STAs operating in the millimeter wave band can successfully perform channel access and frame exchange, thereby bringing about an effect of improving overall performance in terms of throughput / latency utilizing the millimeter wave band.

[0304] Scheduling information for performing channel access in the above millimeter wave band is specifically defined as follows.

[0305] The above scheduling information may include first and second fields. The first field may include information about channel allocation. The second field may include information about the number of the first field.

[0306] The information about the above channel allocation may include at least one of information about an allocation type, information about an allocation identifier, information about a source AID (Association Identification), information about a destination AID, information about an allocation start, information about an allocation duration, and information about an allocation bandwidth.

[0307] For example, if the information about the allocation type is composed of 1 bit or 2 bits, the information about the allocation type can be described as follows.

[0308] Based on the information about the above allocation type being set to a first value (e.g., 1 or 0), channel access of the second non-AP STA may be performed on a contention-based basis in a Contention Based Access Period (CBAP). Channel access of the second non-AP STA may perform backoff according to EDCA rules on a primary channel (as before) or a non-primary channel (if a backoff channel is defined separately).

[0309] Based on the information about the above allocation type being set to a second value (e.g., 0 or 1), channel access of the second non-AP STA can be performed on a contention free basis in the SP (Service Period).

[0310] As another example, if the information about the above allocation type is composed of an 8-bit bitmap, the information about the above allocation type can be described as follows.

[0311] The minimum bandwidth supported in the sub-7 GHz band may be 20 MHz. Based on the fact that the minimum bandwidth supported in the millimeter wave band is obtained based on 4x upclocking with respect to the minimum bandwidth supported in the sub-7 GHz band, the minimum bandwidth supported in the millimeter wave band may be 80 MHz. Accordingly, based on the fact that each bit of the 8-bit bitmap is sorted in ascending frequency order, the BSS operating bandwidth of the millimeter wave band may be 640 MHz.

[0312] For example, if the 8-bit bitmap is 00000001, the channel access of the second non-AP STA may perform backoff according to the EDCA rule on the eighth 80 MHz channel.

[0313] Information about the above allocation identifier may include an identifier that can distinguish the allocation of the CBAP or the SP.

[0314] Information about the above source AID may include the AID of an AP or non-AP STA that can initiate channel access from the CBAP or the SP. For example, if the allocation type is a CBAP that operates on a contention basis, the source AID may be set to a broadcast AID, so that all non-AP STAs can perform channel access on a contention basis during the CBAP.

[0315] Information about the above destination AID may include the AID of an AP or non-AP STA that is the target of frame exchange in the CBAP or the SP.

[0316] Information about the start of the above allocation may include information about the TSF (Time Synchronization Function) where the CBAP or the SP starts.

[0317] Information about the above allocation interval may include information about the interval during which the CBAP or the SP persists. If frame exchange is not completed during the interval during which the CBAP or the SP persists, other channel access may also be affected, and thus the second non-AP STA may not initiate frame exchange.

[0318] The information about the allocated bandwidth may include information about the bandwidth of an allocated channel within the millimeter wave band.

[0319] The minimum bandwidth supported in the sub-7 GHz band may be 20 MHz. Based on the fact that the minimum bandwidth supported in the millimeter wave band is obtained based on 4x upclocking with respect to the minimum bandwidth supported in the sub-7 GHz band, the minimum bandwidth supported in the millimeter wave band may be 80 MHz.

[0320] The information on the above allocated bandwidth is configured as an 8-bit bitmap, and based on the fact that each bit of the 8-bit bitmap is sorted in ascending frequency order, the BSS operating bandwidth of the millimeter wave band can be 640 MHz (80 MHz x 8).

[0321] The second non-AP STA may perform channel access only for a bandwidth for which a bit is set to 1 in the 8-bit bitmap among the BSS operating bandwidth. For example, if the 8-bit bitmap is 00001111, the channel access of the second non-AP STA may be performed in a 320 MHz channel located behind (or having a higher frequency) among the BSS operating bandwidth.

[0322] Based on the fact that the information about the channel allocation further includes information about a backoff channel, the information about the backoff channel may include information that backoff is performed on a non-primary channel other than the primary channel. At this time, the bit for the non-primary channel in the 8-bit bitmap may be set to 1. For example, if the non-primary channel performing the backoff is the second 80 MHz channel, the second bit B1 of the 8-bit bitmap may be set to 1.

[0323] Based on the fact that the information about the channel allocation does not further include information about the backoff channel, the second AP and the second non-AP STA may perform backoff on the primary channel. At this time, the bit for the primary channel in the 8-bit bitmap may be set to 1. If the primary channel for performing the backoff is the first 80 MHz channel, the first bit B0 of the 8-bit bitmap may be set to 1.

[0324] The method for setting information about the allocated bandwidth and information about the backoff channel to perform backoff according to the EDCA rule in the non-primary channel other than the primary channel (assuming that it is allocated by CBAP) is as follows.

[0325] For example, it is assumed that the information about the backoff channel indicates that the non-primary channel performing the backoff is a second 80 MHz channel (assuming 4x upclocking), and that an 8-bit bitmap, which is information about the allocated bandwidth, is set to 0111000. Accordingly, the second non-AP STA performs a backoff on the second 80 MHz channel based on the information about the backoff channel, and if the third and fourth 80 MHz channels are idle by performing CCA during the PIFS before the backoff counter value becomes 0, the second non-AP STA can perform frame exchange including all of the second, third, and fourth 80 MHz channels. If the third and fourth 80 MHz channels are BUSY, the second non-AP STA can perform frame exchange only through the second 80 MHz channel.

[0326] For example, information related to channel access of the second non-AP STA may be signaled through a Reduced Neighbor Report (RNR) element. The RNR element may include a Target Beacon Transmission Time (TBTT) information field type field, a TBTT information length field, and a TBTT information field. The TBTT information field may include information about the channel allocation based on a reserved value of the TBTT information field type field and a reserved value of the TBTT information length field. That is, by setting the reserved value of the TBTT information field type field and the reserved value of the TBTT information length field, necessary information about the channel allocation may be included in the TBTT information field.

[0327] As another example, information related to channel access of the second non-AP STA may be signaled through a Basic Multi-Link element. The Basic Multi-Link element may include a common information field and a link information field. The link information field may include a Per-STA profile for the millimeter wave band based on a reserved value of a subelement ID (Identification). The Per-STA profile for the millimeter wave band may include a STA control field, a STA information field, and a STA profile field. The link ID subfield of the STA control field may include a link ID for the second AP. Information about the channel allocation may be included in the STA information field or the STA profile field.

[0328] That is, the management frame may include the RNR element or the basic Multi-Link element. The management frame may include a beacon, a probe response frame, or a (re)association response frame.

[0329] FIG. 22 is a flowchart illustrating a procedure for a non-AP MLD according to the present embodiment to receive scheduling information for channel access of a non-AP STA operating in a millimeter wave band.

[0330] An example of FIG. 22 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system, 802.11bn or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0331] The present embodiment proposes a method for transmitting scheduling information for performing channel access of a specific non-AP STA (or a specific link supporting the millimeter wave band) operating in the millimeter wave band through a management frame. Specifically, the present embodiment proposes a method for defining scheduling information required for performing channel access on a specific link in the millimeter wave band. In addition, the present embodiment proposes a method for transmitting or scheduling the scheduling information based on an RNR IE, a Basic Multi-Link element, or a newly defined IE.

[0332] In step S2210, a first non-AP STA (station) belonging to a non-AP (non-access point) MLD (multi-link device) receives a management frame from a first AP belonging to an AP MLD.

[0333] At step S2220, the first non-AP STA decodes the management frame.

[0334] The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD.

[0335] The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band. In contrast, the second non-AP STA and the second AP belonging to the AP MLD operate on a second link supporting a millimeter wave (mmWave) band. That is, the AP MLD and the non-AP MLD may be MLDs supporting the millimeter wave band. In this case, the first AP may be referred to as a rAP (reporting AP), and the second AP may be referred to as a mAP (mmWave AP).

[0336] The above sub-7 GHz band may be a band between 2.4 GHz and 7.25 GHz, which is used as an existing Wi-Fi band. The above millimeter wave band may be an unlicensed band between 42 GHz and 71 GHz (i.e., ultra-high frequency).

[0337] Information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band.

[0338] That is, the present embodiment proposes a method for transmitting scheduling information for channel access of non-AP STAs operating in a millimeter wave band (or a link supporting a millimeter wave band) through a management frame transmitted from an AP MLD. At this time, the management frame can be exchanged in a sub 7 GHz band (or a link supporting a sub 7 GHz band), and the scheduling information can include information about a time interval, a channel access type, a bandwidth, etc. so as to perform channel access in the millimeter wave band. Accordingly, non-AP STAs operating in the millimeter wave band can successfully perform channel access and frame exchange, thereby bringing about an effect of improving overall performance in terms of throughput / latency utilizing the millimeter wave band.

[0339] Scheduling information for performing channel access in the above millimeter wave band is specifically defined as follows.

[0340] The above scheduling information may include first and second fields. The first field may include information about channel allocation. The second field may include information about the number of the first field.

[0341] The information about the above channel allocation may include at least one of information about an allocation type, information about an allocation identifier, information about a source AID (Association Identification), information about a destination AID, information about an allocation start, information about an allocation duration, and information about an allocation bandwidth.

[0342] For example, if the information about the allocation type is composed of 1 bit or 2 bits, the information about the allocation type can be described as follows.

[0343] Based on the information about the above allocation type being set to a first value (e.g., 1 or 0), channel access of the second non-AP STA may be performed on a contention-based basis in a Contention Based Access Period (CBAP). Channel access of the second non-AP STA may perform backoff according to EDCA rules on a primary channel (as before) or a non-primary channel (if a backoff channel is defined separately).

[0344] Based on the information about the above allocation type being set to a second value (e.g., 0 or 1), channel access of the second non-AP STA can be performed on a contention free basis in the SP (Service Period).

[0345] As another example, if the information about the above allocation type is composed of an 8-bit bitmap, the information about the above allocation type can be described as follows.

[0346] The minimum bandwidth supported in the sub-7 GHz band may be 20 MHz. Based on the fact that the minimum bandwidth supported in the millimeter wave band is obtained based on 4x upclocking with respect to the minimum bandwidth supported in the sub-7 GHz band, the minimum bandwidth supported in the millimeter wave band may be 80 MHz. Accordingly, based on the fact that each bit of the 8-bit bitmap is sorted in ascending frequency order, the BSS operating bandwidth of the millimeter wave band may be 640 MHz.

[0347] For example, if the 8-bit bitmap is 00000001, the channel access of the second non-AP STA may perform backoff according to the EDCA rule on the eighth 80 MHz channel.

[0348] Information about the above allocation identifier may include an identifier that can distinguish the allocation of the CBAP or the SP.

[0349] Information about the above source AID may include the AID of an AP or non-AP STA that can initiate channel access from the CBAP or the SP. For example, if the allocation type is a CBAP that operates on a contention basis, the source AID may be set to a broadcast AID, so that all non-AP STAs can perform channel access on a contention basis during the CBAP.

[0350] Information about the above destination AID may include the AID of an AP or non-AP STA that is the target of frame exchange in the CBAP or the SP.

[0351] Information about the start of the above allocation may include information about the TSF (Time Synchronization Function) where the CBAP or the SP starts.

[0352] Information about the above allocation interval may include information about the interval during which the CBAP or the SP persists. If frame exchange is not completed during the interval during which the CBAP or the SP persists, other channel access may also be affected, and thus the second non-AP STA may not initiate frame exchange.

[0353] The information about the allocated bandwidth may include information about the bandwidth of an allocated channel within the millimeter wave band.

[0354] The minimum bandwidth supported in the sub-7 GHz band may be 20 MHz. Based on the fact that the minimum bandwidth supported in the millimeter wave band is obtained based on 4x upclocking with respect to the minimum bandwidth supported in the sub-7 GHz band, the minimum bandwidth supported in the millimeter wave band may be 80 MHz.

[0355] The information on the above allocated bandwidth is configured as an 8-bit bitmap, and based on the fact that each bit of the 8-bit bitmap is sorted in ascending frequency order, the BSS operating bandwidth of the millimeter wave band can be 640 MHz (80 MHz x 8).

[0356] The second non-AP STA may perform channel access only for a bandwidth for which a bit is set to 1 in the 8-bit bitmap among the BSS operating bandwidth. For example, if the 8-bit bitmap is 00001111, the channel access of the second non-AP STA may be performed in a 320 MHz channel located behind (or having a higher frequency) among the BSS operating bandwidth.

[0357] Based on the fact that the information about the channel allocation further includes information about a backoff channel, the information about the backoff channel may include information that backoff is performed on a non-primary channel other than the primary channel. At this time, the bit for the non-primary channel in the 8-bit bitmap may be set to 1. For example, if the non-primary channel performing the backoff is the second 80 MHz channel, the second bit B1 of the 8-bit bitmap may be set to 1.

[0358] Based on the fact that the information about the channel allocation does not further include information about the backoff channel, the second AP and the second non-AP STA may perform backoff on the primary channel. At this time, the bit for the primary channel in the 8-bit bitmap may be set to 1. If the primary channel for performing the backoff is the first 80 MHz channel, the first bit B0 of the 8-bit bitmap may be set to 1.

[0359] The method for setting information about the allocated bandwidth and information about the backoff channel to perform backoff according to the EDCA rule in the non-primary channel other than the primary channel (assuming that it is allocated by CBAP) is as follows.

[0360] For example, it is assumed that the information about the backoff channel indicates that the non-primary channel performing the backoff is a second 80 MHz channel (assuming 4x upclocking), and that an 8-bit bitmap, which is information about the allocated bandwidth, is set to 0111000. Accordingly, the second non-AP STA performs a backoff on the second 80 MHz channel based on the information about the backoff channel, and if the third and fourth 80 MHz channels are idle by performing CCA during the PIFS before the backoff counter value becomes 0, the second non-AP STA can perform frame exchange including all of the second, third, and fourth 80 MHz channels. If the third and fourth 80 MHz channels are BUSY, the second non-AP STA can perform frame exchange only through the second 80 MHz channel.

[0361] For example, information related to channel access of the second non-AP STA may be signaled through a Reduced Neighbor Report (RNR) element. The RNR element may include a Target Beacon Transmission Time (TBTT) information field type field, a TBTT information length field, and a TBTT information field. The TBTT information field may include information about the channel allocation based on a reserved value of the TBTT information field type field and a reserved value of the TBTT information length field. That is, by setting the reserved value of the TBTT information field type field and the reserved value of the TBTT information length field, necessary information about the channel allocation may be included in the TBTT information field.

[0362] As another example, information related to channel access of the second non-AP STA may be signaled through a Basic Multi-Link element. The Basic Multi-Link element may include a common information field and a link information field. The link information field may include a Per-STA profile for the millimeter wave band based on a reserved value of a subelement ID (Identification). The Per-STA profile for the millimeter wave band may include a STA control field, a STA information field, and a STA profile field. The link ID subfield of the STA control field may include a link ID for the second AP. Information about the channel allocation may be included in the STA information field or the STA profile field.

[0363] That is, the management frame may include the RNR element or the basic Multi-Link element. The management frame may include a beacon, a probe response frame, or a (re)association response frame.

[0364] <Device Configuration>

[0365] The technical features of the present specification described above can be applied to various devices and methods. For example, the technical features of the present specification described above can be performed / supported by the devices of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above can be applied only to a part of FIG. 1 and / or FIG. 14. For example, the technical features of the present specification described above can be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and the memory (112, 122) of FIG. 1, or based on the processor (610) and the memory (620) of FIG. 14. For example, the device of the present specification receives a management frame from a first AP belonging to an AP (access point) multi-link device (MLD); and decodes the management frame.

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

[0367] The CRM may store instructions for performing operations including a step of receiving a management frame from a first AP belonging to an AP (access point) MLD (multi-link device); and a step of decoding the management frame. The instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to the CRM of the present specification may be the processor (111, 121) or processing chip (114, 124) of FIG. 1, or the processor (610) of FIG. 14. Meanwhile, the CRM of the present specification may be the memory (112, 122) of FIG. 1, the memory (620) of FIG. 14, or a separate external memory / storage medium / disk, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0384] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

In a method performed in a non-AP (non-access point) MLD (multi-link device) in a wireless LAN system, A step in which a first non-AP STA (station) belonging to the non-AP MLD receives a management frame from a first AP belonging to the AP MLD; and The above first non-AP STA includes a step of decoding the management frame, The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD, The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band, The second non-AP STA and the second AP belonging to the AP MLD operate in a second link supporting the millimeter wave (mmWave) band, and The information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band. method. In the first paragraph, The above scheduling information includes first and second fields, The first field above contains information about channel allocation, The second field contains information about the number of the first field. method. In the second paragraph, The information about the above channel allocation includes at least one of information about the allocation type, information about the allocation identifier, information about the source AID (Association Identification), information about the destination AID, information about the start of the allocation, information about the duration of the allocation, and information about the allocation bandwidth. method. In the third paragraph, Based on the information about the above allocation type being set to the first value, channel access of the second non-AP STA is performed on a contention basis in a CBAP (Contention Based Access Period), Based on the information about the above allocation type being set to the second value, the channel access of the second non-AP STA is performed on a contention free basis in the SP (Service Period). method. In paragraph 4, Information about the above allocation identifier includes an identifier that can distinguish the allocation of the CBAP or the SP, Information about the above source AID includes the AID of an AP or non-AP STA that can initiate channel access from the CBAP or the SP, Information about the destination AID includes the AID of the AP or non-AP STA that is the target of frame exchange in the CBAP or the SP, Information about the start of the above allocation includes information of the TSF (Time Synchronization Function) where the CBAP or the SP starts, Information about the above allocation interval includes information about the interval in which the CBAP or the SP persists, Information about the above allocated bandwidth includes information about the bandwidth of the allocated channel within the millimeter wave band. method. In paragraph 5, The minimum bandwidth supported in the above sub-7 GHz band is 20 MHz, Based on the fact that the minimum bandwidth supported in the above millimeter wave band is obtained based on 4x upclocking with respect to the minimum bandwidth supported in the above sub-7 GHz band, the minimum bandwidth supported in the above millimeter wave band is 80 MHz, The information on the above allocated bandwidth is composed of an 8-bit bitmap, and based on the fact that each bit of the 8-bit bitmap is sorted in ascending frequency order, the BSS operating bandwidth of the millimeter wave band is 640 MHz. The above second non-AP STA performs channel access only for the bandwidth for which the bit is set to 1 in the 8-bit bitmap among the BSS operating bandwidth. method. In paragraph 6, Based on the fact that the information about the channel allocation further includes information about a backoff channel, the information about the backoff channel includes information about performing backoff for a non-primary channel other than the primary channel, Among the above 8-bit bitmaps, the bit for the non-primary channel is set to 1. method. In paragraph 6, Based on the fact that the information about the channel allocation does not further include information about the backoff channel, the second AP and the second non-AP STA perform backoff for the primary channel, Among the above 8-bit bitmaps, the bit for the primary channel is set to 1. method. In the third paragraph, Information related to channel access of the second non-AP STA is signaled through a Reduced Neighbor Report (RNR) element, The above RNR element includes a TBTT (Target Beacon Transmission Time) information field type field, a TBTT information length field, and a TBTT information field, The TBTT information field includes information about the channel allocation based on the reserved value of the TBTT information field type field and the reserved value of the TBTT information length field. method. In the third paragraph, Information related to channel access of the second non-AP STA is signaled through the Basic Multi-Link element, The above basic Multi-Link element includes a common information field and a link information field, The above link information field includes a Per-STA profile for the millimeter wave band based on the reserved value of the subelement ID (Identification), The Per-STA profile for the above millimeter wave band includes a STA control field, a STA information field, and a STA profile field, The link ID subfield of the above STA control field includes a link ID for the second AP, Information about the above channel allocation is included in the STA information field or the STA profile field. method. In a wireless LAN system, a non-AP (non-access point) MLD (multi-link device) is memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: A first non-AP STA (station) belonging to the non-AP MLD receives a management frame from a first AP belonging to the AP MLD; and The above first non-AP STA decodes the management frame, The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD, The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band, The second non-AP STA and the second AP belonging to the AP MLD operate in a second link supporting the millimeter wave (mmWave) band, and The information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band. Non-AP MLD. In a method performed in an AP (access point) MLD (multi-link device) in a wireless LAN system, A step in which the first AP belonging to the above AP MLD generates a management frame; and The first AP comprises a step of transmitting the management frame to the first non-AP STA (station) belonging to the non-AP MLD, The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD, The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band, The second non-AP STA and the second AP belonging to the AP MLD operate in a second link supporting the millimeter wave (mmWave) band, and The information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band. method. In paragraph 12, The above scheduling information includes first and second fields, The first field above contains information about channel allocation, The second field contains information about the number of the first field. method. In Article 13, The information about the above channel allocation includes at least one of information about the allocation type, information about the allocation identifier, information about the source AID (Association Identification), information about the destination AID, information about the start of the allocation, information about the duration of the allocation, and information about the allocation bandwidth. method. In Article 14, Based on the information about the above allocation type being set to the first value, channel access of the second non-AP STA is performed on a contention basis in a CBAP (Contention Based Access Period), Based on the information about the above allocation type being set to the second value, the channel access of the second non-AP STA is performed on a contention free basis in the SP (Service Period). method. In Article 15, Information about the above allocation identifier includes an identifier that can distinguish the allocation of the CBAP or the SP, Information about the above source AID includes the AID of an AP or non-AP STA that can initiate channel access from the CBAP or the SP, Information about the destination AID includes the AID of the AP or non-AP STA that is the target of frame exchange in the CBAP or the SP, Information about the start of the above allocation includes information of the TSF (Time Synchronization Function) where the CBAP or the SP starts, Information about the above allocation interval includes information about the interval in which the CBAP or the SP persists, Information about the above allocated bandwidth includes information about the bandwidth of the allocated channel within the millimeter wave band. method. In Article 16, The minimum bandwidth supported in the above sub-7 GHz band is 20 MHz, Based on the fact that the minimum bandwidth supported in the above millimeter wave band is obtained based on 4x upclocking with respect to the minimum bandwidth supported in the above sub-7 GHz band, the minimum bandwidth supported in the above millimeter wave band is 80 MHz, The information on the above allocated bandwidth is composed of an 8-bit bitmap, and based on the fact that each bit of the 8-bit bitmap is sorted in ascending frequency order, the BSS operating bandwidth of the millimeter wave band is 640 MHz. The above second non-AP STA performs channel access only for the bandwidth for which the bit is set to 1 in the 8-bit bitmap among the BSS operating bandwidth. method. In a wireless LAN system, an AP (access point) MLD (multi-link device) memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: The first AP belonging to the above AP MLD generates a management frame; and The above first AP transmits the management frame to the first non-AP STA (station) belonging to the non-AP MLD, The above management frame includes information related to channel access of a second non-AP STA belonging to the non-AP MLD, The first non-AP STA and the first AP operate on a first link supporting a sub-7 GHz band, The second non-AP STA and the second AP belonging to the AP MLD operate in a second link supporting the millimeter wave (mmWave) band, and The information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band. AP MLD. At least one computer-readable medium containing instructions based on being executed by at least one processor, A step of receiving a management frame from a first AP belonging to an AP (access point) MLD (multi-link device); and Including a step of decrypting the above management frame, The above management frame includes information related to channel access of a second non-AP STA belonging to a non-AP MLD, The first non-AP STA and the first AP belonging to the non-AP MLD operate on a first link supporting a sub-7 GHz band, The second non-AP STA and the second AP belonging to the AP MLD operate in a second link supporting the millimeter wave (mmWave) band, and The information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band. Recording medium. In a wireless LAN system, for a device, memory; and A processor operatively coupled to the memory, the processor comprising: Receives a management frame from the first AP belonging to the AP (access point) MLD (multi-link device); and Decrypt the above management frame, The above management frame includes information related to channel access of a second non-AP STA belonging to a non-AP MLD, The first non-AP STA and the first AP belonging to the non-AP MLD operate on a first link supporting a sub-7 GHz band, The second non-AP STA and the second AP belonging to the AP MLD operate in a second link supporting the millimeter wave (mmWave) band, and The information related to channel access of the second non-AP STA includes scheduling information for performing channel access in the millimeter wave band. device.

Images