Wire protocol for a media server system

• US 7,380,012 B2
• Filed: 07/16/2004
• Issued: 05/27/2008
• Est. Priority Date: 12/08/1995
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bolosky, William J., Rashid, Richard F., Fitzgerald, Robert P., Rie, Jan de, Levi, Steven P., Dowell, Craig
• Primary Examiner(s): Meky; Moustafa M
• Application Number:
  US10/893,785
• Publication Number:
  US 20050021700A1
• Time in Patent Office: 1,411 Days
• Field of Search: 709200-203, 709217-233
• US Class Current: 709/227
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/613 for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A wire protocol provides message formats for creating multiple network connections between a media server and a client. These multiple network connections may include a control link connection for passing control information and a data funnel connection for passing data of multiple media. The data funnel connection may be a multipoint-to-point connection that connects multiple data servers with the client. The protocol facilitates multiple requests being concurrently outstanding and asynchronous processing of requests. The protocol is designed to exist on top of a transport protocol layer.

Claims

1. In a computer network having a client on a first computer and a media server for storing data on a second computer, a method comprising the steps of:

providing a wire protocol that facilitates creation of connections between the media server and the client;

using the wire protocol to create a control connection between the media server and the client to facilitate exchange of control information between the media server and the client; and

using the wire protocol to create a data connection between the media server and the client to facilitate the exchange of data between the media server and the client at a rate substantially equal to a rate at which the client consumes the data,

wherein the media server is configured to;

receive one or more request messages from the client, each request message including a unique identifier, which serves as a basis for identifying each request; and

provide a response message to each of the one or more request messages by using the unique identifier as a mechanism to match the response message with one of the one or more request messages.

2. The method of claim 1 wherein the step of providing the wire protocol includes providing formats for messages in the wire protocol.

3. The method of claim 1, further comprising the step of using the control connection to exchange control information between the media server and the client.

4. The method of claim 1, further comprising the step of using the data connection to transfer data of multiple media between the media server and the client.

5. The method of claim 1, further comprising the step of using the wire protocol to cause data to read from the media server and forwarded to the client over the data connection.

6. The method of claim 1 wherein the step of using the wire protocol to create a control connection includes creating a bidirectional control connection that allows control information to flow from the client to the media server and from the media server to the client.

7. The method of claim 1, further comprising the steps of:

sending a request message for service over the control connection from the client to the media server; and

asynchronously processing the request message at the media server.

8. The method of claim 7, further comprising the step of asynchronously generating at the media server and sending over the control connection to the client a response message that responds to the request message.

9. The method of claim 1, wherein the unique identifier includes a playIncarnation Field which holds a play incarnation value.

10. In a distributed system having a media server on a first computer for supplying media output and a client on a second computer for requesting the media output from the media server, a method of interconnecting the media server and the client, comprising the steps of:

creating a control connection for enabling control information to pass between the media server and the client, and

creating a data funnel connection between the media server and the client for data to transferred between the media server and the client at a rate substantially equal to a rate at which the client consumes data,

wherein the media server is configured to;

receive one or more request messages from the client, each request message including a unique identifier, which serves as a basis for identifying each request; and

provide a response message to each of the one or more request messages by using the unique identifier as a mechanism to match the response message with one of the one or more request messages.

11. The method of claim 10 wherein the media output includes multiple media.

12. The method of claim 10 wherein the step of creating the control connection includes passing a message from the client to the media server requesting the control connection.

13. The method of claim 10 wherein the step of creating the data funnel connection includes passing a message from the client to the media server requesting the data funnel connection.

14. The method of claim 10 wherein the control connection is bidirectional.

15. The method of claim 10 wherein the data funnel connection is bidirectional.

16. The method of claim 10, wherein the unique identifier includes a playIncarnation Field which holds a play incarnation value.

17. In a distributed system having a media server for storing files holding data of multiple media, a client for requesting service from the media server, a control connection between the media server and the client for passing control information and a data connection for passing data between the media server and the client, a method comprising the steps of:

sending a read request message from the client to the media server over the control connection wherein said read request message requests that data in a file of multiple media data stored at the media server be read and input to the client,

sending a read request acknowledgment message from the media server to the client over the control connection to acknowledge the read request message; and

forwarding the requested data from the media server to the client over the data connection at a rate that is substantially equal to the rate at which the client consumes the data,

wherein the media server is configured to;

match the read request acknowledgment message with the read request message sent by the client by using a unique identifier, the unique identifier serving as a basis for identifying the read request message.

18. The method of claim 17 wherein the requested data is a single fixed size block of data.

19. The method of claim 17 wherein the requested data is an entire file of data.

20. The method of claim 17, wherein the unique identifier includes a playIncarnation Field which holds a play incarnation value.

21. In a distributed system having a media server storing files holding data of multiple media, a computer system comprising:

a control connection generator for creating a bidirectional control connection between the media server and the computer system to enable control information to be passed between the media server and the computer system; and

a data connection generator for creating a bidirectional data connection between the media server and the computer system to enable data to be passed between the media server and the computer system,

wherein the media server is configured to;

receive one or more request messages from the client, each request message including a unique identifier, which serves as a basis for identifying each request; and

provide a response message to each of the one or more request messages by using the unique identifier as a mechanism to match the response message with one of the one or more request messages.

22. The computer system of claim 21, further comprising a request generator for generating requests for service from the media server that are passed over the control connection wherein each request includes a unique identifier.

23. The computer system of claim 22 wherein the request generator further comprises a read request generator for generating requests to read data from the files of the media server so that the read data is output over the data connection to the computer system.

24. The computer system of claim 21 wherein the unique identifier includes a playIncarnation Field which holds a play incarnation value.