Communication interface and method for robust header compression of data flows

• US 9,392,082 B2
• Filed: 09/12/2013
• Issued: 07/12/2016
• Est. Priority Date: 09/12/2013
• Status: Active Grant

• Current Assignee: NVIDIA Corporation
• Original Assignee: NVIDIA Corporation
• Inventors: De Smet, Bruno, Besson, Fabien, May-Weymann, Alexander
• Primary Examiner(s): WILSON, ROBERT W
• Application Number:
  US14/025,579
• Publication Number:
  US 20150071307A1
• Time in Patent Office: 1,034 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 65/762 at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A communication interface and method for efficient robust header compression (RoHC). One embodiment of the communication interface includes: (1) a data flow associated with a context ID (CID) and a data flow status indicator, and having packets, and (2) a robust header compression (RoHC) compressor configured to employ the CID to compress headers of the packets and to mark the CID as reusable by another data flow if the data flow status indicator indicates the data flow is terminated.

Claims

1. A communication interface, comprising:

a processor configured to generate data for a data flow having packets and associated with a context ID (CID) and a data flow status indicator, and provide a robust header compression (RoHC) compressor that employs said CID to compress headers of said packets and marks said CID as reusable by another data flow if said data flow status indicator indicates said data flow is terminated; and

a transmitter configured to transmit said packets.

2. The communication interface recited in claim 1 wherein said data flow is a real-time transport protocol (RTP) data flow.

3. The communication interface recited in claim 2 wherein said data flow status indicator is contained within an RTP control protocol (RTCP) data flow having RTCP packets.

4. The communication interface recited in claim 3 wherein said RoHC compressor further parses said RTCP packets to extract said data flow status indicator.

5. The communication interface recited in claim 1 wherein said data flow is a transmission control protocol (TCP) data flow having TCP packets.

6. The communication interface recited in claim 5 wherein said data flow status indicator includes a control bit-flag contained within said TCP packets.

7. The communication interface recited in claim 1 wherein said

processor is configured to execute an application that is operable to generate said data in said packets and provide

a protocol stack that packetizes said data into said packets.

8. A method of robust header compression (RoHC), comprising:

employing a context ID (CID) to compress packet headers of a data flow;

gaining access to a data flow status indicator; and

marking said CID as reusable if said data flow status indicator indicates said data flow is terminated, wherein said employing, said gaining and said marking are performed by a processor.

9. The method recited in claim 8 wherein said gaining access includes parsing packets of said data flow.

10. The method recited in claim 8 further comprising:

executing an application to generate data for said data flow; and

packetizing said data.

11. The method recited in claim 10 wherein said packetizing includes packing said data into real-time transport protocol (RTP) packets and RTP control protocol (RTCP) packets.

12. The method recited in claim 11 wherein said RTCP packets contain RTCP data and said gaining access is carried out before said packetizing.

13. The method recited in claim 10 wherein said packetizing includes packing said data into transmission control protocol (TCP) packets.

14. The method recited in claim 13 wherein said data flow status indicator is a control bit-flag in said TCP packets.

15. A modem, comprising:

a modem processor configured to provide a protocol stack that is operable to receive packets of a data flow, said packets having respective headers;

a robust header compression (RoHC) compressor that is operable to;

employ a context ID (CID) to compress said respective headers,

determine if said data flow is terminated based on a data flow status indicator associated with said data flow, and

mark said CID as reusable by another data flow if said data flow is terminated; and

a transmitter configured to transmit said packets.

16. The modem recited in claim 15 further comprising a real-time transport protocol/real-time transport control protocol (RTP/RTCP) stack operable to generate said packets from data generated by an application.

17. The modem recited in claim 16 wherein said data includes RTCP data to which said RoHC compressor is configured to gain access, said RTCP data including said data flow status indicator.

18. The modem recited in claim 15 further comprising a transmission control protocol (TCP) stack operable to generate said packets from data generated by an application, wherein said data and said packets include said data flow status indicator.

19. The modem recited in claim 18 wherein said RoHC compressor is configured to gain access to said data flow status indicator in said data.

20. The modem recited in claim 15 wherein said packets are receivable by said modem processor over a data bus coupled to an application processor configured to:

execute an application to generate data; and

employ a real-time transport protocol/real-time transport control protocol (RTP/RTCP) stack to generate said packets.

21. The modem recited in claim 20 further comprising a packet parser operable to extract said data flow status indicator from said packets received from said application processor.