Your browser is not supported. Please update it.

20 September 2016

Orange boost AT&T’s MANO power play with ECOMP tests

AT&T has scored its first major success in its bid to establish ECOMP, its software-defined network (SDN) platform, as a de facto standard among mobile operators. Orange is testing the platform, building on existing partnerships with AT&T in open source technologies for SDN and NFV (network functions virtualization).

There is a real danger of fragmentation in the critical area of orchestration for virtual network functions (VNFs) in an SDN environment. AT&T is taking a leaf out of Google’s book by placing its inhouse technologies into open source, which could spark wide-scale adoption and give it an important role at the heart of a de facto standard ecosystem.

In SDN and also in 5G, AT&T aims to rally other MNOs to its flag in accelerating official standards processes and, where there are gaps in those, seeking to fill them with de facto specifications. It has been critical of Verizon for pursuing a semi-proprietary route to speed up its own 5G and SDN roll-out, though AT&T certainly isn’t alone in trying to drive standards for NFV/SDN management and orchestration (MANO). China Mobile’s OPEN-O and Telefonica’s OpenMANO are now the basis of rival industry alliance efforts in this area – OPEN-O is under the auspices of the Linux Foundation and closely allied to OpenStack; while ETSI’s OSM (Open Source MANO) group is basing its platform on Telefonica’s project, as well as the Rift.io orchestrator and Canonical’s Juju Charms.

In this confused situation, it is important for AT&T to build up support quickly. It initially opened the kimono on ECOMP (Enhanced Control, Orchestration, Management and Policy) back in March, when it published a white paper, and John Donovan, head of technology and operations, said then that open source would follow if there was sufficient interest.

Many saw this as AT&T’s attempt to be the organization which provides a common MANO blueprint and unites warring factions in carrier SDN/NFV – that could bring it untold influence over the way these critical technologies develop in the 5G era, akin to the power achieved by carriers like NTT Docomo who contributed to fundamental 2G and 3G physical network standards. But whereas those processes still operate in standards bodies and patent pools, the software-driven world will increasingly be about open source. Two months ago, AT&T confirmed that it had migrated the ECOMP code to the Linux Foundation.

In July, Orange agreed to some open source collaborations with AT&T, which have now flowered into a full testing program for ECOMP. It will be evaluating the promises that this MANO platform will allow it to create and control new services quickly, and scale them up massively as required.

This fits well with Orange’s wish to lead the field in flexible networks that can support on-demand services and, eventually, network slicing. At Mobile World Congress earlier this year, it said it had stopped promoting NFV and SDN on the basis of cost reduction and was focusing on new revenue potential enabled by flexible on-demand service delivery.

In the short term, it is working on a virtualized content delivery network (CDN) which could be activated automatically during times of high demand in certain locations to provide temporary capacity increase without provisioning the whole physical network for peak periods. Other use cases involve very granular slicing, of a kind which is unlikely to be practical until supported by some of the technologies evolving for 5G – these will be particularly important to support the wildly diverse behaviors and requirements of different IoT services running on the same network.

AT&T and Orange are among the operators trialling on-demand services for enterprise customers, which could also be extended to MVNOs and service providers in future, allowing organizations to use network capacity and services dynamically as they need them, and pay for what they use rather than signing rigid contracts.

Orange is been demonstrating such ideas under its EasyConnect brand, allowing enterprise customers to set up and manage various services via a self-care portal. This could enable operators to penetrate the world of large industrial private networks, with Orange saying: “Today they use proprietary systems but in future we could build dedicated services that use 4G and later 5G. This is one example of a use case that justifies virtualization.”

ECOMP could be a key enabler of the vision, and the new economics Orange is pursuing. Alain Maloberti, SVP of Orange Labs Network, said in a statement: “We jointly believe that a platform like ECOMP needs a strong and dynamic open source community to drive industry adoption, and we will work with AT&T to create a community to develop a reference software platform for automated network orchestration and management. We plan to start experiments with ECOMP firstly in a lab environment, to be followed by a field trial as part of our On-Demand Networks program.”

Chris Rice, SVP of Domain 2.0 architecture and design at AT&T, said: “ECOMP is a stake in the ground. It’s a declaration that networks of the future will be software-centric, that they’ll be faster, more responsive to customer needs, and more efficient.”

AT&T says it expects more operators to test and adopt ECOMP. In a blog post, Donovan described ECOMP as “one of the most challenging, complex and sophisticated software projects in AT&T’s history …. which provides automation of many service delivery, service assurance, performance management, fault management and SDN tasks.” It is designed to work with OpenStack, but can be adapted for other cloud and compute environments. “ECOMP is the engine that powers our software-centric network,” he added.

It also defines an operational roadmap to get to virtualization. This is an urgent requirement for the carrier itself, with its stated goal of virtualizing 75% of its network functions by 2020, and it will also provide useful guidelines for other, less aggressive operators, increasing the confidence to take the NFV plunge. It has been praised for defining terms clearly and being rigorous in dividing tasks between different areas of the network – the MANO is used only to manage VNFs, while infrastructure management takes place at the infrastructure level and there is a master service orchestrator when an end-to-end view is needed.

ECOMP has two frameworks, for design time and for runtime execution. Their overriding aims are to create a single architecture driven by policy and metadata, which enables the following basic approaches, all critical to Domain 2.0’s commercial and operational objectives:

  • Support a wide range of best-in-class components from many sources
    • Developing common capabilities once and reuse them many times
    • Support a wide variety of AT&T services using the same core capabilities
    • Scale and shrink the network in response to demand or change, in an ‘elastic’ way.