wispiANt

25 minutes ago, PythonFanPA said:

Maybe its just me, but 'staggering' wouldn't be an adjective I'd use to describe peak upload at 200Mbps.   Not saying its bad either, but to reach 'staggering' as the no-hesitation descriptor I'd expect minimum 500 I guess heh.

You'd need ~800MHz of mmWave to hit a per-UE max of 500Mb/s. I don't think T-Mobile has more than 400MHz of a single band in Clark county.

2 hours ago, transitwatch889 said:

I've noticed this too and I wasn't sure if it was because I'm on Boost infinite with a lower prioritization or with the actual Network itself. Because I have a Boost infinite Sim that's for T-Mobile. And I have a visible esim line so on my s23 ultra it actually switches over to the visible line once the data on my main number which is the Boost infinite over T-Mobile is completely not usable which happens very often when I'm traveling through the subway Network.

I'm on postpaid and it's been awful for me, as well. W4th is especially bad, I don't think I've gotten usable service there in at least 2 years. But that may be a separate issue.

2 hours ago, Paynefanbro said:

I might be wrong but I think this is actually a new antenna and it's live. I drove by the site this evening and it seems like I'm actually picking up n41 from it. I think gNB ID 1345521 and eNB 219025 both map to this site. Is this a passive 8-port antenna? I'm gonna swing by again tomorrow to see if I can figure out what's up with this site.

Looks like a passive 4-port (plus two RET ports). Reading the DOBNow filing:
 

Quote

Remove 6 RRHs, install 3 RRHs

I'd guess they've installed two 4460s (4x4 MIMO B2/B66) and a single 8863 (8x8 MIMO B41, split between the two sectors).

On 10/26/2023 at 5:00 PM, wispiANt said:

Threw this together today as I noticed it'd been a while since I had last updated the oDAS map. This should make it significantly easier to update in the future. I'm planning on implementing some basic filtering options later this weekend. 

Let me know if there are any features you'd like to be added (or if you have any older datasets you'd like to see included).

Filtering implemented.

Threw this together today as I noticed it'd been a while since I had last updated the oDAS map. This should make it significantly easier to update in the future. I'm planning on implementing some basic filtering options later this weekend. 

Let me know if there are any features you'd like to be added (or if you have any older datasets you'd like to see included).

Backhaul on eNB 40986 has been upgraded, as well.

15 hours ago, Paynefanbro said:

From what I've seen in some Ericsson PDFs the currently installed 22xx radios support LTE (FDD+TDD) and LAA alongside 5G via software update but I'm not certain what bandwidth on NR. The 44xx radios on the other hand support up to 6 LTE carriers (FDD+TDD) and up to 100MHz on NR but they don't support LAA.

In a previous post you mentioned that you saw 120MHz n41 on a small cell which makes me wonder how they managed to do that given the bandwidth constraints of the currently installed antennas. The small cells are also broadcasting LAA as far as I can tell.

 

 

There's a user on the Cellmapper Reddit who seems to be a tower/small cell tech here in NYC and he mentioned a while back that he hadn't seen any of the designs for the new T-Mobile 5G nodes yet. Hopefully he'll be able to provide some insight in the future.

My guess would be:
- 1x Micro Radio 2205 (LAA)
- 1x Micro Radio 4402 (B66)
- 1x Micro Radio 4402 (B2)
- 1x Micro Radio 4408 (B41)

Alternatively, they could use an AIR 4435 for B41 but that would likely necessitate the removal of the Micro Radio 2205 (as the 4435 is almost exactly the size of two Micro Radio units, as seen here). 

The 4408 supports an NR carrier bandwidth of up to 100MHz, but an IBW of up to 150MHz. So combinations of 100+20MHz or 100+40MHz should be possible.

The 4402 recieved NR certification earlier this month. Per the FCC documentation:

Quote

It supports channel bandwidths of 5 MHz for WCDMA, 200KHz for NB-IoT standalone, 1.4, 3, 5, 10, 15 and 20 MHz for LTE and 5,10,15,20,25,30,40MHz for NR.

3 hours ago, Dkoellerwx said:

Edited: The newer Ericsson n41 antennas do appear to have a different design than what I normally see. I guess I've only ever seen the Nokia deployment and older Ericsson ones. Not used to seeing those two distinct sections/ridges on the back of the antenna.

That's actually an older Ericsson 6449. The newer model is the Ericsson 6419, pictured below.

eNB 880577 is a Sprint conversion at 419 East 81st Street.

---

The Dish network appears to be live across the city and a handful of sites have popped up on CellMapper. Performance seems to be good.
 

Not sure if this is common knowledge, but I've noticed a good number of the new Verizon oDAS nodes have labels designating site ID info. Here are two instances - one from a node in Windsor Terrace and another from a node in Clinton Hill.


 

---

Additionally, I've spotted the Dish PLMN broadcasting in parts of Brooklyn and Manhattan. I'm unable to manually connect, but hopefully this means the network is going live soon.

---

And one more gig+ site: eNB 128069 in Bedstuy.

On 5/8/2023 at 8:29 PM, T-MoblieUser207 said:

Eventually I'll take a trip to the Bronx to check how the towers with the CBRS panel are doing.

If you're planning on heading up to the Bronx, here's a site you should probably check out. C-Band, CBRS, and n41.

n25 SA was added via a carrier configuration update. And it looks as though n261 NSA was removed.

16 hours ago, xmx1024 said:

Is there a map of current n77 deployments? I know all are test sites but just curious.

https://goo.gl/maps/iHPRYLbNrkcAgxLP9

34 minutes ago, Paynefanbro said:

eNB ID 331116

I'm pretty sure this is a newly-constructed site at the fire station (FAA filing here).

Permit filed to decomm the Sprint site at 304 Boerum St. So I guess we can take that off the "keep" list.

n78 NSA was added for the T-Mobile firmware (S21U). Still no n25 SA.

6 hours ago, Paynefanbro said:

Are T-Sprint eNB 839727-49 and T-Mobile eNB 58563-3/13 the same small cell?

eNB 58653 is a macro site. Be sure to double-check the Streetview dates when you're locating oDAS nodes. The CC-NG node a block away is very likely T-Mobile, but it can't be eNB 58653 as that eNB was first mapped in Sept 2020 but Streetview shows there was no equipment on the pole as late as Oct 2021.

Similarly, Verizon eNB 81621-2/22/24 can't be the same as T-Mobile eNB 129525-5/15 as the Verizon node was first mapped in Dec 2016 but there was no equipment on the pole as late as June 2019.

19 minutes ago, dkyeager said:

I think a massive MIMO solution may also play well with mmWave, ie get it on the rebound.  I do also see firms like T-Mobile using it around sites so the bulk of the 2.5Mhz spectrum is not siphoned off by close-in users.  I also see the build-out requirements on some mmWave ultimately pushing them to use it around busy freeway interchanges like they have done in Seattle. 

Of course physics being as they may, 12/13Mhz may be even better.

mMIMO has already been implemented - mmWave antennas are currently pushing over 5x the number of AE as midband mMIMO equipment.

11 minutes ago, 1dante said:

I’m curious to find out how widespread N25 is currently, and also if any has been deployed in my market here in Florida. 

You might be better off posting in the thread concerning your market, or the general T-Mobile/Sprint thread.

But CellMapper is showing sizeable n25 deployment in Florida.

23 hours ago, 1dante said:

I just saw on a YouTube tech channel that T-Mobile will label N25 as UC in markets where they can deploy 30-40MHZ of contiguous spectrum. Anyone know about this? Thoughts?

Generally makes sense as 30MHz of PCS/AWS will have similar per-UE downlink capacity as 40MHz of n41/n77. However, per-sector capacity will be significantly lower as they're relying on existing 4x4 MIMO radios rather than dedicated mMIMO gear.

That said, I'd be surprised to see T-Mobile deploying 30+ MHz of n25 anywhere this year. And it's not really applicable to NYC, as T-Mobile doesn't have 30+MHz of contiguous PCS (25MHz+5MHz) or AWS (25MHz).

On 10/31/2022 at 9:56 PM, wispiANt said:

Spotted some work on the Sprint site at CCNY's Steinman Hall (275 Convent Ave) today. 

This upgrade has been long overdue - the existing T-Mobile site serving the majority of the north side of the campus (eNB 55893) was a B2/B66-only site that hadn't been touched in years. The Sprint site had not been broadcasting the keep PLMN, though B26 remained active. I haven't seen any active permits, but I'm guessing this means they're decommissioning the T-Mobile site across the street. Looking forward to better building penetration and a more resilient n41 connection. 

This site has been live for a week or two now (eNB 331501) but I'm struggling to see the purpose of converting it. It appears as though T-Mobile is keeping the B2/B66 site next-door (eNB 55893) and T-Mobile has angled the sectors of the new site such that you will rarely (if ever) connect to it while on campus. 

On 11/29/2022 at 5:35 PM, Paynefanbro said:

Between the Crown Castle deal and this one, T-Mobile is gonna have a massive small cell presence citywide.

I wonder if this applies to all the Mobilitie small cells or just the Extenet small cells Sprint has deployed. The Mobilitie small cells make up the vast majority of Sprint's small cell presence. If I were to estimate, I'd say Sprint has <100 Extenet small cells deployed in the city.

Now that I mention it, on the newest DOITT export I'm seeing AT&T and Verizon (or maybe T-Mobile?) using ZenFi all across the boroughs. Didn't really get a chance to check this out in detail before. Not seeing any new "Installed" Mobilitie permits (besides some older Sprint deployments, applied for in 2019ish).

I went through CellMapper yesterday and split a whole bunch of nodes in Manhattan/Brooklyn/Queens/Bronx/LI, so at least we know what we're working with.

---

These Verizon nodes are such a pain to locate:

- Practically identical to a good number of T-Mobile nodes

- Only carrier who didn't opt for SC-specific eNB/sector numbering

- Only carrier who deployed lowband (B13, no B5 at least)

- Even the midband transmit distance seems to be twice that of any other carrier

If anyone has any tips/tricks for locating, feel free to share.

---

Just a heads up for anyone locating AT&T nodes in SI - this may be the only borough where AT&T is using ZenFi as a vendor.

For example:

CellMapper: eNB 817675, Sector 115

DOITT Node Map: Node 22440

Streetview: 40.5878594,-74.1531829

---

Also, found another Sprint convert in SI:

- Sprint eNB 80452 (40.606761402444135,-74.13139757485608) --> T-Mobile eNB 326459/326460

n41 has been bumped up to 140MHz.