Jump to content

1xRTT M2M tying up network resources?


Recommended Posts

http://www.fiercewir...down/2013-04-22

 

Why is Sprint tying up its network for peanuts?

Admittedly, I don't know the spectrum layout for Sprint PCS so it's possible that it might have a sliver that can only hold a 1xRTT carrier.

 

However, even if that is the case shouldn't Sprint at the very least only allow M2M modules work on its CDMA-800? That way, it can eventually clear out PCS to use solely for LTE.

Link to comment
Share on other sites

Well, voice is given priority anyways, so I don't really see this as an issue. Data sessions can be dropped and delayed if the network is overloaded.

  • Like 1
Link to comment
Share on other sites

http://www.fiercewir...down/2013-04-22

 

Why is Sprint tying up its network for peanuts?

Admittedly, I don't know the spectrum layout for Sprint PCS so it's possible that it might have a sliver that can only hold a 1xRTT carrier.

 

However, even if that is the case shouldn't Sprint at the very least only allow M2M modules work on its CDMA-800? That way, it can eventually clear out PCS to use solely for LTE.

 

Save the 1xA voice carrier in SMR (800Mhz) for rural coverage, get that roaming bill to Verizon down a bit. The voice carriers are 1.25Mhz FDD I believe, so they are very small, compared to 5Mhz FDD for LTE and I'm think 3.25Mhz FDD for EVDO.

  • Like 1
Link to comment
Share on other sites

And 1xA will not be going anywhere for a long time. It is one of the things that have kept me with Sprint, is the quality of voice that CDMA provides. I can not stand GSM one bit for voice...pun intended.

  • Like 4
Link to comment
Share on other sites

http://www.fiercewir...down/2013-04-22

 

Why is Sprint tying up its network for peanuts?

Admittedly, I don't know the spectrum layout for Sprint PCS so it's possible that it might have a sliver that can only hold a 1xRTT carrier.

 

However, even if that is the case shouldn't Sprint at the very least only allow M2M modules work on its CDMA-800? That way, it can eventually clear out PCS to use solely for LTE.

 

That's assuming that no 1xRTT voice customer will ever be around. They are likely just trying to maximize what's going to be around for a while... which is a single 1x carrier.

 

Why not monetize what your competitors don't want?

Link to comment
Share on other sites

Well, voice is given priority anyways, so I don't really see this as an issue. Data sessions can be dropped and delayed if the network is overloaded.

 

I wasn't focused on competing with resources for voice but rather the burden of being obligated to maintain CDMA PCS for M2M when all other voice traffic has migrated to CDMA-SMR and VoLTE.

Link to comment
Share on other sites

I wasn't focused on competing with resources for voice but rather the burden of being obligated to maintain CDMA PCS for M2M when all other voice traffic has migrated to CDMA-SMR and VoLTE.

You know, I'm not really sure what the big excitement over VoLTE is. LTE is a more "fragile" airlink than 1X, so it requires closer tower spacing or lower frequency to provide the same coverage. Why take up LTE capacity (which, for example, VZW is already running low on in some areas) with VoIP traffic when you can smash a lot more voice capacity in a single 1X carrier?

 

That being said, even VZW isn't shutting down 1X for another decade at minimum.

Link to comment
Share on other sites

1x services are not known for being over capacity or a problem in general. Besides, whenever adding services like this, you better believe that they crunch the numbers and figure out how much it will cost in additional capacity over the lifetime of the contract and price accordingly. And then the resources exist to pay for the added capacity. Making growth pay for itself.

 

Nothing to see here folks. Move along...

 

Robert

Link to comment
Share on other sites

You know, I'm not really sure what the big excitement over VoLTE is. LTE is a more "fragile" airlink than 1X, so it requires closer tower spacing or lower frequency to provide the same coverage. Why take up LTE capacity (which, for example, VZW is already running low on in some areas) with VoIP traffic when you can smash a lot more voice capacity in a single 1X carrier?

 

That being said, even VZW isn't shutting down 1X for another decade at minimum.

 

It will take a lot of work and additional sites before Sprint can't even think about deploying VoLTE.

  • Like 1
Link to comment
Share on other sites

It will take a lot of work and additional sites before Sprint can't even think about deploying VoLTE.

 

I was pretty disappointed when I read that Sprint's HD voice isn't even going to be compatible across current equipment vendors. Not calling someone in Ericsson territory, no HD voice for you!

Link to comment
Share on other sites

I was pretty disappointed when I read that Sprint's HD voice isn't even going to be compatible across current equipment vendors. Not calling someone in Ericsson territory, no HD voice for you!

 

Initially. It won't stay that way.

Link to comment
Share on other sites

 

It will take a lot of work and additional sites before Sprint can't even think about deploying VoLTE.

 

When SMR LTE is deployed, commercial trials can commence. I wouldn't do anything customer facing for VoLTE until they have SMR LTE deployment that's widespread.

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

    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
    • One more SCP beta rolling out.. includes more bugfixes and minor improvements. Pending any major issues with this version, it will be released to the public within a few days. Thanks for all the help and feedback!
    • Passed by the former Sprint site at 1184 60th St in Brooklyn last week and noticed T-Mobile took down all of the Sprint equipment but it looked like they installed some new cabinets so conversion is likely in progress.
  • Recently Browsing

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