The DSR implements the Diameter base protocol to serve primarily as a Diameter Relay Agent to route Diameter traffic based on configured routing data.
Diameter protocol configuration includes components that provide data for routing functions and for transport connection management.
The Diameter protocol functions in a 3-tiered DSR topology.
In DSR topology, the OAM server function is split into Network OAM (NOAM) servers and System OAM (SOAM) servers. A DSR with a pair of NOAM servers is connected to multiple DSRs in the network. Each DSR is connected to up to 16 mated pairs of SOAM servers (to support 3 fully populated enclosures). Each DA-MP resides with a pair of SOAM servers that interact directly with the respective DA-MPs on that DSR.
The DSR does not alter existing DSR functions other than separating what can be configured or managed at which level (DSR NOAM or DSR SOAM).
Each DSR services signaling traffic to and from a collection of Diameter clients, servers, and agents. The DSR MPs provide the Diameter message handling function. Each DSR MP supports connections to all of the DSR Peers.
In DSR topology, there are NOAM servers, SOAM servers, and MP servers. The NOAM server takes on network scope and the SOAM server manages a single DSR Signaling NE.
The SOAM GUI screens can be used to configure and manage Diameter data, Diameter Common data, site-specific Policy and Charging data, IPFE data, MAP-Diameter Interworking data for DM-IWF, and DSR Application data.
Diameter Common provides the Import and Export GUIs on the NOAM and SOAM for exporting and importing the configuration data for Diameter Configuration, IPFE, and DSR Applications, and on the NOAM for exporting and importing Diameter Configuration and Policy and Charging configuration data.