Method and apparatus providing media aggregation in a packet-switched network

• US 8,045,585 B2
• Filed: 06/09/2009
• Issued: 10/25/2011
• Est. Priority Date: 08/18/2000
• Status: Expired due to Term

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Kahane, Opher, Parnafes, Itzhak, Mohaban, Shai
• Primary Examiner(s): MILLS, DONALD L
• Application Number:
  US12/481,452
• Publication Number:
  US 20090245260A1
• Time in Patent Office: 868 Days
• Field of Search: None
• US Class Current: 370/473
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

Abstract

Techniques are described for aggregating multiple media packets to improve end-to-end bandwidth efficiency. The techniques include using an RTP aggregation protocol that is not sensitive to packet loss to aggregate multiple media packets under a single header. According to the RTP aggregation protocol, the single header for an aggregated media packet comprises a version field, a zero field, a sequence number field and a trunk ID field. The single header encapsulates the aggregated payload, which is an aggregation of Real-Time Protocol (RTP) segments. An RTP segment either has a compressed format or an uncompressed format. The uncompressed RTP segment includes the complete uncompressed RTP packet copied from the original User Datagram Protocol (UDP) packet. The compressed RTP segment includes the payload of the original RTP rather than the complete original RTP packet.

Claims

1. A method comprising:

receiving two or more Real Time Protocol (RTP) media packets associated with two or more concurrent media streams originating from one or more source end points, wherein each of the RTP media packets includes at least an Internet Protocol (IP) header, a User Datagram Protocol (UDP) header, a RTP header and an RTP payload;

converting the received two or more RTP media packets into a plurality of corresponding RTP segments by;

(1) removing the IP header and the UDP header from each of the RTP media packets, and (2) forming an RTP segment payload for each of the RTP media packets, where the RTP segment payload includes the RTP payload of the corresponding RTP media packet, and (3) adding an RTP segment header to each of the formed RTP segment payloads;

aggregating the plurality of RTP segments of the two or more RTP media packets into an aggregated media payload;

re-packetizing the aggregated media payload using a single aggregated header to form an aggregated media packet; and

forwarding the aggregated media packet to a next hop in the packet-switched network.

2. The method of claim 1, wherein forming an RTP media segment payload further comprises compressing an RTP header of each RTP media packet.

3. The method of claim 1, further comprising:

de-aggregating the aggregated media payload for one or more destination endpoints by separating the aggregating media payload into the plurality of RTP segments of the two or more RTP media packets;

restoring the two or more RTP media packets from the RTP segments by;

(1) removing the RTP segment header from each of the RTP segments, and (2) reconstructing the IP header and the UDP header for each of the RTP media packets, and (3) adding each of the reconstructed IP headers and the UDP headers to their corresponding RTP media packets;

decompressing an RTP header of each RTP media packet; and

sending each of the restored two or more RTP media packets to one of the one or more destination endpoints, wherein each RTP media packet corresponds to one of the two or more concurrent media streams.

4. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a context ID field indicating a session context ID for the compressed Real-Time Protocol segment.

5. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a compression bit indicating whether the Real-Time Protocol segment is compressed.

6. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a Real-Time Protocol header marker bit.

7. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a length field containing a length of a Real-Time Protocol payload of a Real-Time Protocol packet of the compressed Real-Time Protocol segment.

8. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a sequence number field carrying a Real-Time Protocol header sequence number.

9. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a timestamp field carrying a Real-Time Protocol header timestamp.

10. The method of claim 1, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on a compressed Real-Time Protocol segment format that comprises a padding field that aligns an end of the compressed Real-Time Protocol segment with a next four-byte boundary.

11. The method of claim 1, wherein the RTP segment payload further comprises the RTP header of the corresponding RTP media packet.

12. The method of claim 11, further comprising:

de-aggregating the aggregated media payload for one or more destination endpoints by separating the aggregating media payload into the plurality of RTP segments of the two or more RTP media packets;

restoring the two or more RTP media packets from the RTP segments by;

(1) removing the RTP segment header from each of the RTP segments, and (2) reconstructing the IP header and the UDP header for each of the RTP media packets, and (3) adding each of the reconstructed IP headers and the UDP headers to their corresponding RTP media packets; and

sending each of the restored two or more RTP media packets to one of the one or more destination endpoints, wherein each RTP media packet corresponds to one of the two or more concurrent media streams.

13. The method of claim 11, wherein aggregating the two or more RTP media packets comprises compressing one or more headers of each RTP media packet.

14. The method of claim 11, wherein re-packetizing the aggregated media payload further comprises forming the aggregated media packet based on an aggregated media packet format for each aggregated media packet wherein the aggregated media packet format comprises a version field indicating a version of the aggregation protocol.

15. The method of claim 11, wherein re-packetizing the aggregated media payload further comprises forming the aggregated media packet based on an aggregated media packet format for each aggregated media packet wherein the aggregated media packet format comprises a placeholder field that reserves packet space for future use.

16. The method of claim 11, wherein re-packetizing the aggregated media payload further comprises forming the aggregated media packet based on an aggregated media packet format for each aggregated media packet wherein the aggregated media packet format comprises a sequence number field that is incremented for each aggregated media packet and is used to detect media packet loss.

17. The method of claim 11, wherein re-packetizing the aggregated media payload further comprises forming the aggregated media packet based on an aggregated media packet format for each aggregated media packet wherein the aggregated media packet format comprises a trunk ID field that uniquely identifies a corresponding trunk.

18. The method of claim 11, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on an uncompressed Real-Time Protocol segment format that comprises a context ID field indicating a session context ID for the uncompressed Real-Time Protocol segment.

19. The method of claim 11, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on an uncompressed Real-Time Protocol segment format that comprises a compression bit indicating whether the uncompressed Real-Time Protocol segment is uncompressed.

20. The method of claim 11, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on an uncompressed Real-Time Protocol segment format that comprises a placeholder field for future use.

21. The method of claim 11, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on an uncompressed Real-Time Protocol segment format that includes a full length field containing a length of a Real-Time Protocol packet that corresponds to the uncompressed Real-Time Protocol segment.

22. The method of claim 11, wherein converting the received two or more RTP media packets into a plurality of corresponding RTP segments further comprises forming each RTP segment based on an uncompressed Real-Time Protocol segment format that comprises a padding field that aligns an end of the uncompressed Real-Time Protocol segment with a next four-byte boundary.

23. A method comprising:

receiving two or more Real Time Protocol (RTP) media packets associated with two or more concurrent media streams originating from one or more source end points, wherein each of the RTP media packets includes at least an Internet Protocol (IP) header, a User Datagram Protocol (UDP) header, a RTP header and an RTP payload;

converting the received two or more RTP media packets into a plurality of corresponding RTP segments by;

(1) removing the IP header and the UDP header from each of the RTP media packets, and (2) forming an RTP segment payload for each of the RTP media packets, where the RTP segment payload includes the RTP payload of the corresponding RTP media packet, and (3) adding an RTP segment header to each of the formed RTP segment payloads;

aggregating the plurality of RTP segments of the two or more RTP media packets into an aggregated media payload;

re-packetizing the aggregated media payload using a single aggregated header to form an aggregated media packet; and

forwarding the aggregated media packet to a next hop in the packet-switched network in response to a timer reaching a non-zero maximum allowed delay time value.

24. The method of claim 23, further comprising:

starting a count down for the maximum allowed delay time value when a first media packet arrives for aggregation; and

aggregating subsequent media packets that arrive before the maximum allowed delay time value is reached.

25. The method of claim 24, wherein the delay time value is variable according to user input.

26. The method of claim 24, wherein the RTP segment payload further comprises the RTP header of the corresponding RTP media packet.

27. A non-transitory computer-readable medium comprising one or more sequences of instructions, which sequences of instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving two or more Real Time Protocol (RTP) media packets associated with two or more concurrent media streams originating from one or more source end points, wherein each of the RTP media packets includes at least an Internet Protocol (IP) header, a User Datagram Protocol (UDP) header, a RTP header and an RTP payload;

converting the received two or more RTP media packets into a plurality of corresponding RTP segments by;

(1) removing the IP header and the UDP header from each of the RTP media packets, and (2) forming an RTP segment payload for each of the RTP media packets, where the RTP segment payload includes the RTP payload of the corresponding RTP media packet, and (3) adding an RTP segment header to each of the formed RTP segment payloads;

aggregating the plurality of RTP segments of the two or more RTP media packets into an aggregated media payload;

re-packetizing the aggregated media payload using a single aggregated header to form an aggregated media packet; and

forwarding the aggregated media packet to a next hop in the packet-switched network.

28. The non-transitory computer-readable medium of claim 27, wherein the RTP segment payload further comprises the RTP header of the corresponding RTP media packet.