Jump to content

Spectrum allocation question


red_dog007
 Share

Recommended Posts

So, looking at it.

 

Why not the FCC do this?

 

Right now AWS4 covers 2000-2020 and 2180 - 2200.

 

AWS3 has 15MHz unpaired uplink from 1695-1710.  So why not make that 20MHz, from 1690 -1710 and pair it with upper AWS4 and make this part of AWS3. 

 

Then reallocate 20MHz from 1830-1850 (used by government) to pair with lower AWS4 of 2000-2020 and make this part of PCS. 

 

It would cause complications with Dish owning half of the paired links in both the new extended PCS and AWS ranges.  But for spectrum utilization I think it would have been a solid plan for the long term.  Band 66 wouldn't be weird, which still excludes 30MHz of spectrum in lower AWS4 and PCS H-Block..  Could just make a new band that covers all AWS from 1690-1780 / 2110-2200 and all PCS that covers 1830-1920 / 1930-2020.

 

Instead currently lower PCS H-block and lower AWS4 are bandless.  And we got 15MHz of unpaired junk in AWS3.

 

Its an extra 25MHz the feds would need to surrender. but they are/were pushing for hundreds of MHz that they haven't reached yet.  And it would just be extending PCS and AWS ranges evenly and IMO utilize the spectrum much more efficiently, at least just looking at the numbers.

 

Dish owning it would cause some issues, but it is the feds.  I think they could get it done.  Either force Dish to partner with someone, or if they can't get anything deployed, they'd eventually have to surrender/sell that spectrum.

Link to comment
Share on other sites

In short, your plan would cause lawsuits and political problems.  It took years of negotiations to get the spectrum freed for AWS-3, and billions of dollars that haven't yet been spent.  Saying "it's an extra 25 MHz the feds would need to surrender" is one of those things that sounds very easy on paper but isn't in practice.

 

- Trip

Link to comment
Share on other sites

Who owned the AWS3? Government? If they just of had the idea above from the beginning it wouldnt be as much of an issue. But maybe it was and negotiations failed. They have to release another 30MHz, but can't remember by when. Maybe could have just waited on AWS3 cause some law passed before the auctions, bought Dish's spectrum, and released that 30MHz.

 

I know what is done is done, and can't do this could have should have, but still. It would be nice to see better utilization of this limited resource.

Link to comment
Share on other sites

Yes, government spectrum is being repurposed for AWS-3.  The spectrum is technically not available yet, only after much money is spent moving existing things around will it become available, and I think some of it will never become available, though I'm not 100% certain of that.

 

- Trip

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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Went to Rolling Loud NYC at Citi Field this weekend. Over 60,000 people in attendance. Verizon is a sponsor of the festival this year so naturally they had a ton of COWs set up at the festival. I counted at least 4. As a result, they were virtually the only carrier consistently able to provide a data connection. I didn't see any Verizon 5G, only LTE. T-Mobile on the other hand was a very interesting experience. I was seeing an eNB 331804 which I'm 99% sure is a COW. They also seems to be doing some sort of traffic management because I noticed that if I left my phone idle in my pocket, it would drop down to No Service/SOS or sometimes it would sit on EDGE. But the second that I needed to send a text, make a call, or even use Twitter my phone would switch over to LTE or 5G to complete the task. In an active data session, my phone would constantly flip between Band 2, Band 66, and Band 41. Sometimes, I'd catch myself on the COW and other times I'd get pushed over to eNB 875868, the relatively new Sprint conversion nearby. The network moved at a snails pace though. Where Verizon took about 15 seconds to load Twitter or send a pic, T-Mobile could take up to a minute to complete the same task. Here's some photos of the COWs I spotted. I think that the first two are Verizon and the one in the distance in the third pic is T-Mobile's single COW, not nearly enough for an event that size.  
    • @dkyeager has written up an article for The Wall on the Auction:   Robert
    • You need to have Wi-Fi Calling enabled and also have made at least one phone call over Wi-Fi Calling prior to using the inflight Wi-Fi.
    • See this page: https://www.sprint.com/en/support/in-flight-texting-wi-fi.html Also see the FAQ’s here: https://www.t-mobile.com/benefits/travel/in-flight-wifi “How do I access In-Flight Connection?”
  • Recently Browsing

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