10.01.2017 Views

ANALYTICS

KPsW307SqrH

KPsW307SqrH

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Real-life deployment stories<br />

SK Telecom<br />

South Korea’s largest wireless carrier SK Telecom (SKT) is currently<br />

being defined by the mental software of its chief technology officer Dr.<br />

Alex Jinsung Choi, whose vision is for an all-IT telecoms<br />

infrastructure.<br />

All telecoms network functions will run on its cloud core in its software<br />

defined data centre. When complete, all components in the core<br />

networks in data centres and local network operation centres will be<br />

running as virtualised network functions in an OpenStack cloud<br />

infrastructure.<br />

As a first step SKT is virtualising its traditional telecoms network<br />

functions such as IP Multimedia Systems (IMS) and Evolved Packet<br />

Core (EPC) so they can be ramped up in much greater volumes when<br />

demand for, say, video services booms. These virtual network<br />

functions (VNFs) will be used for providing customer-specific,<br />

dedicated multi-tenant telecoms services with orchestrated service<br />

chaining. The VNFs will also be used to boost service quality and<br />

reliability with elastic VNF resource management and load balancing<br />

control.<br />

amount of capacity. If they could pay for just the capacity they<br />

used, CSPs could save on licensing costs and avoid the<br />

headaches associated with managing the various licensing<br />

models.<br />

The CSPs need an open ecosystem and the current scenario is<br />

still too fragmented, says Monteleone. A more realistic approach<br />

would focus on basic interoperability between entities from<br />

different vendors, such as VNFs and MANO systems, in order to<br />

orchestrate a wide catalogue of tools. You don’t have to<br />

standardise everything right away. It might be better to regularly<br />

consolidate on a continuous process of innovation and<br />

experimentation.<br />

“The initiatives taken around standardisation have helped<br />

significantly to advance the NFV architecture definition and identify<br />

NFV implementation and deployment challenges,” says Amol<br />

Phadke, global network virtualisation and transformation lead at<br />

Accenture.<br />

Market activity so far has shown vendors and service providers<br />

how to develop and deploy NFV. They should trust the evidence<br />

of their own success, rather than the guidance of standards<br />

committees, according to Phadke.<br />

“The pace of progress with some of these initiatives has been<br />

slow and has lagged real world deployments. The scope of some<br />

of these standardisation activities has also been limited in that<br />

they do not provide a complete NFV solution but rather only a<br />

piece of the puzzle,” says Phadke.<br />

Ultimately, NFV could be more successfully brought to market if<br />

there was less obsessiveness about unifying every last aspect of it<br />

and advancing all parties together, says Bell at OpenCloud. A<br />

more lightweight and less encompassing approach, led by AT&T<br />

in the OpenStack camp, would enable individual projects to<br />

advance faster. These advanced parties, that progress on a<br />

variety of fronts, could all be cross-referenced and catch up with<br />

each other at intervals, as happens in the IT industry. As it is, the<br />

pace of progress in the CSP sector is relatively slow.<br />

SKT’s network research and development centre has already<br />

succeeded in deploying parts of the operating IMS services as vIMS<br />

in its commercial operation environment with OpenStack and is<br />

currently operating them successfully. It also aims to commercialise<br />

more parts of the IMS services to vIMS and put them into production.<br />

The next target function for virtualisation is vEPC, says Choi.<br />

Telefónica<br />

The Spanish CSP group has invited Brocade, Intel and Red Hat into<br />

its NFV Reference Lab Framework in order to test and develop virtual<br />

network functions, as a means of upping its service orchestration for<br />

its 313 million accesses across 24 countries.<br />

Ease of use was the main benchmark in its tests. “In less than two<br />

hours, we deployed the Brocade 5600 vRouter from a memory stick<br />

and completed our performance tests in our NFV Reference Lab,”<br />

says Francisco-Javier Ramón, head of Telefónica's NFV Reference<br />

Lab. “These results are allowing us, as network operators, to<br />

aggressively change our perspective regarding what is possible with<br />

software-driven networking in order to accelerate the adoption and<br />

deployment of these revolutionary technologies.”<br />

AT&T<br />

The U.S. CSP claims it is well on its way to implementing a common<br />

infrastructure for all virtual network functions. By 2020, it plans to<br />

virtualise and control more than 75% of its network using a new<br />

software defined architecture to meet the growing demands of data<br />

and video hungry users.<br />

In the last eight years, data traffic on the AT&T network has increased<br />

100,000%, driven primarily by video. As demand expands at this rate<br />

the vertical scaling of traditional hardware models will be impossible,<br />

no matter how sophisticated and complex the routers and switches<br />

may be. Software definition of simple, standard hardware is the only<br />

way to meet the growth in demand for performance and efficiency<br />

while minimising costs.<br />

Half of AT&T’s networks are controlled by open-source SDN code,<br />

according to a statement by AT&T technology and operations vice<br />

president John Donovan. Millions of AT&T wireless subscribers are<br />

connected to virtualised network services with many relying on the<br />

AT&T Integrated Cloud (AIC), which was built using OpenStack.<br />

VANILLAPLUS MAGAZINE I SEPTEMBER / OCTOBER 2016<br />

51

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!