Jump to content

Why is VZ selling prime 700MHz spectrum for AWS?


Recommended Posts

Because they want the AWS for VoLTE on smaller feature phones. Plus the technology isn't developed yet to use both upper and lower 700 block LTE. They pretty much bought the lower 700 block licenses just to keep it out of the hands of their competitors.

 

The lower 700 A block also gets interference from UHF transmissions making it less attractive to build out on.

 

Sent from my Galaxy Nexus using Tapatalk 2

 

Link to comment
Share on other sites

http://arstechnica.c...ever-built-out/

 

There must be a good reason to sell prime 700MHz spectrum to exchange for the less useful AWS Verizon wants to buy, but I have no idea what that reason is.

 

I completely disagree that the AWS spectrum is less useful than the 700 MHz A and B blocks. The 700 MHz A and B blocks are not very attractive especially the A block which is adjacent to TV channels which can interfere with LTE. The 700 MHz A and B blocks are not even nationwide are only in some of the big markets. If Verizon is able to pull this off and offer this as a concession to obtain FCC approval, then Verizon got the better end of the deal did a really good job and fooled the FCC.

 

I used to think that all higher frequencies were considered "less useful" until I understood the trade offs between building penetration and capacity. The ever so increasing data problem in the future like 5 years out will not be building penetration but rather capacity and I think the AWS spectrum (1700/2100 MHz) is a good balance between building penetration and capacity. The reason why AWS spectrum is more useful IMO is because even though AWS spectrum does not have as good building penetration and requires more towers than 700 MHz spectrum, AWS spectrum is able to handle more users in the same exact amount of area due to the increased amount of towers it will need to cover that area.

Link to comment
Share on other sites

The FCC auction for 700 MHz had some complicated rules to it. The result is that Verizon ended up with near nationwide coverage in the upper C block along with some A and B blocks scatterred throughout the country. No one has engineered an antenna that can use both upper 700 MHz and lower 700 MHz bands in a compact form-factor. Verizon logically chose to create devices that use its upper C block. That leaves Verizon with a lot of A and B blocks that are not being built out, so the decision is to sell off those blocks.

 

This probably benefits AT&T the most. AT&T picked up many A and B block licenses, but not enough to have nationwide LTE coverage. Picking up Verizon's licenses will give increased LTE coverage.

 

It doesn't make any sense for Sprint to bid on the licenses because adding a patchwork of 700MHz doesn't improve Sprint's plan to already use 800MHz, 1900MHz and (Clearwire) 2.5GHz. T-Mobile has stated that they're not interested either.

 

SpectrumCo's AWS coverage is coast-to-coast, but there are many holes in between. These licenses do complement Verizon's AWS licenses which is mostly in the Eastern US. While building penetration is not stellar, Verizon could aggregate the AWS band with their 700MHz band (once they upgrade to Release 10 of LTE) much the way Sprint will aggregate Clearwire's 2.5GHz band.

 

The FCC is rightly asking why the 700MHz sale is contingent on the AWS license transfer being approved. Really, Verizon has no interest in using that spectrum anyway, but they're trying to present an incentive for the AWS approval, when they're really not related.

  • Like 1
Link to comment
Share on other sites

The only true Eason is to get that high capacitcy AWS and get rid of the 700 spectrum that gets interference

Link to comment
Share on other sites

What is this gruff about parts of 700mhz not being compatible with the same antenna, amps, etc? That doesn't sound right to me. Sure, it might not be quite as efficient outside its designed band but there is no way it drops off that fast.

 

The rest of it makes sense though.

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

    • I see it as more of an economic calculation.  Basically go after the areas where they have the best odds of retaining or attracting customers versus their MVNO arrangements. The quicker they can switch back and forth between 5g and MVNOs the finer grained this decision zone can be.  Field results will beat theory.  In Sprint days this was up to 15 minutes in theory. In practice AT&T could be quite sticky.  I remember driving by 3 Sprint sites while still stuck on AT&T roaming. Dish will need to do better to thrive. Both their MVNO arrangements reportedly now cost them about $1.50 per GB. With volume that may fall to $1.
    • Man I wish I could get on their beta right now.  Looks like I'll have to wait until Dec or so.  The report is not surprising really.  Largely only have employees roaming around running tests and what not.  I am sure lots of testing is needed to iron out bugs, fix things.  Though a lot of it might be denser network.  Only so much you can do and money is spread out very thin when you have such a large target to hit. 
    • Found some AT&T c band live in Cincinnati today. Not too bad considering I was driving past on the interstate at speed.  
    • Hey Mike, a couple other things you might be able to post for S22Ultra owners, In particular, these deal with the *#0011# menu. The following are true for even the June update:   1. Does not show the second n41 carrier (when it is connected) on LTE+NSA. It shows "NR_NumCC:2" but no additional Carrier. It simply states "CA-Not Config 0 0"This works fine on the S21.  2. There is a line that states "Code Review Required" 3. There is a line that states "Unknown 0"    
    • The see Dish as the Beta network for a while. Basically once they have secured their licenses and have inexpensive phones that utilize all their bands I hope to see them reduce the edge space of their network or improve the transfer performance so customers have more of an invisible handoff experience. This will likely be late 2023. 
  • Recently Browsing

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