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

News Analysis  

Ciena Pushes Ahead to 400G

March 01, 2012 | Craig Matsumoto |

Ciena Corp. is announcing its next 100Gbit/s optical processor on Thursday, readying itself for the 400Gbit/s generation.

The WaveLogic 3 chip promises to extend 100Gbit/s reach to 2,500 km without regeneration, through technologies including soft forward error correction (FEC).

The chip also uses a digital signal processor (DSP) on the transmit side. This opens the possibility to mess with 100Gbit/s wavelengths, squashing them into a space smaller than the usual 50GHz spacing, so that more wavelengths can fit on a fiber.

WaveLogic 3 also takes advantage of increased processing smarts. For example, it can be programmed to make tradeoffs -- improving latency by lightening up on FEC, and therefore giving up some reach.

Ciena expects to have customers running live traffic on WaveLogic 3 this year.

Why this matters
This means the 400Gbit/s generation is almost underway, although Ciena expects it to happen in a limited fashion and doesn't expect customer deployments until 2013.

The real importance is on the 100Gbit/s side, where longer reach and lower power are going to be key topics this year. Cisco already declared the ability to run 100Gbit/s wavelengths for 3,000 km without regeneration, as EANTC verified in its recent test of Cisco CloudVerse, and we'll probably hear plenty more about 100Gbit/s improvements during OFC/NFOEC next week.

A couple of other things to note: Ciena will continue using an in-house chip for its next 100Gbit/s generation, showing the power of vertical integration.

And with the transmit DSP, and the ability to squeeze more wavelengths together, it's setting up applications for flexible-grid reconfigurable optical add/drop multiplexers (ROADM)s in the 100Gbit/s generation. It's suspected that a flexible grid will be useful as the industry approaches 1Tbit/s.

Ciena put together this video to show the thing in action:

For more
Keep up with our coverage on the Light Reading OFC/NFOEC site.

— 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.
 
Related Content
White Papers SPONSORED CONTENT
Featured