At the recent LTE Voice Summit and various social media communities, carriers are expressing interest in integrated STP and DRA functions. Vendors are offering different approaches, and not all are truly integrated.
For example, we believe that offering an STP function on one blade and the DRA function on a separate blade, while in the same chassis, does not equal integration. And some vendors are simply virtualizing these functions to run behind the hypervisor to achieve a semblance of integration in software.
Our approach delivers "one common architecture, with many virtualized network functions.” In this case, our TITAN platform provides both STP and DRA functions on the same software platform. This not only leverages provisioning done centrally in one location as a shared database, but it also distributes that database down to the edge of the network for maximum signaling efficiency. We believe it is more useful to have both functions on the same platform with a common shared database in order to easily support interworking between these two functions and dramatically reduce the signaling storm that happens in the network—and between many of the other signaling and routing functions resident in a carrier network today. This is useful in cases such as the MME/SGSN (S6a /S6d) to the HLR (MAP Gr) as per TS29.305.
We also virtualize these functions. But in our approach, TITAN is able to hold the data in memory and the service logic for either STP or DRA can be interworked without the need for external interactions.
Share your perspective on how best to integrate STP and DRA functions. Or request a demo via email@example.com.