1. Feature Guide
  2. DSR Features and Functions
  3. Routing and Transaction Related Parameters in the DSR
  4. Congestion Control
  5. Diameter Overload Indication Conveyance
  6. DOIC Overload Reports

2.6.15.10.2 DOIC Overload Reports

Once the DSR starts sending OC-Supported-Features AVPs to the Reporting Node, the Reporting Node can start sending back DOIC Overload Reports (OLRs) requesting traffic abatement. The figure below gives a simple example of the Overload Report (OLR) mechanism.

Figure 2-28 DOIC Overload Reports Example


DOIC Overload Reports Example

When the Host decides that it needs to reduce the traffic being sent to it, it includes (piggybacks) an OC-OLR AVP in an answer to a request message that included the OC-Supported-Features AVP. The OC-OLR AVP includes:

  • Type of report (host, realm).
  • Report id (Sequence Number).
  • Length of time the report is valid.
  • Abatement algorithm specific AVPs.

The DSR abates traffic based on the data in the OLR for the duration given in the report, or until the report is effectively cancelled by the DOIC Reporting Node sending a report with 0 for time the report is valid.