2.6.6 Message Prioritization

This feature provides a method for DSR administrators to assign message priorities to incoming Diameter requests. This priority configuration can be associated with a connection, peer node, application routing rule, or a peer routing rule. As messages arrive they are marked with a message priority. Once the message priority is set it can be used as input into decisions around load shedding and message throttling.

The Message Priority Configuration Set (MPCS) table is used for this configuration. The following are some of the defined methods used for setting message priority:

• Based on the connection upon which a message arrives.
• Based on the peer from which a message is sent.
• Based on an Application Routing Rule .
• Based on a Peer Routing Rule.

Each MPCS contains the following information:

MPCS ID – The ID is used when associating the configuration set with a connection.

Set of Application-ID, Command-code, priority tuples, also called message priority rules.

• Application-ID – The Diameter application-ID. The application-id can be a wildcard indicating that all application-ids match this message priority rule.
• Command-code – The Diameter command-code. The command-code can be a wildcard indicating that all command-codes within the specified application match this message priority rule.

  Note:

  If multiple command-codes with the same appl-id are to get the same message priority then there will be a separate message priority rule tuple for each command-code.
• Priority – The priority applied to all request messages that match the Application-ID, Command-Code combination.