TEXT SIZE:

Deploying Sandvine in LTE Networks

Sandvine’s platform elements are flexible enough to give communications service providers (CSPs) many deployment options.

In an LTE network, the main difference between Sandvine deployment options is in what location the Policy Traffic Switch (PTS) intersects traffic; by extension, this determines what the PTS “sees” and will impact the use cases that are available to you.

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.

IntersectionAdvantagesDisadvantages
S1-U
  • See all subscriber traffic
  • eNodeB traffic is often encapsulated in its own tunnel, making it easier to count total Rx and Tx flow to each eNodeB
  • Core Offload use case
  • Need an interface per eNodeB termination
  • Traffic may be IPSEC encrypted
S5/S8
  • See all subscriber traffic in the GTP-U, including GTP-C for signaling (e.g., subscriber-to-IP mapping, TEID, location) and all roaming traffic
  • S11 would need to be tapped to get mobile subscriber eNodeB change notifications
S11
  • See “additional” location granularity (e.g., eNodeB, sector, updates)
  • No subscriber traffic on this interface
SGi
  • See all traffic routed in “North” of the gateway
  • No GTP-C for subscriber mapping
  • No S8 roaming traffic
  • Misses traffic that is local to the P-GW

Deployment considerations:

  • Since the PTS intersects all user traffic, many rich use cases based on complete traffic classification and policy management remain available; also, the Mobile Packet Core Offload use case is an option
  • eNodeB traffic is often encapsulated in its own tunnel, so the PTS is able to count total transmitted and received bytes per eNodeB
  • Intersecting at this location requires an interface per eNodeB termination
  • Traffic may be IPSEC encrypted

Deployment considerations:

  • In this location, the PTS can see all the traffic in the GTP-U, including GTP-C for signaling (e.g., subscriber-to-IP mapping, TEID, location) and all roaming traffic; seeing the roaming traffic brings more use cases into play
  • To get mobile subscriber eNodeB change notifications, S11 needs to be tapped

Deployment considerations:

  • Deploying here lets the PTS see extra details about location, including eNodeB, sector, and updates
  • There is no user traffic on this interface, so use cases are limited

Deployment considerations:

  • 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
  • No GTP-C is available for subscriber mapping
  • No S8 roaming traffic is visible

UPDATED : 2015-03-06 09:44:13