In this section:
DSC 8000 SS7 and Diameter Software Architecture (Control Shelf)
The following figure depicts the DSC 8000 SS7 Software Architecture (Control Shelf) with the DSC 8000 SS7 and DSC software components. This figure also depicts where these components reside and displays some of the interaction and responsibilities of the components. This information may be helpful while provisioning the system and interacting with the various User Interfaces (UIs). For detailed information about the supported UIs, refer to the Web UI and Menu UI Guide.
DSC 8000 SS7 Software Architecture (Control Shelf)
For information about the SS7 software components shown in the preceding figure and some additional software components, such as Point Code Emulator (PCE), Integrated Monitoring Feed (IMF), and Intelligent Network Application Protocol (INAP) Gateway (INAPGW), refer to the appropriate chapters in the SS7 Application Guide 1, SS7 Application Guide 2, and Ribbon DSC Application Guide. The table, DSC SS7 and Diameter Processes, lists and describes the various components that are shown in this figure.
For information about unsupported SS7 and DSC applications, refer to the About the Documentation Library.
DSC8000 Distributed Architecture
As shown in the preceding figure, the DSC 8000 is equipped with two AMC124 Management CPU cards. A primary/standby relationship is supported between the management processes on these cards. Each software layer selects its primary CPU independently, based on the state of the processes for that layer; as a result, the primary process for MTP may be on a different CPU card than that of Signaling Connection Control Part (SCCP).
The DSC 8000 supports a minimum of two CPU cards which process traffic in an active/active relationship. On each CPU, there are one or more processes running for each layer of the SS7 protocol stack. These peer processes continuously share state information about traffic, connections, and provisioning through a Layer Distribution Library (LDL) connection that uses Stream Control Transmission Protocol (SCTP) over the IP backplane. This architecture allows, for example, the reassembly of segmented Signaling Connection Control Part (SCCP) messages even if these messages arrive on links associated with a different CPU.
Note
The maximum number of Routing CPUs for a one-shelf system is ten and for four-shelf system is 46.
DSC SWe SS7 and Diameter Software Architecture
The following figure shows the DSC 8000 SS7 and DSC software components for the DSC SWe.
DSC SWe SS7 Software Architecture
DSC SS7 and Diameter Software Processes
The following table lists and describes the DSC SS7 and Diameter software processes.
DSC SS7 and Diameter Processes
| Process | Implements |
|---|---|
MTP2 | Message Transfer Part Level 2 (MTP2) Hardware provides the utilities to configure and connect the Time Division Multiplex (TDM), Asynchronous Transfer Mode (ATM), and Annex A Signaling Channels. |
MTP3 (SNM and DRE) | MTP3 provides the utilities to configure the DSC internal communication, Network Appearances (NAs) supported by this platform, as well as linksets, links, routesets, and routes processed by the platform. |
| SCCP | Signaling Connection Control Part (SCCP) provides the utilities to configure MTP3 applications. SCCP is only available and visible in the UI if the GTT, Signaling Gateway (SG) or any other SCCP traffic based L4 application is purchased. |
| SG | Signaling Gateway (SG) provides the utilities to configure transparent interworking of SS7 signaling between Public Switched Telephone Network (PSTN) and IP networks. The application supports the following protocols:
|
| GTT | Global Title Translation (GTT) provides the utilities to configure Global Title routing. GTT works in conjunction with SCCP. |
| GWS and MSU Tracing | Gateway Screening (GWS) provides the utilities to control the flow of SS7 messages into and through a signaling network from the SS7 links and SG M3UA/SUA Configured ASPs. A DSC Platform that supports this process examines the contents of incoming messages and determines whether the message is authorized and accepted or is unauthorized and rejected. If a message is accepted, it is sent to MTP3, SCCP, or Integrated Service Digital Network User Part (ISUP) for further processing. If a message is rejected, it is discarded. Message Signal Unit (MSU) Tracing allows a user to trace SS7 messages throughout system processes such as MTP3, SCCP, GTT, and Signaling Gateway. MSU tracing uses the GWS tables to specify the tracking criteria. |
| IWF | Interworking Function (IWF) maps traffic between the SS7/Mobile Application Part (MAP) and Long-Term Evolution (LTE) networks. The DSC STP and SG handle the SS7 routing while the Ribbon DSC handles the Diameter routing. IWF is only available and visible in the UI if the Ribbon DSC and SCCP applications have been purchased. Based on the installation requirements, GTT may also be required. |
| DSC | DSC provides the utilities for Diameter protocol-based signaling in a carrier IP network. This signaling comprises control and monitoring of this IP network, efficient routing of messages, and feasible use of network resources. |
Software Process Scalability and Redundancy
To ensure that your system is provisioned for optimal scalability and redundancy, you can
- add additional CPUs or VMs
- provision multiple M2PA and/or SS7 links (as applicable)
- provision the system for IP-path redundancy (uni-homed or multi-homed configuration)
- use the DSC in a mated pair configuration
For more information about software process redundancy, refer to the applicable pages in the SS7 Application Guide 1, SS7 Application Guide 2, and Ribbon DSC Application Guide.
Overview
Content Tools