Page History
...
- Service Chaining: The SBC includes functions such as call control, routing and policy, signaling normalization, IP firewall and policy, and media transcoding (or trans-rating). Each component of the D-SBC logically provides one or more such functions instantiated in a cluster to support scaling based on the traffic requirement. The signaling component of the SBC chains one or more such functions per call without knowing the media cluster details.
- Investment protection: Reusing existing custom hardware for media interworking saves cost. The custom hardware coexists with the media components providing media inter-working services. Also, when required it is invoked as an external media server.
- High Resilience with Low Media Latency: Geographically separated media components are deployed closer to the network in a cluster resulting in switching media at the network's edge rather than backhauling from the core, and reducing media latency and backhauling costs with increased quality of experience. Also, multiple media instances provide resilience by selecting media components from different site.
...
| Spacevars | ||
|---|---|---|
|
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 environment supports multiple clusters simultaneously, each providing a specific service:
...
These clusters coordinate with each other and are linked by the S-SBC using the Sonus Media the
| Spacevars | ||
|---|---|---|
|
| Caption | ||||
|---|---|---|---|---|
| ||||
|
N:1 Redundancy Architecture
Sonus The D-SBC supports an N:1 mechanism for the SBC SWe Cloud mechanism where one standby instance acts as the back up for "N" active SBC instances. In a fail-over scenario, the standby instance takes over and becomes active and the failed active instance becomes standby, once it is up and running.
| Info | ||
|---|---|---|
| ||
The maximum value for N is one for Signaling SBC (S-SBC) and four for Media SBC (M-SBC). 4:1 M-SBC deployments are supported on OpenStack and must be instantiated using Heat templatesin the OpenStack cloud environment. |
SBC Redundancy Groups
An SBC Redundancy Group (RG) consists of one or more SBC SWe Cloud 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 cluster or a Media cluster.
...
Overview
Content Tools