Tekelec Blog
Home > Policy Control > How to select a Next-Gen Policy server

How to select a Next-Gen Policy server

May 17th, 2012by admin under Policy Control

Policy management is moving to front-and-center stage as service providers manage  the mobile broadband traffic boom unleashed by the popularity of data-enabled smart  devices and applications.  Most early policy deployments have focused on congestion  control and fair data usage as a way to optimize network resources. However, mounting  network costs and revenue objectives are driving the adoption of a broader set of  policy use cases. These use cases are focused on personalization and adding value to cloud, over-the-top (OTT), and machine-to-machine (M2M) services, as well as a more sophisticated approach to managing network resources.

Given the strategic and complex role policy is taking in the network, service providers need to factor in several critical criteria when selecting a policy server. Delivering increasingly innovative services and managing network resources requires a robust policy infrastructure that:

•  Interoperates with a broad array of policy enforcement points and charging systems that support standardized and non-standardized interfaces;

• Enables a broad array of use cases to monetize and manage mobile data growth across multiple access networks using a real-time subscriber profile repository (SPR);

• Provides easy-to-use policy creation and analytics tools to rapidly create, deploy, analyze, and evolve services and adapt to subscriber behavior;

• Has proven scalability and reliability to meet the demands of escalating data and signaling traffic, new service models, and increasing device and application data usage in the world’s largest networks ; and,

• Is part of a new Diameter-based, signaling architecture.

For additional information, download this free whitepaper: Why Tekelec for Policy: Key Considerations in Selecting a Next-Generation Policy Server.

No related posts.

  1. No comments yet.
  1. No trackbacks yet.
<% Response.Write("" & vbcrlf) %>