SDN – Operational Simplification with Greater Profitability
on 08-29-201203:59 PM - last edited on 10-28-201311:00 PM by bcm1
In an effort to find innovative service offerings, we have found that service providers are exploring many alternatives which include how they expose their network assets for profit. In addition, once they do create a new service offering they are looking for ways to increase service velocity to keep ahead of the competition.
Service providers are taking a hard look at their current infrastructure and operations environment and finding that their current operations model and network architectures have some key limitations which are impacting their services from being deployed quickly.
- There is no standard way to change traffic flows to handle user mobility and flip the switch applications
- There are no software tools available that enable them to “dry run” new service options without impacting the production network
- The current back office model does not provide the flexibility needed to make dynamic network changes and create new service offerings.
- Any changes to the production network are difficult, slow, and risky
Although many strides have been taken in collapsing OSS (Operational Support Systems) systems in order to streamline service creation and service deployment, it still continues to be a complex and lengthy process. As you can see from the diagram below, there are multiple devices, multiple databases, and multiple protocols that have to be assimilated at the OSS layer to create an end-to-end service. In addition, with a Video on Demand Service like this example, there is also an unnecessary use of expensive router ports and switches that are involved in the service insertion which all impact the bottom line.
SDN solves both these problems by providing the network abstraction and the operational simplification that will not only accelerate service delivery but will do it more profitably. In some cases, the implementation of SDN with OpenFlow, and RESTful APIs will result in 50% savings under present methods.
This new back office model eliminates some of the complex processes with the use of new APIs like RESTful. These changes will result in service providers increasing the service velocity of these new services. In addition, they will also realize CapEx savings since OpenFlow can set up the paths for the flows, alleviating unnecessary routing and high end router connections.
If you want to hear more about this Cost Analysis Model and the savings result, be sure to join us on Tech Day to hear about our vision and innovation as well as joining the “Ask the Expert” session on SDN here in the Brocade Communities on September 12th and 13th