{"id":1053,"date":"2016-02-08T18:18:43","date_gmt":"2016-02-08T15:18:43","guid":{"rendered":"https:\/\/telcocloudbridge.com\/?p=1053"},"modified":"2016-02-08T18:18:43","modified_gmt":"2016-02-08T15:18:43","slug":"sdn-project-onos-challenges-optical-vendors-business-model","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/?p=1053","title":{"rendered":"SDN Project ONOS Challenges Optical vendors’ Business Model"},"content":{"rendered":"

If you are a traditional optical\/DWDM vendor<\/a>, then be prepared for a shock!<\/p>\n

Because some of you believe that Optical\/DWDM box can be the most closed platform in networking.<\/p>\n

After all, an optical signal is analog (not digital) therefore it is difficult to\u00a0understand\u00a0it.<\/p>\n

And since vendors use proprietary enhancements to carry signals; therefore, it is very difficult to have an open interface to manage them.<\/p>\n

So, customers are obliged to buy from you everything including the management system, the ROADMs (optical switch) and above all your cash cow- the transponders.<\/p>\n

However, you might be preparing for surprises sooner or later.<\/p>\n

As the industry has, already, started talking about the optical white box (Open optical switch configurable with open APIs).<\/p>\n

Therefore, in this blog, I discuss why the optical business model that revolves essentially around selling optical hardware could be at risk because of SDN and in particular, projects like ONOS<\/a>.<\/p>\n

And in the new scenario of open platforms, why it is essential for the optical vendors to look for other business models.<\/p>\n

But before that<\/p>\n

<\/h2>\n

What is ONOS?<\/b><\/h2>\n

ONOS stands for Open Network Operating System.<\/p>\n

According to ONOS<\/a> website:<\/p>\n

The Open Network Operating System (ONOS) is a software-defined networking (SDN) OS for service providers that has scalability, high availability, high performance and abstractions to make it easy to create apps and services.<\/i><\/p>\n

ONOS targets service providers. In that sense, it is different than the other well-known but earlier SDN controller Opendaylight. It is designed from day one with the carrier needs i.e.\u00a0 reliability, redundancy, and scalability. ONOS is still in its infancy but its development is supported by well-known operators and vendors.<\/p>\n

Before moving on to discuss how ONOS targets the business model of optical vendors, it is essential to understand the relevant use case of ONOS that is directly related to Optics<\/p>\n

<\/h2>\n

ONOS Use Case: Packet and Optics integration<\/b><\/h2>\n

One of the main use cases in ONOS is the integration of IP\/Packet and Optical domains. In today\u2019s networks, these two layers evolve independently with no relation to one another even though both form one transport core. This leads to the build-up of both IP and optical domains since the transport links are over provisioned.<\/p>\n

Additionally there are extra maintenance costs since two teams are needed to manage two separate networks.Not to forget the delays in service provisioning owing to the involvement of multiple teams.<\/p>\n

This results in high CAPEX and OPEX spending on acquiring and maintaining two networks.<\/p>\n

ONOS will address all these problems by combining both layers under one controller through standard southbound APIs.<\/p>\n

The controller intelligently optimizes resources and protection on both layers bringing down the usage of both layers ( this will slow down the expansion requirements) and with one team and one interface for provisioning, the\u00a0 time to provision new services will be much faster.<\/p>\n

Interesting, isn’t it?<\/p>\n

<\/h2>\n

So far, everything is good- So where is the issue?<\/b><\/h2>\n

Well, the direction of ONOS is great!<\/p>\n

But, there is a requirement for achieving the objective of the use cases such as Packet and Optical integration.<\/p>\n

And that is making optical switches open and programmable. Yes, the optical white box.<\/p>\n

The concept will become clear from the following two slides from a presentation<\/a>, which I found on the wikiONOS website. (Presentation name: Control of packet over optical networks)<\/p>\n

\"clip_image001\"<\/a><\/p>\n

\"clip_image002\"<\/a><\/p>\n

The first slide talks about open optical hardware. Which is programmable and acts like a White box. Such a box in future will be configurable by any third party supporting relevant open APIs.<\/p>\n

The second slide talks about the shift from traditional ROADM to an open ROADM with the ability for the ROADM to follow open commands like Match and action for ADD, DROP, and FORWARDING using OpenFlow.<\/p>\n

When ROADM becomes an open platform, a controller such as ONOS would be able to program it irrespective of which vendor is providing the box. And this would facilitate the Packet and Optical integration.<\/p>\n

<\/h2>\n

Where does this leave the optical industry?<\/b><\/h2>\n

Well, the concept is disruptive yet achievable, if vendors collaborate.<\/p>\n

let’s face it.<\/p>\n

The concept is still under trial phase. And it will take\u00a0 long time to have something in the production network when\u00a0 standards are finalized.<\/p>\n

But the work has already started.<\/p>\n

Many traditional optical vendors may not like the white box concept.<\/p>\n

But the truth is that there are already small companies emerging that offer some sort of open white box solutions for DWDM. Take a look at Calient<\/a>, Polatis<\/a>, Lumen<\/a>. More of such companies would emerge in future.<\/p>\n

The use case like this one leads us to question the future business model of the traditional DWDM vendors.<\/p>\n

<\/h2>\n

What is your Optical Business Model?<\/h2>\n

Is your business model strictly selling your own optical DWDM system with your own proprietary management system?<\/p>\n

Are you open to the idea of open APIs for managing your box?<\/p>\n

In my view, commoditization will hit the optical industry as it has any other networking business.<\/p>\n

It might take longer to happen given the analog nature of light and the very closed and proprietary nature of the current optical gear.<\/p>\n

Yet, the ball has already started rolling.<\/p>\n

In my personal opinion, this might lead to two business models in future.<\/p>\n

1. Open your box but play in the strict commodity market and compete on price.<\/p>\n

2. Change the business model and reduce dependency on the hardware. Move to the applications that run on top of the hardware. Bring a software story to your hardware gear.<\/p>\n

Some of the hardware players have already sensed the direction of the wind:<\/p>\n

The hard-core hardware vendor Ciena\u2019s acquisition of software player Cyan<\/a> and hardware centered ADVA\u2019s acquisition of overture<\/a> signal that these companies want to move to a more software-centric business model.<\/p>\n

Some are sticking to their guns, yet.<\/p>\n

Some are still defining on what would be the next right strategy.<\/p>\n

<\/h2>\n

What is your opinion?<\/b><\/h2>\n

How do you feel about the optical white box?<\/p>\n

Do you feel that it is a genuine need for operators to have a more open platform thus solving some pain points?<\/p>\n

As a vendor, what are the obstacles you see in implementing a more open optical platform?<\/p>\n

I would love to hear your opinion in the comments section below.<\/p>\n","protected":false},"excerpt":{"rendered":"

If you are a traditional optical\/DWDM vendor, then be prepared for a shock! Because some of you believe that Optical\/DWDM box can be the most closed platform in networking. After all, an optical signal is analog (not digital) therefore it is difficult to\u00a0understand\u00a0it. And since vendors use proprietary enhancements to carry signals; therefore, it is […]<\/p>\n","protected":false},"author":2,"featured_media":1832,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-1053","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sdn"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/1053","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1053"}],"version-history":[{"count":0,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/1053\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/media\/1832"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1053"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1053"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1053"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}