The future is not the cloud or the fog: it is actually the SEA!

A casual reflection on the last few years in the evolution of the wireless network provides us all the insights necessary to reason that there is at least one final frontier coming down the road. Who can deny that the last few years have been owned by the cloud, virtualization and softwarization (if that is even a word!). Edge Computing too, which is really nothing more than the pushing of all of these concepts deep into places in the network where they have never been before. Fog computing is another term (created by Cisco) for something similar but driven in its genesis more bottom up from the many Internet of Things use cases. The bigger trend is obvious; network intelligence is distributing but where will it, can it go, beyond this?

I believe the next big step in the future will be for this trend to consume our end-user devices. More than this, when technology support catches up to this vision there will be a profound reshaping of what we all call devices. This vision is not as far-fetched as it seems. This area of technology research has a name, device virtualization, and some are referring to the new devices of this new technology area as Service Endpoint Agents, or SEA, devices.

What is a Service Endpoint Agent (SEA)?

A SEA device is a complete rethink of how your smartphone works. The phone in your pocket today is basically a fully integrated device consisting of many blocks of hardware and software all dedicated for you and your own purposes alone. With the exception of application software (e.g. gaming, music, personal assistants) that run in some part in the cloud, most everything you do on your device relies in some way or another on a local execution. A SEA device will not necessarily work like this. In the device virtualization paradigm, the same principles that allow virtualization across data centers or the abstractions of EPC elements in the cloud are applied to enable the dynamic decomposition of functions in a device into executable tasks. These functions may then be assigned for execution wherever this may be optimal, e.g., in another end user device or in a nearby Edge node. In this way, a personal virtual device experience can be enabled via any user interface that may be immediately available to an end user. This interface may be simple or complex. The key, however, is that the interface in whatever form it takes provides the role of a SEA to the end user.

Why would we go to all this trouble?

The key motivation driving this nascent technology trend is flexibility. This is the exact same flexibility motivation that is behind the very observable transformation going on in the wider network today. The advantages are similar; the terminal functions, in this case, can be executed at more immediately capable nodes, providing better performance including battery savings. Another advantage is better management of end user services possibly over a centralized management entity along with increased service scalability.

Leave a Reply

Your email address will not be published. Required fields are marked *