DSR Configuration

References:
Configuring the DSR can include:

Configuration of the DSR Topology

DSR supports an OAM architecture with one or more pair of NOAM servers and one or more pairs of SOAM servers per DSR NE.
  • OAM configuration, some Diameter configurations, and some DSR Applications configuration are done on the NOAM
  • Most Diameter and DSR Application configurations are done on the SOAM.
  • Some common utilities can be accessed on either OAM.
The DSR topology NOAM server and SOAM servers, determines how various components are configured. There are two types of GUIs used for managing a network of DSR Signaling NEs.
  • The DSR NOAM hosts a GUI that is primarily for managing A-sourced data. A-sourced data is Platform and topology data.
  • The DSR SOAM hosts a GUI for that is primarily for managing B-sourced data. B-sourced data is DSR data.

The DSR topology allows administrators to access all DSR SOAM GUI pages from a single point. An administrator can access all of the DSR SOAM GUI pages when logged into the DSR NOAM GUI, without needing to re-enter login credentials.

A-sourced, A-scoped, B-sourced, and B-scoped Data

The bulk provisioning data and network topology data (such as user accounts, network elements, servers, server groups, and upgrade) that is to be configured and managed through a DSR NOAM are called A-sourced data. (Some Diameter configuration and some Policy and Charging application configuration is done on the NOAM.)

The Diameter signaling data (such as Local Nodes, Peer Nodes, Connections, Route Groups, and Route Lists) and DSR Application data (FABR, RBAR, CPA, PCA, GLA) that is configured and managed through a DSR SOAM are called B-sourced data.

The platform MEAL data generated by all NOAM, MP, and SOAM servers, which is merged to NOAM servers, are called A-scoped data.

The Diameter signaling MEAL data and DSR Application MEAL data that are generated by all MP servers and merged to SOAM servers are called B-scoped data.

MEAL data is handled as follows:
  • The A-Scoped MEAL data (Platform MEAL data) generated by all NOAM, MP, and SOAM servers can be viewed on NOAM servers.
  • The A-Scoped MEAL data (Platform MEAL data) generated by all MP and SOAM servers can be viewed on SOAM servers.
  • B-Scoped MEAL data (Diameter signaling MEAL data and DSR Application MEAL data) generated by all MP servers can be viewed on SOAM servers.
The following common utilities are available on both the NOAM and SOAM servers:
  • Alarms and Events
  • Security Log
  • Status & Manage
  • Measurements
  • Communication Agent
  • Diameter Common

Diameter Configuration

The DSR requires configuration for Diameter routing and transport functions.

DSR Applications require Diameter configuration that supports and is specific to the functions that the DSR Applications perform.

Diameter Configuration components and configuration procedures are described in detail in the Diameter User 's Guide, Diameter Mediation User 's Guide and Diameter online help.

Configuration for Diameter Routing Functions

Message routing is provided through the DSR. The DSR functions as a Diameter Relay Agent to forward messages to the appropriate destination based on information contained within the message, including header information and applicable Attribute-Value Pairs (AVP). User-defined Peer Routing Rules define where to route a message to upstream Peer Nodes. Application Routing Rules route messages to DSR Applications. The DSR provides the capability to route Diameter messages based on any combination of, or presence or absence of, the following message parameters:
  • Destination-Realm
  • Destination Host
  • Application ID
  • Command Code
  • Origination Realm
  • Origination Host
  • IMSI
The DSR supports multiple transport connections to each Peer Node and provides the following functions:
  • Routing Diameter Request and Answer messages received from Diameter Peers
  • Weighted load sharing
  • Priority routing
  • Rerouting
Configuring DSR routing includes:
  • Creating Route Groups and assigning Capacity levels to each Peer Node in each Route Group.
  • Creating Route Lists and defining Active and Standby Route Groups in each Route List. Active and Standby status is determined by Peer Node Priority and Weight.
  • Creating Peer Routing Rules and assigning Route Lists and Priorities to the rules.
  • Creating Application Routing Rules that route messages to DSR Applications
  • Creating Egress Throttling Groups and Message Copy Configuration Sets

Configuration for Diameter Transport Functions

The Diameter Transport Function communicates connection management information to the Diameter Routing Function that it needs for making routing decisions (including Operational Status changes, rerouting Requests, and Connection Priority Level changes).

A transport connection provides the reliable transport connectivity between a Local Diameter Node and a Peer Diameter Node. A transport connection must be configured in order for the Diameter Routing Function to allow a transport connection to be established with a Peer Diameter Node. A transport connection may use the SCTP or TCP transport protocol. A node using the SCTP transport protocol can be configured to advertise more than one IP address and to establish SCTP paths to more than one Peer IP address. Two IP Addresses are supported for an SCTP multi-homed connection both for the Local Node and Peer Node.

The primary transport Diameter configuration components are Local Nodes, Peer Nodes, Connections, and Configuration Sets. The DSR supports both IPv4 and IPv6 connections.

Configuration for transport includes:
  • Connection TCP or SCTP transport protocol, SCTP multi-homing or uni-homing, and Fixed or Floating (IPFE TSA) connection type
  • Local Node FQDN, Realm, IP Addresses, and transport protocol
  • Peer Node FQDN, Realm, IP Addresses, and transport protocol
  • Connection, Capability Exchange (CEX), Message Priority, and Egress Message Throttling Configuration Sets
  • Common Diameter Application Ids
  • Capacity (ingress and egress message rates) and Congestion Controls:
    • Diameter MP Congestion Management, including internal resource management, MP Processing Overload Control, and Maximum MPS Limitation
    • User Configurable Message Priority
    • Per connection Ingress MPS Control
    • Remote BUSY Congestion
    • Egress Transport Congestion
    • Per Connection Egress Message Throttling
    • User-Configurable Connection Pending Transaction Limiting

DSR Applications Configuration

Configuration for DSR Applications can include:
  • OAM configuration, including servers and server groups
  • Communication Agent configuration
  • Configuration of Diameter components that is specific to the functions that the DSR Applications perform, including
    • MP Profiles for DA-MPs and SBR servers
    • Application Ids for specific Diameter interfaces
    • Command Codes
    • Peer Nodes
    • Local Nodes
    • Connections
    • Route Lists
    • Peer Routing Rules
    • Application Routing Rules
  • Configuration on the NOAM or SOAM, or both, of DSR Application components
Parent topic: DSR Configuration Overview