Paul Golding writes:
In my book and some workshops, I give an anatomy of a mobile phone. A bit of modem here, an operating system there, a sprinkle of APIs, MIDP sauce and so on. I include a “dialler application”, which is not often found on the average handset block diagram. It’s the thingy that takes numbers from the user and passes them to the “call processor” software wotsit, which in turn invokes a protocol stack to go send a “set-up call” message to the switch in the mobile network. Incrediblty boring, mundane and obvious. So obvious, that it doesn’t often get a mention in the block diagram/handset overview in many (most) treatments of the subject. Is this perhaps why it is so lacking in innovation? After all, it’s a dialler – it takes numbers and green-button pushes and does its stuff. Why tinker with this?
Telco marketers have come up with grand gestures of customer satisfaction like the theme of “connecting people” (it has its variants). However, about the only parameter they fiddle around with is the billing arrangement – call home all weekend for free and so on. When I dial a number, why can’t I get useful info about the number I’m dialling? For example, the rating of this plumber on plumber-pages-dot-com [don’t look – I made that up], or the time zone of the person I’m calling (good for all those Indian/US/Euro projects)?