[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Explicit Routing Rules

Explicit routing rules provide greater flexibility for routing requests when implicit routing is not enough. Explicit routing rules can be configured for all request types (authentication, authorization, accounting and WAG requests).

Configuring explicit routing rules consists of defining a condition or set of conditions and selecting a target to which the request is to be routed. You then define the order in which you want the server to evaluate the explicit routing rules.

When the IMS AAA Server receives a request, it examines the request to determine the request type. It then consults the respective routing rules to determine how to route the request. If the routing rules contain any user defined explicit routing rules, they are evaluated before implicit routing rules. The order in which explicit routing rules are evaluated is user defined. For a rule to be selected, all conditions must be true. If a rule is not selected, the next rule in the user defined list is examined, and so on. If a match for all conditions cannot be found in the explicit routing rules, the implicit routing rules are examined.

NOTE: Multiple conditions can be defined for an explicit routing rule. For the explicit routing rule to be selected to route the request, all conditions defined in the rule must be true.


Explicit Routing Rule Conditions

This section provides a description of the conditions that can be defined for explicit routing rules including:

Standard Application Identifier

This option allows you to specify the route based on the Diameter Application Identifier in the request. The available condition tests are equal to or not equal to the standard Diameter Application Identifier values, such as Diameter Network Access Server Application, or Diameter EAP Application.

Customized Application Identifier

This option is the same as the Standard Application Identifier option only you are allowed to enter a custom Diameter Application Identifier value. The available condition tests are equal to or not equal to the specified application identifier value.

NOTE: The Diameter Application Identifier value must be a valid application identifier.


User Identity

This option allows you to specify the route based on the user identity, for example the IMSI or User Name value contained in the request. The available condition tests are equal to, not equal to, present, not present, has this prefix, or has this suffix.

Realm Name

This option allows you to specify the route based on the realm name value contained in the request. The available condition tests are equal to, not equal to, present, not present, has this prefix, or has this suffix.

Service Scenario

This option allows you to specify the route based on the service scenario specified in the request. Any of the six service scenarios supported by the IMS AAA Server may be selected as the matching criteria. The available condition tests are equal to or not equal to.

Dictionary Attribute

This option allows you to specify the route based on the value of a particular dictionary attribute. The attribute is chosen from a pulldown list and the value of the attribute is user defined. The available condition tests are equal to, not equal to, present, not present, has this prefix, has this suffix or is within this range.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]