Jump to content

Spectrum allocation question


red_dog007

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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
    • At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
    • Did you mean a different site? eNB ID 112039 has been around for years. Streetview even has it with C-band back in 2022 - https://www.google.com/maps/@40.7303042,-73.9610924,3a,24.1y,18.03h,109.66t/data=!3m8!1e1!3m6!1s2ossx06yU56AYOzREdcK-g!2e0!5s20220201T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D2ossx06yU56AYOzREdcK-g%26cb_client%3Dmaps_sv.share%26w%3D900%26h%3D600%26yaw%3D18.027734930682684%26pitch%3D-19.664180274382204%26thumbfov%3D90!7i16384!8i8192?coh=205410&entry=ttu Meanwhile, Verizon's eNB 84484 in Fort Greene has been updated to include C-band and CBRS, but not mmWave. I've seen this a few times now on updated Verizon sites where it's just the CBRS antenna on its own, not in a shroud and without mmWave. Odd.
    • Drove out into the country today.  Dish stuck to my phone like glue. At least -120 rsrp. Likely only good for phone calls (should have tested.) It then switched to T-Mobile. Getting back on Dish was another issue. I am used to dragging out coverage so I expected a few miles, but had to drive at least 10 miles towards a Dish site. Airplane mode, which worked for Sprint, did nothing. Rebooting did nothing. Finally got it to change over about 2 miles from the site by manually setting the carrier to Dish then it had great reception. Sprint used to have a 15 minute timeout but I did not have the patience today.  Previously I did a speed test on Dish out in the country at the edge of Dish coverage. My speeds were 2g variety. Dish has really overclocked some of these sites. Seen rssp readings in the 50s. Would have called them boomer sites with Sprint but much  more common with Dish.  
  • Recently Browsing

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