US2005180405A1PendingUtilityA1

Sub-packet insertion for packet loss compensation in voice over IP networks

Assignee: MITEL NETWORKS CORPPriority: Mar 6, 2000Filed: Apr 20, 2005Published: Aug 18, 2005
Est. expiryMar 6, 2020(expired)· nominal 20-yr term from priority
Inventors:Roger Bastin
H04L 9/40H04L 49/9023G10L 19/005H04M 1/2535H04L 1/00
37
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A method of compensating within a receiving endpoint for lost audio packets transmitted across an IP network, comprising the steps of storing a packet buffer of samples as a plurality of sub packets within a jitter buffer, inserting at least one interpolated sub packet between successive sub packets in the buffer, and playing out the sub packets from the buffer, such that only small portions of the jitter buffer are replayed at specific times to minimize the negative effects on voice quality. The inventive method inserts the replayed portions to compensate for packet loss in a way that results in only a relatively low processing burden.

Claims

exact text as granted — not AI-modified
1 . A method of compensating within a receiving endpoint for lost audio packets transmitted across an IP network, comprising the steps of: 
 storing a packet buffer of samples as a plurality of sub packets within a buffer;    inserting at least one interpolated sub packet between successive sub packets in said buffer; and    playing out said sub packets from said buffer.    
     
     
         2 . (canceled)  
     
     
         3 . (canceled)  
     
     
         4 . (canceled)  
     
     
         5 . The method of  claim 1 , further comprising the step of inserting interpolated sub packets between every other one of said sub packets in said buffer.  
     
     
         6 . (canceled)  
     
     
         7 . (canceled)  
     
     
         8 . (canceled)

Join the waitlist — get patent alerts

Track US2005180405A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.