Methods and apparatus for supporting transmission of streaming data

• US 7,447,775 B1
• Filed: 11/07/2003
• Issued: 11/04/2008
• Est. Priority Date: 11/07/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Lemon, Jonathan L., Yang, Zheng, Zhu, Liping, Zhang, Jin
• Primary Examiner(s): Vaughn, Jr.; William C.
• Assistant Examiner(s): Bayard; Djenane M
• Application Number:
  US10/703,825
• Time in Patent Office: 1,824 Days
• Field of Search: 709/226, 709/216, 709/227
• US Class Current: 709/226
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04N 21/23439 for generating different versions
• CPC Class Codes: H04N 21/25816 involving client authentication restricting access to computer systems by authenticating users using a predetermined code G06F21/33; cryptographic authentication protocols H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06
• CPC Class Codes: H04N 21/2585 Generation of a revocation list, e.g. of client devices involved in piracy acts
• CPC Class Codes: H04N 21/26216 involving the channel capacity, e.g. network bandwidth admission control, resource allocation in open networks H04L12/5692; flow control in packet networks H04L47/10; establishing a schedule or organising the servicing of application requests taking into account QoS H04L67/61
• CPC Class Codes: H04N 21/2665 Gathering content from different sources, e.g. Internet and satellite
• CPC Class Codes: H04N 21/643 Communication protocols network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP], H04L65/65
• CPC Class Codes: H04N 21/6437 Real-time Transport Protocol [RTP]
• CPC Class Codes: H04N 21/64738 Monitoring network characteristics, e.g. bandwidth, congestion level data switched network analysis H04L41/14; monitoring functioning in data switched networks H04L43/0817; flow control in packet networks H04L47/10

Abstract

A gateway application in a content engine multiplexes requests for real-time content to servers that, in turn, service the requests by streaming appropriate real-time content to requesting users. A software communication port of the content engine may be reserved to receive request messages from multiple client computers, at least two of which request streaming of real-time content according to different selected formats. After identifying client properties (e.g., a format for which to receive streaming real-time content) associated with the requests for real-time content, the gateway application identifies corresponding servers of the content engine to serve the real-time content according to the different selected formats. The gateway application forwards the requests for streaming of real-time content associated with the request messages to the corresponding servers which, in turn, satisfy the requests by streaming the requested real-time content to the client computers.

Claims

1. A method to support transmission of streaming data from a content engine coupled to a network, the method comprising:

from a requesting source communicating over the network, receiving a request message including a request for particular data from he content engine, the content engine including at least two different types of servers to service the request for particular data;

identifying client type properties associated with the received request message;

depending on the identified client type properties associated with the received request message, forwarding the request for particular data to one of the at least two different types of servers of the content engine to stream the particular data to the requesting source;

determining that the particular data associated with the received request message is stored in a local storage device associated with the content engine; and

from the server of the content engine to which the received request message is forwarded, transmitting the particular data associated with the request message to the requesting source by bypassing a software communication port on which the request message was originally received;

wherein bypassing the software communication port includes spoofing a corresponding server, to which the request is forwarded, into believing that the request for the particular data was received directly from a corresponding requesting source instead of being forwarded from a gateway application in the content engine that forwards the request to the corresponding server; and

wherein forwarding the request for particular data is supported at least in part by;

establishing a communication session between the gateway application and the corresponding server, the communication session including a software communication port associated with the gateway application through which the request message is forwarded to the corresponding server, and

maintaining an alias associated with the software communication port of the gateway application such that, when the corresponding server inquires as to an address of the gateway application forwarding the request to the corresponding server, a source other than the gateway application supplying the alias to the corresponding server to spoof the corresponding computer that the forwarded request was received directly from the requesting source instead of the gateway application.

2. A method as in claim 1 further comprising:

dedicating a single software communication port on which to receive multiple requests from multiple requesting sources requesting data from the at least two different types of servers in the content engine, each of at least two of the multiple requests including a unique format in which to receive streaming real-time data from the content engine.

3. A method as in claim 2, wherein the single software communication port is default RTSP (Real Time Streaming Protocol) port number 554 as specified by Request For Comment 2326.

4. A method as in claim 1, wherein identifying client type properties includes:

processing information in headers of the received request message to identify at least one of;

i) a user agent sending the request message,

ii) a destination of the received request message, and

iii) a media file type associated with requested data.

5. A method as in claim 1, wherein receiving the request message includes

receiving a request message according to a predetermined format, the method as in claim 1 further comprising:

applying a set of rules to the received request message via a gateway application that processes received request messages on behalf of the at least two different types of servers; and

based on application of the set of rules, rewriting at least a portion of the request message to include information for retrieving the particular data from one of the at least two different types of servers of the content engine.

6. A method as in claim 1 further comprising:

if the particular data is not stored in a local storage device associated with the content engine, redirecting the request message to another content source that provides the particular data to the corresponding requesting source.

7. A method as in claim 1 further comprising:

applying a filter to identify whether to deny servicing the request for the particular data and, if so, transmitting a message to the requesting source indicating that service has been denied.

8. A method as in claim 1 further comprising:

utilizing a modified operating system in the content engine to support providing an alias to a corresponding server, to which the request is forwarded, in response to the corresponding server inquiring as to a network address associated with an application from which the request is received.

9. A method as in claim 1 further comprising:

prior to receipt of the request message, storing the particular data associated with the request message in a local storage device associated with the content engine.

10. A method as in claim 1, wherein the request message includes a request for particular data that, when served to the requesting source from the content engine, is played back in real-time for a user.

11. A method as in claim 10, wherein the servers of the content engine run on a single operating system of a computer having access to stored files of raw data that are served to the user for playback in real-time.

12. A method as in claim 1 further comprising:

reserving the software communication port of the content engine to receive request messages from multiple client computers, at least two of which request streaming of real-time content according to different selected formats;

providing the gateway application in the content engine to process the request messages received on the software communication port, the gateway application identifying corresponding servers of the content engine to serve the real-time content according to the different selected formats;

forwarding requests for streaming of real-time content associated with the request messages to the corresponding servers; and

from the corresponding servers of the content engine, transmitting the appropriate real-time content from the content engine to the multiple client computers by bypassing the software communication port of the gateway application, wherein bypassing the software communication port includes spoofing the servers into believing that the requests for real-time content were received from corresponding client computers instead of being forwarded from the gateway application to the corresponding servers.

13. A method as in claim 1, wherein a first server is arranged to respond to requests for a first media file type;

wherein a second server is arranged to respond to requests for a second media file type; and

wherein forwarding the request for particular data includes;

(i) sending the request for particular data to the first server when the identified client type properties indicate that the client is associated with the first media file type, and alternatively (ii) sending the request for particular data to the second server when the identified client type properties indicate that the client is associated with the second media file type.

14. A computer system coupled to a network that supports transmission of streaming data, the computer system including:

a processor;

a memory unit that stores instructions associated with an application executed by the processor;

a communication interface that supports communication with other nodes of the physical network; and

an interconnect coupling the processor, the memory unit, and the communication interface, enabling the computer system to execute the application and perform operations of;

from a requesting source communicating over the network, receiving a request message including a request for particular data from the content engine, the content engine including at least two different types of servers to service the request for particular data;

identifying client type properties associated with the received request message;

depending on the identified client type properties associated with the received request message, forwarding the request for particular data to one of the at least two different types of servers of the content engine to stream the particular data to the requesting source;

determining that the particular data associated with the received request message is stored in a local storage device associated with the content engine; and

from the server of the content engine to which the received request message is forwarded, transmitting the particular data associated with the request message to the requesting source by bypassing a software communication port on which the request message was originally received;

wherein bypassing the software communication port includes spoofing a corresponding server, to which the request is forwarded, into believing that the request for the particular data was received directly from a corresponding requesting source instead of being forwarded from a gateway application in the content engine that forwards the request to the corresponding server; and

wherein forwarding the request for particular data is supported at least in part by;

establishing a communication session between the gateway application and the corresponding server, the communication session including a software communication port associated with the gateway application through which the request message is forwarded to the corresponding server, and

maintaining an alias associated with the software communication port of the gateway application such that, when the corresponding server inquires as to an address of the gateway application forwarding the request to the corresponding server, an operating system maintaining the alias supplies the alias to the corresponding server to spoof the corresponding computer that the forwarded request was received directly from the requesting source instead of the gateway application.

15. A computer system as in claim 14 that additionally performs operations of:

dedicating a single software communication port on which to receive multiple requests from multiple requesting sources requesting data from the at least two different types of servers in the content engine, each of at least two of the multiple requests including a unique format in which to receive streaming real-time data from the content engine.

16. A computer system as in claim 15, wherein the single software communication port is default RTSP (Real Time Streaming Protocol) port number 554 as specified by Request For Comment 2326.

17. A computer system as in claim 14, wherein identifying client type properties includes:

processing information in headers of the received request message to identify at least one of;

i) a user agent sending the request message,

ii) a destination of the received request message, and

iii) a media file type associated with requested data.

18. A computer system as in claim 14, wherein receiving the request message includes receiving a request message according to a predetermined format, the computer system as in claim 14 additionally performing operations of:

applying a set of rules to the received request message via a gateway application that processes received request messages on behalf of the at least two different types of servers; and

based on application of the set of rules, rewriting at least a portion of the request message to include information for retrieving the particular data from one of the at least two different types of servers of the content engine.

19. A computer system as in claim 14 that additionally performs operations of:

if the particular data is not stored in a local storage device associated with the content engine, redirecting the request message to another content source that provides the particular data to the corresponding requesting source.

20. A computer system as in claim 14 that additionally performs operations of:

applying a filter to identify whether to deny servicing the request for the particular data and, if so, transmitting a message to the requesting source indicating that service has been denied.

21. A computer system as in claim 14 that additionally performs operations of:

utilizing a modified kernel and corresponding stack in an operating system of the content engine to support providing an alias to a corresponding server, to which the request is forwarded, in response to the corresponding server inquiring as to a network address associated with an application from which the request is received.

22. A computer system as in claim 14 that additionally performs operations of:

prior to receipt of the request message, storing the particular data associated with the request message in a local storage device associated with the content engine.

23. A computer system as in claim 14, wherein the request message includes a request for particular data that, when served to the requesting source from the content engine, is played back in real-time for a user.

24. A computer system as in claim 23, wherein the servers of the content engine run on a single operating system of a computer having access to stored files of raw data that are served to the user for playback in real-time.

25. A computer system as in claim 14 that additionally performs the operations of:

reserving the software communication port of the content engine to receive request messages from multiple client computers, at least two of which request streaming of real-time content according to different selected formats;

providing the gateway application in the content engine to process the request messages received on the software communication port, the gateway application identifying corresponding servers of the content engine to serve the real-time content according to the different selected formats;

forwarding requests for streaming of real-time content associated with the request messages to the corresponding servers; and

from the corresponding servers of the content engine, transmitting the appropriate real-time content from the content engine to the multiple client computers by bypassing the software communication port of the gateway application, wherein bypassing the software communication port includes spoofing the servers into believing that the requests for real-time content were received from corresponding client computers instead of being forwarded from the gateway application to the corresponding servers.

26. A computer system as in claim 14, wherein a first server is arranged to respond to requests for a first media file type;

wherein a second server is arranged to respond to requests for a second media file type; and

wherein the computer system, when forwarding the request for particular data, is arranged to;

(i) send the request for particular data to the first server when the identified client type properties indicate that the client is associated with the first media file type, and alternatively (ii) send the request for particular data to the second server when the identified client type properties indicate that the client is associated with the second media file type.

27. A method for supporting transmission of streaming data from a content engine coupled to a network, the method comprising:

from multiple requesting sources communicating over the network, receiving request messages including corresponding requests for particular data from the content engine, the content engine including at least two different types of servers to service the requests for the particular data according to corresponding at least two different types of streaming formats;

executing a gateway application in the content engine to identify client type properties associated with each of the request messages;

depending on the identified client type properties associated with each of the request messages as identified by the gateway application, selectively forwarding the requests associated with each of the request messages to one of the at least two different types of servers to stream the particular data from the content engine to the requesting sources, the content engine being coupled to a storage device that stores at least one file of raw data content capable of being served according to the at least two different types of streaming formats;

determining that the particular data associated with each of the received request messages is stored in a local storage device associated with the content engine; and

from the server of the content engine to which each of the received request messages is forwarded, transmitting the particular data associated with each of the request messages to the requesting source by bypassing a software communication port on which each of the request messages was originally received;

wherein bypassing the software communication port includes spoofing a corresponding server, to which each of the requests is forwarded, into believing that each of the requests for the particular data was received directly from a corresponding requesting source instead of being forwarded from a gateway application in the content engine that forwards each of the requests to the corresponding server; and

wherein forwarding the request for particular data is supported at least in part by;

establishing a communication session between the gateway application and the corresponding server, the communication session including a software communication port associated with the gateway application through which each of the request messages is forwarded to the corresponding server, and

maintaining an alias associated with the software communication port of the gateway application such that, when the corresponding server inquires as to an address of the gateway application forwarding each of the requests to the corresponding server, a source other than the gateway application supplying the alias to the corresponding server to spoof the corresponding computer that the each of forwarded requests was received directly from the requesting source instead of the gateway application.

28. A computer system that supports transmission of streaming data from a content engine coupled to a network, the computer system including:

means for receiving a request message including a request for particular data from the content engine from a requesting source communicating over the network, the content engine including at least two different types of servers to service the request for particular data;

processing means for identifying client type properties associated with the received request message;

means for forwarding the request for particular data to one of the at least two different types of servers of the content engine to stream the particular data to the requesting source depending on the identified client type properties associated with the received request message;

means for determining that the particular data associated with the received request message is stored in a local storage device associated with the content engine; and

from the server of the content engine to which the received request message is forwarded, means for transmitting the particular data associated with the request message to the requesting source by bypassing a software communication port on which the request message was originally received;

wherein bypassing the software communication port includes spoofing a corresponding server, to which the request is forwarded, into believing that the request for the particular data was received directly from a corresponding requesting source instead of being forwarded from a gateway application in the content engine that forwards the request to the corresponding server; and

wherein means for forwarding the request for particular data is supported at least in part by;

means for establishing a communication session between the gateway application and the corresponding server, the communication session including a software communication port associated with the gateway application through which the request message is forwarded to the corresponding server, and

means for maintaining an alias associated with the software communication port of the gateway application such that, when the corresponding server inquires as to an address of the gateway application forwarding the request to the corresponding server, an operating system maintaining the alias supplies the alias to the corresponding server to spoof the corresponding computer that the forwarded request was received directly from the requesting source instead of the gateway application.

29. A computer program product including a computer-readable medium having instructions stored thereon for processing data information, such that the instructions, when carried out by a processing device, enable the processing device to perform the steps of:

from a requesting source communicating over the network, receiving a request message including a request for particular data from the content engine, the content engine including at least two different types of servers to service the request for particular data;

identifying client type properties associated with the received request message;

depending on the identified client type properties associated with the received request message, forwarding the request for particular data to one of the at least two different types of servers of the content engine to stream the particular data to the requesting source;

determining that the particular data associated with the received request message is stored in a local storage device associated with the content engine; and

from the server of the content engine to which the received request message is forwarded, transmitting the particular data associated with the request message to the requesting source by bypassing a software communication port on which the request message was originally received;

wherein bypassing the software communication port includes spoofing a corresponding server, to which the request is forwarded, into believing that the request for the particular data was received directly from a corresponding requesting source instead of being forwarded from a gateway application in the content engine that forwards the request to the corresponding server; and

wherein forwarding the request for particular data is supported at least in part by;

establishing a communication session between the gateway application and the corresponding server, the communication session including a software communication port associated with the gateway application through which the request message is forwarded to the corresponding server, and

maintaining an alias associated with the software communication port of the gateway application such that, when the corresponding server inquires as to an address of the gateway application forwarding the request to the corresponding server, a source other than the gateway application supplying the alias to the corresponding server to spoof the corresponding computer that the forwarded request was received directly from the requesting source instead of the gateway application.

30. A method to support transmission of streaming data, the method comprising:

from a requesting source communicating over a network, receiving a request message at a gateway application of a first content engine, the request message including a request for particular data, the first content engine including at least two different types of servers to service the request for particular data;

identifying properties associated with the received request message;

depending on the identified properties associated with the received request message, forwarding the request for particular data to a server of a second content engine, the second content engine including at least two different types of servers to stream data;

establishing a link between the gateway application of the first content engine and the server of the second content engine on which the request message is forwarded, the gateway application including a software communication port on which to forward the request message on the link; and

maintaining an alias associated with the software communication port of the gateway application such that, when the corresponding server at the second content engine inquires as to an address of the software communication port of the gateway application, an operating system maintaining the alias supplies the alias to the corresponding server to spoof the corresponding server at the second content engine that the forwarded request was received directly from the requesting source instead of the gateway application at the first content engine.