Phone: 214-960-4447

System Overload Protection

Convene Networks uses multiple mechanisms to prevent system overload and protect against different types of overload conditions.   One of these mechanisms is the use of Constraint Rules to insure that critical system resources remain available for priority message traffic.

Constraint Rules

Convene Networks, ConveneDRA, ConveneGSC, Diameter Message Routing

Constraint rules provide system overload protection by providing:

  • Message and AVP/IE dictionaries defining templates that can be used to match messages;
  • Configurable limits on occurrences of constraint types;
  • Types of constraints to be applied when constraint rule is applied;
  • Treatments used when constraint limits are met.

Up to 1000 rules can be configured and applied to ingress or egress messages, and the basis of:

  • Group;
  • Cluster;
  • Interface Application;
  • Interface;
  • Peer.

Constraint rules have unique priorities and are strictly processed on descending priority order.  Once a constraint treatment is applied, no further rules are applied.  Constraint rules are applied prior to manipulation rules.

Constraint types include:

  • Request Rate – Maximum rate at which requests are allowed;
  • Active Session Limit – Maximum simultaneously active sessions;
  • Pending Request Limit – Maximum outstanding/unanswered requests;
  • Message Match – Messages match a configured template;
  • Message Match Rate – Maximum rate at which messages matching templates may be processed.

If the constraint type condition is met, the associated treatment is applied.  For treatments applied to outbound messages, if another route is available without violating a constraint, that route will be used rather than applying the treatment.

Treatments include (Diameter interfaces):

  • Drop – The message will be silently discarded;
  • DIAMETER_COMMAND_UNSUPPORTED – Reject with Result code 3001;
  • DIAMETER_UNABLE_TO_DELIVER – Reject with Result code 3002;
  • DIAMETER_REALM_NOT_SERVED – Reject with Result code 3003;
  • DIAMETER_TOO_BUSY – Reject with Result code 3004;
  • DIAMETER_APPLICATION_UNSUPPORTED – Reject with Result code 3007;
  • Vendor ID/Result Code – Reject with configured Vendor ID and Result code.

More information on ConveneGSC.

More information on Convene Networks and its products.