| Diameter Signaling Router Policy and Charging Application Release 8.2 E89000 |
|
 Previous |
 Next |
CCR
Credit-Control-Requests (CCRs) with CC-Request-Type set to UPDATE_REQUEST (2) received from online charging clients to update existing credit-control sessions are routed to the same online charging server that served the session initiation (for example, CCR-I) request.
OC-DRA determines whether session state is maintained based on session state configuration and message content. If session state is not maintained, OC-DRA routes the CCR-U without modification, expecting the online charging client to have set its Destination-Host AVP value to the hostname of the same online charging server that served the session initiation request. If session state is maintained, OC-DRA queries the Session SBR to retrieve and refresh the session state associated with the received Session-Id by sending a findAndRefreshOcSession stack event to the Session SBR. If session state is found, OC-DRA replaces the Destination-Realm and Destination-Host in the CCR-U with the realm and hostname of the online charging server obtained from the session state and forwards it to DRL for routing. If session state is not found or an SBR error is encountered, OC-DRA will determine how to handle the message based upon the user-configurable Session State Unavailable Action.
CCR-T
Credit-Control-Requests (CCRs) with CC-Request-Type set to TERMINATION_REQUEST (3) received from online charging clients to terminate existing credit-control sessions are routed to the same online charging server that served the session initiation request (for example, CCR-I).
OC-DRA determines whether session state is maintained based on session state configuration and message content. If session state is not maintained, OC-DRA routes the CCR-T without modification, expecting the online charging client to have set its Destination-Host AVP value to the hostname of the same OCS that served the session initiation request. If session state is maintained, OC-DRA queries the Session SBR to retrieve and remove the session state associated with the received Session-Id by sending a findAndRemoveOcSession stack event to the Session SBR. If session state is found, OC-DRA replaces the Destination-Realm and Destination-Host in the CCR-T with the realm and hostname of the online charging server obtained from the session state and forwards it to DRL for routing. If session state is not found or an SBR error is encountered, OC-DRA will determine how to handle the message based upon the user-configurable Session State Unavailable Action.
RAR
Re-Auth-Request (RARs) received from online charging servers to re-authorized existing credit-control sessions are routed to the online charging client that originated the session initiation request (for example, CCR-I).
OC-DRA determines whether session state is maintained on the behalf of the online charging server based on session state configuration and message content. If session state is not maintained, OC-DRA routes the RAR without modification, expecting the online charging server to have set its Destination-Host AVP value to the hostname of the online charging client that originated the session initiation request. If session state is maintained, OC-DRA queries the Session SBR to retrieve and refresh the session state associated with the received Session-Id by sending a findAndRefreshOcSession stack event to the Session SBR. If session state is found, OC-DRA replaces the Destination-Realm and Destination-Host in the RAR with the realm and hostname of the online charging client obtained from the session state and forwards it to DRL for routing. If session state is not found or an SBR error is encountered, OC-DRA will determine how to handle the message based upon the Session State Unavailable Action.
Routing In-Session Request Messages when Unable to Retrieve Session State
When OC-DRA cannot successfully process an in-session request (for example, CCR-U/T and RAR) due to its inability to retrieve session state associated with the received Session-Id from the SBR (either session state is not found or an SBR error is encountered), the operator is provided the flexibility to determine how to handle the message based upon the Session State Unavailable Action user-configurable setting.
When configured to forward route the message, OC-DRA forwards the in-session request message to DRL for routing using PRT. When configured to reject the message, OC-DRA abandons request message processing, generates and sends an Answer response using the Result-Code configured for error condition to the peer that initiated the Diameter transaction.
