Diameter message mediation helps to solve interoperability issues. Mediation uses rules to manipulate header parts and Attribute-Value Pairs (AVPs) in incoming routable messages and peer to peer messages, when data in the message matches some specified conditions at a specified point of message processing. Tasks of the “if condition matches, then do some action” type can be solved in the most efficient way.
The Diameter Mediation feature can make the routable decisions of send reply, drop the message or set the destination-realm.
After a Rule Template definition is complete, a Rule Set can be generated from the Rule Template. The data needed for the Conditions and the Actions is provisioned in the generated Rule Set.
A Mediation rule is an instance of the data needed for the execution of Mediation logic. The actual data needed for the Conditions and the Actions is provisioned in one or more rules in the generated Rule Set. All of the rules associated with one Mediation Rule Template are collectively referred to as the Rule Set for the Rule Template. See Rule Sets.
Rule Sets can be associated with pre-defined Request or Answer Trigger Points in the DSR message processing logic. When message processing reaches a Trigger point and the Conditions in an associated Rule Set are met, the Actions for that Rule Set are applied to the message. The changes to the message content can result in modifying the message processing behavior and the routing decision at that Trigger point in the processing logic. See Triggers.
When the Mediation feature is activated in the system and Administrator privileges are activated for the feature, the Rule Templates folder appears under the Mediation folder in the Diameter left-hand GUI menu.
The Administrator privileges can be deactivated later, so that the Rule Templates folder does not appear under the Mediation folder. This prevents unauthorized modification of the created Rule Templates in the system.
When a Rule Template is being created or modified, it is in the Development state.
The Rule Template state can be changed from Development to Test to allow its Rule Set to be tested or to allow the Rule Template to be exported.
The Rule Template state can be changed to Active to enable use of its generated Rule Set for live traffic.
The Rule Template state can be changed from Test or Active back to Development to allow modification of the Rule Template (all existing rule provisioning for its associated Rule Sets will be deleted).
After a Rule Template is created and activated, the generation of the Rule Set from the Rule Template creates an entry in the Mediation Rule Sets GUI folder.
The Rule Template state can be changed to Test for testing its Rule Sets or to Active for enabling its Rule Sets for use with live traffic.
When Administrator privileges are deactivated, the state cannot be changed back to Development.
A Diagnostics Tool is available to test Mediation rules before they are subjected to live traffic in the network. The DSR Diagnostics Tool logs the rules applied, Actions taken, and other diagnostics information when a test message is injected into the system. The tool generates traffic and sends Diameter Messages on a test connection. As a test message traverses the system, the DSR application logic generates diagnostics messages at Trigger points. The Diameter > Reports > Diagnostics Tool GUI is used to view the diagnostics log reports. See Reports in the DSR Diameter User’s Guide.
The state of an imported Rule Template is set to Test by default.
The Rule Template "Message Copy" Action can be defined to trigger Diameter Message Copy for messages that are processed by Diameter Mediation.
The Message Copy Action triggers Diameter Message Copy, and specifies the Message Copy Configuration Set (MCCS) that contains the Request/Answer content criteria to be used by the Message Copy function to copy the message to a DAS. The Message Copy Configuration Set specifies a Route List for the DAS. See Configuration in the DSR Diameter User’s Guide.
If Message Copy is triggered for the same message from multiple locations, the Message Copy Configuration Set for the latest Message Copy triggering prevails.
In the case of Request re-route due to invalid Result-Code, only the Message Copy Configuration Set that is associated with the Answer that completes the transaction at ATP1 is considered.
The Message Copy is performed after the completion of the original transaction. The copy of the message is not processed by the Mediation Triggering Points.