SDP – Case Examples

The SDP concept is these days enjoying the most success in the area of mobile content and messaging services. Nearly every mobile operator has implemented a SDP including a Content Management System, a rendering solution, and a set of connectors to SMS, MMS, WAP and charging capabilities.

Only a few operators have successful SDP deployments in the area of voice value added services. Core voice services are more difficult to create and they demand higher performance and reliability requirements from the SDP than mobile services. The early adopters of voice enabled SDPs face problems with finding 3^rd party application developers who could create revenue-generating services on their SDPs. The operator requires partners who can guarantee the quality of the developments and delivery as well as long-term maintenance of such services rather than garage companies. Continuously more applications are created and the concept of SDP is evolving to the benefit of the operator.  

Recent trials and deployments have shown that SDP implementations can match the challenging reliability and performance requirements. As technology performance is no longer an issue operator’s focus now on the commercial aspects of the SDP investments. Crucial for the success of the SDP architecture is a positive business case also in terms of competitive pricing compared with the legacy stove-pipe service platforms.

The NGN transformation process in Operators networks is ongoing. The SDP concept provides a chance to consolidate the service silos and to manage and execute multiple services on a single platform. Beside new service potentials to be leveraged by service orchestration and feature interaction scenarios the end of life of legacy systems is a major diver for platform modernization.

SDP – Guidelines to the Deployment

An SDP implementation should focus on a clear set of applications that can generate a solid business case. This could be also a well established service running on one or more stove pipes. The definition of architectural frame conditions enables an incremental, evolutionary approach for the SDP deployment. It does not harm the SDP concept if initially only a few services are deployed. Gradual extension of the SDP with new features, components and enabler as they become necessary is a valid strategy to exactly meet the requirements for either service consolidation of the existing stove-pipe platforms or service extension like identity management. Beside the functional and performance aspects it is very important to have a clear view on service management, security and service related business processes.

Next page