The purpose of SCCP management (SCMG) is to maintain—if possible—the transfer of SCCP messages when failures occur in the signaling network and/or subsystems, and to inform SCCP users to stop sending messages that cannot be delivered. If a failed subsystem has a duplicate, SCMG requests its SCCP to reroute messages to the backup subsystem .
15.5.1 SCMG Interfaces
SCMG has interfaces with the subsystems, the MTP, and the SCCP connectionless control at its signaling points—see Fig. 15.1-2.
N-Primitives are the interface with the local subsystems. The subsystems pass information, to SCMG in N-requests and N-responses, and SCMG passes information to the subsystems in N-indications and N-confirmations.
The interface with SCCP connectionless control allows SCMG to send and receive SCCP Unitdata messages to/from SCMGs in other signaling points.
The interface with the local MTP consists of MTP-pause, MTP-resume, and MTP-status indications (Section 8.9.1).
15.5.2 N-Primitives and Their Parameters Primitives. The N-primitives (Fig. 15.1-2) are outlined below:
N-State Primitives. These primitives indicate a change in status of a subsystem. A subsystem indicates a status change to its SCMG in an N-state request, and
TABLE 15.5-1 SCCP Management Primitives and Parameters
Was this article helpful?