Major Software Elements

Overview

The DSC uses CPUs networked with the integrated high-speed (up to 10 GB) packet-switched backplane, which are segregated by a particular function – Routing, Management, and Applications. Partitioning the functionality segregates the processing requirements of the OA&M activities from those associated with routing messages, which provides the operator with better control and security over routing elements.

For information about the DSC 8000 CPUs and DSC SWe VMs, refer to the appropriate pages in the DSC 8000 Hardware Installation Guide, DSC 8000 System Cards, and  DSC SWe (on KVM) Software Installation Guide, or DSC SWe (on VMware) Software Installation Guide. For information about OA&M functions of this platform, refer to the DSC - SP2000 Platform Manager User Guide.

The following figures show the major internal modules for the DSC 8000.

DSC 8000 Internal Modules

DSC SWe Internal Modules

Routing Software

A minimum of two Routing CPUs are required for each DSC 8000. This number can increase to a maximum of 10 Routing CPUs in a standalone chassis and up to a maximum of 12 Routing CPUs per shelf in a multi-shelf system. The actual number of Routing CPUs needed is based on the traffic handling requirements for each system deployment.

The Connection Manager process handles both internal and external logical connections to other Diameter peers.

The Routing and Screening Manager process is responsible for routing, modifying, and/or screening messages as they traverse the system. These functions are dependent on the instructions that are administered in various system routing tables.

Processes that support the translation to SS7 Mobile Application Part (MAP) messages, along with other processes such as Interworking Function (IWF) and Subscription Location Function (SLF), can also run on the Routing CPU (or a separate Routing CPU) if they are licensed for the system.

Management Software

Management CPUs and VMs support all OA&M functions for the DSC 8000 and the DSC SWe, respectively. This support includes such items as running the Web server, logging, and collecting data measurements. 

By utilizing a shared IP address for connecting to one of the available Management CPUs, connectivity to the system is simplified. 

The Proxy Bridge process (pxbr) on the Management CPUs forms the focal point for User Interface (UI) connections. The pxbr runs the TL1 and menu interface directly. This CPU also exposes UI objects to the Web interface and the Simple Network Management Protocol (SNMP) interface. Processes on other CPUs communicate with the pxbr for management functions.

Session Management Database

IP-CAN session information is stored on separate CPUs. This information is shared and synchronized across two or more CPUs to support a recovery event. In the event that one CPU restarts, the CPU will receive updated information from its peers.