Re: [Dime] OLR applicable for any/all applications

["Shishufeng (Susan)" <[e-mail]>]

Hi MCruz,

I don't see any use case at least in 3GPP for this. There is no more than one application between two nodes so far. And even the case is valid, it could be reached by multiple sending of the overload report per application, which could be seen as an optimization in the future if there is clear scenario for such an optimization.

Best Regards,
Susan

From: Maria Cruz Bartolome [mailto:[e-mail]]
Sent: Tuesday, December 03, 2013 4:43 PM
To: [e-mail]
Subject: [Dime] OLR applicable for any/all applications


Dear all,

There may be a need by a reporting node to request traffic reduction for all traffic, application independent, e.g. if an operator's network becomes severely overloaded, it may be of interest to signal directly general overload to the client.
In this case, since reacting node obtains affected application from the application message, we may need to extend OLR.

At least we got following options:



A)     Define a new optional AVP that could be included into OLR, like e.g.:

   OC-OLR ::= < AVP Header: TBD2 >

              < TimeStamp >

              [ Reduction-Percentage ]

              [ ValidityDuration ]

              [ ReportType ]

              [All applications]

            * [ AVP ]



B)      Extend  ReportTypes like e.g.:

   3  Destination-Host All Applications report.  Similar to Destination-Host report but it would apply to any application regardless the application message this report is received within.

   4  Realm (aggregated) All Applications report.  Similar to Realm report but it would apply to any application regardless the application message this report is received within.



I tend to prefer option A, but let me know your opinions and preferences.
Best regards
/MCruz