Interesting article here about the impact of email and other background applications on mobile networks, commenting that regular polling of servers generates an increase in signalling traffic, even if the actual data being transferred is in small chunks.
This fits in with a theme I've been hearing a lot about recently - it's not just about the GB of data, there are other "resources" that need to be managed. Various people have also talked to me about power-control messages, number of separate parallel TCP connections and so forth.
This is likely to cause some interesting headaches for policy management and future business models - it's one thing to say (perhaps) that someone should pay for 10GB of video traffic traversing a network with a high QoS. At least there's a fair chance that all involved understand what that means, even if they don't like it.
But trying to tell application developers or content providers to keep a lid on their apps' consequential signalling traffic is a bit of a tall order, especially as it will probably be highly dependent on both the type of phone, and the precise way a given network has been configured (timeouts, power setting etc).
Separately, I've commented before that always-on applications also have a tendency to kill handset batteries, as they keep the radio in a high-powered state.
Dean Bubley's Disruptive Wireless: Thought-leading wireless industry analysis
4 comments:
Apple has been criticized a lot on their iPhone push solution but in fact it targets both your observations.
With their solution network resources are only used to indicate users that something needs their attention not for, mostly, useless polling.
Hi Dean,
I call the phenomena IP background noise. It's been on the agenda of 3GPP for HSPA+ and here's some background on how to improve network capacity for such noise with an enchanced Cell_FACH state :-)
http://mobilesociety.typepad.com/mobile_life/2008/05/more-hspa-enhan.html
Cheers,
Martin
Hi Dean,
Re your closing comment on device battery, check this interesting post from Ericsson Labs going into precisely this issue.
https://labs.ericsson.com/apis/mobile-java-push/blog/save-device-battery-mobile-java-push
Thomas
Eelco,
Even with solutions where application servers push data to the phones there are challenges.
One of the first resources exhausted in push scenarios are those associated with paging. And it is very much dependent on the paging algorithms used in the network.
Doug
Post a Comment