T-Mobile Merger/5G NR Deployment
5 topics in this forum
-
- 7.4k replies
- 259.6k views
-
- 40 replies
- 1.6k views
-
- 8 replies
- 355 views
-
- 16 replies
- 531 views
-
- 1 reply
- 301 views
-
-
New Topics
-
-
Trending Topics
-
-
Recent Posts
-
If they trade it'll be AT&T most likely since they own the B block and Bluegrass has C block. -
By Paynefanbro · Posted
Initially T-Mobile was simply slapping n41 panels onto existing sites which meant that NR+LTE aggregation aggregated all available LTE bands with NR. Now, T-Mobile seems to be replacing 600/700MHz antennas every time they add n41 and as a result, the city is getting covered in split eNB IDs. On a local (legacy) 600MHz site by my home, when I connect to n71 it's n71 + Band 2 + Band 66 + Band 71 or Band 12 for a combined total of 50MHz of spectrum. However on my home site, because of the split eNB, when I force my phone to connect to n71 it only aggregates n71 + Band 2 + Band 66 for a total of 45MHz of spectrum. It seems weird that T-Mobile is allowing this to happen instead of fixing it so that they can squeeze as much performance out of their network as possible. 5MHz of LTE is not much but it's still an extra ~37Mbps of speed and capacity that could be provided in NSA mode. Interestingly this problem is not something I experience in LTE-only mode much anymore. My phone seems to have no issue aggregating LTE bands across the split most of the time. Another thing that has been bothering me is that according to the FCC dashboard T-Mobile has 400MHz of spectrum in the 39GHz band here in NYC that they won in December of 2019 but they haven't done any upgrades to actually use that spectrum here. Instead they've been relying on the two 50MHz blocks aggregated together in the 28GHz band which performs worse than n41 on average. -
By bookertdub · Posted
Ah okay. Thank you for the clarification.
-
-
Recently Browsing
No registered users viewing this page.
