> when they throttle in areas with weak cell signal, the throttling is aggressive and internet practically doesn't work.
I want to add in for those that don't know. There's a difference between throttling and deprioritization. Throttling usually kicks in as some specified speed at the IP network's level(like 256kbps). This isn't going to make a difference whether you're close to a tower or far away. It will make a massive difference on your battery life if your user equipment has to stay transmitting forever to complete transfers (this is a big problem when roaming on t-mobile's throttled international plans, battery life is obliterated).
Deprioritization is very different. The radio layer (called radio access network) of the tower (specifically the sector) that you're connected to controls how much time your device gets using a QoS scheduler. Stuff like voice always takes priority no matter what, since it all goes over the same data network now. I'm going to try to explain this below in easier to comprehend language...
In LTE, resources can be allocated out to a device as resource blocks. Each layer allows up to 100 physical resource blocks at any given time. Depending on the quality of the signal (how far away you are and how many people are using it), the blocks can be broadcast at different MCS levels. This controls the amount of error correction and the amount of data that can be carried per resource block. So when you're stuck at cell fringes and only allowed to get less than 5 resource blocks at an instant, the transfer rates will be slow. When you're close and allowed to use higher orders of modulation with less error correction (256QAM broadcast 4x4 MIMO), the performance loss isn't going to be as noticeable.
Deprioritization can be worked around by connecting to a different sector that isn't as busy. It's also assessed pretty quickly, something like 20ms the radio scheduling happens. Sprint's the only network afaik that posts something even slightly technical to the general public: https://www.sprint.com/en/legal/open-internet-information.ht...
I want to add in for those that don't know. There's a difference between throttling and deprioritization. Throttling usually kicks in as some specified speed at the IP network's level(like 256kbps). This isn't going to make a difference whether you're close to a tower or far away. It will make a massive difference on your battery life if your user equipment has to stay transmitting forever to complete transfers (this is a big problem when roaming on t-mobile's throttled international plans, battery life is obliterated).
Deprioritization is very different. The radio layer (called radio access network) of the tower (specifically the sector) that you're connected to controls how much time your device gets using a QoS scheduler. Stuff like voice always takes priority no matter what, since it all goes over the same data network now. I'm going to try to explain this below in easier to comprehend language...
In LTE, resources can be allocated out to a device as resource blocks. Each layer allows up to 100 physical resource blocks at any given time. Depending on the quality of the signal (how far away you are and how many people are using it), the blocks can be broadcast at different MCS levels. This controls the amount of error correction and the amount of data that can be carried per resource block. So when you're stuck at cell fringes and only allowed to get less than 5 resource blocks at an instant, the transfer rates will be slow. When you're close and allowed to use higher orders of modulation with less error correction (256QAM broadcast 4x4 MIMO), the performance loss isn't going to be as noticeable.
Deprioritization can be worked around by connecting to a different sector that isn't as busy. It's also assessed pretty quickly, something like 20ms the radio scheduling happens. Sprint's the only network afaik that posts something even slightly technical to the general public: https://www.sprint.com/en/legal/open-internet-information.ht...