[New Feature - 5.10.0] Asymmetric Uplink Bandwidth

Affected platforms: AX
Affected versions: 5.10.0 and newer

The Asymmetric Uplink Bandwidth feature is introduced for ePMP 4xxx/Force 4xxx. This feature allows configuring a narrower Uplink channel bandwidth while the Access Point (AP) continues operating on a wider Downlink channel. The Uplink channel remains within the same frequency range as the Downlink transmission.
Implementing asymmetric channel bandwidth enhances spectrum efficiency, reduces interference, and improves overall network performance. The primary objective is to achieve higher Modulation and Coding Schemes (MCSs) while minimizing the Uplink retransmission rate, even at the cost of channel bandwidth.

The following configurable feature can be enabled or disabled via the AP GUI:

  • Asymmetric Uplink Bandwidth Enable/Disable
  • Asymmetric Uplink Bandwidth (MHz)
  • Asymmetric Uplink Central Frequency (MHz)

To configure the Asymmetric Uplink Bandwidth:
Navigate to AP > Configuration > Radio.

To view the status, navigate to AP > Monitor > Wireless.

To view the SM status, navigate to SM > UI > Status.

Perform the following to configure Asymmetric Uplink Bandwidth on the AP through cnMaestro Template:

{
"device_props": {
"asymBwEnable": "1",
"asymBwPrimaryFreq": "6675",
"asymBwUplinkBw": "5"
}
}

ClI configuration:

E4600_4x4_f00ae1>config set asymBwEnable 1
E4600_4x4_f00ae1>config set asymBwPrimaryFreq 6605
E4600_4x4_f00ae1>config set asymBwUplinkBw 1
E4600_4x4_f00ae1>config commit
E4600_4x4_f00ae1>config show | asy
asymBwEnable                             1
asymBwMode                               0
asymBwPrimaryFreq                     6705
asymBwUplinkBw                           5

Corresponding MIB objects:

asymBwEnable OBJECT-TYPE
SYNTAX
Integer32 (0|1)
MAX-ACCESS
read-write
STATUS
current
DESCRIPTION
"Enable Asymmetric Bandwidth:
0 - Disable,
1 - Enable
Device Allocation: AP, SM"
DEFVAL { 0 }
::= { cambiumAsymBw 1 }

asymBwMode OBJECT-TYPE
SYNTAX
Integer32 (0|1)
MAX-ACCESS
read-write
STATUS
current
DESCRIPTION
"Mode of Asymmetric Bandwidth:
0 - Manual mode,
1 - Automatic mode
Device Allocation: AP"
::= { cambiumAsymBw 2 }

asymBwPrimaryFreq OBJECT-TYPE
SYNTAX
Integer32 (4800..7200)
MAX-ACCESS
read-write
STATUS
current
DESCRIPTION
"Primary frequency for Asymmetric Bandwidth.
Device Allocation: AP"
::= { cambiumAsymBw 3 }

asymBwUplinkBw OBJECT-TYPE
SYNTAX
Integer32 (0|1|2|5|6)
MAX-ACCESS
read-write
STATUS
current
DESCRIPTION
"Uplink bandwidth for Asymmetric Bandwidth.
0 - auto
1 - 20 MHz
2 - 40 MHz
5 - 80 MHz
6 - 160 MHz
Note: The UL Bandwidth configuration cannot be wider than the channel
bandwidth.
Device Allocation: AP"
::= { cambiumAsymBw 4 }
  • Not supported on DFS channels but works with FCC channels.
  • Compatibility with ePMP 3xxx/Force 3xx may be limited in the first Beta release.
  • SMs may not correctly apply Uplink bandwidth narrowing in certain cases.
6 Likes

So in theory could I have two 80mhz APs running the same channel front to back and have each of them running a 40mhz uplink with one on the upper 40mhz and one on the lower 40mhz and by doing that maybe be able to increase the signal received at the AP?

Right now with front to back I usually have to have the AP RX signals set to around -60db to limit interference from the opposite side, which of course limits the UL modulation rates. If I can have say the front AP receive on the lower 40mhz of an 80mhz channel and the other AP receive on the upper 40mhz of an 80mhz channel I could instead allow the AP RX signals to be stronger and increase the UL modulation?

1 Like

Does this mean that Force300s connected to a 4500 AP that is using Asymmetric Uplink Bandwidth will work but at the full bandwidth size or will they simply not connect to the AP?

1 Like

Will work at the full bandwidth.

Thanks

This is brilliant. This’ll be great for those busy towers!
Does this work in ePTP links, as well as TDD modes?

TDD and TDD PTP only at that moment.

Thank you.

1 Like

Tested, works. This is a real silver bullet game changer for us. Speedtest loves no retransmissions on the uplink channel, gamers love no retransmissions.
Better jitter, better ping for all those with transmitters high and a lot of noise around.

4 Likes

That’s ok for now - I was asking because of some F-300c backhauls which we’re going to upgrade to AX as soon as there is 4500AP to 300SM compatibility. But I’m going to go to 4500L Masters and Sync all those backhauls, so TDD PTP will be perfect for that project anyway. This is a GREAT feature - it’s a game changer level feature.

1 Like

In case anyone else is wondering how this affects Force 300 clients connected to a 4500 AP, this feature does still function, albeit the F300 client’s upload stays on the full channel width (which I’m guessing is a hardware limitation on the F300). BUT - the good news is this feature still functions on a mixed PtMP 4500 series AP with a mix of 300 & 4525 SM flavors.:+1:

3 Likes

It’s not the hardware limitation.
F300s connected to ePMP45xx will support this feature in the next Beta release.

Thank you.

3 Likes

Oh, that’s great Fedor. Thanks! This is is a Kickass feature! I’m trying currently on one AP which allowed me to go to 80Mhz on the download and keep the upload at 40Mhz and performance is great!

1 Like

We would really appreciate it if you could share some Before and After statistics.

Thank you in advance.

Some of the clients who already had low retransmissions look about the same, but some other clients have significantly less retransmission. For example, this guy has gone from 10-20% retransmissions, to 3-5% retransmissions, and it’s very clear on this graph when I switched the firmware and turned on Asymmetric Uplink about 4 Hours ago.

And client performance is pretty good - here’s a couple tests.


Of course, I don’t know if this throughput is better throughput or not (and of course, upload throughput should be actually lower than it would be at 80Mhz/80Mhz, since the upload is now 40Mhz). This AP is currently set at a duty cycle of 75%/25% and set at 80Mhz/40hz so with the upload bandwidth being set at 1/2 the channel width, so I guess that essentially makes the expected throughput split more like 88%/12% in a way, even though the duty cycle is still 75%/25% time. Most often, clients don’t use their 25% upload to capacity, so being able to free up the spectrum is a very efficient feature to have available. And clearly it can make a significant difference in retransmissions for some clients bumping into noise.

I’ll have to do some testing with 70/30 and 65/35 and 60/40 duty cycles and see what results I get from that too.

1 Like

Sometimes, changing the uplink channel disrupts downlink operation — causing modulation drop. Tested on 80 MHz channels and ePMP 4500. Restoring the uplink to the previous position immediately fixes download on the SM.

2 Likes

We will try to get it replicated in the lab.
Thank you for the heads up!

I have seen the same execept in some cases I had SMs whose DL rates were not fixed until I rebooted the SM.

Hi @2jarek and @terintamel,

we have a fix for DL drop after narrowing UL bandwidth.
It is incorporated into 5.10.1-RC9. It was tested in lab and works as expected. 5.10.1 is about to be beta.
I will really appreciate if you can try in your production as well.

@aka I loaded this FW on an AP with 3 SMs. So far going to 40mhz uplink and 80mhz downlink I do not see a drop in DL modulation.

However, there is one issue where it seems Dual SM Link tests no longer work on this FW.

I run the link test but it only gives results for one SM. It is not a reporting error as I logged into the 2 SMs and watched the throughput chart during the dual SM test and only one SM showed the test traffic.

1 Like

Whatever changes were made are performing even better, especially in noisy conditions. Retransmissions are fewer and asymmetric channels are working better. We’ll keep testing gradually.


4 Likes

Is this feature available for e3k?