As Principal Analyst for Service Provider Infrastructure, David is responsible for tracking the evolution and key developments within the IP Services Infrastructure market. His coverage areas include Hosted Multimedia Application Servers, IP Multimedia Subsystems (IMS), Mobile Softswitching, Policy Control, Service Delivery Platforms (SDPs), Session Border Controls (SBCs) and Softswitches.
Deploying a VoLTE-capable network core has become much easier and faster with NFV.
However, some of today’s pre-integrated vVoLTE solutions may re-introduce the specter of vendor lock-in.
Like virtual customer premises equipment (vCPE), virtual voice over LTE (vVoLTE) is viewed by operators and vendors alike as one of the top NFV use cases slated for early implementation. In many ways, vVoLTE’s popularity has been the result of fortuitous timing. VoLTE depends on the deployment of the IP Multimedia Subsystem (IMS), which until now has been both a costly and protracted deployment undertaking for the carrier. However, NFV now offers infrastructure cost reduction by using shared common hardware and a faster, software-only implementation of IMS using virtual network functions (VNFs). Put these two together and you seem to have a ‘marriage made in heaven’ (that’s good). Continue reading “Virtual VoLTE: A ‘Marriage Made in Heaven’ or a ‘Double Whammy’?”→
‘Stateless operation’ is the result of taking all the state (or session) data out of an application and relocating it into some form of ‘shared data entity’ to enable easier VNF scaling, failover, upgrade and so on.
With at least three different approaches emerging, VNF data management may prove as much of a hindrance to NFV rollout as NFV MANO.
‘Cloud native’ is the new virtualization mantra, often used to highlight the characteristics of applications designed for the cloud from the start.
A host of smaller network vendors are already claiming to be ‘microservices-based,’ a key attribute of being ‘cloud native.’ Larger vendors need to be careful not to lag behind.
It could hardly have escaped anyone’s notice at the SDN World Congress in The Hague this October that ‘cloud native’ is the new mantra in describing virtualized network functions (VNFs). Hardly a discussion or presentation from either operator or vendor took place without mentioning the term at least once. Generally, the term ‘cloud native’ highlights the differences between simply converting physical network function-based software into VNFs and creating VNFs ‘designed for the cloud’ from the start. Continue reading “Microservices: How ‘Cloud Native’ Are Network Vendors Today?”→
AT&T’s decision to open source ECOMP and its selection of Amdocs as a partner illustrate that traditional standardization by cooperation behind closed doors is being superseded by public and open initiatives.
The number of operator-vendor-open source combinations for NFV MANO continues to increase. A shakeout is both inevitable and necessary to bring about multi-vendor VNF interoperability.