Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

Table of Contents

This section describes the basics of the SBC SWe Cloud architecture model.

...

Overview 

In traditional real-time communication, voice sessions have a one-to-one relationship between signaling and media, either with or without transcoding. The service provider defines the application that runs on the device; hence, network elements, gateways, or SBCs require single dimensional scaling. An integrated signaling and media network element (I-SBC) scales horizontally and often runs on a custom hardware to provide the required scaling and capacity. I-SBCs dominate the network traffic in service provider networks. The SBC hardware series is designed to process and transcode more calls, utilizing all the available media resources. But as services evolve to support multimedia, the change in traffic turns out to be more dynamic.

...

The D-SBC architecture breaks all the services into separate functions known as clusters. A cluster is a single application consisting of multiple discrete compute elements such as VMs. A cluster includes one application, such as S-SBC or M-SBC, with multiple nodes providing a specific service. The cloud A virtual environment supports multiple clusters simultaneously, each providing a specific service:

...

Info
titleNote

 The maximum value for N is currently four in the OpenStack cloud environment.

SBC Redundancy Groups

An SBC Redundancy Group (RG) consists of one or more SBC SWe node instances. All the instances in an RG must have homogeneous resource allocation, configuration and personality. A cluster is a group of one or more SBC RGs. All RGs in a cluster must use the same SBC type (Signaling SBC or Media SBC), which dictates the cluster type such as a Signaling signaling cluster or a Media media cluster.