Jitter management for packet data network backhaul of call data

Abstract

Managing packet data network jitter is disclosed. A first call data associated with a mobile network communication session is received. A second call data that is older than the first call data is dropped from a buffer if required to make room in the buffer for the first call data.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating elements of a typical GSM network.

FIG. 2 is a block diagram illustrating an embodiment of a mobile network with packet data network backhaul.

FIG. 3 is a block diagram illustrating an embodiment of a jitter management buffer.

FIG. 4 is a flow chart illustrating an embodiment of a process for pulling and transmitting call data packets/frames from a jitter management buffer.

FIG. 5 is a flow chart illustrating an embodiment of a process for receiving call data.

Claims

1. A method of managing packet data network jitter, comprising: receiving a first call data associated with a mobile network communication session; anddropping from a buffer a second call data that is older than the first call data if required to make room in the buffer for the first call data.

2. A method as recited in claim 1, wherein the first data and the second call data comprise packet data network packets.

3. A method as recited in claim 1, wherein the first data and the second call data comprise time division multiplexing frames.

4. A method as recited in claim 1, wherein the second call data that is older than the first call data if the second call data is associated with a first sequence number preceding a second sequence number associated with the first call data.

5. A method as recited in claim 1, wherein receiving the first call data includes associating a timestamp with the first call data.

6. A method as recited in claim 5, wherein the timestamp is used to determine whether the first call data or the second call data should be dropped.

7. A method as recited in claim 1, wherein if the first call data was received after another call data has already been transmitted with a first sequence number subsequent to a second sequence number of the first call data, the first call data is dropped and the second call data is not required to be dropped from the buffer.

8. A method as recited in claim 1, wherein the second call data is dropped based at least in part on a determination that the buffer is full.

9. A method as recited in claim 1, wherein the buffer is used to manage jitter associated with transporting the first call data via a packet data network.

10. A method as recited in claim 1, wherein the method is implemented on one or more of the following: a base transceiver station, a base station controller, and an aggregation gateway.

11. A method as recited in claim 1, wherein receiving the first call data includes extracting the first call data from a packet used to transport the first call data.

12. A method as recited in claim 1, further comprising placing the first call data in the buffer in a buffer position determined at least in part by using a sequence number associated with the first call data.

13. A method as recited in claim 12, wherein the sequence number is a Real-time Transport Protocol sequence number.

14. A method as recited in claim 1, wherein dropping from the buffer the second call data includes dropping a number of the oldest call data in the buffer, and the number of the oldest call data dropped is one more than the difference between a maximum depth associated with the buffer and a minimum depth associated with the buffer.

15. A method as recited in claim 1, wherein the buffer comprises a queue.

16. A method of managing packet data network jitter, comprising: waiting for a buffer to fill to a prescribed depth with call data; andtransmitting a next call data from the buffer.

17. A method as recited in claim 16, wherein if a prescribed transmission time has been reached, the next call data is transmitted without waiting for the buffer to be filled to the prescribed depth.

18. A method as recited in claim 16, wherein if call data filling the buffer are received in a sequence number order, a next call data that is next in the sequence number order is transmitted at a prescribed interval without waiting for the buffer to be filled to the prescribed depth.

19. A method as recited in claim 16, wherein the buffer is not filled beyond a maximum depth.

20. A method as recited in claim 16, wherein call data in the buffer are transmitted until the buffer is depleted.

21. A method as recited in claim 20, wherein the call data are transmitted at a prescribed interval.

22. A method as recited in claim 20, wherein when the buffer is depleted, call data in the buffer is not transmitted until the buffer has filled back to the prescribed depth.

23. A method as recited in claim 16, wherein after waiting for the buffer to fill to the prescribed depth with call data, call data in the buffer are analyzed to determine whether any call data in the buffer should be dropped.

24. A method as recited in claim 16, wherein a late call data in the refilled buffer is dropped from the buffer.

25. A method as recited in claim 24, wherein the late call data is determined to be late based at least in part on a determination that the late call data is associated with a sequence number preceding a sequence number of an already transmitted call data.

26. A system for managing packet data network jitter, comprising: a communication interface configured to receive a first call data associated with a mobile network communication session; anda processor configured to drop from a buffer a second call data that is older than the first call data if required to make room in the buffer for the first call data.

27. A system for managing packet data network jitter, comprising: a processor configured to wait for a buffer to fill to a prescribed depth with call data; anda communication interface configured to transmit a next call data from the buffer.

28. A computer program product managing packet data network jitter, the computer program product being embodied in a computer readable medium and comprising computer instructions for: receiving a first call data associated with a mobile network communication session; anddropping from a buffer a second call data that is older than the first call data if required to make room in the buffer for the first call data.

29. A computer program product managing packet data network jitter, the computer program product being embodied in a computer readable medium and comprising computer instructions for: waiting for a buffer to fill to a prescribed depth with call data; andtransmitting a next call data from the buffer.