Auxiliary primary channel access mechanism in wireless communications

Abstract

Techniques for assisting a primary channel access mechanism in wireless communications are described herein. An apparatus (e.g., an access point (AP) or a non-AP working station (STA)) detects overlapping basic service set (OBSS) transmissions on a primary channel. In response to detecting an OBSS transmission on the primary channel, the apparatus switches to a secondary primary channel.

Description

[0001] Cross-referencing

[0002] This disclosure is part of a non-provisional patent application that claims priority to U.S. Provisional Patent Application No. 63 / 498,565 (filed April 27, 2023), the entire contents of which are incorporated herein by reference. [Technical Field]

[0003] This disclosure generally relates to wireless communications, and more specifically, to a secondary master channel access mechanism in wireless communications. [Background Technology]

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the following claims and are not acknowledged as prior art in this section.

[0005] In wireless communications, such as Wi-Fi (or WiFi) and wireless local area networks (WLANs) under the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, access points (APs) and their associated non-AP stations (STAs) monitor the primary channel to detect transmissions on the primary channel or perform channel access to initiate transmissions when the channel is determined to be idle. When a device (e.g., an AP or a non-AP STA) detects an overlapping basic service set (OBSS) transmission with a signal strength equal to or greater than a certain level (e.g., -62 dBm), the device can monitor a non-primary channel (referred to herein as the “secondary primary channel”) to transmit or receive data without including the primary channel and one or more other non-primary channels occupied by OBSS frame transmissions. Before initiating a transmission opportunity (TXOP) on the secondary primary channel, the device can invoke a backoff procedure. After the TXOP on the secondary primary channel ends, the device can switch back to the primary channel to resume its operation on the primary channel.

[0006] However, the AP and its associated non-AP STAs may not have the same channel state on the primary channel and the secondary primary channel. If the AP and its associated non-AP STAs are not on the same channel, transmissions may be missed. For example, a non-AP STA may have switched to the secondary primary channel and detected an OBSS transmission on the secondary primary channel. The non-AP STA may then switch back to the primary channel. However, the AP may be exchanging frames with one or more of its other associated non-AP STAs on the secondary primary channel, while the non-AP STA is on the primary channel. Therefore, when a non-AP STA detects an OBSS transmission on the primary channel, the AP may not see the same OBSS transmission on the primary channel. If a non-AP STA switches to the secondary primary channel because it detected an OBSS transmission on the primary channel, the AP and that non-AP STA will not be able to exchange frames with each other. It can be seen that how to effectively utilize the secondary primary channel remains a key problem that needs to be solved. Therefore, a solution for a secondary primary channel access mechanism in wireless communication is needed. [Summary of the Invention]

[0007] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary aims to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments will be further illustrated in the detailed description. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0008] The objective of this disclosure is to provide schemes, concepts, designs, techniques, methods, and apparatus related to auxiliary master channel access mechanisms in wireless communication. It is believed that implementing one or more of the schemes proposed herein may solve or mitigate the aforementioned problems.

[0009] In one aspect, one method might involve a processor at a workstation (STA) detecting OBSS transmissions on the primary channel. Another method might involve the processor switching to a secondary primary channel in response to the detection of OBSS transmissions on the primary channel.

[0010] In another aspect, one approach might involve the AP's processor detecting OBSS transmissions on the primary channel. The approach might also involve the processor switching to a secondary primary channel in response to the detection. This secondary primary channel might be aligned with one or more STAs associated with the AP that have secondary primary channel access capabilities.

[0011] In another aspect, an apparatus may include a transceiver configured for wireless communication and a processor coupled to the transceiver. The processor may detect OBSS transmissions on a primary channel. The processor may also switch to a secondary primary channel in response to the detection of OBSS transmissions on the primary channel.

[0012] It is worth noting that while the descriptions provided herein may be within the context of certain wireless access technologies, networks, and network topologies (such as Wi-Fi), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of wireless access technologies, networks, and network topologies, such as, but not limited to, Bluetooth, ZigBee, 5G / New Radio (NR), LTE, LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial Internet of Things (IIoT), and Narrowband Internet of Things (NB-IoT). Therefore, the scope of this disclosure is not limited to the examples described herein. [Attached Image Description]

[0013] The accompanying drawings are included to provide a further understanding of this disclosure and form part of this disclosure. These drawings illustrate embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0014] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes consistent with this disclosure can be implemented.

[0015] Figure 2 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0016] Figure 3 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0017] Figure 4 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0018] Figure 5 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0019] Figure 6 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0020] Figure 7 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0021] Figure 8 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0022] Figure 9This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0023] Figure 10 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0024] Figure 11 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0025] Figure 12 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0026] Figure 13 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0027] Figure 14 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0028] Figure 15 This is a schematic diagram of an example scenario in which the proposed solutions consistent with this disclosure can be implemented.

[0029] Figure 16 This is a block diagram of an example communication system, consistent with various embodiments of this disclosure.

[0030] Figure 17 This is a flowchart of a first example process, consistent with various embodiments of this disclosure.

[0031] Figure 18 This is a flowchart of a second example process, consistent with various embodiments of this disclosure.

Detailed Implementation Methods

[0032] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter and can be embodied in various forms. This disclosure can be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are intended to make the description of this disclosure comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. Details of well-known features and techniques may be omitted in the following description to avoid unnecessarily obscuring the presented embodiments and implementations.

[0033] Overview

[0034] The implementations disclosed herein relate to various techniques, methods, schemes, and / or solutions for auxiliary master channel access mechanisms in wireless communication. According to this disclosure, many possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of them can be implemented in one or another combination. These various solutions and schemes implement auxiliary master channel access mechanisms between APs and non-AP STAs. Therefore, the various solutions and schemes presented herein can solve or alleviate the aforementioned problems.

[0035] Figure 1 An example network environment 100 is shown, in which various solutions and schemes can be implemented according to this disclosure. Figures 2 to 18 Examples of implementations of various proposed schemes in network environment 100 according to this disclosure are shown. The following descriptions of the various proposed schemes are based on… Figures 1 to 18 Provided.

[0036] Reference Figure 1 Network environment 100 may include at least a first STA (STA 110) and a second STA (STA 120). One of STA 110 and STA 120 may be an AP STA (interchangeably referred to herein as "AP"), while the other of STA 110 and STA 120 may be a non-AP STA associated with an AP STA (interchangeably referred to herein as "STA"). Although other STAs may be involved in network environment 100 under one or more of the scenarios presented herein, for simplicity, Figure 1 Only two STAs (STA 110 and STA 120) are shown in this document; it should be understood that other STAs may be involved (e.g., other non-AP STAs participating in the auxiliary master channel access mechanism of the proposed schemes in this disclosure). Each of STA 110 and STA 120 can be configured to implement various proposed schemes according to this disclosure, as described below. It is worth noting that although various proposed schemes may be described individually or separately below, in actual implementation, some or all of these proposed schemes may be used in combination or implemented. Of course, each proposed scheme can be used or implemented individually or separately.

[0037] According to the proposed scheme disclosed herein, as a secondary primary channel access rule, when an AP or non-AP STA detects that the primary channel is busy due to OBSS transmissions, it can initiate channel access on the secondary primary channel (non-primary channel). The non-AP STA can further check if its internal Basic Service Set (intraperi-BSS) network allocation vector (NAV) counter is zero. If the internal BSS NAV counter is not zero, it should remain on the primary channel without switching to the secondary primary channel upon detecting OBSS transmissions on the primary channel. The secondary primary channel can be aligned with all associated STAs that have secondary primary channel access capabilities. Under the proposed scheme, after switching from the primary channel to the secondary primary channel, if the AP detects a physical-layer protocol data unit (PPDU) sent to the AP or obtains a transmission opportunity to exchange frames with one or more associated non-AP STAs, it can continue to remain on the secondary primary channel. Furthermore, if any of several events occur, the AP can return to the primary channel. One such event might be that the value of the AP's Basic Network Allocation Vector (NAV) counter on the primary channel is less than or equal to a threshold (e.g., ≥0), even if the AP is not participating in a TXOP on the secondary primary channel. Another event might be that the AP sends a notification to return to the primary channel, which is carried in the physical-layer (PHY) header or medium access control (MAC) header or MAC payload of a PPDU sent by the AP, or in a specific control frame, etc. Yet another event might be that the AP detects an OBSS transmission on the secondary primary channel whose OBSS PPDU or TXOP ends after a threshold time (e.g., the threshold is equal to or greater than zero) prior to the end time of the AP's Basic NAV or OBSS PPDU length on the primary channel.

[0038] According to the proposed scheme of this disclosure, after switching from the primary channel to the secondary primary channel, a non-AP site (STA) can remain on the secondary primary channel upon detecting a Physical Layer Protocol Data Unit (PPDU) sent by its associated Access Point (AP). This PPDU can be used to set the Intra-BSS Network Allocation Vector (NAV) based on the PPDU detected on the secondary primary channel. Under the proposed scheme, after switching from the primary channel to the secondary primary channel, the non-AP STA can return to the primary channel if any of the following events occur: The first event (Case A) is that the non-AP STA's Intra-BSS NAV has been set and counted down to zero based on the PPDU detected on the secondary primary channel. The second event (Case B) is that the non-AP STA participated in a Transmission Opportunity (TXOP) on the secondary primary channel, and that TXOP has ended. The third event (Case C) is that the value of the non-AP STA's basic NAV counter on the primary channel is less than or equal to a threshold (e.g., ≥0) if the non-AP STA did not participate in a TXOP on the secondary primary channel. The fourth event (Case D) could be that the maximum number of retries for initiating frame switching on the secondary primary channel by the non-AP STA has been reached (e.g., after sending a request-to-send (RTS) frame, no response is detected for a duration equal to the short interframe space (SIFS) plus the physical-layer reception delay (PHY_RX_Ddelay) after the request frame ends). The fifth event (Case E) could be that the non-AP STA receives an OBSS transmission on the secondary primary channel, where the end time of the OBSS PPDU or TXOP transmission is later than a threshold time prior to the end time of the basic NAV on the primary channel by the non-AP STA (e.g., the threshold is equal to or greater than zero). The sixth event (Case F) could be that the non-AP STA receives a notification from the AP returning to the primary channel.

[0039] According to the proposed scheme of this disclosure, after switching back to the primary channel from the secondary primary channel, a non-AP STA can switch to access the secondary primary channel according to the aforementioned secondary primary channel access rules after determining that the associated AP has returned to or is already on the primary channel. If the non-AP STA detects a PPDU transmitted by its associated AP on the primary channel, it determines that the AP is on the primary channel. The non-AP STA can start a timer (e.g., a primary channel synchronization delay timer, or a PrimaryChannelSyncDelay timer) when returning to the primary channel. If the non-AP STA detects a PPDU transmitted by its associated AP on the primary channel, the timer can be reset to zero during the countdown. A timer reaching zero can be equivalent to or considered as an event in which the non-AP STA detects that its associated AP has transmitted a PPDU on the primary channel, so that the non-AP STA can determine that the associated AP has returned to or is already on the primary channel. Under the proposed scheme, the AP can start a timer (e.g., a primary channel synchronization delay timer, or a PrimaryChannelSyncDelay timer) when returning to the primary channel. The AP can reset the timer after transmitting a PPDU indicating that the AP has returned to the primary channel. A PPDU can be a PPDU transmitted to one or more target non-AP STAs, a response PPDU in response to a PPDU received from a non-AP STA, or a control frame that does not require a response, such as CTS-to-Self. If the timer value is zero, the AP can switch to accessing the secondary primary channel according to the secondary primary channel access rules described above.

[0040] Figure 2 An example scenario 200 is shown, in which the proposed scheme according to this disclosure can be implemented. Scenario 200 relates to an example of auxiliary primary channel access under the proposed scheme. In scenario 200, the AP and non-AP STAs (in...) Figure 2A primary AP (STA1) can detect an OBSS transmission on the primary channel (e.g., a 20MHz primary channel) and, therefore, switch to the secondary primary channel (e.g., a 20MHz secondary primary channel) at time 1, provided that STA1's internal basic service set (intra-BSS) NAV value is zero. STA1 can execute an enhanced distributed channel access (EDCA) backoff procedure and obtain a TXOP by successfully initiating a request to transmit (RTS) frame on the secondary primary channel to its associated AP. The duration of the TXOP can be limited by the duration of the OBSS TXOP on the primary channel. At time 2, when the TXOP ends, STA1 and the AP can switch back to the primary channel. The AP can provide an indication to STA1 in a block acknowledgement (BA) frame or in another frame, aggregated with the BA, that the AP will return to the primary channel at the end of the BA frame.

[0041] Figure 3 An example scenario 300 is shown, in which the proposed scheme of this disclosure can be implemented. Scenario 300 relates to an example of secondary primary channel access under the proposed scheme. In scenario 300, a non-AP site (in Figure 3 A primary access point (AP) labeled "STA1" can detect an OBSS transmission on the primary channel (e.g., a 20MHz primary channel) and therefore switch to the secondary primary channel (e.g., a 20MHz secondary primary channel) at time 1 if the NAV value of STA1's internal basic service set (intra-BSS) is zero. An associated AP (as the TXOP holder) and STA1 (as the TXOP responder) can exchange frames on the secondary primary channel. At time 2, when the TXOP ends, STA1 and the AP can switch back to the primary channel. The AP can provide an indication in a downlink (DL) PPDU or in aggregation with a DL PPDU in another frame to indicate that the AP will return to the primary channel if: (i) if the DL PPDU solicits an immediate response frame, it returns to the primary channel at the end of the BA frame; or (ii) if the DL PPDU does not solicit an immediate response frame, it returns to the primary channel at the end of the DL PPDU. It is noteworthy that the TXOP on the secondary primary channel ends at time 2, which may be later than the end time of the OBSS TXOP detected by STA1 on the primary channel.

[0042] Figure 4 An example scenario 400 is shown, in which the proposed scheme of this disclosure can be implemented. Scenario 400 relates to an example of secondary primary channel access under the proposed scheme. In scenario 400, a non-AP site (in Figure 4The site marked "STA2" detects OBSS transmission on the primary channel (e.g., 20MHz primary channel) and therefore switches to the secondary primary channel (e.g., 20MHz secondary primary channel) at time point 1. An associated AP and another non-AP site (in...) Figure 4 STA1 (marked as "STA1") can perform frame switching on the secondary primary channel. STA2 can detect PPDUs (e.g., RTS) transmitted by its associated AP on the secondary primary channel and thus set its intra-BSS NAV based on the duration information in the PPDU. The AP can provide an indication in the DL PPDU or by aggregating it with a DL PPDU in another frame to indicate that it will return to the primary channel. At the end of the TXOP, at time point 2, STA1, STA2, and the AP can switch back to the primary channel. It is worth noting that the TXOP on the secondary primary channel may end at time point 2, which may be later than the end time of the OBSS TXOP on the primary channel detected by STA2.

[0043] Figure 5 An example scenario 500 is illustrated, in which the proposed scheme of this disclosure can be implemented. Scenario 500 relates to an example of secondary primary channel access under the proposed scheme. In Scenario 500, a non-AP site may perform an EDCA backoff procedure and initiate an RTS frame to its associated AP on a secondary primary channel (e.g., a 20MHz secondary primary channel). The non-AP site may not receive a CTS (clear-to-send) frame as a response to the RTS frame for a duration after the RTS ends, which is SIFS+PHY_RX_Ddelay. The non-AP site may retry initiating the RTS, but may not receive any CTS as a response to the RTS for the duration SIFS+PHY_RX_Ddelay after the RTS ends. After the number of retries reaches a maximum threshold, the non-AP site may switch back to the primary channel (e.g., the 20MHz primary channel). It is worth noting that the non-AP site may switch back to the primary channel before its basic NAV counter on the primary channel reaches a threshold (e.g., ≥0).

[0044] Figure 6An example scenario 600 is shown, in which the proposed scheme of this disclosure can be implemented. Scenario 600 relates to an example of secondary primary channel access under the proposed scheme. In scenario 600, a non-AP site can detect OBSS transmissions on a secondary primary channel (e.g., a 20MHz secondary primary channel). The non-AP site can determine that the end time of the OBSS transmission's OBSS PPDU or TXOP is later than a threshold time (e.g., the threshold is equal to or greater than zero) prior to its basic NAV end time on the primary channel. The non-AP site can switch back to the primary channel (e.g., the 20MHz primary channel) in response to such determination. Notably, the non-AP site may switch back to the primary channel before its basic NAV counter on the primary channel reaches a threshold (e.g., ≥0).

[0045] Figure 7 An example scenario 700 is shown, in which the proposed scheme of this disclosure can be implemented. Scenario 700 relates to an example of secondary primary channel access under the proposed scheme. In scenario 700, a non-AP site may switch back to the primary channel (e.g., the 20MHz primary channel) after the maximum number of failed frame switching attempts has been reached. The non-AP site may also start a timer (e.g., the PrimaryChannelSyncDelay timer). The non-AP site may start the timer's countdown to zero, regardless of whether an OBSS PPDU is detected on the primary channel. After the timer reaches zero, the non-AP site may switch back to the secondary primary channel (basic NAV set or updated) upon detecting an OBSS transmission on the primary channel (e.g., by detecting the preamble of OBSS PPDU2).

[0046] Figure 8An example scenario 800 is shown, in which the proposed scheme according to this disclosure can be implemented. Scenario 800 relates to an example of secondary primary channel access under the proposed scheme. In scenario 800, a non-AP STA can switch back to the primary channel (e.g., the 20MHz primary channel) after detecting an OBSS transmission, and the non-AP STA can start a timer (e.g., a PrimaryChannelSyncDelay timer). The non-AP STA can start the countdown of the timer. When the non-AP STA detects a PPDU (e.g., a CTS-to-Self with the BA, CTS, Duration field set to 0) sent by its associated AP, the timer (e.g., the PrimaryChannelSyncDelay timer) can be reset to zero in response to the detection of the PPDU. After the timer reaches zero, the non-AP STA can switch back to the secondary primary channel from the primary channel upon detecting an OBSS transmission on the primary channel (where the basic NAV has been set or updated) (e.g., by detecting the preamble of OBSS PPDU2).

[0047] Figure 9 An example scenario 900 is shown, in which the proposed scheme according to this disclosure can be implemented. Scenario 900 relates to an example of secondary primary channel access under the proposed scheme. In scenario 900, a non-AP STA can switch back to the primary channel (e.g., the 20MHz primary channel) from the secondary primary channel (e.g., the 20MHz primary channel) and can start a timer (e.g., the PrimaryChannelSyncDelay timer). The non-AP STA can start the countdown of the timer. The AP associated with the non-AP STA can initiate frame exchange with the non-AP STA on the primary channel (e.g., by sending a DL PPDU to the non-AP STA). The timer can be reset to zero in response to receiving the DL PPDU. After the timer is reset to zero, the non-AP STA can switch back from the primary channel to the secondary primary channel upon detecting an OBSS PPDU or TXOP on the primary channel.

[0048] Figure 10An example scenario 1000 is shown, in which the proposed scheme according to this disclosure can be implemented. Scenario 1000 relates to an example of secondary primary channel access under the proposed scheme. In scenario 1000, a non-AP STA can complete frame exchange with its associated AP on the secondary primary channel (e.g., a 20MHz secondary primary channel) and switch back to the primary channel (e.g., the 20MHz primary channel). The non-AP STA may not start a timer (e.g., a PrimaryChannelSyncDelay timer) (i.e., set the timer to zero), and because the timer value is zero (because the timer is not started), it can switch from the primary channel to the secondary primary channel when an OBSS transmission on the primary channel is detected.

[0049] Figure 11 An example scenario 1100 is shown, in which the proposed scheme according to this disclosure can be implemented. Scenario 1100 relates to an example of secondary primary channel access under the proposed scheme. In scenario 1100, the AP and its associated STA1 and STA2 can participate in downlink multi-user (MU) frame switching on a secondary primary channel (e.g., a 20MHz secondary primary channel). STA1 and STA2 can set their internal basic service set (intra-BSS) NAV based on the Duration field of the MU-RTS frame received from the AP. STA1 and STA2 can switch back to the primary channel (e.g., the 20MHz primary channel) at the end of the TXOP on the secondary primary channel (e.g., when the intra-BSS NAV reaches zero) without starting a timer (e.g., a PrimaryChannelSyncDelay timer). STA1 and STA2 can monitor the primary channel after switching back from the secondary primary channel. STA1 and STA2 can switch back from the primary channel to the secondary primary channel when an OBSS transmission (e.g., a preamble for OBSS PPDU2) is detected on the primary channel.

[0050] Figure 12 An example scenario 1200 is shown, in which the proposed scheme according to this disclosure can be implemented. Scenario 1200 relates to an example of auxiliary primary channel access under the proposed scheme. In scenario 1200, a non-AP STA (in Figure 12The AP (marked "STA1") can monitor the secondary primary channel (e.g., a 20MHz secondary primary channel) and detect the intra-basic service set (intra-BSS) TXOP between its associated AP and a third-party AP (STA2) on the secondary primary channel. STA1 can set its intra-basic service set NAV based on the Duration field of the intra-basic service set TXOP. STA1 can switch back to the primary channel (e.g., the 20MHz primary channel) without starting a timer (e.g., the PrimaryChannelSyncDelay timer) when the intra-basic service set TXOP on the secondary primary channel ends (e.g., when the intra-basic service set NAV reaches zero). STA1 can monitor the primary channel after switching back from the secondary primary channel. STA1 can also switch back from the primary channel to the secondary primary channel when it detects an OBSS transmission on the primary channel (e.g., a preamble to an OBSS PPDU). It is worth noting that the intra-basic service set TXOP may end after STA1's basic NAV on the primary channel.

[0051] Figure 13 An example scenario 1300 is illustrated, in which the proposed scheme according to this disclosure can be implemented. Scenario 1300 relates to an example of a network allocation vector (NAV) mechanism for secondary primary channel access under the proposed scheme. In scenario 1300, an access point (AP) can indicate that it is located on a secondary primary channel (e.g., a 20MHz secondary primary channel) and the duration it will remain on the secondary primary channel. For downlink (DL) transmissions on the secondary primary channel, the AP can initiate a transmission opportunity (TXOP) by sending a request transmission (RTS), multi-user request transmission (MU-RTS), or buffer status request poll (BSRP) with a transmitter address (TA) that is the AP's MAC address and a duration set to the time the AP will remain on the secondary primary channel. A non-AP site (STA) (in Figure 13 The device marked "STA2" may not be the target receiver of the RTS, and it can set its internal basic service set (intra-BSS) NAV on the secondary primary channel based on the RTS transmitted by the AP. STA2's virtual channel sensing (CS) on the primary channel may indicate busy before time point 1.

[0052] Figure 14An example scenario 1400 is illustrated, in which the proposed scheme according to this disclosure can be implemented. Scenario 1400 relates to an example of a network allocation vector (NAV) mechanism for secondary primary channel access under the proposed scheme. In scenario 1400, an AP can indicate that it is located on a secondary primary channel (e.g., a 20MHz secondary primary channel) and the duration it will remain on the secondary primary channel. For uplink (UL) transmissions on the secondary primary channel, the AP can respond to an RTS sent by STA1 on the secondary primary channel by sending a spontaneous acknowledgment frame (CTS-to-SELF). The CTS-to-SELF frame can carry the receiver address (RA) as the AP's own MAC address. The AP can set the value of the Duration field of the CTS-to-SELF frame based on: (i) the setting rules for the response frame (e.g., the Duration field based on the RTS), or (ii) the expected duration of the AP's stay on the secondary primary channel (e.g., based on the AP's basic NAV on the primary channel). STA2 may not be the target receiver of the RTS, and it can set its internal Basic Service Set (intra-BSS) NAV on the secondary primary channel based on the CTS-to-SELF frames transmitted by the AP. STA2's virtual channel awareness (CS) on the primary channel may indicate busy status before time point 1.

[0053] Figure 15 An example scenario 1500 is illustrated, in which the proposed scheme according to this disclosure can be implemented. Scenario 1500 relates to an example of a network allocation vector (NAV) mechanism for auxiliary primary channel access under the proposed scheme. In scenario 1500, if STA2 returns to the primary channel (e.g., a 20MHz primary channel) after the basic NAV end time on its primary channel, STA2 may be considered to be in a "medium synchronization lost" state on the primary channel. Figure 15 Part (A) shows an example case where STA2 sets its internal basic service set (intra-BSS) NAV at the end of the RTS frame. Figure 15 Section (B) shows an example scenario where STA2 sets its intra-BSS NAV at the end of a CTS-to-SELF frame. In both cases, STA2 may perform medium synchronization recovery at time 1 to exit the "medium synchronization lost" state.

[0054] Example Implementation

[0055] Figure 16An example system 1600 is described, having at least one example device 1610 and one example device 1620, consistent with an embodiment of this disclosure. Each of devices 1610 and 1620 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to auxiliary master channel access mechanisms in wireless communications, including the schemes described above related to various proposed designs, concepts, schemes, systems, and methods, as well as the processes described below. For example, device 1610 may be implemented in a non-AP site (STA) (e.g., STA 110), while device 1620 may be implemented in an access point (AP) (e.g., STA 120).

[0056] Each of devices 1610 and 1620 can be part of an electronic device, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. When implemented in a STA, each of devices 1610 and 1620 can be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device (e.g., tablet, laptop, or notebook computer). Each of devices 1610 and 1620 can also be part of a machine-type device, which can be an Internet of Things (IoT) device, such as a non-movable or fixed device, a home appliance, a wired communication device, or a computing device. For example, each of devices 1610 and 1620 can be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, devices 1610 and / or 1620 can be implemented in a network node, such as an access point (AP) or mesh device in a WLAN.

[0057] In some embodiments, each device 1610 and device 1620 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. In the various embodiments described above, each device 1610 and device 1620 may be implemented in a station (STA) or access point (AP) or as a STA or AP. Each device 1610 and device 1620 may include... Figure 16At least some of the components shown are, for example, processors 1612 and 1622. Each device 1610 and device 1620 may also include one or more other components unrelated to the scheme of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for simplicity and brevity, these components are not listed. Figure 16 This is shown in the text and not described in the following text.

[0058] In one aspect, each processor 1612 and processor 1622 may be implemented as one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processor 1612 and processor 1622, each processor 1612 and processor 1622 may include multiple processors in some embodiments and a single processor in other embodiments, according to the present disclosure. In another aspect, each processor 1612 and processor 1622 may be implemented in hardware (and optionally firmware) and include electronic components, such as, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, which are configured and arranged to achieve a specific purpose according to the present disclosure. In other words, in at least some embodiments, each processor 1612 and processor 1622 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to auxiliary master channel access mechanisms in wireless communications according to various embodiments of the present disclosure.

[0059] In some embodiments, device 1610 may further include a transceiver 1616 coupled to processor 1612. Transceiver 1616 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. In some embodiments, device 1620 may further include a transceiver 1626 coupled to processor 1622. Transceiver 1626 may include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. It is worth noting that although transceiver 1616 and transceiver 1626 are shown as external and independent components of processor 1612 and processor 1622, respectively, in some embodiments, transceiver 1616 may be an integral part of processor 1612 as a system on chip (SoC), and transceiver 1626 may be an integral part of processor 1622 as a SoC.

[0060] In some embodiments, device 1610 may further include a memory 1614 coupled to processor 1612, which can be accessed by processor 1612 and stores data. In some embodiments, device 1620 may further include a memory 1624 coupled to processor 1622, which can be accessed by processor 1622 and stores data. Each of memory 1614 and memory 1624 may include a random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, each of memories 1614 and 1624 may further include a read-only memory (ROM), such as a mask ROM, a programmable ROM (PROM), an erasable programmable ROM (EPROM), and / or an electrically erasable programmable ROM (EEPROM). Optionally or additionally, each of memories 1614 and 1624 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0061] Each device 1610 and device 1620 can be a communication entity capable of communicating using various schemes according to this disclosure. For illustrative purposes and not to be limited thereto, the following description of the capabilities of device 1610 or device 1620 as a STA (e.g., STA 102, 104, 106) or AP (e.g., AP 108) is provided in the context of example flows 1700 and 1800. It is worth noting that although a detailed description of the capabilities, functions, and / or technical features of device 1610 and device 1620 is provided below, these contents also apply to the other party of device 1610 and device 1620, although a detailed description is not provided for the sake of brevity. Furthermore, it is worth noting that although the following example embodiments are provided in the context of a wireless local area network (WLAN), these contents can also be implemented in other types of networks.

[0062] Example Process

[0063] Figure 17 An example process 1700 according to an embodiment of this disclosure is illustrated. Process 1700 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 1700 may represent one aspect of proposed concepts and schemes related to auxiliary master channel access mechanisms in wireless communication. Process 1700 may include one or more operations, actions, or functions, as shown in one or more blocks 1710 and 1720. Although illustrated as discrete blocks, the individual blocks of process 1700 may be divided into more blocks, merged into fewer blocks, or omitted, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 1700 may be arranged according to... Figure 17 The process can be executed in the order shown, or in a different order. Furthermore, one or more blocks / sub-blocks of process 1700 can be executed repeatedly or iteratively. Process 1700 can be implemented by or in devices 1610 and 1620, and any variations thereof. For illustrative purposes only and without limitation, process 1700 is described below in the context of device 1610 as a non-AP STA (e.g., STA 110) in a wireless network (e.g., WLAN) in a network environment 100 conforming to one or more IEEE 802.11 standards, and device 1620 as an AP (e.g., STA 120) in a wireless network (e.g., WLAN) in a network environment 100 conforming to one or more IEEE 802.11 standards. Process 1700 may begin at block 1710.

[0064] At 1710, process 1700 may involve the processor 1612 of device 1610, acting as a non-AP STA (e.g., STA 110), detecting OBSS transmissions on the main channel via transceiver 1616. Process 1700 can proceed from 1710 to 1720.

[0065] At 1720, process 1700 may involve processor 1612 switching to the secondary main channel via transceiver 1616 in response to the detection of OBSS transmission on the main channel.

[0066] In some embodiments, if the intra-BSS NAV counter in device 1610 is not zero, process 1700 may also involve processor 1612 remaining on the primary channel without switching to the secondary primary channel in response to detecting an OBSS transmission on the primary channel.

[0067] In some embodiments, process 1700 may involve processor 1612 performing additional operations. For example, process 1700 may involve processor 1612 detecting, via transceiver 1616, physical layer protocol data units (PPDUs) transmitted by or to an associated AP (e.g., device 1620 as STA 120), the PPDU residing on the secondary primary channel. Furthermore, process 1700 may involve processor 1612 setting an intra-BSS NAV based on the detected PPDU.

[0068] In some embodiments, process 1700 may also involve processor 1612 returning from the secondary primary channel to the primary channel via transceiver 1616 in response to the occurrence of a predefined event. In some embodiments, the predefined event may include one of the following: (a) the internal basic service set (intra-BSS) NAV counter of device 1610 has been set and counted down to zero; (b) device 1610 has participated in a TXOP on the secondary primary channel and the TXOP has ended; (c) in the absence of participation in a TXOP on the secondary primary channel, the value of the basic NAV counter of device 1610 is less than or equal to a threshold; (d) the maximum number of retries to initiate frame switching on the secondary primary channel has been reached; (e) device 1610 receives another OBSS transmission on the secondary primary channel, the end time of which is later than the threshold time prior to the end time of the basic NAV of device 1610 on the primary channel; and (f) device 1610 receives a notification from an associated AP (e.g., device 1620) instructing the associated AP to return to the primary channel. In some embodiments, the threshold may be equal to or greater than zero. In some embodiments, the threshold time may be equal to or greater than zero.

[0069] In some embodiments, process 1700 may additionally involve processor 1612, via transceiver 1616, switching to access the secondary primary channel in response to detecting OBSS transmissions on the primary channel after determining that the associated AP (e.g., device 1620) has returned to the primary channel.

[0070] In some embodiments, process 1700 may further involve processor 1612 starting a timer (e.g., a PrimaryChannelSyncDelay timer) upon returning to the primary channel. In some embodiments, the timer may be reset to zero during a countdown if a PPDU is detected being transmitted by the associated AP on the primary channel. In some embodiments, a zero value for the timer may be equivalent to determining that the associated AP (e.g., device 1620) has returned to the primary channel by detecting a PPDU transmitted by the associated AP on the primary channel.

[0071] Figure 18 An example process 1800 according to an embodiment of this disclosure is illustrated. Process 1800 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 1800 may represent one aspect of proposed concepts and schemes related to auxiliary master channel access mechanisms in wireless communication. Process 1800 may include one or more operations, actions, or functions as shown in Figures 1810 and 1820. Although shown as discrete blocks, the individual blocks of process 1800 may be divided into more blocks, merged into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 1800 may be arranged according to... Figure 18 The process can be executed in the sequence shown, or in a different order. Furthermore, one or more blocks / sub-blocks of process 1800 can be executed repeatedly or iteratively. Process 1800 can be implemented by or in devices 910 and 920, and any variations thereof. For illustrative purposes only and without limitation, process 1800 is described below in the context of device 1610 as a non-AP STA (e.g., STA 110) in a wireless network (e.g., WLAN) in a network environment 100 conforming to one or more IEEE 802.11 standards, and device 1620 as an AP (e.g., STA 120) in a wireless network (e.g., WLAN) in a network environment 100 conforming to one or more IEEE 802.11 standards. Process 1800 may begin at block 1810.

[0072] At 1810, process 1800 may involve the processor 1622 of device 1620, acting as an AP (e.g., STA 120), detecting OBSS transmissions on the main channel via transceiver 1626. Process 1800 can proceed from 1810 to 1820.

[0073] At 1820, process 1800 may involve processor 1622 switching to a secondary primary channel via transceiver 1626 in response to detection. The secondary primary channel may be aligned with one or more STAs associated with device 1620 that have secondary primary channel access capability (e.g., device 1610 included in STA 110 as a non-AP STA).

[0074] In some embodiments, process 1800 may involve processor 1622 performing additional operations. For example, process 1800 may involve processor 1622 performing one or more frame exchanges on a secondary primary channel via transceiver 1626.

[0075] In some embodiments, process 1800 may involve processor 1622 returning from the secondary master channel to the master channel via transceiver 1626 in response to the occurrence of a predefined event. In some embodiments, the predefined event may include one of the following: (a) the value of the basic NAV counter on the master channel is less than or equal to a threshold when the AP is not participating in a TXOP on the secondary master channel; (b) device 1620 sends a notification instructing device 1620 to return to the master channel; and (c) another OBSS transmission is detected on the secondary master channel, the end time of which is later than a threshold time prior to the end time of the basic NAV on the master channel. In some embodiments, the threshold may be equal to or greater than zero. In some embodiments, the threshold time may be equal to or greater than zero.

[0076] In some embodiments, process 1800 may also involve processor 1622 switching to accessing the secondary primary channel in response to detecting an OBSS transmission on the primary channel after transmitting a PPDU via transceiver 1626 on the primary channel. In some embodiments, process 1800 may further involve processor 1622 transmitting a control frame via transceiver 1626 to indicate the presence of (device 1620) on the primary channel.

[0077] In some embodiments, process 1800 may further involve processor 1622 starting a timer (e.g., a PrimaryChannelSyncDelay timer) upon returning to the primary channel. In some embodiments, the timer may be reset to zero during a countdown if device 1620 transmits a PPDU on the primary channel. In some embodiments, a zero value for the timer may be equivalent to the AP transmitting a PPDU on the primary channel.

[0078] Additional notes

[0079] The topics described herein sometimes demonstrate different components contained within or connected to other components. It should be understood that these illustrated architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” with each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” with each other to achieve the desired function. Specific examples of operational coupling include, but are not limited to, physically connectable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0080] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, a person with technical skills may appropriately translate from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed in this document.

[0081] Furthermore, those skilled in the art will understand that, in general, the terms used herein, particularly in appended claims, such as the body of an appended claim, are often considered "open" terms; for example, the word "comprising" should be interpreted as "comprising but not limited to," the word "having" should be interpreted as "having at least," and the word "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also understand that if a particular quantity is intentionally introduced in a claim, that intention will be explicitly stated in the claim; if no such statement is given, then no such intention exists. For example, to aid understanding, the appended claims below may contain statements introducing the claim using the introductory phrases "at least one" and "one or more." However, the use of these phrases should not be construed as implying that a claim statement introduced by the indefinite article "a" or "an" limits any particular claim containing such an introductory claim statement to containing only one such statement, even if the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to definite articles used to introduce claim statements. Furthermore, even when a specific number of claims is explicitly stated, those skilled in the art will recognize that such statements should be interpreted as at least the stated number. For example, the single statement "two statements," without any other modifier, means at least two statements, or two or more statements. Additionally, when using conventions such as "at least one A, B, and C, etc.", generally, such a structure is understood by those skilled in the art to mean the convention. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or systems having A, B, and C together, etc. Similarly, when using conventions such as "at least one A, B, or C, etc.", generally, such a structure is understood by those skilled in the art to mean the convention. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or systems having A, B, and C together, etc. Those skilled in the art will also understand that virtually any extractive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to include the possibility of containing one term, either term, or both terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

[0082] As can be understood from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and their true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: The station's processor detects overlapping basic service set transmissions on the main channel; as well as In response to the detection of the overlapping basic service set transmission on the primary channel, the processor switches to the secondary primary channel.

2. The method of claim 1, further comprising, when the internal basic service set network allocation vector counter in the site is not zero: In response to the detection of the overlapping basic service set transmission on the primary channel, the processor remains on the primary channel without switching to the secondary primary channel.

3. The method of claim 2, further comprising: The processor detects physical layer protocol data units sent by or to the associated access point on the auxiliary main channel. as well as The processor sets the internal basic service set network allocation vector counter based on the detected physical layer protocol data unit.

4. The method of claim 1, further comprising: The processor responds to the occurrence of a predefined event and returns from the secondary master channel to the master channel.

5. The method of claim 4, wherein the predefined event includes one of the following: (a) The site’s internal basic service set network allocation vector counter has been set and counted down to zero; (b) The site has participated in a transmission opportunity on the secondary primary channel, and that transmission opportunity has ended; (c) If the site does not participate in the transmission opportunity on the secondary primary channel, the value of the basic network allocation vector counter is less than or equal to the threshold. (d) The maximum number of retries to initiate frame switching on the auxiliary primary channel has been reached; (e) The station receives another overlapping basic service set transmission on the secondary primary channel, the physical layer protocol data unit or transmission opportunity of the other overlapping basic service set transmission having an end time later than a threshold time before the end time of the basic network allocation vector of the station on the primary channel. as well as (f) The station receives a notification from the associated access point instructing the associated access point to return to the main channel.

6. The method of claim 4, further comprising: After determining that the associated access point has returned to the primary channel, the processor switches to the secondary primary channel in response to detecting the overlapping basic service set transmission on the primary channel.

7. The method of claim 4, further comprising: The processor starts a timer upon returning to the main channel.

8. The method of claim 7, wherein if the physical layer protocol data unit is detected to be transmitted by the associated access point on the main channel, the timer is reset to zero during the countdown.

9. The method of claim 7, wherein a zero value of the timer is equivalent to determining that the associated access point has returned to the main channel.

10. A method comprising: The processor at the access point detects the transmission of overlapping basic service sets on the main channel; as well as The processor switches to the secondary main channel in response to the detection. The secondary primary channel is aligned with one or more sites associated with the access point that have secondary primary channel access capabilities.

11. The method of claim 10, further comprising: The processor responds to the occurrence of a predefined event and returns from the secondary master channel to the master channel.

12. The method of claim 11, wherein the predefined event includes one of the following: (a) If the access point does not participate in the transmission opportunity on the secondary primary channel, the value of the basic network allocation vector counter on the primary channel is less than or equal to the threshold. (b) The access point sends a notification instructing it to return to the main channel; and (c) Another overlapping basic service set transmission is detected on the secondary primary channel, the physical layer protocol data unit or transmission opportunity of the other overlapping basic service set transmission having an end time later than a threshold time prior to the end time of the basic network allocation on the primary channel.

13. The method of claim 11, further comprising: After sending physical layer protocol data units to the primary channel, the processor switches to accessing the secondary primary channel in response to detecting the overlapping basic service set transmission on the primary channel.

14. The method of claim 13, further comprising: The processor sends control frames to indicate its presence on the main channel.

15. The method of claim 11, further comprising: The processor starts a timer when returning to the main channel.

16. The method of claim 15, wherein if the access point transmits a physical layer protocol data unit on the main channel, the timer is reset to zero during the countdown.

17. The method of claim 15, wherein a zero value of the timer is equivalent to the access point transmitting a physical layer protocol data unit on the main channel.

18. An apparatus comprising: A transceiver; and A processor, coupled to the transceiver and configured to perform operations via the transceiver, including: Detect overlapping basic service set transmissions on the main channel; and In response to the detection of the overlapping basic service set transmission on the primary channel, switch to the secondary primary channel.

19. The apparatus of claim 18, wherein, If the internal basic service set network allocation vector counter in the site is not zero, the processor is further configured to perform operations, including: In response to the detection of the overlapping basic service set transmission on the primary channel, remain on the primary channel without switching to the secondary primary channel.

20. The apparatus of claim 19, wherein the processor is further configured to perform operations including: Detect physical layer protocol data units sent or received by the associated access point on the secondary primary channel; and The internal basic service set network allocation vector counter is set based on the detected physical layer protocol data unit.

Images