| Asset ID: |
1-71-2254898.1 |
| Update Date: | 2017-06-01 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2254898.1
:
Diameter Signaling Router (DSR) - How Policy & Charging Application (PCA) Manages the Generation of "Release" Re-Authentication Request (RAR) Messages?
| Related Items |
- Oracle Communications Diameter Signaling Router (DSR)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
|
In this Document
Created from <SR 3-14551190221>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.2.0 and later
Information in this document applies to any platform.
Goal
How Policy & Charging Application (PCA) Manages the Generation of "Release" Re-Authentication Request (RAR) Messages?
Solution
The PCA shall generate and send Diameter RAR messages to Policy Client servers under specific conditions. The PCA application shall generate and send two types of RAR Diameter messages, Query and Release.
“Release” RAR Diameter messages are generated by several parts of PCA functionality including the Enhanced Suspect Binding feature.
When the DSR initiates a RAR "Release" message towards the Policy Client servers (such as PCEFs) asking to remove the concerned session, it will not stop re-sending RARs until one of the below conditions is met:
- A RAA Answer message is received from the Policy Client server for the specific Diameter Session with a Result Code AVP value of 5002.
- The Session is ended via normal Diameter messaging( i.e. receipt of a CCR-T Diameter message).
- The number of times the “Release” RAR Diameter message is sent meets or exceeds the configured “Maximum Attempts Per Release RAR” values on the "PDRA Network-Wide Options" GUI which is by default configured to 12 attempts (from "Main Menu -> Policy and Charging -> Configuration -> Policy DRA -> Network-Wide Options" menu of the Active NOAM GUI)
Attachments
This solution has no attachment
