Despite having kicked off the O-RAN platform with its inhouse code, AT&T has been publicly cautious about its timelines for virtualizing its RAN, or supporting open platforms. In other parts of its network, however, it has been a trailblazer for open, disaggregated systems, particularly in migrating its IP core network to white box architectures.
Now it is extending the technology it has used in the IP core to the network edge, where it will adapt the software, but run it on the same underlying, non-proprietary hardware. Having the same white box platform from core to edge will reduce cost, support scalability and reduce procurement time and deployment or maintenance complexity.
AT&T’s CTO, Andre Fuetsch, said deployment of the disaggregated IP systems at the edge in the production network was “a really big development in the networking ecosystem”.
The operator is also seeking to drive adoption of its developments by other operators, and further scale for the market, by contributing code and specifications to open initiatives. Its distributed network operating system (dNOS) became the foundation of a Linux Foundation project called Danos, while AT&T has also contributed white box specs to multiple open networks initiatives. Its Distributed Disaggregated Chassis (DDC) model was adopted by the Facebook-led Open Compute Platform (OCP).
The multiyear effort to bring white box hardware and disaggregated, open software up to scratch for the primary IP network is starting to deliver commercial results for AT&T, which claims it is already driving down opex, and diversifying its supply chain to increase competition and innovation. For instance, one of the providers of cloud-native IP routing software for the DDC, to run on the Broadcom-based servers, is an Israeli new entrant called Drivenets.
DriveNets has innovated in its business model as well as its technology. Its customers buy white boxes directly from the hardware manufacturers at cost and then pay for DriveNets’ software licence separately, rather than on a per-port or per-box basis. This Network Cloud software runs on scalable physical clusters ranging from 4Tbps to 768Tbps, acting as a single router entity, so that scaling can be done rapidly.
The DDC runs on Broadcom’s Jericho2 system-on-chip (SoC), and is now supporting AT&T’s new generation IP MPLS core routing platform, providing the network operating system for that core use case and traffic engineering features for MPLS transport. The whole core routing hardware and software stack has been rewritten from scratch to support containers and microservices, which will handle the huge array of workloads for specific router functions.
The data plane functions run on white boxes and the control plane on x86 servers. AT&T has deployed 192 white boxes from Ufispace.
Now AT&T is extending its open networking model to the edge of its IP network, using the same white boxes from Taiwan’sUfiSpace on Jericho2 chips, but with software from Cisco rather than Drivenets. This highlights how Cisco, however reluctantly, has repurposed its network operating system – the IOS-XR – to run on third party hardware. It is initially being used to support peering with other ISPs’ networks but Fuetsch said AT&T is working with Cisco on developing other edge use cases such as “broadband, IP content, Ethernet, mobility and VPN services. We have started the journey to converge the disparate edge implementations we have today onto common software and hardware driving uniformity, simplification, and agility.”
This, he has made clear in the past, does not have to run entirely on Cisco software – other routing software may come into play to provide the best combination of performance and competition. Other new network software players, apart from Drivenets, which have appeared in AT&T trials or deployments include Arrcus, Pureport and Volta Networks.
Fuetsch said in a statement last week: “This model gives us options and flexibility in our supply chain and enables us to use best-in-breed products whether they come from established or disruptive suppliers. And this is well past lab experiments; the technologies and ecosystem have matured, and we are now into the production deployment phase.”
Cisco’s IOS-XR provides management and control functions for the IP edge. Some of the key features implemented to support the peering use case are BGP Flowspec, unicast Reverse Path Forwarding (uRPF), and port mirroring. Together, these enable granular security monitoring, and mitigation actions for threats such as directed denial of service (DDoS) attacks.
AT&T has deployed Broadcom’s new Jericho2 DDC design, which has been accepted by the OCP. The UfiSpace portfolio consists of three elements – a 10×400 GigE Line card based on the Jericho2 packet forwarding engine; a 10x400G line card system, also based on Jericho2; and a 48x400G fabric system based on Broadcom’s Ramon chipset. Those building blocks are deployed in a modular way depending on individual site requirements, to support routers with capacity from 4Tbps to 192Tbps.
In its switching network, which has also been migrating to white boxes, AT&T has been a major supporter of programmable switch pioneer Barefoot Networks, alongside Broadcom, but the future of that relationship is less clear now Barefoot bas been acquired by Intel.