Re-Purposing of basic capabilities

Smartphones don’t include the machinery for a flashlight, but they do include a display that is under the complete control of the software. Somebody put two and two together and came up with an app to set the display to its maximum brightness. This example points to how creating APIs allows developers to use the equipment in novel ways to create new services and applications. Having the ability to deploy today’s applications (VPN, routing, firewall, SBC, etc.) in a flexible and low cost fashion is great. What happens when somebody comes up with a great new way to process and deliver packets? What kind of new services will that enable?

The idea of creating new applications that are based on control of the native capabilities of the equipment is one of the main components of SDN in general and of OpenFlow in particular. The inventors of OpenFlow envisioned the ability to create and deploy new network protocols without having to upgrade the network equipment or its software. What’s more interesting to me is the possibility of creating new network applications that leverage the built-in functions of the equipment. For example, we may choose to provide the ability to run virtual machines in a piece of gear at the customer premise with the idea that it will be used for today’s functions such as firewalls and routers. What if we then use that compute and store resources to provide some sort of “virtual office” (whatever that is)?

Lowering the barriers

The laundry app is a great example of what happens when you make development easier. By virtue of creating a system where any industrious developer can write an app, smart phones have democratized and expanded the creation of content. The same principle applies to SDN and NFV. By creating open APIs and an ecosystem of software suppliers, we will have enabled a new breed of developers to apply their creativity. Instead of standalone smart phone apps, they will be using “network as a service” to create advanced applications that couple connect, compute and storage functions. 

But how do we make money?

I have written elsewhere that successful innovation needs three components:

1. Domain knowledge: in this case, the service providers are bringing their deep knowledge of communications networks to the party.
2. Technology: SDN, NFV and cloud technologies provide new tools to enable innovation.
3. A problem or opportunity: The Metro Edge is a target-rich environment, both for improving cost as well as for new services based on the technologies above.

By combining domain knowledge and technology to solve today’s problems CSPs will be able to develop lucrative new services and cut costs. They will also clear a path to the unknown innovations of tomorrow.