Multiplex communications – Fault recovery – Bypass an inoperative channel
Reexamination Certificate
1997-03-31
2004-08-03
Kizou, Hassan (Department: 2662)
Multiplex communications
Fault recovery
Bypass an inoperative channel
C370S252000, C370S468000
Reexamination Certificate
active
06771594
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
The invention relates generally to the field of communications systems. More specifically, the invention relates to protocols for data networking.
2. Description of Related Art
In communications networks utilizing Internet Protocol (IP), real-time data, such as audio and/or video (A/V) data, is typically transmitted using the User Datagram Protocol (UDP). UDP is referred to as a “non-reliable” protocol since data “packets” lost during transmission are not retried or re-transmitted. If lost UDP data packets were re-transmitted at a later instant in time, the resulting A/V playback may be jumbled with frames of video or audio out of order. Retransmission or retries destroys the proper sequencing of audio and video information that is desired for audio and video transmissions, especially in videoconferencing or teleconferencing sessions. When the amount of packet loss is not too severe, A/V playback may pop or jitter with lost packets but will be audible and viewable. However, when the packet loss is too severe, the result may be inaudible, or confusing to the point where the afflicted recipient may prefer a delayed or semi-realtime transmission as a substitute for a severely degraded realtime transmission.
By contrast, Transmission Control Protocol (TCP), which also runs over IP, is a “reliable” protocol in that data packets are “guaranteed” to eventually reach their destination. The packets are numbered and sequenced when first transmitted so that upon a retry or retransmission, the packets can be ordered correctly. TCP is normally utilized for text binary file transfer and for transferring control messages which do not ordinarily need realtime transfer, and wherein it is important that transmitted packets eventually be received at their intended destination. The amount of packet loss for TCP packets is less critical than for UDP packets, since TCP is retry capable. If voice and A/V data were transmitted over TCP, the resulting realtime playback might be chaotic and out-of-order, especially where the quality of the network connection or routing is poor, since lost packets would be retried and arrive out-of-order.
Thus, there is a need to provide a mechanism which can reliably transmit A/V and other realtime data even when network connections are poor.
SUMMARY
The invention provides a method and apparatus for increasing the reliability of data communications based on network quality of service. The quality of service is determined to be inadequate based upon a certain threshold. If the quality of service is inadequate, data is routed through a reliable communications service.
REFERENCES:
patent: 5115429 (1992-05-01), Hluchyj et al.
patent: 5153877 (1992-10-01), Esaki et al.
patent: 5367523 (1994-11-01), Chang et al.
patent: 5430727 (1995-07-01), Callon
patent: 5461611 (1995-10-01), Drake, Jr. et al.
patent: 5488609 (1996-01-01), Hluchyj et al.
patent: 5742772 (1998-04-01), Sreenan
patent: 5896372 (1999-04-01), Auerbach et al.
LandOfFree
Reliable/non-reliable transmission of voice using TCP/UDP... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Reliable/non-reliable transmission of voice using TCP/UDP..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Reliable/non-reliable transmission of voice using TCP/UDP... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3271140