Light Reading Mobile – Telecom News, Analysis, Events, and Research

Rumors  

Rumor: Google to Add SDN Smarts to Android

May 20, 2013 | Ray Le Maistre |
Here's a software-defined networking (SDN) story straight out of left field: Google, it seems, is planning to incorporate the OpenFlow protocol, which is currently being deployed in many initial SDN-enabled architectures, into a future version of the Android operating system (OS).

At first, the notion is hard to comprehend. But according to a senior Tier 1 telecom operator executive, who discussed his insight into Google's plans on condition of anonymity, this is on the Android roadmap and is part of Google's plan to extend the reach of its virtual data center all the way to the very edge of the network -- to the mobile device.

And that's a lot of devices: Google has just announced at its I/O developer conference that the Android OS has been activated more than 900 million times.

But why would Google do this? That's the big question. Google, it appears, would like each Android device to become a mini blade in its ever-expanding virtual global data center. In OpenFlow, it has possibly identified the protocol to manage that resource in the best possible way.

This isn't anything that's in the public domain, though. The Open Networking Foundation, which is promoting the use of OpenFlow and the concept of SDN, says it is not aware of such a development, and Google is indicating it is not aware of the Android/OpenFlow plan.

Network operators, though, are monitoring the development and trying to figure out how such a move might further relegate them to bit pipes and strengthen the hand of one of the major over-the-top (OTT) service providers.

Google is already very familiar with OpenFlow and how it can be used in a network management context, as it operates what is probably still the world's largest SDN architecture. (See Google: SDN Works for Us.)

— Ray Le Maistre, Editor-in-Chief, Light Reading



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Going Soft at MWC

SPONSORED BY
White Papers SPONSORED CONTENT
Featured
Circuit-Switch Fallback (CSFB)
A standard for delivering legacy voice and SMS services to LTE devices