You may be configuring a new SMS Application or modifying an existing one in the MGR GUI under SMS Applications -> Applications
You wish to know what the Throughput AO Maximum and Throughput AO Committed Settings are meant for:
The RTR and the HUB can provide throughput control for all application-originating (AO) and application-terminating (AT) traffic. Throughput is controlled by the RTR and is configured in the HUB. Fine tuning of throughput control is recommended to avoid congestion of SMSC nodes or applications. The throughput control mechanism is designed to either limit the throughput and not let it go beyond a certain value(MAX AO Throughput) or to ensure that at least a certain throughput value is available (Committed).
1. Throughput AO Maximum
- This term is defined as: Maximum messages per second allowed from the application to the HUB (default 65,535). Our system will try to use the "Maximum" throughput if there are still spare resources to do so.
- This value is used in times of normalcy, when there is no congestion-like situation and all resources are working optimally. Here, the application is limited by the defined value of Throughput AO Maximum.
2. Throughput AO Committed
- This term is defined as: Committed messages per second allowed from the application to the HUB (default 65,535).Our system commits to support the "Committed" throughput.
- This value is used in times when the system is considered to be in a state of congestion. There could be various conditions that could cause congestion-like situations, such as: overwhelming traffic volume from different sources at the same time (AO,AT,MO,MT), Congestion on RTR /HUB/AMS, sctp congestion, congestion on links (m3ua congestion) etc.
- In this situation, Lithium would like to ensure that all applications send/receive at least a minimum throughput value, which is the defined value of Throughput AO Committed.
- In case this throughput is crossed, Lithium will not drop/reject these messages but rather delay their processing to the next second and will continue to do this, considering that the state of congestion will eventually be eased.
- If there is congestion on a system with multiple SMS Applications defined, then a subset of them may go beyond the committed throughput which is less than the maximum value, while the remainder are constrained at the committed throughput value. E.g. from the 5 SMS applications defined, it is possible that 3 of them go beyond committed but less than max, while 2 others are stopped at committed (and delay their processing of messages to the next second).