Thursday, August 17, 2017

Going Cloud-Native with Radiator VNF

Cloud-native packet core architecture

Nowadays, many telcos target their packet core architecture at a cloud-native implementation, which is deployed in their own virtual infrastructure environment. In this environment, all different network functions, such as AAA, are virtualised.

This infrastructure supports all services (data, voice, IoT, and so on) and all wireless access technologies including WiFi, LTE, and 5G. Also the data plane and control plane are fully separated. They are likely to follow different deployment models, such as centralised control plane and session management or distributed data plane.

Radiator - cloud-native AAA solution

Radiator VNF is an ideal solution for this kind of approach and migration to cloud-native infrastructure. Radiator VNF components and virtual hosts are configured automatically through a centralised configuration system. In addition to this, all VNF components interact using the redundant message queue. Cloud-native approach is also seen in load balancers, that ensure that you always have the right amount of AAA capacity in your cloud-native network.

radiator-vnf-architecture.png

Radiator VNF is cloud-native from architecture point of view as well

Two ways: cloud-native from the start or step-by-step approach

For transition to Radiator VNF for your AAA solution, you can run it on your cloud-native infrastructure, such as Openstack. The other alternative is that you run Radiator VNF with a static configuration on VMs. In that case, you can have all the components, such as load balancers, developed for Radiator VNF, but options in scaling and automatic configuration are more limited. They emerge when your infrastructure is transformed to be cloud-native. Our licensing options and Radiator deployments support both approaches.

If you want to get more information, please see Radiator VNF technical documentation, or contact our team at info@open.com.au

No comments:

Post a Comment