COTS hardware has been around for more than a decade. What is keeping equipment makers from deploying these solutions?
A suitable COTS architecture has only been available for two years. Other COTS architectures like Compact PCI were basically enterprise technology. So COTS suitable for core telecom
applications that can support five nines did not exist until ATCA availability. And ATCA availability goes back a couple of years.
I do see ATCA growing to be a multi-billion dollar business, but, as with all things in telecom, it will take time. The biggest complexity has not been about ATCA itself. It is about porting applications over to ATCA and, in particular, making a move to Linux. So moving to ATCA hardware is quite easy to do, but a lot of legacy applications simultaneously moving to ATCA are also moving from proprietary, 20-year–old, home-grown OSes to Linux.
One of the biggest motivations for using COTS hardware is the time-to-market factor. How far have vendors been able to achieve that in practice?
We have customers, who, using ATCA, have brought applications to market in under 12 months versus classic 24-to-36 month development period. We have a customer in Asia that chose our ATCA platform in Spring 2007 and, before the end of 2007, had live service up and running for a wireless application.
Can you perhaps name some of the application categorises that are being enabled by COTS hardware such as ATCA? How would you generalise the type of applications being ported over to ATCA platform?
ATCA will be the hardware of choice for a wide spectrum of applications. Over the last few years we have seen particular strength in the wireless arena: media gateway, RNC, SBC, and IMS applications like media server. IPTV has also been a very good adopter of using ATCA. From the fixed network side, we are seeing elements like access consolidator and echo cancellation as prime candidates.