Low-frequency 5G is going to be broadly deployed and will replace LTE over time. High-frequency (mmWave) 5G will be much harder to deploy due to its very limited range; that is what will enable the dramatic increase in bandwidth available. The 5G NR air interface is designed to support extremely large number of devices; this means that regardless of the spectrum used; performance in scenarios like crowded transit terminals and massive IoT communications will see substantial improvements.
Device capacity is only part of the story, though.
Until the high-frequency 5G cells are widespread, the performance advantage visible to the end user is going to be limited. We're probably going to see these mmWave cells in places like crowded transit terminals and sports arenas first precisely because that's where the highest demand for bandwidth is.
Users will see performance improvements both upon initial launch of 5G service and over time, but it'll probably take 5-10 years and massive investments for the full benefit to be realized by the majority of users.
> Simulation of standalone eMBB deployments showed improved throughput by 2.5× below 6 GHz and by nearly 20× at millimeter waves.
The thing that matters for the next couple of years is going to be that 2.5× number. As mmWave cells proliferate, we'll see performance ramp up dramatically.
Regardless, I'm going to be upgrading from an LTE Cat. 6 device, which is actually pretty anemic when you compare it to the "gigabit LTE" (Cat. 16) devices currently available.
While my mobile carrier (T-Mobile) has been busy adding mid-band (bands 2 and 4) spectrum capacity across New York City and elsewhere over the past several months, resulting in visible improvements in cellular data performance (both bandwidth and latency) even on this old (2016) device, it's going to pale in comparison to a modern Cat. 16 gigabit LTE device, let alone 5G.
@JourneymanGeek THREE YEARS. THREE LONG YEARS I HAVE BEEN A PART OF THIS CHAT ROOM. DO THEY MEAN NOTHING TO YOU!?!?!?!?!?! HOW CAN YOU JUST DISREGARD IT ALL!?!?!?!?!!??
Inspired by this superuser.com/questions/1408123. Should a Linux user/geek know script syntax of every "pid = 1" systems? I'm familiar with systemd .service file.
Looking at their discussion of OFDMA, it seems this technology enables overlapping time slices. Am I understanding this correctly?
I've always understood this as simply a way of encoding data that allows the router to handle more devices at the same time, but I'm not too familiar with how it works.
(enhanced MU-MIMO in 802.11ax is not a mystery to me, and I'm well aware that the new standard allows up to eight devices to share a time slice)
Maybe @FMLCat (our resident wireless expert :P) understands this better?
(somebody tell @FMLCat that I no longer need to be blocked)
> OFDMA subdivides a channel into smaller frequency allocations, called resource units (RUs). By subdividing the channel, parallel transmissions of small frames to multiple users can happen simultaneously.
Oh, wow. So basically, the router can use small bits and pieces of the spectrum to communicate with multiple devices simultaneously?
A common misconception about #Linux swap spaces is that putting one on an SSD will quickly exhaust its endurance and kill it. This is simply not true for the vast majority of use cases: https://bwdraco.blogspot.com/2019/02/using-ssd-as-linux-swap-device-isnt.html #solidstatedrive #linuxswap