Sandvine’s platform elements are flexible enough to give communications service providers (CSPs) many deployment options fitting their network architecture.
This flexibility is enabled by the deployment versatility of Sandvine platform element the Policy Traffic Switch (PTS), which intersects data traffic. The location of the PTS in the network determines what the PTS can see and how it can impact use cases.
By understanding the trade-offs, CSPs are able to make informed decisions about the best deployment option. The table and expandable sections below show the options available and will help you choose the deployment model that works for you.
See all subscriber traffic in the GTP-U, including GTP-C for signaling (subscriber to IP mapping, TEID, location), and all roaming traffic
A must to deploy location to count and apply policy on the inbound roaming traffic
Decentralized deployment, less traffic, suitable for use on the PTS 22000 and Virtual Platforms (Virtual Packet Core)
Perform subscriber mapping using the GTP-C transparently, thus saving the overhead of integrating with the backend servers
Allow counting and applying policy on relevant to subscribers-to-subscribers and subscribers-to-gateway more effectively
Enable insertion of VAS (Caching, Video Optimization, and URL filtering) at this point in the network by stripping/reapplying tunnel/encapsulation headers
Add complexity to manage fragmented tunneled traffic
See all traffic routed “north” of the Gateway
Enable the VAS deployment
Automatic subscribers IP prefixes learning using the BGP Routing protocol
More centralized enables converged deployments and the use of larger scale PTS 32000
Flexibility in segregating deployment based on IP traffic. For example, IPv4 and IPv6
Support CGN deployments, VLAN, and QinQ using the Session Qualifiers
In this location, the PTS will see all traffic routed in above the gateway, but will not see traffic that is routed locally below the P-GW