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

News Analysis  

Alcatel-Lucent CTO States the Case for NFV

April 03, 2013 | Craig Matsumoto |
SANTA CLARA, Calif. -- The industry needs hardware virtualization, and while network functions virtualization (NFV) might not be the answer, it's a good start, Alcatel-Lucent's CTO said here yesterday.

Marcus Weldon was speaking as part of the launch of Nuage Networks, the AlcaLu spin-in focusing on software-defined networking (SDN). (See Alcatel-Lucent Spins Up Its SDN.)

The answer is certainly not ATCA, which is "the last attempt of the industry to standardize and has largely failed," Weldon said.

What's wrong with ATCA is that it's a box mentality, Weldon said. A particular function is scaled up by adding the exact card for that function, and when you run out of room in the box, you've got to install and configure another box.

What NFV promises is freedom from boxes, in a sense. You'd still need equipment, but a function could grow by being activated in as many instances as necessary. "That's the problem. We're running at box scaling rules and we have to get to Web scale," Weldon said.

NFV isn't necessarily going to save the world. In fact, Weldon took a couple of jabs at the group: "They're not going to standardize anything; they're just going to point to standards," he said. "They're united, but they're not sure what they're united around'

Fair enough. The NFV has only met a couple of times, just long enough to establish that they exist and determine how well the members get along. The group's next meeting is in three weeks in Santa Clara, at Huawei Technologies Co. Ltd.'s site, which added a touch of timeliness to Weldon's talk.

Virtualization is important because it's happening on the data-center side, and telecom, for now, can't possibly keep up, Weldon said.

He gave the example of WebRTC, open-source software that allows for real-time communications on the Web. Apps using WebRTC could scale up rapidly at peak times -- if everybody ran to grab a particular Web video promoted in a Super Bowl ad, for instance -- but on the telecom side, IMS wouldn't be able to respond in kind. IMS is still bound by telecom systems that can't be expanded so quickly.

NFV sometimes gets described as an attempt to bring cheaper hardware into telecom. But the real benefits are in scaling, not penny-pinching, Weldon said. By escaping that box paradigm and working on a virtualized basis, operators would be able to deploy functions more quickly, and scale them up and down at will, he added.

Of course, cost matters, too. NFV could result in some telecom equipment moving to virtual form running on general-purpose processors. But it wouldn't happen to everything, Weldon argued.

Anything coming in contact with the physical layer is probably not do-able on a general-purpose processor -- that would include coherent optics, the radio access network and DSL, Weldon said. He also argued that core routers won't virtualize, as the number of processors needed to replace a core-router ASIC would be just ridiculous.

Virtualization comes with risk, as Weldon mentioned repeatedly during his talk. Server virtualization is based on the assumption that server failures are no big deal; that's fingernails on a chalkboard to the telco five-nines mentality. Changes to OSSs might be required as well.

Then there's the telecom culture, Weldon said. Network operators would have to work hand-in-hand with IT, "and that's not a comfortable conversation or an easy one."

For more

— Craig Matsumoto, Managing Editor, 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