My grocery store sells generic versions of bottled water, soap, breakfast cereal, butter, milk and mobile voice/Internet service. Now thats quite remarkable considering Rewe, the German grocery store chain I am alluding to, doesn't really have a history in the German telecommunications market. What they do have are 15445 stores across Europe that can stock up prepaid SIM cards branded "ja! Mobil" (the name comes from their generic in-store brand). Their physical presence and the mind space ja! occupies drives their business model. If shoppers can drink ja! branded generic cola then they could as well use ja!-branded mobile voice/Internet service.
The innovation here is the marketing possibility offered by Rewe grocery stores (instead of any technical innovation). Rewe has partnered with T-Mobile in Germany to implement its ja! branded "mobile operator". T-Mobile provides a white-label technical platform and Rewe simply brands it "ja! mobile". T-Mobile wins because it gets to sell its service at a discount to lower-paying market segments without putting off the premium T-Mobile customers, Rewe makes a neat profit by leveraging the ja! brand, and the customer wins by getting a discounted service from the best mobile operator of Germany, minus the T-Mobile brand.
I was looking at ja! mobile pricing. There are various flavors of pre-paid and flat-rate plans, although the focus seems to be on pre-paid plans that require no long-term contract and can be dispensed at Rewe's check-out counters. Depending on a customer's typical usage, s/he can can trade-off get a discounted subset of services from among the services offered - SMS, MMS, in-network calling, fixed-line calls, data etc. Interestingly, customer support is not free. Its a little like the contemporary airline business where everything from customer service to carry-on baggage can become a chargeable add-on rather than part of the product. Customers need to be mindful of what their money is buying them before assuming that things like customer service or technical support is part of the product.
Brick-and-mortar stores also sell iTunes gift cards and Facebook credit nowadays. Dell and Amazon partner with Best Buy to sell computers and Kindle e-books respectively. There are interesting business opportunities for anyone who can funnel real customers and subscribers (read: money) into the virtual/communications world. Very real profits await those brick-and-mortar outfits who can build bridges between technology companies and customers, even if they are just plain-Jane grocery stores!
Sunday, October 31, 2010
Wednesday, October 13, 2010
Fancy Vertical Handover: A victim of REST?
There has been a ton of research, standardization work, and development around Vertical Handover - the ability to change the underlying network access without disturbing the overlying communication protocol (TCP or application) sessions. The simplest example is when a user moves from a Wifi zone (e.g. office) to a 3G zone (outdoors). A seamless handover hides the underlying rewiring of the access and lets the user continue using the device as if nothing changed. Vertical handovers have quickly graduated from laboratory quirk to mainstream occurance, with Wifi-enabled smart-phones switching between access technologies multiple times daily.
But the vertical handover on my smart-phone doesn't really preserve the underlying TCP session and yet works pretty well. Why? Because most of the apps on my phone use REST-ful protocols like HTTP, XML-RPC, or SOAP. That means they are, in theory, stateless. In fact, a TCP connection is created and torn down for every message exchange between the service server and the client. Sometimes TCP connections linger on to improve efficiency (carrying multiple request-response mesages between the client and service server), but a discontinuity in the TCP connection is not catastrophic. I simply see my smart-phone negotiate a new connection with the new access (3G or Wifi) and then my app keeps working as if nothing has changed.
All that talk about preserving TCP connections across access technologies was much ado about nothing!
But the vertical handover on my smart-phone doesn't really preserve the underlying TCP session and yet works pretty well. Why? Because most of the apps on my phone use REST-ful protocols like HTTP, XML-RPC, or SOAP. That means they are, in theory, stateless. In fact, a TCP connection is created and torn down for every message exchange between the service server and the client. Sometimes TCP connections linger on to improve efficiency (carrying multiple request-response mesages between the client and service server), but a discontinuity in the TCP connection is not catastrophic. I simply see my smart-phone negotiate a new connection with the new access (3G or Wifi) and then my app keeps working as if nothing has changed.
All that talk about preserving TCP connections across access technologies was much ado about nothing!
Wednesday, October 6, 2010
Mobile Video Calling: Can Tango Tango?
Tango is a newly launched mobile-to-mobile video calling application for iPhone and Android devices. Tango enables smart-phone owners to see each other in addition to speaking with each other during a Voice Over IP (voip) conversation. Many smart-phones come with front facing cameras, ostensibly for video calling, and Tango enables people to use these cameras during a voip call. Think of mobile video calling when you want to see your expat pet doing silly tricks on video (or for beach and boardroom voyeurism).
But, as Walter Mossberg's Tango's review in WSJ reports, the quality of Tango's video call leaves a lot to be desired. I came across a video on Gizmodo's website showing Tango in action. The verdict is that Tango's performance is way below expectation. In fact, Tango's video frame-rate seemed to be approximately 1 frame per second in the Gizmodo video (and not the "high quality video mobile calling service" as the company's press release claims).
Make no mistake, achieving even 1 frame-per-second video+voice is no small feat. Tango's engineers have packed a real-time video+voice encoder/decoder into a smart-phone and have managed to trasmit/receive two parallel audio/video streams over Wifi (they also claim high quality video calls over 3G but lets not give Tango all the benefit of doubt :-) ). On top of this, achieving this for both the Android and iPhone platforms and for dozens of smart-phone models is admirable.
Frankly, I am not surprised by Tango's dismal video frame rate - resource bottlenecks such as smart-phone hardware, software/OS, network bandwidth and latency have to be overcome before an acceptable double digit frame-rate is achieved. But what surprised me was the poor voice quality: the Tango call sounded a lot like those cheap international calling cards I used to make international calls from the US many years ago. Terrible sound quality. I wonder why Tango engineers didn't trade more video quality (or even cut out video entirely when resources were scarce) and spend resources on improving voice? Voice over IP for mobile phones is a solved problem - Skype and the umpteen number of mobile SIP voip clients got audio to work well even on older smart-phones. Why couldn't Tango?
Tango is an over-the-top application, meaning that it runs over the best-effort (ordinary) Internet. I mention this here because the alternative, 3G telecom-operator-supported video calling, uses a dedicated network channel to ensure call quality assurance. But a Tango call will be carried over the same pipes as plain web traffic, making the video/voice call quality dependent on what else is being transmitted during the call. Telecom-supported 3G video calling is also much more energy (battery) efficient than Tango.Why? Because in order to remain signed-into Tango to receive calls, the smart-phone has to periodically send "I-am-alive" messages to the Tango server. This means that a TCP or UDP socket is always active (or repeatedly created and and torn-down), effectively disabling the smart-phone's built-on power-saving sleep function. Offcourse, telecom supported 3G video calling costs money, but it is technically superior to Tango or any other over-the-top mobile video calling system.
But this is not about Telecom vs. Internet applications. This is about the use-case. Video calling was touted as one of the big use-cases for 3G Telecom networks (and 4G too?). 3G standards support video calling and so there is hardware acceleration, network resource reservation, optimized audio/video codecs, and cross-phone/OS support for video calling on every modern smart-phone. But apart from the cost of making 3G video calls, is their something else that relegated video calling to its sad never-used status in phones? Yes there is. Video calling has simply not been accepted as a viable form of mass communication in our society, and remains to-date, a quirky add-on. When was the last time you placed a video call?
When Internet telephony (voip) arrived it quickly replaced circuit-switched calling. With mobile video calling, even if Tango can eventually fix its technical/engineering limitations, there is nothing to replace! Sadly, the mobile video calling use-case was still-born from the beginning.
Make no mistake, achieving even 1 frame-per-second video+voice is no small feat. Tango's engineers have packed a real-time video+voice encoder/decoder into a smart-phone and have managed to trasmit/receive two parallel audio/video streams over Wifi (they also claim high quality video calls over 3G but lets not give Tango all the benefit of doubt :-) ). On top of this, achieving this for both the Android and iPhone platforms and for dozens of smart-phone models is admirable.
Frankly, I am not surprised by Tango's dismal video frame rate - resource bottlenecks such as smart-phone hardware, software/OS, network bandwidth and latency have to be overcome before an acceptable double digit frame-rate is achieved. But what surprised me was the poor voice quality: the Tango call sounded a lot like those cheap international calling cards I used to make international calls from the US many years ago. Terrible sound quality. I wonder why Tango engineers didn't trade more video quality (or even cut out video entirely when resources were scarce) and spend resources on improving voice? Voice over IP for mobile phones is a solved problem - Skype and the umpteen number of mobile SIP voip clients got audio to work well even on older smart-phones. Why couldn't Tango?
Tango is an over-the-top application, meaning that it runs over the best-effort (ordinary) Internet. I mention this here because the alternative, 3G telecom-operator-supported video calling, uses a dedicated network channel to ensure call quality assurance. But a Tango call will be carried over the same pipes as plain web traffic, making the video/voice call quality dependent on what else is being transmitted during the call. Telecom-supported 3G video calling is also much more energy (battery) efficient than Tango.Why? Because in order to remain signed-into Tango to receive calls, the smart-phone has to periodically send "I-am-alive" messages to the Tango server. This means that a TCP or UDP socket is always active (or repeatedly created and and torn-down), effectively disabling the smart-phone's built-on power-saving sleep function. Offcourse, telecom supported 3G video calling costs money, but it is technically superior to Tango or any other over-the-top mobile video calling system.
But this is not about Telecom vs. Internet applications. This is about the use-case. Video calling was touted as one of the big use-cases for 3G Telecom networks (and 4G too?). 3G standards support video calling and so there is hardware acceleration, network resource reservation, optimized audio/video codecs, and cross-phone/OS support for video calling on every modern smart-phone. But apart from the cost of making 3G video calls, is their something else that relegated video calling to its sad never-used status in phones? Yes there is. Video calling has simply not been accepted as a viable form of mass communication in our society, and remains to-date, a quirky add-on. When was the last time you placed a video call?
When Internet telephony (voip) arrived it quickly replaced circuit-switched calling. With mobile video calling, even if Tango can eventually fix its technical/engineering limitations, there is nothing to replace! Sadly, the mobile video calling use-case was still-born from the beginning.
Wednesday, September 1, 2010
Android Device Chatter with the Google Mother Ship
Parts of this post were moved into a formal research study (click link below).
https://sites.google.com/site/sachinkagarwal/home/publications-talks/gis-2011-infocom-2011
https://sites.google.com/site/sachinkagarwal/home/publications-talks/gis-2011-infocom-2011
Saturday, July 3, 2010
Microsoft Kin: RIP == Social Networks:RIP (?)

Microsoft Kin 04/2010-06/2010
Microsoft is phasing out its social-network/cloud storage-heavy Kin smart phone just 2 months after launch. This embarrassing report from CNN claims that the Microsoft+Verizon Kin sold less than 10000 units in the two months. RIP Kin.
I never got around to using the Kin, but apparently the market didn't see the justification for the expensive data plan (>=$29 p.m.) tagged on to the Kin by Verizon. The market was supposed to be teens looking to stay connected via social networks, but they did not bite into the insanely high data-plan tariff. Social networking, it seems, is not worth that much to them. How much is it worth anyway?
Lets not belittle the effort Microsoft put into this device - as a product the Kin was fully functional and seemed to do the things you would expect from this sort of device - Internet social networking, cloud storage and syncing of users' data, a built in Zune player, sleek design, etc. And at under $100 (with a data plan) it had a low entry barrier too. It seems like all the pieces were there but the Kin machine never got off the ground.
I don't know if the lack of a credible app store spelt the end for the Kin. What I do know is that social networking apps completely failed to drive sales. Next time someone uses social networking as the use-case for a device or service that is supposed to make money, say - Kin!
Lets not belittle the effort Microsoft put into this device - as a product the Kin was fully functional and seemed to do the things you would expect from this sort of device - Internet social networking, cloud storage and syncing of users' data, a built in Zune player, sleek design, etc. And at under $100 (with a data plan) it had a low entry barrier too. It seems like all the pieces were there but the Kin machine never got off the ground.
I don't know if the lack of a credible app store spelt the end for the Kin. What I do know is that social networking apps completely failed to drive sales. Next time someone uses social networking as the use-case for a device or service that is supposed to make money, say - Kin!
Friday, April 30, 2010
Untitled Poem
Among many other things, my father taught me how to read and write English. Everything I've ever written starts with what he taught me. Now as he lies dying of cancer, I wrote this for him. Say a prayer for him.
All of my thoughts
Like river drops
Together making up me
Like a river that flows
Until it throws
Fresh into the salty sea
All rivers meet that end
No matter what they pretend
Or how many bends they make
And so it will be
With every drop inside me
No matter what path I take
So you may ask
The point of the task
To meander toward the salty end
But don't we all know
Drops become vapor and snow
From which new rivers descend
All of my thoughts
Like river drops
Together making up me
Like a river that flows
Until it throws
Fresh into the salty sea
All rivers meet that end
No matter what they pretend
Or how many bends they make
And so it will be
With every drop inside me
No matter what path I take
So you may ask
The point of the task
To meander toward the salty end
But don't we all know
Drops become vapor and snow
From which new rivers descend
Friday, January 8, 2010
Plug and play internal HDDs, literally!
I just saw this contraption on a colleagues desk. As you can see, a 3.5" HDD is literally plugged into the dock as if it were some super-sized memory card . Well, thats exactly what it is. The dock also has ports for USB keys, SD cards, and probably a few other formats.
Interesting to see the form factor difference between the SD slot and the 3.5" HDD slot. Flash memory capacity is quickly catching up with HDD capacity (the latter's lead has shrunk to only about ~10x). HDDs are endangered species!
Monday, December 14, 2009
India's Broadband Future
Ajit Balakrishnan, CEO, Rediff gave a keynote in IIT Delhi earlier today. His talk suggested that Indian telecommunication operators and the government should not be concentrating at delivering niche multi-Mbps broadband services but should instead concentrate on delivering reasonably good service (100s of kbps) to a larger population. Ajit flashed a slide which showed that 86% of 3G users use their smartphones to access their email, a relatively low bandwidth application, but only 6% use 3G to download and watch videos. Ajit's point was to recognize the importance of broadband as an "always on" connection rather than a high-bandwidth connection in India.
There is a analogue in India's history to this choice that Indian telecommunication operators and the government has to make. The government of India created top notch higher education institutes - IITs, RECs, and IIMs - in the 1950s (after Indian independence). It spends tens of thousands of dollars per year on each student enrolled in these institutes, arguably at the expense of thousands of primary education schools in backward areas of the country. The thinking at the time of creation of these institutes was that this creme de la creme would catalyze the growth of industry and technology in the country. Similarly, it may be theorized that by providing high-speed Internet connectivity, early adoptors will drive applications and create demand in the general population to upgrade their connectivity.
Countries like China or South Korea concentrated on their primary education institutions rather than creating world-class higher education institutes. It is safe to say that both these countries are significantly ahead of India, measured via any human development index. But does this analogy suggest that India should concentrate on democratization of (relatively low speed) broadband rather than creating small pockets of high speed broadband?
I think that the market forces will decide the balance between broadband services in India. The ARPU on low-speed broadband may not exceed $5, but this will be compensated via large volumes. I also believe that low-speed broadband will be served via wireless in India. With mobile phones outpacing fixed line connections by a 12:1 ratio in the country, there is limited scope for technologies like DSL to be widely deployed. Fortunately, 3G, LTE and Wimax are nicely poised to fill in for the lack of fixed line infrastructure in India. As for the niche multi-Mbps broadband, I expect FTTX being deployed in highly urbanized areas where western ARPUs (10s of dollars) are possible.
There is a analogue in India's history to this choice that Indian telecommunication operators and the government has to make. The government of India created top notch higher education institutes - IITs, RECs, and IIMs - in the 1950s (after Indian independence). It spends tens of thousands of dollars per year on each student enrolled in these institutes, arguably at the expense of thousands of primary education schools in backward areas of the country. The thinking at the time of creation of these institutes was that this creme de la creme would catalyze the growth of industry and technology in the country. Similarly, it may be theorized that by providing high-speed Internet connectivity, early adoptors will drive applications and create demand in the general population to upgrade their connectivity.
Countries like China or South Korea concentrated on their primary education institutions rather than creating world-class higher education institutes. It is safe to say that both these countries are significantly ahead of India, measured via any human development index. But does this analogy suggest that India should concentrate on democratization of (relatively low speed) broadband rather than creating small pockets of high speed broadband?
I think that the market forces will decide the balance between broadband services in India. The ARPU on low-speed broadband may not exceed $5, but this will be compensated via large volumes. I also believe that low-speed broadband will be served via wireless in India. With mobile phones outpacing fixed line connections by a 12:1 ratio in the country, there is limited scope for technologies like DSL to be widely deployed. Fortunately, 3G, LTE and Wimax are nicely poised to fill in for the lack of fixed line infrastructure in India. As for the niche multi-Mbps broadband, I expect FTTX being deployed in highly urbanized areas where western ARPUs (10s of dollars) are possible.
Sunday, December 6, 2009
Thermal imaging cameras at Bangalore airport!
Arriving on an international flight at the Bangalore International airport, I was surprised to see two thermal imaging cameras. Each camera was looking at arriving passengers and visually marking those who had an elevated body temperature, in order to discern people who may be suffering from Swine Flu. These cameras are sensitive to IR heat radiation in the body temperature range. The cameras work by mapping temperature readings into a colormap that visually depicts body temperature. The video images produced by the cameras looked eerily similar to the IR images that the alien saw in the Predator movie series!
As compared to conventional body temperature measurements via thermometers, this real-time technique makes it possible for a medical officer to screen many more people. I wonder why these systems are not installed in other world airports.
Tuesday, November 24, 2009
Multiprocessing vs. Network I/O
I've been reading up on Python's (v2.6 and above) multiprocessing module. While multiprocessing has been around for a long time, simplified libraries like this multiprocessing module may spur even casual programmers to consider parallelism in their programs. My feeling is that if issues like inter-process communication, synchronization among processes, and deadlock avoidance are dealt with painlessly, then many non-professional programmers would feel confident enough to load up CPUs with programs with multiple processes to speed things up. Moreover, given that multiple CPU cores are becoming the norm rather than the exception on commodity hardware, there is a real incentive to eventually switch to multiprocessing.
What will this switch in program design mean for network data I/O? Will average users end up opening and using more network connections on average? Web browser tabs are a good example of multiple threads or processes. When modern browsers fire up they often connect to several websites saved from the previous session. I conjecture that multiple tabs fill up the network's queue faster than was possible with single core CPUs. Although Network I/O is much slower than CPU bandwidth (data rate at which CPUs process say, HTML), there is a point beyond which a single core CPU becomes the bottle-neck (e.g. firing a dozen browser tabs). But multiple cores remove this limitation and drive network I/O to its physical (or traffic-shaped) limits. I plan to measure this interplay between multiprocessing and network I/O. Watch this space!
What will this switch in program design mean for network data I/O? Will average users end up opening and using more network connections on average? Web browser tabs are a good example of multiple threads or processes. When modern browsers fire up they often connect to several websites saved from the previous session. I conjecture that multiple tabs fill up the network's queue faster than was possible with single core CPUs. Although Network I/O is much slower than CPU bandwidth (data rate at which CPUs process say, HTML), there is a point beyond which a single core CPU becomes the bottle-neck (e.g. firing a dozen browser tabs). But multiple cores remove this limitation and drive network I/O to its physical (or traffic-shaped) limits. I plan to measure this interplay between multiprocessing and network I/O. Watch this space!
Thursday, November 12, 2009
Free airport Wifi as a marketing tool
Google is offering free Wifi in 47 US airports during the holiday season The idea is to flash a few web pages marketing Google's software and services to users in return for free Wifi service. According to this CNN article, Google is not the only company to do so - apparently Lexus and Ebay have also implemented similar ideas, or intend do so in the near future.
Free service is probably going to bring a torrent of airport Wifi users online - probably many more than the current number of (paying) users. Given that Wifi Internet channel space is a shared resource, it will be interesting to see how airport Wifi scales with the up-tick in usage. I just hope that the service doesn't deteriorate so much that the sponsoring companys' well-meaning message is lost to disgruntled users. And I do hope that engineers running these Wifi access points have done the networking provisioning Math beforehand.
Now the economics. The sponsoring company (Google) is probably going to pay a lot less than the retail price of airport Wifi connectivity. Why? Because the sheer volume of users will be much higher than when users have to pay individually. I think that the payment will include a fixed component depending on the number of access points participating in the service, and a variable component depending on the number of users accessing the service.
Lets assume that an average airport has about 20 accessible Wifi access points. Each access point can support (with any reasonable quality of service) about 10 concurrent users. If the airport is busy for, say, 12 hours in a day, and further say that we assume an average utilization of 50% of the total capacity of the access points, then we have (per day)
10 * 20 * 12 * 0.5 = 1200 hours of usage per day per airport.
I would assume that the sponsoring company (Google) would pay about $5000 per day as a fixed cost and then about $1 per hour usage. This brings the daily total cost per airport for the sponsoring company to $5000+$1200 = $6200.
So for 47 airports and 50 holiday season days, we are looking at a bill of about
6200 * 47 * 50 = $14.57m
That's not a bad deal for a big company like Google, considering the number of eyeballs they will capture. Lets say a user uses the free Wifi for 30 minutes on average. So, we are looking at about 12*10*20/(1/2) = 4800 users per airport, per day. That works out to over 11m users in the 47 airports over the 50 day holiday period. Even if we assume that most people make round trips and therefore use the Wifi connection 2 times, Google can still reach about 5.5 million unique users! No too bad for the $15 million spent.
And I haven't even started counting the goodwill ROI bonus for playing Santa during holiday season! Nifty nifty marketing.
Free service is probably going to bring a torrent of airport Wifi users online - probably many more than the current number of (paying) users. Given that Wifi Internet channel space is a shared resource, it will be interesting to see how airport Wifi scales with the up-tick in usage. I just hope that the service doesn't deteriorate so much that the sponsoring companys' well-meaning message is lost to disgruntled users. And I do hope that engineers running these Wifi access points have done the networking provisioning Math beforehand.
Now the economics. The sponsoring company (Google) is probably going to pay a lot less than the retail price of airport Wifi connectivity. Why? Because the sheer volume of users will be much higher than when users have to pay individually. I think that the payment will include a fixed component depending on the number of access points participating in the service, and a variable component depending on the number of users accessing the service.
Lets assume that an average airport has about 20 accessible Wifi access points. Each access point can support (with any reasonable quality of service) about 10 concurrent users. If the airport is busy for, say, 12 hours in a day, and further say that we assume an average utilization of 50% of the total capacity of the access points, then we have (per day)
10 * 20 * 12 * 0.5 = 1200 hours of usage per day per airport.
I would assume that the sponsoring company (Google) would pay about $5000 per day as a fixed cost and then about $1 per hour usage. This brings the daily total cost per airport for the sponsoring company to $5000+$1200 = $6200.
So for 47 airports and 50 holiday season days, we are looking at a bill of about
6200 * 47 * 50 = $14.57m
That's not a bad deal for a big company like Google, considering the number of eyeballs they will capture. Lets say a user uses the free Wifi for 30 minutes on average. So, we are looking at about 12*10*20/(1/2) = 4800 users per airport, per day. That works out to over 11m users in the 47 airports over the 50 day holiday period. Even if we assume that most people make round trips and therefore use the Wifi connection 2 times, Google can still reach about 5.5 million unique users! No too bad for the $15 million spent.
And I haven't even started counting the goodwill ROI bonus for playing Santa during holiday season! Nifty nifty marketing.
Friday, November 6, 2009
Call for action! Powering down PCs

I've been playing with the idea of building a PC application that measures a computer's idle time. The idea is to gently convince users to suspend or power-down their PCs when they are not being utilised. I strongly believe that if PCs are optimally powered down, then many users could cut energy consumption (and hence also save on energy bills). Powering down battery-powered laptops will also increase the longevity of batteries and thereby decrease toxic battery waste in landfills.
As an example of where the possible savings may be, above is a pie chart showing my own PC usage over the past few working days. As you can see, there is ample scope to power down/suspend PCs when they are idle.
If you want to contribute time to this project (coding/web page/translation into other languages/spreading the word), feel free to contact me. If not, then do suspend your PC every time you are away for more than a few minutes :-).
Friday, October 30, 2009
Impact of International Domain Names
On the 40th birthday of the Internet last week, The Internet Corporation for Assigned Names and Numbers (ICANN) formally announced that there would now be domain name support for non-latin character URLs. This concept, called international domain names or IDNs, will allow URLs composed from letters of scripts of languages such as Korean, Chinese, Hebrew, Arabic and Hindi.
A little digging on Wikipedia about IDNs reveals that the underlying implementation is based on translating unicode names into DNS-compatible (ascii) URLs and visa versa in order to keep the current DNS system functional. This makes the system backward compatible with currently deployed name resolution infrastructure. In fact most of the translation to/from the non-Latin scripts will be done on the users' browsers.
But what does this mean for the fabric of DNS address space and the web?
Dilution of Latin namespace (?) Will we see some dilution in the value of address real estate? For example will http://www.doctor.com become less valuable because folks in Germany can now remember it instead as the more meaningful http://ärzt.com (Ärzt is German for medical doctor)? And what of those tens of thousands of domain names registered from different languages in Latin script (e.g. http://naukri.com in India. Naukri in Hindi means job).
The registration rush Initially, web content providers will scurry to buy up non-Latin names. But this will be more important for those content providers who do not have a global brand-name, or have a brand-name that defines their product or service. For a content provider like doctor.com, it will make sense to buy the synonyms of "doctor" in other languages, in addition to the spelling of "doctor" in the other languages. On the other hand, Microsoft.com will only buy up the spelling "Microsoft" in the languages/scripts becoming available through IDNs. At the very least, I forsee most businesses re-evaluating their namespace position on the web.
Security and phishing Completely unrelated characters in different scripts can look the same to the human eye. This means that users can be tricked into thinking that the address displayed in the address bar points to a legitimate page when in fact it points to a phishing page. It may be prudent for businesses to be aware of these security vulnerabilities of their URLs and perhaps register "similar looking" URLs in other languages/scripts proactively.
Impact on search engines Search engines are known to weigh in address name strings in their ranking algorithms. This may need some re-thinking. At the very least, some search engines may need to use automated translators to link up semantically similar web pages irrespective of how the address space links different copies of the same information in different languages/scripts.
A little digging on Wikipedia about IDNs reveals that the underlying implementation is based on translating unicode names into DNS-compatible (ascii) URLs and visa versa in order to keep the current DNS system functional. This makes the system backward compatible with currently deployed name resolution infrastructure. In fact most of the translation to/from the non-Latin scripts will be done on the users' browsers.
But what does this mean for the fabric of DNS address space and the web?
Dilution of Latin namespace (?) Will we see some dilution in the value of address real estate? For example will http://www.doctor.com become less valuable because folks in Germany can now remember it instead as the more meaningful http://ärzt.com (Ärzt is German for medical doctor)? And what of those tens of thousands of domain names registered from different languages in Latin script (e.g. http://naukri.com in India. Naukri in Hindi means job).
The registration rush Initially, web content providers will scurry to buy up non-Latin names. But this will be more important for those content providers who do not have a global brand-name, or have a brand-name that defines their product or service. For a content provider like doctor.com, it will make sense to buy the synonyms of "doctor" in other languages, in addition to the spelling of "doctor" in the other languages. On the other hand, Microsoft.com will only buy up the spelling "Microsoft" in the languages/scripts becoming available through IDNs. At the very least, I forsee most businesses re-evaluating their namespace position on the web.
Security and phishing Completely unrelated characters in different scripts can look the same to the human eye. This means that users can be tricked into thinking that the address displayed in the address bar points to a legitimate page when in fact it points to a phishing page. It may be prudent for businesses to be aware of these security vulnerabilities of their URLs and perhaps register "similar looking" URLs in other languages/scripts proactively.
Impact on search engines Search engines are known to weigh in address name strings in their ranking algorithms. This may need some re-thinking. At the very least, some search engines may need to use automated translators to link up semantically similar web pages irrespective of how the address space links different copies of the same information in different languages/scripts.
Saturday, July 25, 2009
Feel good sustainable energy video from RWE
This video from RWE, Germany's second largest electricity producer, is sweet. Too bad that in reality, Germany depends on polluting coal for much of its electricity.
Sunday, July 5, 2009
Pimped up Tom-toms...Netbooks+GPS: where is the value?
There is something funny going on in consumer electronics and personal computing nowadays. There is the tendency to combine different functionality into one all encompassing device. Management calls it convergence. Sales and marketing call it up-selling. The product guys call it how-to-keep-your-job-important. Consumers see it as a peculiar phenomena where devices become pricier even though they should be getting cheaper.
Here is a good example :
Smart phone = phone + camera + GPS + DVB-H TV receiver + memory stick + music player + ...
OK so I see some value in this smart phone convergence algebra. All the above services may be useful to a user and its great to carry them all in your pocket.
But it struck me as odd that Dell is planning to up-sell its Mini notebooks by charging users for extra GPS hardware. Apart from robotic aficionados who would want such GPS service on a netbook? The significant time it will take to power on a netbook and fire up the GPS would probably mean you've overshot a couple of highway exits before the GPS locks on and tells you where you are. And that will be after you've somehow placed the netbook over the dashboard for line-of-sight to GPS satellites, driving at 70mph. Netbooks with their limited battery lives would make for poor trekking-in-the-Rockies aids (and why would someone carry a netbook instead of a small portable tom tom up the trail anyway)?.
But the guys at Dell must have thought of all this. Even after you remove the management, sales, and product-team views on such matters, there must be someone who tried to write up credible use-cases. What is the killer-app use-case?
In my opinion, there is a very significant business-opportunity here. Dell wants to know where you are, in order to introduce location-based services (e.g. locality-aware advertising) in return for GPS map services. If you think about it, operators have an advantage over other IT vendors because they know (through cellular triangulation) where a user is. Hardware and software vendors would also want a piece of this action because of the significant scope for location-based advertising. GPS gives them that chance (and more accurate location information). Dell could know, through its GPS/map services, that its 13:00 on a Wednesday afternoon and I am sitting in a downtown Berlin park about 3 minutes walking distance from a restaurant serving schweine haxe and Berliner pilsner. I bet I'd take the bait of a 10% coupon to get there! And Dell would get a piece of the pork too.
Here is a good example :
Smart phone = phone + camera + GPS + DVB-H TV receiver + memory stick + music player + ...
OK so I see some value in this smart phone convergence algebra. All the above services may be useful to a user and its great to carry them all in your pocket.
But it struck me as odd that Dell is planning to up-sell its Mini notebooks by charging users for extra GPS hardware. Apart from robotic aficionados who would want such GPS service on a netbook? The significant time it will take to power on a netbook and fire up the GPS would probably mean you've overshot a couple of highway exits before the GPS locks on and tells you where you are. And that will be after you've somehow placed the netbook over the dashboard for line-of-sight to GPS satellites, driving at 70mph. Netbooks with their limited battery lives would make for poor trekking-in-the-Rockies aids (and why would someone carry a netbook instead of a small portable tom tom up the trail anyway)?.
But the guys at Dell must have thought of all this. Even after you remove the management, sales, and product-team views on such matters, there must be someone who tried to write up credible use-cases. What is the killer-app use-case?
In my opinion, there is a very significant business-opportunity here. Dell wants to know where you are, in order to introduce location-based services (e.g. locality-aware advertising) in return for GPS map services. If you think about it, operators have an advantage over other IT vendors because they know (through cellular triangulation) where a user is. Hardware and software vendors would also want a piece of this action because of the significant scope for location-based advertising. GPS gives them that chance (and more accurate location information). Dell could know, through its GPS/map services, that its 13:00 on a Wednesday afternoon and I am sitting in a downtown Berlin park about 3 minutes walking distance from a restaurant serving schweine haxe and Berliner pilsner. I bet I'd take the bait of a 10% coupon to get there! And Dell would get a piece of the pork too.
Subscribe to:
Posts (Atom)