Linked by Howard Fosdick on Sun 18th Dec 2011 05:12 UTC
Permalink for comment 501285
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
Carriers in general never do any significant number of infrastructure tools themselves (heck, they often aren't the ones actually building and maintaining their network)
It was always ~COTS; and such analysis can work also on the side of the network, which - as you say yourself - needs to actively track the state of connected devices anyway, to maintain that connection.
Curiously - many places where mobile phone networks are generally held in high regard ...somehow manage to not rely on CarrierIQ* / such style of tools. What the "network tools" provide seems more than enough (well, at least if a nicely functioning network with good coverage is the actual goal, I guess)
*working only on some smartphones, that's a great QoS... They are still a minority of phones; the radio stack runs on separate RTOS, separate ARM core (though, say, Symbian virtualizes it, not much difference), anyway; and they often have regressions of radio block design (already forgot iPhone antennagate / Brush of Death? Not "grip" - it's enough to bridge in one spot two stupidly exposed antenna sections) that should be resolved before using them as "tools" of network QoS.
Anyway, lets check out some information helpfully provided by... CarrierIQ: http://www.carrieriq.com/overview/IQInsightExperienceManager/Experi...
Capture a vast array of experience data including screen transitions, button presses, service interactions and anomalies
View application and device feature usage, such as camera, music, messaging, browser and TV
Yeah right, "not espionage" / "only network QoS"... ~half of that stuff is much more than that (and the rest can be glanced on the side of network)