Jump to content

Sprint SMR Spectrum holdings...


Recommended Posts

817/861mhz would be where the 1xAdvanced would be placed... wonder why that might be missing from the list, seems also this map shows Sprint having the spectrum thru all the SouthernLinc areas too.

 

/b

Link to comment
Share on other sites

The blog notes this:

 

"The SMR and EBS/BRS spectrum is a bit messy – the spectrum licenses I download don’t correspond to the ULS, so there are mismatches and somewhat clumsy records."

 

So that could explain it.

Link to comment
Share on other sites

It may be that he is working through the kinks of his new method. The previous way he would update the maps got borked, and he now has to comb threw the data manually. 

 
 
 
here is a link to the blog post explaining his new method. 
Link to comment
Share on other sites

http://specmap.sequence-omega.net

 

This has been updated to include sprints SMR licenses and the BRS, seems in most places Sprint only has 12mhz?  That's not enough for a 5x5 and 1xAdvanced is it?  Unless the data is incorrect.

 

Thoughts?

 

/b

 

I love what Anthony is doing.  He is obviously very talented in coding methods to pull data automatically.  But his data is not hand massaged, is not always accurate -- especially pertaining to partitions and disaggregations.  I have long advised people to use his maps only as thumbnail sketches.

 

In this case, the FCC ULS is at fault.  SMR 800 MHz is in disarray during the Public Safety rebanding process.  For now, the ULS indicates that Sprint holds the rebanded SMR X block 12 MHz license:  818-824 MHz x 863-869 MHz.  However, across most of the country, Sprint controls an additional 1 MHz below both the uplink and downlink for the following total:  817-824 MHz x 862-869 MHz.

 

In short, that is 7 MHz FDD -- sufficient for one CDMA1X carrier, one LTE 5 MHz FDD carrier, and guard bands.

 

AJ

  • Like 4
Link to comment
Share on other sites

Link to comment
Share on other sites

Why does the map when you filter under SMR 800 (806-824) show that Los Angeles, San Diego, Phoenix, Tucson and San Antonio do not have any SMR licenses?  Since the author pulls these records from the FCC, is this just an error with the FCC's documentation?

Link to comment
Share on other sites

Why does the map when you filter under SMR 800 (806-824) show that Los Angeles, San Diego, Phoenix, Tucson and San Antonio do not have any SMR licenses?  Since the author pulls these records from the FCC, is this just an error with the FCC's documentation?

 

In the FCC ULS, SMR 800 MHz is separated into several different service codes.  Only one those service codes, YH, is for rebanded SMR 800 MHz spectrum.  That is the data that Anthony pulled down.  If no rebanded licenses have been issued, then his data does not reflect that Sprint holds unrebanded YC/YF/YG service code spectrum that will be converted to YC in due time.

 

Eric, since you are in LA, this is for you...

 

http://wireless2.fcc.gov/UlsApp/UlsSearch/license.jsp?licKey=8347

 

That is only one of many, but proof that Sprint still holds active SMR 800 MHz licenses in those markets.

 

AJ

  • Like 1
Link to comment
Share on other sites

In the FCC ULS, SMR 800 MHz is separated into several different service codes.  Only one those service codes, YH, is for rebanded SMR 800 MHz spectrum.  That is the data that Anthony pulled down.  If no rebanded licenses have been issued, then his data does not reflect that Sprint holds unrebanded YC/YF/YG service code spectrum that will be converted to YC in due time.

 

Eric, since you are in LA, this is for you...

 

http://wireless2.fcc.gov/UlsApp/UlsSearch/license.jsp?licKey=8347

 

That is only one of many, but proof that Sprint still holds active SMR 800 MHz licenses in those markets.

 

AJ

 

thanks for the link.  I didn't doubt that the So Cal area lost the 800 Mhz spectrum.  I was just curious why the map didn't reflect that it had 800 MHz in the southwest markets along CA, AZ and TX.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • The DAS at LGA Terminal B actually has n41 at 100+20, but if you are deprioritized, good luck on the busy days, as all the bands are congested, even B41 and n41, with data being worse than 128kbps international roaming. It has SA active for n41 as well. The L train tunnel is actually 80+20 for n41, with SA n41 active. Speeds aren't anything compared to Philadelphia's DAS system that has n41 though. The gig+ upgrades are expanding, as eNBs 894588 (Sprint convert site) and 55987 can both pass 1 Gbps now. Clocked nearly 1.3Gbps on eNB 55987 today.
    • Hopefully this goes thru!  https://www.reddit.com/r/tmobile/comments/1211mh7/tmobile_files_another_sta_application_to/
    • Yup 80MHz C-band + 40MHz DoD for a total of 120MHz. They should be pretty well setup post-clearance. — — — — — Famous Verizon site on Atlantic referenced in this reddit post got moved to the top of the building next door. — — — — — Also looks like I mapped a T-Mobile oDAS node eNB 347812 in Brooklyn Heights. Streetview shows it as one of the CC nodes with no antenna on top as of May 2022 but this specific eNB was first mapped this month. I didn't notice that I mapped it until I got home but the range on it is significantly greater than the normal "antenna-less" nodes T-Mobile deploys. I'm wondering if it got upgraded to the new 5G oDAS design but I won't be able to check it out until next weekend.  
    • I didn't know they had access to 80 MHz of c-band that does change some things then once that's online
    • While I've been loath to update my Samsung devices past the May 2022 update to keep the Band Selection tool, I note that it looks like Android 14 is going to add Timing Advance for NR to the API.  (Was looking today as I have another Verizon A42 5G now that I'm going to unlock for T-Mobile, and wanted to figure out if I should let it update or not.)  Since I can technically make band changes from *#73#, on the A42 5Gs, I can probably live without the Band Selection tool if a later Android version adds something useful like TA values. I assume SCP will be updated to support that once it becomes publicly available.  The real question is whether or not the phones will support it.  My S21FE and A42 5G devices do on LTE, but I know the S22 and the A32 5G do not support it even on LTE, providing just zero in that field. - Trip
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...