Exchange of information for accessing non-primary channels

Abstract

The technical features of this disclosure may relate to a method or apparatus performed in a wireless local area network (WLAN) system. For example, this disclosure may propose a specific technique in which an MLD with Non-Master Channel Access (NPCA) capability enables or disables NPCA mode taking into account power savings, QoS requirements, etc. For example, an example is proposed where signaling information about the mode can be configured based on a link, and information about the NPCA mode for a link can also be transmitted over another link based on the MLD level. For example, information about the NPCA mode can be exchanged between stations (STAs) via management frames.

Description

Technical Field

[0001] This specification relates to a wireless local area network (WLAN) system, and more specifically, to an improved method and apparatus for accessing channels other than the main channel of a wireless LAN system. Background Technology

[0002] Wireless LANs (LANs) have been improved in various ways. For example, the EHT (Extreme High Throughput) specification can utilize newly proposed increased bandwidth, improved PPDU (Protocol Data Unit) structure, improved sequencing, HARQ (Hybrid Automatic Repeat Request) technology, etc. The EHT specification can be referred to as the IEEE 802.11be specification.

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

[0004] In the EHT specification, wide bandwidth (e.g., 160 / 240 / 320MHz) can be used for high throughput. Furthermore, to efficiently utilize bandwidth, preamble punching and multi-RU transmission can be employed.

[0005] The UHR (Ultra-Reliability) specification can further improve WLAN systems. The UHR system can also be referred to as the IEEE 802.11bn specification. The purpose of the UHR system is to support ultra-high reliability in signal transmission to STAs. To this end, various technologies are considered for supporting high throughput, low latency, and extended range for UHR systems.

[0006] WLAN systems perform media access based on the primary channel. For example, information related to the primary channel with a bandwidth of 20MHz is delivered to multiple STAs via management frames, and STAs attempting frame switching can perform access to the primary channel. Summary of the Invention

[0007] Technical issues

[0008] Current 802.11 BSS operation channels can be configured based on a primary channel (PCH) and one or more secondary channels (SCHs). To transmit frames based on a BSS operation channel, backoff must always be performed on the PCH, and the backoff counter (BC) on the PCH must be 0. Therefore, when the PCH is determined to be busy, the radio channel / medium cannot be used. However, according to conventional techniques, even when only the PCH is busy, and the SCHs (or non-primary channels) are idle, the corresponding SCHs cannot be used, which can significantly reduce medium efficiency. To address this issue, various information must be exchanged to support operation on accessed SCHs (or non-primary channels).

[0009] Technical solution

[0010] This specification sets forth various technical features. These technical features can be applied to various types of STAs / devices.

[0011] For example, this specification may propose a specific technique by which an MLD with NPCA (Non-Primary Channel Access) capability enables or disables NPCA mode taking into account power savings, QoS requirements, etc. For example, an example may be proposed in which signaling information related to the mode can be configured based on a link, and information related to the NPCA mode for another link can be delivered at the MLD level over any link.

[0012] For example, the technical features of this specification may relate to a method or apparatus performed in a wireless local area network (WLAN) system. For example, the method of this specification may include a first STA (station) sending a first management frame to a second STA based on a first link. For example, the first STA may be attached to a first MLD (multi-link device) performing multi-link operations related to multiple links, and the second STA may be attached to a second MLD performing multi-link operations related to said multiple links. For example, the first management frame may include first bit map information related to an NPCA (non-primary channel access) mode performed by the first MLD for multiple links.

[0013] For example, the method described in this specification may include the first STA receiving a second management frame from a second STA based on the first link. For example, the second management frame may include second bitmap information relating to the NPCA mode performed by the second MLD for the plurality of links.

[0014] Beneficial effects

[0015] The technical features described in this specification can produce various beneficial effects. For example, when exchanging information related to NPCA mode according to the techniques proposed in this specification, efficient and flexible communication corresponding to various types of services is possible. For example, when the traffic volume is large, NPCA mode can be enabled, and thus NPCA can be performed to receive OBSS services, thereby improving throughput performance. For example, when the traffic to be processed by the STA is small, NPCA mode can be disabled. Thus, when receiving OBSS services, a gain in power saving during the corresponding time period can be obtained, thereby providing flexibility for NPCA mode for MLD STAs. Attached Figure Description

[0016] Figure 1 Examples of transmitting and / or receiving devices described in this specification are shown.

[0017] Figure 2 This is a conceptual diagram illustrating the structure of a wireless LAN (WLAN).

[0018] Figure 3 This is a diagram illustrating the typical link establishment process.

[0019] Figure 4 An implementation of the multi-link (ML) approach is shown.

[0020] Figure 5 The PPDU sent / received at the STA in this specification is shown.

[0021] Figure 6 This is a diagram showing the arrangement of resource units (RUs) for a 20 MHz PPDU.

[0022] Figure 7 This is a diagram showing the arrangement of resource units (RUs) for a 40 MHz PPDU.

[0023] Figure 8 This is a diagram showing the arrangement of resource units (RUs) for an 80 MHz PPDU.

[0024] Figure 9 The operation according to UL-MU is shown.

[0025] Figure 10 An example of a channel used / supported / defined within the 2.4 GHz band is shown.

[0026] Figure 11 An example of a channel used / supported / defined within the 5 GHz band is shown.

[0027] Figure 12 An example of a channel used / supported / defined within the 6 GHz band is shown.

[0028] Figure 13 An example of a MAC frame header is shown.

[0029] Figure 14 Examples of modifications to the transmitting and / or receiving devices described in this specification are shown.

[0030] Figure 15 An example of NAV (Network Assignment Vector) settings is shown.

[0031] Figure 16 Examples related to primary channel, secondary channel, and channel extension / binding are shown.

[0032] Figure 17 Examples involving channel access related to an 80MHz channel.

[0033] Figure 18 An example of the SCA process is shown.

[0034] Figure 19 An example related to the first method of this specification is shown.

[0035] Figure 20 An example related to the first method of this specification is shown.

[0036] Figure 21 An example related to the second method in this specification is shown.

[0037] Figure 22 An example related to the second method in this specification is shown.

[0038] Figure 23 An example related to the second method in this specification is shown.

[0039] Figure 24 An example related to the third method in this specification is shown.

[0040] Figure 25 An example related to the third method in this specification is shown.

[0041] Figure 26 This is a process flowchart illustrating the above example in this specification.

[0042] Figure 27 This is another process flowchart illustrating the above example in this specification.

[0043] Figure 28 This is another process flowchart illustrating the above example in this specification.

[0044] Figure 29 This is another process flowchart illustrating the above example in this specification. Detailed Implementation

[0045] As used herein, “A or B” may mean “A only,” “B only,” or “both A and B.” Alternatively, “A or B” may be interpreted as “A and / or B.” For example, as used herein, “A, B, or C” may mean “A only,” “B only,” “C only,” or “any combination of A, B, and C.”

[0046] As used in this article, a forward slash ( / ) or a comma can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

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

[0048] Furthermore, the parentheses used herein may mean "for example." Specifically, when "control information (UHR signal field)" is indicated, "UHR signal field" may be suggested as an example of "control information." In other words, "control information" in this specification is not limited to "UHR signal field," and "UHR signal field" may be cited as an example of "control information." Moreover, even when "control information (UHR signal field)" is indicated, "UHR signal field" may be cited as an example of "control information."

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

[0050] Furthermore, the expressions “based on,” “on the basis of,” or “according to” used in this specification mean “based on at least part of” and not “based on only” a single element.

[0051] The technical features described individually in a single figure in this specification can be implemented individually or simultaneously.

[0052] The examples in this specification can be applied to various wireless communication systems. For example, the examples in this specification can be applied to wireless local area network (WLAN) systems. For example, this specification can be applied to the IEEE 802.11a / g / n / ac / ax / be / bn standards. Furthermore, the examples in this specification can also be applied to ultra-high reliability (UHR) standards or next-generation WLAN standards that enhance IEEE 802.11bn. Additionally, the examples in this specification can be applied to mobile communication systems. For example, they can be applied to mobile communication systems based on Long Term Evolution (LTE) and their evolution based on the 3rd Generation Partnership Project (3GPP) standards.

[0053] In the following text, in order to illustrate the technical features of this specification, the technical features applicable to this specification will be described.

[0054] Figure 1 Examples of transmitting and / or receiving devices shown in this specification are illustrated.

[0055] Figure 1 Examples can perform the following technical features. Figure 1 This involves at least one STA (station). For example, the STA (110, 120) in this specification may also be referred to by various names such as mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit (MS), or simply user. The STA (110, 120) in this specification may also be referred to by various names such as network, base station, node B, access point (AP), repeater, router, or relay. The STA (110, 120) in this specification may also be referred to by various names such as receiving device, transmitting device, receiving STA, transmitting STA, receiving apparatus, or transmitting apparatus.

[0056] For example, the STA (110, 120) in this specification can be used as an access point (AP) or a non-AP. That is, the STA (110, 120) in this specification can perform the functions of an AP and / or a non-AP STA. In this specification, an AP can also be referred to as an AP STA.

[0057] The STAs (110, 120) in this specification support various communication standards other than the IEEE 802.11 standard. For example, they support 3GPP-based communication standards (e.g., LTE, LTE-A, 5G NR standards). Furthermore, the STAs in this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. Additionally, the STAs in this specification support communications for various communication services, such as voice calls, video calls, data communications, and autonomous driving (self-driving).

[0058] In this specification, the STA (110, 120) may include a media access control (MAC) and physical layer interface for wireless media that conforms to the IEEE 802.11 standard.

[0059] The following is based on Figure 1 The subgraph (a) is used to describe STA (110, 120).

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

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

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

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

[0064] For example, a non-AP STA processor (121) may receive signals via a transceiver (123), process the received signals, generate transmission signals, and perform control for signal transmission. A non-AP STA memory (122) may store signals received via the transceiver (123) (e.g., receive signals) and signals to be transmitted via the transceiver (123) (e.g., transmit signals).

[0065] For example, the operation of a device designated as an AP in the following specification can be performed by a first STA (110) or a second STA (120). For example, if the first STA (110) is an AP, the operation of the device designated as an AP is controlled by the processor (111) of the first STA (110), and related signals can 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 the AP's transmit / receive signals can be stored in the memory (112) of the first STA (110). In addition, if the second STA (110) is an AP, the operation of the device designated as an AP is controlled by the processor (121) of the second STA (120), and related signals 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 AP's transmit / receive signals can be stored in the memory (122) of the second STA (110).

[0066] For example, the operation of a device designated as a non-AP (or user STA) in the following description can be performed in either the first STA (110) or the second STA (120). For example, if the second STA (120) is a non-AP, the operation of the device designated as a non-AP can be controlled by the processor (121) of the second STA (120), and related signals can be sent or received via a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of a non-AP or the transmit / receive signals of an AP can be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of the device designated as a non-AP is controlled by the processor (111) of the first STA (110), and related signals can be sent or received via a transceiver (113) controlled by the processor (111) of the first STA (120). In addition, control information related to the operation of non-APs or the transmission / reception signals of APs can be stored in the memory (112) of the first STA (110).

[0067] In the following instructions, (transmit / receive) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmit / receive) terminal, (transmit / receive) device, (transmit / receive equipment), network, etc. may refer to... Figure 1STA (110, 120) in the diagram. For example, devices indicated without specific reference numerals as (transmit / receive) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmit / receive) terminal, (transmit / receive) device, (transmit / receive equipment), network, etc., may also refer to... Figure 1 STAs (110, 120) in the example. For example, in the following example, the operation of various STAs for transmitting and receiving signals (e.g., PPDU) can be achieved by... Figure 1 The transceivers (113, 123) in the code perform the actions. Additionally, in the following examples, the actions of various STAs that generate transmit / receive signals or pre-process or calculate data on transmit / receive signals can be performed by... Figure 1 The processors (111, 121) in the STA execute the following operations: For example, examples of generating transmit / receive signals or performing data processing or calculations on transmit / receive signals in advance include: 1) determining / obtaining / configuring / calculating / decoding / encoding the bit information of the subfields (SIG, STF, LTF, data) included in the PPDU; 2) determining / configuring / obtaining the time or frequency resources (e.g., subcarrier resources) for the subfields (SIG, STF, LTF, data) included in the PPDU; 3) determining / configuring / obtaining the specific sequence (e.g., pilot sequence, STF / LTF sequence, additional sequence applied to SIG) for the subfields (SIG, STF, LTF, data) included in the PPDU; 4) power control actions and / or power-saving actions applied to the STA; 5) actions related to determining / obtaining / configuring / calculating / decoding / encoding the ACK signal. Additionally, in the following examples, various information used by various STAs to determine / obtain / configure / calculate / decode / encode transmit / receive signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) can be stored in the STA. Figure 1 In the memory (112, 122) shown.

[0068] The above Figure 1 The device / STA of subgraph (a) can be as follows Figure 1 The subgraph (b) is modified as shown. Now it will be based on Figure 1 Subgraph (b) describes the STA (110, 120) of this specification.

[0069] For example, Figure 1 The transceivers (113, 123) shown in subgraph (b) can perform the same functions as described above. Figure 1 The transceiver shown in subgraph (a) has the same function. For example, Figure 1 The processing chips (114, 124) shown in sub-figure (b) may include processors (111, 121) and memory (112, 122). Figure 1The processors (111, 121) and memories (112, 122) shown in sub-diagram (b) can perform the same operations as described above. Figure 1 The processors (111, 121) and memories (112, 122) shown in sub-diagram (a) have the same functions.

[0070] The following terms—mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, user, subscriber 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 equipment and / or transmitting equipment—may refer to… Figure 1 The STA (110, 120) shown in subgraphs (a) / (b), or may refer to Figure 1 The processing chips (114, 124) are shown in sub-figure (b). That is, the technical features of this specification can be found in... Figure 1 It can be performed in the STA (110, 120) shown in subgraphs (a) / (b), or it can be performed only in the subgraphs (a) / (b). Figure 1 This is executed in the processing chips (114, 124) shown in sub-diagram (b). For example, the technical feature of transmitting control signals by the STA can be understood as... Figure 1 The control signals generated in the processors (111, 121) shown in sub-figures (a) / (b) are transmitted through... Figure 1 The technical features transmitted by the transceivers (113, 123) shown in sub-figures (a) / (b) are illustrated. Alternatively, the technical features of the STA transmitting control signals can be understood as follows: Figure 1 The technical features of generating control signals to be sent to transceivers (113, 123) in the processing chips (114, 124) shown in sub-figure (b).

[0071] For example, the technical characteristics of receiving STA control signals can be understood as follows: Figure 1 The technical features of the transceivers (113, 123) receiving control signals shown in sub-figure (a) are illustrated. Alternatively, the technical features of the STA receiving control signals can be understood as follows: Figure 1 The control signals received by the transceivers (113, 123) shown in sub-diagram (a) are... Figure 1 The sub-figure (a) shows the technical features acquired by the processors (111, 121). Alternatively, the technical features of receiving the STA control signal can be understood as follows: Figure 1 The control signals received by the transceivers (113, 123) shown in sub-diagram (b) are... Figure 1 The technical features obtained by the processing chips (114, 124) shown in sub-figure (b).

[0072] Reference Figure 1Subgraph (b), software code (115, 125) may be stored in memory (112, 122). Software code (115, 125) may include instructions that control the operation of processor (111, 121). Software code (115, 125) may be used in various programming languages.

[0073] Figure 1 The processors (111, 121) or processing chips (114, 124) shown may include application-specific integrated circuits (ASICs), another chipset, logic circuitry, and / or data processing devices. The processor may be an application processor (AP). For example, Figure 1 The processors (111, 121) or processing chips (114, 124) shown 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, Figure 1 The processors (111, 121) or processing chips (114, 124) shown may be SNAPDRAGON® series processors manufactured by Qualcomm®, EXYNOS® series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIO® series processors manufactured by MediaTek®, ATOM® series processors manufactured by Intel®, or enhanced processors thereof.

[0074] In this specification, "uplink" can refer to a link used for communication from a non-AP STA to an AP STA, through which uplink PPDUs / packets / signals, etc., can be transmitted. Similarly, in this specification, "downlink" can refer to a link used for communication from an AP STA to a non-AP STA, through which downlink PPDUs / packets / signals, etc., can be transmitted.

[0075] Figure 2 This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0076] Figure 2 The top shows the structure of the Infrastructure Base Set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.

[0077] Reference Figure 2 At the top, a wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter referred to as BSSs). A BSS (200, 205) is a collection of APs (access points, 225) and STAs (stations, 200-1) that have been successfully synchronized and can communicate with each other; it does not refer to a specific area. A BSS (205) may include one or more connectable STAs (205-1, 205-2) connected to a single AP (230).

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

[0079] The distributed system (210) can connect multiple BSSs (200, 205) to implement an Extended Service Set (ESS) 240. ESS (240) can be used as a term to indicate a network formed by connecting one or more APs via the distributed system (210). APs included in a single ESS (240) may have the same SSID (Service Set Identifier).

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

[0081] In BSS, for example Figure 2 The upper part of the network enables networking between APs (225, 230) and between APs (225, 230) and STAs (200-1, 205-1, 205-2). However, it is also possible to establish a network and perform communication between STAs without APs (225, 230). A network that establishes a network and performs communication between STAs without APs (225, 230) is defined as a self-organizing network or Independent Basic Service Set (IBSS).

[0082] Figure 2 The bottom of the diagram shows the concept of IBSS.

[0083] Reference Figure 2 At the bottom, IBSS is a BSS that operates in a self-organizing mode. Since IBSS does not include APs, there is no centralized management entity. That is, in IBSS, STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs and are not allowed to access the distributed system, thus forming a self-contained network.

[0084] Figure 3 This is a diagram illustrating typical link setup processing.

[0085] In step S310, the STA can perform a network discovery operation. This network discovery operation may include scanning. That is, for the STA to access a network, it must look for networks 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.

[0086] Figure 3 As an example, a network discovery operation including active scanning is illustrated. In active scanning, the STA performing the scan sends probe request frames to discover nearby APs and waits for a response while moving through the channel. A responder responds to the probe request frame by sending a probe response frame to the STA that sent the probe request frame. Here, the responder can be the STA that last sent a beacon frame in the BSS of the scanned channel. In the BSS, the AP sends a beacon frame, making it a responder. In the IBSS, STAs within the IBSS take turns sending beacon frames, so the responder is not fixed. For example, an STA that sends a probe request frame on channel 1 and receives a probe response frame on channel 1 can store the BSS-related information contained in the received probe response frame and move to the next channel (e.g., channel 2) to perform a scan in the same manner (e.g., sending and receiving probe requests and responses on channel 2).

[0087] although Figure 3 Not shown in the example, scanning can also be performed passively. STAs performing scans based on passive scanning can move between channels while waiting for beacon frames. Beacon frames (management frames in IEEE 802.11) announce the existence of the wireless network and are periodically sent to scanning STAs for discovery and joining. In a BSS, the AP sends beacon frames periodically, while in an IBSS, STAs within the IBSS take turns sending beacon frames. When a scanning STA receives a beacon frame, it stores the BSS information contained in the beacon frame and moves to a different channel, recording beacon frame information for each channel. Upon receiving another beacon frame, the STA stores the BSS-related information contained in the received beacon frame and moves to the next channel, using the same method to perform a scan on the next channel.

[0088] In step S320, the STA in the network is found to be capable of performing authentication processing. This authentication processing may be referred to as the first authentication processing to clearly distinguish it from the security setup operation in step S340 below. The authentication processing in S320 may include the STA sending an authentication request frame to the AP and the AP sending an authentication response frame to the STA in response. The authentication frame used for the authentication request / response corresponds to a management frame.

[0089] The authentication frame may include information such as the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust secure network (RSN), and finite cyclic group (FCG).

[0090] The STA can send an authentication request frame to the 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 then provide the STA with the result of the authentication process via an authentication response frame.

[0091] A successfully authenticated STA can perform connection processing based on step S330. Association processing involves the STA sending an association request frame to the AP, and the AP responding by sending an association response frame to the STA. For example, the association request frame may include information related to various capabilities, such as beacon listening interval, service set identifier (SSID), supported rates, supported channels, RSN, mobile domain, supported operation categories, service indication map broadcast request, and interoperability service capabilities. For example, the association response frame may include information related to various capabilities, status codes, association ID (AID), supported rates, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), received signal-to-noise ratio indicator (RSNI), mobile domain, timeout interval (association regression time), overlapping BSS scan parameters, TIM broadcast response, QoS map, etc.

[0092] Subsequently, in step S340, the STA may perform security setup processing. This security setup processing in step S340 may include, for example, setting a private key via a four-way handshake using an extensible authentication protocol over a LAN (EAPOL) frame.

[0093] Figure 4 This illustrates an implementation of multi-link (ML).

[0094] like Figure 4 As shown, multiple multi-link devices (MLDs) can communicate via multiple links. MLDs can be classified as AP MLDs, which include multiple APSTAs, and non-AP MLDs, which include multiple non-AP STAs. Specifically, an AP MLD may include an affiliated AP (e.g., an APSTA), and a non-AP MLD may include an affiliated STA (e.g., a non-AP STA or a user STA).

[0095] Multiple links may include a first link and a second link, and different channel / subchannel / frequency resources may be allocated to the first link and the second link. The first and second multiple links may be identified using a 4-bit (or other n-bit) link ID. The first link and the second link may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz frequency band. Alternatively, the first link and the second link may be configured in different frequency bands.

[0096] Figure 4 The AP MLD includes three affiliated APs. Figure 4 In the example, AP1 operates in the 2.4 GHz band, AP2 operates in the 5 GHz band, and AP3 operates in the 6 GHz band. Figure 4 In the example, the first link for both AP1 and non-AP1 operations can be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Furthermore, in Figure 4In the example, the second link for both AP2 and non-AP2 operations can be defined as a channel / subchannel / frequency resource within the 5 GHz band. Additionally, in Figure 4 In the example, the third link for both AP3 and non-AP3 operation can be defined as a channel / subchannel / frequency resource within the 6 GHz band.

[0097] exist Figure 4 In the example, AP1 can initiate a multi-link setup procedure (ML setup procedure) by sending an association request frame to a non-AP STA1. Figure 4 In the example, a non-AP STA1 may send an association response frame in response to an association request frame. Figure 4 The individual APs described in the document (e.g., AP1 / 2 / 3) can be compared with... Figure 1 and / or Figure 2 The AP described in the text is the same. Figure 4 The various non-APs described in the text (e.g., non-AP1 / 2 / 3) can be compared with... Figure 1 and / or Figure 2 The STAs described in the text (e.g., user STAs or non-AP STAs) are the same.

[0098] The specific features of this instruction manual are not limited to Figure 4 The specific features described herein include the ability to define the number of links in various ways, and the ability to define multiple links in various ways within at least one frequency band.

[0099] Figure 5 This specification shows the PPDU (Physical Protocol Data Unit or Physical Layer (PHY) Protocol Data Unit) transmitted / received by the STA.

[0100] The STA (e.g., AP STA, non-AP STA, AP MLD, or non-AP MLD) in this specification can send and / or receive. Figure 5 The PPDU described herein may have, for example, Figure 5 The structure is described herein. Furthermore, the PPDU described herein, the Ultra-High Reliability (UHR) PPDU, may be referred to by various names, such as Transmit PPDU, Receive PPDU, Type 1 PPDU, or Type N PPDU. The PPDU described herein can be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that enhance IEEE 802.11bn.

[0101] Figure 5 The PPDU can encompass various PPDU types used in UHR systems. For example, Figure 5Examples can be used for at least one of single-user (SU) mode / type / transmission, multi-user (MU) mode / type / transmission, and null data packet (NDP) mode / type / transmission related to channel detection. For example, if Figure 5 If the example involves NDP, the data fields shown can be omitted. Figure 5 If the PPDU is used in trigger-based (TB) mode, it can be omitted. Figure 5 The UHR-SIG. In other words, the STA that receives the trigger frame for UL-MU (Uplink-MU) communication can send a PPDU, in which... Figure 5 UHR-SIG is omitted in the example.

[0102] exist Figure 5 In this context, L-STF or UHR-LTF can be referred to as a preamble or physical preamble, and can be generated / transmitted / received / acquired / decoded at the physical layer (including in the transmit / receive STA).

[0103] Figure 5 The blocks shown can be referred to as fields / subfields / signals, etc. For example... Figure 5 As shown, the names of these fields / subfields / signals can be Traditional Short Training Field (L-STF), Traditional Long Training Field (L-LTF), Traditional Signal (L-SIG), Repeated L-SIG (RL-SIG), Universal Signal (U-SIG), UHR Signal (UHR-SIG), etc.

[0104] Figure 5 The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and data fields can be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be represented in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and data fields can be represented in units of 78.125 kHz.

[0105] exist Figure 5 In the PPDU, L-LTF and L-STF can be the same as traditional fields (e.g., non-HTLTF and non-HT STF as defined in traditional WLAN standards).

[0106] Figure 5The L-SIG field 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 duration of the PPDU. For example, the value of the 12-bit length field may be determined based on the type of PPDU. For example, if the PPDU is a non-HT (non-high throughput), HT (high throughput), VHT (very high throughput) PPDU, EHT (extremely high throughput) PPDU, or UHR PPDU, the value of the length field may be determined to be a multiple of 3. For example, if the PPDU is an HE PPDU, the value of the length field may be determined to be a multiple of 3 + 1 or a multiple of 3 + 2. In other words, for non-HT, HT, VHT, EHT, and UHR PPDUs, the length field value may be determined to be a multiple of 3. For HE (high efficiency) PPDUs, the length field value may be determined to be a multiple of 3 + 1 or a multiple of 3 + 2. In other words, the length field in the UHR PPDU is set to a value that satisfies the condition that LENGTH divided by 3 leaves a remainder of zero.

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

[0108] For example, a (non-AP and AP) STA can generate an RL-SIG identical to the L-SIG. BPSK modulation can be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine whether the received PPDU is an HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, if the RL-SIG exists, the receiving (non-AP and AP) STA can determine whether the received PPDU is an HE PPDU, EHT PPDU, or UHR PPDU. In other words, if the RL-SIG does not exist, the receiving (non-AP and AP) STA can determine whether the received PPDU is a non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repetition of the L-SIG field and is used to distinguish UHR PPDUs from non-HT PPDUs, HT PPDUs, and VHT PPDUs.

[0109] Available Figure 5 A general-purpose signal (U-SIG) is inserted after RL-SIG. U-SIG can be referred to by various names, such as First SIG Field, First SIG, First Type SIG, Control Signal, Control Signal Field, First (Type) Control Signal, Common Control Field, and Common Control Signal.

[0110] The U-SIG may contain N bits of information and may include information to identify the type of EHT PPDU. For example, the U-SIG may be based on two symbols (e.g., two consecutive / adjacent OFDM symbols). Each symbol of the U-SIG (e.g., an OFDM symbol) may have a duration of 4 μs. Each symbol of the U-SIG may be used to transmit 26 bits of information. For example, each symbol of the U-SIG may be based on 52 data tones and 4 pilot tones for transmission and reception.

[0111] For example, A bits of information (e.g., 52 uncoded bits) can be transmitted via U-SIG, and the first symbol of U-SIG can transmit the first X bits of the total A bits of information (e.g., 26 uncoded bits), and the second symbol of U-SIG can transmit the remaining Y bits of the total A bits of information (e.g., 26 uncoded bits). For example, the transmitting STA can obtain the 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional coding (e.g., BCC coding) based on a code 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 BPSK symbols to generate 52 BPSK symbols assigned 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 pilot tones -21, -7, +7, and +21.

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

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

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

[0115] In other words, when an (AP / non-AP) STA sends an EHT PPDU, it can set the 3-bit PHY version identifier to a 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 with the first value, and can determine that the received PPDU is a UHR PPDU based on the PHY version identifier with the second value.

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

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

[0118] For example, if the UHR PPDU is classified into various types (e.g., types related to SU transmission (performed based on UL or DL), types related to DL transmission, types related to NDP transmission, types related to DL non-MU-MIMO, types related to DL MU-MIMO, types related to multi-AP operation, types related to CBF (coordinated beamforming), SR (space reuse), types related to C-OFDMA (coordinated OFDMA), and types related to C-TDMA (coordinated TDMA), then information about the type of EHTPPDU (e.g., 2-bit or 3-bit information) can be included in the version-related bits of the U-SIG.

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

[0120] Can be Figure 5 The PPDU uses preamble puncturing. Preamble puncturing means applying puncturing to a portion of the entire frequency band of the PPDU (e.g., the secondary 20 MHz band). For example, when transmitting an 80 MHz PPDU, the STA can apply puncturing to the secondary 20 MHz band within the 80 MHz band and transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0121] For example, a preamble punching pattern can be preset. For example, if a first punching pattern is applied, punching can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, if a second punching pattern is applied, punching 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, if a third punching pattern is applied, punching can be applied only to the secondary 20 MHz bands included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when a fourth punching pattern is applied, punching can be applied to at least one 20 MHz channel that is not included in the primary 40 MHz band, which exists within the 160 MHz band (or 80+80 MHz band).

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

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

[0124] Alternatively or additionally, U-SIG and UHR-SIG may include information related to preamble puncturing based on the following methods: U-SIG may include information related to preamble puncturing across all frequency bands (e.g., information related to the preamble puncturing pattern). That is, UHR-SIG does not include information related to preamble puncturing, and only U-SIG may include information related to preamble puncturing (e.g., information related to the preamble puncturing pattern).

[0125] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, the U-SIG can be duplicated. That is, an 80 MHz PPDU can include four identical U-SIGs. PPDUs with bandwidths exceeding 80 MHz can include different U-SIGs.

[0126] Figure 5 The UHR-SIG may include control information for receiving STA data. The UHR-SIG may be transmitted via at least one symbol, each symbol having a length of 4 μs. Information related to the number of symbols used for the UHR-SIG may be included in the U-SIG.

[0127] UHR-SIG provides additional signals to the U-SIG field to enable the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits common to all users. The UHR-SIG field also includes resource allocation information, allowing the STA to locate resources used in fields including the data field, UHR-STF, and UHR-LTF (e.g., the UHR modulation field of the UHR PPDU).

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

[0129] Figure 6 This is a diagram illustrating the layout of a resource unit (RU) for a 20MHz PPDU. Specifically, the UHR-LTF, UHR-STF, and / or data fields included in the 20MHz PPDU can be accessed via... Figure 6 Use at least one of the various RUs defined in the code to send / receive.

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

[0131] also, Figure 6 The RU arrangement can be used not only for multi-user (MU) but also for single-user (SU). In this case, such as Figure 6 As shown at the bottom, a single 242 unit can be used, in which case three DC tones can be inserted.

[0132] exist Figure 6 In the examples, various sizes of RUs are proposed, such as 26-RU, 52-RU, 106-RU, and 242-RU. Since the specific size of these RUs can be expanded or increased, this embodiment is not limited to the specific size of each RU (e.g., the number of corresponding notes). In this specification, N-RU can be represented as an N-note RU, etc. For example, 26-RU can be represented as a 26-note RU.

[0133] Figure 7 This is a diagram showing the layout of the resource unit (RU) for a 40MHz PPDU.

[0134] With the use of RUs of various sizes Figure 6 Similar to the example, Figure 7 Examples can also use RUs of 26, 52, 106, 242, and 484 RUs. Furthermore, five DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40MHz band.

[0135] Additionally, as shown, the 484-RU can be used for a single user. Figure 6 Similar to the example, the specific number of RUs can vary.

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

[0137] Figure 9The operation according to UL-MU is illustrated. As shown, a transmitting STA (e.g., AP) can acquire a TXOP (925) and transmit a trigger frame (930) by performing channel access via contention (e.g., backoff operation). That is, the transmitting STA (e.g., AP) can transmit a PPDU including the trigger frame (930). Upon receiving the PPDU including the trigger frame, a TB (trigger-based) PPDU is transmitted after a delay equal to SIFS.

[0138] TB PPDUs (941, 942) are transmitted simultaneously and can be transmitted from multiple STAs (e.g., user STAs) that indicate their AID from the trigger frame (930). The ACK frame (950) of the TB PPDU can be implemented in various forms. For example, the ACK frame (950) of the TB PPDU can be implemented as a BA (block ACK).

[0139] exist Figure 9 In this context, the transmission of trigger frames (930), TB PPDUs (941, 942) and / or ACK frames (950) can be performed within TXOP (925).

[0140] Figure 10 Examples of channels used / supported / defined within the 2.4 GHz band are shown.

[0141] The 2.4 GHz band can also be referred to by other names, such as the first band. Furthermore, the 2.4 GHz band can refer to the frequency range of channels whose center frequency is adjacent to 2.4 GHz (e.g., channels with center frequencies between 2.4 GHz and 2.5 GHz).

[0142] The 2.4 GHz band may include multiple 20 MHz channels. Each 20 MHz channel within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 to 14). For example, the center frequency of the 20 MHz channel assigned channel index 1 may be 2.412 GHz, the center frequency of the 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of the 20 MHz channel assigned channel index N may be (2.407 + 0.005 GHz). N) GHz. The channel index can be referred to by various names, such as channel number. The specific values ​​of the channel index and center frequency can vary.

[0143] Figure 10Four channels within a 2.4 GHz frequency band are shown. Each of the first frequency range (1010) to the fourth frequency range (1040) can include one channel. For example, the first frequency domain (1010) can include channel 1 (the 20 MHz channel with index 1). In this case, the center frequency of channel 1 can be set to 2412 MHz. The second frequency domain (1020) can include channel 6. In this case, the center frequency of channel 6 can be set to 2437 MHz. The third frequency domain (1030) can include channel 11. In this case, the center frequency of channel 11 can be set to 2462 MHz. The fourth frequency domain (1040) can include channel 14. In this case, the center frequency of channel 14 can be set to 2484 MHz.

[0144] Figure 11 Examples of channels used / supported / defined within the 5 GHz band are shown.

[0145] The 5 GHz band can also be referred to as a second band, etc. A 5 GHz band can refer to a frequency range that uses / supports / defines channels with a center frequency greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz). Alternatively, a 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. Figure 11 The specific figures shown may vary.

[0146] Multiple channels within the 5 GHz band include the unlicensed U.S. 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 referred to as UNII Mid and UNII-2 Extended. UNII-3 may be referred to as UNII-Upper.

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

[0148] Figure 12 Examples of channels used / supported / defined within the 6 GHz band are shown.

[0149] The 6 GHz band may be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range that uses, supports, or defines channels with a center frequency of 5.9 GHz or higher. Figure 12 The specific values ​​shown can vary.

[0150] For example, Figure 12 The 20 MHz channel can be defined starting from 5.940 GHz. Specifically, Figure 12 The leftmost channel in the 20 MHz channel can have an index of 1 (or channel index, channel number, etc.) and can be assigned a center frequency of 5.945 GHz. In other words, the center frequency of channel index N can be determined as (5.940 + 0.005 GHz). N) GHz.

[0151] therefore, Figure 12 The indices (or channel numbers) of the 20 MHz channels are 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Additionally, according to the above (5.940+0.005) N) GHz rules, Figure 12 The indices for the 40MHz channels 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, and 227.

[0152] The structure, type, and / or subtype of MAC frames are described below.

[0153] Figure 13 An example of a MAC frame header is shown. As shown, a MAC frame may include a 2-octet frame control field / information, a 2-octet duration field / information, a 6-octet RA (Receiver Address) field / information, and a 6-octet TA (Transmitter Address) field / information. Figure 13 As shown, the four fields can be adjacent. Figure 13 The MAC header can be modified in various ways, by inserting new fields between the four fields shown, or by omitting at least one of the fields shown.

[0154] Figure 13 The MAC header shown can be located at the very beginning of the MAC frame. That is, the MAC frame may include, for example,... Figure 13 The diagram shows the MAC header and the MAC body fields / information adjacent to the MAC header. This includes... Figure 13 The MAC frame header is inserted / included in the MAC frame. Figure 5 The data fields of the PPDU shown (e.g., UHR PPDU).

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

[0156] For example, management frames include association requests, association responses, reassociation requests, reassociation responses, probe requests, probe responses, beacons, disassociation, authentication, and deauthentication frames / signals as defined in traditional WLANs. For management frames, Figure 13 The type fields (B3 and B2) are set to 00. Additionally, Figure 13 The values ​​of the subtype fields (B7, B6, B5, B4) in the data are as follows: Association Request (0000), Association Response (0001), Re-association Request (0010), Re-association Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Cancel Authentication (1100).

[0157] For example, control frames include triggered beamforming report polling, 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 as defined in traditional WLANs. For control frames, Figure 13 The values ​​of the type fields (B3 and B2) are set to 01. Additionally, Figure 13 The values ​​of the subtype fields (B7, B6, B5, B4) in the following are: 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).

[0158] For example, data frames include (QoS) data, (QoS) space, etc., as defined in traditional WLANs. For data frames, Figure 13 The values ​​of the type fields (B3 and B2) are set to 10.

[0159] MAC frames / signals used in this specification can be identified by the type field / information and subtype field / information described above. For example, a "trigger frame" in this specification may refer to a MAC frame in which type bits B3 and B2 in the frame control field of the MAC header are set to 01 and subtype bits B7, B6, B5, and B4 in the frame control field are set to 0010. The various MAC frames described in this specification are inserted into / included in the data fields of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDUs).

[0160] Figure 14 Examples of modifications to the transmitting and / or receiving devices described in this specification are shown.

[0161] Figures 1 to 4 The device shown (e.g., AP STA, non-AP STA) can be as follows Figure 14 The modifications shown. Figure 14 The transceiver (630) in the middle can be connected with Figure 1 The transceivers (113, 123) in the middle are the same. Figure 14 The transceiver (630) may include a receiver and a transmitter.

[0162] Figure 14 The processor (610) can be used with Figure 1 The processors (111, 121) are the same. Alternatively, Figure 14 The processor (610) can be used with Figure 1 The processing chips (114, 124) are the same.

[0163] Figure 14 The memory (150) can be connected with Figure 1 The memory (112, 122) is the same. Alternatively, Figure 14 The memory (150) can be with Figure 1 The memory (112, 122) are separate external memories.

[0164] Reference Figure 14 The power management module (611) manages the power supply to the processor (610) and / or transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs the processing results of the processor (610). A keypad (614) receives inputs to be used by the processor (610). The keypad (614) can be displayed on the display (613). The SIM card (615) can be an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated key for identifying and authenticating subscribers in mobile devices such as mobile phones and computers.

[0165] Reference Figure 14 The speaker (640) can output the sound-related processing results of the processor (610). The microphone (641) can receive sound-related inputs to be used by the processor (610).

[0166] Figure 15 An example of NAV (Network Assignment Vector) settings is shown. Figure 15 The example involves the exchange of RTS (Ready To Send) frames and CTS (Clear To Send) frames. Figure 15 This section provides an example of setting up NAV based on RTS / CTS exchange.

[0167] Reference Figure 15 The source STA sends an RTS frame, and the destination STA sends a CTS frame. As mentioned above, the destination STA designated as the receiver via the RTS frame does not set the NAV. Some of the remaining STAs can receive the RTS frame and set the NAV, while some other STAs can receive the CTS frame and set the NAV.

[0168] If no CTS frame (e.g., PHY-RXSTART.indication primitive) is received within a specific time period starting from the time the RTS frame is received (e.g., the time the MAC receives the PHY-RXEND.indication primitive corresponding to the RTS frame), the STA that sets or updates NAV via the RTS frame can reset (e.g., reset to 0) the NAV. This specific time period can be (2... aSIFSTime+CTS_Time+aRxPHYStartDelay+2 aSlotTime). CTS_Time can be calculated based on the length of the CTS frame indicated by the RTS frame and the data rate.

[0169] exist Figure 15 Although the setting or updating of NAV is shown via RTS or CTS frames for convenience, it can be performed based on various other frames, such as a duration field included in a PPDU (e.g., the duration field in the MAC header of a MAC frame) of a non-HT PPDU, HT PPDU, VHT PPDU, HE PPDU, EHT PPDU, and / or UHRPPDU. For example, if the RA field in a received MAC frame does not match its own address (e.g., MAC address), the STA can set / reset / update the NAV.

[0170] Figure 15The source STA can be modified in different ways. For example, Figure 15 The source STA can be a non-AP STA or an AP. Alternatively, or alternatively, Figure 15 The source STA can be at least one non-AP STA included in the non-AP MLD, or at least one AP included in the AP MLD. Alternatively or concurrently, Figure 15 The source STA can be any type of STA, such as STA1, STA2, AP1, AP2, etc., as described below.

[0171] The following text describes the primary channel, secondary channel, channel extension / bonding, etc.

[0172] For example, in an IEEE 802.11n system, two 20MHz channels can be combined to perform a 40MHz channel spread / bonding. Furthermore, in an IEEE 802.11ac system, 40 / 80 / 160MHz channel spread / bonding can be performed.

[0173] For example, a STA can perform channel extension / bonding for a primary 20MHz channel (or P20 channel) and a secondary 20MHz channel (S20 channel). For channel extension / bonding, a backoff counter can be used. The backoff counter value is selected as a random value and can be decreased during the backoff interval. Typically, when the backoff counter value becomes 0, the STA (e.g., a non-AP STA or AP) can attempt to access the channel.

[0174] When the P20 channel is determined to be idle during the backoff interval and its backoff count becomes 0, the STA performing channel extension / binding determines whether the S20 channel remains idle during a specific time period (e.g., PIFS (Point Coordination Function Inter-Frame Interval)). If the S20 channel is idle, the STA can perform binding of the P20 and S20 channels. That is, the STA can transmit signals (e.g., PPDU) through a 40MHz channel that includes both the P20 and S20 channels (i.e., a 40MHz bound channel).

[0175] Figure 16 Examples related to primary channels, secondary channels, and channel extension / bonding are shown. For example... Figure 16 As shown, the primary 20MHz channel and the secondary 20MHz channel can be extended / bonded to form a 40MHz channel (the primary 40MHz channel). That is, the extended / bonded 40MHz channel can include the primary 20MHz channel and the secondary 20MHz channel.

[0176] Figure 16 The positions of the channels shown (e.g., P20 / S20 / S40 / S80 channels) in the frequency domain can be modified differently.

[0177] According to conventional techniques, channel extension / bonding can be performed when the channels following the primary channel are idle. That is, the primary 20MHz channel (or P20 channel), secondary 20MHz channel (or S20 channel), secondary 40MHz channel (or S40 channel), and secondary 80MHz channel (or S40 channel) can be extended / bonded sequentially. If the secondary 20MHz channel (or S20 channel) is determined to be busy, channel extension / bonding may not be performed even if all other secondary channels are idle. Furthermore, when the secondary 20MHz channel (or S20 channel) is idle and the secondary 40MHz channel is determined to be busy, channel extension / bonding can be performed only on the primary 20MHz channel (or P20 channel) and the secondary 20MHz channel (or S20 channel).

[0178] For example, in a wireless LAN system (e.g., an 802.11 system), channel access can be performed based on a primary channel (e.g., the P20 channel). For instance, as described above, when the primary channel (e.g., the P20 channel) is idle and the backoff counter (BC) becomes 0, a STA can transmit a frame (e.g., a 40MHz PPDU) that includes an idle secondary channel (e.g., the S20 channel). Therefore, it is preferable that all STAs perform CCA on the primary channel (e.g., the P20 channel).

[0179] Therefore, the AP can advertise the BSS's primary channel (e.g., the P20 channel). For example, information related to the primary channel can always be included in management frames such as beacon or probe response frames sent by the AP. Such a mechanism is effective for performing frame exchange between all STAs and the AP without interference (or for proper media protection). However, when only the primary channel (e.g., the P20 channel) is busy and the surrounding secondary channels are idle, the STA can perform access on the idle secondary channels. Therefore, from a media usage point of view, there may be technical features that reduce efficiency.

[0180] Figure 17 Examples involving channel access related to an 80MHz channel. For example, Figure 17 This involves channel access based on a primary channel defined on a wireless medium with an 80MHz bandwidth. Figure 17 The three channels / sub-channels shown are denoted as P20, S20, S40, etc., and the related terms can be described as follows.

[0181] P20: Main 20MHz channel

[0182] S20: Secondary 20MHz channel

[0183] S40: Secondary 40MHz channel

[0184] S80: Secondary 80MHz channel

[0185] S160: Secondary 160MHz channel

[0186] The above P20, S20, S40, S80 and S160 can correspond to Figure 16 The individual channels / subchannels are shown.

[0187] For example, when the CCA result for P20 (channel) is determined to be busy, or when NAV is set for P20 (in... Figure 15 (As described in the text) and when it is determined that it is in a busy state, the BC for P20 is not reduced. In this case, BC may not be reduced until P20 becomes idle. When BC becomes 0 through such backoff processing (e.g., BC reduction processing), the STA can check the channel states of S20 (channel) and S40 (channel) (e.g., a check based on CCA technology). Additionally, the corresponding STA can send frames through extended channels / resources based on the check results. Figure 17 In the example, because S40 (channel) is busy, frames corresponding to 40MHz PPDUs are transmitted via P20 and S20. In other words, Figure 17 The example involves configuring a 40MHz channel including P20 and S20 channels through the previously described channel extension / bonding.

[0188] As in Figure 17 In the example, when P20 is determined to be busy and S20 and S40 are determined to be idle, the STA operating according to conventional access technology wastes the corresponding 60MHz of bandwidth. This reduces the efficiency of media usage. Examples in this specification present various techniques / methods / devices to improve this situation. For example, examples in this specification present various techniques / methods / devices to enable access to secondary channels (or non-primary channels) even when P20 is busy.

[0189] Preferably, the following various examples are applied to the STAs in a wireless LAN system. For example, the subsequent STAs (or STA1 to STA#N, etc.) can be at least one non-AP STA (included in a non-AP MLD) or at least one AP (included in an AP MLD).

[0190] This specification relates to the operation of accessing a secondary channel (e.g., S20). Access to a secondary channel can be represented as SCA (Secondary Channel Access). When SCA is started / executed / triggered, the STA can switch to the secondary channel (e.g., S20), and thereafter perform CCA sensing (and / or decrementing of the backoff counter) on the switched secondary channel.

[0191] The term SCA can be modified in various ways. For example, SCA can have the same meaning as NPCA (Non-Main Channel Access). For example, in the following examples, the term SCA can be replaced by the term NPCA. For example, in the following examples, expressing SCA mode can be replaced by expressing NPCA mode. Furthermore, in the following examples, the existence of the term SCA enabled can be replaced by the existence of the term NPCA enabled.

[0192] Additionally or alternatively, the term secondary channel may be modified differently. For example, since the primary operation associated with SCA / NPCA is performed by the STA (e.g., AP / non-AP STA) in the previously described secondary 20MHz channel, it may also be referred to as the NPCA primary channel.

[0193] The following text describes information related to the capability for secondary channel access.

[0194] For example, capabilities for SCA (or NPCA) can be predefined / exchanged / negotiated. For example, non-AP STAs and APs can inform each other of the defined / exchanged / negotiated information. For example, capabilities for SCA (or NPCA) can be associated with the ability to identify CCA (e.g., traditional preamble detection (PD)-based operations) of Wi-Fi frames performed on the main channel (e.g., the P20 channel mentioned above). For example, as in the following specific example, capabilities for SCA (or NPCA) can include information regarding whether a frame can be decoded on the SCH (or S20 channel or NPCA main channel). With such capabilities for SCA / NPCA, additional NAVs (e.g., at least one BSS-intra-BSSNAV) and / or a basic NAV can even be set on the SCH (or NPCA main channel).

[0195] For example, capabilities for SCA (or NPCA) can be configured based on 2-bit information. For instance, levels 0 / 1 / 2 can be identified using the first / second / third value of the 2-bit information. The length of the 2-bit information can be modified in various ways. Therefore, 2-bit information can also be configured using 3 / 4 / 5 bits, etc. Levels 0 / 1 / 2 are not necessarily required, and at least one can be used selectively.

[0196] The three specific levels of the capabilities for SCA (or NPCA) are described below.

[0197] Level 0: For example, Level 0 can mean "no backoff on the SCH". For example, when a level is set, conventional CCA can be performed on the SCH (by the STA). In this case, CCA that can detect that it is a Wi-Fi signal (e.g., called Guard Interval Detection (GID)) and / or CCA that detects a signal with a specific strength or higher (e.g., called Energy Detection (ED)) can be performed, etc.

[0198] Level 1: For example, Level 1 can mean "backoff on SCH once". For example, when the level is set, PD can be performed only on one secondary channel at a time.

[0199] Level 2: For example, Level 2 can mean "simultaneous backoff on SCH". For example, when a level is set, PD can be performed simultaneously on multiple secondary channels.

[0200] For example, the aforementioned capabilities can be included in UHR capabilities such as IE, and therefore can be included in various management frames generated / transmitted by the AP, such as beacon, probe response frames, and (re)association request frames. Alternatively or additionally, the aforementioned capabilities can be included in various management frames generated / transmitted by non-AP STAs, such as probe request frames and (re)association request frames.

[0201] exist Figure 15 The NAVs described can be divided into Intra-BSS NAVs and Basic NAVs. Intra-BSS NAVs can be NAVs set by Intra-BSS frames / PPDUs, while Basic NAVs can be NAVs set by OBSS (Overlapping BSS) frames / PPDUs.

[0202] For example, if the in-BSS NAV for the PCH is set by a STA (e.g., a non-AP STA or an AP), then SCA (or NPCA) may not be performed. For instance, when an AP exchanges frames with any STA (e.g., a non-AP STA) within a TXOP acquired by the AP, another STA can thereby set the in-BSS NAV based on the primary channel. In this case, the STA that set the in-BSS NAV can access the SCH and then send frames to the AP, and in this situation, if the corresponding AP is performing a Tx (e.g., DL data, Ack, etc.), the corresponding AP will not receive the relevant signals. Therefore, it is preferable that the STA only starts / triggers SCA when the basic NAV is set on the PCH.

[0203] The above technical features can be expressed in various ways. For example, the above technical features can also be expressed as: when a basic NAV is set on the PCH, the STA (e.g., a non-AP STA or AP) can perform SCA.

[0204] Figure 18 An example of the SCA process is shown. Figure 18 Examples of backoff (e.g., SCA / NPCA operation) can be performed by STA1 (e.g., an AP or non-AP STA). As shown, if a basic NAV is set while backoff is performed on the P20 channel, backoff can be performed on the S20 channel (or the NPCA main channel) at the same time the corresponding basic NAV is set. In this case, backoff can be performed on the S20 channel (or the NPCA main channel) after a delay from the time the basic NAV is set, rather than immediately after the time the basic NAV is set. For example, there may be a handover delay for the PD used to perform the operation from the P20 channel to the S20 channel. From the viewpoint that CCA can be performed on the S20 channel, the above example is different in terms of CCA method and CCA can be performed at all levels. The reason for performing backoff on the S20 channel (or the NPCA main channel) is that if surrounding STAs with the same or similar operating channels as STA1 are idle without backoff, they may transmit frames simultaneously, and in this case, collisions may occur, resulting in wasted channel space.

[0205] SCA / NPCA can be performed based on the following technical features.

[0206] First, here is an example of setting up TXOP on the secondary channel (or NPCA primary channel).

[0207] For example, when the basic NAV on the P20 channel expires, a CCA may have to be performed on the P20 channel. Therefore, it is preferable that the end time of the TXOP for the secondary channel (e.g., the S20 channel or the NPCA primary channel) is set to end before the time when the basic NAV on the primary channel (e.g., the P20 channel) expires.

[0208] Alternatively, if there is insufficient time to set the TXOP of the secondary channel, frames may not be transmitted (on the secondary channel).

[0209] For example, if the TXOP end time of the secondary channel is set to end after the basic NAV expiration time (of the primary channel), then conventional STAs can transmit frames through the P20 channel, and therefore may result in... Figure 18 The STA1 cannot receive it. Additionally, problems may occur if TBTT is set in the middle of the basic NAV, because... Figure 18 STA1 must be prepared to send a beacon immediately after the basic NAV.

[0210] Secondly, an example of transmitting frames on a secondary channel (e.g., at least one channel including the NPCA primary channel) is described.

[0211] Traditionally, preamble puncturing can only be performed based on the idle / busy status of at least one SCH channel when the P20 channel is determined to be idle. For the SCA / NPCA of this specification, since the case of a busy P20 channel is considered, the rules used here can be modified as follows: For example, when the P20 channel is determined to be busy, the corresponding P20 channel is punctured, and other SCHs based on the busy S20 channel can also be punctured, and as a result, frames can be transmitted through the idle SCH. For example, in Figure 18 In the example, it is determined that all three 20MHz channels, including the S20 and S40 channels, are idle. Therefore, STA1 can transmit an 80MHz PPDU (including a MAC frame) while performing preamble puncturing on the P20 channel of the 80MHz PPDU. That is, the information indicating the puncturing of the P20 channel can be included in the U-SIG field, etc., of the corresponding 80MHz PPDU.

[0212] The following text describes the various technical features associated with the SCA / NPCA model.

[0213] For example, when a STA (AP or non-AP STA) has the capability for SCA / NPCA, the following problem may occur if the corresponding STA must switch to the S20 channel (or the NPCA master channel) to perform SCA / NPCA when the basic NAV is set on the P20 channel.

[0214] For example, when the BSS operating channel of an AP (MLD) overlaps with the BSS operating channel of an adjacent AP (i.e., the AP that is an OBSS), they may interfere with each other during SCA / NPCA. Specifically, when one AP successfully uses all SCHs in SCA, channel access opportunities may be reduced if the PCHs of another AP overlap. For example, when Figure 18 STA1 is Figure 22 and / or Figure 23 When AP1 is in use, since AP1's S20 (channel) is AP2's P20 (channel), AP2 may not be able to use P20, S20, etc. In this case, when AP1 performs SCA, another AP2 (not shown) may not have many opportunities for traditional PCH-based channel access. Furthermore, when one AP has SCA capability while another does not, the AP with SCA capability may occupy the channel for a longer period, potentially reducing fairness.

[0215] Furthermore, the AP may perform SCA / NPCA when all STAs associated with an AP that has SCA capability (or NPCA capability) do not have SCA capability. In this case, the AP may not need to perform SCA because successful frame exchange with all STAs is impossible. Alternatively, when the AP does not have SCA capability, even if the STAs associated with the AP have SCA capability, the STA may not need to perform SCA. Alternatively, even if at least one STA has SCA capability, it may not want to perform SCA for energy saving. As mentioned above, if the operation of STA switching to the S20 channel (or NPCA master channel) to perform SCA / NPCA when the basic NAV is set on the PCH is defined as an optional function, then the STA and AP cannot determine whether each other performs SCA when the basic NAV is set. Therefore, normal frame exchange between AP / STA may be impossible. Therefore, it is preferable that the STA with SCA capability (e.g., AP and / or STA) considers the surrounding circumstances and its own intentions to indicate whether to perform SCA / NPCA. Furthermore, from the STA's perspective, even if it has SCA capability, it may not implement SCA if it aims to save energy. Moreover, from the AP's perspective, it may not implement SCA if it wants to ensure fairness in PCH-based transmissions of the OBSS.

[0216] For example, a STA (e.g., an AP and / or a non-AP STA) may include at least one of the following information for secondary channel access operations. For example, the following information (e.g., information relating to secondary channel access capabilities, secondary channel access modes, and / or SCA disable counts described below) may be included in the (UHR) operational IE, or in a new IE form in a management frame including the AP's beacon, (multilink) probe response, and (re)association response. Alternatively or additionally, the following information may be included in the (UHR) operational IE, or in a new IE form in a management frame including the non-AP STA's (multilink) probe request and (re)association request. Alternatively or additionally, the following information may be delivered via the multilink element or the reduced neighbor report element of the beacon frame. Alternatively or additionally, the following information may be delivered in the multilink element of the multilink probe response frame.

[0217] Secondary Channel Access (SCA) capability

[0218] The following describes information related to secondary channel access capabilities. As mentioned above, since the term secondary channel access can be replaced by NPCA, this information can be referred to as SCA capability field / information / subfield / bit, etc., or by various names such as NPCA capability field / information / subfield / bit, etc.

[0219] The aforementioned SCA capability field / information / subfield / bit includes information related to whether the STA (e.g., a UHR non-AP STA or a UHR AP) has the capability to perform SCA.

[0220] For example, the above information can have various bit lengths. For instance, when configured based on 1 bit, a value "1" (or "0") can indicate that the corresponding STA has SCA capability, while a value "0" (or "1") can indicate that the corresponding STA does not have SCA capability.

[0221] Secondary Channel Access (SCA) mode: The following describes information related to SCA mode. As mentioned above, since the term Secondary Channel Access can be replaced by NPCA, this information can be referred to as SCA mode field / information / subfield / bit, etc., or by various names such as NPCA mode field / information / subfield / bit, etc.

[0222] When a STA (e.g., a non-AP STA or AP) with its SCA capability field set to 1 sets a basic NAV on the PCH, it can indicate whether to switch to the SCH (or NPCA main channel) and perform SCA / NPCA.

[0223] For example, when configuring SCA mode information based on 1 bit, a first value (e.g., a "1" value) means to perform SCA, while a second value (e.g., a "0" value) can indicate that SCA is not performed. Alternatively, when the SCA mode is indicated by the first value, the SCA mode can be indicated as enabled. Alternatively, when the SCA mode is indicated by the second value, the SCA mode can be indicated as disabled.

[0224] Alternatively or concurrently, a STA with an SCA capability of 1 (e.g., a non-AP STA or AP) (i.e., a STA equipped with / supporting SCA capability) may always indicate a value associated with SCA mode information.

[0225] Example 1: The following describes the situation where an AP with SCA capability set to 1 announces by setting SCA mode to 0.

[0226] Example 1-1: A STA associated with an AP (e.g., at least one non-AP STA) can notify the AP of its own SCA mode field according to its own intentions. In this case, regardless of the SCA mode, unnecessary SCA execution by the non-AP STA and the AP can be prevented by not switching to SCH (in any case, a non-AP STA with SCA mode set to 1 knows that it will not switch even if it switches to AP).

[0227] Example 1-2: A STA associated with an AP (e.g., at least one non-AP STA) can set its own SCA mode field to 0, the same as the AP.

[0228] Example 1-2-1: A STA associated with an AP (e.g., at least one non-AP STA) can keep the SCA mode at 0 until the AP announces the SCA mode as 1 again, and when the AP announces the SCA mode as 1, it can return to the SCA mode originally set by the non-AP STA.

[0229] Example 1-2-2: When the AP announces SCA mode as 1 again, all STAs (e.g., all non-AP STAs) can indicate their own SCA mode via SCA mode notification frames.

[0230] Example 2: The following describes the situation where an AP with SCA capability set to 1 announces this by setting the corresponding field to 1.

[0231] Each STA (e.g., a non-AP STA) indicates this by setting its own SCA mode field to 0 or 1. The AP does not perform SCA with STAs that have their SCA mode set to 0 (e.g., non-AP STAs), but can perform frame exchange via SCA with STAs that have their SCA mode set to 1 (e.g., non-AP STAs).

[0232] Example 2-1: The AP can maintain its own SCA mode but not switch to the SCH (or NPCA main channel). The reason is that it currently knows that all STAs (e.g., non-AP STAs) have set their SCA mode to 0, and it knows that there are no STAs capable of performing SCA.

[0233] Example 2-2: If all STAs (e.g., all non-AP STAs) set their SCA mode to 0, then the AP can change its own SCA mode to 0.

[0234] Example 2-2-1: When one or more STAs (e.g., non-AP STAs) update and indicate that their own SCA mode is 1, the AP can again set its own SCA mode to 1 to perform SCA with the corresponding STA.

[0235] Alternatively, in the absence of an AP announcing the SCA mode as described in Example 1, an AP with SCA capability can always set the SCA mode to enabled. In this case, only STAs (e.g., non-AP STAs) indicate their own SCA mode, and the AP can also perform SCA if an enabled STA (e.g., a non-AP STA) exists. In this case, if all STAs (e.g., non-AP STAs) are disabled, the AP may not perform SCA.

[0236] The AP can deliver the above information by including it in the UHR operation IE or in a new IE within a management frame that includes beacon, probe response, and correlation response.

[0237] Alternatively or concurrently, in beacon, probe request / response, and association request / response, only SCA capabilities may be exchanged between the AP and STA (e.g., non-AP STA). In this case, the STA associated with the AP (e.g., non-AP STA) and the AP may initially connect in SCA mode with the SCA mode disabled by default. In this case, when the AP or STA (e.g., non-AP STA) wants to change the SCA mode, the AP or STA (e.g., non-AP STA) can send an SCA mode notification frame to the AP or STA (e.g., non-AP STA) by setting the SCA mode value to a first value (e.g., the first value corresponding to the enabled mode).

[0238] Alternatively or concurrently, SCA capabilities may be exchanged between the AP and STA only in beacon, probe request / response, and association request / response scenarios. In this case, the STA associated with the AP (e.g., a non-AP STA) and the AP can initially connect in SCA mode with enabled by default. In this case, when the AP or STA (e.g., a non-AP STA) wants to change the SCA mode, the AP or STA (e.g., a non-AP STA) can send an SCA mode notification frame to the AP or STA (e.g., a non-AP STA) by setting the SCA mode value to a second value (e.g., a second value corresponding to the disabled mode).

[0239] For example, an AP can determine whether it will not perform SCA on a STA (e.g., a non-AP STA) that indicates the SCA mode is a second value (e.g., the second value corresponding to the disabled mode). In this case, the AP may not send a frame to the corresponding STA via SCA, but may send a frame to a STA that sets the SCA mode to a first value (e.g., the first value corresponding to the enabled mode). For example, the STA (e.g., a non-AP STA) may include the relevant information in a new IE in a management frame that includes the STA's probe request and (re)association request.

[0240] Alternatively or concurrently, APs and STAs (e.g., non-APs) that wish to change their own SCA mode after the association process can do so via an SCA mode notification frame. For example, an AP can announce this via a beacon by setting the SCA mode value to a first value (e.g., 1, corresponding to enabled). In this case, a specific STA can include in its association request frame whether it will not perform SCA for energy-saving purposes (e.g., whether SCA mode = 0) and send it. In this case, the STA (e.g., a non-AP STA) does not perform SCA, and the AP, having determined this, may not send a frame to the STA when SCA is performed. Subsequently, when the STA (e.g., a non-AP STA) wants to perform SCA, it can send the changed / updated SCA mode to the AP by setting the SCA mode value to a first value (e.g., 1, corresponding to enabled) in the SCA mode notification frame. In this case, since the APs are also enabled, the meaning of them performing SCA on each other can be conveyed.

[0241] For example, the SCA mode notification frame can be renamed to various names. For example, it can be called NDPCA mode notification frame, mode notification frame, and node update / change frame.

[0242] - SCA Disabled Count : The following describes information related to SCA disabled counting. As mentioned above, since the term Secondary Channel Access can be replaced by NPCA, this information can be referred to as SCA disabled counting field / information / subfield / bit, etc., or by various names such as NPCA disabled counting field / information / subfield / bit, etc.

[0243] When an indication is not to perform SCA (e.g., when the indication's disabled mode is set to a value of 0), information related to the SCA disabled count can indicate that SCA will be re-enabled after the TBTT specified in the corresponding field. For example, the corresponding field can be indicated only when the SCA mode is set to 0.

[0244] Alternatively, information related to SCA disable counts may be indicated in µs. Alternatively, information related to SCA disable counts may be indicated in TUs. Alternatively, information related to SCA disable counts may be indicated based on TSF.

[0245] For example, when configuring information related to the SCA disable count based on 8 bits, a corresponding bit value of 0 could mean that the SCA mode will be held at 0 until it indicates its own enabled / disabled state via an SCA mode notification frame, regardless of time. Conversely, a corresponding bit value of 1 could mean that the SCA mode value will be set to 1 after 1 TBTT. Additionally or alternatively, the STA can set the value related to the SCA disable count to reflect interference caused by the coexistence of non-WiFi STA devices.

[0246] For example, a STA can determine whether there is interference on the PCH caused by periodic (or non-periodic and sustained for a specific period) traffic from a non-WiFi STA. In this case, the STA (e.g., a non-AP STA or AP) can switch to the SCH and perform SCA while the PCH is unavailable due to the corresponding interference. Furthermore, it can notify surrounding STAs (e.g., non-AP STAs or APs) of the unavailability time information (start time / end time / period / duration) and / or information related to the frequency band / frequency resource / channel / subchannel where the interference is occurring.

[0247] For example, the PCH may be unavailable to a mobile AP due to services from a non-WiFi STA. In this case, the corresponding mobile AP may broadcast information about the unavailability time and / or information related to the frequency band / frequency resource / channel / subchannel where interference is occurring. In this situation, a non-AP STA that has received this information may switch to the SCH during the corresponding time period and perform SCA with the mobile AP.

[0248] Based on this information, it can be determined that the frequency band / frequency resources / channel / subchannel occupied by non-WiFi STAs are included in the SCA channel set by the AP. For example, in this case, an AP with SCA mode enabled can change its own SCA mode to disabled and can announce this by setting a value reflecting the time period during which interference from non-WiFi STAs exists as the SCA disabled count value. STAs that have received this information (e.g., non-AP STAs) can determine that during the corresponding time period, the AP is in a state where frame transmission and reception are impossible due to traffic from non-WiFi STAs, without switching to the SCH. For example, from the STA's point of view, switching to an unnecessary SCH can be prevented and backoff can be performed.

[0249] Alternatively or concurrently, in 11bn, new action frames can be defined (e.g., they can be referred to by various terms such as SCA mode notification frames). For example, after association, the AP and STA (e.g., non-AP STA) can include the relevant information in an SCA mode notification frame and send it.

[0250] This specification provides examples of providing the various information related to SCA / NPCA mentioned above at the MLD level. For example, the various information presented in this specification can be configured at the MLD level, rather than at the level of a link (or a non-AP STA or AP).

[0251] The first approach related to the information configured at the MLD level is as follows.

[0252] First Method

[0253] Figure 19 and Figure 20 An example related to the first method is shown. The first method involves an SCA mode link bitmap. For example, an SCA mode link bitmap can have a length of up to 16 bits.

[0254] For example, AP MLDs and non-AP MLDs can deliver information related to another link (e.g., at least one second link) via a multi-link element through one link (e.g., at least one first link). By leveraging this, each AP attached to an AP MLD and each STA attached to a non-AP MLD can enable or disable each link via the corresponding bitmap and SCA mode subfield defined above. For example, as... Figure 19As shown, three links connect the AP MLD and a non-AP MLD, with the first link having a link ID of 0, the second link having a link ID of 1, and the third link having a link ID of 2. For example, in this case, if the AP MLD wants to enable SCA mode for links with link IDs 0 and 1, the AP MLD sets the SCA mode value in the beacon to 1 and sets the bit at the corresponding position for the respective link to 1. Figure 19 In the example, the SCA mode link bitmap can have a length of 3 bits. Figure 19 In the example, the corresponding bitmap can be set to 110. The non-AP MLD that has received this can notify the AP MLD of information related to the SCA mode for each affiliated STA (e.g., information related to enabling or disabling). Accordingly, the operations described above regarding the SCA mode can be performed for each affiliated STA or each affiliated AP (based on per link). Thus, it can be confirmed that when in the PCH (e.g., Figure 20 When the basic NAV is set on the P20 channel shown, Figure 20 AP1 and STA1 shown in the diagram perform SCA.

[0255] Alternatively or optionally, Figure 19 and Figure 20 Examples can be represented differently as follows. One example in this specification relates to an operation between a first MLD and a second MLD. For example, an example of the first MLD could be... Figure 19 AP MLD. An example of a second MLD might be... Figure 19 Non-AP MLDs. For example, the first MLD can be executed with multiple links (e.g., Figure 19 This refers to multi-link operations related to Link 1, Link 2, Link 3, etc. (as shown in the diagram). For example, the first MLD may include affiliated STAs, and the affiliated STAs may be multiple STAs (e.g., Figure 19 AP1, AP2, and AP3 are shown in the diagram. For example, the second MLD can perform operations with multiple links (e.g., Figure 19 This refers to multi-link operations related to Link 1, Link 2, Link 3, etc. (as shown in the diagram). For example, the second MLD may include affiliated STAs, and the affiliated STAs may be multiple STAs (e.g., Figure 19 The non-AP STA1, non-AP STA2, and non-AP STA AP3 are shown in this specification. According to the first STA in this specification (e.g., Figure 20 AP1 shown in the diagram can be based on the first link (e.g., Figure 19 Link 1 shown in the diagram leads to the second STA (e.g., Figure 20 STA1 shown in the figure sends the first management frame (e.g., Figure 20 The beacon shown. For example, the first management frame (e.g., Figure 20 The beacon shown may include first-bit graph information (e.g., related to the NPCA mode performed by the first MLD for multiple links) that is associated with the NPCA mode performed by the first MLD for multiple links. Figure 20 The SCA mode link bitmap shown. For example, the first STA (e.g., Figure 20 AP1 shown can be based on the first link (e.g., Figure 19 Link 1 shown in the diagram is from the second STA (e.g., Figure 20 STA1 shown receives a second management frame (e.g., Figure 20 The associated request frame shown. For example, the first graph information (e.g., Figure 20 The SCA mode link bitmap shown can be 16 bits long. For example, one bit in the first bitmap can indicate whether the first MLD performs NPCA on the link corresponding to that bit. Therefore, in Figure 20 In the example, a 110-bit graph can indicate an enabled mode for a first link, an enabled mode for a second link, and a disabled mode for a third link. For example, the first management frame (e.g., Figure 20 The beacon shown in the diagram may also include a first STA (e.g., Figure 20 The first NPCA mode information related to the NPCA mode shown in AP1) (e.g., Figure 20 The SCA mode shown is 1 (enabled). For example, the NPCA mode based on the first STA is enabled, and the first NPCA mode information (e.g., Figure 20 The SCA mode shown: 1 (Enabled) can be set to the first value (e.g., Figure 20 The “1” shown). For example, after exchanging the first management frame (e.g., Figure 20 The beacon shown) and the second management frame (e.g., Figure 20 Following the association request frame shown, it can be handled by the first STA (e.g., Figure 20 AP1) performs NPCA / SCA. For example, the first STA performs NPCA to the main channel (e.g., S20 channel) based on the basic NAV set for the main channel of the first link. Figure 20 The switching of the SCH (for backoff). For example, it can be achieved by the first STA (e.g., Figure 20The basic NAV is set by receiving the OBSS PPDU from AP1. After the first STA performs the NPCA primary channel handover, the first STA can acquire the TXOP for the NPCA primary channel based on backoff performed on the NPCA primary channel. For example, based on the acquired TXOP, the first STA can send a message to the second STA (e.g., based on the NPCA primary channel (and at least one SCH / NPCA channel based on channel extension) via the NPCA primary channel (and at least one SCH / NPCA channel based on channel extension). Figure 20 The STA1 shown sends frames (e.g., Figure 20 The control frame to STA1 shown in the figure.

[0256] like Figure 19 and Figure 20 As shown, the first method described above can indicate the same SCA mode for multiple links. It can be improved in various ways. Figure 19 and Figure 20 Related methods. For example, through Figures 21 to 23 An additional second method is proposed for situations where a non-AP MLD wants to change to disable for STA2 and enable for STA3. For example, a second method related to information configured at the MLD level could be proposed.

[0257] Figures 21 to 23 An example related to the second method is shown.

[0258] The second method described below can be executed based on the various information / bits / subfields / fields presented below.

[0259] SCA is enabled (e.g., 1 bit).

[0260] The following describes information related to SCA enabled presence. As mentioned above, since the term SCA can be replaced by NPCA, this information can be referred to as the SCA enabled presence field / information / subfield / bit, etc., or by various names such as NPCA enabled presence field / information / subfield / bit, etc.

[0261] Information related to SCA enable can be configured as bits of various lengths, and can be configured as, for example, a field / information / subfield of 1 bit length. For example, if the corresponding value is set to a first value (or 1), it can mean that the enable link bitmap field / information / subfield / bit described below is present. For example, the first value can indicate that SCA mode is enabled for a specific link according to the enable link bitmap described below. For example, if the corresponding value is set to a second value (or 0), it means that the enable link bitmap is not present.

[0262] SCA is disabled (e.g., 1 bit).

[0263] The following describes information related to the presence of SCA being disabled. As mentioned above, since the term SCA can be replaced by NPCA, this information can be referred to as the SCA disabled presence field / information / subfield / bit, etc., or by various names such as NPCA disabled presence field / information / subfield / bit, etc.

[0264] Information related to the presence of SCA disabling can be configured using bits of various lengths, and can be configured as, for example, a field / information / subfield of 1 bit length. For example, if the corresponding value is set to the first value (or 1), it can mean that the disabled link bitmap field / information / subfield / bit described below is present. For example, the first value indicates the meaning of the disabled SCA mode for a specific link according to the disabled link bitmap. For example, if the corresponding value is set to the second value (or 0), it means that the disabled link bitmap is not present.

[0265] Enable link bitmap (0 or 16 bits)

[0266] The following describes information related to enabling the link bitmap. This information may be referred to by various names such as Enable Link Bitmap field / information / subfield / bit, etc.

[0267] For example, the information associated with the enabled link bitmap can have a bitmap of up to 16 bits in size only when the aforementioned SCA enable presence value is set to the first value (or 1). Alternatively, the information associated with the enabled link bitmap can indicate the links that have SCA mode enabled by setting the bits corresponding to each link to 1.

[0268] For example, as in Figures 21 to 23 In the example, three links connect the AP MLD and the non-AP MLD, and the link ID of the first link can be 0, the link ID of the second link can be 1, and the link ID of the third link can be 2. In such an example, to enable SCA mode for links with link ID 1 and link ID 2, the bit at the position corresponding to the respective link can be set to 1.

[0269] Disable link bitmap (0 or 16 bits)

[0270] The following text describes information related to disabling the link bitmap. This information may be referred to by various names such as Disable Link Bitmap field / information / subfield / bit, etc.

[0271] For example, the information associated with the disabled link bitmap can have a bitmap of up to 16 bits in size only when the aforementioned SCA disable presence value is set to the first value (or 1). Alternatively, the information associated with the disabled link bitmap indicates which links should be disabled in SCA mode by setting the bits corresponding to each link to 1.

[0272] For example, as in Figures 21 to 23 In the example, three links connect the AP MLD and the non-AP MLD, and the link ID of the first link can be 0, the link ID of the second link can be 1, and the link ID of the third link can be 2. In such an example, if the SCA mode for the links with link ID 1 and link ID 2 is to be disabled, the bit at the position corresponding to the corresponding link is set to 1.

[0273] The following is for reference Figures 21 to 23 The second method is described below. It can be executed sequentially. Figure 22 and Figure 23 The operation. That is, Figure 22 The operation can be represented as Figure 23 S2310. For example... Figure 21 As shown, AP1 and AP2, attached to the AP MLD, are enabled, while AP3 is disabled. Furthermore, as shown, STA1 and STA3, associated with the non-AP MLD, are enabled, while STA2 is disabled. Therefore, when the corresponding channel (PCH) is determined to be busy due to the OBSS PPDU set on the PCH, only AP1 and STA1 perform a switch to the SCH (e.g., S20 channel or NPCA main channel), and SCA / NPCA can then be performed. Subsequently, it is possible that the non-AP MLD may want to enable link 2 and disable link 3. According to the second method described above, the non-AP MLD can set the SCA enable presence value to 1 and the SCA disable presence value to 1. Furthermore, the non-AP MLD can send an SCA mode notification frame by setting the bitmaps of the links to be enabled and disabled. The AP MLD that has received the corresponding signal / frame can perform SCA with STA2 via link 2. If a non-AP MLD has no links to be disabled and wants to enable only link 3, it can set the SCA disable presence value to 0, and the disable link bitmap can have a length of 0 bits. Figures 21 to 23 The advantage of the method shown is that it is compatible with... Figure 19 and Figure 20 Compared to the method shown, it can enable or disable each link individually through a single frame.

[0274] Alternatively or optionally, Figures 21 to 23 Examples can be represented differently as follows. Figures 21 to 23The example is Figure 19 and Figure 20 An improvement to the example, and Figures 21 to 23 Technical features can be combined with Figure 19 and Figure 20 The technical features operate together. For example, the examples in this specification relate to operations between a first MLD and a second MLD. For example, an example of the first MLD could be... Figure 21 AP MLD. An example of a second MLD could be... Figure 21 Non-AP MLDs. For example, the first MLD can be executed with multiple links (e.g., Figure 21 This refers to multi-link operations related to Link 1, Link 2, Link 3, etc. (as shown in the diagram). For example, the first MLD may include affiliated STAs, and the affiliated STAs may be multiple STAs (e.g., Figure 21 AP1, AP2, and AP3 are shown in the diagram. For example, the second MLD can perform operations with multiple links (e.g., Figure 21 This refers to multi-link operations related to Link 1, Link 2, Link 3, etc. (as shown in the diagram). For example, the second MLD may include affiliated STAs, and the affiliated STAs may be multiple STAs (e.g., Figure 21 The non-AP STA1, non-AP STA2, and non-AP STA AP3 are shown in this specification. According to the first STA in this specification (e.g., Figure 23 AP1 shown in the diagram can be based on the first link (e.g., Figure 21 Link 1 shown in the diagram leads to the second STA (e.g., Figure 22 STA1 shown in the figure sends the first management frame (e.g., Figure 22 (The beacon shown in the image). For example, the first management frame (e.g., Figure 22 The beacon shown may include first-bit graph information (e.g., related to the NPCA mode performed by the first MLD for multiple links) that is associated with the NPCA mode performed by the first MLD for multiple links. Figure 22 The enabled link bitmap shown. For example, the first bitmap information could be the enabled bitmap (e.g., Figure 22 The enabled link bitmap shown is an example. For instance, the enabled bitmap can be 16 bits long. For example, based on the NPCA mode enabled on a link, a corresponding bit in the enabled bitmap can be set to a first value (e.g., "1"). Therefore, in... Figure 22 In the example, the value "110" can be set corresponding to the SCA / NPCA mode of the three links. For example, the first management frame (e.g., Figure 22 The beacon may also include enabling presence information (e.g., Figure 22 SCA enable presence). For example, enable presence information can have a length of 1 bit. For example, when included in the enable bitmap (e.g., included in...). Figure 22When at least one bit in the enabled link bitmap of the beacon is set to a first value, the value of the enabled presence information can be set to a first value (e.g., "1"). For example, in the first management frame (e.g., Figure 22 The beacon may also include a disable bitmap with a length of 16 bits (e.g., included in...). Figure 22 The disabled link bitmap in the beacon). Based on the mode of disabling NPCA on a link, the corresponding bit in the disabled bitmap can be set to a first value (e.g., "1"). Therefore, in Figure 22 In the example, the value "001" can be set corresponding to the SCA / NPCA mode of the three links. For example, the first management frame (e.g., Figure 22 The beacon may also include disabling presence information (e.g., including in...). Figure 22 The presence of SCA is disabled in the beacon. For example, the presence-disable information can be 1 bit long. For example, when included in the disable bitmap (e.g., included in...). Figure 22 When at least one bit in the disabled link bitmap of the beacon is set to a first value, the value of the disabled presence information can be set to a first value (e.g., "1").

[0275] Alternatively or optionally, Figures 21 to 23 Examples can be represented differently as follows. For example, the first STA (e.g., Figure 22 AP1 shown can be based on the first link (e.g., Figure 21 Link 1 shown in the diagram is from the second STA (e.g., Figure 22 STA1 shown receives a second management frame (e.g., Figure 22 The associated request frame shown. For example, second bitmap information (e.g., included in the image). Figure 22 The enabled link bitmap in the association request can have a length of 16 bits. For example, the second bitmap information can be an enabled bitmap (e.g., included in...). Figure 22 The enabled link bitmap in the associated request. For example, the enabled bitmap can have a length of 16 bits. For example, based on the mode of enabling NPCA on a link, a corresponding bit in the enabled bitmap can be set to a first value (e.g., "1"). Therefore, in Figure 22 In the example, the value "101" can be set to correspond to the SCA / NPCA modes of the three links. For example, the first management frame (e.g., Figure 22 The association request may also include enabling existence information (e.g., including in the association request). Figure 22 The SCA enable presence is included in the associated request. For example, the enable presence information can be 1 bit long. For example, when included in the enable bitmap (e.g., included in...). Figure 22When at least one bit in the enabled link bitmap of the association request is set to a first value, the value of the enabled presence information can be set to a first value (e.g., "1"). For example, in a second management frame (e.g., Figure 22 The associated request may also include a disabled bitmap with a length of 16 bits (e.g., included in...). Figure 22 The disabled link bitmap in the association request). Based on the mode of disabling NPCA on a link, the corresponding bit in the disabled bitmap can be set to a first value (e.g., "1"). Therefore, in Figure 22 In the example, the value "010" can be set corresponding to the SCA / NPCA mode of the three links. For example, the second management frame (e.g., Figure 22 The association request may also include disabling presence information (e.g., including in the association request). Figure 22 The SCA is disabled in the associated request. For example, the disabled presence information can be 1 bit long. For example, when included in a disabled bitmap (e.g., Figure 22 When at least one bit in the associated request disable link bitmap is set to a first value, the value of the disable presence information can be set to a first value (e.g., "1").

[0276] Alternatively or optionally, Figures 21 to 23 Examples can be represented differently as follows. For example, after exchanging the first management frame (e.g., Figure 22 The beacon shown) and the second management frame (e.g., Figure 22 Following the associated request frame shown, execution can be performed by the first STA (e.g., Figure 22 NPCA / SCA is performed on the AP1 channel. For example, based on the basic NAV set for the primary channel of the first link, the first STA performs NPCA on the primary channel (e.g., S20 channel or...). Figure 22 The switching of the SCH (for backoff). For example, it can be achieved by the first STA (e.g., Figure 22 The basic NAV is set by receiving the OBSS PPDU from AP1. After the first STA performs an NPCA primary channel handover, the first STA can acquire a TXOP for the NPCA primary channel based on backoff performed on the NPCA primary channel. For example, based on the acquired TXOP, the first STA can send a message to the second STA (e.g., based on the NPCA primary channel (and at least one SCH / NPCA channel based on channel extension) via the NPCA primary channel (and at least one SCH / NPCA channel based on channel extension). Figure 22 The STA1 shown sends frames (e.g., to...) Figure 22 The control frame to STA1 shown in the figure.

[0277] Alternatively or optionally, Figures 21 to 23 Examples can be represented differently as follows. For example, the second STA (e.g., Figure 22 and Figure 23 AP1) can send to the first STA (e.g., Figure 22 and Figure 23 AP1) sends a notification frame (e.g., Figure 23 The SCA mode notification frame shown is an example. For instance, the notification frame may include a disabled bitmap that has been changed / updated at the second STA. Figure 23 Disabled link bitmap) and / or enabled bitmap ( Figure 23 The enabled link bitmap). For example, the notification frame may include enabled presence information indicating the presence of a disabled bitmap (e.g., Figure 23 SCA enabled presence). For example, the notification frame may include disabled presence information indicating the presence of the enabled bitmap (e.g., Figure 23 (SCA is disabled). When a notification frame is delivered to the first STA, the first STA and the second STA can exchange notification frames based on the exchanged notification frames (e.g., in...). Figure 23 The SCA mode notification frame shown in the image executes NPCA / SCA. For example, in... Figure 23 In the example, after the SCA mode notification frame is exchanged, the AP MLD and non-AP MLD can confirm that NPCA / SCA is enabled for link 2 and disabled for link 3. Therefore, in Figure 23 In the example, NPCA / SCA can be performed on link 2, but not on link 3.

[0278] In the following text, a third approach related to the information configured at the MLD level may be proposed.

[0279] The third method described below involves techniques for exchanging information related to channel handover between STA1 and STA2 at the MLD level, for example, in Figure 18 In addition, information related to channel switching associated with the third method involves... Figure 24 and Figure 25 The NAV sharing is illustrated below. NAV sharing is described first, followed by a technique for exchanging channel handover-related information at the MLD level according to a third method.

[0280] For example, in Figure 18In the example, STA1 (e.g., AP) and STA2 (e.g., non-AP STA) cannot know precisely whether a NAV (e.g., basic NAV) is set on the PCH. In other words, sharing NAV information with each other may be helpful for SCA / NPCA, but often it may be difficult to deliver information via a channel on which a NAV is set (e.g., P20 channel). With this in mind, multi-link operation can be used for NAV sharing. For example, regarding NAV information, one or more pieces of information may be included as follows (at least one of information related to NAV information, link ID, channel switching indication, and / or channel switchback indication, as described below). The corresponding information can be transmitted using data frames by being included in HE A-control, etc., or based on separate management frames.

[0281] Among the various information shared with NAV, NAV information is described as follows.

[0282] NAV Information

[0283] The information related to NAV information described above can indicate the remaining NAV duration from the start (or end) time of the frame through which the corresponding NAV information is delivered. The remaining NAV information indicated by the aforementioned NAV information can be based on two octets of the duration / ID field included in the conventional MAC header. Alternatively, the field size (of the corresponding NAV information) can be reduced by using a granularity similar to the TXOP field in the PHY header (8µs, 32µs, 128µs, etc.). For example, one or two bits can indicate the granularity, and the remaining six or more bits can be used to indicate the actual NAV duration information. Since the NAV duration indicated as described above is information received on another link, the actual application can be determined based on the TSF of the link where the NAV is set.

[0284] The above information related to NAV information can be modified as follows. For example, the NAV information can indicate the end time of the NAV instead of its duration. For instance, the end time of the NAV can be called the NAV end time, i.e., NAV_ET. Since the NAV_ET of one link must be notified on another link, and each link's AP operates on a per TSF basis, it is necessary to adjust the timing. For example, when delivering NAV_ET on one link, the TSF of the link corresponding to NAV_ET can be taken into account. For example, if the TSF difference between two links is 30, it is preferable to indicate it with a 30-bit drift. However, if NAV_ET gives approximately 8 octets of information corresponding to the TSF, it may have too much overhead. Therefore, like TWT, it can be configured with 2 octets by utilizing some bits of the TSF.

[0285] Among the various information shared with NAV, the Link ID is described below.

[0286] The corresponding link ID can be the ID of a link that has the aforementioned NAV duration set (e.g., the remaining NAV information indicated by the NAV information or information related to NAV_ET). The link ID can be 4 bits long, or it can be 1 / 2 / 3 bits long, or 5 bits or more long.

[0287] Figure 24 and Figure 25 This is a diagram illustrating operations related to NAV sharing.

[0288] For example, such as Figure 24 As shown, an AP MLD may include at least two APs (e.g., AP1, AP2), and a non-AP MLD may include at least two non-AP STAs (non-AP STA1, non-AP STA2).

[0289] Figure 24 and Figure 25 An example of basic NAV sharing using AP MLD is shown. As illustrated, the basic NAV can be set by AP1 on the PCH (shown as PCH1 or P20 channel). In this case, as... Figure 25 As shown, AP2 can include NAV information for AP1 in the frame (the NAV information for AP1 shown) and advertise it individually to a single STA, or broadcast it so that several STAs can recognize it. In this case, within the non-AP MLD that has already recognized this information, NAV sharing is performed, as follows: Figure 25 As shown. Specifically, as Figure 25As shown, when a non-AP STA2 receives NAV information for AP1 (the NAV information of AP1 shown), the received information can be shared within the non-AP MLD. Therefore, non-AP STA1 can acquire the received information (the NAV information of AP1). Consequently, non-AP STA1 can switch to SCH because it can expect the shown AP1 to perform SCA, even if the current PCH (e.g., ...) Figure 24 PCH1 shown is idle.

[0290] Alternatively or concurrently, this specification may provide information related to channel handover indication and information related to channel handover return indication.

[0291] Channel switching indication

[0292] This information can be a notification that a switch to the SCH (or S20 channel, or NPCA main channel) has taken place. For example, information related to a channel switching indication can be 1 bit long.

[0293] Channel switchback indication: This information can be a notification that a switch to the PCH (or P20 channel) has taken place, consisting of a field, subfield, or bit. For example, information related to a channel switchback indication could be 1 bit long.

[0294] For example, it can be Figure 25 The non-AP STA1 is shown with a basic NAV set on its PCH (e.g., P20 channel or PCH1). In this case, the non-AP STA2 can include information in the frame to be sent to AP2 regarding whether the non-AP STA1 has set a basic NAV on its PCH (e.g., P20 channel or PCH1) and whether it has switched to its SCH (e.g., S20 channel or NPCA main channel) (e.g., setting the channel switching indication to a first value (e.g., 1)). When Figure 25 When AP2 receives a corresponding frame, it shares relevant information within the AP MLD. As a result, AP1, included in the corresponding AP MLD, can identify / acknowledge channel switching by non-AP STA1. For example, AP1 can determine that a non-AP STA1 has switched to SCH and is performing backoff on a channel that is not aligned with AP1's channel. Therefore, AP1 can send frames to STAs other than non-AP STA1. This prevents the AP from performing unnecessary frame exchanges with STA1 (i.e., exchanging unsuccessful frames), thus preventing an unnecessary increase in the AP's CW value.

[0295] Alternatively, it can notify AP1 (or AP MLD) that non-AP STA1 has switched back to PCH by setting the channel switchback indication value to a first value (e.g., 1). Alternatively, the channel switchback indication information can be delivered along with information related to the aforementioned NAV information. In this way, the AP that has received the corresponding information can obtain information about when non-AP STA1 will switch back to PCH again.

[0296] Various examples including the first, second, and third methods described above can be represented using process flowcharts.

[0297] Figure 26 This is a process flowchart illustrating the above example in this specification. Figure 26 This can involve the STA's transmission process. Figure 26 The operation can be performed in the first STA (e.g., AP). According to step S2610, the first STA (e.g., AP) with SCA capability can set its own SCA mode to a first or second value and perform an announcement. According to step S2620, the first STA can receive a response to its sent SCA mode from at least one second STA (e.g., a non-AP STA). According to step S2630, when the SCA mode of all second STAs (e.g., all non-AP STAs) is set to the second value (e.g., 0), the first STA may not perform a handover to the SCH even if the PCH is determined to be busy due to the OBSS PPDU. According to step S2640, when the SCA mode of at least one second STA is set to the first value (e.g., 1), if the PCH is determined to be busy due to the OBSS PPDU, the first STA performs a handover to the SCH and can perform SCA with at least one second STA.

[0298] Figure 27 This is a process flowchart illustrating the above example in this specification. Figure 27 This can involve the STA's receiving process. Figure 27The operation can be performed in a second STA (e.g., a non-AP STA). According to step S2710, the second STA can receive frames related to the SCA mode of the first STA (e.g., AP) that have SCA capability. According to step S2720, if the SCA mode of the first STA (e.g., AP) is a second value (e.g., 0), the second STA (e.g., a non-AP STA) can notify the first STA of its own SCA mode, or set its own SCA mode to the second value (e.g., 0). According to step S2730, the second STA can maintain its SCA mode at 0 until the SCA mode of the first STA (e.g., AP) is updated to 1. According to step S2740, when the SCA mode of the first STA (e.g., AP) is updated to 1, the second STA (e.g., a non-AP STA) can return to the initially set SCA mode (e.g., the SCA mode corresponding to the first value). According to step S2740, if the SCA mode of the first STA (AP) is a first value (e.g., 1), the second STA (non-AP STA) can notify the AP of its own SCA mode. According to step S2750, only if the SCA mode of the first STA (AP) is a first value (e.g., 1), the second STA (non-AP STA) determines whether the PCH is busy due to the OBSS PPDU, and if the PCH is busy, it can perform a switch to the SCH and perform SCA.

[0299] Various examples, including the first method, the second method, and the third method, based on the examples in this specification can be modified in various ways. These various examples in this specification can be operated according to the following technical features.

[0300] Even during the period when a NAV (e.g., a basic NAV) is set on the PCH, a STA (e.g., an AP or non-AP STA) performing the SCA / NPCA of this specification can still transmit frames / PPDUs on the SCH. For example, an STA (e.g., an AP or non-AP STA) can obtain an idle state determined by backoff performed on one or more SCHs (e.g., the S20 channel or the NPCA master channel) (and the CCA result of one or more SCHs on which backoff is not performed). In this way, the STA can transmit frames / PPDUs over at least one SCH (excluding the PCH / puncturing the PCH).

[0301] Alternatively or concurrently, a TXOP that begins with a frame / PPDU transmission on the SCH (e.g., the S20 channel or the NPCA master channel) can be set to end before the NAV end time on the PCH. The TXOP length can be set / indicated by the duration / ID field of the corresponding frame. For example, the value of the duration / ID field can be set to the value of the time (including the inter-frame interval (IFS)) required for frame / PPDU exchange after the corresponding frame / PPDU.

[0302] Alternatively or additionally, the EDCA parameter set for each SCH on which backoff is performed can be set to the EDCA parameter set on the PCH, the MU EDCA parameter set, or a new EDCA parameter set. This EDCA parameter set can be applied to all SCHs identically or separately (or differently).

[0303] In this specification, even during the period when NAV (e.g., basic NAV) is set on the PCH, a STA (e.g., AP or non-AP STA) receiving frames transmitted via SCA / NPCA can perform frame detection on the SCH (e.g., S20 channel or NPCA main channel). For example, an STA (e.g., AP or non-AP STA) can perform backoff on the SCH because it has a frame to transmit, or even when it does not have a frame to transmit, it can attempt to receive on the SCA whether a frame addressed to itself exists. Furthermore, the STA can perform NAV setting / resetting based on the value of the duration / ID field of the frame detected on the SCH.

[0304] Alternatively or additionally, the EDCA parameter set for each SCH on which backoff is performed can be set to the EDCA parameter set on the PCH, the MU EDCA parameter set, or a new EDCA parameter set. This EDCA parameter set can be applied to all SCHs identically or individually (or differently).

[0305] Alternatively or additionally, STAs and APs with SCA capability can confirm whether a STA or AP is performing SCA by including an indication in management frames (e.g., beacon, probe request / response frame, SCA mode request / response frame, etc.) regarding whether SCA is performed when a basic NAV is set on the PCH.

[0306] Alternatively, when SCA mode is disabled (SCA allow can be set to 0), the SCA disable count field can be used to indicate when SCA mode will be disabled.

[0307] Alternatively, the AP MLD or non-AP MLD can indicate whether SCA mode is enabled / disabled for each link via an SCA mode link bitmap.

[0308] Alternatively, multiple links can be individually indicated in a single frame by enabling link bitmaps, disabling link bitmaps, enabling SCA presence, and disabling SCA presence.

[0309] Figure 28 This is a process flowchart illustrating an example of the procedures described in this specification. For ease of description, Figure 28 The examples are described as being executed by the first STA. However, the examples in this specification can also be executed by MLD. That is, Figure 28 Each step can be represented as being performed by the first STA, or it can be represented as being performed by the first MLD attached to the first STA.

[0310] As shown in the figure, step S2810 involves sending a first management frame from the first STA (station) to the second STA. For example, the first management frame can be sent via a first link. For example, the first STA can be an AP or a non-AP STA. For example, the first STA can be any one of multiple APs attached to an AP MLD. For example, the first STA can be any one of multiple non-AP STAs attached to a non-AP STA MLD. For example, the first STA can be... Figures 19 to 25 Any of the AP1s shown, or Figures 19 to 25 Any of the STA1s shown in the diagram (or non-AP STA1s). For example, the second STA could be... Figures 19 to 25 Any of the STA1s shown in the table (or non-AP STA1s), or Figures 19 to 25 Any of the AP1s shown in the diagram.

[0311] For example, the first management frame may include first bit map information related to the NPCA (Non-Master Channel Access) mode performed by the first MLD for multiple links. For example, the first management frame may be... Figure 20 or Figure 22 The beacon shown. For example, the first-bit graph information associated with NPCA (Non-Master Channel Access) mode could be... Figure 20 The image shows a link bitmap for SCA mode.

[0312] Alternatively, the first management frame may also include NPCA capability information relating to whether the first STA has NPCA-related capabilities. For example, the NPCA capability information may be information relating to the aforementioned secondary channel access capabilities. For example, the NPCA capability information may have a length of 1 bit.

[0313] Alternatively or concurrently, the first management frame may also include first NPCA mode information related to the NPCA mode of the first STA. For example, the first NPCA mode information may include... Figure 20The SCA mode information in the beacon shown. For example, the first NPCA mode information can be set to a first value based on whether the NPCA mode of the first STA is enabled. For example, the first NPCA mode information can be set to a second value based on whether the NPCA mode of the first STA is disabled.

[0314] Alternatively or concurrently, the first management frame may also include an enable bitmap. For example, the enable bitmap may be included in... Figure 22 The first management frame may also include an enable link bitmap in the beacon. Alternatively, the first management frame may also include enable presence information. For example, the enable presence information may be a 1-bit message indicating whether the enable bitmap exists. Figure 22 The SCA enable information is present in the beacon.

[0315] Alternatively or concurrently, the first management frame may also include a disabled bitmap. For example, the disabled bitmap may be included in... Figure 22 The first management frame may also include a disabled link bitmap in the beacon. Alternatively, the first management frame may also include disabled presence information. For example, the disabled presence information may be a 1-bit message indicating whether the disabled bitmap exists. Figure 22 The SCA is disabled in the beacon.

[0316] Alternatively or concurrently, the first management frame may also include first information relating to whether another STA attached to the first MLD has switched to the NPCA primary channel. For example, the first information may be the channel switching indication information described above.

[0317] Alternatively or additionally, it may include second information relating to whether another STA attached to the first MLD has switched from the NPCA main channel to the main channel. For example, the second information may be the aforementioned channel switchback indication information.

[0318] As shown in the figure, step S2820 involves the first STA (station) receiving a second management frame from a second STA. For example, the second management frame can be received via a first link.

[0319] Alternatively, the second management frame may also include NPCA capability information relating to whether the second STA has NPCA-related capabilities. For example, the NPCA capability information may be information relating to the aforementioned secondary channel access capabilities. For example, the NPCA capability information may be 1 bit in length.

[0320] Alternatively or additionally, the second management frame may also include second NPCA mode information related to the NPCA mode of the second STA. For example, the second NPCA mode information may include... Figure 20The SCA mode information in the associated request is shown. For example, the second NPCA mode information can be set to a first value based on whether the NPCA mode of the second STA is enabled. For example, the second NPCA mode information can be set to a second value based on whether the NPCA mode of the second STA is disabled.

[0321] Alternatively or concurrently, the second management frame may also include an enable bitmap. For example, the enable bitmap may be included in... Figure 22 The link enable bitmap is included in the association request. Alternatively, the second management frame may also include enable presence information. For example, the enable presence information may be a 1-bit message indicating whether the enable bitmap exists. Figure 22 The SCA enablement information exists in the associated request.

[0322] Alternatively or additionally, the second management frame may also include a disabled bitmap. For example, the disabled bitmap may be included in... Figure 22 The link-disabled bitmap is included in the association request. Alternatively, the second management frame may also include disable presence information. For example, the disable presence information may be a 1-bit message indicating whether the disable bitmap exists. Figure 22 The SCA disabling information exists in the associated request.

[0323] Based on step S2830 shown, NPCA / SCA can be performed based on the first management frame and the second management frame. For example, the first STA performs NPCA to the NPCA main channel (e.g., channel S20) based on the basic NAV set for the main channel of the first link. Figure 22 The switching of the SCH (for backoff). For example, it can be achieved by the first STA (e.g., Figure 22 The basic NAV is set by receiving the OBSSPPDU from AP1. After the first STA performs the NPCA primary channel handover, the first STA can acquire the TXOP for the NPCA primary channel based on backoff performed on the NPCA primary channel. For example, based on the acquired TXOP, the first STA can send a message to the second STA (e.g., based on the NPCA primary channel (and at least one SCH / NPCA channel based on channel extension) via the NPCA primary channel (and at least one SCH / NPCA channel based on channel extension). Figure 22 The STA1 shown sends frames (e.g., Figure 22 (The control frame to STA1 shown). Step S2830 is not a necessary step and can be omitted. Alternatively, step S2830 can be performed after step S2840, as described below.

[0324] Based on the illustrated step S2840, the second STA (e.g., Figure 22 and Figure 23AP1) can send to the first STA (e.g., Figure 22 and Figure 23 AP1) sends a notification frame (e.g., Figure 23 The SCA mode notification frame shown in the image. For example, the notification frame may include a disabled bitmap that has been changed / updated at the second STA ( Figure 23 Disabled link bitmap) and / or enabled bitmap ( Figure 23 The enabled link bitmap). For example, the notification frame may include enabled presence information indicating the presence of a disabled bitmap (e.g., Figure 23 SCA enabled presence). For example, the notification frame may include disabled presence information indicating the presence of the enabled bitmap (e.g., Figure 23 (SCA is disabled). When a notification frame is delivered to the first STA, the first STA and the second STA can exchange notification frames based on the exchanged notification frames (e.g., in...). Figure 23 The SCA mode notification frame shown in the image executes NPCA / SCA.

[0325] Alternatively, step S2840 may be performed by the first STA instead of the second STA. Specifically, the notification frame may include disabled and / or enabled bitmaps that have been changed / updated at the first STA. For example, the notification frame may be generated by the first STA and sent to the second STA. Step S2840 is not a necessary step and its execution may be omitted.

[0326] Figure 29 This is a process flowchart illustrating an example of the procedures described in this specification. For ease of description, Figure 29 The examples are described as being executed by a second STA. However, the examples in this specification can also be executed by MLD. That is, Figure 29 Each step can be represented as being performed by a second STA, or it can be represented as being performed by a second MLD attached to a second STA.

[0327] As shown in the figure, step S2910 involves the second STA receiving a first management frame from the first STA (station). For example, the technical features of the first management frame applied to step S2910 may be the same as those in step S2810. Therefore, redundant descriptions are omitted.

[0328] As shown in the figure, step S2920 involves sending a second management frame from the second STA to the first STA (station). For example, the technical features of the second management frame applied to step S2920 can be the same as those in step S2820. Therefore, redundant descriptions are omitted.

[0329] Based on step S2930 shown, NPCA / SCA can be performed based on the first management frame and the second management frame. For example, the technical features of step S2930 can be the same as those of step S2830. Therefore, redundant descriptions are omitted.

[0330] Based on the illustrated step S2940, the first STA or the second STA can send the aforementioned notification frame (e.g., in...). Figure 23 (The SCA mode notification frame shown in the figure). The notification frame in step S2940 can be the same as the notification frame in step S2930 described above. Therefore, redundant descriptions are omitted.

[0331] The technical features of this specification can be implemented by various devices. The devices described in this specification can be... Figure 1 / Figure 14 The apparatus described herein may include at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions for performing operations based on execution by the at least one processor.

[0332] For example, the processor can be Figure 1 and / or Figure 14 The processor described herein. That is, as stated above, the processor in this specification may include at least one of a DSP (Digital Signal Processor), a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). The processor includes not only computers with various architectures such as single / multiprocessor architectures and sequential (Von Neumann) / parallel architectures, but also dedicated circuitry such as FPGAs, ASICs, signal processing devices, and other devices. For example, the processor in this specification may be a SNAPDRAGON® series processor manufactured by Qualcomm®, an EXYNOS® series processor manufactured by Samsung®, an A-series processor manufactured by Apple®, a HELIO® series processor manufactured by MediaTek®, an ATOM® series processor manufactured by Intel®, or a processor enhancing these.

[0333] For example, the instructions may refer to computer program instructions that are executed by the at least one processor. These (computer program) instructions provide logic and / or routines that allow the technical features of this specification to be executed by the processor. The at least one processor may load and execute the computer program by reading the at least one memory.

[0334] The computer program defined by these instructions can reach the apparatus of this specification (e.g., STA) via a suitable delivery mechanism. The delivery mechanism may be, for example, a computer-readable storage medium, a computer program product, a memory device, a recording medium such as a CD-ROM or DVD, or an article tangibly embodying the computer program. The delivery mechanism may be a signal configured to reliably transmit the computer program via a wireless or electrical connection.

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

[0336] For example, the memory can be Figure 1 and / or Figure 14 The memory described herein. That is, as stated above, the memory of this specification can store control information related to the operation of the STA in this specification or information related to signals sent and received by the corresponding STA (e.g., PPDUs including management / control / data frames).

[0337] The technical features of this specification can also be implemented as at least one computer-readable medium (CRM). The CRM includes instructions based on instructions executed by at least one processor described above. The instructions stored in the CRM can be the aforementioned computer program instructions.

[0338] The apparatus described in this specification may also include a transceiver. The transceiver may be operatively connectable to a memory / processor, etc. The transceiver may be... Figure 1 and / or Figure 14 The transceiver shown.

[0339] The technical features described above in this specification can be applied to various applications or business models. For example, these technical features can be applied to wireless communication in devices that support artificial intelligence (AI).

[0340] Artificial intelligence (AI) refers to the field of studying artificial intelligence or the methods that enable the creation of AI, while machine learning refers to the field of addressing various problems within the domain of AI and its research methods to solve them. Machine learning is also defined as algorithms that improve the performance of a specific task through stable experience with that task.

[0341] Artificial neural networks (ANNs) are models used in machine learning, and can refer to overall models capable of solving problems. They consist of artificial neurons (nodes) that form a network through the combination of synapses. An artificial neural network can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation functions that generate output values.

[0342] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes 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 in response to the input signal, weights, and bias inputs via a synapse.

[0343] Model parameters refer to the parameters determined through learning, including the weights of synaptic connections and the biases of neurons. Hyperparameters, on the other hand, are parameters that must be set before learning in a machine learning algorithm, including the learning rate, number of iterations, mini-batch size, and initialization function.

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

[0345] Based on the learning method, machine learning can be divided into supervised learning, unsupervised learning, and reinforcement learning.

[0346] Supervised learning refers to the method of training an artificial neural network in states where labels are given for the learning data, and the labels can refer to the correct answer (or result value) that the artificial neural network must infer when the learning data is input into the artificial neural network. Unsupervised learning refers to the method of training an artificial neural network in states where no labels are given for the learning data. Reinforcement learning refers to the learning method of training an agent defined in a specific environment to select actions or action sequences that maximize the cumulative reward in each state.

[0347] In artificial neural networks, machine learning implemented as deep neural networks (DNNs) with multiple hidden layers is also called deep learning, and deep learning is a part of machine learning. In the following text, machine learning will be used in the sense that it includes deep learning.

[0348] Furthermore, the aforementioned technical features can be applied to wireless communication for robots.

[0349] A robot can refer to a machine that automatically processes or operates a given task through its own capabilities. In particular, a robot that has the ability to recognize its environment, determine and execute operations autonomously can be called an intelligent robot.

[0350] Depending on their purpose or application area, robots can be categorized into industrial, medical, domestic, and military applications. A robot may include a drive unit containing actuators or motors to perform various physical operations, such as moving the robot's joints. Additionally, mobile robots include wheels, brakes, propellers, etc., in their drive units and can move on the ground or fly in the air via these drive units.

[0351] Furthermore, the aforementioned technical features can be applied to devices that support extended reality.

[0352] Extended reality generally refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology provides real-world objects or backgrounds only as CG images, AR technology provides virtually created CG images on top of real-world object images, and MR technology is a computer graphics technology that mixes and combines virtual objects from the real world to provide them.

[0353] MR (Mixed Reality) technology is similar to AR (Augmented Reality) technology in that it displays real and virtual objects together. However, the difference lies in that in AR technology, virtual objects are used to complement real objects, while in MR technology, virtual and real objects are used with the same characteristics.

[0354] XR technology can be applied to HMD (Head-Up Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktop computers, TVs, digital signage, etc., and devices that use XR technology can be called XR devices.

Claims

1. A method executed in a wireless local area network (WLAN) system, the method comprising: The first STA sends the first management frame to the second STA based on the first link. The first STA is attached to a first multi-link device (MLD) that performs multi-link operations related to multiple links, and the second STA is attached to a second MLD that performs multi-link operations related to the multiple links. The first management frame includes first-bit graph information related to the non-primary channel access (NPCA) mode performed by the first MLD for the plurality of links; and The first STA receives the second management frame from the second STA based on the first link. The second management frame includes second bitmap information related to the NPCA mode executed by the second MLD for the plurality of links.

2. The method according to claim 1, wherein, The first bitmap information is configured based on a first bitmap with a length of 16 bits. In this context, one bit of the first bitmap indicates whether the first MLD performs NPCA on a link corresponding to that bit.

3. The method according to claim 1, wherein, The first management frame also includes NPCA capability information related to whether the first STA has NPCA-related capabilities. The NPCA capability information has a length of 1 bit.

4. The method according to claim 1, wherein, The first management frame also includes first NPCA mode information related to the NPCA mode of the first STA. The first NPCA mode information is set to a first value based on the first STA having its NPCA mode enabled.

5. The method according to claim 1, wherein, The first management frame also includes enabling presence information. The enabled presence information has a length of 1 bit. The first bitmap information is the enabled bitmap. The enabled bitmap has a length of 16 bits. Wherein, one bit of the enable bitmap is set to a first value based on the mode of enabling NPCA on the link corresponding to the one bit. The value of the enable presence information is determined based on whether at least one bit included in the enable bitmap is set to the first value.

6. The method according to claim 5, wherein, The first management frame also includes disabling presence information. The disabled presence information has a length of 1 bit. The first management frame also includes a 16-bit disabled bitmap. Wherein, a bit of the disable bitmap is set to a first value based on a mode that disables NPCA on a link corresponding to the bit included in the disable bitmap. The value of the disable presence information is determined based on whether at least one bit included in the disable bitmap is set to the first value.

7. The method according to claim 1, wherein, The first management frame also includes first information relating to whether another STA attached to the first MLD has switched to the NPCA primary channel. The first information has a length of 1 bit.

8. The method according to claim 1, wherein, The first management frame also includes second information regarding whether another STA attached to the first MLD has switched from the NPCA primary channel to the primary channel. The second information has a length of 1 bit.

9. The method according to claim 1, wherein, The first MLD is the access point (AP) MLD, and the first STA is the first AP. Wherein, the second MLD is a non-AP STA MLD, and the second STA is the first non-AP STA.

10. The method according to claim 1, wherein, The first management frame is at least one of a beacon frame, an association response frame, and a probe response frame.

11. A first station STA, the first STA comprising: At least one processor; as well as At least one computer memory, operatively connectable to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations performed by the instructions in the at least one computer memory including: The first STA sends a first management frame to the second STA based on the first link. The first STA is attached to a first multi-link device (MLD) that performs multi-link operations related to multiple links, and the second STA is attached to a second MLD that performs multi-link operations related to the multiple links. The first management frame includes first-bit graph information related to the non-primary channel access (NPCA) mode performed by the first MLD for the plurality of links; and The first STA receives the second management frame from the second STA based on the first link. The second management frame includes second bitmap information related to the NPCA mode executed by the second MLD for the plurality of links.

12. The first STA according to claim 11, wherein, The instructions of the at least one computer memory perform operations relating to any one of claims 2 to 10.

13. A method performed in a wireless local area network (WLAN) system, the method comprising: The second STA receives the first management frame from the first STA via the first link. The first STA is attached to a first multi-link device (MLD) that performs multi-link operations related to multiple links, and the second STA is attached to a second MLD that performs multi-link operations related to the multiple links. The first management frame includes first-bit graph information related to the non-primary channel access (NPCA) mode performed by the first MLD for the plurality of links; and The second STA sends a second management frame to the first STA based on the first link. The second management frame includes second bitmap information related to the NPCA mode executed by the second MLD for the plurality of links.

14. The method according to claim 13, wherein, The second STA performs the operation relating to any one of claims 2 to 10.

15. A second station STA, the second STA comprising: At least one processor; as well as At least one computer memory, operatively connectable to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations performed by the instructions in the at least one computer memory including: The second STA receives the first management frame from the first STA based on the first link. The first STA is attached to a first multi-link device (MLD) that performs multi-link operations related to multiple links, and the second STA is attached to a second MLD that performs multi-link operations related to the multiple links. The first management frame includes first-bit graph information related to the non-primary channel access (NPCA) mode performed by the first MLD for the plurality of links; and The second STA sends a second management frame to the first STA based on the first link. The second management frame includes second bitmap information related to the NPCA mode executed by the second MLD for the plurality of links.

16. The second STA according to claim 15, wherein, The second STA performs the operation relating to any one of claims 2 to 10.

17. At least one computer-readable medium (CRM) in a wireless local area network (WLAN) system, said at least one CRM storing instructions, said instructions performing operations based on execution by at least one processor, said operations including: The first STA sends the first management frame to the second STA based on the first link. The first STA is attached to a first multi-link device (MLD) that performs multi-link operations related to multiple links, and the second STA is attached to a second MLD that performs multi-link operations related to the multiple links. The first management frame includes first-bit graph information related to the non-primary channel access (NPCA) mode performed by the first MLD for the plurality of links; and The first STA receives the second management frame from the second STA based on the first link. The second management frame includes second bitmap information related to the NPCA mode executed by the second MLD for the plurality of links.

Images