US Wireless Carriers Shifting To Voice Over LTE 126
jfruh writes "For years for cell phone companies, one specific kind of data — voice calls placed by dialing a traditional telephone number — was entirely different from all the other kinds of data a phone used. But in the U.S., that's finally starting to change, as all the major carriers are planning shifts to voice over LTE. The carriers promise sharper call quality and quicker connections."
Will it count against the data? (Score:1)
Or will it be counted per minute? Per byte sounds more reasonable.
Re:Will it count against the data? (Score:5, Insightful)
Do you have any doubt that it will be counted as both?
Re: (Score:3)
Re: (Score:3)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
What's being discussed here is a software solution. Audio processing and compression done in software, on the general purpose CPU.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Voice Doesn't Use Much Data (Score:4, Informative)
I don't know the VoLTE protocols, but for regular PBX-style VOIP, the voice compression is good enough and the voice payload in the packets is small enough that most of the bandwidth is used for IP/UDP/RDP headers, not the actual voice. There are way too many standards to choose from, but most of them run about 5KB/sec or less (that's bytes, not bits), so about 300 KB/min, or about 3000 min for 1 GB. There are people who use that much voice time, but not many :-) I'd expect that for a while you'll see multiple different standards for handling hd-mobile-to-hd-mobile, sd-mobile-to-sd-mobile, mobile-to-wireline, mobile-to-other-mobile-carrier, etc.
Back around 1990, I went to a technology talk by a guy from MCI who thought that the conflicting economics of offering voice and video on the same network were going to be a serious problem for telcos - video at the time meant ~1.5-3 Mbps corporate teleconferencing, and either you could price video too high to sell much of it, or you could sell T1 bandwidth cheaply enough to make videoconferencing affordable, in which case you'd undercut your voice pricing because companies would buy your video T1s to interconnect their PBXs for cheap. Better video compression got us out of that hole for a few years (384kbps or especially 128kbps video didn't cause that much trouble), but the Internet came along and started doing the same technological undercutting, VOIP started becoming feasible, etc. Mobile phones gave us a way to charge lots of money per minute again, but Moore's Law is still relentless.
Disclaimer: I do work for AT&T, but I do computer security, not mobile phones, so I have no idea what they're planning to charge for this, this is my own opinion, not the company's, blah blah blah. On the other hand, I have been doing various kinds of telco things for many generations of technology :-)
Re: (Score:2)
Comment removed (Score:5, Informative)
Re: (Score:2, Informative)
Why would they do it for minutes?
As an experience and abused Verizon subscriber, I would offer several reasons.
(A) The can
(B) They want to
(C) They are Verizon
(D) All of the above
My guess is D.
Re: (Score:3)
Verizon does double-dip in some situations, and has TRIED to do it more, but once the DoJ put their foot on Verizon's neck and started investigating, Verizon changed their mind... Or rather, delayed the changes indefinitely, and eventually rolled them out only slowly to new customers and new de
Re: (Score:2)
Voice traffic is not worth measuring. It just does not take up bandwidth at all.
Re: (Score:2)
4500 minutes at 3G quality is on the order of 500MB. Surely upping your bandwidth cap by 500MB is insignificant when you pay for 4500 minutes.
Re: (Score:3)
everyone offers unlimited minutes these days
Re: (Score:3)
Re: (Score:1)
AOL (Score:2)
Re: (Score:3)
But Verizon beats that at .002 CENTS per KB [blogspot.com]
Re: (Score:2)
...byte sounds...
I see what you did there....
Seamless fallback (Score:5, Insightful)
Blindingly obvious to me is the fact that voice calls and SMS reaches me even without a high bandwidth 3G or faster data connection. If this leads to better network coverage for high speed data, I will be the first to celebrate, but until then I will stick to a split data/voice provider ... or one that can transition relatively seamlessly between the two types of networks...
Cheers!
Re: (Score:2)
Yep, they're doing seamless feedback (Score:3)
until [data coverage improves] I will stick to a split data/voice provider ... or one that can transition relatively seamlessly between the two types of networks
The article mentions that T-Mobile will implement handoff from VoLTE to the legacy system. "T-Mobile is using eSRVCC (Enhanced Single Radio Voice Call Continuity), a feature from the LTE Advanced set of standards, CTO Neville Ray wrote in a blog post. The new feature will ensure calls don't get dropped when users move into areas that don't have LTE, he said."
Re:Yep, they're doing seamless feedback (Score:4, Insightful)
Re: (Score:3)
And eventually you could use both frequencies you control for LTE, leading to much higher capacity.
Re: (Score:2)
And eventually you could use both frequencies you control for LTE, leading to much higher capacity.
Only if you have enough bandwidth in the older block of frequencies.
If they can't use a big enough chunk of frequency, they can't run LTE at a high speed.
It's been a point of contention around the airwave auctions, with AT&T in particular being pissed off about the terms.
Re: (Score:2)
I do not know if I should apologize for RTFA or that I made the post above without doing so....
Re: (Score:2)
Unfortunately, the major carriers keep scaling down the voice repeaters to increase the data bandwidth instead. The network I'm on (Sprint) is getting worse and worse for pure voice calls, with new dead zones appearing very frequently - all in a metropolitan area.
Soon the voice service will be so bad you'll be happy to permanently switch to VoIP.
Does VoLTE work from one carrier to another? (Score:3)
Re: (Score:1)
And will calls across carriers count against your data cap?
Re: (Score:2)
Re: (Score:2)
Heck it is IM different protocols. Except this is your phone.
Can't wait to see what happens when it hits the same iMessage fiasco.
Re: (Score:2)
So it won't make much of a dent at all (Score:2)
GSM phones will not talk to VoLTE phone with the current LTE revisions. A T-Mobile VoLTE phone cannot talk to an AT&T VoLTE phone (unless roaming- the latency requirements are too rigid to allow for it).
The main driver behind VoLTE is to get more traffic over to one type of network (4G) instead of having to keep two networks up and running (4G+3G).
So unless all major carriers merge into one, something that no sane national competition regulator will approve, all carriers will have to keep their 3G networks going more or less indefinitely. These limits would appear to prevent any substantial progress toward the "main driver". And good luck replacing the CDMA2000 flip phones that people still use precisely because voice-only service on a dumbphone is cheaper than voice and data service on a smartphone.
Re: (Score:2)
my GN3 makes calls just fine. why should i spend another $800 so the carrier can save some money?
unless i get a free phone with no increase in my bill i'll probably keep my GN3 for 3-5 years
Re: (Score:2)
Good luck complaining to your local carrier about poor quality on your 2G phone ("We understand sir, how about we ship you a Samsung Galaxy S4 for free?").
If carriers are willing to replace an outdated phone at no charge to keep a customer, that's one thing. But alen says it's unlikely to happen [slashdot.org]. How were the handset replacements associated with transitions away from AMPS and D-AMPS handled?
2G is going away fast - LTE's more efficient (Score:2)
My GPS uses 2G cellular to get its traffic data and gas prices and to do Google search for destinations. It's going away next year, because Garmin's contract with the cellphone carrier isn't going to be renewed :-(.
Carriers really want that spectrum back, and 3G and LTE are much more efficient in terms of data bitrate per MHz of radio, plus they want to cut down on the number of separate types of equipment (not only for equipment costs, but also because keeping two separate channels of data is much less ef
Re: (Score:2)
It seems strange to me that VoLTE needs *both* ends to support it in order to work. What about when you want to call a traditional non-mobile number? Surely they can't intend to keep 2G/3G around forever for this purpose, or is this feature planned for a later version of LTE?
Re: (Score:3)
It doesn't. They can terminate the VoIP call to the PSTN. It's just that when they control both ends it's possible for the devices to talk directly to each other, using whatever route the IP network finds most efficient, rather than forcing all calls out onto the PSTN or through their central VoIP server.
It's nothing different than the way SIP calling works today in non-mobile contexts -- all setup goes through a central server, and the server *can* route to non-SIP targets or forward voice traffic between
Re: (Score:2)
Makes sense, but then surely the same gateway could be used to let an LTE mobile phone talk to a non-LTE mobile phone, without the need to kick the handset itself onto 3G. I can understand the lack of urgency though - VoLTE is hardly a selling point and they'll have to maintain the older network for the forseeable future anyway.
Re: (Score:3)
GSM phones will not talk to VoLTE phone with the current LTE revisions. A T-Mobile VoLTE phone cannot talk to an AT&T VoLTE phone
Kinda sorta correct but only in a very narrow sense of "talk to." True, you can't currently roam across VoLTE carriers - which is why all these phones will still carry 3G chips for a long time to come. HOWEVER, when you make a VoLTE call, the carrier routes it back to their PSTN switches, and where it goes from there is immaterial - to a land line, to another carrier, to a data-less feature phone, wherever. So it's not like having a VoLTE phone means you can only call other VoLTE users on the same carrier -
Re: (Score:2)
Old tech. VoLTE is only for the air interface protocol in handling calls and passing them off to the POTS network.
You see, LTE is data only, and it work
Expose limits as unnecessary? (Score:2)
Re: (Score:1)
Is it possible to put a meaningful dent in data using voice?
5 hours a day using the highest voip kbps here (http://www.cisco.com/c/en/us/support/docs/voice/voice-quality/7934-bwidth-consume.html) gives me 80MB/month.
Voice Codecs and Protocol Overhead (Score:2)
Vanilla telco G.711 is 64kbps, and it's what the digital parts of a telco voice call use. G.729 codecs, mostly used for PBXs, use 8 kbps. GSM had several codecs, including 13.3, 6.5, and less. The problem with all of these is that they need to send lots of packets per second to minimize latency - typically 20 or 30 - so the transport protocol overhead is usually several times higher than the actual voice payload, between IP, UDP, RDP, plus any layer-2 overhead (Ethernet's huge, or ATM's a bit less, if yo
Re: (Score:2)
Google tells me that 150 hours * 8 kilobits per second is 527 megabytes per month. And that's the lowest bitrate I can find for wideband voice (G.729). Skype uses 5 times that.
Re: (Score:1)
yes, I messed up and only went to minutes from hours, shame on me.
For people that still talk a lot, it will be a relevant amount of data.
Re: (Score:2)
In my case, going with 15kbps because I'm hoping for that as a minimum, would be 43MB/mo. (wife and I combined) at my talking level.
Re: (Score:1)
I use about 30 - 300 minutes / month now.(wow, before smart phones I would regularly break 2000), so that's 3.5 - 35 at 16kbps (I used 2 KB, because google).
Re:Expose limits as unnecessary? (Score:5, Insightful)
Re: (Score:2)
But the current state of things is that we pay more for data than for voice.
Some problems (Score:2, Interesting)
First, data doesn't get the same protections as voice. Not that voice gets much protection as it is.
Second, carriers have said they will throttle data connections. This has serious implications for digital because it means carrier-to-carrier connections will (not may, will) be of inferior quality.
Third, I would believe digital was going to deliver, except that nobody uses much in the way of error-correction, the speakers and microphones are deteriorating in quality and reliability is naff.
Lastly, phone comp
Re: (Score:2)
http://www.jitterbugdirect.com... [jitterbugdirect.com]
My mom uses Jitterbug (Score:2)
Jitterbug's been a great phone for my mom. Her vision's not very good, so she doesn't bother texting (she'd need to hold a magnifying glass in one hand and use the phone with the other) , and she's stubborn enough she doesn't like to carry the phone around unless she expects to need it (e.g. going somewhere that she'll need to call a taxi), but it's reliable, does voice just fine, has big buttons for dialing, and makes free long-distance calls (so she doesn't bother buying long-distance from her landline t
Re: (Score:3)
My smartphone reboots itself regularly for no obvious reason.
That's probably not AT&T or verizon's fault though.
I used to be able to run a phone on full batteries for 2 days without a recharge. (Yes, phones "do more", but I don't bloody well want most of the more and the bits I do want aren't any bloody good! That is NOT a good exchange for 1/12th the uptime and nobody sells low-consumption phones any more.)
Well then go back to a dumb phone. 38 days of battery life on the nokia 515 [wired.com]. Or buy an expanded battery. Plus, again, how is that your carrier's fault?
I can't remember the last free phone upgrade offered.
Did phone companies ever offer you a phone that was worth more than $20 without a contract?
The first part of your post makes sense I think but asking AT&T to give you a free portable computer that has no software problems and doesn't occasionally need energy is a bit unrealistic.
Re: (Score:2)
Well then go back to a dumb phone. 38 days of battery life on the nokia 515. Or buy an expanded battery. Plus, again, how is that your carrier's fault?
I got the Nokia 301 (the plastic predecessor of the 515) before the 515 was announced.
The battery life is never 38 days unless you use your phone as a paper weight.
The phones have not lived up to the marketing hype and Nokia is several firmware updates deep in trying to meet their published specs.
IMO the relevant number to look at is talk time:
The 301 has 6 hours of 3G talk time.
The 515 has 5.3 hours of 3G talk time.
To put that into perspective, for the 515, every minute of talk is worth ~3 hours (171 minut
Re: (Score:2)
I used to be able to run a phone on full batteries for 2 days without a recharge.
I have an LG G2 and always get at least 50 hours before I hit 10% remaining on my battery. I have gone as much as 79 hours before getting down that low.
If my phone is idle, it uses around 1% per hour. Running most apps, I don't use more than 3% per hour, unless I run something that really uses the CPU or GPU. E-mail, web, light games, etc., all are easy on my battery.
That's on a phone with a quad-core processor, 1920x1080 screen, 2GB of RAM, and 32GB of flash storage.
Re:Some problems You're forgetting iPV6 (Score:1)
You're forgetting iPV6 has protections for VoIP as well as added other beneffits. As more carriers make the switch its reasonable to assume everyone will just use this down the road
Compact Disc error correction (Score:1)
Why do you want error correction of any sort for an audio stream?
Ask the inventors of Compact Disc Digital Audio why it includes CIRC error correction. I've had too many calls stay in the loss concealment zone to the point where unconcealed losses keep me from understanding the other party.
Error correction introduces latency
I don't see why it'd introduce more than 10 milliseconds.
Re: (Score:1)
By which mechanism would you do error correction for VoIP that won't introduce lots of latency? VoIP(SIP at least) largely uses RTP over UDP, sending packets with 20 milliseconds of audio data. It accepts that UDP is unreliable, and that losing 20 milliseconds of voice is not a problem. Latency (despite what you seem to think) is a real problem in voice. CDs buffer and play, they are not real time in any case. And the quality needed for a decent voice conversation is in any case quite different than t
Depends on the packet loss rate (Score:2)
Re: (Score:2)
If you do FEC, you need to buffer on the transmitting end. Built in latency.
If you do any sort of compression, such as linear prediction or cosine transform, you likewise need to buffer. Match the size of your FEC packets to your codec packets.
and if you are losing 10 consecutive packets
I apologize for being unclear; I didn't mean 10 in a row, just any 10 out of 50.
how can FEC help you?
We appear to have lost sync, and we won't be able to progress until we renegotiate definitions [c2.com]. Is a packet considered "lost" if it contains a single bit error at the receiver?
And besides, you are wasting lots of bandwidth to add the redundant data needed for FEC
When the receiver detects excessive errors, that means the channel capacity (in Shannon'
Re: (Score:2)
100 ms latency is perfectly fine for voice. VoIP from Europe to China with 400ms is surprisingly usable, most users do not notice the walkie-talkie effect. Anyway, it is trivial to do error correction for VoIP with far less than 100ms latency. The easiest solution is to include a digest of the previous packet in the following packet -- if the previous packet arrives later than the following packet or not at all, use the lower-quality data in the following packet. Spread the information across multiple packe
Re: (Score:2)
Error correction does not introduce anything like 400ms latency. 20ms lets you conceal the loss of one packet perfectly. 40ms allows you to lose two in a row. No humans will be able to detect 40ms latency.
Re: (Score:2)
The point you miss is that humans also won't notice the loss of a 20 or 40 milliseconds of data as long as the receiving end does something reasonable (e.g. replicating last received packet).
This is not true. Packet loss of less than 1% is detectable by actual customers with typical VoIP phones and the Alaw (or ulaw) codecs. It would be very handy to handle links with 0.3% packet loss, but that requires switching to codecs with built-in PLC, and transcoding is expensive.
Re: (Score:1)
My smartphone reboots itself regularly for no obvious reason. I used to be able to run a phone on full batteries for 2 days without a recharge.
This has happened to me before: you probably have some app with a memory leak running in the background (or possibly some malware). One common warning sign is when a free app started out good, but after some patch, started serving up a whole bunch of advertisement. Start with uninstalling any rarely-used free applications and see if the problem goes away, then update your other apps.
Data on the bus (Score:2)
I just use the old smart phone on wifi which is nearly ubiquitous in my regular haunts.
But how ubiquitous is Wi-Fi between haunts, such as while riding transit?
Lack of offline mode (Score:2)
What I learned over the years is that I don't need to be constantly plugged into the Matrix. It is actually better for my productivity
Until the applications that you need to use stop offering a useful offline mode in favor of increased reliance on "the cloud" (that is, someone else's computer). "Please connect to the Internet to save your changes." Or "Please connect to the Internet to identify this song" (as opposed to recording the snippet while it is playing and identifying it once you do connect; Google Play Song Search is guilty).
ISDN flashback (Score:5, Interesting)
Once upon a time when 128Kbps BRI ISDN was fast, voice calls were frequently billed at a lower per-minute rate than data calls. To take advantage of this, a common trick was to place a voice call and then pass data over it. This did result in a lower data rate of 56Kbps per channel or 112Kbps overall, but if that was enough, you could save a lot of money.
Fast-forward to VOLTE.
Most wireless carriers offer unlimited voice minute plans. Since it's all going to be IP over LTE now, I have to wonder if there will a way to pass your data off as a 'voice' call and avoid data caps and limits? Not on a stock phone, but on a rooted device with a custom OS build, maybe?
Re: (Score:2)
become incredibly proficient at whistling, save money.
Re: (Score:2)
so how does netflix look like at 64kbps? what about 256kbps?
Re: (Score:2)
Absolutely. There's nothing to stop you using a modem with your voice link. As in the ISDN days the bandwidth is much more limited when you used the encoded voice channel, and as with all voice connections you can only reach one endpoint at a time, but if you want to setup a PPP gateway someplace you can call into it and slowly exchange data with it all day long.
I suspect you'll have trouble improving upon the $/byte ratio when limiting yourself to cellular modem speeds -- your voice channel is probably les
Re: (Score:2)
Modern wide-band codecs use on the order of 50kbps for really high quality voice. If you use 50kbps continuously, you have added 16GB to your data cap each month (or 32GB is you transfer full duplex). Useful perhaps, but your phone would be constantly busy and battery life would suck. What are you going to transfer at 6kBps per second anyway?
Data masquerading as voice? Not likely (Score:2)
When you make a VOIP connection, you're signalling to the network that you want to do that, it finds you the IP address and port number, either for a gateway into the old telco network or else for the phone you're calling. That's not getting you out to the public internet, though if you've got another friend with another rooted phone who's also got an active wifi connection, maybe you could do something useful with it.
But remember the other signalling that's going on, between your phone and the cell tower
Re: (Score:2)
2G networks got about 20kbps data throughput. Sure, you could set-up a call and do some acoustic coupling for data modulation over a call, but that's the ballpark of the speed you'll be getting.
https://en.wikipedia.org/wiki/... [wikipedia.org]
Consumers wouldn't WANT the low speeds and inconvenience of the ad-hoc process, and I'm pretty sure business customers (like alarm service providers) could get dedicated data
Title II, when? (Score:2)
Data, communications, all synonymous, eh? I mean, HTTP really is a back and forth exchange.
Yep, reclassifying all Internet services as Title II makes so much sense.
Que Oversaturation in 3...2...1... (Score:2)
Remember a time when cellular carriers were trying to justify getting rid of unlimited data plans by claiming that the networks were becoming oversaturated?
Pepperidge Farms remembers. And we'll remember it when it happens again.
Re: (Score:2)
This will actually help!
First, voice doesn't use that much data. For example, Viber (a popular VOIP app) uses 0.5MB/min which would be about 0.5GB for 1000min.
More importantly, once every one is transitioned off 3G onto 4G/LTE (i.e. VOIP over LTE) the carriers can repurpose the 3G spectrum for 4G and thereby gain more 4G/LTE capacity.
Voice over LTE (Score:2)
Re: (Score:2)
A new way to screw your customers! Nice! (Score:2)
Voice and data are separated (Score:2)
The SIP signaling also uses a dedicated AP that cannot be used for anything else. Traffic is only allowed towards P-CSCF.
All the IMS client, Quality of Service and dedicated bearers are implemented in the baseband chip (Qualcom dominates that market) and is off-limits to the operating system of the phone, even to root.
Buh Byee Sprint (Score:1)
Which has no measurable LTE. But I'm sure they'll tell us they're 'upgrading the towers in your area' for the next 20 years.
T-mobile (Score:2)
Personally, I'd like to see mo
Re: (Score:2)
Call Quality :-) (Score:2)
Back in the 90s and early 2000s, we were trying to sell businesses on using 8kbps G.729 calls from IP PBXs instead of 64kbps telco voice, and they would whine about Mean Opinion Scores and latency (and didn't get that India just wasn't going to get any closer and the speed of light wasn't going to change.) Cell phones convinced most of those people that they didn't really need to care - GSM was 13kbps or 6.5, and your office PBX phones had much better microphones than a typical cellphone and usually didn't