Real Time transport protocol connector

• US 20030065804A1
• Filed: 10/03/2001
• Published: 04/03/2003
• Est. Priority Date: 10/03/2001
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Owerfeldt, Marc, Wong, Ivan, Bundschuh, Michael
• Application Number:
  US09/970,724
• Publication Number:
  US 20030065804A1
• Time in Patent Office: Days
• US Class Current: 709/231
• 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]
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]

Abstract

An invention is provided for a transport-independent RTP stack. The transport-independent RTP stack includes a transport-independent tasks module, which includes methods that are independent of an underlying transport layer. In communication with the transport-independent module is a connector module, which includes methods that are dependent on the underlying transport layer. In one aspect, the connector module includes data input and output methods, which can be utilized by the transport-independent tasks module to communicate with the underlying transport layer.

Claims

1. A transport-independent real-time transport protocol (RTP) stack, comprising:

a transport-independent tasks module, wherein the transport-independent tasks module includes methods that are independent of an underlying transport layer; and

a connector module in communication with the transport-independent module, wherein the connector module includes methods that are dependent on the underlying transport layer.

2. A transport-independent RTP stack as recited in claim 1, wherein the connector module includes data input and output methods.

3. A transport-independent RTP stack as recited in claim 2, wherein the data input and output methods are utilized by the transport-independent tasks module to communicate with the underlying transport layer.

4. A transport-independent RTP stack as recited in claim 3, wherein the data input and output methods include an RTP output stream method that returns an RTP output stream to a calling method.

5. A transport-independent RTP stack as recited in claim 4, wherein the data input and output methods include an RTP input stream method that returns an RTP input stream to a calling method.

6. A transport-independent RTP stack as recited in claim 3, wherein the data input and output methods include a real-time transport control protocol (RTCP) output stream method that returns an RTCP output stream to a calling method.

7. A transport-independent RTP stack as recited in claim 6, wherein the data input and output methods include an RTCP input stream method that returns an RTCP input stream to a calling method.

8. A real-time transport protocol (RTP) connector module, comprising:

an RTP output stream method that returns an RTP output stream to a calling method;

an RTP input stream method that returns an RTP input stream to a calling method;

a real-time transport control protocol (RTCP) output stream method that returns an RTCP output stream to a calling method; and

an RTCP input stream method that returns an RTCP input stream to a calling method.

9. AN RTP connector module as recited in claim 8, wherein the RTP connector module generates transport-independent input/output streams.

10. AN RTP connector module as recited in claim 9, wherein the transport input/output streams provide access to a particular type of underlying transport layer.

11. AN RTP connector module as recited in claim 10, wherein the RTP connector module is in communication with a transport-independent tasks module, wherein the transport-independent tasks module includes methods that are independent of the underlying transport layer.

12. AN RTP connector module as recited in claim 11, wherein the transport-independent tasks module processes the transport-independent input/output streams using transport-independent operations.

13. A transport-independent real-time transport protocol (RTP) stack, comprising:

a transport-independent tasks module having an RTP transmitter module and an RTP receiver module, wherein the RTP transmitter module and the RTP receiver module are independent of a first underlying transport layer; and

a connector module having an RTP output stream method in communication with the RTP transmitter module, and an RTP input stream method in communication with the RTP receiver module, wherein the RTP output stream method and the RTP input stream provide access to the first underlying transport layer.

14. A transport-independent RTP stack as recited in claim 13, wherein the RTP output stream method returns an RTP output stream to the RTP transmitter module.

15. A transport-independent RTP stack as recited in claim 14, wherein the RTP input stream method returns an RTP input stream to the RTP receiver module.

16. A transport-independent RTP stack as recited in claim 13, wherein the transport-independent tasks module further includes a real-time transport control protocol (RTCP) transmitter module and an RTCP receiver module.

17. A transport-independent RTP stack as recited in claim 16, wherein the RTCP transmitter module and the RTCP receiver module are independent of the first underlying transport layer.

18. A transport-independent RTP stack as recited in claim 17, wherein the connector module further includes an RTCP output stream method that returns an RTCP output stream to the RTCP transmitter module.

19. A transport-independent RTP stack as recited in claim 18, wherein the connector module further includes an RTCP input stream method that returns an RTCP input stream to the RTCP receiver module.

20. A transport-independent RTP stack as recited in claim 18, wherein the connector module c an be modified to operate utilizing a second underlying transport without modifying the transport-independent tasks module.