Jump to content

Recommended Posts

Posted

Isnt 20 billion pretty cheap for 45 mil customers and their spectrum?

I do agree tmo knows down the road sprints network will be much improved and on par with the big2 and tmo will be looking to play catch up and that will cost $$$$$$

whats funny though is 20 billion... That alone is probably why sprint is moving forward.... 20 billion for 45 mil subs which will put you right where you wanna be.....

ATT was willing to pay $39 billion and that was before TMO upgraded 37k towers and before adding 9 mil metros.

 

$20bil is simply market cap, not what sprint would pay.

 

Sure ATT was willing to pay a huge premium to become sole gsm carrier but that doesn't mean that sprint will get away with not paying a premium to the stock price. The premium is standard in takeover bids.

Posted

If the deal was to go through. Will sprint be forced (or should sprint) sell of tmobiles aws licenses to regional carriers or to the big 2?

Posted

If the deal was to go through. Will sprint be forced (or should sprint) sell of tmobiles aws licenses to regional carriers or to the big 2?

Divest T-Mobile's AWS? You must be kidding. No, that would not happen.

 

AJ

Posted (edited)

If the deal was to go through. Will sprint be forced (or should sprint) sell of tmobiles aws licenses to regional carriers or to the big 2?

 

No, but they might elect to sell some of their EBS licenses to the big two or Dish. They will have 800 MHz SMR, AWS, PCS and BRS/EBS spectrum. If they want to do some horse trading to keep their spectrum holdings at 4 bands they might want to trade their SMR holdings for 600MHz after the 600MHz auction.

Edited by bigsnake49
Posted (edited)

No, but they might elect to sell some of their EBS licenses to the big two or Dish. They will have 800 MHz SMR, AWS, PCS and BRS/EBS spectrum. If they want to do some horse trading to keep their spectrum holdings at 4 bands they might want to trade their SMR holdings for 600MHz after the 600MHz auction.

And lose 800-1xA voice? Ain't happening. Edited by meilu
  • Like 1
Posted

And lose 800-1xA voice? Ain't happening.

What I'm advocating won't happen right away.  600Mhz auction won't happen until 2015 and it will probably take until 2016 or 2017 before 600Mhz is ready to be used. By that time, VoLTE should be ready. 1xA will be immaterial by 2017-2018.

Posted

Also remember that even if T-Mobile and Sprint merge, they will only have around 53M postpaid customers (per WSJ). That a lot less than Verizon's 95M postpaid and AT&T's 72M.

I thought sprint had nearly that many customers themselves. How many prepaid customers do tmo and sprint have?

 

Jim, Sent from my Photon 4G using Tapatalk 2

 

 

 

Posted

What I'm advocating won't happen right away. 600Mhz auction won't happen until 2015 and it will probably take until 2016 or 2017 before 600Mhz is ready to be used. By that time, VoLTE should be ready. 1xA will be immaterial by 2017-2018.

Cue pounding from AJ.

 

I'll do some prep: you think Sprint is gonna buy everyone a volte phone to replace 1xA? Sprint said its gonna keep CDMA until sometime very early 2020s.

Posted (edited)

Cue pounding from AJ.

 

I'll do some prep: you think Sprint is gonna buy everyone a volte phone to replace 1xA? Sprint said its gonna keep CDMA until sometime very early 2020s.

 

Yes, so does Verizon, but I don't think it will last that long. Once VoLTE has been perfected, then the next phone you buy will only be a VoLTE one with no Circuit Switched Fallback and you won't notice the difference. It will simplify things tremendously for both the carriers and the handset makers. No need for SV-DO or SV-LTE.

Edited by bigsnake49
Posted

I thought sprint had nearly that many customers themselves. How many prepaid customers do tmo and sprint have?

 

Jim, Sent from my Photon 4G using Tapatalk 2

30.1M postpaid, 15.3 prepaid and 7.86M wholesale for Sprint. 21.4 Postpaid and total of 21.4 prepaid and wholesale for T-Mobile.

Posted

Yes, so does Verizon, but I don't hink it will last that long. Once VoLTE has been perfected, then the next phone you buy will only be a VoLTE one with no Circuit Switched Fallback and you won't notice the difference. It will simplify things tremendously for both the carriers and the handset makers. No need for SV-DO or SV-LTE.

 

Do you mean e/CSFB?  Both SVDO and SVLTE are now basically out of the pipeline.

 

Also, I see that you removed your statement about the speed/ease of T-Mobile-MetroPCS integration.  I was going to address it, but have you retracted it?

 

AJ

Posted

Do you mean e/CSFB?  Both SVDO and SVLTE are now basically out of the pipeline.

 

Also, I see that you removed your statement about the speed/ease of T-Mobile-MetroPCS integration.  I was going to address it, but have you retracted it?

 

AJ

 

No I thought it was kind of peripheral to the discussion, OT. We can address it if you like.

Posted

30.1M postpaid, 15.3 prepaid and 7.86M wholesale for Sprint. 21.4 Postpaid and total of 21.4 prepaid and wholesale for T-Mobile.

Ok that makes sense. Thanks.

 

Jim, Sent from my Photon 4G using Tapatalk 2

 

 

 

Posted

No I thought it was kind of peripheral to the discussion, OT. We can address it if you like.

 

The ease of T-Mobile-MetroPCS integration has been due to two factors:  it is limited to LTE so far, and the two operators share AWS as their LTE band.  The eventual CDMA2000 changeover will be more painful.

 

AJ

  • Like 1
Posted (edited)

The ease of T-Mobile-MetroPCS integration has been due to two factors:  it is limited to LTE so far, and the two operators share AWS as their LTE band.  The eventual CDMA2000 changeover will be more painful.

 

AJ

Yes, I'm sure there will be some MetroPCS customers that will eventually be told that their CDMA flip phone will not work any longer and they will need to purchase another phone. Meanwhile as more CDMA channels become empty they will be reused for LTE. There are no new CDMA phones being sold as far as I know.

Edited by bigsnake49
Posted

The ease of T-Mobile-MetroPCS integration has been due to two factors: it is limited to LTE so far, and the two operators share AWS as their LTE band. The eventual CDMA2000 changeover will be more painful.

 

AJ

I think T-Mobile will make a really enticing offer for MetroPCS customers to switch to GSM/W-CDMA/LTE devices in the near future so they can kill the CDMA2000 network maybe even sooner than originally planned.

Posted

Yes, I'm sure there are some MetroPCS customers that will eventually be told that their CDMA flip phone will not work anylonger and they will need to purchase another phone. Meanwhile as more CDMA channels become empty they will be reused for LTE.

 

I will be interested to see how T-Mobile handles the handset swap situation with low rent MetroPCS subs.

 

And roaming could be a sticking point.  By switching away from CDMA2000, MetroPCS subs will definitely lose overall roaming coverage, both in market and out of market.

 

Back to LTE integration, since each CDMA1X carrier occupies only 1.25 MHz FDD, do not expect to see much refarming until MetroPCS CDMA2000 goes away completely.  This is particularly true since nearly all MetroPCS CDMA1X is in the PCS band, and T-Mobile has made no moves about doing band 2 LTE 1900.

 

AJ

Posted

I think T-Mobile will make a really enticing offer for MetroPCS customers to switch to GSM/W-CDMA/LTE devices in the near future so they can kill the CDMA2000 network maybe even sooner than originally planned.

 

And if so, that means T-Mobile will have to shell out the cash to subsidize low rent MetroPCS subs.  Good, good, make magenta pay...

 

AJ

Posted

And if so, that means T-Mobile will have to shell out the cash to subsidize low rent MetroPCS subs. Good, good, make magenta pay...

 

AJ

They should since they bought them out.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Posted

I will be interested to see how T-Mobile handles the handset swap situation with low rent MetroPCS subs.

 

And roaming could be a sticking point.  By switching away from CDMA2000, MetroPCS subs will definitely lose overall roaming coverage, both in market and out of market.

 

Back to LTE integration, since each CDMA1X carrier occupies only 1.25 MHz FDD, do not expect to see much refarming until MetroPCS CDMA2000 goes away completely.  This is particularly true since nearly all MetroPCS CDMA1X is in the PCS band, and T-Mobile has made no moves about doing band 2 LTE 1900.

 

AJ

 

They don't need to do LTE in the PCS band yet. They have HSPA+ in that band which will accomodate the additional voice demands of migrating Metro customers.

 

As far as roaming, they might have to include some roaming on AT&T for Metro PCS customers on the more expensive plans.

Posted

They don't need to do LTE in the PCS band yet. They have HSPA+ in that band which will accomodate the additional voice demands of migrating Metro customers.

 

As far as roaming, they might have to include some roaming on AT&T for Metro PCS customers on the more expensive plans.

Tiered service coverage? Wow, that would be an interesting change of marketability.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Posted

And if so, that means T-Mobile will have to shell out the cash to subsidize low rent MetroPCS subs.  Good, good, make magenta pay...

 

AJ

 

They might push them into higher cost plans. 

 

Prepaid does not necessarily mean low rent. AIO Wireless' $55/mo plan is not low rent.

Posted

Tiered service coverage? Wow, that would be an interesting change of marketability.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

 

Maybe Sprint should market to those people?

Posted

They don't need to do LTE in the PCS band yet. They have HSPA+ in that band which will accomodate the additional voice demands of migrating Metro customers.

But that is my point. You stated that MetroPCS CDMA2000 would be incrementally refarmed to LTE.  However, if nearly all of that CDMA1X is in PCS and T-Mobile has no present plans for band 2 LTE 1900, then the incremental refarming has no practical application.

 

As far as roaming, they might have to include some roaming on AT&T for Metro PCS customers on the more expensive plans.

 

On CDMA2000, MetroPCS has greater roaming coverage than even T-Mobile postpaid does. So, I doubt that supplemental AT&T roaming would be the answer. That would be awkward for converted MetroPCS subs to have greater overall coverage than existing T-Mobile subs do.

 

AJ

  • Like 1
Posted

But that is my point. You stated that MetroPCS CDMA2000 would be incrementally refarmed to LTE.  However, if nearly all of that CDMA1X is in PCS and T-Mobile has no present plans for band 2 LTE 1900, then the incremental refarming has no practical application.

 

 

On CDMA2000, MetroPCS has greater roaming coverage than even T-Mobile postpaid does. So, I doubt that supplemental AT&T roaming would be the answer. That would be awkward for converted MetroPCS subs to have greater overall coverage than existing T-Mobile subs.

 

AJ

OK, so they won't use PCS 2 for LTE for a while. You got me :).

 

So Metro subs might lose coverage. They're low rent, right? They might lose a few of them to Straight Talk, AIO, Page Plus or Sprint.

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Well you officially fried my brain. Many of these topics are well beyond my very rudimentary amateur knowledge.. this has my head spinning even more than usual. When someone figures it out, just let me know what I need to do with the app! 😂
    • Confusingly, there are two different types of Cell IDs, the NR Cell ID (NCI) and the Local Cell ID, which I will call the LCID from here on out. From my understanding, @Trip is trying to get the LCID from the NCI but the same gNB is showing up for multiple sites in the app. Some background for those that don’t know about NCIs (NR Cell ID) and how they relate to gNBs and LCIDs. Just like the E/GCI which is comprised of the eNB + LCID with the eNB denoting the site, the NCI is comprised of the gNB + LCID with the gNB denoting the site. A major difference is that the eNB is a fixed number of bits in the E/GCI but the gNB can vary between 22-32 bits (out of 36) in the NCI and there is nothing transmitted which tells you what the length is. The reason for the mentioning LTE sites is that Verizon’s gNB numbering scheme in most of the USA is based upon the sites eNB (using the rules I mentioned) and a 22-bit gNB. Additionally, their LCIDs start at 25 and increment by compinations of 16 and 1. Basically, it is common to see LCID sets of 25/26/27, 41/42/43, and 57/58/59. Looking at Trip’s data and some other data from the area, they are not following the format used in the rest of the USA.  From what I can tell, they are using a 29-bit or 30-bit gNB (that gives LCIDs that follow Verizon’s standard patterning). 29-bit shares the same gNB across the two locations, while 30-bit splits the two sets: 18504107674 - gNB 144563341 + CLID 26 (29-bit) or 289126682 + CLID 26 (30-bit) 18504107690 - gNB 144563341 + CLID 42 (29-bit) or 289126682 + CLID 42 (30-bit)  18504107691 - gNB 144563341 + CLID 43 (29-bit) or 289126682 + CLID 43 (30-bit)  18504107706 - gNB 144563341 + CLID 58 (29-bit) or 289126682 + CLID 58 (30-bit)  18504107707 - gNB 144563341 + CLID 59 (29-bit) or 289126682 + CLID 59 (30-bit) 18504107738 - gNB 144563341 + CLID 90 (29-bit) or 289126683 + CLID 26 (30-bit)  18504107739 - gNB 144563341 + CLID 91 (29-bit) or 289126683 + CLID 27 (30-bit)  If true, this is a problem for SignalCheck and other mapping apps because this means they are using at least two different gNB lengths depending on the location in the USA.
    • Yeah I can confirm that the status bar is updating correctly and as often as the main app!  Great to have that back after so long. Waiting on the app to pick up the 5G data.  I'm on AT&T and I find that it only reports the 5G signal data a fraction of the time.  Once I can get it to pop back up I'll send a report with the LTE RSRP showing up in the status bar instead of the NR RSRP. I am not sure if it is new behavior with the Beta because I had it set to just show the Band since I couldn't display the band and signal at the same time. Edit:  Sent a diagnostic and here's a screenshot:
    • Yes, for various reasons the beta mapping project was limited to S4GRU sponsors at launch. It's still a work in progress but I have added a few users as it has evolved. I am inclined to leave it as-is for now -- it's not completely off-limits to discuss here (especially if there's an outage), but with so many posts I just try to keep discussions organized. RAvirani handles the map server and he monitors the other thread closer.   I might be confused, but are we talking apples and oranges here? My interpretation was Trip is talking about NR cells on different sites sharing cell IDs as far as the app is concerned, while the other comments are about LTE to NR cell ID calculations?
    • I hope this is true!! The Android development team did claim this bug was fixed several months ago, and it is typical for it to take several releases before changes are included. I was on the Android beta until I got my Pixel 9, now I am back on the public releases. With each monthly update, I have optimistically checked this icon and been disappointed. This would be fantastic to get back!   Could you send some diagnostic reports when you see this please? It is new behavior with QPR Beta 3?
  • Recently Browsing

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