TCP is still exposed to losing packets due to difference among access links and several sources of packet losses (e.g., congestion, wireless errors, and packet-reordering).
Particular attention is given to flow control, congestion control, error control, addressing for mobility, radio/logical link control, medium access control, digital modulation and link budgets.
Particular attention is given to flow control, congestion control, error control, addressing mobility, radio/logical link control, medium access control, digital modulation and link budgets.
Due to network congestion, random bit errors and packet losses may cause substantial quality degradation of the compressed video sequence.
Jitter can be caused due to transmission errors, congestion and with varying number of hops to the reach the destination.
Wireless channel congestion and/or noise errors [32] could be other possible causes for link breakages as well.
As a result, TCP DOOR is less accurate and responsive than a feed-back based approach, which can determine whether congestion or route errors occur in a responsive manner.
For this simulation, we use three TCP connections with 1% of packet reorder rate and the packet loss rate varies from 5, 7, and 9% due to network congestion and transmission errors.
It infers segment loss due to congestion and random error (i.e., halving Cwnd value), due to random errors (i.e., Cwnd × 4/5), or due to congestion (i.e., halving Cwnd value).
In addition, we design a mechanism called Explicit Loss Notification that can successfully distinguish between congestion and channel error-induced packet losses to substantially enhance end-to-end performance.
