Your browser is not supported. Please update it.

21 February 2013

Big vendors ensure SDN remains closely tied to their routers

So it’s here again, Mobile World Congress, when the heavy-hitting cellcos very publicly lay down their demands for their vendors, and suppliers large and small leap to the challenge, while outlining the key directions for future platforms. The more that January’s Consumer Electronics Show focuses on mobile devices, the more MWC emphasizes the network (in its broadest sense, from infrastructure to software to back end systems). There will be big splashes by HTC (see separate item), Samsung and others, but the lack of Apple, BlackBerry or even (probably) a Galaxy S4 mean the Barcelona event will not really represent the handset industry. By contrast, any firm whose business is focused on helping operators cope with those handsets profitably will be vying for attention in Spain. Naturally, the agenda will largely be set by the major carriers and the big seven network providers, and in the run-up to the show this year, Ericsson has been particularly vocal, throwing aside its recent caution about new trends, and in effect proclaiming that this is the right time to talk about HetNet, LTE-Advanced and other nascent approaches. Last week we looked at the big vendors’ stance on small cells and network optimization, and no doubt there will be more on those themes once MWC kicks off. This week, we focus on two more major topics of discussion among the big vendors ‘ software defined networking (SDN) and cloud services.

The interest in software defined networking (SDN) among mobile operators is breeding a high level of hype, and the usual exaggerated expectations, but while the technologies may not be entirely in place, there is clear interest in a way to allocate resources flexibly and deliver many types of data – at different levels of quality, to many kinds of device – all in a dynamic way that squeezes the most out of the network. That is the dream, and this is becoming relevant to mobile operators as their IP data packets multiply by the minute.

However, while the major vendors are embracing SDN, they need to do this in a way that enhances their businesses. The logical extension of SDN thinking is to commoditize the hardware completely, but the large OEMs are currently managing to argue that this approach requires greater investment in their upgraded routers. Network functions will indeed be virtualized, and implemented in software rather than on appliances, but they will need router hardware optimized for the cellco, argue Ericsson and others. And moreover, the suppliers will place their own cloud platforms at the heart of carrier SDN.

This approach will be resisted by purists, and by would-be disruptors of the hardware status quo ‘ for instance, start-up Connectem virtualizes an entire packet core on a commodity x86 box, bypassing not just the specialized one-function boxes of current cores, but even the router. But for now, the vendor’s arguments are carrying significant weight in a cellco community which is interested in SDN, but nervous of such a major change to its thinking.

For most early movers, the router is, for now, key to carrier SDN and of course Cisco, Alcatel-Lucent and other network equipment makers push this approach, deploying the functions currently handled by dedicated appliances on routers as software. In future, the router could be commoditized and/or the functions move to x86 servers, but for now there is a significant opportunity for vendors ‘ especially those facing intense squeeze on base station hardware ‘ to grow their router business.

Ericsson is busily adding functionality to its Smart Services Router (SSR) range, a highlight of its recent quarter (it gained 19 new SSR deals in the period, doubling its total to 39). It even announced its first specific SDN product, saying it will add an OpenFlow 1.3 controller to the SSR 8000 router in the fourth quarter of 2013.

It not only aims to boost its mobile operators’ need for this infrastructure, but also to target wireline and cloud providers. And like rivals such as Huawei, ALU and Cisco, the cloud lies at the heart of its telco SDN strategy, with all the functions of the network ‘ not just the base station processing, as in Cloud-RAN ‘ migrating to virtualized and hosted server platforms.

This was seen in pre-MWC announcements by Ericsson and also Huawei, which laid out a full roadmap for its SoftCom SDN platform, which it has been developing for several years. This echoed the common principles of telco SDN, setting out open, streamlined architectures for communications, which separate the control and data planes and virtualize all the elements of the IP network, running them as applications on standard x86 or router hardware.

As at Ericsson, there was heavy focus on hosting the OSS/BSS systems on the telco’s cloud servers, delivering everything ‘as a service’, and with those hosted facilities distributed throughout the network.

Huawei expects to have commercial trials of SoftCom next year and full deployments in 2015, although much of its roadmap is firmly at the R&D stage still. Here there is particular emphasis on supporting NFV (Network Functions Virtualization), the ETSI-backed platform that adapts many SDN concepts specifically for telcos. Huawei says it is building NFV support for key elements of the mobile evolved packet core as well as for IMS and session border controllers. Here, too, it echoes its greatest rival in wireless ‘ Ericsson has been a major force in insisting that carriers need a specific implementation of SDN and has been active in the ongoing standards activity in that area, including NFV.

Critics complain that efforts such as NFV are smokescreens for the big OEMs to maintain their control over key platforms, and to slow down the shift of network functions towards commodity hardware rather than their expensive routers. But Ericsson retorts: ‘Using current data center SDN switching and controller technology is not sufficient in a real time telecom environment. A carrier-grade, virtualized, wide area network infrastructure that supports telecom services as well as large scale OSS and BSS is also required. Service Provider SDN means adding control to all domains of the telecom network. It links control of the cloud to the control of the network. Service Provider SDN integrates network control and orchestration, cloud management and service exposure.’

Yet Don Clarke – head of network evolution innovation at British Telecom and head of the ETSI NFV technical group – ran a recent study to investigate the potential of using commodity equipment for network services and believes this approach is already viable in real world networks, and can even bring some advantages. ‘The idea is to take a network appliance and run it as software on servers, storage and switches. Of course, it’s easier to deploy software images than it is to deploy hard boxes, but you can also apply resilience concepts that do not even exist in hardware, as well as it making testing and service assurance easier,’ he said.

This is the key to what promises to be the most important clash between the top network vendors, in terms of the strategic hold they can assert over their mobile customers for the second half of the decade. Supporting SDN while ensuring they retain control of the underlying infrastructure, and putting themselves at the heart of the related move towards hosted cloud platforms, will be critical.

Ericsson plans to unveil a full cloud platform at MWC, running on its SSR and its blade servers. In this respect, it is well behind ALU, which unveiled its own CloudBand offering in late 2011, running on its 7750 Service Routers. This harnesses algorithms developed at ALU’s Bell Labs unit, which can analyze a range of conditions – such as server load and network congestion ‘ as well as user requirements, to obtain the best settings for a given application at any given time. The idea is that operators should be able to use a single cloud platform to service consumers, corporate customers and third party service providers, and support services like voice and video without dedicated hardware, all in the most flexible way to maximize network efficiency. CloudBand has two elements – the CloudBand Management System, which coordinates and optimizes services between the network and the cloud; and the CloudBand Node, which provides the computing, storage and networking hardware and associated software.

Huawei picked up many of the themes this week. ‘The SoftCom strategy is all about helping the telco service providers to transform within the new digital economy,’ said Sanqi Li, CTO of the carrier division. ‘In the next 10 years, more changes will happen than in the last 100 years and the carrier is the foundation. The challenge is for the carrier to embrace this transformation.’

There are four elements to SoftCom, which Huawei rather unfortunately labels ‘cloudilization’. The first is at hardware level, deploying functions on standard routers. The second is at network level, consolidating the traffic tasks into one plane. Third is to replace the usual infrastructure with cloud-based systems. And fourth is to adopt an internet oriented operation, rather than the traditional telecoms view, in order to simplify infrastructure and processes, and reduce costs.

‘Existing network infrastructure is closed and protocol centric,’ said Li. ‘Software is embedded into the network device and when that device is added into the network, it can be there for 10, 15, even 20 years. It is complicated, it is controlling … the traditional service model can no longer sustain this. The end objective is to move the other way, from closed networks to open systems. The bottom line is to bring cloud business technology to telecoms and to take SDN to them as well.’

Meanwhile, Ericsson has developed a Cloud Execution Environment, based on OpenStack and KVM hypervisors, plus its own Cloud Manager OSS tools. It says its system will distribute and orchestrate cloud capabilities horizontally across the network, enabling new vertical exposure opportunities. ‘Cloud services need to be distributed and networks – including computing and storage capabilities – need to be elastic on an end-to-end basis. This combination will bring a new set of capabilities that doesn’t exist today,’ said the company. The new environment allows virtualized and non-virtualized applications (from Ericsson or third parties) to execute side-by-side ‘ important to cellcos, few of which will want a ‘big bang’ migration to SDN or the cloud.

One of the big debates at MWC is sure to be how long the vendors can convince cellcos that off-the-shelf x86 hardware is not suited to carrier SDN/cloud, and that their own routers and blades remain critical. Some companies will see the chance to disrupt the power of Cisco, Juniper, ALU and others by commoditizing or marginalizing the router. Stu Bailey, CTO of SDN provider Infoblox, recently told the GigaOM blog that the emphasis on networking hardware would be shortlived. Cloud and mobile networks are becoming hugely complicated mainly because of the rising number and variety of devices at the edge, from smartphones to sensors, he argued, saying: ‘How quickly will a large healthcare org realize that the network is not a collection of routers and switches, but is instead those things connected to the network? How they interact and how they are secured is responsible for the business. With that awareness they need SDN economics and OpenFlow will hasten that.’

OpenFlow, the open source controller, is only one way to achieve SDN, but it is gaining significant support in the data center world and some impact in mobile ‘ there is even a mobile specific version called OpenRoads or OpenFlow Wireless, which has been trialled in particular by NEC. OpenFlow is in pole position to become the standard switching specification for carrier SDN, while the cloud OS is likely to be based on OpenStack, and a network OS is still to be decided on. Some elements remain in proprietary hands, or unserved by standards, however (Huawei is building its own centralized routing control algorithm for instance).

The OpenFlow Controller manages network resources in a programmable manner, so carriers can set priorities and rules, and it controls all kinds of elements – routers, hubs, switches and so on ‘ as a unified and virtualized ‘slice’. The ability to manage these slices of resources from end-to-end is why many analysts believe OpenFlow will finally persuade carriers to embrace IMS (IP Multimedia Subsystem) wholeheartedly, as the new technology can be included in the IMS fabric, improving flexibility, quality of service and cost-effectiveness when carriers are delivering a wide range of IP services to different networks and devices.

However, the logical by-product of OpenFlow and full software implementation is to commoditize the hardware completely, clearly a result Cisco and others will battle against with their halfway house approach to SDN, involving virtualization but clinging to special hardware. And there is some justice on their side ‘ OpenFlow is far from being commercially deployable on a large scale without significant proprietary tweaking. To gain real mass, it needs standard merchant silicon that can support its fastest iterations ‘ most early providers of OpenFlow switches are actually using specialized chips from firms like EZchip, which creates another layer of lock-in.

Other companies try to take their eyes off the network layer and come from the service layer downwards, like F5, which recently bought SDN start-up LineRate Systems. F5’s differentiation in the IP world is to push an application control plane, where the network is programmed at the service rather than the router layer. “You sit above the network fabric and add a layer of application-fluent services,’ says the firm, envisaging the day when network services are closely coupled with applications, and have to move with the virtual machine that’s running the application.