Section: D.4.1 Example of possible implementation
Content: This clause provides an example of a possible implementation of the enforcement of overload control between remote GTP-C entities, amongst other possible methods, considering the example network topology described in Figure D.4.1-1. Figure D.4.1-1: Example network topology The source GTP-C entity can apply message throttling according to the maximum of the overload reduction metric reported by the intermediate and target GTP-C entities, i.e. max (Intermediate_Overload-Metric, Target_Overload-Metric), for each of the path between the source and the target GTP-C entities. Each path is considered independently whilst performing the message throttling. Considering the following example overload condition for the topology above: Target_Overload-Metric = 30% IntermediateA_Overload-Metric = 10% IntermediateB_Overload-Metric = 20% IntermediateC_Overload-Metric = 40% Target_Terminated-Messages = 100 IntermediateA-Target_Messages = 20 IntermediateB-Target_Messages = 50 IntermediateC-Target_Messages = 30 the source GTP-C entity applies message throttling as follows: Source-IntermediateA_Messages = 14 (message throttling of 30% applied) Source-IntermediateB_Messages = 35 (message throttling of 30% applied) Source-IntermediateC_Messages = 18 (message throttling of 40% applied) Source-Target_Messages = 67 (the Target GTP-C entity receives 67 messages although it could have handled 70 messages in the overloaded condition).