Archive for January, 2010

Don’t Invest In DPI Until Net Neutrality Has Been Resolved

Monday, January 25th, 2010 by Jon Linden

Sorry, there should be a question mark at the end of that heading, and the answer is No!  The fact is you need to invest in DPI now. I know I’m biased, but that’s why I possess hands-on knowledge and facts of what our customers do and why.

DPI does not equal P2P throttling and Net Neutrality infringement. P2P control originally presented itself as an opportunity for DPI with a quick ROI on a hair-on-fire issue where P2P filesharing rampaged at an exponential growth rate, which meant exponential cost. But today we’re in the second, or I would even argue the third generation of DPI, and both products, and the use of these products, have evolved and become much more sophisticated.

Today the most common request is visibility. Visibility of what traffic is traversing the network in order to detect changes early in user behavior to avoid surprises on the core business and business models. Today’s rapid increase in streaming video is both a threat and an opportunity to cable MSOs, whose core business is TV distribution.

This is a good illustration of why network traffic intelligence is so important. Today we don’t watch TV as we did before. We don’t watch in real-time since we have TiVo and subscribe to episodes as they are “released”. It’s just a small step to Hulu and the broadcasting companies’ Play services. Early detection of these phenomena gives the operator the ability to offer relevant packages, change pricing, and develop new services without being left far behind.

In all honesty, very few of our customers and prospects even consider limitation of competing over-the-top (OTT) services. Savvy end-users catch what they do, draw attention to it, and the operator is caught with their pants down. You don’t “get away with it”.

But knowledge is power. Based on proper network intelligence you can make proper decisions. For example reach out to emerging services and join them instead of trying to beat them, look at the value add of your paid-for services compared to free OTT services, see the impact on your network of new applications, and project the investments required to accommodate these new services.

You could actually go as far as to say that DPI is required to enable Net Neutrality. Transparency is a cornerstone in Net Neutrality and DPI offers the tools that verify that you are transparent, that you’re not preventing good service levels due to obsolete policies supporting an old reality.

We, Procera, have not seen an impact on our DPI business from Net Neutrality, and I think it’s due to the above. Operators understand this, have understood why DPI is necessary, how it’s used properly, and are able to discard the background noise of an infected discussion while listening to creative and reasonable input.

DPI + Policy Control = True

Monday, January 11th, 2010 by Jon Linden

The rumor is true, DPI and Policy Control are confirmed to be a couple and have been seen hand-in-hand even in public recently. Feelings are mutual and this is bound to last “until death do us part”.

The 3GPP framework rules! At least in the mobile space and it’s also making headway into fixed. That’s good. DPI has become a critical component in a service provider network, which requires DPI to interact with surrounding systems. On top of this complexity grows with tiered services, volume quotas, sponsored sites, and premium gaming and telecommuter services.

This is where the policy server, or PCRF (Policy Charging and Rules Function), comes in.  DPI is an excellent traffic analyzer and policy enforcer. But since DPI in most cases resides inline and manages large volumes of traffic, it can’t afford  “wasting” cycles on polling information from other systems and correlating a lot of conditions.

This is a perfect assignment for the out-of-band PCRF server. PCRF is a decision point – PDP (Policy Decision Point). Once the decision is made it’s sent out to one or more PEPs (Policy Enforcement Point). DPI is a great PEP, but other equipment in the network might occasionally be better suited to host certain policies. The Gx interface in 3GPP enables standardized integration between DPI and PCRF. But the fact is that most installations still use a SOAP interface and a more or less proprietary API, but Gx is starting to make an entrance.

Since DPI and PCRF is part of the same eco system, resolving the same challenges, it’s quite understandable that there is some confusion as to whether or not DPI competes with PCRF vendors like Camiant, Openet, Bridgewater and Volubill. That’s certainly not the case. It’s rather the opposite where everyone’s working with everyone. I dare say it’s flat out promiscuous. Do I also dare to assume there will be consolidation within and between the two segments? Well, let me put it this way: anything else would surprise me.

We, Procera, see that most of our customers and prospects either made a decision or are making a decision on PCRF as they deploy DPI today. This is great. It opens up even more opportunities and options for how to create new services, how to strengthen the operators’ business case, and how to adjust to accommodate the ever-changing reality.