Jump to content

RAvirani

S4GRU Staff
 View Profile  See their activity

  • Posts

    3,457

  • Joined

  • Last visited

  • Days Won

    159

 Content Type 

Everything posted by RAvirani

  1. RAvirani
    Yes, those can be configured remotely.
  2. RAvirani
    The northwest site might be a good one to decom. The Sprint site and the southern T-Mobile site would provide awesome service to the area. Fingers crossed that's their long-term plan!
  3. RAvirani
    I used to frequent those sites (oftentimes going to the Wingstop just south of that intersection). The Sprint site gets much better coverage going east on 64 than T-Mobile's existing sites. I also think adding the Sprint site will allow T-Mobile to reconfigure the southern site to better meet capacity demands, as coverage will be well taken care of.
  4. RAvirani
    There's no reason to deploy n41 SA outside of NR-only deployments. If you're in n41 range, you're most definitely in range of LTE. Why not tap into whatever extra capacity LTE has to offer?
  5. RAvirani
    Nope, still outdoor-only!
  6. RAvirani
    Does anyone know how to get a USCC SIM onto LTE for mapping/logging purposes? Do you have to buy prepaid service for a month or is there a way to activate without doing yhat?
  7. RAvirani
    I was under the impression that this was a keep site. I'll try to drive by in the next few days. If it's still out, I'll reach out to the network team.
  8. RAvirani
    For anyone who is unhappy after being moved over to T-Mobile, I was moved back to Sprint by the retentions department. That what I'd recommend anyone do who sees a decline in service with TNX/TNA.
  9. RAvirani
    This is what I was thinking, yes. EDGE would be in PCS guard bands. Even if you did want to run 1x on PCS, you don't need to cut an entire 5 MHz of LTE. You can just blank the resource blocks that overlap with the 1x carrier. That would be less than 1 MHz of wasted LTE spectrum (provided some of the 1x carrier was in the guard band).
  10. RAvirani
    1x/EDGE/LTE/NR would be ideal in my opinion.
  11. RAvirani
    Other than seeing B2 more often you won't notice too much difference. I believe the updated QRxLevMin is -124. QQualMin values should be the same.
  12. RAvirani
    The 20x20 B2 rollout will be completed today. Final edited handoff/load balancing parameters will go live tonight to account for the additional BW.
  13. RAvirani
    I was unable to roam on US Cellular with ROAMAHOME in Moclips/Pacific Beach, WA recently. Sprint devices were roaming on US Cellular LTE.
  14. RAvirani
    Getting rid of SE03314B and keeping the other 3 would work out best. Three sites will more than cover the area's capacity needs, and it's not difficult to make use of downtilt and 45° antennas (as opposed to the usual 65° antennas) to keep the SNR from dropping due to inter-site noise. The number one problem with T-Mobile in the Seattle market today is that their signal to noise ratio is consistently terrible (by comparison to the other carriers). This is not due to congestion but due to overlapping sectors. It seems the Sprint team was largely retained (as all my former contacts are staying with T-Mobile) and they're working to clean the network up as much as possible. EDIT: New imgur link https://imgur.com/a/Op6GVHs
  15. RAvirani
    I saw that permit as well. I honestly think that site should be decommissioned - it does more damage to the SNR of other sites than good. There's another colocation planned in that area on the same building as the AT&T site (47.7095747, -122.1880277). That should be interesting!
  16. RAvirani
    Oops - I totally misread your message. Permits are in to put 2500 on the downtown Kirkland site (SE02100T). That's why my mind went there. Nice find!
  17. RAvirani
    Is this the T-Mobile site on the Livengood building?
  18. RAvirani
    I was actually in Kansas city a few weeks ago for work! Although I wasn't paying particular attention, I don't recall ever seeing LTE on my phone except for once deep in a building (because I couldn't place a call).
  19. RAvirani
    This is absolutely correct. This has been the trend more often than not, although it is not true 100% of the time.
  20. RAvirani
    Interesting. This is the info I got: https://imgur.com/a/bVymrPP
  21. RAvirani
    2HH-38A-R4-V2. It has two 4x4 Rx/Tx chains, each with a 38° horizontal beamwidth. The gain figures are solid, ranging from 19.3-20 dBi on AWS/PCS.
  22. RAvirani
    The MFBI spec does not support simultaneously different IBWs/center frequencies. For example: 15x15 C block carrier could be simultaneously broadcasted as B2 (1125) and B25 (8565) with MFBI. However, MFBI does not support simultaneous broadcast of 15x15 B2 (EARFCN 1125 in the PCS C block) and 20x20 B25 (EARFCN 8590 in the PCS C+G block) that overlap by 15 MHz. Achieving the latter is a much more complex problem due to the fact that guard bands would be of different widths and thus, the physical resource blocks and LTE subcarriers wouldn't necessarily line up. These challenges require careful timing, real-time PRB blanking, dynamically served handoff parameters, etc. to solve.
  23. RAvirani
    Keep your eyes open. Rumor has it there's something similar to DSS in the works. It would allow a PCS C+G carrier to be simultaneously broadcasted as a 15x15 B2 C carrier and a 20x20 B25 C+G carrier based on device compatibility.
  24. RAvirani
    PCS E+F+C3+C4. They chopped the C4 block off Sprint's 15x15 carrier.
  25. RAvirani
    T-Mobile L1900 is going to 20x20 in two weeks per the engineering team's estimate!
×
×
  • Create New...