Pain Points of Deploying NFV

July 24, 2015

whiteford_smallNFV is clearly revolutionizing the Telecom market and every day more and more Mobile Network Operators are sitting up and taking notice of its benefits. Although some might say that the technology is in its early stages, NFV has quickly moved from Proof of Concept, to field deployments carrying traffic for some of the world’s largest network operators, such as AT&T who named Affirmed Networks to their Domain 2.0 Program in March 2014.

When operators transition to a virtualized architecture, they likely need to undergo a restructuring of internal operations. Since the solution is more software centric, traditional ways of working with blades, boxes and replacing cards would no longer be valid. It calls for operators to adopt a software centric approach with a growth mindset.

As John Donovan, Senior Executive, VP – AT& T mentioned during the ONS seminar this year,

“We had to create a new eco system. Before our industry was built around the specified, standardized implement approach that’s too slow and cumbersome”

Operational models become leaner, reducing Opex. Open source software can become an important component of the architecture and there is an opportunity for new skills to be developed.

Operators would also have to start thinking about services and scalability from a software standpoint. In any case the benefits of adopting NFV outweigh the pain points. Every year that the MNO delays the move, it costs them millions of dollars in CAPEX and OPEX. It does not make sense to stay with legacy systems.

Affirmed’s CEO, Hassan Ahmed elaborates on the pain points of deploying NFV. Watch the full video below.

 
Do you think that there are other pain points than the ones mentioned in the article? Join the conversation on our LinkedIn page or on our Twitter Feed (@AffirmedNetwork)