Beyond SDN

image presenting Software-defined EPC based on YateUCN

Beyond SDN is a software implementation of all core network functions, that splits the control plane, which enables flexibility, from the data plane, which facilitates enables performance and speed. In other words, beyond SDN combines the virtualization and automation from network function virtualization (NFV) and the programmable nature of software-defined networking (SDN).

Our YateUCNTM core network solution uses a single hardware- and software- agnostic server to carry out all the core network functions of the many different boxes, protocols and interfaces of GSM and LTE core networks.

Using commodity hardware, this solution is a commercial, off-the-shelf server, and can be reconfigured to support any mix of technologies. This eliminates the investment required by special-purpose equipment.

As opposed to the virtualized Evolved Packet Core, this technology implements a single software, based on Yate (an expandable software implementation of a telephony engine), and performs all the functions of typical 4G MME, S-GW and P-GW.

Beyond SDN implements the hardware switch used in the SDN technology in the Yate kernel.

Supports all the interfaces required for connecting to a Home Subscriber Server and to the VoLTE IMS, and all SS7 protocols specific to a GSM network, allowing mobile operators to deploy 4G networks that can easily inter-work with legacy networks.

PSTN interworking can be provided either via VoIP (SIP) or over ISUP controlling an external media gateway.


SDN/NFV deployments

image presenting the openflow virtual EPC solution

SDN splits the control plane from the data plane and makes the network more programmable.

NFV, as a part of SDN, virtualizes the functions of a network’s nodes typically executed by hardware equipment, into several software implementations.

An SDN implementation uses a hardware equipment (namely a switch), which is external to the network and enables the separation of the control and data planes. Introducing a new piece of hardware into the ecosystem limits the advantages of a truly software-defined network.

The additional hardware switch is required to convert GTP to IP.

The purpose of the switch is to have a hardware implementation of the data plane in the P-GW and to send it to the eNodeB via the data plane. Therefore, the switch must support both the encapsulation and decapsulation of the IP within the GTP. What’s more, a protocol like OpenFlow must be implemented to connect the P-GW control plane component to the data plane component.