« 4G and Peak-Rate Marketing | Main | News from Wireless Austria »


TrackBack URL for this entry:

Listed below are links to weblogs that reference The FACH Power Consumption Problem:



Interesting Analysis. From an operator point of view the trade off is between saving resources (such as use of Radio Base Stations HW consumption, SF Codes, RBS Power ecc) that leads to fast DCH to FACH switches; while on the other hand it’s important to reduce “unnecessary” channel switching (ex. DCH to FACH to DCH within few seconds) to improve user experience and reduce signalling messages.
Battery power drain can be a problem but optimising a network it’s interesting to know what kind of device is used for PS traffic. If the majority of our user connect to the network with PC data cards, battery consumption becomes a lower priority matter... :-)Anyway the use of common channels is becoming an interesting topic and new timers are often tested and implemented, following the evolution of traffic patterns in our network

Mark Livas

Hi Martin, as always interesting post. I am aware of a number of devices with embedded e-mail clients which actually trigger the release of the RRC connection so they don't have to go through the state transitions and waste battery. According to the specs the RRC connection cannot be released by the UE directly so what they have implemented is a RRC SIGNALLING CONNECTION RELEASE which triggers the release of the PS RAB (from the SGSN point of view). Once this occurs the RNC releases the RRC connection as well.


With devices like Blackberries that are true push, I wonder if they would offer better battery life. RIM is starting to roll out 3G devices so we should be able to soon get data.

As well, Apple offers true push now and enterprise (Microsoft) integration.

The comments to this entry are closed.

My Photo

The Books to this Blog

Prepaid Wireless Wiki

My Pictures on Flickr

  • www.flickr.com
    martin.sauter's photos More of martin.sauter's photos

Android Cell Logger App


  • Clicky
    Clicky Web Analytics