Category: Uncategorized

Here’s some free advertising for T-Mobile. Stunning, so I had to link. Watch in HQ and full screen!

The T-Mobile Dance in Liverpool station:

And the ‘making of’:

Enjoy!

Not a truly mobile story today by itself but one that started as a such some time ago on this blog. A while back I reported on a first weakness found in the Wi-Fi WPA encryption. I didn't get all the facts right the first time and was promptly corrected by a reader who was kind enough to supply a link to Security Now, a great podcast show, that each week explains security issues at great length but easy to understand. I listened to the podcast, corrected my mistakes and subscribed to the podcasts on my N95 to have interesting podcasts while traveling. Recently I listened to podcast 172 about a program called Sandboxie for Windows machines that I think is so useful that I would like to mention it here.

With Sandboxie, you can put programs like web browsers, e-mail clients, instant messengers, etc. in a sandbox that redirects write access to files and the registry to a copy instead of to the original. This way should you catch a virus via a web page or via that attached power point file of an e-mail from a trusted friend, all the malicious code can do is harm a copy of the file and the registry. It can still steal data as it has standard read access to all other files but it can't harm the machine anymore. As soon as the last program in the sandbox ends, the files in the sandbox are deleted and gone is the threat.

It's even possible to install programs in the sandbox. They just run just fine afterward, but only in the Sandbox of course. Once you are done with testing, delete the sandbox and you can start from scratch. No orphan files remaining, no extra clutter in the already fat registry. So the concept of Sandboxie is quite similar to that of a virtual machine except that the applications have read access to the outside. The big advantages are that it requires no extra memory and processor resources, it just adds a shell of protection around those programs so they can't do any harm.

Completely blocking write access has it's drawbacks, too, of course. With a complete isolation, it's not possible to permanently store bookmarks for example and you will also loose your e-mail that is stored in local files once the sandbox is deleted. But the author has thought about that as well and it's possible to activate exceptions for the most well known programs so that their configuration and data files are not sandboxed. For less well known programs, it's possible to configure files or directories that are excluded from the sandbox manually. And, with the registered version, it's even possible to define programs which are automatically run in the sandbox when they are started. Great for an installation for less computer savy users to make the sandbox almost transparent for them.

So while it's not the purpose of Sandboxie to replace an anti-virus scanner it's a great tool to add another layer of protection. It takes some knowledge to configure it for individual purposes but once done, even less computer savvy users should not have a problem with it. So while the proof for that is still outstanding, I'll install it on a normob notebook soon 🙂

I love it how one gets from A to B on the web, I would never have heard of it would I not have blogged about the Wi-Fi WPA attack, if someone would not have commented and left a link and if someone else hadn't bothered to do a great podcast every week I listened to on my mobile phone during a long car trip. In this way, it is actually a mobile story after all.

This week, the Carnival of the Mobilists has stopped over at Tsahi Levent-Levi's blog, aka the VoIP survivor for an as usual impressive roundup of what's been happening in the mobile blogging sphere over the past week. To my great pleasure and surprise, my entry on the use of Wi-Fi in mobile devices has been voted for being the best post of the week. Thanks for that, I really appreciate it! So for all the best from the mobile blogging sphere, don't hesitate, head over and enjoy!

Quite often I discuss with colleagues and friends what went right and wrong over the years in 3GPP standardization. We usually agree that the first version of UMTS didn't get the data part quite right and that the first version of LTE has a serious problem with missing voice capabilities. Recently a friend said 'When 3G was designed, data was forgotten. When 4G was designed, voice was forgotten'. At first, I agreed to this but after some more reflection I think it doesn't quite hit what's happened.

I still remember vividly that when the 3G UTRAN (UMTS Terrestrial Radio Interface) was first designed, it was done with the purpose to add data capabilities beyond what was possible with 2G GPRS at the time. From that point of view, 3GPP has succeeded, because the 384 kbit/s downlink speed reached by first networks was an order of a magnitude higher than what was possible with GPRS at the time. However, the mindset at the time was still very much focused on dedicated channels on the air interface. So this was the method of choice for data transmissions despite the rest of the network being packet switched. Unfortunately, this lead to a very inefficient use of the air interface for packet data transmission such as web browsing with the resulting limitation in speed and number of simultaneous users. The situation was eventually fixed with the introduction of high speed shared channels, known as HSPA today.

Fast forward 10 years and we are now in the days of E-UTRAN, aka, LTE standardization. This time, the mindest was on packet switched only, at any cost. The cost was the 'down to earth – works out of the box' voice capability, which is sadly missing so far. I am sure there are quite a number of reasons for this but I think one of the main ones is that a majority of the companies in 3GPP are pushing for IMS and have been vehemently against any other form of voice capabilities. Other companies have made good suggestions, such as connecting the MSC to the E-UTRAN but so far the suggestion went nowhere.

Well, I guess it will be as in the case of UTRAN: A second round might be required before LTE can truly succeed UMTS.

After a year of hard work, it's a great pleasure to be able to announce the general availability of my latest book "Beyond 3G – Bringing Networks, Terminals and the Web Together". If you are a regular reader of this blog you can probably already guess what it is about. While the topics discussed in the book are similar to those I write about here, a book offers the opportunity to discuss them in much more detail and show the interactions between them.

O.k. so what's it about?

I start with giving a sound technical introduction to 3GPP LTE and SAE by explaining the decisions taken during standardization while also examining the likely competition for LTE such as HSPA+ and WiMAX. Capacity considerations follow. Then, I describe the latest mobile device developments, voice and multimedia services and the mobile web 2.0. Throughout the book, I do not only analyze how the systems, devices and software work but also the reasons behind why they are designed in this particular way. How these elements strongly influence each other is discussed as well as how network capabilities, available bandwidth, mobile device capabilities and new application concepts will shape the way we communicate in the future.

Some More Details

• I examine current and next-generation network technologies such as UMTS, HSPA+, WiMAX, LTE and Wifi
• Performance and capacity in practice are analyzed as well as future capacity requirements and how they can be fulfilled.
• You get an Introduction to the current cellular telephony architecture and to voice over IP architectures such as SIP, IMS and TISPAN.
• I look at mobile device hardware and mobile operating system evolution.
• And finally, I examine the major global wireless standards for application development and the latest state of the mobile web 2.0.

Where Can You Get it?

If I've aroused your interest and you are thinking about picking up a copy, there are many places to get it. It's available at Amazon.co.uk for next day delivery and Amazon.com in the U.S. will start shipping it in the next couple of days.  You can also order it directly at my publisher John Wiley & Sons, their worldwide shipping department is very efficient. You can of course also go to a book store and give them the title and the following ISBN number: 978-0-470-75188-6.

Browsing The Book Online

For more details, Amazon offers a 'look inside the book' function and a keyword search which brings up a list of all pages where the word is mentioned. From there you can jump to a page and also see a couple of follow up pages.

There we go! If you like this blog, then this book is definitely something for you! As always, I am glad about feedback and I wish you happy reading!

When I see one of my non-tech friends having bought a new mobile I always ask them a lot of questions about their new toy to figure out what works and what doesn't. Recently, one of my friends bought a Nokia N78, following my advice, as he wanted to have a nice phone, a good camera and mobile Internet connectivity. Also following my advice, he installed OperaMini, all by himself, I might add, and has figured out how to use the built in Wi-Fi to browse the web at home. Not bad I would say. But here are a some basic things he has not figured out by himself:

• Multitasking: He always used the 'red' button to end an application instead of the Symbian menu button. When I showed him he was very surprised and asked me how he could have known this. Right, how could he have known this!? But he was very happy about it because he immediately saw the value of just sending the browser and other applications to the background and returning to it later.

• GPS: He wasn't aware that GPS is only working outdoors. Therefore he was not sure if his GPS was working or not and a bit displeased with Nokia Maps for not showing him were he was. At least, the APN for the A-GPS was configured automatically so if he had tried it outdoors it would have worked. Maybe a notice when starting up Nokia Maps for the first couple of times to try it outdoors would help.

• E-Mail configuration: He asked me if he could also receive is personal e-mail on the phone. Sure you can I said, let's configure it together next time we see each other and you have all the required configuration information (pop, smtp server, etc.) Hm, the right answer would have been: Sure no problem, just type in your e-mail address and password and the phone figures out the rest. To this end, I think Nokia has made great progress already, as it worked pretty much like that on the Nokia 5000 when I was tested that device a while ago.

• Idle screen configuration: To start OperaMini he always went to the menu, selected applications and scrolled down to the OperaMini icon instead of putting it as a small icon on the idle screen for fast selection.

If I remember right, Nseries mobiles have a kind of "First Steps" application to inform new users about the capabilities of the device and maybe to teach them some tricks. However, I don't have it on my own device I must have probably deleted it. In any case, he did not use it, not sure why. So it might help to put that application into a more promiment place, add some more basic tips and tricks and maybe to ask the first couple of device startups if the application should be started. Or how about a discovery mode where tips&tricks are shown until the user turns it off? For the moment, I've sent him this link for further advice.

I last checked the Flickr camera statistics back in January 2008 and at the time, the Nokia N95 was the most used camera phone from which pictures were sent to Flickr, with the iPhone in hot pursuit. At some point in 2008, however, the iPhone has clearly surpassed the N95. While the graphs don't show absolute numbers the manufacturer statistics do and it's worth taking a look:

• From the Nokia N95, about 1100 users upload pictures daily. Whether that is directly from the phone or via a PC can't be seen. When taking the numbers of all Nokia models together, there are about 3500 users uploading pictures daily. The total number of pictures uploaded with the N95 is around 3.6 million.

• From iPhones (Flickr does not distinguish different models), there are about 3000 users that are uploading pictures daily. Again, it's not distinguishable if this is directly from the phone or via a PC. The total number of pictures taken with an iPhone and stored on Flickr is around 6 million these days.

Now let's compare that with the most popular non mobile phone camera, the Canon Digital Rebel XTi DSLR:

• From the Canon Digital Rebel XTi, there are about 6800 users that are uploading pictures daily. The total number of pictures on Flickr from that camera are 51 million, and one should probably also add the 60 million pictures taken with the Digital Rebel XT.

Sounds like a lot more!

But then, when looking at point and shoot cameras from Sony, Panasonic, Canon, etc., the picture once again changes a bit. Even the Sony Cybershot DSC-W55 has 'only'  770 users uploading pictures daily. In all fairness, one should add the number of users uploading pictures for the other leading Sony cameras in the statistic and then compare that with the N95 and the iPhone. The numbers become quite equal then.

And again from a different perspective: When looking at 'all brands' sorted by most popular brands, Nokia is in 9th place, Sony Ericsson in 10th, and Apple beyond 30. Unfortunately, the statistics don't take into account how long a model has already been on the market (a disadvantage for Apple I suppose) and it's also not stated over which timeframe the numbers were summed up. It would be interesting to see the statistics over all cameras for 2008 only, I think they would look quite different. For the moment, however, I would say that 'stand alone' cameras are still more popular than mobile phones for pictures uploads to Flickr. Let's see how the statistics look a bit later in the year.

As a follow up to yesterday's post on touch I've been wondering if Java programs have any means today to make full use of a touch screen with existing JSRs available on mobile devices or if support of a new JSR is required for that? I've been browsing a bit trough the list of APIs of the Nokia 5800, but as a non-Java developer it doesn't tell me a lot. It would be good if programs such as OperaMini that are used on devices of a great number of different manufacturers would have the possibility of using a standardized API. Anyone out there aware of what is (already) available/possible?

Lately, I've had the opportunity to experiment a bit with a Samsung F480, also known as the Toco, one of Samsung's touch screen phones. At a price point of 300 euros without a contract one would expect it to be a smartphone, as devices such as the Nokia N78 are available for less these days. However, it is not. Instead, it's a classic mid-range phone with a touch screen, so a bit pricey for it's capabilities.

That said, however, I found the touch screen implementation to be very good, intuitive and easy to use. A well done device that will surely find it's customers. After having gotten used to the large screen and big icons, it takes a minute to adapting again to the comparatively small screen of the N78. Many people will feel the same when taking the decision in a shop for which phone to go so this is a big advantage for touch phones in general.

When I look around in the metro these days I see a lot of touch based phones and mobile devices in the hands of non-geeks. Quite a rapid adoption in less than a year. The F480's touch interface can be used with one hand only, something that I think is very useful in crowded places such as the metro.

I guess what many people find appealing about touch user interfaces apart from the bigger screen sizes is the missing indirection from what they see to what they press. You want to launch the calendar application, you simply click on it instead of using the D-pad at the other end of the phone to first scroll through the icon list to select it. It's straight forward.

So where is Nokia with touch phones these days? There is the Nokia 5800 but it is still not generally available in December 2008, so Samsung, LG and others have a considerable advantage for the moment. I guess it has something to do with Nokia implementing the touch interface in their high end S60 smart phone OS, i.e. the task takes considerably more time than for a mid-range phones with a limited amount of software on it. There's a good review by Rafe Blandford of the 5800 and he comes to a similar conclusion.

In addition, what makes a smartphone powerful is the number of third party applications. While most current applications will run on a touch enabled S60 device they can't take advantage of the touch based UI unless they are adapted. Take OperaMini for example which is strongly keypad/shortcut based. For efficient use on a touch device a separate touch version needs to be developed so zooming, scrolling and selecting commands and options works via the touch interface as well. Many software developers won't be too happy about developing yet one more version / input method. 

The first N-series touched based device, the N97, is still at least 6 to 9 months out. That's a long time to wait. But it seems there are not many alternatives for me at this time. The iPhone is too restrictive, Windows Mobile based touch devices only seem to have a touch layer for use with fingers in the front with most applications in the back still being stylus based. And also, OperaMini is not yet touch based… Still too many obstacles for the moment.

Recently, Vodafone Germany's boss is quoted (in Germany) saying that Vodafone Germany currently spends a middle three digit million sum a year on power for its mobile networks in Germany. Interesting, so let's break that number down a bit.

Let's assume that Vodafone's yearly power bill for their complete GSM and UMTS networks is 400 million euros and that their DSL assets are not included. I am not certain of the later one but there's no telling if that is the case or not and how much power their DSL lines use. Let's further speculate that around 25 million people in Germany are using their network today (not SIM cards!). 400 million euros / 12 months / 25 million people = 1.3 euros per person per month.

I'd say their revenue per person (i.e. not ARPU per SIM card) is around 15 euros, which is probably on the conservative side. So around 8-10% of that is spent on power.

At a rate of 0.2 euros per kW/h, that means I 'personally' use about 6.5 kWh of power a month for mobile telephony and mobile Internet access. An interesting number, that is a bit higher than the 1.4 kWh that resulted from a calculation in this previous post. In the previous post however, a global average was given which did not take into account that in most European countries, most network operators have both a GSM and a UMTS network, thus doubling power consumption compared to countries which only have GSM networks. Also, networks are much more heavily used per person in industrialized countries, which again increases the power consumption per person as more base stations are required. For the total power use for my mobile activities one has to of course also add the power for recharging the mobile phone and to a certain extent also the power consumption of my notebook.

It would be an interesting comparison how much power is required for my fixed line DSL and telephony connection at home and in the office. The DSL modem / Wifi access point / DECT phone setup (let's say this is my private fixed line mini base station) consumes at least 15 watts, which amounts to 15 watts * 24 hours * 30 days = 10 kWh a month. In this number, the power requirements of the network behind is not yet included.

While not directly comparable, each of those numbers give an interesting insight into how much power is required per person to drive our information society. Compared to the several hundreds of kwh of power per month consumed per person in Europe, however, the number is not negligible but still quite small.