Jump to content

wispiANt

S4GRU Premier Sponsor
  • Posts

    241
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by wispiANt

  1. 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. 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.
  3. Looks like a passive 4-port (plus two RET ports). Reading the DOBNow filing: I'd guess they've installed two 4460s (4x4 MIMO B2/B66) and a single 8863 (8x8 MIMO B41, split between the two sectors).
  4. 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).
  5. Backhaul on eNB 40986 has been upgraded, as well.
  6. 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:
  7. That's actually an older Ericsson 6449. The newer model is the Ericsson 6419, pictured below.
  8. 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.
  9. 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.
  10. If you're planning on heading up to the Bronx, here's a site you should probably check out. C-Band, CBRS, and n41.
  11. n25 SA was added via a carrier configuration update. And it looks as though n261 NSA was removed.
  12. I'm pretty sure this is a newly-constructed site at the fire station (FAA filing here).
  13. Permit filed to decomm the Sprint site at 304 Boerum St. So I guess we can take that off the "keep" list.
  14. n78 NSA was added for the T-Mobile firmware (S21U). Still no n25 SA.
  15. 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.
  16. mMIMO has already been implemented - mmWave antennas are currently pushing over 5x the number of AE as midband mMIMO equipment.
  17. 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.
  18. 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).
  19. 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. 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.
  20. 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).
  21. 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
×
×
  • Create New...