A Traffic Throttle Point (TTP) is the logical entity that contains the information that is required to perform (Peer Node, Application ID) ETR throttling. It contains user-defined configuration attributes and dynamic throttling information received from upstream Peer Nodes via DOIC.
When the routing application selects a Peer Node or Connection from a Route Group (or selects a Peer Node for implicit Routing), it checks if a TTP exists for the selected Peer Node/Connection and Application ID in the Request message. If an active TTP exists, ETR throttling can be applied.
When routing a Request message, which has an associated Active TTP with DOIC enabled, upstream Peer Nodes are notified that the node supports DOIC and provides a list of DOIC Abatement Algorithms. When an OC-Supported-Features AVP is sent in a Request message, it saves the TTP which triggered sending the DCA in the PTR. When an Answer response is received from a Peer Node and a non-NULL TTP is saved in the PTR, the application checks for DOIC AVPs that might contain a new overload report (OLR) or contain changes to an existing overload report being processed. Otherwise, the application does not check for DOIC AVPs in Answer responses. Any valid requests from the upstream Peer Node to reduce traffic are stored in the TTP and immediately applied.
Information collected at the TTP level for DOIC throttling can be used to improve routing decisions.
You can perform these tasks on an Active System OAM (SOAM).
On the Traffic Throttle Points [Insert] page, you can add a new Traffic Throttle Point. See Adding Traffic Throttle Points.
If the maximum number of Traffic Throttle Points already exists in the system, an error message displays.
See Editing Traffic Throttle Points.
If no Name is selected, Edit is disabled.