Jump to content

AT&T Wireless purchases Leap Wireless (Cricket Wireless)


avb

Recommended Posts

Yeah I know ATT nor any carrier would make any concessions unless forced by the FCC.  I just hope the FCC puts required divestitures on the PCS spectrum.  I am sure the main reason for the Leap purchase for ATT is that they covet the AWS spectrum so they can combine their AWS holdings to deploy LTE on it.  The PCS spectrum is just the cherry on top.

Link to comment
Share on other sites

Yeah I know ATT nor any carrier would make any concessions unless forced by the FCC. I just hope the FCC puts required divestitures on the PCS spectrum. I am sure the main reason for the Leap purchase for ATT is that they covet the AWS spectrum so they can combine their AWS holdings to deploy LTE on it. The PCS spectrum is just the cherry on top.

They are planning on using PCS for LTE also and iphone 5, for example, already supports Band 2 (PCS). I think the AWS gained will, as AJ said, give them scale in terms of equipment purchases, but PCS is not any less valuable for LTE than AWS long term. Short-term, AWS is more valuable because it's not being used for HSPA.

Link to comment
Share on other sites

They are planning on using PCS for LTE also and iphone 5, for example, already supports Band 2 (PCS). I think the AWS gained will, as AJ said, give them scale in terms of equipment purchases, but PCS is not any less valuable for LTE than AWS long term. Short-term, AWS is more valuable because it's not being used for HSPA.

 

I understand that PCS spectrum is still valuable spectrum and will eventually be converted to LTE.  I am just saying if divestitures were required on either PCS or AWS on this deal, I am sure ATT would choose PCS over AWS since they have a decent amount of PCS spectrum holdings already and ATT needs to deploy their AWS spectrum soon.

  • Like 1
Link to comment
Share on other sites

Is this what you are seeking?

 

10dfhcl.png

 

Leap PCS does little for AT&T outside of the Pacific Northwest -- Seattle and Portland, which were Cingular sore spots prior to the AT&TWS merger nine years ago.

 

AJ

 

Looks like at&t will have to divest some of that PCS Spectrum they would acquire from this deal.

Link to comment
Share on other sites

In my opinion, the FCC should require divestiture so that:

  • They should not have more than 30Mhz of AWS in any one market upon completion of the merger.
  • Their combined PCS + AWS in any market should not exceed 60Mhz upon completion of the merger.
And finally my blanket rule for all mergers involving ATT and VZW: Require them to divest any Cell 850 spectrum so they own no more than half the Cell 850 spectrum in a given market. They can do this through spectrum swaps or sales if they'd like. It's just stupid to have ATT or VZW owning both the A and B sides of the spectrum in a given market (or even all of one side and part of another).

That's a little unreasonable.

  • Like 2
Link to comment
Share on other sites

I decided to do an analysis of a market near and dear to me: San Antonio.

 

Currently...

 

  • AT&T has both Cellular licenses, 5x5 of PCS, and what looks to be no AWS; I'm guessing the duplicate 1735-1740 license goes to T-Mobile in this case. Plus 12x12+6 of 700. So, discounting unpaired 700, 84MHz of spectrum they can use right now.
  • Verizon has 15x15 of contiguous PCS, plus its usual 700MHz license, plus 10x10 of SpectrumCo AWS.
  • Sprint has 15x15 of contiguous PCS, though this PCS isn't contiguous with the G block. They also have BRS/EBS, but I don't feel like doing those calcs.
  • T-Mobile has 10x10 + 5x5 of PCS, with no hope of getting that contiguous through reasonable spectrum swaps. They also have 10x10 + 10x10 of AWS.
  • CricKet has 10x10 of PCS (5x5 ex-Pocket Communications, who itself bought it from AT&T Wireless...I mentioned on StopTheCap that this was a divestiture requirement of AT&T + Cingular but it might have just been AT&TWS selling spectrum to keep afloat back when you didn't need tons of spectrum to be viable), plus 5x5 of AWS. I don't think they actually deployed 5x5 LTE on that spectrum...and I'm not sure how to use my Optimus Regard to check...but overall not a bad position.
  • Aloha, a spectrum speculator of some sort, has 10x10 of AWS below Verizon's block.

 

So, if AT&T is unscathed by divestiture requirements in San Antonio, they'll end up with 10x10 + 5x5 of PCS and 5x5 of AWS.

 

A spectrum swap apiece in PCS and AWS would give AT&T 15x15 contiguous in PCS while boosting T-Mobile to 20x20 contiguous in AWS, without any other contiguity changes. On the PCS side, T-Mobile would swap its 1895-1900 uplink PCS disaggregation for AT&T's 1885-1890 block, re-aggregating the 1895-1910 block. On the AWS side, AT&T's new 1740-1745 block would get swapped for T-Mobile's 1730-1735 one.

 

Since AT&T owns so much CLR spectrum in San Antonio, they could then choose to run all non-LTE operations in CLR without any fear of capacity issues (since they're pretty much doing that right now), and hit a 15x15 FD-LTE channel in PCS (which devices like the iPhone support). And they'd still have AWS to add a little bit of capacity for devices with AT&T's initial 4 + 17 LTE band support.

 

And of course that would mean that T-Mobile could continue to run DC-HSPA+ in PCS, and eventually hit 20x20 FD-LTE in San Antonio, with a smooth transition from 10x10 to 15x15 to 20x20 as their subscriber base gets phones that support LTE in AWS and/or HSPA+ in PCS. And in the mean while, GSM will sit on TMo's lonesome 5x5 PCS block for as long as it needs to.

 

As a side note, I expect Verizon to buy up Aloha's AWS license to San Antonio within a year or two, allowing them to run 20x20 FD-LTE in town potentially before T-Mobile does, and almost certainly before AT&T hits 15x15 in PCS. But not before Sprint launches TD-LTE in BRS/EBS, considering that carrier's market share in SA, how far NV has come there, and how much the area is blanketed by Clear WiMAX.

  • Like 1
Link to comment
Share on other sites

I agree. Though more than 50 MHz of AWS or 50-60 MHz of PCS should probably be divested.

this sounds a little more fair.

 

You can't be too heavy handed about mandating divestures if you're the FCC. Particularly when you auction off more and more spectrum every few years. It would make sense to set the threshold fairly high at like you said, 50 or 60 MHz and then maybe consider blocking them from acquiring more through the H block auction or further acquisitions in these particular bands.

  • Like 1
Link to comment
Share on other sites

In my opinion, the FCC should require divestiture so that:

  • They should not have more than 30Mhz of AWS in any one market upon completion of the merger.
  • Their combined PCS + AWS in any market should not exceed 60Mhz upon completion of the merger.

And finally my blanket rule for all mergers involving ATT and VZW: Require them to divest any Cell 850 spectrum so they own no more than half the Cell 850 spectrum in a given market. They can do this through spectrum swaps or sales if they'd like. It's just stupid to have ATT or VZW owning both the A and B sides of the spectrum in a given market (or even all of one side and part of another). 

That's a little unreasonable.

Why do you think that's unreasonable? Which parts? If it was 70Mhz of PCS + AWS would that make this ok?

Link to comment
Share on other sites

It caps the spectrum limit too low.  That's the unreasonable part.  I'm all for not letting one company control the whole enchilada - but you have to allow them to acquire spectrum pretty freely otherwise you might as well just lease it annually like AJ proposed (in another thread?).  The only reason to limit the amount is to not let one company monopolize (or duopolize) the market.  

  • Like 1
Link to comment
Share on other sites

It caps the spectrum limit too low.  That's the unreasonable part.  I'm all for not letting one company control the whole enchilada - but you have to allow them to acquire spectrum pretty freely otherwise you might as well just lease it annually like AJ proposed (in another thread?).  The only reason to limit the amount is to not let one company monopolize (or duopolize) the market.  

I'm with you in spirit on this one Mac, I don't want the FCC micromanaging the spectrum allocations of different companies either. I think we just disagree in this specific instance about the size of the cap for this merger. I'm going to create another post to explain the rationale for my lower cap in this specific instance.

Link to comment
Share on other sites

Will ATT tell low-paying Cricket subs to scram?

 

AT&T Will Buy Leap for Spectrum and Get Low-Paying Customers

 

http://mobile.businessweek.com/articles/2013-07-15/at-and-t-buys-leap-for-spectrum-gets-low-paying-customers?campaign_id=yhoo

 

ATT already has two prepaid brands: GoPhone and it-that-shall-not-be-named.

I doubt it's gonna take on another. I looked at Cricket's prices and if anything, ATT will get rid of ITSNBN and just replace it with Cricket. ITSNBN isn't even available outside of 3 markets.

Link to comment
Share on other sites

The most likely candidate is USCC in my opinion.

USCC just bailed out of Chicago by selling off the market to Sprint. No way does USCC buy back in for only LTE spectrum.

 

AJ

Link to comment
Share on other sites

Who else is there? Sprint has no other 700MHz licenses and as such probably wouldn't be interested. T-Mobile only has a 700MHz in Boston via MetroPCS with no announced plans to do anything with it. AT&T has shown no interest in 700MHz lower A licenses since they don't want to support Band 12 and 700MHz interoperability. Verizon has likewise shown no interest in 700MHz lower A spectrum. So who's left that's a willing buyer?

Link to comment
Share on other sites

Who else is there? Sprint has no other 700MHz licenses and as such probably wouldn't be interested. T-Mobile only has a 700MHz in Boston via MetroPCS with no announced plans to do anything with it. AT&T has shown no interest in 700MHz lower A licenses since they don't want to support Band 12 and 700MHz interoperability. Verizon has likewise shown no interest in 700MHz lower A spectrum. So who's left that's a willing buyer?

Speculator.
Link to comment
Share on other sites

A quarter of a billion dollars (give or take) is a lot of money to speculate with...

 

I have said it before and will say it again:  there is too much spectrum in circulation.  Speculators may be headed for a crash.

 

AJ

Link to comment
Share on other sites

Who else is there? Sprint has no other 700MHz licenses and as such probably wouldn't be interested. T-Mobile only has a 700MHz in Boston via MetroPCS with no announced plans to do anything with it. AT&T has shown no interest in 700MHz lower A licenses since they don't want to support Band 12 and 700MHz interoperability. Verizon has likewise shown no interest in 700MHz lower A spectrum. So who's left that's a willing buyer?

 

They (Verizon) certainly have alot of lower A licenses for not being interested.

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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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