| Diameter Signaling Router Policy and Charging Application Release 8.2 E89000 |
|
 Previous |
 Next |
Gy/Ro Credit-Control-Requests (CCRs) with CC-Request-Type AVP set to INITIAL_REQUEST (1) received from online charging clients to initiate credit-control sessions are load balanced across a collection of OCS servers connected to the DSR that can serve the Diameter request.
If OC-DRA is configured to operate in Single OCS Pool mode, OC-DRA removes the Destination-Host AVP from the received session initiation request (if present) and forwards it to DRL where PRT/RL will be used to route the session initiation request to one of the available OCS servers connected to the DSR.
If OC-DRA is configured to operate in Multiple OCS Pools mode, OC-DRA forwards the session initiation request without modification to DRL where PRT/RL will be used to load balance the session initiation request across a subset (for example, one of several pools) of available OCS servers connected to the DSR that can serve the request. In this mode, OC-DRA relies on RBAR to be invoked prior to OC-DRA invocation to populate the Destination-Host AVP and/or Destination-Realm AVP in session initiation requests. The hostname that RBAR uses to populate session initiation request's Destination Host AVP can be a real hostname or a virtual hostname that is used to represent a pool of OCS servers that can serve the request.
Subsequent Gy/Ro CCR messages with CC-Request-Type AVP set to UPDATE_REQUEST | TERMINATION_REQUEST within the session are routed to the same OCS that served the CCR-I either by means of destination-host routing or by the stateful mechanism
