Access point that facilitates scheduling of communications for interference-sensitive communication devices

Abstract

To provide an access point capable of including a circuit and a transmitter.SOLUTION: The circuit is capable of reserving a subset of the operating frequency bandwidth for a group of communication devices that are susceptible to interference when operating within their operating frequency bandwidth, and capable of scheduling communication related to at least one communication device in the group of communication devices based on a reserved subset of the operating frequency bandwidth. The transmitter is capable of transmitting information about the reserved subset of the operating frequency bandwidth when operating.SELECTED DRAWING: Figure 5a

Description

[Technical Field]

[0001] The present disclosure generally relates to at least one access point (AP) that facilitates communications associated with one or more communication devices that are susceptible to interference. The present disclosure further relates to communication methods associated with the AP(s). [Background technology]

[0002] In general, it is not unexpected for interference to occur within a communication system, and when interference occurs, the integrity of communications in the communication system can be adversely affected.

[0003] Solutions have been devised to mitigate interference and restore communication integrity within communication systems.

[0004] This disclosure recognizes the need for alternative solutions to mitigate interference. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] IEEE 802.11REVmd_D2.0 [Non-patent document 2] IETF RFC 6225 (Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information) Summary of the Invention [Problem to be solved by the invention]

[0006] SUMMARY OF THE INVENTION Non-limiting exemplary embodiments facilitate scheduling of communication devices for the purpose of interference mitigation. [Means for solving the problem]

[0007] In one embodiment, the disclosed technology features an access point (AP).

[0008] The AP may include circuitry that, in operation, reserving a subset of the operating frequency bandwidth for a group of communications devices that are susceptible to interference when operating within the operating frequency bandwidth; and Scheduling communications associated with at least one communication device in the group of communication devices based on a reserved subset of the operating frequency bandwidth.

[0009] The AP may further include a transmitter that, when operational, transmits information on the reserved subset of the operating frequency bandwidth.

[0010] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any combination thereof.

[0011] Further benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. These benefits and / or advantages may be obtained individually by the various embodiments and features of the specification and drawings, and it is not necessary for all of these features to be present in order to obtain one or more of such benefits and / or advantages. [Brief explanation of the drawings]

[0012] An embodiment of the present disclosure will now be described with reference to the following drawings. [Figure 1] FIG. 1 illustrates a system that may include at least one access point (AP) and at least one communication device, according to one embodiment of the present disclosure. [Figure 2a] FIG. 2 illustrates various communications within the system of FIG. 1 that may cause interference, according to one embodiment of the present disclosure. [Figure 2b]FIG. 2 illustrates various communications within the system of FIG. 1 that may cause interference, according to one embodiment of the present disclosure. [Figure 2c] FIG. 2 illustrates various communications within the system of FIG. 1 that may cause interference, according to one embodiment of the present disclosure. [Figure 3a] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 3b] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 4a] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 4b] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 4c] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 5a] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 5b] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 5c] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 5d] FIG. 2 illustrates scheduling based on a first exemplary scenario associated with the system of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 6] FIG. 2 illustrates scheduling based on a second exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 7] FIG. 2 illustrates scheduling based on a second exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8a] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8b] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8c] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8d] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8e] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8f] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8g] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8h] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 8i] FIG. 2 illustrates scheduling based on a third exemplary scenario associated with the system of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 9] FIG. 8 illustrates device location information elements associated with the third example scenario of FIGS. 8a-8i, according to one embodiment of the present disclosure. [Figure 10] FIG. 2 illustrates the access point (AP) of FIG. 1 in further detail, according to one embodiment of the present disclosure. [Figure 11] FIG. 2 illustrates the communication device of FIG. 1 in further detail, according to one embodiment of the present disclosure. [Figure 12] FIG. 2 illustrates a communication method associated with the system of FIG. 1 according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] The present disclosure believes that it would be useful to facilitate scheduling of communication device(s) within a system (i.e., a communication system) that is susceptible to interference, e.g., in one or both of the frequency and / or time domains, while avoiding the need for strict synchronization between APs, which may lead to complications as discussed above with respect to conventional solutions.

[0014] In order to facilitate scheduling in a manner that avoids the need for strict synchronization between APs, this disclosure believes that it is generally useful to identify one or more (i.e., any one or any combination) of the following: Information Shared At least one communication device in the system that is susceptible to interference One or more factors / conditions related to the interference (location of the interference, cause / source of the interference)

[0015] The above will be described in more detail below with reference to FIGS.

[0016] 1 illustrates a system 100 according to one embodiment of the present disclosure. The system 100 may correspond to a communication system suitable for, for example, IEEE 802.11-based communication.

[0017] In the context of technologies related to IEEE 802.11 (Wi-Fi) based communications, a station (also synonymously referred to as a STA) is a communication-type device (i.e., a communications device) capable of using the 802.11 protocol. Based on the definition in IEEE 802.11-2016, a STA can be any device that includes an IEEE 802.11-compliant medium access control (MAC) and physical layer (PHY) interface to the wireless medium (WM).

[0018] For example, the STA may be a notebook, a desktop personal computer (PC), a personal digital assistant (PDA), an access point (AP), or a Wi-Fi phone in a wireless local area network (WLAN) environment. The STA may be fixed or mobile.

[0019] An access point (AP), also known synonymously as a wireless access point (WAP) in IEEE 802.11 (Wi-Fi) technology, is a communications device that allows STAs other than APs (non-AP STAs) in a WLAN to connect to the wired network (also known as the distribution system). APs are typically connected to a router (through the wired network) as standalone devices, but can also be integrated with or used within a router.

[0020] Non-AP STAs are simpler devices that rely on APs to communicate with the distribution system, and for simplicity, will be referred to hereinafter simply as STAs.

[0021] 1, the system 100 may include one or more basic service sets (i.e., BSSs) 102, one or more access points (i.e., APs) 104, and one or more communication devices 106. Generally, the APs 104 and the communication devices 106 may be associated with a base station subsystem 102. The communication devices 106 may correspond to one or more STAs, for example.

[0022] In one embodiment, the BSS(s) 102 may include a first basic service set (BSS) 102a (also referred to as "BSS1" in FIG. 1) and a second basic service set (BSS) 102b (also referred to as "BSS2" in FIG. 1). The AP(s) 104 may include a first AP 104a (e.g., also referred to as "AP1" in FIG. 1) and a second AP 104b (e.g., also referred to as "AP2" in FIG. 1). The communication device(s) 106 may include a first communication device / first set of communication devices 106a and a second communication device / second set of communication devices 106b. In one example, the communication device(s) 106 may include a first set / group of communication devices 106a (e.g., first set / group of STAs) and a second set / group of communication devices 106b (e.g., second set / group of STAs).

[0023] The first BSS 102a may be associated with a first operating frequency bandwidth. Based on the coverage range of the first operating frequency bandwidth, the first BSS 102a may be associated with a first operating region 108.

[0024] The second BSS 102b may be associated with a second operating frequency bandwidth. Based on the coverage area of ​​the second operating frequency bandwidth, the second BSS 102b may be associated with a second operating region 110.

[0025] According to various embodiments of the present disclosure, an overlap region 112 may be formed associated with the first BSS 102a and the second BSS 102b, as described in more detail below. Additionally, in one embodiment, one or more resource units (RUs) may be reserved associated with the first operating frequency bandwidth (i.e., corresponding to the reserved resource unit set(s) 114 associated with BSS1), as described in more detail below with reference to Figures 3-5. Additionally, in one embodiment, one or more resource units may be reserved associated with the second operating frequency bandwidth (i.e., corresponding to the reserved resource unit set(s) 116 associated with BSS2), as described in more detail below with reference to Figures 3-5.

[0026] The first AP 104a may be used or suitable for use in combination with the first BSS 102a. Specifically, the first AP 104a may be associated with the first BSS 102a. More specifically, the first AP 104a may be configured to transmit and / or receive data / information, for example, in association with the first BSS 102a.

[0027] The second AP 104b may be used or suitable for use in combination with the second BSS 102b. Specifically, the second AP 104b may be associated with the second BSS 102b. More specifically, the second AP 104b may be configured to transmit and / or receive data / information, for example, in association with the second BSS 102b.

[0028] The present disclosure contemplates that, according to one embodiment of the present disclosure, the first AP 104a and the second AP 104b may be similar in functionality and / or hardware structure. The AP(s) 104 (e.g., the first AP 104a and / or the second AP 104b) according to one embodiment of the present disclosure are described in further detail below with reference to FIG.

[0029] A first set of communication devices 106a may be located / located within a first operating region 108. Specifically, the first set of communication devices 106a may be configured to communicate with, for example, a first AP 104a.

[0030] A second set of communication devices 106b may be disposed / located within the second operating region 110. Specifically, the second set of communication devices 106b may be configured to communicate with, for example, a second AP 104b.

[0031] As previously described, a first operating region 108 may be associated with the first BSS 102a based on the coverage range of the first operating frequency bandwidth, and a second operating region 110 may be associated with the second BSS 102b based on the coverage range of the second operating frequency bandwidth. Additionally, as previously described, an overlap region 112 may be formed in association with the first BSS 102a and the second BSS 102b.

[0032] This disclosure contemplates the possibility that a first BSS 102a may be adjacent (e.g., in terms of location / position) to a second BSS 102b such that a portion of a first operating region 108 overlaps a portion of a second operating region 110, such that an overlap region 112 may be defined. The overlap region 112 may, according to one embodiment of the present disclosure, indicate / represent overlapping basic service set (OBSS)-based interference. Careful planning of operating frequencies, i.e., operating channels, may help reduce interference between neighboring BSSs. However, due to their distributed nature, avoiding inter-BSS interference is difficult, especially in unmanaged networks or when the operating bandwidth is wide (e.g., 160 MHz or 320 MHz), despite the lack of non-overlapping wideband channels.

[0033] Furthermore, the first active region 108 may include a base region 108a and a fringe region 108b. The first AP 104a may be located / disposed within the base region 108a, and the fringe region 108b may substantially surround the base region 108a. The fringe region 108b may, for example, define an end region of the first active region 108. In this regard, the fringe region 108b may correspond to a peripheral region of the first active region 108. The base region 108a and the fringe region 108b of the first active region 108 may also be referred to as a "first base region" and a "first fringe region," respectively. The base region may also be referred to as a cell center region, and the fringe region may also be referred to as a cell edge region.

[0034] Similarly, the second active region 110 may include a base region 110a and a fringe region 110b. The second AP 104b may be located / disposed within the base region 110a, and the fringe region 110b may substantially surround the base region 110a. The fringe region 110b may, for example, define an end region of the second active region 110. In this regard, the fringe region 110b may correspond to a peripheral region of the second active region 110. The base region 110a and the fringe region 110b of the second active region 110 may also be referred to as a "second base region" and a "second fringe region," respectively.

[0035] Furthermore, in one embodiment, the operating area(s) (i.e., the first operating area 108 and / or the second operating area 110) may be segmented into multiple regions / zones, as described in more detail below with reference to FIG. 8.

[0036] As shown, one or more communication devices of the first set of communication devices 106a (e.g., labeled "STA2" and "STA4" in FIG. 1) may be located / disposed within the first fringe region 108b, and one or more communication devices of the second set of communication devices 106b (e.g., labeled "STA1" and "STA3" in FIG. 1) may be located / disposed within the second fringe region 110b. In general, communication devices (e.g., STA1, STA2, STA3, and / or STA4) located / disposed within the fringe regions (i.e., the first fringe region 108b and / or the second fringe region 110b) may be considered cell-edge type devices, while communication devices located / disposed within the base regions (i.e., the first base region 108a and / or the second base region 110a) may be considered cell-center type devices.

[0037] Classification of STAs as belonging to the base (cell-center) region or the fringe (cell-edge) region may be based on measurements of parameters such as channel propagation loss, RSSI (Received Signal Strength Indicator) or SINR (Signal to Interference plus Noise Ratio), or any combination thereof. For example, an associated STA (e.g., STA3) determined by an AP (e.g., AP2) to experience a propagation loss of more than 65 decibels (dB) may accordingly be determined by the AP (e.g., AP2) to be a cell-edge-type device (i.e., a cell-edge STA). Conversely, an associated STA determined by the AP to experience a propagation loss of less than 65 decibels (dB) may be determined by the AP to be a cell-center-type device.

[0038] According to one embodiment of the present disclosure, cell-edge type devices (e.g., STA2, STA3) located / placed within overlap region 112 are susceptible to interference, whereas cell-edge type devices (e.g., STA1, STA4) located / placed outside of overlap region 112 are substantially less susceptible to interference. Cell-edge type devices (e.g., STA2, STA3) that are susceptible to interference can be considered vulnerable cell-edge type devices (i.e., vulnerable STAs), while cell-edge type devices (e.g., STA1, STA4) that are less susceptible to interference (i.e., have minimal or no interference) can be considered non-vulnerable cell-edge type devices (i.e., non-vulnerable STAs).

[0039] In one embodiment, the present disclosure contemplates that interference may occur due to a cell-edge type device (e.g., STA2) in an operating area (e.g., first operating area 108) engaging in communications (e.g., uplink and / or downlink type communications) associated with an adjacent operating area (e.g., communications from AP2 located / disposed in second operating area 110), as will be described in more detail below with reference to FIG.

[0040] It will be appreciated that vulnerable STAs are typically located within the overlap region 112. Communication integrity can be an issue for vulnerable STAs, e.g., miscommunications can occur at vulnerable STAs due to interference.

[0041] It is further understood that, according to one embodiment of the present disclosure, vulnerable STAs may in some cases be located outside of the overlap region 112 (e.g., in the base region 108a / 110a) but still experience interference (e.g., OBSS-based interference), as will be explained in more detail below with reference to FIG. 4a.

[0042] In this regard, the present disclosure recognizes the need to be able to substantially maintain the integrity of communications for vulnerable STAs, and further recognizes that scheduling can be useful in this regard.

[0043] Specifically, the present disclosure contemplates that it would be useful to facilitate scheduling from the perspective of vulnerable STAs. Further, the present disclosure contemplates that scheduling can be facilitated in a manner that avoids the need for strict synchronization between APs. According to one embodiment of the present disclosure, scheduling may be performed in conjunction with AP(s) 104 (e.g., AP1 and AP2).

[0044] To facilitate scheduling, this disclosure believes it is useful to identify one or more (ie, any one or any combination) of the following: Information to be shared. In one example, information related to transmission data / information associated with vulnerable STAs may be shared between AP1 and AP2. In another example, information related to the allocation of one or more reserved resource units may be shared between AP1 and AP2. In yet another example, information related to the transmission timing of AP1 and AP2 may be shared between AP1 and AP2. In yet another example, information related to the transmit power associated with each of AP1 and AP2 may be shared between AP1 and AP2. In yet an additional example, beamforming information associated with each of AP1 and AP2 may be shared between AP1 and AP2. Identifying one or more communication devices in the system 100 that are susceptible to interference (i.e., vulnerable STAs). For example, STA2 and STA3 may be identified (e.g., by one or more APs) as vulnerable STAs. One or more factors / conditions associated with the interference (e.g., location, cause / source of interference). In one example, related to location, the overlap region 112 described above may be identified. In another example, related to interference source, it may be determined whether communications related to AP2 are causing interference to STA2 and / or whether communications related to STA2 are causing interference to STA3.

[0045] Scheduling is described in further detail below with reference to a first exemplary scenario, a second exemplary scenario, and a third exemplary scenario, according to various embodiments of the present disclosure.

[0046] As previously mentioned, the present disclosure contemplates that interference may occur due to a cell-edge type device (e.g., STA2) in an operating area (e.g., first operating area 108) engaging in communications (e.g., uplink and / or downlink type communications) associated with an adjacent operating area (e.g., communications from AP2 located / disposed in second operating area 110). This is explained in more detail below with reference to Figure 2 (i.e., Figures 2a-2c).

[0047] 2a, 2b, and 2c, STA2 and STA3 can be considered to be located at the boundary between BSS1 and BSS2. Specifically, overlap region 112 can indicate the boundary between BSS1 and BSS2. STA2 and STA3 can be classified as cell-edge type STAs by BSS1 and BSS2, respectively. Specifically, STA2 and STA3 can be classified as vulnerable cell-edge type devices by BSS1 and BSS2, respectively, in one example. In another example, an AP (e.g., AP1 and / or AP2) can classify an associated STA (e.g., STA2 and / or STA3) as a vulnerable cell-edge type device (i.e., a vulnerable STA). The STAs can be classified as vulnerable cell-edge type devices (i.e., vulnerable STAs) based on channel propagation loss, RSSI (Received Signal Strength Indicator), SINR (Signal-to-Interference-Plus-Noise Ratio), or any combination thereof. For example, a STA (e.g., STA3) determined by an AP (e.g., AP2) to experience a propagation loss of more than 65 decibels (dB) may be determined by the AP (e.g., AP2) to be a vulnerable cell edge type device (i.e., a vulnerable STA) accordingly.

[0048] 2a further illustrates that downlink (DL) transmissions 202a / 202b may cause interference within the overlap region 112. In one example, a DL transmission 202a from AP1 to STA2 may cause interference to STA3. In another example, another DL transmission 202b from AP2 to STA3 may cause interference to STA2.

[0049] 2b further illustrates that uplink (UL) transmissions 204 may cause interference within the overlap region 112. For example, UL transmission 204 from STA2 to AP1 may cause interference to STA3. In most cases, UL transmissions from cell-edge type devices use high transmit power due to the relatively large distance from the AP, and as a result, UL transmissions have a higher interference potential compared to DL transmissions.

[0050] Furthermore, FIG. 2c illustrates that not all cell-edge type devices are equally susceptible to interference. As illustrated, STA1 and STA4 are considered cell-edge type devices, but STA1 and STA4 are outside the overlap region 112 and are not particularly susceptible to interference. Specifically, communications associated with cell-edge type devices (e.g., STA1, STA4) that are far from one another may cause minimal, negligible, or no interference to one another. In one example, DL transmission 206a and UL transmission 208a between AP2 and STA1 cause minimal, negligible, or no interference to STA4. In another example, DL transmission 206b and UL transmission 208b between AP1 and STA4 cause minimal, negligible, or no interference to STA1. In this regard, STA1 and STA4 may be examples of the non-vulnerable STAs discussed above.

[0051] Scheduling will now be described with reference to a first exemplary scenario according to one embodiment of the present disclosure.

[0052] In a first exemplary scenario, as described with reference to Figures 3-5, scheduling may occur in a situation where information related to the allocation of one or more reserved resource units may be shared between APs (e.g., AP1 and AP2). In this regard, the first exemplary scenario may relate to frequency-domain based scheduling.

[0053] Specifically, in a first exemplary scenario, the AP(s) 104 (i.e., one or both of the first AP 104a and the second AP 104b) may be configured to reserve a subset of the operating frequency bandwidth (i.e., one or both of the first operating frequency bandwidth and the second operating frequency bandwidth).

[0054] For example, the first AP 104a (i.e., “AP1”) may be configured to reserve at least one subset of a first operating frequency bandwidth. The reserved subset of the first operating frequency bandwidth may correspond to at least one resource unit that can be considered to correspond to at least one reserved resource unit associated with the first operating frequency bandwidth. Specifically, the reserved subset of the first operating frequency bandwidth may correspond to at least one reserved resource unit associated with the first operating frequency bandwidth. The reserved resource unit associated with the first operating frequency bandwidth may be used, for example, for one or more vulnerable STAs (e.g., STA2) that are susceptible to interference when operating within the first operating frequency bandwidth. The reserved resource unit set(s) 114 associated with the first operating frequency bandwidth (i.e., associated with BSS1) may also be referred to as a BSS1 reserved resource unit set 114 or a cell-edge resource unit set. On the other hand, in one embodiment, for example, non-vulnerable STAs (e.g., STAs located / located within the first base region 108a) may be assigned any resource units associated with the first operating frequency bandwidth.

[0055] Similarly, the second AP 104b (i.e., “AP2”) may be configured to reserve, for example, at least one subset of the second operating frequency bandwidth. The reserved subset of the second operating frequency bandwidth may correspond to at least one resource unit that can be considered to correspond to at least one reserved resource unit associated with the second operating frequency bandwidth. Specifically, the reserved subset of the second operating frequency bandwidth may correspond to at least one reserved resource unit associated with the second operating frequency bandwidth. The reserved resource unit set 116 associated with the second operating frequency bandwidth (i.e., associated with BSS2) may be used, for example, for one or more vulnerable STAs (e.g., STA3) that are susceptible to interference when operating within the second operating frequency bandwidth. The reserved resource unit set(s) 116 associated with the second operating frequency bandwidth (i.e., associated with BSS2) may also be referred to as a BSS2 reserved resource unit set 116 or a cell-edge resource unit set. On the other hand, in one embodiment, for example, non-vulnerable STAs (e.g., STAs located / located within the second base region 110a) may be assigned any resource units associated with the second operating frequency bandwidth.

[0056] In general, a reserved subset of the operating frequency bandwidth may correspond to at least one resource unit, which may be considered to correspond to, for example, at least one reserved resource unit. Specifically, a reserved subset of the operating frequency bandwidth may correspond to at least one reserved resource unit. The reserved resource unit(s) may be used, for example, for one or more vulnerable STAs in a BSS (e.g., reserved resource unit set 114 for STA2 in BSS1 or reserved resource unit set 114 for STA3 in BSS2). More specifically, one or more reserved resource units may be assigned for use by one or more vulnerable STAs (i.e., STAs that are susceptible to interference when operating within the operating frequency bandwidth).

[0057] In this regard, it will be appreciated that resource unit(s) can be reserved when at least one STA (e.g., a vulnerable STA, such as STA2 or STA3) can be determined to be susceptible to interference. In one example, an AP (e.g., AP1, AP2) can reserve one or more resource units when it determines that a STA is susceptible to excessive interference (i.e., a vulnerable STA, such as STA2 or STA3). In one example, the AP can consider all cell-edge STAs in a BSS to be vulnerable STAs and susceptible to excessive interference. It will be further appreciated, therefore, that the reservation of at least one resource unit does not need to be performed all the time (e.g., when triggered by the AP's determination that the STA is a vulnerable STA). Grouping STAs (as cell-edge STAs or cell-center STAs) to form a reserved / cell-edge resource unit set and correspondingly restricting RUs to cell-edge STAs can be triggered by excessive failures to communicate with cell-edge STAs or by reports of interference from STAs, etc. In this case, resource units are reserved for a group of cell-edge STAs (eg, STA1 and STA3 in BSS2, STA2 and STA4 in BSS1).

[0058] As previously mentioned, to facilitate scheduling, in accordance with one embodiment of the present disclosure, information related to the allocation of one or more reserved resource units (for use by one or more vulnerable STAs) may be shared between AP1 and AP2.

[0059] In one example, data / information regarding the BSS1 cell edge resource unit set 114 may be communicated from AP1 to AP2. AP2 may be configured to determine the BSS2 cell edge resource unit set 116 based on the received data / information regarding the BSS1 cell edge resource unit set 114. Specifically, AP2 may be configured to determine the BSS2 cell edge resource unit set 116 such that there is minimal or no overlap between the BSS2 cell edge resource unit set 116 and the BSS1 cell edge resource unit set 114.

[0060] In another example, data / information regarding the BSS2 cell edge resource unit set 116 may be communicated from AP2 to AP1. AP1 may be configured to determine the BSS1 cell edge resource unit set 114 based on the received data / information regarding the BSS2 cell edge resource unit set 116. Specifically, AP1 may be configured to determine the BSS1 cell edge resource unit set 114 such that there is minimal or no overlap between the BSS1 cell edge resource unit set 114 and the BSS2 cell edge resource unit set 116. In general, it is expected that an AP setting up a BSS at a later point in time will be configured to determine its own cell edge resource unit set by taking into account data / information of the cell edge resource unit sets of neighboring existing BSSs.

[0061] The communication of information corresponding to the allocation of the reserved resource unit(s) may be performed by communicating one or both of at least one beacon frame and at least one probe response frame.

[0062] In one embodiment, the size of each of the BSS1 cell edge resource unit set 114 and the BSS2 cell edge resource unit set 116 may be determined according to the proportion of vulnerable STAs in the respective first operating region 108 and second operating region 110. In another embodiment, each of the BSS1 cell edge resource unit set 114 and the BSS2 cell edge resource unit set 116 may include multiple resource units that may be associated with different zones of the operating frequency bandwidth for frequency diversity. For example, an RU located in a higher frequency zone of the cell edge resource unit set 114 may be assigned to transmit with STA4, and an RU located in a lower frequency zone of the cell edge resource unit set 114 may be assigned to transmit with STA2.

[0063] An AP (e.g., AP1, AP2) can be configured to restrict scheduled communications (e.g., orthogonal frequency division multiple access (OFDMA)-based communications) to vulnerable STAs based on the assigned reserved resource units (e.g., BSS1 cell edge resource unit set 114, BSS2 cell edge resource unit set 116). For example, the AP can restrict all scheduled OFDMA-based communications to the vulnerable STAs to the assigned reserved resource units. The scheduled communications can include one or both of uplink (UL) and downlink (DL) type communications. The AP can allocate RUs of the same size or smaller size from within the reserved resource unit set to the STAs. For example, if the reserved resource unit set is a 106-tone RU, the AP can allocate one or more 26-tone or 52-tone RUs, or the entire 106-tone RU, within the reserved resource unit set to schedule cell-edge STA transmissions.

[0064] Optionally, according to one embodiment of the present disclosure, UL type communications may be restricted based on the allocated reserved resource unit(s), and DL type communications may be allowed at a lower transmission power (i.e., not restricted based on the allocated reserved resource unit(s)).

[0065] As mentioned above, the communication of data / information corresponding to the allocation of the reserved resource unit(s) may be effected by communicating at least one beacon frame and / or at least one probe response frame, as will be explained in more detail below with reference to Figure 3 (i.e. Figures 3a and 3b).

[0066] 3a illustrates a first exemplary cell-edge resource unit (RU) set field 304 that may be included in a beacon / probe response frame to convey data / information corresponding to the allocation of one or more reserved resource units, according to one embodiment of the present disclosure. This first exemplary cell-edge RU set field 304 may be conveyed in a beacon / probe response frame from an AP (e.g., AP1, AP2). The conveyance of the first exemplary cell-edge RU set field 304 in a beacon / probe response frame may occur, for example, via broadcast-based communication.

[0067] A first exemplary Cell-edge RU Set field 304 (also referred to as the "cell-edge RU set" as labeled in FIG. 3a) may be included in a beacon / probe response frame transmitted by an AP. Generally, the Cell-edge RU Set field 304 may indicate reserved RU(s) assigned for use by one or more cell-edge-type devices. Specifically, the Cell-edge RU Set field 304 may indicate reserved RU(s) assigned for use by one or more vulnerable STAs (e.g., STA2, STA3). Furthermore, the assignment of the reserved RU(s) may be based on coding similar to or the same as the coding of the RU assignment field of an 11ax-based trigger frame. In one embodiment, the RU assignments may be of various sizing (i.e., different sizes).

[0068] The Cell-edge RU Set field 304 may include one or more subfields 306. For example, the Cell-edge RU Set field 304 may include a first subfield 306a and one or more RU Allocation subfields 306b / 306c. The first subfield 306a may indicate the number of RU allocations conveyed in the Cell-edge RU Set field 304. The RU Allocation subfields 306b / 306c indicate reserved resource unit sets. When multiple RU Allocation subfields 306b / 306c are present, the first RU Allocation subfield may indicate a reserved RU associated with the lowest frequency in the reserved resource unit set, and the last RU Allocation subfield may indicate a reserved RU associated with a higher frequency in the reserved resource unit set. The other RU Allocation subfields between the first and last subfields indicate reserved RUs associated with other frequencies within the reserved resource unit set.

[0069] The Cell-edge RU Set field 304 can be included in, for example, a high-throughput (HT) element, a very high-throughput (VHT) element, or a high-efficiency (HE) operation element. This can indicate that the reserved RU is associated with an operating frequency band (i.e., 2.4 GHz or 5 GHz associated with HT, 5 GHz associated with VHT, or 2.4 GHz, 5 GHz, or 6 GHz associated with HE). In this regard, a first exemplary Cell-edge RU Set field 304 can be conveyed in a beacon / probe response frame in association with a particular operating frequency band (e.g., 2.4 GHz, 5 GHz, or 6 GHz).

[0070] The Cell-edge RU Set field may also be included in a neighbor report element or a reduced neighbor report element that may be transmitted from an AP (e.g., AP1) to advertise the reserved RUs of at least one neighboring AP (e.g., AP2).

[0071] The reservation of RUs for cell-edge STAs and the broadcasting / advertising of cell-edge resource unit sets (e.g., in the Cell-edge RU Set field 304) is not always performed and can be triggered only when the AP determines that its associated cell-edge STAs are experiencing excessive interference (e.g., based on interference reports from the STAs).

[0072] 3b illustrates a second exemplary Cell-edge RU Set element 308 that can be included in a beacon / probe response frame to convey data / information corresponding to the allocation of one or more reserved resource units in accordance with another embodiment of the present disclosure. This second exemplary Cell-edge RU Set element 308 can be conveyed by inclusion in a beacon / probe response frame transmitted by an AP (e.g., AP1, AP2). The conveyance of the second exemplary Cell-edge RU Set element 308 in the beacon / probe response frame can be performed, for example, via broadcast-based communication. In one example, the AP can be a multi-band capable EHT-type AP that can be configured to convey the second exemplary Cell-edge RU Set element 308 associated with multiple operating frequency bands (e.g., 2.4 GHz, 5 GHz, and 6 GHz). In this regard, an AP (e.g., a multi-band capable EHT AP) can be considered to be configured to convey a consolidated cell-edge RU set (associated with multiple operating frequency bands).

[0073] As shown, the second exemplary Cell-edge RU Set element 308 can include multiple Band-specific cell-edge RU set fields 310. Each Band-specific cell-edge RU set field 310 can be used to define a reserved RU set in a particular operating frequency band, where the operating frequency band is identified by the Band ID subfield of the Band-specific cell-edge RU set field 310, while the reserved RU set is indicated by the Cell-edge RU set subfield of the Band-specific cell-edge RU set field 310.

[0074] This disclosure contemplates that conveying the second exemplary Cell-edge RU Set element 308 in a beacon / probe response frame is useful for deployment in multi-vendor scenarios where there is no direct communication link between neighboring APs (e.g., AP1, AP2) and centralized management of the APs (e.g., AP1, AP2) cannot be facilitated. One or more APs (e.g., AP1) can be configured to cooperatively adapt allocations of reserved RU(s) associated with neighboring APs (e.g., AP2) based on the conveyed second exemplary Cell-edge RU Set element 308 in order to minimize interference to vulnerable STA(s).

[0075] As previously mentioned, vulnerable STAs may generally be located within the overlap region 112. In one embodiment, the present disclosure contemplates that vulnerable STAs may in some cases be located outside the overlap region 112 but may still experience interference (e.g., OBSS-based interference), as will be explained in more detail below with reference to Figure 4 (i.e., Figures 4a-4c).

[0076] FIG. 4a generally illustrates that one or more vulnerable STAs (e.g., STA2 and STA3) may be located / located within the overlap region 112. As illustrated, STA2 and STA3 may experience actual interference (e.g., located within the OBSS-based severe interference region 402). This disclosure further contemplates the possibility that a STA (labeled “STA5” in FIG. 4a) located within a base region (e.g., within the second base region 110a but outside the overlap region 112) may experience interference (e.g., located within the OBSS-based severe interference region 402) despite being within the base region, and thus may be considered / determined (e.g., by AP2) to be a vulnerable STA. On the other hand, STA1 and STA4 may be considered / determined (by AP2 and AP1, respectively) to be non-vulnerable STAs because they are located away from the OBSS-based severe interference region 402.

[0077] This disclosure assumes that vulnerable STAs (e.g., STA2, STA3, and / or STA5) require protection from, for example, OBSS-based interference, whereas such protection may not be necessary / important for non-vulnerable STAs (e.g., STA1 and / or STA4). Accordingly, an AP (i.e., AP1, AP2) may be configured to reserve at least one resource unit (RU) for vulnerable STA(s) (i.e., also referred to as a "reserved RU set" or "protected RU set"). Meanwhile, in one embodiment, no restrictions need be placed on the selection of RUs for non-vulnerable STA(s). In this case, resource units are reserved for a group of vulnerable STAs (e.g., STA2, STA3, and / or STA5) that are actually subject to interference.

[0078] In one embodiment, information corresponding to the "reserved RU set" / "protected RU set" may be communicated from an AP (e.g., AP1) to one or more other APs (e.g., AP2), for example, by broadcast (e.g., beacon-based broadcast using one or more beacons) and / or AP-AP-based communication (e.g., one or more direct communication links between the AP and another AP), as will be described in more detail below with reference to FIG. 4b in connection with AP-AP-based communication.

[0079] An AP may be configured to identify / determine one or more vulnerable STAs based on one or more reports from one or more associated STAs and / or select at least one suitable RU for reservation purposes (i.e., obtain / generate / create at least one "reserved RU set"). For example, AP2 may be associated with STA1, STA3, and STA5 (i.e., may be generally associated with BSS2), while AP1 may be associated with STA2 and STA4 (i.e., may be generally associated with BSS1).

[0080] In a more specific example, AP2 may be configured to identify vulnerable STAs (e.g., STA3 and / or STA5) and / or select at least one suitable RU for reservation purposes based on reports from STA1, STA3, and / or STA5.

[0081] In another more specific example, AP1 may be configured to identify / determine a vulnerable STA (e.g., STA2) based on reports from STA2 and / or STA4, and / or to select at least one suitable RU for reservation purposes (i.e., obtain / generate / create at least one “reserved RU set” / “protected RU set”).

[0082] In one embodiment, an AP can be configured to identify / determine one or more interfering STAs from adjacent operating regions based on report(s) from associated STA(s). For example, a vulnerable STA (e.g., STA3) operating in the second operating region 110 can communicate a report (e.g., to AP2) indicating that a STA (e.g., STA2) operating in the first operating region 108 (adjacent to the second operating region 110) is an interfering STA. AP2 can communicate the identity of the interfering STA (e.g., STA2) to the OBSS AP (e.g., AP1), which can use the information to restrict the RU(s) associated with the interfering STA to its “reserved RU set” / “protected RU set.”

[0083] Examples of reports for identifying / determining vulnerable STAs and optionally identifying / determining one or more interfering STAs may include bandwidth query reports and / or interference reports from associated STAs. Information corresponding to the reserved set of RUs and, optionally, identities of the interfering STAs may be communicated from an AP (e.g., AP1) to one or more other APs (e.g., AP2), for example, via one or both of broadcast (e.g., beacon-based broadcast using one or more beacons) and AP-AP-based communication (e.g., one or more direct communication links between the AP and another AP). Examples of reports are described in more detail below with reference to FIG. 4c.

[0084] In this regard, it will be appreciated that an AP (e.g., AP1) may be configured to communicate data / information corresponding to one or both of the aforementioned “reserved RU set” / “protected RU set” and the aforementioned report to one or more other APs (e.g., AP2).

[0085] Furthermore, this disclosure contemplates that an AP (e.g., AP1) associated with an operating area (e.g., the first operating area 108 associated with BSS1) can be configured to select at least one suitable RU for reservation (i.e., obtain / generate / create a reserved / protected RU set) by considering the reserved / protected RU set(s) associated with an adjacent operating area (e.g., the second operating area 110 associated with BSS2). In this way, the reserved / protected RU set(s) associated with the operating area (e.g., the first operating area 108) can have minimal or no overlap with the reserved / protected RU set(s) associated with an adjacent operating area (e.g., the second operating area 110).

[0086] Referring to FIG. 4b, according to one embodiment of the present disclosure, an AP can be configured to communicate its "reserved RU set" / "protected RU set" (or the aforementioned consolidated cell edge RU set) to one or more other APs via AP-to-AP-based communication (via a wired or wireless link). The AP-to-AP link can be an in-band wireless link or a wireless link in another band. For example, a unicast Public Action frame can be defined for this purpose, or a new secure AP-to-AP in-band interface can be defined. It is also possible for the AP-to-AP link to use a wired link (either a direct link or a link relayed via another device such as an AP controller).

[0087] 4b illustrates an exemplary communication frame 406. The communication frame 406 may correspond to, for example, an action frame, which may be transmitted over a wireless link to another AP in its original format or may be transmitted via encapsulation within a data frame (e.g., as an Ethertype 89-0d frame).

[0088] The communication frame 406 may be defined by an AP (e.g., AP1, AP2) such that a MAC portion 406a (also referred to as a "MAC header") and a body portion 406b (also referred to as a "frame body") are defined. Specifically, the communication frame 406 may include the MAC portion 406a and the body portion 406b.

[0089] In one embodiment, information / data associated with at least one "reserved RU set" / "protected RU set" (denoted by the "Reserved RU Set element" in FIG. 4b) may be carried by the communication frame 406 in the main body portion 406b. The Reserved RU Set element carries information of a reserved RU set for a vulnerable STA and shares the same format as the Cell-edge RU Set element 308 in FIG. 3b.

[0090] In another embodiment, information / data identifying one or more of the aforementioned interfering STAs (denoted in FIG. 4b by “List of interfering STAs (Optional)”) may be conveyed by the communication frame 406 in the main body portion 406b.

[0091] In yet another embodiment, information associated with at least one “reserved RU set” / “protected RU set” and information identifying one or more of the aforementioned interfering STAs may be conveyed by the communication frame 406 in the body portion 406b.

[0092] In this regard, communication frame 406 may correspond to, for example, an "AP coordinated reserved RU action frame" (with the Category field set to "AP coordination reserved RU") that may be communicated from an AP (e.g., AP1) to one or more other APs (e.g., AP2) to communicate information to facilitate scheduling while minimizing / mitigating the need for strict synchronization (e.g., between APs). The communicated information / data may be associated with at least one "reserved RU set" / "protected RU set" and / or information identifying one or more of the aforementioned interfering STAs.

[0093] In one embodiment, the information conveyed by a communication frame 406 (i.e., a current communication frame) transmitted from an AP (e.g., AP1) and received by another AP (e.g., AP2) may be valid until the next communication frame 406 (i.e., a subsequent communication frame) transmitted from an AP (e.g., AP1) and received by another AP (e.g., AP2).

[0094] In one embodiment, an AP (e.g., AP1) can autonomously communicate the communication frame 406 to one or more other APs (e.g., AP2) and / or communicate the communication frame 406 to one or more other APs (e.g., AP2) based on a request signal. The request signal can be generated by one or more other APs (e.g., AP2) and communicated to the AP (e.g., AP1) that generates and communicates the communication frame 406.

[0095] An AP that receives an AP cooperative reservation RU action frame from a neighboring AP uses information about the reserved RU set to determine its own reserved RU set. When determining RUs for communication with associated STAs reported as interfering STAs (in the List of Interfering STAs field), the AP is careful not to select RUs that are in the reserved RU set of the reporting AP.

[0096] Alternatively, in a managed network (e.g., an enterprise network), instead of communicating directly with neighboring APs, each AP reports its reserved set of RUs to a multi-AP coordinator or AP controller (which may be one of these APs), which can then assign RUs to be used by vulnerable STAs of each AP so that there is minimal overlap between the APs it manages.

[0097] 4c, an AP (e.g., AP1) may be configured to generate a request (e.g., a request signal) to measure interference and communicate the request to a STA (e.g., STA2). The request may be conveyed, for example, by one or more EHT action frames 408, according to one embodiment of the present disclosure.

[0098] Upon receiving the request, STA2 may be configured to perform one or more measurement-related tasks and generate a measurement report accordingly. The measurement report may then be communicated from the STA to the requesting AP. The measurement report may be conveyed in one or more EHT action frames 410, according to one embodiment of the present disclosure.

[0099] This disclosure contemplates that, in one embodiment, a STA may also perform one or more measurement-related tasks autonomously (e.g., periodically without a request from an AP) and generate measurement reports accordingly, which may then be communicated from the STA to one or more APs.

[0100] In general, "Channel Number" indicates the channel on which interference is measured, "Measurement Start Time" indicates the time when interference measurement started, "Measurement Duration" indicates the duration of the requested / reported measurement (expressed in time units (TU)), "Count" indicates the number of interfered RUs to be reported, "Interference Level" indicates the maximum interference level (dBm) of the entire receive chain averaged over a fixed period across interfered RUs, and "Interfered RU" indicates the RU that the interferer PPDU (Physical Layer Protocol Data Unit) occupies.

[0101] This disclosure contemplates that the ability of a STA to measure RU-level interference may depend on the hardware capabilities of the STA, and the process may not be straightforward.

[0102] As an example, a Pre-11be-based STA is only required to receive / transmit data associated with one RU at any given time, because such a STA may only be able to measure and detect OBSS OFDMA transmissions associated with one RU at a time. Thus, the STA may need to receive and decode many multi-user (MU) PPDUs from the OBSS so that it can measure interference at all RUs in a specified channel.

[0103] In another example, an EHT-based STA with hardware capability to simultaneously receive data / information for multiple RUs can measure interference and detect OBSS OFDMA transmissions associated with multiple RUs simultaneously.

[0104] Furthermore, this disclosure assumes that, with respect to a DL MU PPDU from an OBSS, a STA can determine the RU allocation in the Data field of the PPDU by analyzing the SIG-B field of the PPDU. With respect to a UL MU PPDU, the RU allocation information can be obtained from the User Info field of the trigger frame that initiates the UL MU PPDU. After the RU allocation information is obtained, the STA can measure the interference level of the RU and decode the A-MPDU (Aggregated MAC Protocol Data Unit) / MPDU (MAC Protocol Data Unit) on a specific RU to extract the MAC address and OBSS BSSID (Basic Service Set Identifier) ​​of the interfering STA.

[0105] Alternatively, instead of collecting MAC addresses, the STA can collect information about the association identifier (AID) of the interfering STA, for example, from the SIG-B field associated with the DL MU PPDU or from the User Info field of the trigger frame. Furthermore, instead of the BSSID, the STA can collect information related to the BSS color of the OBSS from the SIG-A field of the PPDU. Furthermore, the STA can simply measure the interference level of the RU without having to decode the Data field of the PPDU. In addition, the STA can report the AID of the interfering STA instead of the MAC address and the BSS color of the OBSS instead of the BSSID in the EHT interference measurement report. This can help reduce the effort required for the STA to collect interference measurement reports from OBSS OFDMA transmissions.

[0106] Based on interference reports from STAs associated with the AP, the AP can classify STAs that are affected by interference (e.g., STAs that experience interference above a threshold level) as vulnerable STAs and select RUs in the reserved RU set so as to mitigate interference (e.g., OBSS-based interference) to those vulnerable STAs.

[0107] The above will be explained in more detail below with reference to FIG.

[0108] Specifically, Figure 5a illustrates a first exemplary communication scenario 502 according to an embodiment of the present disclosure. Figure 5b illustrates a second exemplary communication scenario 504 according to an embodiment of the present disclosure. Figure 5c illustrates a third exemplary communication scenario 506 according to an embodiment of the present disclosure. Figure 5d illustrates a fourth exemplary communication scenario 508 according to an embodiment of the present disclosure.

[0109] 5a, a first exemplary communication scenario 502 may be based on an exemplary context in which BSS1 and BSS2 may be associated with the same operating channels (labeled "CH1," "CH2," "CH3," and "CH4" in FIG. 5a). Specifically, the operating channels associated with BSS1 and the operating channels associated with BSS2 may correspond to operating channels having, for example, the same bandwidth and the same primary channel.

[0110] As shown, the cell-edge RU set associated with BSS1 may be assigned to CH4, while the cell-edge RU set associated with BSS2 may be assigned to CH2 (based on information exchanged between the APs of the two BSSs). For example, reserved RUs may be assigned to CH2 for use by cell-edge STAs associated with BSS2, while reserved RUs may be assigned to CH4 for use by cell-edge STAs associated with BSS1.

[0111] For example, if there is DL multi-user (MU) physical layer protocol data unit (PPDU)-based communication in BSS2, AP2 may be configured to perform DL transmission(s) to a cell-edge STA (e.g., STA3) on CH2 (i.e., based on the aforementioned cell-edge RU set(s) assigned to CH2). Furthermore, in relation to BSS1, AP1 may be configured to solicit / request UL transmissions from a cell-edge STA (e.g., STA2) associated with BSS1 by communicating one or more trigger frames (TFs) based on the DL MU PPDU-based communication to STA2 via CH4. STA2 may then communicate (i.e., UL PPDU-based communication) with AP1 on CH4 (i.e., based on the aforementioned cell-edge RU set(s) assigned to CH4). Thus, according to one embodiment of the present disclosure, communication(s) associated with a cell-edge STA may be restricted based on the aforementioned cell-edge RU set(s).

[0112] It can be seen that CH2 and CH4 do not overlap. Thus, the cell-edge RU set(s) associated with BSS1 and the cell-edge RU set(s) associated with BSS2 can be considered non-overlapping. This disclosure believes this is useful for minimizing / mitigating interference (e.g., inter-basic service set (BSS) type interference, inter-BSS interference). Thus, for example, scheduling between AP1 and AP2 can be facilitated in a manner that avoids the need for strict synchronization (i.e., minimizes the signaling required between AP1 and AP2) for purposes of mitigating / minimizing interference (e.g., inter-BSS type interference). This disclosure further believes this is useful for promoting spatial reuse. For example, if no cell-edge RU set is reserved for CH4 and RUs are assigned (e.g., by an MU TF) to CH2 for use by cell-edge STAs associated with BSS1, the cell-edge STAs associated with BSS1 will be informed that CH2 is busy (due to DL transmissions in BSS2), and thus UL transmissions will be blocked (i.e., not allowed). However, by ensuring that the cell-edge RU sets do not overlap, transmissions in both BSSs can occur simultaneously without causing destructive interference to each other.

[0113] Although not shown in the figure, non-cell-edge STAs can be scheduled in RUs of the remaining channels (in the white space in the PPDU).

[0114] Reserving the same set of RUs for DL ​​and UL transmissions within the same BSS may be more advantageous because it simultaneously avoids UL-DL interference (interference between non-AP STAs and non-AP STAs). However, it is also possible that the reserved RUs are not the same for DL ​​and UL, and different sets of RUs may be reserved for UL and DL transmissions within a BSS.

[0115] 5b, a second exemplary communication scenario 504 may be based on an exemplary context in which BSS1 and BSS2 may be associated with different operating channels (labeled "CH1," "CH2," "CH3," "CH4," "CH5," and "CH6" in FIG. 5b). Specifically, the operating channels associated with BSS1 and BSS2 may correspond to operating channels having the same bandwidth but different starting frequencies and / or different primary channels, for example.

[0116] As shown, BSS1 may be associated with a first group of operating channels, while BSS2 may be associated with a second group of operating channels. The first group of operating channels may include CH1, CH2, CH3, and CH4. The second group of operating channels may include CH3, CH4, CH5, and CH6. The cell-edge RU set(s) associated with BSS1 may be assigned to CH1 and CH2, while the cell-edge RU set(s) associated with BSS2 may be assigned to CH5 and CH6. For example, reserved RUs may be assigned to CH5 and / or CH6 for use by vulnerable STAs associated with BSS2, while reserved RUs may be assigned to CH1 and / or CH2 for use by vulnerable STAs associated with BSS1.

[0117] For example, when there is an UL MU PPDU-based communication in BSS2, with respect to AP2, DL transmission(s) / UL transmission(s) to / from a vulnerable STA (i.e., STA3) can occur on CH5, CH6 (i.e., based on the aforementioned cell-edge RU set(s) assigned to CH5 and / or CH6). Furthermore, with respect to BSS1, AP1 can be configured to solicit / request UL transmissions from a vulnerable STA (i.e., STA2) associated with BSS1 by transmitting one or more trigger frames (TFs) based on the DL MU PPDU-based communication to STA2. STA2 can then communicate (i.e., UL PPDU-based communication) with AP1 on CH1, CH2 (i.e., based on the aforementioned cell-edge RU set(s) assigned to CH1 and / or CH2). Thus, according to one embodiment of the present disclosure, communication(s) associated with a vulnerable STA can be restricted based on the aforementioned cell-edge RU set(s).

[0118] It can be understood that there may be overlap in CH3 and CH4 (between BSS1 and BSS2), but CH1 and CH2 do not overlap with CH5 and CH6. Thus, the cell-edge RU set(s) associated with BSS1 and the cell-edge RU set(s) associated with BSS2 can be considered non-overlapping.

[0119] The present disclosure believes that this is useful for minimizing / mitigating interference (e.g., inter-basic service set type interference, inter-BSS interference). Thus, scheduling can be facilitated between AP1 and AP2 in a manner that avoids the need for strict synchronization (i.e., minimal signaling is required between AP1 and AP2), for example, to mitigate / minimize interference (e.g., inter-BSS type interference). Furthermore, the present disclosure believes that this is further useful for promoting spatial reuse.

[0120] 5c, a third exemplary communication scenario 506 may be based on an exemplary context in which BSS1 and BSS2 may be associated with different operating channels (labeled “CH1,” “CH2,” “CH3,” “CH4,” “CH5,” and “CH6” in FIG. 5c). Specifically, the operating channels associated with BSS1 and BSS2 may correspond to operating channels having the same bandwidth but different starting frequencies and / or different primary channels, for example.

[0121] The third example communication scenario 506 may be further based on an example context in which a cell edge RU set(s) associated with BSS1 and a cell edge RU set(s) associated with BSS2 are located on overlapping channels of the two BSSs.

[0122] As shown, BSS1 may be associated with a first group of operating channels, while BSS2 may be associated with a second group of operating channels. The first group of operating channels may include CH1, CH2, CH3, and CH4. The second group of operating channels may include CH3, CH4, CH5, and CH6. The cell-edge RU set(s) associated with BSS1 and the cell-edge RU set(s) associated with BSS2 may be located on overlapping channels of the two BSSs, i.e., CH3 and CH4. The cell-edge RU set associated with BSS1 may be assigned to CH4, while the cell-edge RU set associated with BSS2 may be assigned to CH3. For example, reserved RUs for use by vulnerable STAs associated with BSS2 may be assigned to CH3, while reserved RUs for use by vulnerable STAs associated with BSS1 may be assigned to CH4.

[0123] For example, if there is UL MU PPDU-based communication in BSS2, with respect to AP2, DL transmission(s) / UL transmission(s) to / from a vulnerable STA (i.e., STA3) can occur on CH3 (i.e., based on the aforementioned cell-edge RU set assigned to CH3). Furthermore, with respect to BSS1, AP1 can be configured to solicit / request UL transmissions from a vulnerable STA (i.e., STA2) associated with BSS1 by conveying one or more trigger frames (TFs) based on the DL MU PPDU-based communication to STA2. STA2 can then communicate (i.e., UL PPDU-based communication) with AP1 on CH4 (i.e., based on the aforementioned cell-edge RU set(s) assigned to CH4). Thus, according to one embodiment of the present disclosure, communication(s) associated with a vulnerable STA can be restricted based on the aforementioned cell-edge RU set(s).

[0124] Although there may be overlap between CH3 and CH4 (between BSS1 and BSS2), the cell edge RU set associated with BSS1 (i.e., assigned to CH4) and the cell edge RU set associated with BSS2 (i.e., assigned to CH3) can nevertheless be considered non-overlapping.

[0125] Thus, although there may be one or more overlapping operating channels between the cell-edge RU set associated with BSS1 and the cell-edge RU set associated with BSS2, interference (e.g., inter-basic service set type interference, inter-BSS interference) can still be mitigated / minimized. Thus, scheduling can be facilitated between AP1 and AP2 in a manner that avoids the need for strict synchronization (i.e., minimal signaling is required between AP1 and AP2), for example, to mitigate / minimize interference (e.g., inter-BSS type interference). Furthermore, the present disclosure believes that this is further useful for promoting spatial reuse.

[0126] 5d, a fourth exemplary communication scenario 508 may be based on an exemplary context in which communications among multiple APs (e.g., one of which is AP1) may be coordinated by a coordinating AP (e.g., AP2). Thus, the coordinating AP may be considered a master AP for one or more remaining APs in the system 100, while the remaining AP or APs may be considered one or more slave APs for the coordinating AP. This type of coordinated transmission may be expected in a multi-AP managed network in which transmissions by multiple APs are closely coordinated, for example, by a multi-AP coordinator (AP2). The multi-AP coordinator may collect information regarding the reserved RU sets of each AP in advance. The multi-AP coordinator may determine the transmission timing as well as the RUs used for transmissions to and from vulnerable STAs, such that RUs used by STAs associated with different APs do not overlap with each other.

[0127] For example, a master AP (e.g., AP2) can be configured to transmit a master trigger frame (MTF), shown as "Multi-AP Trigger Frame" in FIG. 5d, to a slave AP (e.g., AP1) to initiate cooperative communication. The master trigger frame (MTF) can indicate instructions for the slave AP to initiate communication (e.g., UL transmission) from a vulnerable STA (e.g., STA2) associated with the slave AP and to allocate a first set of cell-edge RUs to be used for communication (e.g., UL transmission) with a cell-edge STA associated with the slave AP. The master AP can be configured to allocate a second set of cell-edge RUs to be used for communication (e.g., UL transmission) with a vulnerable STA (e.g., STA3) associated with the master AP. After a short interframe space (SIFS) has elapsed, both the master AP and the slave AP can be configured to transmit a basic trigger frame (BTF). After the next SIFS following the BTF, a vulnerable STA associated with the master AP (e.g., STA3) can be configured to communicate based on the second set of cell edge RUs (denoted by "UL PPDU" in FIG. 5d), while a vulnerable STA associated with the slave AP (e.g., STA2) can be configured to communicate based on the first set of cell edge RUs (denoted by "UL PPDU" in FIG. 5d). Transmissions from the two STAs occur simultaneously but in different parts of the frequency. After yet another SIFS following the communication from the vulnerable STA (i.e., "UL PPDU"), each of the master AP and slave AP can be configured to convey an acknowledgment frame (denoted by "Block Ack Frame" in FIG. 5d) based on the same RU used by the UL PPDU.

[0128] Based on the above-described arrangement of the Master AP and Slave APs, scheduling (i.e., coordination of allocation of cell-edge RU sets associated with vulnerable STAs) can be facilitated in such a way that the need for strict synchronization is avoided (e.g., excessive signaling between AP1 and AP2 can be avoided), for example, in order to mitigate / minimize interference (e.g., inter-BSS type interference).

[0129] Scheduling will now be described with reference to a second exemplary scenario according to one embodiment of the present disclosure.

[0130] In a second exemplary scenario, as described with reference to Figures 6 and 7, scheduling may occur in a situation where information related to scheduled communications associated with vulnerable STA(s) may be shared between APs (e.g., AP1 and AP2). In this regard, the second exemplary scenario may relate to time-domain based scheduling.

[0131] Specifically, in a second exemplary scenario, the AP(s) 104 (i.e., one or both of the first AP 104a and the second AP 104b) may be configured to provide information (e.g., periodic information) regarding scheduled communications associated with the vulnerable STA(s).

[0132] In one example, a first AP 104a (i.e., “AP1”) may be configured to provide information related to scheduled communications (e.g., planned transmissions) of one or more vulnerable STAs (e.g., STA2) associated with BSS1.

[0133] In another example, a second AP 104b (i.e., “AP2”) may be configured to provide information related to scheduled communications (e.g., planned transmissions) of one or more vulnerable STAs (e.g., STA3) associated with BSS2.

[0134] Time domain based scheduling is explained in more detail below with reference to FIGS.

[0135] Although the information of the reserved RU set of the OBSS is useful, completely avoiding overlap of the reserved RU set of the OBSS when scheduling transmissions of vulnerable STAs is advantageous from the viewpoint of interference avoidance, but reduces spectral efficiency. Having information of the transmission schedule between the vulnerable STAs of the OBSS helps the AP avoid scheduling the transmissions of vulnerable STAs on RUs that are in the reserved RU set of the OBSS when transmitting to and from the vulnerable STAs of the OBSS. In time slots where transmissions of vulnerable STAs of the OBSS are not scheduled, the AP can use any RU (not limited to the reserved RU set) for transmissions to and from its own vulnerable STAs.

[0136] As shown in FIG. 6 , according to one embodiment of the present disclosure, a transmitting AP (e.g., AP1) may provide information corresponding to an estimate 600 of whether vulnerable STA(s) (e.g., STA2) associated with the transmitting AP (e.g., associated with BSS1) have been scheduled for transmission for a number of time periods (denoted by “x TUs” in FIG. 6 ) from a reference time (denoted by “Reference Time” in FIG. 6 ). For example, in FIG. 6 , the number “1” may represent that the vulnerable STA has been scheduled for communication (by the AP) during that corresponding time period (i.e., “x TUs”), while the number “0” may represent that the vulnerable STA has not been scheduled for communication (by the AP).

[0137] The receiving AP (e.g., AP2) can be configured to schedule communications for vulnerable STA(s) associated with the receiving AP (e.g., associated with BSS2) based on information corresponding to estimate 600 in a manner that avoids / minimizes overlapping communications with the vulnerable STA(s) associated with the transmitting AP. In this manner, overlapping communications (e.g., transmissions) between vulnerable STA(s) associated with the transmitting AP (e.g., AP1) and vulnerable STA(s) associated with the receiving AP (e.g., AP2) can be avoided / minimized. The AP's planned transmission schedule is assumed to repeat until it receives another schedule from the AP.

[0138] As an example, information corresponding to the estimate 600 can be provided from a transmitting AP (e.g., AP1) to a receiving AP (e.g., AP2) in units of 10 TU (time units) for the next beacon interval referenced to the next TBTT (Target Beacon Transmission Time). TU approximately corresponds to, for example, 1024 μS (microseconds). In this example, the beacon interval = 100 TU, and the reference time of the first AP is TBTT1, which refers to the target beacon transmission time (TBTT) of the first AP (that transmitted the transmission schedule). The reference time of the coordinator AP (the AP receiving the transmission schedule) is TBTT2 = TBTT1 + 10 TU. Based on the estimate of the first AP's transmission schedule, the coordinator AP adjusts its transmission schedule so as not to schedule transmissions to and from its vulnerable STAs in the same time slot.

[0139] In one embodiment, information corresponding to estimate 600 may be communicated by the transmitting AP to the receiving AP by including an Interference Impact Estimate element in an AP coordination information response frame, as described in more detail below with reference to Figure 7. The format of the Interference Impact Estimate element is described in more detail with reference to Figure 8d.

[0140] Referring to FIG. 7 , the transmitting AP may correspond to, for example, an EHT-type AP. Information corresponding to the estimate 600 may be conveyed by the EHT-type AP by at least one AP transmitting an AP coordination information request frame 702 to another AP indicating that an interference impact estimate is requested. The AP receiving the request transmits an AP coordination information response frame 704 including an Interference Impact Estimate element. Alternatively, the transmission of the AP coordination information response frame 704 may be unsolicited, for example, by periodic broadcast. In one example, the AP coordination information response frame 704 may be conveyed from the transmitting AP to the receiving AP at least 20 TUs prior to the next TBTT to allow the receiving AP sufficient time to plan its transmission schedule.

[0141] It can be appreciated that the time domain based scheduling described above helps to minimize / mitigate interference (eg, inter-BSS type interference).

[0142] As described above (based on the first and second exemplary scenarios), the present disclosure contemplates that scheduling may be performed in connection with frequency domain based scheduling in one embodiment, and in connection with time domain based scheduling in another embodiment.

[0143] Furthermore, the present disclosure contemplates that, as yet another embodiment, scheduling may be performed in connection with a combination of frequency domain based scheduling and time domain based scheduling, as will be described below with reference to a third exemplary scenario.

[0144] In a third exemplary scenario, as described with reference to Figures 8a-8i, information related to allocation of one or more reserved resource units (as described in connection with the first exemplary scenario) may be shared between APs, and information related to scheduled communications associated with vulnerable STA(s) (as described in connection with the second exemplary scenario) may be shared between APs. In this regard, relevant portions of the foregoing discussion regarding the first and second exemplary scenarios apply equally in connection with the third exemplary scenario.

[0145] In a third exemplary scenario, an AP (e.g., AP1), such as an EHT-type AP, can be configured to communicate information regarding the impact of planned communications that may cause interference to other BSSs (e.g., BSS-based interference).

[0146] 8a illustrates a first chart 800a according to one embodiment of the present disclosure. In connection with the first chart 800a, an AP (e.g., AP1) can be configured to provide information in the time (denoted by “t” in FIG. 8a) and frequency (denoted by “f” in FIG. 8a) domains. Additionally, information regarding an interference impact estimate for each time-frequency (TF) resource block associated with a vulnerable STA (e.g., STA2) can be provided by the AP. In this example, the channel bandwidth of the BSS is 320 MHz, the RU granularity is 20 MHz (i.e., 242 tones), the time granularity is 10 Tu, the reference time is TBTT, and the interference impact estimate is provided for the next beacon interval.

[0147] The information regarding the interference impact estimate may be represented in Figure 8a by the numbers "0", "1", "2", and "3", where "0" may indicate no or negligible impact, "1" may indicate small impact, "2" may indicate medium impact, and "3" may indicate large impact. These numbers (i.e., values ​​"0" through "3") are shown in a first table 802.

[0148] The AP may be configured to determine an estimate of the interference impact based on one or both of the communication schedule and the communication parameters.

[0149] In one example, if the AP determines (based on the communication schedule) that communication is not scheduled, it may derive the number "0."

[0150] In another example, if the AP determines that the transmission power is low and / or the transmission is directed toward a non-vulnerable STA(s) (based on parameters such as "transmission strength / power" / "transmission directivity," which are examples of communication parameters mentioned above), it may derive the number "1."

[0151] In yet another example, if the AP determines that there is a DL type communication to a vulnerable STA(s), it may derive the number "2."

[0152] In yet another example, if the AP determines that there is a UL type communication from a vulnerable STA(s), it may derive the number "3."

[0153] 8b illustrates a second chart 800b according to one embodiment of the present disclosure. In the second chart 800b, (in addition to FIG. 8a) the AP may consider additional elements of geographic information for purposes of determining the interference impact estimate described above. In this example, the BSS channel bandwidth is 80 MHz, the RU granularity is 106 tones, the time granularity is 5 Tu, the reference time is the middle of the beacon interval (i.e., TBTT+50 Tu), and an interference impact estimate is provided for the remaining half of the beacon interval.

[0154] For example, one or both of the first operating area 108 and the second operating area 110 can include multiple zones, which can include a north zone, a south zone, an east zone, and a west zone. Each of the north zone, south zone, east zone, and west zone can indicate a geographic location that includes the operating area (i.e., the first operating area 108 and / or the second operating area 110). For example, in relation to an operating area (e.g., the second operating area 110), a STA (e.g., STA1) can be located at one geographic location (e.g., the west zone), while another STA (e.g., STA3) can be located at another geographic location (e.g., the south zone). An AP (e.g., AP2) associated with the operating area (e.g., the second operating area 110) can be configured to determine the location of the STA within the operating area (e.g., the second operating area 110).

[0155] The information about the interference impact estimate can be represented by the numbers "0" through "11." These numbers (i.e., values ​​"0" through "11") are shown in a second table 804. The AP provides an interference impact estimate for each of the four zones.

[0156] 8c illustrates a third chart 800c according to one embodiment of the present disclosure, which is similar to the second chart 800b in that the AP may take into account the aforementioned geographic information for purposes of determining the aforementioned interference impact estimate.

[0157] Specifically, in the third chart 800c, an AP (e.g., AP1) can determine / plan its (e.g., AP1's) communication schedule in a manner that efficiently reuses the medium (i.e., efficient spatial reuse) in the operating area (e.g., first operating area 108) based on a combination of interference impact estimates and information about the STAs (e.g., STA2, STA4) associated with the AP (i.e., associated with BSS1). To do this, the present disclosure assumes that the APs (AP1 and AP2) in system 100 should be aware of each other's geographic locations (e.g., AP1 should be aware of the geographic location of AP2, and vice versa), and further, that the APs should be aware of the geographic locations of the STA(s) associated with them (e.g., AP1 should be aware of the geographic locations of STA2 and STA4, and AP2 should be aware of the geographic locations of STA1 and STA3). The present disclosure assumes that a device location information element can be used to convey location (i.e., geographic location) information, as described in more detail below with reference to FIG. 9. For example, AP2 may be configured to communicate its location information to AP1 via device location information element 900 of FIG.

[0158] In one example, upon receiving an interference impact estimate from AP2, AP1 can utilize the interference impact estimate element received from AP2 when planning / determining communications to one or more vulnerable STAs (e.g., STA2) associated with AP1 to plan its own transmission schedule such that time-frequency resources with potentially high or medium interference impact are avoided for AP1's vulnerable STAs. For example, when scheduling STA2's transmission, because STA2 is located near the South and East zones of BSS2, it can avoid time-frequency resource blocks with values ​​indicating "high impact—all zones," "medium impact" in the South and East zones, and "high impact" in the South and East zones (e.g., labeled "South and East Zones" in the third chart 800c). Alternatively, more robust coding / modulation schemes can be used when using these time-frequency resources.

[0159] In another example, AP1 may be configured to perform beamforming so that time-frequency resource blocks labeled, for example, "North and West Zones" may be used for communications related to STA2.

[0160] Furthermore, this disclosure assumes that for cell edge type devices such as STA4, which are considered to be far from AP2, there is no need to consider the effects associated with AP2.

[0161] 8d illustrates an example format 800d of an interference impact estimate element (described above in connection with FIGS. 8a-8c) according to one embodiment of the present disclosure. The table below illustrates the encoding of the fields of the interference impact estimate element. [Table 1]

[0162] For octet alignment (i.e. to ensure that elements are multiples of 8 bits), a padding bit field is added at the end.

[0163] Additionally, Figure 8d shows an exemplary Interference Impact Estimate element 805 used to encode timing information from AP1 in Figure 6. In this example, information is provided only in the time domain, so m=1 and each Time Period Info field is 1 bit. Six padding bits are added at the end for octet alignment.

[0164] The present disclosure contemplates that, to assess the accuracy of an interference impact estimate, an AP (e.g., AP1) may be configured to request another AP (e.g., AP2) to provide a record of actual communications for a previous estimation period, which may be illustrated in Figure 8e, according to one embodiment of the present disclosure.

[0165] As shown in FIG. 8e, the “Interference Impact Estimate element” portion of the “Frame Body” of communication frame 800e can be communicated from an AP (e.g., AP2) to another AP (e.g., AP1) and can convey information regarding the actual record of transmissions during the previous beacon interval. In one embodiment, the AP (e.g., AP1) can request its associated cell-edge-type STA(s) (e.g., STA2, STA4) to perform channel measurements during the same period and use the measurement reports from these STAs to evaluate the accuracy of the impact estimate provided by another AP (e.g., AP2). This disclosure assumes that due to contention-based channel access, actual transmissions may differ from the provided transmission schedule, and channel conditions may also vary in various regions of the BSS. The AP can further evaluate the accuracy of the impact estimate provided by another AP by obtaining the actual record of transmissions during a period and comparing it with the measurement reports from its own STAs.

[0166] As previously mentioned, an operating area (e.g., first operating area 108 and / or second operating area 110) may include multiple zones that may indicate geographic locations within the operating area. In this regard, a geographic location may correspond to a geographic zone.

[0167] According to one embodiment of the present disclosure, the present disclosure contemplates that pseudo-zones can be defined instead of geographical zones.

[0168] As shown in FIG. 8f, a zone-based operating region 810 (which may be similar to, for example, the second operating region 110 described above) may include multiple pseudo-zones (labeled “Zone 0,” “Zone 1,” “Zone 2,” and “Zone 3” in FIG. 8f). The zone-based operating region 810 may be associated with an access point (labeled “AP0” in FIG. 8f), which may be considered to be adjacent to one or more other APs (e.g., the first, second, and third APs described above, labeled “AP1,” “AP2,” and “AP3” in FIG. 8f). Additionally, STA1 and STA3 may be associated with the zone-based operating region 810.

[0169] In one embodiment, one or more of the APs (e.g., AP1, AP2, and / or AP3) may be considered to be interfering with the STA(s). This disclosure contemplates that such interfering AP(s) may be configured to avoid using RUs for communications associated with the STA(s) that are deemed to be near a considered high impact zone (which may be based on the interference impact estimates described above). Information regarding the interference impact estimates may be represented by the numbers "0" through "11." These numbers (i.e., values ​​"0" through "11") are shown in a third table 806.

[0170] The pseudo-zones can be defined / classified based on either or both measurements by AP(s) (e.g., AP0) and measurement reports (e.g., distance estimates based on signal strength and / or propagation loss) from STA(s) (e.g., STA1, STA3) about one or more neighboring APs. Alternatively, the ToA (Time of Arrival) or TDoA (Time Difference of Arrival) method can be used to determine the assignment of STAs to zones (assuming the STA is within range of at least three coordinating APs). The ToA method estimates the location of a STA by calculating the time it takes for signals from three or more APs to reach the STA. For example, AP0 can request STA3 to calculate the time it takes to receive special frames (including the transmission times) from multiple APs and report the calculated values ​​to AP0. AP0 can estimate the location of STA3 through triangulation and classify STA3 into one of the zones (e.g., Zone 3).

[0171] The TDoA method estimates the location of a STA by generating a time difference curve of signals from the STA to three or more APs. For example, AP0 can request all neighboring APs to record the time of arrival (ToA) of a special frame transmitted by STA3 and provide that ToA to AP0. If at least AP1 and AP3 provide their ToA to AP0, AP0 can estimate the location of STA3 by also using its own ToA records and classify it into one of the zones (e.g., Zone 3).

[0172] This disclosure contemplates that pseudo-zone classification is useful when an AP has limited or no capability to perform beamforming communications and / or when information regarding the geographic location of the STA(s) is unavailable.

[0173] An example of zone classification is described below with reference to Figures 8g and 8h.

[0174] 8g shows a first classification example 812 based on the RSSI of received beacon frames. The average RSSI of the beacon frames transmitted by the AP can be classified into high (H), medium (M), and low (L) (H can be greater than or equal to -40 dBm, M can be greater than or equal to -65 dBm and less than -40 dBm, and L can be less than -65 dBm). The AP can classify the STA(s) into the appropriate zone(s) based on the RSSI reported by the STA(s).

[0175] FIG. 8h shows a second classification example 814 based on the path loss of the received trigger frame. The average path loss can be classified as high (H), medium (M), and low (L) (H can be 75 dBm or greater, M can be between 65 dBm or greater and less than 75 dBm, and L can be less than 65 dBm). The AP can classify the STA(s) into the appropriate zone(s) based on the path loss reported by the STA(s). The path loss of the trigger frame can be calculated by the STA(s) based on the reduction in received power from the transmitted power.

[0176] Since the definition of a zone may vary from AP to AP, an AP also needs to communicate the definition of the zone to other APs. An AP (the sending AP) can be configured to communicate information regarding the above-mentioned zone classification / identification to one or more other APs.

[0177] As shown in FIG. 8i, according to one embodiment of the present disclosure, an AP cooperation information response frame 816 can be used to convey information regarding the above-mentioned zone classification / identification (denoted as "Zone information element" in FIG. 8i). The transmitting AP can list the interfering APs in each of its zones. As previously mentioned, information regarding the zone classification is useful for obtaining information regarding interference impact estimates.

[0178] An AP listed as an interfering AP in a zone may avoid using time-frequency resources indicated as high and / or medium impact in that zone (e.g., based on the interference impact estimates described above) for communication to its associated STA(s) in order to avoid causing interference. In this manner, the present disclosure believes that more flexible pseudo-zone-based optimized interference mitigation can be facilitated.

[0179] Referring to FIG. 9, a device location information element 900 is shown in accordance with one embodiment of the present disclosure.

[0180] The device location information element 900 can be used to report geolocation information (e.g., associated with AP(s) and / or STA(s)). For example, AP1 can be configured to communicate its location information to AP2 via the device location information element 900. Associated STAs can also report their location information to their APs via the device location information element 900.

[0181] This disclosure contemplates that a single exchange of AP coordination information frames is sufficient since the AP(s) (eg, AP1, AP2) are generally expected to be stationary.

[0182] Furthermore, this disclosure assumes that the STA(s) are mobile. Due to the mobility of the STA, the AP(s) need to periodically inquire about the location of the STA. For example, 11.22.4 (Location Tracking Procedure) or 11.10.9.6 (Location Setting Information Report) defined in Non-Patent Document 1 can be used. In a more specific example, device location information can be defined in Section 9.4.1.56 of Non-Patent Document 1, and all fields therein can be defined in Section 2.2 of Non-Patent Document 2.

[0183] In view of the above, it should be appreciated that the present disclosure contemplates one or more types of scheduling, which may include (i.e., one or more, or any combination of) the following: Scheduling in the time domain, according to one embodiment of the present disclosure. For example, APs can be configured to coordinate the timing of communications, as previously described. Scheduling in the frequency domain, according to one embodiment of the present disclosure. For example, the AP may be configured to coordinate the allocation of the reserved RU(s), as described above. Beamforming-based scheduling, according to one embodiment of the present disclosure. For example, APs can be configured to cooperate based on beamforming, as described above. Spatial reuse based scheduling, according to one embodiment of the present disclosure. For example, APs can be configured to cooperate based on transmit power, as previously described.

[0184] Referring to FIG. 10, an AP 104 (eg, AP1 or AP2) of the system 100 is shown in further detail, according to one embodiment of the present disclosure.

[0185] According to one embodiment of the present disclosure, the AP 104 (e.g., AP1) may include a central processing unit (CPU) 1102 and a communication unit 1104. The CPU 1102 may be coupled to the communication unit 1104. The communication unit 1104 may include (or correspond to) one or both of a transmitter and a receiver (i.e., a transmitter and / or a receiver).

[0186] In another embodiment, the AP 104 may further include a location module 1106, a power module 1108, a memory module 1110, or a secondary storage module 1112, or any combination thereof.

[0187] CPU 1102 may correspond, for example, to circuitry that, in operation, does the following: reserving a subset of the operating frequency bandwidth for at least one communication device 106 that is susceptible to interference when operating within the operating frequency bandwidth; and Scheduling communications associated with at least one communication device 106 based on the reserved subset of the operating frequency bandwidth.

[0188] The present disclosure contemplates that, in one embodiment, the CPU 1102 may be configured to reserve a subset of the operating frequency bandwidth (e.g., a first operating frequency bandwidth associated with BSS1 and / or a second operating frequency bandwidth associated with BSS2) for a group of communication devices (i.e., a group of STAs) that are susceptible to interference when operating within the operating frequency bandwidth.

[0189] In another embodiment, the CPU 1102 can be configured to identify whether one or more communication devices are located on the fringe of an operating area (e.g., fringe area 108b of the first operating area 108) and whether the communication devices located on the fringe of the operating area are susceptible to interference. In one example, the communication device(s) identified as being located on the fringe of the operating area can correspond to cell-edge type devices. The CPU 1102 can be configured to reserve a subset of the operating frequency bandwidth (e.g., the first operating frequency bandwidth associated with BSS1) for the cell-edge type devices.

[0190] In one example, the group of communication devices may correspond to STA2 and STA4 mentioned above, in connection with which a subset of the first operating frequency bandwidth (associated with BSS1) is reserved.

[0191] In another example, the group of communication devices may correspond to STA1 and STA3 mentioned above, in connection with which a subset of the second operating frequency bandwidth (associated with BSS2) is reserved.

[0192] The present disclosure contemplates that the CPU 1102 may be further configured to schedule communications (e.g., transmissions) associated with at least one communication device (e.g., STA2) within the group of communication devices (e.g., STA2 and STA4) based on the reserved subset of the operating frequency bandwidth (e.g., in connection with a first subset of the operating frequency bandwidth being reserved).

[0193] The communication unit 1104 may include (or correspond to) one or both of a transmitter and a receiver (i.e., a transmitter and / or a receiver), as previously described. Specifically, the communication unit 1104 may correspond to, for example, an AP-to-AP communication unit, a wired interface unit (denoted "Wired I / F"), or a wireless unit (denoted "Wireless I / F"), or any combination thereof. The wireless interface unit may include one or more sub-modules, such as a STA grouping sub-module (denoted "STA grouping module"), an RU management sub-module (denoted "RU management module"), and / or a PHY sub-module (denoted "PHY").

[0194] The STA grouping submodule may be configured to perform the task of grouping related STAs (e.g., the aforementioned vulnerable STAs, cell-edge type STAs, and / or zones). The STA grouping submodule may further be configured to request (e.g., by communicating a request signal) the STA(s) to perform one or more measurement-related tasks (e.g., interference measurement, path loss measurement, RSSI, and / or SINR). The STA grouping submodule may further be configured to collect measurement reports generated by the STAs in connection with the measurement-related tasks (e.g., by receiving one or more feedback signals communicated from the STAs).

[0195] The RU management module may be configured to determine RUs (e.g., the cell edge resource unit set 114 of BSS1 described above) to be reserved for a STA or group of STAs. The RU management module may further be configured to allocate RUs from communications associated with the STA or group of STAs. In an embodiment in which the AP 104 corresponds to a multi-AP coordinator, the RU management module may further be configured to determine RU(s) associated with one or more other APs to facilitate communications.

[0196] The AP-to-AP communication module may be configured to transmit and / or receive AP-to-AP messages (e.g., signals to be transmitted to and / or received from one or more other APs), which may be transmitted and / or received via wired and / or wireless units.

[0197] The location module may be configured to determine / generate information regarding geographic location and / or collect information related to the location of the STA(s) (e.g., via feedback signals from the STA(s)).

[0198] In one aspect of the present disclosure, the communication unit 1104 may correspond to a transmitter that, in operation, transmits information of a reserved subset of the operating frequency bandwidth. The transmitter may be configured to transmit (e.g., by one or more signals) information of the reserved subset of the operating frequency bandwidth via at least one of a beacon frame and a probe response frame (i.e., via one or both of a beacon frame and a probe response frame).

[0199] The communication unit 1104 may correspond to a receiver in another aspect of the disclosure, as will be described in more detail below.

[0200] The communication unit 1104 may correspond to a transmitter and a receiver in yet another aspect of the disclosure.

[0201] In one embodiment, the reserved subset of the operating frequency bandwidth may correspond to at least one reserved resource unit (RU). Further, the transmitter may be configured to transmit (e.g., via one or more signals) information of the at least one reserved resource unit to another AP. This other AP may correspond to "AP2," for example, if AP 104 corresponds to "AP1."

[0202] The communication unit 1104, in one embodiment, may further correspond to a receiver that, during operation, receives information of another reserved subset of the operating frequency bandwidth (e.g., a second operating frequency bandwidth associated with BSS2) communicated from another AP (e.g., AP2). The CPU 1102 may be configured to take the other reserved subset into account when reserving the subset of the operating frequency bandwidth for the group of communication devices.

[0203] In one embodiment, the receiver can be configured to receive a request signal (e.g., from another AP, AP2). The CPU 1102 can be configured to generate a record of transmissions in a preceding transmission period associated with the AP 104 based on the received request signal. The transmitter can be configured to transmit (by one or more signals) the record of transmissions to another AP (e.g., AP2).

[0204] In one embodiment, the CPU 1102 may be further configured to generate transmission timing information associated with the group of communication devices, and the transmitter may be further configured to transmit (by one or more signals) this transmission timing information to another AP (e.g., AP2).

[0205] In one embodiment, the CPU 1102 may be configured to determine whether a communication device (e.g., STA2) in a group of communication devices (e.g., STA2 and STA4) is susceptible to interference based on at least one report generated by the communication device (e.g., STA2). The report may correspond to, for example, a bandwidth query report and / or an interference report (i.e., a bandwidth query report and / or an interference report).

[0206] In one embodiment, the CPU 1102 can be configured to determine whether a communication device (e.g., STA2) in a group of communication devices (e.g., STA2 and STA4) is located on the fringe of an operating region associated with an operating frequency bandwidth (e.g., a first operating frequency bandwidth associated with BSS1) based on one or both (i.e., at least one of the following): Estimated distance of the communication device from AP 104 At least one report generated by a communication device (e.g., STA2) indicating signal strength

[0207] In one embodiment, CPU 1102 may be configured to provide an estimate of interference impact based on transmission timing information associated with a group of communication devices (eg, STA2 and STA4).

[0208] In one embodiment, a group of communication devices (eg, STA2 and STA4) may be divided into multiple subgroups based on any of the following: A geographical location within an operating region associated with an operating frequency bandwidth (e.g., a first operating frequency bandwidth associated with BSS1). At least one report from at least one communication device (e.g., STA2) in the group of communication devices (e.g., STA2 and STA4) regarding at least one measurement of at least one characteristic (e.g., signal strength) associated with at least one wireless signal transmitted within the operating area.

[0209] As mentioned above, the present disclosure contemplates that, in another aspect of the present disclosure, the aforementioned communication unit 1104 may correspond to a receiver.

[0210] In this regard, in another aspect of the present disclosure, it is assumed that the AP 104 (e.g., AP1) may include a receiver that, in operation, receives information of a reserved subset of an operating frequency bandwidth (e.g., a second operating frequency bandwidth associated with BSS2) from a second AP (e.g., AP2). The first AP 104 may further include circuitry (i.e., circuitry corresponding to the aforementioned CPU 1102) that, in operation, performs at least one of the following (i.e., one or both): Scheduling communications of at least one communication device (e.g., STA2) in a group of communication devices (e.g., STA2 and STA4) susceptible to interference from communications associated with the operating frequency bandwidth based on the received information. Adjusting the transmit power of signals transmitted from the first AP 104 that are associated with the reserved subset of the operating frequency bandwidth.

[0211] In one embodiment, the first AP 104 may serve as a coordinator AP (i.e., master AP) for a second AP (i.e., slave AP). As previously described, the master AP may be configured to communicate a master trigger frame (MTF), which may indicate instructions for the slave AP to initiate communication (e.g., UL transmission) from a vulnerable STA associated with the master AP (e.g., STA2) and allocate a first cell-edge RU set to be used for the communication (e.g., UL transmission). Additionally, the master AP may be configured to allocate a second cell-edge RU set to be used for communication (e.g., UL transmission) with a vulnerable STA associated with the master AP (e.g., STA3).

[0212] Referring to FIG. 11, a communication device 106 (eg, a STA such as STA1, STA2, STA3, STA4, etc.) of the system 100 is shown in further detail, according to one embodiment of the present disclosure.

[0213] According to one embodiment of the present disclosure, a communication device 106 (e.g., STA1) (hereinafter simply referred to as "STA" (also referred to as STA 106)) may include a central processing unit (CPU) 1202 and a communication unit 1204. The CPU 1202 may be coupled to the communication unit 1204. The communication unit 1204 may include (or correspond to) one or both of a transmitter and a receiver (i.e., a transmitter and / or a receiver).

[0214] The communication unit 1204 may include a measurement module 1206, which may be configured to perform the aforementioned measurement-related tasks (e.g., interference measurement, path loss measurement, RSSI, and / or SINR) based on, for example, a request (e.g., via a transmitted request signal) from an AP (e.g., AP2). In another example, the measurement module 1206 may be configured to autonomously perform the aforementioned measurement-related tasks and communicate measurement reports to the AP.

[0215] The STA 106 may further include a location module 1208 that may be configured to determine the geographic location of the STA 106 .

[0216] 12, a communication method 1300 according to one embodiment of the present disclosure is shown. The communication method 1300 may be associated with the system 100 according to one embodiment of the present disclosure.

[0217] In one embodiment, the communication method 1300 may include a reserving step 1302, a scheduling step 1304, and a transmitting step 1306. In another embodiment, the communication method 1300 may further include a determining step 1308.

[0218] In a reservation step 1302, a subset of the operating frequency bandwidth (e.g., a first operating frequency bandwidth associated with BSS1) may be reserved for a group of communication devices (e.g., STA2 and STA4) that are susceptible to interference when operating within the operating frequency bandwidth. The reserved subset of the operating frequency bandwidth may correspond, for example, to at least one reserved resource unit (RU).

[0219] In a scheduling step 1304, communications associated with at least one communication device (e.g., STA2) within the group of communication devices (e.g., STA2 and STA4) may be scheduled based on the reserved subset of the operating frequency bandwidth.

[0220] In a transmitting step 1306, information about / associated with the reserved subset of the operating frequency bandwidth may be transmitted, for example, information about at least one reserved RU may be transmitted to an access point (AP).

[0221] In a determining step 1308, it may be determined whether the communication device (e.g., STA2) belongs to a particular group of communication devices (e.g., cell-edge STAs). For example, the determining step may include determining whether the communication device (e.g., STA2) is located on the fringe (e.g., fringe region 108b of the first operating region 108) of an operating region (e.g., the first operating region 108).

[0222] In one embodiment, the determination may be based on an estimated distance from an AP (eg, AP1) to the communication device (eg, STA2).

[0223] In another embodiment, the determination may be based on at least one report generated by a communication device (eg, STA2) indicating signal strength.

[0224] In yet another embodiment, the determination may be based on both an estimated distance from the AP (e.g., AP1) to the communication device (e.g., STA2) and at least one report generated by the communication device (e.g., STA2) indicating signal strength.

[0225] As another example, the determining step may include determining whether the communication device (e.g., STA2) belongs to a group of vulnerable STAs. This determination may be made based on interference measurement reports collected from the STAs, with STAs reporting interference levels above a certain threshold being considered vulnerable STAs.

[0226] The present disclosure can be implemented by software, hardware, or software operating in conjunction with hardware. Each functional block used in the above-described embodiments can be implemented, in whole or in part, by an LSI such as an integrated circuit. Each process described in each embodiment can be controlled, in whole or in part, by the same LSI or a combination of LSIs. The LSI can be formed as an individual chip, or a single chip can be formed to include some or all of the functional blocks. The LSI can include a data input / output unit coupled to it. Depending on the level of integration, the LSI can also be referred to as an IC, system LSI, super LSI, or ultra LSI. However, the technology for implementing an integrated circuit is not limited to LSI, and can be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (field programmable gate arrays), which can be programmed after LSI fabrication, and reconfigurable processors, which can reconfigure the connections and settings of circuit cells arranged within the LSI, can also be used. The present disclosure can be implemented using digital or analog processing. If, as a result of advances in semiconductor technology or other derivative technologies, LSI is replaced by future integrated circuit technologies, these future integrated circuit technologies can be used to integrate functional blocks. Biotechnology can also be applied.

[0227] The present disclosure may be implemented by any type of apparatus, device, or system having communication capabilities (referred to as a communication apparatus).

[0228] A communication device may include a transceiver and processing / control circuitry. The transceiver may include and / or function as a receiver and a transmitter. As a transmitter and receiver, the transceiver may include an RF (radio frequency) module including an amplifier, an RF modulator / demodulator, etc., and one or more antennas.

[0229] Some non-limiting examples of such communications devices include telephones (e.g., mobile phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, e-readers, telehealth / telemedicine devices, vehicles (e.g., automobiles, airplanes, ships) that provide communications capabilities, and various combinations thereof.

[0230] Communication devices are not limited to portable or mobile devices, but can also include any type of non-portable or fixed equipment, device, or system, such as smart home devices (e.g., appliances, lights, smart meters, control panels), vending machines, and any other "thing" in an "Internet of Things" (IoT) network.

[0231] Communication can include, for example, exchanging data through cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

[0232] A communications device may include devices such as a controller or a sensor coupled to the communications device to perform the communications functions described in this disclosure. For example, a communications device may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications device.

[0233] The communications apparatus may further include infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicate with or control apparatuses such as the apparatuses in the non-limiting examples above.

[0234] Although some features of various embodiments are described with reference to devices, corresponding features also apply to the methods of various embodiments, and vice versa.

[0235] It will be appreciated by those skilled in the art that numerous changes and / or modifications may be made to the present disclosure as set forth in the specific embodiments without departing from the spirit or scope of the disclosure as broadly described, and the embodiments herein are therefore to be considered in all respects as illustrative and not restrictive.

[0236] Those skilled in the art will appreciate that variations and combinations of the above-described features are not alternatives or permutations, but may be combined to form further embodiments.

[0237] Various embodiments of the present disclosure have been described above to address at least one of the above-mentioned shortcomings. Such embodiments are intended to be encompassed by the following claims and are not limited to the specific forms or arrangements of parts described herein. Numerous changes and / or modifications may be made, as will be apparent to those skilled in the art in light of this disclosure, and these changes and / or modifications are also intended to be encompassed by the following claims.

Claims

1. An access point (AP), When in operation, reserving a subset of the operating frequency bandwidth for a group of cell-edge type communication devices; and scheduling communications associated with at least one cell-edge type communication device in the group of cell-edge type communication devices based on the reserved subset of the operating frequency bandwidth; The circuit and a transmitter that, in operation, transmits information on the reserved subset of the operating frequency bandwidth; Equipped with The classification of the cell edge type communication device is based on channel path loss, received signal strength indicator (RSSI), or signal-to-interference-plus-noise ratio (SINR). AP.

2. the reserved subset of the operating frequency bandwidth corresponds to at least one reserved resource unit (RU); the transmitter is configured to transmit information of the at least one reserved resource unit to another AP; The AP according to claim 1 .

3. a receiver that, in operation, receives information about another reserved subset of the operating frequency bandwidth communicated from another AP; It also has the circuitry is configured to take into account the other reserved subset when reserving the subset of operating frequency bandwidth for the group of cell-edge type communication devices. The AP according to claim 1 .

4. the receiver is further configured to receive a request signal; the circuitry is configured to generate a record of transmissions associated with the AP during a preceding transmission period based on the received request signal; the transmitter is configured to transmit a record of the transmission to the other AP; The AP according to claim 3.

5. the transmitter is configured to transmit information of the reserved subset of the operating frequency bandwidth in at least one of a beacon frame and a probe response frame. The AP according to claim 1 .

Images