Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Configuring Request Routing Rules

To configure request routing rules for an authentication or authorization request type using the Web GUI:

  1. Select Diameter Configuration > Request Routing > Authentication Routing Rules or Authorization Routing Rule.

    The Request Routing page for the particular request type appears. As an example, Figure 178 shows the Authentication Routing Rules page.

    Figure 178: Authentication Routing Rules Page

    Authentication
Routing Rules Page

    Referring to Figure 178, the Explicit Routing Rules area displays any explicit routing rules already defined for the request type. Any implicit routing rules are displayed in the Implicit Routing Rules area.

  2. Define explicit routing rules. For more information about defining explicit routing rules, see Defining Explicit Routing Rules.

    You can modify the explicit routing rules entry by using the Edit and Delete buttons.

    Note: The implicit routing rules are automatically populated in the Implicit Routing Rules area after assigning functions to the Diameter remote network element. For more information about assigning functions to the Diameter remote network element, see Assigning Functions to the Diameter Remote Network Element.

  3. Define the order of explicit routing rules by selecting each explicit routing rule and using the Up or Down arrow.
  4. Click Save to save the configuration.

Defining Explicit Routing Rules

Explicit routing rules provide greater flexibility for routing requests when implicit routing is not sufficient. Explicit routing rules can be configured for both the authentication and authorization request types.

When defining explicit routing rules, you define a condition or set of conditions and select a target to which the request is to be routed.

When SBR Carrier 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 list of explicit routing rules 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.

To define explicit routing rules using the Web GUI:

  1. In the Request Routing page (for a sample Authentication Routing Rules page, see Figure 178), click Add to add a new explicit routing rule.

    The Add Explicit Routing Rule dialog box for the selected routing rule appears. Figure 179 shows this dialog box for authorization requests. The dialog is same for both the authorization and authentication requests, only the respective target varies.

    Figure 179: Add Explicit Routing Rule Dialog for Authorization Requests

    Add
Explicit Routing Rule Dialog for Authorization Requests
  2. Select a target for the authentication or authorization request type from the Target list.

    Table 44 shows the targets for each request type.

    Table 44: Request Type and Target

    Request Type

    Target

    Authentication

    • HSS
    • Downstream (Diameter server)

    Authorization

    • Downstream (Diameter server)
  3. Define a condition for the explicit routing rule. For more information about defining conditions for the explicit routing rule, see Defining Conditions for the Explicit Routing Rule.

    You can modify the condition entry by using the Edit and Delete buttons

  4. Click OK to save the configuration.

    The Explicit Routing Rules area in the Request Routing page (For a sample Authentication Routing Rules page, see Figure 178) displays the updated list of explicit routing rules.

Defining Conditions for the Explicit Routing Rule

To define a condition for the explicit routing rule using the Web GUI:

  1. In the Add Explicit Routing Rule dialog box (Figure 179), click Add.

    The Add Condition dialog box (Figure 180) appears.

    Figure 180: Add Condition Dialog

    Add Condition Dialog
  2. In the Add Condition dialog box, you can:

Defining Standard Application Identifier Conditions

This standard application identifier condition allows you to define the routing rule 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.

To define the standard application identifier condition for the explicit routing rule using the Web GUI:

  1. In the Add Condition dialog box (Figure 180), select the Standard Application Identifier option.

    The Standard Application Identifier pane (Figure 181) appears.

    Figure 181: Standard Application Identifier Pane

    Standard
Application Identifier Pane
  2. Select either Is equal to or Is not equal to in the Condition Test field.

    Note: The Name field displays the name of the Diameter application identifier. This is a read-only field.

  3. Select a standard Diameter application identifier from the Value list.
  4. Click OK.

    The Conditions area in the Add Explicit Routing Rule dialog box (Figure 179) displays the updated list of condition rules.

Defining Customized Application Identifier Conditions

The customized application identifier condition is the same as the standard application identifier condition, the only difference is that here 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.

To define a custom application identifier condition for the explicit routing rule using the Web GUI:

  1. In the Add Condition dialog box (Figure 180), select the Customized Application Identifier option.

    The Customized Application Identifier (Figure 182) pane appears.

    Figure 182: Customized Application Identifier Pane

    Customized
Application Identifier Pane
  2. Select either Is equal to or Is not equal to in the Condition Test field.

    Note: The Name field displays the name of the Diameter application identifier. This is a read-only field.

  3. Enter a valid application identifier in the Value field.
  4. Click OK.

    The Conditions area in the Add Explicit Routing Rule dialog box (Figure 179) displays the updated list of condition rules.

Defining User Identity Conditions

The user identity condition allows you to define the routing rule based on the user identity, for example the IMSI or username value contained in the request. The available condition tests are equal to, not equal to, present, not present, has this prefix, and has this suffix.

To define a user identity condition for the explicit routing rule using the Web GUI:

  1. In the Add Condition dialog box (Figure 180), select the User Identity option.

    The User Identity pane (Figure 183) appears.

    Figure 183: User Identity Pane

    User Identity Pane
  2. Select a condition in the Condition Test field.

    Note: The Name field displays the name of the user identity. This is a read-only field.

  3. Enter the user identity in the Value field.
  4. Click OK.

    The Conditions area in the Add Explicit Routing Rule dialog box (Figure 179) displays the updated list of condition rules.

Defining Realm Name Conditions

The realm name condition allows you to define the routing rule 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.

To define a realm name condition for the explicit routing rule using the Web GUI:

  1. In the Add Condition dialog box (Figure 180), select the Realm option.

    The Realm pane (Figure 184) appears.

    Figure 184: Realm Pane

    Realm Pane
  2. Select a condition in the Condition Test field.

    Note: The Name field displays the realm string. This is a read-only field.

  3. Enter the realm name in the Value field.
  4. Click OK.

    The Conditions area in the Add Explicit Routing Rule dialog box (Figure 179) displays the updated list of condition rules.

Defining Dictionary Attribute Conditions

This dictionary attribute condition allows you to specify the route based on the value of a particular dictionary attribute. The attribute is chosen from a 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.

To define a dictionary attribute condition for the explicit routing rule using the Web GUI:

  1. In the Add Condition dialog box (Figure 180), select the Dictionary Attribute option.

    The Dictionary Attribute pane (Figure 185) appears.

    Figure 185: Dictionary Attribute Pane

    Dictionary Attribute
Pane
  2. Select a dictionary attribute from the Attribute list.

    You can search the attributes by entering the attribute name in the text box.

  3. Select a condition in the Condition Test field.
  4. Enter the value for the dictionary attribute in the Value field.
  5. Click OK.

    The Conditions area in the Add Explicit Routing Rule dialog box (Figure 179) displays the updated list of condition rules.

Modified: 2017-09-27