Diameter Configuration
-
Log in into Policy Builder.
-
Select Reference Data tab.
-
From the left pane, select Systems.
-
Select and expand your system name.
-
Select Diameter Configuration.
-
In the right pane, to add the parameters of the inbound message overload handling, check the Inbound Message Overload Handling check box.
-
In the Inbound Message Overload Handling area, define the following parameter details.
Inbound Message Overload Handling Parameters Parameter
Description
Default Priority
Default priority to be assigned to an incoming message if no specific priority is defined in the Message Handling Rules table.
Default value is 0.
Message Sla Ms
Service Level Agreement (SLA) in milliseconds, defines the number of milliseconds that are associated with an incoming event or message. In case the configured duration times out, the Discard Behavior configured in the Message Handling Rules is applied else the Default Discard Behavior is used.
Maximum time (in millisec) that a message has in an inbound message handling queue waiting for a worker thread. Configuring this value avoids processing a message to time out by a remote peer.
Default value is 1500 ms.
Inbound Message Queue Size
Allows the maximum number of messages in the Inbound Message Queue. When the number of messages exceeds this value, messages are discarded as defined in the Message Handling Rules and the Default Discard Behavior.
Default value is 1000.
Default Instance Rate Limit
This parameter is applied to messages that do not have an applicable overload handling rule configured in the Message Handling Rules table.
Default value is 0.
Default Discard Behaviour
Default behavior to be applied to an incoming message if no specific discard behavior for that message is defined in the Message Handling Rules table.
-
MESSAGE_DROP: Discards the request.
-
DIAMETER_TOO_BUSY: Sends a response message havingResult-Code AVP value set to DIAMETER_TOO_BUSY (3004).
Default value is MESSAGE_DROP
Rx Message Prioritization
Defines Rx eMPS message handling priority based on the Rx message MPS-Identifier and Reservation-Priority AVPs. For more information see Table 2.
Message Handling Rules
Defines specific inbound message overload handling rules based on different criteria. For more information, see Table 3.
Inbound Message Overload Handling Parameters Rx Message Prioritization Parameters Parameter
Description
MPS Identifier
MPS-Identifier indicates that an AF session relates to an MPS session. It contains the national variant forMPS service name. For example, NGN GETS.
Reservation Priority
The AF specifies the Reservation-Priority AVP at request level in the AA-Request in order to assign a priority to the AF session as well as specify the Reservation-Priority AVP at the media-component-description AVP level to assign a priority to the IP flow.
The Reservation-Priority AVP available at the request level only is used under Rx Message Prioritization table.
If Reservation priority is not found at the message level in Rx message, then best value of Reservation Priority is calculated from the MCD and used for lookup.
Range: 1 to 15, where 15 is considered as the highest priority and 1 is considered as the least priority.
Priority
A user defined priority based on MPS-Identifier and Reservation-Priority combination.
Higher Priority messages are processed before lower priority messages.
Message Handling Rules Parameters Parameter
Description
Diameter Client
This is used to configure different priorities for different clients based on realms.
Protocol
Specific application id value to be used for scoring. This value is used to match Auth-Application-Id AVP value.
Command Code
Specific command code value to be used for scoring. This value is used to match the Command-Code field. These command codes map to different types of Diameter messages.
Request Type
Specific request type value to be used for scoring. This value should match the value of the CC-Request-Type AVP for Gx CCR messages.
-
0: Request Type not used for scoring
-
1: INITIAL_REQUEST (1)
-
2: UPDATE_REQUEST (2)
-
3: TERMINATION_REQUEST (3)
Default value is 0.
Request type should match the value of the Rx-Request-Type AVP for Rx messages.
-
0: INITIAL_REQUEST (0)
-
1: UPDATE_REQUEST (1)
Request type should match the value of SL-Request-Type AVP for Sy SLR messages. The possible values are:
-
INITIAL_REQUEST (0)
-
INTERMEDIATE_REQUEST (1)
It has to be configured to zero if the incoming message does not have a request type AVP. For example, Rx STR does not have a request type AVP or Rx-Request-Type AVP is unavailable in Rx message as it is not a mandatory AVP per 3GPP TS 29.214.
Priority
Priority value assigned to the message. Higher numerical value has the higher priority.
Default value is 0.
For example, 10, 20, 100, 200, 300, 500 and so on.
Per Instance Tps
Transactions per second limit per process. This value is the TPS that these messages are limited to.
The actual system's transaction per second limit can be calculated using the following formula:
Per Instance Tps x Number of instances per VM x Number of VMs.
Default value is 0.
For example, 1000, 2000, 5000 and so on.
Discard Behavior
Behavior to be applied to an incoming message.
-
MESSAGE_DROP: Discards the request.
-
DIAMETER_TOO_BUSY: Sends a response message having Result-Code AVP value configured to DIAMETER_TOO_BUSY (3004).
Default value is MESSAGE_DROP.
-