Page 20 - cdm-2014

.1),% /( .$)(- $,./ &$4 .$)( ( * % . (-* .$)(
3)( .# 3-. ,3

Much discussion has occurred around Network Functions Virtualization (NFV) and the proper
deployment models for Deep Packet Inspection (DPI) in the emerging virtualized landscape. To
listen to some, this has taken on all the mystery of a Hollywood thriller complete with twists and
turns, car chases and dark alleys, all adding to the confusion with this movement - one in which
the standards have not yet become the norm.

Confusing and confounding the marketplace seems to be the raison d’etre for those poorly
equipped to address it with solutions.

However, as this NFV story unfolds, we will begin to realize that this unnecessary mystery can
easily be replaced with clear and logical solutions.

At Procera, we believe that the demand for embedded application identification enabled by DPI
within virtualized network elements is simply the logical next step for certain applications. Just
as composed solutions built on purpose-built hardware required this important capability, so too
will the virtual evolution of these devices.

As posited in the mythical “Occam’s Razor” and as is evident in this case, the simple answer is
preferable, and more often than not, correct.

Demonstrative of this succinct dynamic, our customers continue to virtualize their products
making them more economical to deploy. Increasingly, what was once a premise-based box is
now packaged and sold as a cloud-based service.

While somewhat counterintuitive, we have seen many cases where this has increased average
selling price and driven broader adoption and deployment.

The applications of virtualization run the full gamut of categories. From bread and butter security
use cases to application performance monitoring, as well as virtual challenges to the “big iron”
of yesterday’s evolved packet core (EPC), DPI continues to be a critical component of these
functions, and Procera remains committed to serving this marketplace with our embedded DPI
engine, Network Application Visibility Library (NAVL), just as we always have. Our resolve to do
so is paying the dividends we anticipated.

As one happy customer recently noted, “NAVL is a critical component of what we do and while
our product certainly brings application identification to light through superior presentation and
analytics capabilities, it requires NAVL regardless of deployment model or packaging.

Moving to a virtualized solution has been a commercial success beyond our expectations. Doing
so has allowed the customer to deploy our virtual solution in more points of presence thereby
increasing wallet share for us.”

! " $ !
! # ! "