| Diameter Signaling Router Policy and Charging Application Release 8.2 E89000 |
|
 Previous |
 Next |
Table 6-14 describes the elements on the page on the NOAM.
Table 6-14 Policy DRA Network-Wide Options Elements
| Fields (* indicates a required field) | Description | Data Input Notes |
|---|---|---|
| General Options | ||
| Enable PCRF Pooling | Indicates whether the PCRF Pooling feature is enabled. Check the box to allow a subscriber's policy sessions to be routed to different PCRFs depending on the Access Point Network the session originated from. this box must be checked following acceptance of upgrade or future upgrades will be disallowed. |
Format: Checkbox Default: PCRF Pooling Enabled (checked) for fresh installs, PCRF Pooling Disabled (unchecked) Range: Checked or Unchecked |
| PCRF Pooling Mode | Indicates whether PCRF Pooling should operate in Single Pool or Multi Pool mode.
Select Single Pool Mode if several items are true:
When Single Pool Mode is selected, all new binding capable session creation messages are routed using the Default PCRF Pool, regardless of the APN to PCRF Pool mapping. When Multi Pool Mode is selected, new binding capable session creation messages are routed using the PCRF Pool associated with the APN in the session creation message. |
Format: Radio button Default: Multi Pool Mode Range: Single Pool Mode or Multi Pool Mode |
| Default APN for Non Specific Binding Key Correlation | APN to use for binding correlation if no APN is present in a binding dependent session creation request that needs to correlate using an IMSI or MSISDN key. If several items are true:
If this field is enabled, no APN is selected and a binding dependent session creation request is received that includes an IMSI or MSISDN key, neither IMSI nor MSISDN, will be used for binding correlation. Default APN for Non Specific Binding Correlation is disabled if Single Pool Mode is selected. |
Format: Drop-down list Default: N/A Range: List of configured APNs |
| Early Binding Options | ||
| * Early Binding Polling Interval | The number of milliseconds between sending queries to the early binding master to determine which PCRF the master session was routed to so that the slave session can be routed to the same PCRF. The goal is to set this value such that the master session has time to receive an answer a high percentage of the time. Choosing a low value increases database queries, but may reduce latency. A high value does the opposite Note: This values is used only when PCRF Pooling is enabled. |
Format: Text box Default: 200 milliseconds Range: 50 to 10000 milliseconds |
| * Maximum Early Binding Lifetime | The maximum time that a binding is allowed to remain as an early binding. The ideal setting for this value is 100 - 200 msec longer than the Diameter transaction timeout. This value prevents bindings from becoming stuck for long periods in the early binding state due to congestion or other error conditions. If a new Diameter request or polling attempt discovers a binding session that has been in the early state for longer than this time, the binding session is removed. Note: This value is used only when PCRF Pooling is Enabled. |
Format: Text box Default: 2500 milliseconds Range: 500 to 15000 milliseconds |
| Topology Hiding Options | ||
| Enable Topology Hiding | Enable or disable topology hiding using the check box. Once enabled or disabled here, the Topology Hiding is enabled or disabled at all SOAMs under this NOAM. | Format: Check box Default: Disabled (unchecked) Range: Enabled (checked), Disabled (unchecked) |
| Topology Hiding Scope | This sets the scope of messages where topology hiding will be applied. Select All Messages to perform topology hiding for all messages destined to policy clients. Select All Foreign Realms to perform topology hiding for messages destined to the policy clients whose realms are different from the realm of the PCRF to be bound. Select Specific Clients to perform topology hiding for the policy clients that are configured in on the SOAM GUI Main Menu: screen. Select All Foreign Realms + Specific Clients to perform topology hiding if either condition (All Foreign Realms or Specific Clients) is met. | Format: Drop-down list Default: N/A Range: All Messages, All Foreign Realms, Specific Clients, All Foreign Realms + Specific Clients |
| Default Topology Hiding Virtual name |
|
Format: Text box Default: N/A Range: FQDN and Realm - a case-insensitive string consisting of a list of labels separated by dots, where a label may contain letters, digits, dashes (-) and underscore (_). A label must start with a letter, digit or underscore and must end with a letter or digit. Underscores may be used only as the first character. A label must be at most 63 characters long and a FQDN must be at most 255 characters long. |
| Suspect Binding Removal Options | ||
| * Suspect Binding Removal Events Ignore Interval | This value can be used to ignore Suspect Binding Removal Events that arrive in quick succession. If a Suspect Binding Removal Event arrives for a given binding, but the time interval specified Suspect Binding Removal Events Ignore Interval has not yet elapsed, the event will not be counted against the Suspect Binding Removal Events Threshold. Setting the value to zero means that no events are ignored. It may be desirable to select a value such that retransmissions are ignored. |
Format: Text box Default: 1 Range: 0-30 sec |
| * Suspect Binding Removal Events Reset Interval | This value is used to separate occurrences of PCRF unavailability. The interval is started at the time when the last suspect binding event is counted. If no subsequent suspect binding event occurs after this interval, the suspect binding event count is reset and the suspect binding associated with the count is no longer considered as suspect until the next suspect binding event occurs. |
Format: Text box Default: 60 min Range: 1-3600 min |
| * Suspect Binding Removal Events Threshold | The Suspect Binding Removal Events Threshold value can be used to avoid triggering suspect binding removal for transient events (for example, Diameter timeouts). This value specifies the number of Suspect Binding Removal Events that must occur for a given binding before the system will attempt to remove the binding by initiating a Session-Release RAR towards the Policy Client. This value is used when the Remove Suspect Binding Immediately value in the matched rule on the screen on the SOAM is set to No. |
Format: Text box Default: 3 Range: 2-10 |
| Session Integrity Options | ||
| Origin-Host and Origin-Realm for Policy DRA generated RAR messages | The selection option's Origin-Host and Origin-Realm will be used as the Origin-Host and Origin-Realm in the RAR messages constructed and sent by Policy DRA to the Policy Clients. | Format: Radio button Default: Local Host Range: Local Host or PCRF |
| * Maximum Query RAR Rate Per Session Server Group | This value specifies the maximum rate in messages per second at which a given Session SBR Server Group can send RAR message to Policy Clients for the purpose of auditing to determine if the session still exists. | Format: Text box Default: 50 Range: 50-5000 |
| * Maximum Attempts Per Query RAR | This value specifies the maximum number of times a given RAR will attempt to be sent to the Policy Client for purposes of querying for session existence when no response is received. If no response is received after the Maximum Attempts Per Query RAR has been reached, the Diameter session and associated binding keys are removed automatically. | Format: Text box Default: 12 Range: 1-12 |
| * Maximum Release RAR Rate Per Session Server Group | This value specifies the maximum rate in messages per second at which a given Session SBR Server Group can send RAR message to Policy Clients for the purpose of requesting removal of a session. Session removal is requested if a session or its associated binding keys cannot be successfully stored in the SBR database, or when a Suspect Binding is to be removed due to PCRF inaccessibility. | Format: Text box Default: 50 Range: 50-5000 |
| * Maximum Attempts Per Release RAR | This value specifies the maximum number of times a given RAR will attempt to be sent to the Policy Client for purposes of requesting removal of a session when no response is received. If no response is received after the Maximum Attempts Per Release RAR has been reached, the Diameter session and associated binding keys are removed automatically | Format: Text box Default: 12 Range: 1-12 |
| * Query RAR Queue Capacity Per Session Server Group | This value specifics the maximum number of RARs that can be queued in a given Session SBR Server Group for sending to Policy Clients for the purpose of querying for session existence. If a query RAR cannot be queued because the Pending Query RAR Capacity Per Session Server Group has been reached, the next pass of the session audit will attempt to queue the query RAR again. | Format: Text box Default: 1000 Range: 1000-50,000 |
| * Release RAR Queue Capacity Per Session Server Group | This value specifies the maximum number of RARs that can be queued in a given Session SBR Server Group for sending to Policy Clients for the purpose of requesting removal of sessions. If a release RAR cannot be queued because the Pending Release RAR Capacity Per Session Server Groups has been reached, another attempt to queue the release RAR will occur the next time a Suspect Binding Removal Even occurs for that binding. | Format: Text box Default: 100,000 Range: 100,000-500,000 |
