Jump to content

T-Mobile LTE & Network Discussion


CriticalityEvent

Recommended Posts

 

Can we get somebody to introduce Peyton Manning to John Legere?  Have the Tin Man QB shout at the Pink Batman?

 

peyton-manning.jpg

 

Omaha!  Omaha!  Omaha!

 

AJ

  • Like 3
Link to comment
Share on other sites

Blast it all. It's rather annoying that T-Mobile still doesn't have Nebraskan numbers, so they won't fix this market because they can't sell anything there...

 

I am sorry, Neal, but nobody else buys that explanation.  It is bullshit.  T-Mobile is not stopped in the Omaha metro because of lack of available local exchange numbers -- for better than a decade.

 

AJ

  • Like 1
Link to comment
Share on other sites

I am sorry, Neal, but nobody else buys that explanation.  It is bullshit.  T-Mobile is not stopped in the Omaha metro because of lack of available local exchange numbers -- for better than a decade.

 

AJ

Considering that the pool of blocks of numbers for area code 402 ran out in 2001 (when T-Mobile was still VoiceStream and was closing the deal to be acquired by Deutsche Telekom), it's an extremely valid explanation. Heck, you've admitted as much, knowing full well that there were far more cellular networks in Omaha than the rest of the country. There were more pagers, more phones, more data cards, more everything. The 531 area code overlay was created in 2011, but numbers were not even being issued until last year! As far as I know, the blocks allocated for 531 have only been to wireline and VoIP providers so far.

 

And to address mobile number portability, you aren't allowed to port numbers that you don't have a local exchange for. That is, because T-Mobile lacks any local exchange reserves in Nebraska, it cannot accept Nebraskan numbers for number portability. Number portability is a "local" process, despite the fact that you're allowed to port mobile numbers from anywhere a carrier has an exchange these days. If there's no exchange, you don't get to port in. It's that simple.

 

What I don't get is how you don't know this, A.J.? This is Phone System 101!

Link to comment
Share on other sites

Blast it all. It's rather annoying that T-Mobile still doesn't have Nebraskan numbers, so they won't fix this market because they can't sell anything there...

It is curious that T-Mobile is the only carrier that never was able to get Nebraska numbers then. AJ may correct me, but we may have had the record for most wireless providers at once in Omaha in the early 2000's: Cingular-->AT&T, Sprint, Nextel, Qwest, Cricket, Us West (Airtouch--> Verizon), Verizon, Alliant-->Alltel--> Verizon, Us Cellular, and T-Mobile sitting on their protection network. It seems like their were plenty of numbers to go around here for anyone that wanted them.

Link to comment
Share on other sites

Considering that the pool of blocks of numbers for area code 402 ran out in 2001 (when T-Mobile was still VoiceStream and was closing the deal to be acquired by Deutsche Telekom), it's an extremely valid explanation.

 

. . .

 

What I don't get is how you don't know this, A.J.? This is Phone System 101!

 

More bullshit.  USCC launched newly constructed band class 1 CDMA2000 service in Omaha well after 2001.  Come on, Neal, stop with the excuses.

 

You have yet to show any official documentation.  And this so called absence of local exchange numbers has not affected any other major operator in the same way in any other major market.  The issue does not exist in the way that you think it does.

 

If T-Mobile really wanted to serve Omaha, it could get it done.  But T-Mobile does not really want to serve Omaha -- because it and 3GPP are late and so far behind the curve in Nebraska.  That is the T-Mobile modus operandi across the geographic majority of the country.  Deal with it.

 

AJ

Link to comment
Share on other sites

It is curious that T-Mobile is the only carrier that never was able to get Nebraska numbers then. AJ may correct me, but we may have had the record for most wireless providers at once in Omaha in the early 2000's: Cingular-->AT&T, Sprint, Nextel, Qwest, Cricket, Us West (Airtouch--> Verizon), Verizon, Alliant-->Alltel--> Verizon, Us Cellular, and T-Mobile sitting on their protection network. It seems like their were plenty of numbers to go around here for anyone that wanted them.

Originally, T-Mobile did not administer the network that existed in the Great Plains. The Iowan network, as everyone knows, is controlled by Iowa Wireless Services. But what isn't as well known is that the spectrum (and the associated network) for the rest of the area was controlled by Cook Inlet.

 

For those who don't know, Cook Inlet Region, Inc is an Alaskan company that develops businesses to support the local Alaskan communities. One of the more unusual ventures of Cook Inlet was partnering with Western Wireless/VoiceStream to create a joint venture to acquire PCS licenses to construct a GSM network across the western half of the United States (and some parts of the Northeast), excluding Iowa. Cook Inlet constructed the facilities, dealt with permitting, acquired phone numbers, and such. VoiceStream would act as the "face" and sell the service, while paying Cook Inlet to have exclusive access to resell service on the network.

 

Cook Inlet's economic share in the venture gradually declined since the VoiceStream/Omnipoint/Powertel merger and Deutsche Telekom acquisition. However, Cook Inlet continued to hold a stake (and control) until last year. Last year (after the T-Mobile/MetroPCS deal closed), all the Cook Inlet/VS subsidiaries that represented T-Mobile's PCS licenses and carrier authorizations were folded into T-Mobile License LLC after T-Mobile bought out Cook Inlet from the venture. This was also disclosed in 2013 Annual Report to Stockholders issued on February 2014. Prior to this event, T-Mobile could not legally acquire phone numbers (it technically didn't own the facilities it used and was constrained by the terms of Cook Inlet). Cook Inlet didn't want to go through the effort and pay for the numbers for Omaha (which it never really cared for, not like Las Vegas), so T-Mobile never had numbers. And T-Mobile was capital-constrained in 2010-2012, so it wasn't really going to dedicate limited cash to give to Cook Inlet to acquire blocks of numbers then.

 

More bullshit.  USCC launched newly constructed band class 1 CDMA2000 service in Omaha well after 2001.  Come on, Neal, stop with the excuses.

 

You have yet to show any official documentation.  And this so called absence of local exchange numbers has not affected any other major operator in the same way in any other major market.  The issue does not exist in the way that you think it does.

 

If T-Mobile really wanted to serve Omaha, it could get it done.  But T-Mobile does not really want to serve Omaha -- because it and 3GPP are late and so far behind the curve in Nebraska.  That is the T-Mobile modus operandi across the geographic majority of the country.  Deal with it.

 

AJ

 

And USCC also controlled 850MHz spectrum throughout Nebraska for years before entering Omaha after the turn of the century. Area codes 402 and now 531 cover more than Omaha, you know. Even though the Omahan network was new, USCC had a presence in Nebraska for years. So of course it had numbers.

 

Blaming 3GPP technology is stupid and irrelevant. AT&T and Viaero Wireless both have Nebraskan numbers due to their legacies in Nebraska. And the sheer number of phone numbers used in Nebraska triggered number pooling to be implemented earlier than most states, and number allocation rates still remained high.

 

For Omahans' sake, I do hope T-Mobile does want to really serve the market. While one of the issues has only been recently addressed (T-Mobile being formally authorized as a carrier in Nebraska), the other issues do need to be dealt with (network quality and phone number allocations) in order to do well there. Now that T-Mobile has cash and is growing, I hope it will do something soon.

Link to comment
Share on other sites

And USCC also controlled 850MHz spectrum throughout Nebraska for years before entering Omaha after the turn of the century. Area codes 402 and now 531 cover more than Omaha, you know. Even though the Omahan network was new, USCC had a presence in Nebraska for years. So of course it had numbers.

 

Blaming 3GPP technology is stupid and irrelevant. AT&T and Viaero Wireless both have Nebraskan numbers due to their legacies in Nebraska. And the sheer number of phone numbers used in Nebraska triggered number pooling to be implemented earlier than most states, and number allocation rates still remained high.

 

No, Neal, you are distorting the chronology to suit your argument.  USCC did not control Cellular 850 MHz spectrum in Nebraska until Alltel acquired WWC and divested the overlapping Cellular A block licenses in rural Kansas and Nebraska.  That was not until 2005, yet USCC had already launched PCS 1900 MHz service in Omaha in 2003.

 

Roughly the same is true of Viaero.  It does not serve Omaha, but it did not expand into eastern Nebraska until well after T-Mobile had started constructing a network in Omaha in 2001.  So, again, how did both USCC and Viaero receive local exchange numbers but T-Mobile could not?

 

And you can blame Cook Inlet all you want.  But T-Mobile is still ultimately responsible for Omaha.  Maybe you should say that T-Mobile nee VoiceStream got what it deserved -- for using sham Native American bidding groups to loophole the FCC.  AT&TWS and Cingular did likewise, but for the record, Sprint never did that. 

 

AJ

Link to comment
Share on other sites

No, Neal, you are distorting the chronology to suit your argument.  USCC did not control Cellular 850 MHz spectrum in Nebraska until Alltel acquired WWC and divested the overlapping Cellular A block licenses in rural Kansas and Nebraska.  That was not until 2005, yet USCC had already launched PCS 1900 MHz service in Omaha in 2003.

 

Roughly the same is true of Viaero.  It does not serve Omaha, but it did not expand into eastern Nebraska until well after T-Mobile had started constructing a network in Omaha in 2001.  So, again, how did both USCC and Viaero receive local exchange numbers but T-Mobile could not?

 

And you can blame Cook Inlet all you want.  But T-Mobile is still ultimately responsible for Omaha.  Maybe you should say that T-Mobile nee VoiceStream got what it deserved -- for using sham Native American bidding groups to loophole the FCC.  AT&TWS and Cingular did likewise, but for the record, Sprint never did that. 

 

AJ

Okay, first of all. I will concede on the USCC. I misread the authorizations on that. But USCC entered at around the time the last of the number pools were available (2000-2003). Obviously now there's a new set of numbers, so T-Mobile should take the opportunity to correct this. Regardless of Cook Inlet's decisions in the past, T-Mobile has an opportunity to fix it now. It should.

 

Secondly, though, the Cook Inlet/VoiceStream JV was never qualified as a Native American bidding group. The only thing it was qualified as was a "small business". It got a 25% bidding credit. US Cellular does the same thing in every auction. It's a terrible, untruthful, horrible usage of a FCC auction rules, but US Cellular still does it using various sham companies (it's doing it now in the AWS-3 auction as "Advantage Spectrum, L.P." and "Wolverine Wireless, L.P."), and T-Mobile does not. Cook Inlet/VoiceStream has never accepted money from Native American funds either. I don't know about the others, though.

 

Thirdly, Viaero Wireless has been in Nebraska since the 1990s. They expanded into "402" area in 1997 after acquiring PCS licenses for the area. They called themselves "Nebraska Wireless" back then.

Link to comment
Share on other sites

From the Q3 statement:

 

250 mil LTE pops covered

260 million by 2014 year end estimated

300 million goal by 2015 year end

 

Wideband LTE is in 19 markets, aiming for at least 26 by end of 2014.

40 markets have LTE on PCS 1900, and growing

 

 http://newsroom.t-mobile.com/issues-insights-blog/company-news/t-mobile-lte-now-reaches-250-million-americans-months-ahead-of-schedule.htm

Link to comment
Share on other sites

From the Q3 statement:

 

250 mil LTE pops covered

260 million by 2014 year end estimated

300 million goal by 2015 year end

 

Wideband LTE is in 19 markets, aiming for at least 26 by end of 2014.

40 markets have LTE on PCS 1900, and growing

 

 http://newsroom.t-mobile.com/issues-insights-blog/company-news/t-mobile-lte-now-reaches-250-million-americans-months-ahead-of-schedule.htm

Interesting.

Link to comment
Share on other sites

From the Q3 statement:

 

250 mil LTE pops covered

260 million by 2014 year end estimated

300 million goal by 2015 year end

 

Wideband LTE is in 19 markets, aiming for at least 26 by end of 2014.

40 markets have LTE on PCS 1900, and growing

 

 http://newsroom.t-mobile.com/issues-insights-blog/company-news/t-mobile-lte-now-reaches-250-million-americans-months-ahead-of-schedule.htm

That puts T-Mobile at 5-8 million POPs less than Verizon and 5 million POPs less than AT&T for native coverage. That's pretty amazing, actually.

Link to comment
Share on other sites

That puts T-Mobile at 5-8 million POPs less than Verizon and 5 million POPs less than AT&T for native coverage. That's pretty amazing, actually.

 

It will be nice when their legacy E/G networks die.

 

In other news, latest financials show churn declining 10bps YoY to 1.60% but increasing QoQ from 1.5%.

 

T-Mobile's net add numbers are crazy.

Link to comment
Share on other sites

That puts T-Mobile at 5-8 million POPs less than Verizon and 5 million POPs less than AT&T for native coverage. That's pretty amazing, actually.

 

Is it really that "amazing"?  In the US, something like 90 percent of the population is confined to 10 percent of the land area.

 

Prima facie, stats can be impressive, can appear similar to other stats.  But in depth analysis shows that they are not so similar.

 

AJ

  • Like 2
Link to comment
Share on other sites

Exactly. POP coverage may be similar, but in comparing how much their network covers in terms of the land mass of the United States, their network will still be small. 

 

Sprint's network has grown by about 4 Million POP's in the last year and that's almost exclusively because of people moving into cities rather than new sites and the network expanding a ton.

Link to comment
Share on other sites

Is it really that "amazing"?  In the US, something like 90 percent of the population is confined to 10 percent of the land area.

 

Prima facie, stats can be impressive, can appear similar to other stats.  But in depth analysis shows that they are not so similar.

 

AJ

Actually no. It's a little over 50%.

 

There's substantial geographic expansion required to move from 285 million people covered by the 2G network to 300 million people covered by the 4G network.

Link to comment
Share on other sites

Actually no. It's a little over 50%.

 

There's substantial geographic expansion required to move from 285 million people covered by the 2G network to 300 million people covered by the 4G network.

 

I used those hypothetical stats for illustrative purposes.  The actual percentages are not important.

 

But there is good reason why T-Mobile advertises its coverage POPs, not its coverage area.  T-Mobile is still -- by good measure -- the weakling among the big four.

 

AJ

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • 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...