 to telco capabilities. These requirements align with the NGN service stratum requirements. So, the SDP can be used for the NGN service platform. The SDP would require some architecture to satisfy these requirements, and also promote its structure for the NGN service platform architecture. Currently, the SDP has no standardized architecture. However, diverse archi- tectural interpretations exist. These interpretations are influenced by standards and technologies defined for the telco and IT-based enterprise networks. Also, many of these interpretations are based on vendor-specific solutions. Some vendor-driven architectures focus on satisfying specific SDP requirements, such as converged billing, content delivery, or service creation. A general SDP architecture is proposed in [2]. We use this general SDP archi- tecture but add detail that includes converged networks, interfaces, and a distribu- tion plane. The more detailed SDP architecture is shown in Figure 2.2. The architecture also shows standard-based technology mappings to its interfaces. For example, existing standards implement vertical interfaces but standards for hori- zontal interfaces are lacking. The SDP architecture identifies various distributed service platforms that con- stitute a SDP. These platforms abstract and simplify telco resources and capabilities as service enablers. These platforms and their enablers are Network Abstraction Platform houses network service enablers that provide a common point of access to heterogenous network resources and capabilities. Content Delivery Platform houses content service enablers that provide and deliver content to customers. We regard content as a network resource, which is either provided by the telco or external providers. Management Platforms contains management service enablers that abstract telco OSS/BSS functionality. Service Execution Platform contains telco applications that provide telco services to customers. These services include voice, data, or multimedia-based Service Delivery Platform for th