Channel switching techniques for accessing non-primary channels

Abstract

Technical features of the present disclosure can relate to devices or methods performed in a wireless local area network (WLAN) system. For example, the present specification proposes technical features to suggest optimal timing for performing non-primary channel access (NPCA) according to a PPDU format / type / version that an overlapping basic service set (OBSS) traffic has. For example, a station (STA) can receive an OBSS signal. For example, based on the OBSS signal, the STA can access a NPCA primary channel, attempt / perform a switch to the NPCA primary channel, or trigger or perform a NPCA operation. The NPCA primary channel can be accessed based on at least one of: a network allocation vector (NAV) set for the primary channel according to the OBSS signal; and a wait time associated with the OBSS signal. For example, the wait time associated with the OBSS signal can be set based on a NAVWaitTime.

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, the UHR system is considering various technologies to support high throughput, low latency, and extended range.

[0006] WLAN systems perform media access based on the primary channel. For example, information related to a primary channel with a bandwidth of 20MHz is sent 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 existing technology, since only the PCH is busy and even when other SCHs (or non-primary channels) are idle, the corresponding SCHs cannot be used, this can significantly reduce medium efficiency. However, various conditions must be considered to trigger operation on accessing the SCH (or non-primary channel).

[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, the technical features presented in this specification propose the optimal timing for performing NPCA (Non-Main Channel Access) based on the PPDU format / type / version of the OBSS service (e.g., OBSS PPDU).

[0012] For example, a STA (Station) can receive OBSS (Overlapping Basic Service Set) signals. Based on the OBSS signals, the STA can perform access to the NPCA (Non-Main Channel Access) primary channel, attempt / perform a handover to the NPCA primary channel, or trigger / perform NPCA operations. Access to the NPCA primary channel can be performed based on at least one of the basic NAV (Network Assignment Vector) set for the primary channel according to the OBSS signals and the waiting time associated with the OBSS signals. The waiting time associated with the OBSS signals can be set based on NAVWaitTime.

[0013] Beneficial effects

[0014] The technical features described in this specification can produce various beneficial effects. For example, the NPCA triggering conditions proposed in this specification can obtain the information required to execute NPCA at the earliest possible time point based on the PPDU format of the OBSS service. Furthermore, the technical features proposed in this specification enable the STA executing NPCA / SCA to switch to a non-primary channel at the earliest or optimized time point based on the information obtained by the STA, thereby executing NPCA for the longest possible duration. Attached Figure Description

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0033] Figure 19 This is an example of a network topology related to the examples in this specification.

[0034] Figure 20 An example related to case 2-1 is shown.

[0035] Figure 21 This is a flowchart of the process related to sending STA.

[0036] Figure 22 This is a flowchart of the process related to receiving the STA.

[0037] Figure 23 This is another process flowchart illustrating an example from this specification.

[0038] Figure 24 This is another process flowchart illustrating an example of this specification.

[0039] Figure 25 An example related to channelization is shown.

[0040] Figure 26 An example of SCA / NPCA execution at 320MHz is shown.

[0041] Figure 27 An example of SCA / NPCA execution at 320MHz is shown. Detailed Implementation

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

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

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

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

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

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

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

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

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

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

[0052] Figure 1 Examples can perform the following technical features. Figure 1This 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.

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

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

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

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

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

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

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

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

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

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

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

[0064] 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 1 STA (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 1The 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.

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

[0066] 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 1 The 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.

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

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

[0069] Reference Figure 1 Subgraph (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0083] Figure 3As 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0165] 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 NAV (e.g., reset it to 0). 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.

[0166] Although for convenience, Figure 15 The diagram illustrates setting or updating the NAV via RTS or CTS frames, but NAV setting / resetting / updating can also be performed based on a duration field included in a PPDU (e.g., the duration field in the MAC header of a MAC frame), or on various other frames (e.g., non-HT PPDU, HT PPDU, VHT PPDU, HE PPDU, EHT PPDU, and / or UHR PPDU). 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.

[0167] 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 and AP2 as described below.

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

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

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

[0171] During the backoff interval, when the P20 channel is determined to be idle and the backoff count for the P20 channel 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).

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

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

[0174] According to existing technology, 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; and 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 for the primary 20MHz channel (or P20 channel) and the secondary 20MHz channel (or S20 channel).

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

[0176] 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 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, there may be technical features that reduce efficiency in terms of media usage.

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

[0178] P20: Main 20MHz channel

[0179] S20: Secondary 20MHz channel

[0180] S40: Secondary 40MHz channel

[0181] S80: Secondary 80MHz channel

[0182] S160: Secondary 160MHz channel

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

[0184] 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 the P20 channel and the S20 channel through the channel extension / binding described above.

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

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

[0187] 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 CCA sensing (and / or decrementing of the backoff counter) can be performed on the switched secondary channel.

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

[0189] 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., by the AP / non-AP STA) in the previously described secondary 20MHz channel, it may also be referred to as the NPCA primary channel (or NPCH).

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

[0191] 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 operation) of Wi-Fi frames performed on the primary 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 primary channel or NPCH). With such capabilities for SCA / NPCA, additional NAVs (e.g., at least one Intra-BSS NAV and / or a basic NAV) can be set on the SCH (or NPCA primary channel or NPCH).

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

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

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

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

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

[0197] For example, the aforementioned capabilities may be included in UHR capabilities such as IE, and 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 may be included in various management frames generated / transmitted by non-AP STAs, such as probe request frames and (re)association request frames.

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

[0199] For example, if a STA (e.g., a non-AP STA or an AP) sets an in-BSS NAV for the PCH, the STA may not perform SCA (or NPCA). For instance, when an AP performs frame exchange with any STA (e.g., a non-AP STA) within a TXOP obtained / acquired by the AP, another STA can thereby set an in-BSS NAV based on the primary channel. In this case, the STA that has set the in-BSS NAV can send a frame to the AP after accessing the SCH, 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 signal. Therefore, it is preferable that the STA only starts / triggers SCA when a basic NAV is set on the PCH.

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

[0201] 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 or NPCH) at the 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, a handover delay may occur 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 do not perform backoff and are idle, they may transmit frames simultaneously, and in this case, collisions may occur, wasting the channel.

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

[0203] First, an example of transmitting frames on a secondary channel (e.g., at least one channel including the NPA main channel (or NPAH)) is described.

[0204] Normally, preamble puncturing can only be performed based on the idle / busy determination 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 where the P20 channel is busy is considered, the rules used here can be modified as follows: For example, if the P20 channel is determined to be busy, the corresponding P20 channel can be punctured, and other busy SCHs based on the S20 channel can also be punctured, and as a result, frames can be transmitted through idle SCHs. For example, in Figure 18 In the example, all three 20MHz channels, including the S20 and S40 channels, are determined to be idle. Therefore, STA1 can perform preamble puncturing on the P20 channel of the 80MHz PPDU while transmitting the 80MHz PPDU (including the MAC frame). 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.

[0205] Secondly, the following is an example of setting TXOP on the secondary channel (or NPCA main channel or NPCH).

[0206] For example, when the basic NAV on the P20 channel expires, it may be necessary to perform CCA on the P20 channel. Therefore, it is preferable that the end time of TXOP for the secondary channel (e.g., the S20 channel, the NPCA main channel, or the NPCH) is set to end before the time when the basic NAV on the main channel (e.g., the P20 channel) expires.

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

[0208] For example, if the TXOP end time of the secondary channel is set to end after the basic NAV (of the primary channel) expires, then since conventional STAs can transmit frames through the P20 channel, this 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.

[0209] To efficiently execute SCA / NPCA, the aforementioned technical features must be further improved. For example, it is preferable to optimize the timing of SCA / NPCA execution, or to switch to SCH (or NPCA main channel or NPH) to enable SCA / NPCA execution.

[0210] For example, initiating a switch to SCH (or NPCA main channel or NPH) to perform SCA / NPCA may involve triggering SCA / NPCA (operation). For example, triggering SCA / NPCA (operation) may mean switching to SCH (or NPCA main channel) or accessing the appropriate channel. Alternatively or alternatively, triggering SCA / NPCA (operation) may mean determining whether to switch to SCH (or NPCA main channel) (or whether to access the appropriate channel). Alternatively or alternatively, triggering SCA / NPCA (operation) may mean switching to SCH (or NPCA main channel) after acquiring / obtaining control information for switching to SCH (or NPCA main channel) (e.g., acquiring / obtaining information related to the OBSS PPDU). For example, switching to SCH (or NPCA main channel) may mean performing a process after completing operations on PCH and before receiving signals (e.g., CCA / ED / PD) on SCH (or NPCA main channel).

[0211] This specification describes various triggering conditions for SCA / NPCA (operation). When the various triggering conditions set forth in this specification are met, the corresponding STA (e.g., AP or non-AP STA) may initiate / attempt a switch to the aforementioned SCH (or NPCA main channel or NPCH). When the various triggering conditions set forth in this specification are not met, the corresponding STA (e.g., AP or non-AP STA) may not initiate / attempt a switch to the aforementioned SCH (or NPCA main channel).

[0212] The NPCA triggering conditions described in this specification can be determined based on 1) the version (or type) of the OBSS PPDU (or received service) received by the STA and / or 2) predetermined or negotiated rules. For example, the NPCA triggering conditions may vary depending on which version (or type) of the OBSS PPDU received by the STA. Alternatively or additionally, the NPCA triggering conditions may vary according to predetermined or negotiated rules.

[0213] Preferably, the above-mentioned NPCA triggering conditions are optimized taking into account various situations (e.g., conditions / timing for switching to an NPCA-related channel, conditions / timing for accessing the corresponding channel). As described below, improving the NPCA triggering conditions may be related to the execution of NPCA / SCA.

[0214] For example, for higher performance NPCA / SCA, it is preferable that the STA performing NPCA / SCA switches to the NPCA main channel (e.g., S20 channel or NPCH) at the earliest possible time after acquiring the information necessary to perform NPCA / SCA. Alternatively, it is preferable that multiple SCAs switch to the NPCA main channel (e.g., S20 channel) as simultaneously as possible. For example, when performing / initiating a handover quickly, the STA performing NPCA / SCA can acquire / set a longer TXOP on the NPCA main channel (e.g., S20 channel). Furthermore, for example, performing / initiating a handover at the closest or most similar time possible can prevent unnecessary FE (frame switching) from being initiated on the NPCA main channel (e.g., S20 channel).

[0215] In other words, various technical effects may occur when the NPCA triggering conditions are improved (e.g., the timing / operation of switching to the NPCA main channel (e.g., S20 channel or NPCH), or the start / operation of accessing the corresponding channel).

[0216] For example, the timing of switching to the NPCA main channel (e.g., S20 channel or NPCH) or triggering the NPCA can be defined differently based on the version / type of the PPDU (e.g., OBSS PPDU). For instance, to perform NPCA / SCA, at least one STA (e.g., AP or non-AP STA) can 1) determine whether the received service is an OBSS PPDU or an in-BSS PPDU and 2) obtain information about the duration of the NPCA / SCA (e.g., TXOP information or PPDU length information). Alternatively, the corresponding STA can 3) determine whether a backoffed SCH (e.g., NPCA main channel, NPCH, or S20 channel) overlaps with an OBSS service (e.g., an OBSS PPDU received on the PCH). This is because, for example, when the channel / subchannel / frequency resource receiving the OBSS service overlaps with the SCH (or NPCH, S20 channel, etc.), it may be meaningless for the STA to switch to the corresponding SCH and perform SCA (or NPCA). For example, the timing at which the above information can be obtained may vary depending on the PPDU version / type (non-HT, HT, VHT, HE, EHT, or UHR PPDU). Furthermore, for example, executing / starting a switch (or triggering NPCA) at the earliest possible time after obtaining the above information (and at the closest or most similar time) may affect the execution of NPCA / SCA.

[0217] For example, an STA (e.g., an AP) may advertise information about: a) whether the necessary information for NPCA / SCA is provided based on the PHY header (e.g., the PHY preamble included in the OBSS PPDU), and b) whether the information for NPCA / SCA is provided based on the MAC header (e.g., the MAC header included in the OBSS PPDU). Alternatively, the STA may advertise c) information about setting the duration for which NPCA / SCA can be performed based on the TXOP or PPDU length. Alternatively, since the STA cannot perform sufficient FE (frame exchange) even if NPCA / SCA is performed when the TXOP or PPDU length is too short, the STA may advertise information related to a threshold (e.g., a TXOP duration threshold or a PPDU length threshold) by which the TXOP can be obtained by performing NPCA / SCA. For example, an STA (e.g., an AP) may include at least one of the information elements (IEs) for NPCA / SCA operation described below. The corresponding Information Element (IE) can be included within the UHR operation IE or as a new IE in the management frame that includes the STA's beacon and probe responses.

[0218] Examples of various information elements are described below.

[0219] First Information Element (IE): PHY / MAC-based NPCA

[0220] The first information element (IE) may be an indication of whether the necessary information for obtaining NPCA / SCA is based on the PHY header (e.g., the PHY preamble of the PPDU received on the PCH) and the switch to the SCH channel is based on the obtained information, or whether the necessary information for obtaining NPCA / SCA is based on the MAC header (e.g., the MAC header of the MAC frame included in the data field of the PPDU received on the PCH) and the switch to the SCH channel is based on the obtained information.

[0221] For example, when the first information element (IE) has a length of 1 bit, if it is set to a first value (or a value of 0), the information necessary for NPCA / SCA can be obtained based on the PHY header, while if it is set to a second value (or a value of 1), the information necessary for NPCA / SCA can be obtained based on the MAC header. For example, the first information element (IE) can have various bit lengths. For example, if the first information element (IE) has a third value (or a value of 2), the information necessary for NPCA / SCA can be obtained based on both the PHY and MAC headers.

[0222] For example, when obtaining the necessary information for NPCA / SCA based on the PHY header, there is an advantage that NPCA / SCA can be executed at an earlier point in time, thus ensuring a longer TXOP on the SCH. On the other hand, considering that the necessary information for executing NPCA / SCA based on the PPDU type in the PHY header may be insufficient, obtaining the necessary information for NPCA / SCA based on the MAC header has the advantage of being able to execute NPCA / SCA for more OBSS PPDU types.

[0223] For example, when the first information element (IE) is set to a third value (e.g., when the PHY / MAC-based NPCA is set to 2), the time point at which the information necessary to obtain the NPCA / SCA can be obtained can vary depending on the PPDU format of the OBSS service. Specifically, the time point at which the information necessary to obtain the NPCA / SCA can be determined together with the second information element described below (e.g., the NPCA field based on the TXOP / PPDU). For example, when the second information element (e.g., the NPCA field based on the TXOP / PPDU) is a first value (e.g., 0) (e.g., in the case of TXOP-based OBSS PPDU), for non-HT / HT / VHT OBSS PPDUs, the NPCA / SCA can be performed after obtaining the TXOP information from the MAC header, and for HE / EHT / UHR OBSS PPDUs, the NPCA / SCA can be performed after obtaining the TXOP information from the PHY header. For example, when the second information element (e.g., the NPCA field based on TXOP) is the second value (e.g., 1) (e.g., in the case of PPDU length), for non-HT / HT OBSSPPDUs, NPCA / SCA is performed after confirming the RA / TA address, which allows us to determine from the MAC header whether it is an OBSS PPDU. In this case, for VHT / HE / EHT / UHR OBSS PPDUs, we can determine whether it is an OBSS PPDU based on the BSS color of the PHY header, and NPCA / SCA can be performed.

[0224] Second Information Element (IE): NPCA based on TXOP PPDU

[0225] For example, the second information element (IE) can indicate whether the duration for which NPCA / SCA can be performed is set based on the TXOP value or the PPDU length value.

[0226] For example, when the second information element (IE) has a length of 1 bit, the NPCA / SCA duration is set based on the TXOP value if the corresponding information element is set to the first value (e.g., 0), and the NPCA / SCA duration can be set based on the PPDU length value if it is set to the second value (e.g., 1).

[0227] For example, when setting up an NPCA based on TXOP, there is an advantage that the duration of the NPCA / SCA can be longer when executing the NPCA / SCA because the TXOP value usually has a longer value than the PPDU length.

[0228] For example, when setting the PPDU length NPCA, there is an advantage that after performing NPCA / SCA, when returning from SCH (e.g., S20 channel) to PCH (e.g., P20 channel), the problem of losing media synchronization on PCH does not occur.

[0229] Third Information Element (IE): TXOP Duration Threshold

[0230] For example, the third information element (IE) may include information about the duration of the TXOP, which must be guaranteed to be minimum when the value of the second information element (e.g., NPCA based on the TXOP / PPDU) is a first value (e.g., 0) (e.g., when NPCA / SCA is performed based on the TXOP value). That is, when the TXOP value of the OBSS PPDU (e.g., the basic NAV value) is less than the value set by the third information element, NPCA / SCA may not be performed even if the PCH (e.g., the P20 channel) is busy.

[0231] For example, the unit of the third information element can be represented in milliseconds (ms). Alternatively, when the third information element has a length of 8 bits, for example, the value 00000011 can indicate that the TXOP duration threshold is set to 3 ms. In this case, based on the third information element, the STA can perform NPCA / SCA only when the basic NAV (value) is longer than 3 ms. Alternatively, the unit of the corresponding field can be microseconds (µs), and the bit length can also be varied.

[0232] Fourth Information Element (IE): PPDU Length Threshold: For example, the fourth information element (IE) may include information about the TXOP duration, which must be guaranteed to be minimum when the aforementioned second information element (e.g., NPCA based on TXOP / PPDU) is related to the PPDU length value. For example, if the OBSS PPDU length value is less than the value of the fourth information element, the STA may not perform NPCA / SCA even if the PCH (e.g., P20 channel) is determined to be busy. For example, the PPDU length value can be identified / obtained through the LENGTH field of the PPDU's L-SIG field.

[0233] For example, the unit of the fourth information element can be represented in milliseconds (ms). Alternatively, when the fourth information element has a length of 8 bits, for example, the value 00000011 can indicate that the PPDU length threshold is set to 3 ms. In this case, based on the fourth information element, the STA can perform NPCA / SCA only when the length of the OBSS PPDU is longer than 3 ms. Alternatively, the unit of the corresponding field can be microseconds (µs), and the bit length can also be varied.

[0234] At least one of the first to fourth information elements is related to a condition for triggering NPCA (or a condition for handover / access to the NPCA main channel (or NPCH)). In other words, in order to trigger NPCA (or to perform handover / access to the NPCA main channel), a condition related to at least one of the first to fourth information elements must be met (e.g., the condition that the OBSS PPDU length is greater than the fourth information element, or the condition that the TXOP value of the OBSS PPDU is greater than the third information element).

[0235] The conditions used to trigger an NPA (or for switching / accessing the NPA primary channel (or NPAH)) can be based on the PPDU version / type as described above. For example, the PPDU version / type can be one of a non-HT (non-high throughput) PPDU (Physical Protocol Data Unit), HT (high throughput) PPDU, VHT (very high throughput) PPDU, HE (high efficiency) PPDU, EHT (extremely high throughput) PPDU, and UHR (ultra-high reliability) PPDU. Alternatively, the PPDU version / type can be related to whether the corresponding PPDU includes an RTS or MU-RTS. Alternatively, the PPDU version / type can be related to whether the corresponding PPDU is a non-HT PPDU including an RTS or MU-RTS.

[0236] The specific technical features related to the version / type of PPDU are as follows.

[0237] First version / type PPDU (e.g., RTS in a non-HT PPDU)

[0238] For example, when a PPDU (e.g., an OBSSPPDU received on a PCH) received by a STA (e.g., an AP or a non-AP STA) is a non-HT PPDU that includes an RTS or MU-RTS, the following can be considered.

[0239] In other words, the first version / type PPDU can be a PPDU that includes RTS or MU-RTS (e.g., a non-HT PPDU or a non-HT repeated PPDU). When the first version / type PPDU is received on the PCH, the following factors are considered to determine the conditions for triggering the NPA (or the conditions for switching / accessing the NPA main channel (or NPCH)).

[0240] The information necessary to execute an NPCA / SCA may be insufficient in the PHY header of a non-HT PPDU. Therefore, the duration information for executing an NPCA / SCA and information about whether it is an OBSS service can be obtained through the MAC header of the corresponding non-HT PPDU.

[0241] In traditional wireless LAN systems, when a NAV is set due to an RTS or MU-RTS, if no PPDU detection (e.g., detection of the PHY-RXEARLYSIG.indication or PHY-RXSTART.indication primitive) is received during a specific time period (hereinafter referred to as NAVWaitTime or "NAV Wait Time"), the NAV set due to the corresponding RTS or MU-RTS can be reset (e.g., set to 0). The NAVWaitTime can be calculated as (2 × aSIFSTime) + (CTS_Time) + aRxPHYStartDelay + (2 × aSlotTime), and CTS_Time can be calculated based on the length of the CTS frame and the PHY data rate. aSIFSTime, CTS_Time, aRxPHYStartDelay, and aSlotTime are widely known parameter values ​​in wireless LAN technology, where aSIFSTime can have a value corresponding to the length of the SIFS (Short IFS), and CTS_Time can have a value corresponding to the length of the CTS frame corresponding to the RTS / MU-RTS. Furthermore, for example, aRxPHYStartDelay is an integer delay value determined based on the relevant PPDU version, where each delay, in microseconds, is the earlier of the start of the PPDU at the receiver's antenna and the transmission of the primitive PHYRXEARLYSIG.indication (if transmitted) or PHYRXSTART.indication. Additionally, for example, aSlotTime can be a slot time in microseconds used by the MAC layer of the wireless LAN device to define the IFS.

[0242] For example, for a STA (e.g., non-AP / AP) that switches to SCH (e.g., S20 channel, NPCA main channel, or NPCH) and performs NPCA / SCA due to an RTS (or MU-RTS) received from OBSS (e.g., OBSS PPDU on PCH), the following problem may occur when the NAV set by the corresponding RTS (or MU-RTS) is reset. For example, the NAV must be reset in the following situations: For example, when a) the associated CTS is not received due to a failure of the RTS transmission (or MU-RTS transmission), or b) the RTS transmission (or MU-RTS transmission) is successful, but a failure occurs in the transmission / reception of the CTS corresponding to the RTS, the corresponding NAV must be reset.

[0243] Under the above circumstances, the following problems may occur.

[0244] When the basic NAV is set due to an RTS or MU-RTS on the OBSS (e.g., an OBSS PPDU on the PCH), but the PPDU detection (e.g., detection of the PHY-RXEARLYSIG.indication or PHY-RXSTART.indication primitive) cannot be performed during a specific time (e.g., the NAVWaitTime mentioned above), the basic NAV must be reset (e.g., set to 0). However, since the STA that set the basic NAV (e.g., AP / non-AP) has switched to the SCH, it may not be aware of the basic NAV reset. As a result, when the STA that performed NPCA / SCA (e.g., AP and non-AP) returns to the PCH, there may be a problem of lost media synchronization. Furthermore, for example, since legacy STAs that reset the basic NAV (e.g., existing STAs before 11bn or existing STAs before UHR) can send frames based on the PCH, there may be a problem of frame collisions.

[0245] To address the aforementioned issues, the STA described in this specification may perform the following actions. For example, when a basic NAV is set due to an RTS (or MU-RTS) received on the PCH, it is preferable that the STA (e.g., AP / non-AP) does not immediately switch to the SCH and execute NPCA / SCA after the basic NAV is set. In other words, the NPCA may not be triggered immediately after the basic NAV is set. Instead, the STA described in this specification may wait for a maximum of NAVWaitTime (e.g., wait for a maximum of NAVWaitTime from the time the basic NAV was set). When a PPDU detection occurs during NAVWaitTime (e.g., when a data frame is detected on the PCH, or when a CTS frame is detected on the PCH), it can be determined that the basic NAV, which has not been reset, has been set, and the STA may switch to the SCH (or access the SCH or trigger NPCA).

[0246] Alternatively, when the STA does not detect any PPDU while waiting for a maximum of NAVWaitTime (on the PCH), the STA may also not switch to the SCH, reset the basic NAV on the PCH (e.g., set it to 0), and continue the backoff process on the PCH.

[0247] Figure 19 This is an example of a network topology related to the examples in this specification.

[0248] like Figure 19As shown, when a non-AP STA1-1 sends an RTS to AP1, non-AP STA 2-1, non-AP STA 2-2, and AP2, which can listen to frames from non-AP STA1-1, can set the basic NAV due to the RTS. In this case, the STAs that set the basic NAV can wait during the NAVWaitTime period without immediately switching to the SCH. For example, if a PPDU detection is acknowledged during the NAVWaitTime period, the basic NAV will not be reset, and the corresponding STA can switch to the SCH.

[0249] Reference Figure 19 The technical features applicable to each STA are described by dividing them into Case 1 and Case 2.

[0250] Scenario 1: The operation of a STA (e.g., AP / non-AP) based on Case 1 can be as follows.

[0251] For example, the following scenario allows for the receipt of an OBSS PPDU and immediate switching to the SCH. For instance, non-AP STA 2-1, non-AP STA 2-2, and AP2 can receive an RTS sent by non-AP STA 1-1 and immediately switch to the SCH to perform NPCA / SCA. This has the advantage that the STA performing NPCA / SCA can occupy the TXOP on the SCH for a longer period. Alternatively, the OBSS PPDU can be an RTS or a MU-RTS.

[0252] In other words, a STA operating under Case 1 can receive OBSS PPDU received on the PCH, and when the corresponding OBSS PPDU includes RTS (or MU-RTS), sets a basic NAV for the PCH, and immediately performs a handover to the NPCA main channel (or NPCH) at the start time of the basic NAV (or immediately performs NPCA triggering).

[0253] Scenario 2: The following describes Case 2. The technical features of Case 2 are described based on Case 2-1 and Case 2. A STA operating under Case 2 can detect PPDUs on the PCH while waiting for a specific period, without immediately switching to the SCH after setting the basic NAV. If the PPDU detection is confirmed on the PCH during the waiting period, the corresponding STA can switch to the SCH to perform NPCA / SCA based on the confirmation of the PPDU detection.

[0254] Case 2-1: Figure 20An example related to case 2-1 is shown. For example, STA (e.g., Figure 20 The non-AP STA 2-1 can receive response frames for OBSS PPDU (e.g., Figure 20 (CTS from AP1 to non-AP STA 1-1). STA can perform a handover to SCH based on the corresponding response received on PCH. For example, due to... Figure 20 Non-AP STA 2-1 is included in the listening range of PPDUs sent by AP1. If AP1 sends a response to an OBSS PPDU within NAVWaitTime, non-AP STA 2-1 can detect it. For example, when a PPDU detection is determined, non-AP STA 2-1 can switch to SCH. Alternatively, the response frame to an OBSS PPDU may be a CTS.

[0255] Figure 20 Examples can be represented differently as follows. A STA (e.g., non-AP STA 2-1) can receive OBSS PPDUs via a primary channel (e.g., P20 channel). For example, the OBSS PPDU may include an RTS (or MU-RTS). When the received OBSS PPDU includes an RTS (or MU-RTS), a) the corresponding STA sets a basic NAV for the primary channel, b) at the start time of the basic NAV, the handover to the NPCA primary channel (or NPCH) may not be performed immediately (or the NPCA trigger may not be performed immediately), and c) the handover to the SCH (or the NPCA trigger) may be postponed to the aforementioned NAVWaitTime. For example, if the PPDU detection is acknowledged during NAVWaitTime (e.g., CTS), then even during NAVWaitTime, the STA can immediately perform the handover to the NPCA primary channel (or immediately perform the NPCA trigger) at the time of PPDU detection acknowledgment.

[0256] Situation 2-2: Case 2-1 above is an example of performing a switch to the NPCA main channel (or NPCH) (or immediately triggering an NPCA) when a response frame (e.g., CTS) for an OBSS PPDU is acknowledged, while case 2-2 involves an example of performing a switch to the NPCA main channel (or immediately triggering an NPCA) when a frame (e.g., a data frame) received after the response frame is acknowledged.

[0257] For example, Figure 19AP2 and non-AP STA 2-2 may not receive the response to the OBSS PPDU sent by AP1. In this case, when non-AP STA 1-1 sends a frame following the response frame to the OBSS PPDU, AP2 and non-APSTA 2-2 can detect the frame within NAVWaitTime and switch to SCH. Alternatively, the frame following the response frame to the OBSS PPDU may be a data frame.

[0258] The above situation 2-2 can be expressed in different ways as follows.

[0259] STAs (e.g., AP2 or non-AP STA 2-2) can receive OBSSPPDUs via a primary channel (e.g., P20 channel). For example, an OBSS PPDU may include an RTS (or MU-RTS). When the received OBSS PPDU includes an RTS (or MU-RTS), a) the corresponding STA sets a basic NAV for the primary channel, b) at the start time of the basic NAV, a handover to the NPCA primary channel (or NPCH) may not be performed immediately (or an NPCA trigger may not be performed immediately), and c) the handover to the SCH (or NPCA trigger) may be postponed to the aforementioned NAVWaitTime. For example, even if no OBSS response frame (e.g., CTS) is received during the NAVWaitTime, if a frame following the corresponding OBSS response frame (e.g., a data frame associated with the RTS) is acknowledged, the STA may immediately perform a handover to the NPCA primary channel (or immediately perform an NPCA trigger) at the time the corresponding frame (e.g., a data frame associated with the RTS) is acknowledged, even during the NAVWaitTime.

[0260] Case 2, including cases 2-1 and 2-2 above, can proceed to SCH (e.g., after confirming that the basic NAV set on PCH has not been reset) after verification. Figure 20 The switching of the S20 channel (or NPCA main channel or NPCH) is shown. As a result, when returning to the PCH after performing NPCA / SCA, the corresponding STA may not lose media synchronization on the PCH, which is advantageous.

[0261] In scenario 2 above, there are additional issues that must be considered. For example, depending on the network topology, the timing of the handover between non-AP STAs and APs to the SCH can change, as in scenarios 2-1) and 2-2). In this case, the non-AP STA that switches to the SCH first may attempt meaningless frame switching with non-AP STAs that have not yet switched, potentially wasting resources. Therefore, a method can be proposed in which STAs (e.g., non-APs and APs) can switch at the same time (or, even if one switches first, frame switching can begin when it can be guaranteed that the receiving STA has already switched to the SCH). Such a method can be implemented using methods-1,-2, and-3 below.

[0262] Method-1)

[0263] According to Method 1, even after all STAs have received the RTS (or MU-RTS) and then received a response frame (e.g., CTS) for the RTS (or MU-RTS), they may not immediately switch to the SCH. In this case, the STAs can wait until they receive a frame (e.g., a data frame associated with the RTS) after the corresponding response frame, and switch to the SCH when the corresponding frame (e.g., a data frame) is received. In this case, the transmitting STA can transmit the frame only considering the channel handover delay that occurs when the receiving STA switches to the SCH. Such Method 1) guarantees that the receiving STA has completed the handover to the SCH.

[0264] Method 2)

[0265] For an STA that receives a frame following a response frame (e.g., a data frame related to RTS) and performs a handover, an STA that receives a response frame for RTS (or MU-RTS) (e.g., CTS) and performs a handover can back off considering a preset time (T). In this case, when the value of T is greater than the backoff counter value, the corresponding STA can wait for T - the backoff counter value before starting frame switching. Alternatively, T can be set to the value of CTS_TIME + aSIFSTime + aRxPHYStartDelay + Diff (channel handover delay). For example, when the channel handover delay of the transmitting STA is large, Diff (channel handover delay) can have a value of 0. Furthermore, for example, when the channel handover delay of the receiving STA is large, Diff can have a value obtained by subtracting the value of the transmitting side's channel handover delay from the value of the receiving STA's channel handover delay.

[0266] Method 3)

[0267] STAs whose basic NAV set due to RTS (or MU RTS) is not reset during NAVTimeout (i.e., NAVWaitTime mentioned above) can begin switching to SCH after NAVTimeout.

[0268] Second version / type PPDU (non-HT PPDU without RTS)

[0269] The aforementioned second version / type PPDU can be a non-HT (or non-HT replicated PPDU) excluding RTS (or MU-RTS). When a second version / type PPDU is received on the PCH, the following factors are considered to determine the conditions for triggering an NPA (or for switching / accessing the NPA main channel (or NPCH)).

[0270] When the received PPDU is a non-HT PPDU (or a non-HT repeated PPDU) that does not include an RTS (or MU-RTS), the following must be considered. In other words, when the received PPDU is a second version / type PPDU, the following must be considered. First, OBSS PPDU identification must be performed based on the RA / TA address of the MAC header of the received PPDU. For example, when the NPCA based on the PHY / MAC is a first value (e.g., 0) (e.g., in the case based on the PHY header), for non-HT PPDUs that do not include an RTS (or MU-RTS), NPCA / SCA based on the duration of the TXOP may not be performed. For example, when the NPCA based on the PHY / MAC is a second value (e.g., 1) or a third value (e.g., 2), OBSS PPDU identification can be performed based on the RA / TA address of the MAC header of the received PPDU. For example, when the NPCA field value based on the TXOP / PPDU is the first value (e.g., 0), the STA can identify the duration field value of the MAC header of the received PPDU and switch to SCH after decoding the RA / TA of the corresponding MAC header.

[0271] Alternatively, the STA can identify the duration field value of the MAC header of the received PPDU, decode up to the RA / TA of the MAC header, perform FCS check to confirm validity, and then switch to SCH.

[0272] Alternatively, when the PHY / MAC-based NPCA is 1 or 2 and the TXOP / PPDU-based NPCA field value is 1, NPCA / SCA can be performed based on the length field value of the L-SIG field of the received PPDU. In this case, the STA can decode from the MAC header of the received PPDU up to RA / TA, and then switch to SCH.

[0273] Alternatively, the STA can decode the MAC header of the received PPDU up to the RA / TA, perform FCS verification, and switch to SCH at the point when the validity verification is completed.

[0274] Third version / type PPDU (HT PPDU)

[0275] The aforementioned third version / type PPDU can be an HT PPDU. When a third version / type PPDU is received on the PCH, the following considerations should be taken into account to determine the conditions for triggering the NPA (or the conditions for switching / accessing the NPA main channel (or NPCH)).

[0276] When the received PPDU is an HT PPDU, OBSS PPDU identification can be performed based on the RA / TA address of the MAC header of the received PPDU. For example, when the NPCA based on PHY / MAC is a first value (e.g., 0) (e.g., in the case of PHY header), NPCA / SCA may not be performed for HT PPDUs. Therefore, when the NPCA based on PHY / MAC is a second value (e.g., 1) or a third value (e.g., 2), OBSS PPDU identification can be performed based on the RA / TA address of the MAC header of the received PPDU. Additionally, when the NPCA field value based on TXOP / PPDU is 0, the STA can identify the duration field value of the MAC header of the received PPDU, confirm the validity until the corresponding MAC header RA / TA, complete the validity check through FCS check, and then switch to SCH.

[0277] Alternatively, the STA can verify the duration, RA, and TA fields in the MAC header of the received PPDU, omit the validity check via FCS, and immediately switch to SCH.

[0278] Alternatively, when an A-MPDU included in the HT PPDU is received, the STA can verify the duration, RA, and TA information up to the MAC header of the first MPDU, complete the FCS check of the first MPDU, and then switch to the SCH.

[0279] Furthermore, for example, when the NPCA field value based on the TXOP / PPDU is 1, the STA can perform NPCA / SCA based on the length field value of the L-SIG field of the received PPDU. In this case, the STA can decode from the MAC header of the received PPDU up to RA / TA, and then switch to SCH.

[0280] Alternatively, the STA can decode the MAC header of the received PPDU up to the RA / TA, and then switch to the SCH after the validity check is completed via FCS check.

[0281] Alternatively, when receiving an A-MPDU included in the HT PPDU, the STA can confirm the RA and TA information through the MAC header of the first MPDU, complete the FCS verification of the first MPDU, and then switch to SCH.

[0282] Version 4 / Type PPDU (in the case of VHT PPDU)

[0283] The aforementioned fourth version / type PPDU can be a VHT PPDU. When a fourth version / type PPDU is received on the PCH, consider the following to determine the conditions for triggering the NPA (or the conditions for switching / accessing the NPA main channel (or NPCH)).

[0284] When the received PPDU is a VHT PPDU, OBSS PPDU identification can be performed based on the partial AID and Group ID field values ​​of the VHT-SIG-A field in the PHY header of the received PPDU. When the NPCA based on the PHY / MAC is a first value (e.g., 0) (e.g., in the case of a PHY header) and the NPCA field value based on the TXOP / PPDU is a second value (e.g., 1), OBSS PPDU identification can be performed using the Group ID and partial AID fields of the VHT-SIG-A field. In this case, after performing OBSS PPDU identification, the STA immediately switches to the SCH and can perform NPCA / SCA based on the LENGTH field of the L-SIG field of the VHT PPDU for the PPDU length.

[0285] Alternatively, when the OBSS PPDU received by the STA via the PCH corresponds to a VHT PPDU, the STA may switch to the SCH after completing the validity check through the CRC check of the VHT-SIG-A field of the corresponding VHT PPDU.

[0286] Additionally, when the NPCA field based on the TXOP / PPDU is the first value (e.g., 0), OBSS PPDU identification can be performed using the group ID and part of the AID field in the VHT-SIG-A field. After performing OBSS PPDU identification, the STA can decode only the duration field of the MAC header up to the VHT PPDU and then immediately switch to SCH to perform NPCA / SCA.

[0287] Alternatively, when the OBSS PPDU received by the STA via the PCH corresponds to a VHT PPDU, the STA can perform NPCA / SCA based on the PPDU length of the corresponding VHT PPDU after completing the validity verification through the FCS check of the MAC header of the corresponding VHT PPDU.

[0288] Alternatively, upon receiving a second version / type PPDU (e.g., non-HT without RTS), a third version / type PPDU (e.g., HT PPDU), and / or a fourth version / type PPDU (e.g., VHT PPDU), the STA can decode the information from the MAC header of the first MPDU included in the corresponding PPDU when obtaining information from the MAC header of the received PPDU, and switch to SCH after FCS verification is complete. Thus, the STA begins switching to SCH at an earlier point in time and can therefore acquire a longer TXOP on SCH.

[0289] Alternatively or additionally, the processing delay that occurs when decoding the MAC header of the received PPDU (or a delay such as that occurring when performing FCS verification) can vary depending on the capabilities of the STA. That is, the start time of handover can be varied for each STA. With this in mind, STAs (e.g., AP and non-AP STAs) can be ensured to start handover simultaneously by allowing handover to occur after a specific time following the received OBSS PPDU (e.g., which may be referred to below as the start handover alignment time, and the corresponding terminology may be changed). Alternatively or additionally, the start handover alignment time can begin after the MAC receives PHYRXEND.indication from the PHY. For example, the corresponding value can be defined as SIFS, and can be defined as SIFS + alpha (α). For example, the AP may include start handover alignment time information for secondary channel access operations. This information may be included in the management frame that includes the AP's beacon and probe responses, either within the UHR operation IE or in the form of a new IE. Alternatively or alternatively, similar to procedures such as NAVTimeout, the STA can switch after the start of the switch alignment time following the PHYRXEND.indication received by the MAC from the PHY, without notification from the AP.

[0290] Version 5 / Type PPDU

[0291] For example, the aforementioned version 5 / type PPDU can represent a PPDU with a PHY version starting with HE and EHT. For example, a PPDU with a PHY version starting with EHT can include an EHT PPDU and a UHR PPDU. For example, a UHR PPDU can refer to a PPDU defined by 802.11bn, and the specific name can be changed. When a version 5 / type PPDU is received on the PCH, the following considerations are taken into account to determine the conditions for triggering an NPA (or for handover / access to the NPA primary channel (or NPAH)).

[0292] In PPDUs from 11ax forward, the TXOP field is present in the PHY header. Additionally, since the BSS color field is added to the PHY header, identification of whether a PPDU was received from the OBSS can be performed based on the BSS color field. Therefore, for PPDU formats including HE PPDUs and subsequent PPDUs, the STA can switch based on either the PHY header or the MAC header of the received PPDU (based on the values ​​set in the PHY / MAC-based NPCA). For example, when the OBSS PPDU received on the PCH is an HE PPDU, the corresponding TXOP and BSS color fields are included in the HE-SIG-A field. For example, when the OBSS PPDU received on the PCH is an EHT PPDU, the TXOP and BSS color fields are included in the U-SIG field. For example, when the OBSS PPDU received on the PCH is a UHR PPDU (although the PPDU structure is still under discussion), part / all of the U-SIG field of the EHT standard will be retained. Assuming this, like a traditional EHT PPDU, a UHR PPDU will include the TXOP and BSS color fields in the U-SIG field. For example, based on the above, a STA (e.g., AP and non-AP STAs) that has received an OBSS PPDU corresponding to an HE PPDU via the PCH can (immediately) switch to SCH after decoding up to the BSS color and TXOP fields of the HE-SIG-A field. Alternatively, a STA (e.g., AP and non-AP STAs) that has received an OBSS PPDU corresponding to a PPDU with a PHY version starting with EHT (e.g., EHT PPDU, UHR PPDU) on the PCH can (immediately) switch to SCH after decoding up to the BSS color and TXOP fields of the U-SIG field. Based on this, a STA (e.g., AP and non-AP STAs) can switch to SCH at an earlier point in time based on the PHY header of the received OBSS PPDU without decoding the MAC header of the received OBSS PPDU. Therefore, STA can have the advantageous technical effect of obtaining a longer TXOP on SCH while performing NPCA / SCA.

[0293] Alternatively, when the OBSS PPDU received via PCH corresponds to an HE PPDU, the STA receiving the corresponding HEPPDU (e.g., AP and non-AP STA) can decode up to the BSS color and TXOP field included in the HE-SIG-A field of the received PPDU, perform a validity check by CRC check of the corresponding HE-SIG-A field, and then switch to SCH.

[0294] Alternatively, when the OBSS PPDU received via PCH corresponds to an EHT / UHR PPDU, the STA (e.g., AP and non-AP STA) that received the corresponding PPDU can decode up to the BSS color and TXOP field included in the U-SIG field of the received PPDU, perform validity verification by CRC check of the U-SIG field, and then switch to SCH.

[0295] Additionally or alternatively, the technical features for the case of receiving EHT and OBSS services after EHT PPDU are described below. In other words, when the OBSS service (or OBSS PPDU) received via PCH corresponds to EHT PPDU and PPDU defined after EHT (e.g., UHR PPDU), restriction rules may be defined additionally or alternatively.

[0296] Figure 25 Examples related to channelization are shown. For example, Figure 25 Channelization can be based on IEEE 802.11be (or EHT). For example, according to IEEE 802.11be-based channelization, 320MHz (or 320MHz band / channel / subchannel / resource) can consist of two adjacent 160MHz channels in a 6GHz band. For example, 320MHz (or 320MHz band / channel, etc.) can be divided into 320MHz-1 and 320MHz-2. For example, 320MHz-1 is defined as a 320MHz channel with channel center frequency numbers 31, 95, and 159, and 320MHz-2 can be defined as a 320MHz channel with channel center frequency numbers 63, 127, and 191.

[0297] like Figure 25 As shown, a BSS based on a 320MHz configuration can be configured in the 320MHz-1 band / channel and can be configured in the 320MHz-2 band / channel. For example, depending on the configurations of 320MHz-1 and 320MHz-2, the OBSS can overlap with the lower 160MHz (and / or higher 160MHz).

[0298] Figure 26 An example of SCA / NPCA execution at 320MHz is shown.

[0299] For example, such as Figure 26As shown, when the NPCA BSS operates based on the 320MHz-1 band / channel, it can receive OBSS PPDUs with a 320MHz bandwidth (e.g., EHT / UHR PPDUs with a 320MHz bandwidth). Various examples of OBSS PPDUs (e.g., EHT / UHR PPDUs associated with the OBSS) can be... Figure 26 The OBSS1, OBSS2, OBSS3 and / or OBSS4 shown.

[0300] Alternatively or at another location Figure 26 OBSS1 refers to an example where 160MHz of a frequency band / channel (e.g., the lower 160MHz frequency band / channel) within the entire 320MHz frequency band / channel (e.g., 320MHz-1 frequency band / channel) is configured as a PCH. For example, Figure 26 OBSS2 involves an example of configuring 160MHz of a frequency band / channel (e.g., the lower 160MHz frequency band / channel) within the entire 320MHz band / channel (e.g., 320MHz-2 band / channel) as a PCH. For example, Figure 26 OBSS3 involves an example of configuring 160MHz of a frequency band / channel (e.g., the higher 160MHz frequency band / channel) within the entire 320MHz band / channel (e.g., 320MHz-2 band / channel) as a PCH. For example, Figure 26 OBSS4 involves an example of configuring 160MHz of a frequency band / channel (e.g., the lower 160MHz frequency band / channel) within the entire 320MHz band / channel (e.g., 320MHz-2 band / channel) as a PCH. For example, Figure 26 The frequency band / channel occupied by OBSS1 can be completely consistent with the frequency band / channel occupied by NPCA BSS, and the frequency band / channel occupied by the PCH of OBSS1 can be completely consistent with the frequency band / channel occupied by the PCH of NPCA BSS. For example, Figure 26 The frequency band / channel occupied by OBSS2 partially overlaps with the frequency band / channel of NPCA BSS, while the frequency band / channel occupied by the PCH of OBSS2 may not overlap with NPCA BSS. For example, Figure 26 The frequency band / channel occupied by OBSS3 partially overlaps with the frequency band / channel occupied by NPCA BSS, and the frequency band / channel occupied by the PCH of OBSS3 may not overlap with that of NPCA BSS (e.g., the frequency band / channel occupied by the PCH of NPCA BSS). For example, Figure 26 The frequency band / channel occupied by OBSS4 partially overlaps with the frequency band / channel of NPCA BSS, and the frequency band / channel occupied by OBSS4's PCH can overlap with the frequency band / channel occupied by NPCA BSS's NCPH.

[0301] like Figure 26 As shown, when an OBSS PPDU (e.g., EHT / UHR PPDU) is received, the bandwidth information / field / subfield included in the U-SIG of the received PPDU may include information about the bandwidth value occupied by the corresponding PPDU. Specifically, information about whether the corresponding PPDU is transmitted / received through the 320MHz-1 or 320MHz-2 frequency band / channel can be indicated by the U-SIG. When such bandwidth information / field / subfield of the U-SIG is received, the STA that received the corresponding PPDU (e.g., EHT / UHRPPDU) can determine that it is performing SCA / NPCA SCH (e.g., ...) on it. Figure 26 Does the NPCH (with a bandwidth of 160MHz shown) overlap with the channel / band occupied by OBSS services (e.g., OBSS1, OBSS2, OBSS3, and / or OBSS4)? For example, based on... Figure 26 The frequency band / channel occupied by the NPH shown overlaps with the received OBSS service (e.g., the channel / resource / frequency band on which OBSS1, OBSS2, OBSS3 and / or OBSS4 are transmitted / received), so SCA / NPCA may not be performed. For example, based on the... Figure 26 The frequency bands / channels associated with the NPH shown do not overlap with the frequency bands / channels associated with received OBSS services (e.g., channels / resources / frequency bands on which OBSS1, OBSS2, OBSS3, and / or OBSS4 are transmitted / received), allowing SCA / NPCA to be performed. This determination prevents unnecessary switching to SCH / NPCH. Meanwhile, Figure 26 The terminology can be changed in different ways. For example, it can be... Figure 26 The name NPCA BSS used has been changed to various names such as SCA BSS, and the technical features of this specification are not affected. Figure 26 Restrictions on specific terms.

[0302] Alternatively or concurrently, when performing NPCA / SCA according to this specification, it may be assumed that the determination of NPCH is performed within a secondary (i.e., half the width of the BSS operating channel) channel / sub-channel / resource. In other words, Figure 26 An example could be determining the NPCH within a secondary (i.e., half the width of the BSS operating channel) channel / subchannel / resource. Based on this assumption, an AP operating at 320MHz could determine the secondary 160 channel (i.e., secondary 160MHz) as the NPCH. In other words, in Figure 26 In the example, NPCH can exist on the secondary 160MHz.

[0303] The following describes specific examples related to the above, based on Examples 1, 2, and 3.

[0304] Example 1)

[0305] Example 1 described below involves a situation where the 320MHz (e.g., 320MHz-1 band / channel / band / resource) of the NPCA BSS operating above and the PPDU bandwidth (e.g., 320MHz-1 band / channel / band / resource) of the OBSS service are identical to each other. For example, the following technical features may be similar to... Figure 26 The comparison between NPCA BSS and OBSS1 shown is relevant.

[0306] For example, based on Figure 25 For channelization, the BSS operating channel width (e.g., 320MHz-1 band / channel / band / resource) of the NPCA BSS can be the same as the bandwidth (or band / channel / band / resource) of the OBSS service (e.g., EHT PPDU). For example, when the bandwidth field included in the U-SIG field of the OBSS service (e.g., EHT PPDU) indicates 320MHz-1, the bandwidth of the OBSS service can be determined to be the same as the BSS operating channel width of the NPCA BSS. In this case, since the band / channel associated with the NPCH of the NPCA BSS always overlaps with the band / channel associated with the OBSS service, preferably, the corresponding STA does not perform NPCA / SCA. That is, when the above conditions are met, the corresponding STA does not perform a handover to NPCH / SCH.

[0307] Example 2)

[0308] Example 2 described below addresses a situation where the 320MHz band (e.g., 320MHz-1 band / channel / band / resource) operating on the NPCA BSS and the PPDU bandwidth (e.g., 320MHz-2 band / channel / band / resource) of the OBSS service differ. For example, the following technical features may differ from... Figure 26 The comparison between NPCA BSS and OBSS2 (or OBSS3) shown is relevant.

[0309] For example, based on Figure 25For channelization, the bandwidth (e.g., 320MHz-1 band / channel / band / resource) of the BSS operating channel on the NPCA BSS and the bandwidth (or band / channel / band / resource) of the OBSS service (e.g., EHT PPDU) can be different. For example, when the bandwidth field in the U-SIG field of the OBSS service (e.g., EHT PPDU) indicates 320MHz-2, 1) the bandwidth of the OBSS service overlaps with the 160MHz channel (e.g., primary 160MHz) of the PCH including the NPCA BSS, but 2) the bandwidth of the OBSS service does not overlap with the 160MHz channel (e.g., secondary 160MHz) of the NPCH including the NPCA BSS. For example, when the above conditions are met, the corresponding STA can perform a handover to the NPCH / SCH. In other words, in Example 2, the frequency bands / channels associated with NPCA BSS and OBSS2 (or OBSS3) partially overlap, the frequency bands / channels associated with PCH on NPCABSS overlap with those associated with OBSS2 (or OBSS3), but the frequency bands / channels associated with NPCH on NPCA BSS do not overlap with those associated with OBSS2 (or OBSS3). Based on this, the corresponding STA can perform a handover to the NPCH / SCH allocated on NPCA BSS.

[0310] Example 3)

[0311] Example 3 described below addresses a situation where the 320MHz bandwidth (e.g., 320MHz-1 band / channel / band / resource) for NPCA BSS operations and the PPDU bandwidth (e.g., 320MHz-2 band / channel / band / resource) for OBSS services differ. For example, the following technical features may differ from... Figure 26 The comparison between NPCA BSS and OBSS4 shown is relevant.

[0312] For example, based on Figure 25For channelization, the bandwidth of the BSS operating channel (e.g., 320MHz-1) and the bandwidth of the OBSS service (e.g., EHT PPDU) operating on the NPCA BSS can be different. For example, when the bandwidth field in the U-SIG field of the OBSS service (e.g., EHT PPDU) indicates 320MHz-2, the bandwidth of the OBSS service can overlap with the 160MHz channel (e.g., secondary 160MHz) of the NPH of the NPCABSS. For example, when the above conditions are met, since the PCH is not busy and the NPCA execution conditions are not met, NPCA / SCA can be omitted. As a result, NPCA / SCA is not executed, and PCH-based channel access can be performed according to conventional baseline operation. In other words, in Example 3, the frequency band / channel associated with the NPCA BSS and the frequency band / channel associated with OBSS4 partially overlap, but the frequency band / channel associated with the PCH on the NPCA BSS does not overlap with the frequency band / channel associated with OBSS4. Based on this, the STA does not need to perform NPCA / SCA and can perform channel access based on the PCH on the NPCA BSS.

[0313] Alternatively or optionally, it can be used with Figure 25 and Figure 26 Various modifications can be made to the related examples. For example, the above examples are described based on the assumption that the NPCH is determined within the secondary (i.e., half the width of the BSS operating channel) channel / subchannel / resource. This assumption can be changed. For example, the NPCH can exist anywhere within the width of the BSS operating channel. Therefore, the NPCH does not have to be configured as secondary 160MHz, but can be allocated / determined on secondary 80MHz in different frequency regions.

[0314] Figure 27 An example of SCA / NPCA execution at 320MHz is shown. For example, although in Figure 26 In the example, NPH was assigned / determined on the secondary 160MHz, but in Figure 27 In the example, the NPCH can exist anywhere within the BSS operating channel width. Therefore, in Figure 27 In the example, NPCH can be assigned / determined on various secondary 80MHz.

[0315] Example 4)

[0316] For example, Example 4 involves a situation where the 320MHz band / channel (e.g., 320MHz-1 band / channel) operated by the NPCA BSS and the band / channel (e.g., 320MHz-1 band / channel) occupied by received OBSS services (e.g., OBSS PPDU or EHT / UHR PPDU associated with the OBSS) are the same. For example, Example 4 involves a situation where... Figure 27 Example 4 compares NPCA BSS and OBSS1. In other words, Example 4 involves a case where the frequency band occupied by NPCA BSS and the frequency band / channel occupied by OBSS PPDU are exactly the same.

[0317] When based on Figure 25 When the channelization (e.g., 802.11be / EHT channelization) is determined, NPCA / SCA may not be performed if the channel / band indicated by the U-SIG field of the OBSS service (e.g., EHT / UHR PPDU) matches the channel / band related to the BSS operation channel width operated by the NPCA BSS above. For example, in the above case, the STA may not switch to NPCH. In other words, as in Figure 27 In the OBSS1 example, when the bandwidth field of the U-SIG of the OBSS service (EHT PPDU) indicates a frequency band / channel corresponding to 320MHz-1, and the frequency band / channel corresponding to the BSS operating channel width is also 320MHz-1, NPCA / SCA may not be performed. This is because NPCA BSS and OBSS services (e.g., EHT / UHR PPDUs associated with OBSS) always overlap.

[0318] Example 5)

[0319] For example, Example 5 can involve a situation where the 320MHz band / channel (e.g., 320MHz-1 band / channel) operated by the NPCA BSS is not the same as the band / channel (e.g., 320MHz-1 band / channel) occupied by OBSS services (e.g., OBSS PPDUs or EHT / UHR PPDUs associated with OBSS). In other words, Example 5 can involve a situation where the 320MHz band / channel (e.g., 320MHz-1 band / channel) operated by the NPCA BSS partially overlaps with the band / channel (e.g., 320MHz-1 band / channel) occupied by OBSS services (e.g., OBSS PPDUs or EHT / UHR PPDUs associated with OBSS). In other words, Example 5 involves a situation where... Figure 27Example 5 compares NPCA BSS and OBSS2 (or OBSS3). In other words, Example 5 involves a situation where the frequency band occupied by the NPH on the NPCABSS overlaps with the frequency band / channel occupied by the OBSS PPDU.

[0320] When based on Figure 25 When the channelization (e.g., 802.11be / EHT channelization) is determined, NPCA / SCA may not be performed if the channel / band indicated by the U-SIG field of the OBSS service (e.g., EHT / UHR PPDU) partially overlaps with the channel / band portion related to the BSS operation channel width operated by the NPCA BSS above. In other words, as in Figure 27 In the example of OBSS2 (or OBSS3), when the bandwidth field of the U-SIG of the OBSS service (e.g., EHT / UHR PPDU) corresponds to 320MHz-2, and the bandwidth / channel corresponding to the BSS operating channel width is also 320MHz-1, NPCA / SCA may not be performed. In other words, when the NPCH located on the secondary 80MHz and the bandwidth field of the U-SIG of the OBSS service (EHT / UHR PPDU) overlap, NPCA / SCA may not be performed.

[0321] Example 6)

[0322] For example, Example 6 can involve a situation where the 320MHz band / channel (e.g., 320MHz-1 band / channel) operated by the NPCA BSS is not the same as the band / channel (e.g., 320MHz-2 band / channel) occupied by OBSS services (e.g., OBSS PPDUs or EHT / UHR PPDUs associated with OBSS). In other words, Example 6 can involve a situation where the 320MHz band / channel (e.g., 320MHz-1 band / channel) operated by the NPCA BSS partially overlaps with the band / channel (e.g., 320MHz-2 band / channel) occupied by OBSS services (e.g., OBSS PPDUs or EHT / UHR PPDUs associated with OBSS). In other words, Example 6 involves a situation where... Figure 27 Example 6 compares NPCA BSS and OBSS4. In other words, Example 6 involves the case where the frequency band / channel occupied by NPCH on NPCA BSS and the frequency band / channel occupied by OBSS PPDU do not overlap.

[0323] In the case of Example 6, when based on Figure 25When the channelization (e.g., 802.11be / EHT channelization) is determined, the BSS operating channel bandwidth of the NPCA BSS is associated with a 320MHz-1 band / channel, and the bandwidth field of the U-SIG for OBSS services (e.g., EHT / UHR PPDU) is associated with a 320MHz-2 band / channel. For example, in Figure 27 In the case of OBSS4, OBSS services (e.g., EHT / UHR PPDU) may not overlap with NPCH. In this case, since the PCH is not busy, the NPCA execution conditions are not met, and accordingly, NPCA / SCA can be omitted. As a result, PCH-based channel access is performed based on conventional baseline operations. In other words, in Example 6, the frequency band / channel associated with the NPCA BSS and the frequency band / channel associated with OBSS4 partially overlap, but since the frequency band / channel associated with the PCH on the NPCA BSS does not overlap with the frequency band / channel associated with OBSS4, NPCA / SCA is not required. Based on this, the STA can perform channel access based on the PCH on the NPCA BSS.

[0324] Examples of this specification can be represented by various process flowcharts.

[0325] For example, Figure 21 This is a flowchart of the process related to sending STA. Figure 21 The operation can be performed at either the AP or a non-AP STA. For example, to perform... Figure 21 The AP can be any one of multiple APs attached to a multi-link device (e.g., AP MLD). For example, performing... Figure 21 A non-AP STA can be any one of multiple non-AP STAs attached to a multi-link device (e.g., a non-AP STA MLD).

[0326] As shown in step S2110, when the STA receives a frame from another BSS (e.g., an OBSS frame), it can set a basic NAV on the main channel.

[0327] Step S2120 shown relates to a scenario based on Case 1 described above. For example, as mentioned above, Case 1 may involve receiving an OBSS PPDU on the PCH and immediately performing a switch to the SCH. For example, as shown in step S2120, the STA may immediately switch to the SCH (e.g., the NPCA main channel, the S20 channel, or the NPCH) and perform a backoff.

[0328] Step S2130 shown relates to a scenario operating based on Case 2 described above (e.g., including Case 2-1 and Case 2-2). For example, as described above, a STA operating based on Case 2 can, after receiving an OBSS PPDU on the PCH, postpone access to or switching to the SCH for up to a maximum NAV wait time (e.g., NAVWaittime) instead of immediately switching to the SCH. If PPDU detection (e.g., detection of CTS and / or data frames) is performed during the NAV wait time, the STA can switch / access the SCH. For example, as in step S2130 shown, if the PPDU detection is acknowledged while waiting during the wait time (e.g., NAVWaitTime), the STA can immediately switch to the SCH (e.g., the NPCA main channel, NPCH, or S20 channel) and perform backoff.

[0329] For example, step S2130 can be performed after performing step S2120 or step S2130 above. For example, as shown in step S2140, when the BC counter becomes 0 on the SCH that has performed backoff (e.g., NPCA main channel or NPCH), the STA can perform CCA on another SCH (e.g., S40 / S80).

[0330] For example, when channel extension is applied to an additional SCH, step S2150 can be performed. For example, in step S2150 as shown, the STA can send a PPDU comprising a frame having bandwidth including the SCH that has performed backoff and another SCH whose CCA result is determined to be idle.

[0331] For example, Figure 22 This is a flowchart of the process related to receiving the STA. Figure 22 The operation can be performed at either the AP or a non-AP STA. For example, to perform... Figure 22 The AP can be any one of multiple APs attached to a multi-link device (e.g., AP MLD). For example, performing... Figure 22 A non-AP STA can be any one of multiple non-AP STAs attached to a multi-link device (e.g., a non-AP STA MLD).

[0332] As shown in step S2210, when the STA receives a frame from another BSS (e.g., an OBSS frame), it can set a basic NAV on the main channel.

[0333] Step S2220 shown relates to a scenario based on Case 1 described above. For example, as mentioned above, Case 1 may involve receiving an OBSS PPDU on the PCH and immediately performing a switch to the SCH. For example, as shown in step S2220, the STA may immediately switch to the SCH (e.g., the NPCA main channel, NPCH, or S20 channel) and perform backoff.

[0334] Step S2230 shown relates to a scenario operating based on Case 2 described above (e.g., including Case 2-1 and Case 2-2). For example, as described above, a STA operating based on Case 2 can, after receiving an OBSS PPDU on the PCH, postpone access to or switching to the SCH for up to a maximum NAV wait time (e.g., NAVWaittime) instead of immediately switching to the SCH. If PPDU detection (e.g., detection of CTS and / or data frames) is performed during the NAV wait time, the STA can switch / access the SCH. For example, as in step S2230 shown, if the PPDU detection is acknowledged while waiting during the wait time (e.g., NAVWaitTime), the STA can immediately switch to the SCH (e.g., the NPCA main channel, NPCH, or S20 channel) and perform backoff.

[0335] For example, step S2230 can be performed after performing step S2220 or step S2230 above. For example, as shown in step S2240, when a PPDU including at least one frame is received while performing backoff, the STA can determine whether the corresponding frame is addressed to itself (e.g., determine whether the RA field matches the MAC address of the receiving STA).

[0336] If, as a result, the corresponding frame is addressed to itself, then step S2260 can be executed. For example, according to step S2260, the STA can decode the frame body of the received frame.

[0337] If, as a result, the corresponding frame is not addressed to itself, step S2250 can be executed. For example, according to step S2250, the STA can set the NAV based on the value of the duration field included in the MAC header of the received frame.

[0338] Various modifications can be made to the examples in this specification. The examples in this specification can be modified in the following ways.

[0339] For example, even when a NAV (e.g., a basic NAV set by a received OBSS PPDU) is set on a PCH (e.g., a channel including a primary 20MHz channel), a STA performing NPCA / SCA (e.g., an AP or non-AP STA) can still transmit frames / PPDUs on a SCH. For example, a STA can transmit PPDUs on at least one SCH in an idle state determined by backoff performed on one or more SCHs (e.g., a channel including an S20 channel or a primary NPCA channel) (and the CCA result of one or more SCHs without backoff). For example, PPDUs can be subjected to preamble puncturing against the subchannel corresponding to the PCH.

[0340] Alternatively or concurrently, the TXOP acquired for a frame / PPDU transmission on the SCH can be set to end before the end time of the NAV (e.g., the basic NAV) on the PCH. For example, the length of the TXOP can be set / indicated by the duration / ID field of the corresponding frame (e.g., the MAC header of the frame / PPDU transmitted on the SCH). For example, the value of the duration / ID field can be set to the value of the time required for frame / PPDU exchange after the corresponding frame / PPDU (e.g., including the inter-frame interval (IFS) time).

[0341] Alternatively or concurrently, the EDCA parameter set for each SCH that has performed backoff can be set to the EDCA parameter set on the PCH or the MU EDCA parameter set, or a new EDCA parameter set. This EDCA parameter set can be applied to all SCHs either identically or individually (or differently).

[0342] 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, NPCA main channel, or NPCH). For example, an STA (e.g., AP or non-AP STA) can perform backoff on the SCH because a frame to be transmitted exists, or even when no frame to be transmitted exists, 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.

[0343] Alternatively or concurrently, the EDCA parameter set for each SCH that has performed backoff can be set to the EDCA parameter set on the PCH or the MU EDCA parameter set, or a new EDCA parameter set. This EDCA parameter set can be applied to all SCHs either identically or individually (or differently).

[0344] Alternatively, when a basic NAV is set on the PCH due to an OBSS PPDU, the STA (e.g., an AP or non-AP STA) can trigger NPCA based on the technical features of Case 1 or Case 2 above, switch to the NPCA main channel (or NPCH), or access the NPCA main channel. For example, based on Case 1 above, the STA can immediately trigger NPCA (or switch to the NPCA main channel, or access the NPCA main channel) based on setting a basic NAV on the PCH.

[0345] Alternatively, based on setting a basic NAV on the PCH, the STA in Case 2 above may not immediately trigger NPCA (or switch to the NPCA main channel (or NPCH), or access the NPCA main channel). Specifically, the STA in Case 2 above may not immediately trigger NPCA, but instead wait for a preset waiting time (e.g., referred to as NAVWaitTime) (or postpone the triggering of NPCA, postpone the access to NPCA, or postpone the switch to SCH). For example, during the aforementioned waiting period, when the corresponding STA performs PPDU detection, it may trigger NPCA (or switch to the NPCA main channel, or access the NPCA main channel). For example, PPDU detection may mean receiving a PPDU including CTS on the PCH, or receiving a PPDU including data frames related to RTS / CTS exchange on the PCH. As mentioned above, the NAV waiting time or NAVWaitTime can be calculated based on parameters widely known in wireless LAN systems. For example, NAVWaitTime can be calculated as (2 × aSIFSTime) + (CTS_Time) + aRxPHYStartDelay + (2 × aSlotTime), and CTS_Time can be calculated based on the length of the CTS frame and the PHY data rate.

[0346] Figure 23 This is another process flowchart illustrating an example from this specification.

[0347] The steps S2310 and S2320 shown are examples of this specification. Figure 23 The operation can be performed at either AP or non-APSTA locations. For example, Figure 23 The operation can be executed by Figure 21 or Figure 22 The device is used to perform this.

[0348] For example, in step S2310, the STA may acquire information related to the triggering of the NPCA. For instance, acquiring information related to the triggering of the NPCA (or information related to the triggering conditions) may be a process of acquiring information related to the OBSS PPDU (or OBSS signal / service / frame, etc.) received on the PCH (including the primary 20MHz channel). Alternatively, step S2310 may include a process of determining whether the BSS PPDU received on the PCH is an OBSS PPDU or an OBSS-internal PPDU. The specific method for performing OBSS PPDU identification based on the version / type of the received PPDU may be the same as the example described above in this specification.

[0349] Alternatively, step S2310 may include at least one of the following: the process of the STA receiving the OBSS PPDU; the process of determining whether the OBSS PPDU includes an RTS / MU-RTS; and / or the process of determining whether the OBSS PPDU is a non-HT / HT / VHT / HE / EHT / UHR PPDU. Alternatively, step S2310 may include the process of the STA confirming / obtaining the TXOP length and / or PPDU length of the OBSS PPDU.

[0350] For example, in step S2320, the STA may perform a handover to the NPCA main channel (e.g., a channel including the SCH or S20 channel) based on information related to the triggering of the NPCA. Alternatively, performing a handover to the NPCA main channel may be represented as attempting / performing access to the NPCA main channel, or attempting / performing NPCA / SCA.

[0351] As in step S2320, a handover to the NPCA main channel (e.g., a channel including the SCH or S20 channel) can be performed based on information related to the triggering of the NPCA. For example, when the various triggering conditions set forth in this specification are met, the corresponding STA (e.g., AP or non-AP STA) can begin / attempt a handover to the aforementioned SCH (or NPCA main channel or NPCH). For example, when the various triggering conditions set forth in this specification are not met, the corresponding STA (e.g., AP or non-AP STA) cannot begin / attempt a handover to the aforementioned SCH (or NPCA main channel).

[0352] For example, information related to the triggering of NPCA may include information about the basic NAV associated with PCH. For example, a STA operating according to Case 1 of this specification may, according to step S2320, immediately perform a switch to the NPCA main channel (e.g., a channel including SCH or S20 channel) when the basic NAV is set on PCH.

[0353] For example, information related to NPCA triggering may include information related to the version / type of the received PPDU (e.g., OBSS PPDU). Furthermore, information related to NPCA triggering may include information about whether the received PPDU (e.g., OBSS PPDU) includes an RTS (or MU-RTS). Therefore, according to step S2320, the STA operating based on Case 2 of this specification may wait for up to NAVWaitTime if the received PPDU (e.g., OBSS PPDU) includes an RTS (or MU-RTS) without immediately performing a handover to the NPCA main channel (e.g., a channel including the SCH or S20 channel). When the STA receives a response frame (e.g., a data frame related to RTS / CTS exchange or a CTS) on the PCH while waiting during NAVWaitTime, the STA may immediately perform a handover to the NPCA main channel (e.g., a channel including the SCH or S20 channel).

[0354] Alternatively or alternatively, when performing steps S2310 and S2320, at least one of steps S2140 and S2150 may be performed sequentially. Alternatively or alternatively, when performing steps S2310 and S2320, at least one of steps S2240 to S2260 may be performed sequentially.

[0355] Figure 24 This is another process flowchart illustrating an example of this specification. Figure 24 The operation can be performed at either the AP or a non-AP STA. For example, Figure 24 The operation can be executed by Figure 21 , Figure 22 or Figure 23 The device is used to perform this.

[0356] According to step S2410 shown, the STA can receive the OBSS (Overlapping Basic Service Set) signal. For example, the OBSS signal can be an OBSS PPDU (or service / frame, etc.). For example, the OBSS signal can be received through the PCH (including the primary 20MHz channel) mentioned above. For example, a basic NAV can be set for the PCH based on the OBSS signal.

[0357] According to step S2420, the STA can perform access to the NPCA (Non-Main Channel Access) main channel based on the OBSS signal. For example, access to the NPCA main channel may include a handover performed by the STA to the NPCA main channel. For example, access to the NPCA main channel may mean performing an NPCA / SCH operation. For example, access to the NPCA main channel may mean triggering an NPCA. For example, when performing access to the NPCA main channel, the STA can perform backoff against the NPCA main channel.

[0358] According to step S2420, access / handover to the NPA main channel is performed based on the received OBSS signal (e.g., OBSS PPDU). For example, the start time of access / handover to the NPA main channel can be determined based on the received OBSS signal (e.g., OBSS PPDU). For example, it can be determined whether to perform access / handover to the NPA main channel based on the received OBSS signal (e.g., OBSS PPDU).

[0359] According to step S2420, access / handover to the NPCA main channel can be performed based on at least one of the basic NAV (Network Assignment Vector) set for the main channel according to the OBSS signal and the waiting time associated with the OBSS signal. In other words, access / handover to the NPCA main channel can be performed immediately after setting the basic NAV, or after waiting during the waiting time associated with the OBSS signal (e.g., the aforementioned NAV waiting time). In other words, the STA can postpone access to the NPCA main channel based on the NAV waiting time (e.g., the aforementioned NAV waiting time). For example, when a CTS or data frame (related to RTS / CTS switching) is received (on the PCH) during the NAV waiting time, access to the NPCA main channel can be performed immediately based on CTS / data frame detection. In other words, when the STA receives a CTS during the NAV waiting time, the STA can perform access to the NPCA main channel based on receiving a data frame or CTS through the main channel. This situation relates to the example of situation 2 described in this specification. For example, even if the received PPDU includes RTS / MU-RTS, the aforementioned NAV waiting time (e.g., the aforementioned NAV waiting time) can be disregarded, and the STA can perform access to the NPCA main channel based on the basic NAV (immediately). This situation relates to the example of Case 1 described in this specification. For example, the NAV waiting time (e.g., the aforementioned NAV waiting time) can be calculated based on a parameter obvious to those skilled in the art as (2 × aSIFSTime) + (CTS_Time) + aRxPHYStartDelay + (2 × aSlotTime). In other words, the NAV waiting time can be set based on the length of the CTS (associated with the RTS (or MU-RTS)).

[0360] Alternatively or alternatively, when performing steps S2410 and S2420, at least one of steps S2140 and S2150 may be performed sequentially. Alternatively or alternatively, when performing steps S2410 and S2420, at least one of steps S2240 to S2260 may be performed sequentially.

[0361] Alternatively or concurrently, when performing steps S2410 and S2420 above, due to NPCA / SCA, the transmission and reception of PPDUs on channels other than PCH are possible. Therefore, based on access to the NPCA main channel, the STA can perform PPDU transmission based on a first channel including the NPCA main channel. Furthermore, for example, based on access to the NPCA main channel, the STA can receive PPDUs through a second channel including the NPCA main channel. For example, the PPDUs transmitted / received through the first / second channel can be at least one of the following: non-HT (non-high throughput) PPDUs (Physical Protocol Data Units), HT (high throughput) PPDUs, VHT (very high throughput) PPDUs, HE (high efficiency) PPDUs, EHT (extremely high throughput) PPDUs, and / or UHR (ultra-high reliability) PPDUs.

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

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

[0364] 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 read the at least one memory to load and execute the computer program.

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

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

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

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

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

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

[0371] 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 domains of AI and 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.

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

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

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

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

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

[0377] Supervised learning refers to the method of training an artificial neural network in states where labels for the training data are given, and the labels can refer to the correct answer (or result value) that the artificial neural network must infer when the training data is input. Unsupervised learning refers to the method of training an artificial neural network in states where no labels are given for the training 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.

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

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

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

[0381] 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 may include wheels, brakes, propellers, etc., in their drive unit, enabling them to move on the ground or fly in the air.

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

[0383] Extended reality is a general term encompassing 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 provides this by mixing and combining virtual objects from the real world.

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

[0385] 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 STA receives the Overlapping Basic Service Set (OBSS) signal; as well as Based on the OBSS signal, the STA performs access to the NPCA main channel from the non-main channel. The access to the NPCA main channel is performed based on at least one of the basic network allocation vector NAV set for the main channel according to the OBSS signal and the waiting time associated with the OBSS signal.

2. The method according to claim 1, wherein, The access to the NPCA main channel includes: a handover performed by the STA to the NPCA main channel. Specifically, based on the handover to the NPCA main channel, the STA performs backoff for the NPCA main channel.

3. The method according to claim 1, wherein, The OBSS signal includes a request to send an RTS or a multi-user RTS (MU-RTS). The waiting time associated with the OBSS signal is the NAV waiting time associated with the RTS or the MU-RTS. The NAV waiting time is set based on the length of the allowed CTS transmission associated with the RTS or the MU-RTS.

4. The method according to claim 3, wherein, The STA postpones its access to the NPCA main channel based on the NAV waiting time.

5. The method according to claim 4, wherein, Based on the STA receiving the CTS during the NAV waiting time, the STA performs the access to the NPCA main channel based on receiving a data frame through the main channel or the CTS.

6. The method according to claim 1, wherein, The OBSS signal includes a request to send an RTS or a multi-user RTS (MU-RTS). The STA performs access to the NPCA main channel based on the basic NAV without considering the waiting time associated with the OBSS signal.

7. The method according to claim 1, wherein, The main channel includes a primary 20 MHz channel, and the NPCA main channel includes a secondary 20 MHz channel.

8. The method according to claim 1, wherein, The OBSS signal includes at least one of the following: non-high throughput non-HT physical protocol data unit (PPDU), high throughput HT PPDU, very high throughput VHT PPDU, high efficiency HE PPDU, extremely high throughput EHT PPDU, and / or ultra-high reliability UHR PPDU. Specifically, based on the PPDU version of the OBSS signal, the timing point for performing the access to the NPCA main channel of the non-main channel is determined.

9. The method according to claim 1, wherein, Based on the access to the NPCA main channel, the STA performs PPDU transmission based on a first channel including the NPCA main channel.

10. The method according to claim 1, wherein, Based on the access to the NPCA main channel, the STA receives PPDU through a second channel including the NPCA main channel.

11. The method according to claim 1, wherein, The STA is an access point (AP) or a non-AP STA.

12. A station STA, the STA comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: The STA receives the Overlapping Basic Service Set (OBSS) signal; and The STA performs access to the NPCA main channel from the non-main channel based on the OBSS signal. The access to the NPCA main channel is performed based on at least one of the basic network allocation vector NAV set for the main channel according to the OBSS signal and the waiting time associated with the OBSS signal.

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

14. 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 STA receives the Overlapping Basic Service Set (OBSS) signal; as well as The STA performs access to the NPCA main channel from the non-main channel based on the OBSS signal. The access to the NPCA main channel is performed based on at least one of the basic network allocation vector NAV set for the main channel according to the OBSS signal and the waiting time associated with the OBSS signal.

15. The computer-readable medium according to claim 14, wherein, The computer-readable medium performs operations relating to any one of claims 2 to 11.

Images