US 7,783,772 B2Grant
Session description message extensions
Issue Date:2010-08-24
•17 Claims
•5 Drawing Sheets
Abstract
Session description message extensions include information describing a multimedia presentation or a single media presentation. The session description message is typically sent from one device to another device to which the multimedia or single media presentation will be streamed. Several extensions are described that extend the information that can be included in the session description message.
Metadata
Assignee
- Microsoft Corporation
Inventor
- Anders E. Klemets
Application Information
Application Number:US 11/459,279
Filing Date:2006-07-21
Priority Date:2004-04-30
Art Unit:2446
Classifications
IPC:
G06F15/16
Patent Drawings (5 sheets)
Description
Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 10/836,141, filed Apr. 30, 2004, which is hereby incorporated by reference herein.
Technical Field
[0002] This invention relates to streaming media and data transfers, and particularly to session description message extensions.
Background
[0003] Content streaming, such as the streaming of audio, video, and/or text is becoming increasingly popular. The term “streaming” is typically used to indicate that the data representing the media is provided over a network to a client computer on an as-needed basis rather than being pre-delivered in its entirety before playback. Thus, the client computer renders streaming content as it is received from a network server, rather than waiting for an entire “file” to be delivered.
[0004] The widespread availability of streaming multimedia content enables a variety of informational content that was not previously available over the Internet or other computer networks. Live content is one significant example of such content. Using streaming multimedia, audio, video, or audio/visual coverage of noteworthy events can be broadcast over the Internet as the events unfold. Similarly, television and radio stations can transmit their live content over the Internet.
[0005] The Session Description Protocol (SDP), Network Working Group Request for Comments (RFC) 2327, April 1998, is a text-based format used to describe properties of a multimedia presentation, referred to as a “session”, and properties of one or more media streams contained within the presentation. SDP has been developed as an application level protocol intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. SDP can be used in accordance with other protocols, such as the Real-Time Streaming Protocol (RTSP) or the HyperText Transfer Protocol (HTTP), to describe and/or negotiate properties of a multimedia session used for delivery of streaming data.
[0006] SDP, however, is limited in the properties of the multimedia presentation that can be described. One solution to such limitations is to embed a different file header, such as an ASF (Advanced Streaming Format or Advanced Systems Format) file header, within an SDP message. Such a solution is described, for example, in U.S. Patent Application No. 2003/0236912, entitled “System and Method for Embedding a Streaming Media Format Header Within a Session Description Message”. However, embedding such a file header can create problems, such as requiring the recipient of such an SDP message to be able to parse and understand the different file header, and increasing the size of the SDP message that includes the different file header. Thus, it would be beneficial to have a way to overcome these limitations of SDP without requiring recipients to be able to parse and understand an embedded different file header (such as ASF).
Summary
[0007] Session description message extensions are described herein. These extensions extend the information that can be included in a session description message for streaming media.
[0008] In accordance with certain aspects, the session description message extensions include one or more of: a mutual exclusivity extension that specifies which of multiple media streams of a multimedia (or single media) presentation are mutually exclusive, a marker extension that specifies an index into a multimedia presentation, a script command extension that specifies data that is to be presented during playback of a multimedia presentation, a leaky bucket extension that specifies how much data of a multimedia presentation to buffer when playing the multimedia presentation at a particular bit rate, a caching information extension that specifies information about caching of a multimedia presentation, an encapsulation extension that specifies codec parameters for one or more of a plurality of different codecs, a bandwidth sharing extension that specifies media streams of a multimedia presentation that share bandwidth, or a stream prioritization extension that specifies which media streams of a multimedia presentation should have priority over which other media streams of the multimedia presentation.
Brief Description of the Drawings
[0009] The same numbers are used throughout the document to reference like components and/or features.
[0010] FIG. 1 illustrates an example network environment that can be used to stream media using the session description message extensions described herein.
[0011] FIG. 2 illustrates example client and server devices that can stream media content using the session description message extensions described herein.
[0012] FIG. 3 illustrates an example session description message format.
[0013] FIG. 4 is a flowchart illustrating an example process for extending a session description message for a multimedia presentation.
[0014] FIG. 5 illustrates a general computer environment, which can be used to implement the techniques described herein.
Detailed Description
[0015] Session description message extensions are described herein. A session description message includes information describing a multimedia presentation or a single media presentation. The session description message is typically sent from a server device to a client device to which the multimedia presentation will be streamed. Several extensions are described herein that extend the information that can be included in the session description message.
[0016] FIG. 1 illustrates an example network environment 100 that can be used to stream media using the session description message extensions described herein. In environment 100, multiple (a) client computing devices 102(1), 102(2), . . . , 102(a) are coupled to multiple (b) server computing devices 104(1), 104(2), . . . , 104(b) via a network 106. Network 106 is intended to represent any of a variety of conventional network topologies and types (including wired and/or wireless networks), employing any of a variety of conventional network protocols (including public and/or proprietary protocols). Network 106 may include, for example, the Internet as well as possibly at least portions of one or more local area networks (LANs).
[0017] Computing devices 102 and 104 can each be any of a variety of conventional computing devices, including desktop PCs, workstations, mainframe computers, Internet appliances, gaming consoles, handheld PCs, cellular telephones, personal digital assistants (PDAs), etc. One or more of devices 102 and 104 can be the same types of devices, or alternatively different types of devices.
[0018] Server devices 104 can make any of a variety of data available for streaming to clients 102. The term “streaming” is used to indicate that the data representing the media is provided over a network to a client device and that playback of the content can begin prior to the content being delivered in its entirety (e.g., providing the data on an as-needed basis rather than pre-delivering the data in its entirety before playback). The data may be publicly available or alternatively restricted (e.g., restricted to only certain users, available only if the appropriate fee is paid, etc.). The data may be any of a variety of one or more types of content, such as audio, video, text, animation, etc. Additionally, the data may be pre-recorded or alternatively “live” (e.g., a digital representation of a concert being captured as the concert is performed and made available for streaming shortly after capture).
[0019] A client device 102 may receive streaming media from a server 104 that stores the streaming media content as a file, or alternatively from a server 104 that receives the streaming media from some other source. For example, server 104 may receive the streaming media from another server that stores the streaming media content as a file, or may receive the streaming media from some other source (e.g., an encoder that is encoding a “live” event).
[0020] As used herein, streaming media refers to streaming one or more media streams from one device to another (e.g., from a server device 104 to a client device 102). The media streams can include any of a variety of types of content, such as one or more of audio, video, text, and so forth.
[0021] FIG. 2 illustrates example client and server devices that can stream media content using the session description message extensions described herein. Client device 102 includes a streaming media player 142 configured to access a streaming module 144 of server device 104. Media content including session description message(s) 146 is streamed from streaming module 144 to streaming media player 142, where the steaming media can be presented to a user of client device 102. The streaming media 146 can be streamed in accordance with different protocols, such as the Real-Time Streaming Protocol (RTSP) or the HyperText Transport Protocol (HTTP). Although not shown in FIG. 2 , one or more additional devices (e.g., firewalls, routers, gateways, bridges, etc.) may be situated between client device 102 and server device 104.
[0022] One or more session description messages are used to describe properties of the multimedia presentation streamed as streaming media 146. Different media formats or protocols can be used for such session description messages. An example of such a media format is the Session Description Protocol (SDP), Network Working Group Request for Comments (RFC) 2327, April 1998. In certain embodiments, the session description message discussed herein is a message in accordance with the SDP format described in RFC 2327.
[0023] Although different formats can be used to describe properties of the multimedia presentation, one or more session description messages are sent from streaming module 144 to streaming media player 142 that include identifier(s) of the properties. A single session description message may be sent by streaming module 144 for a particular multimedia presentation, or alternatively multiple session description messages may be sent. If multiple session description messages are sent, the multiple messages may include the same information, different information, or overlapping information.
[0024] A session description message includes, for example, one or more of: descriptions of each media stream available in the multimedia presentation (e.g., indicating the type of stream (e.g., video or audio), a bit-rate of each media stream, a language used in the stream, etc.); error correction information; security/authentication information; encryption information; or digital rights management (DRM) information; etc.
[0025] FIG. 3 illustrates an example session description message format. Although illustrated as a specific example in FIG. 3 , the session description message could have a format with fields or portions in different orders, or alternatively spread across different messages.
[0026] Session description message 180 includes a session level description portion 182 and zero or more media level description portions 184. Session level description portion 182 includes one or more fields having data that applies to the whole session and all media streams that are part of the session. Each media level description portion 182, on the other hand, includes one or more fields having data that applies only to a single media stream.
[0027] The data fields in media level description portion 182 describe properties for particular media streams. These properties may be in addition to properties described in session level description portion 182, or in place of properties described in session level description portion 182. For example, one or more properties in a particular media level description portion 182 may override, for the particular media stream associated with that particular media level description portion 182, properties identified in session level description portion 182.
[0028] Session description message 180, and the structure of message 180 is discussed in additional detail below specifically with respect to SDP. It is to be appreciated that these specific structures are only examples, and that the session description message can take different forms.
[0029] Session level description portion 182 begins with a particular field, referred to as the protocol version field. Similarly, media level description portions 184 each start with a particular field, referred to as a media name and transport address field. In certain embodiments, multiple fields of the same type may be included in a session description message (e.g., a single session description message may have two or more attribute fields).
[0030] Table I below illustrates example fields that may be included in session level description portion 182. Table I includes a name for each example field, an abbreviation or type for each example field, and a brief discussion of each example field. In certain embodiments, the protocol version field, the owner/creator and session identifier field, the session name field, and the time description field are required whereas all other fields in Table I are optional.
[0031]
| TABLE I | ||
|---|---|---|
| Name | Type | Description |
| protocol | v = | The version of the SDP. |
| version | ||
| origin | o = | The originator of the session (e.g., user name and |
| address of the user's host), plus a session id and a | ||
| session version number. | ||
| session name | s = | The name of the session. |
| session | i = | Information about the session. |
| information | ||
| URI of | u = | A pointer to additional information about the |
| description | session. | |
| email address | e = | Email address of person responsible for the |
| session. | ||
| phone number | p = | Phone number of person responsible for the |
| session. | ||
| connection | c = | Connection data describing the connection for the |
| information | session, such as network type, type of addressing | |
| being used, and a connection address. | ||
| bandwidth | b = | The proposed bandwidth to be used by the |
| information | session. | |
| time | See Table II below. | |
| description | ||
| time zone | z = | Specifies adjustment times and offsets to allow |
| adjustments | for daylight-saving time. | |
| encryption key | k = | Indicates the mechanism to be used to obtain an |
| encryption key for the session by external means, | ||
| or from an included encoded encryption key. | ||
| attribute | a = | Attribute of the session extending the SDP. |
[0032] Table II below illustrates the time description field in additional detail. Table II includes a name for each field in the time description field, an abbreviation or type for each field in the time description field, and a brief discussion of each field in the time description field. The time the session is active field is required whereas the zero or more repeat times field is optional.
[0033]
| TABLE II | ||
|---|---|---|
| Name | Type | Description |
| time the session is active | t = | The start and stop times for the session. |
| zero or more repeat | r = | Specifies repeat times for the session. |
| times | ||
[0034] Table III below illustrates example fields that may be included in a media level description portion 184. Table III includes a name for each example field, an abbreviation or type for each example field, and a brief discussion of each example field. In certain embodiments, the media announcement field is required whereas all other fields in Table III are optional.
[0035]
| TABLE III | ||
|---|---|---|
| Name | Type | Description |
| media | m = | The media type of the media stream, the transport |
| announcement | port to which the media stream will be sent, the | |
| transport protocol for the media stream, and the | ||
| media format(s) for the media stream. | ||
| media title | i = | Information about the media stream (e.g., a label |
| for the media stream). | ||
| connection | c = | Connection data describing the connection for the |
| information | media stream, such as network type, type of | |
| addressing being used, and a connection address. | ||
| bandwidth | b = | The proposed bandwidth to be used by the media |
| information | stream. | |
| encryption key | k = | Indicates the mechanism to be used to obtain an |
| encryption key for the media stream by external | ||
| means, or from an included encoded encryption | ||
| key. | ||
| attribute | a = | Attribute of the media stream extending the SDP. |
[0036] In certain embodiments, the session description message extensions discussed herein are included as attribute fields in the session level description 182 and/or one or more media level descriptions 184.
[0037] FIG. 4 is a flowchart illustrating an example process 200 for extending a session description message for a multimedia presentation. Process 200 may be performed in software, firmware, hardware, or combinations thereof. Process 200 is typically performed by a source of the multimedia presentation (e.g., an encoder device that is generating the multimedia presentation). For stored multimedia presentations, the information included in the session description message extensions is typically also stored along with the multimedia presentation or alternatively elsewhere. When the multimedia presentation is to be retrieved and streamed to a client device, the stored information can be retrieved and the session description message, with extensions, generated. For live multimedia presentations, the information included in the session description message is added to the session description message (e.g., by a human user or automatically by a computing device) at the beginning of the multimedia presentation and/or during the multimedia presentation (e.g., information may be added to or changed in the session description message as the live multimedia presentation changes).
[0038] Initially, the information to be included in the session description message is identified (act 202). This information can be identified in one or more different manners. One manner in which this information can be identified is retrieval from a file or record. In certain embodiments, at least some of the information is stored in a file or record associated with the multimedia presentation that the session description message is to describe. This file or record is accessed in act 202 to retrieve the information stored therein.
[0039] Another manner in which this information can be identified is receipt from a human user. In certain embodiments, at least some of the information is received from a human user. These user inputs are used in act 202 as at least some of the information to be included in the session description message.
[0040] Another manner in which this information can be identified is automatic detection. In certain embodiments, at least some of the information can be identified automatically by a computing device by analyzing the source of the multimedia presentation or the multimedia presentation itself. This automatically detected information is used in act 202 as at least some of the information to be included in the session description message.
[0041] The extensions to be added to the session description message in order to include all of the identified information are then identified (act 204). These extensions can be identified in different manners. One manner in which these extensions can be identified is automatically based on the identified information. In this manner, given the information that is identified, the particular extensions to be used to include that information in the session description message are automatically identified. For example, a table or record mapping information to extension may be accessed, the device performing the automatic configuration may be configured or programmed with the appropriate extensions for particular information, and so forth.
[0042] Another manner in which these extensions can be identified is identification of the extension information with the information itself. For example, when the information is identified in act 202, the information may also include the identification of which extension to use to include the information in the session description message.
[0043] The session description message is then generated including the extensions identified in act 204 and the information identified in act 202 (act 206). Once generated, the session description message can be sent to the client device to inform the client device of the information describing the multimedia presentation associated with the session description message.
[0044] A wide variety of information can be included in the session description message extensions. In certain embodiments, these extensions include information that would also be included in an ASF file header associated with the multimedia presentation. By using the session description message extensions to include such information, the ASF file header would not need to be communicated to the client device. This alleviates the need for the client device to be able to understand the ASF file header, can reduce the size of the session description message by not embedding the entirety of the ASF file header in the session description message, and can eliminate the need to generate an ASF file header in situations where an ASF file header has not already been generated.
[0045] It should be noted that the session description message extensions discussed herein are separate from the ASF file header. These session description message extensions are defined as being separate from any ASF file header (i.e., these session description message extensions are not simply part of an ASF file header that is embedded in a session description message). These session description message extensions can also be used in situations where there is no ASF file header associated with the multimedia presentation.
[0046] Table IV below is a summary of several extensions that can be included in a session description message. In certain embodiments, each of these extensions are added using an attribute field of the session description. The discussions of these extensions following Table IV indicate whether these extensions are typically found in session level description 182 or media level description 184, although alternatively these extensions could be located in either session level description 182 or media level description 184.
[0047]
| TABLE IV | |
|---|---|
| Name | Description |
| Mutual | Specifies whether media streams are mutually exclusive. |
| Exclusivity | |
| Marker | User-friendly indexes into the media stream(s). |
| Script | Specifies text (or other data) that is to be displayed or an |
| Command | identifier of a web page that should be displayed at a |
| particular time during playback of the media stream(s). | |
| Leaky Bucket | When playing back variable bit-rate content at a constant |
| bit-rate, specifies how much data of the media stream(s) | |
| the client should buffer. | |
| Caching | Specifies information about caching of the media |
| Information | stream(s), such as whether the stream(s) can be |
| cached, how long the stream(s) are | |
| considered fresh, etc. | |
| RTP | Specifies codec initialization parameters generically |
| Encapsulation | across a broad variety of codecs for data |
| transmitted over RTP. | |
| Bandwidth | Specifies streams that share bandwidth so that the |
| Sharing | maximum bandwidth of the set of specified streams is |
| less than the sum of the maximum bandwidths of the | |
| individual streams. | |
| Stream | Specifies which streams should have priority over which |
| Prioritization | other streams (e.g., which streams should or should not |
| be dropped in the event of network congestion). | |
[0048] Each of the extensions included in the summary of Table IV are described in the following in additional detail. Various example syntaxes are discussed below for the various extensions. It is to be appreciated that these are only examples, and that other syntaxes can alternatively be used. For example, the parameters or the order of the parameters may be changed. By way of another example, the names of specific attributes may be changed (e.g., the name for the mutual exclusivity attribute discussed below may be changed to something other than “a=group”).
[0049] It should be noted that references are made herein to identifications of particular media streams. These identifications can be made at different times. In certain embodiments, identifiers of the media streams are created by an author or designer (or alternatively automatically) when the media stream is encoded (e.g., for a live broadcast) or when the media stream is stored (e.g., as an ASF file). In other embodiments, identifiers of the media streams are created when the streaming of the multimedia presentation (or single media presentation) from the server device begins.
[0050] The identifiers themselves can be generated in any of a variety of manners. In certain embodiments, the identifiers are identifiers of RTP sessions. In these embodiments, individual media streams are streamed from the server device to the client device using the Realtime Transport Protocol (RTP) as described in Network Working Group Request for Comments (RFC) 3550, July 2003. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. Each media stream is streamed over a different RTP session. These RTP sessions can be assigned numbers in different manners, such as by using the “a=mid:” attribute as described in the Grouping of Media Lines in the Session Description Protocol (SDP) Network Working Group Request for Comments (RFC) 3388, December 2002. In other embodiments RTP sessions can be assigned numbers in different manners, such as by using an “a=stream:” attribute or some other attribute. Alternatively, the identifiers may be generated by simply using the same identifiers as the ASF Stream IDs, as assigned in the ASF file header.
[0051] Mutual Exclusivity
[0052] The mutual exclusivity extension specifies whether media streams are mutually exclusive. In certain implementations, streams are mutually exclusive based on bit rate and language. For example, a multimedia presentation may have multiple streams of the same content (e.g., audio or video) that are encoded at different bit rates. Only one of these streams at a time, having the desired bit rate, should be selected for streaming to the client device. By way of another example, a multimedia presentation may have multiple streams of the same content (e.g., audio) that are in different languages. Only one of these streams at a time, in the desired language, should be selected for streaming to the client device.
[0053] In certain embodiments, the parameters for the mutual exclusivity extension are obtained by accessing the Bitrate Mutual Exclusion Object or Advanced Mutual Exclusion Object in an ASF file header associated with the multimedia presentation. The parameters identified in the ASF file header are retrieved and used as the parameters of the mutual exclusivity extension. If there are multiple Bitrate Mutual Exclusion Objects and/or Advanced Mutual Exclusion Objects in the ASF file header, then a separate mutual exclusivity extension is included in the session description message for each of those multiple Bitrate Mutual Exclusion Objects and/or Advanced Mutual Exclusion Objects.
[0054] The mutual exclusivity extension is included in the session level description using an “a=group” attribute. The syntax for the “a=group” attribute is defined as follows:
[0055] a=group:ExclusionType StreamNumbers
[0056] The ExclusionType parameter can be set to different values to indicate the type of the mutual exclusivity. For example, the ExclusionType parameter may be set to “MBR” to indicate that the streams are mutually exclusive based on bit rate, but set to “LANG” to indicate that the streams are mutually exclusive based on language. In certain embodiments, when basing the mutual exclusivity extension on the information in an ASF file header, if the value of the “Exclusion Type” GUID in the Bitrate Mutual Exclusion Object or Advanced Mutual Exclusion Object of the ASF file header is ASF_Mutex_Language then the ExclusionType parameter is set to “LANG”, and if the value of the “Exclusion Type” GUID in the Bitrate Mutual Exclusion Object or Advanced Mutual Exclusion Object of the ASF file header is ASF_Mutex_Bitrate then the ExclusionType parameter is set to “MBR”.
[0057] The StreamNumbers parameter contains a list of streams that the mutual exclusion applies to. These streams are identified, for example, by their RTP sessions. In certain embodiments, when basing the mutual exclusivity extension on the information in an ASF file header, for each stream in the “Stream Numbers” field of the Bitrate Mutual Exclusion Object or Advanced Mutual Exclusion Object of the ASF file, the number assigned to the corresponding RTP session is added to the list of streams in the StreamNumbers parameter.
[0058] Marker
[0059] The marker extension specifies user-friendly indexes into the media stream(s). These user-friendly indexes are intended to be easily understood by human readers. The marker extension is included in the session level description using an “a=marker” attribute.
[0060] In certain embodiments, the parameters for the marker extension are obtained by accessing the Marker Object in an ASF file header associated with the multimedia presentation. The parameters identified in the ASF file header are retrieved and used as the parameters of the marker extension. If there are multiple Markers in the ASF file header, then a single marker extension can be used to identify all of the multiple Markers. Alternatively, a separate marker extension may be included in the session description message for each of those multiple Markers.
[0061] The syntax for the “a=marker” attribute is defined as follows:
[0062] a=marker:name time; desc
[0063] The name parameter specifies the name of the marker being specified by the marker extension. In certain embodiments, when basing the marker extension on the information in an ASF file header, the value of “Name” in the Marker Object of the ASF file header is UTF-8 encoded and used as the value of the name parameter in the marker extension.
[0064] The time parameter specifies the presentation time of the marker. In certain embodiments, when basing the marker extension on the information in an ASF file header, the value of “Presentation Time” in the Marker Object of the ASF file header is used as the value of the time parameter in the marker extension. In certain implementations, if the ASF file header specifies an amount of time to buffer data before starting to play the multimedia presentation (e.g., in the “Preroll” field of the File Properties Object), then that specified amount of time is subtracted from the value of “Presentation Time” in the Marker Object of the ASF file header, and the resulting difference is used as the value of the time parameter in the marker extension.
[0065] The desc parameter specifies the user-friendly index that is to be presented to the user as the marker. In certain embodiments, when basing the marker extension on the information in an ASF file header, the value of “Marker Description” in the Marker Object of the ASF file header is UTF-8 encoded and used as the value of the desc parameter in the marker extension.
[0066] The “a=marker” attribute may optionally include time and desc parameters for multiple markers. Each parameter pair is separated from the previous parameter pair by a space character (or alternatively by some other character(s), such as a comma, colon, period, etc.).
[0067] Script Command
[0068] The script command extension specifies text (or other data) that is to be displayed at a particular time during playback of the media stream(s), or specifies an identifier of a web page that should be displayed (e.g., within a web browser) at a particular time during playback of the media stream(s). The script command extension is included in the session level description using an “a=script” attribute.
[0069] In certain embodiments, the parameters for the script command extension are obtained by accessing the Script Command Object in an ASF file header associated with the multimedia presentation. The parameters identified in the ASF file header are retrieved and used as the parameters of the script command extension. If there are multiple Commands in the ASF file header, then a single script command extension can be used to identify all of the multiple Commands. Alternatively, a separate script command extension may be included in the session description message for each of those multiple Commands.
[0070] The syntax for the “a=script” attributes is defined as follows:
[0071] a=script:type time; command
[0072] The type parameter specifies the name of a type of command being specified by the script command extension. In certain embodiments, when basing the script command extension on the information in an ASF file header, the value of “Command Type Name” in the Script Command Object of the ASF file header is UTF-8 encoded and used as the value of the type parameter in the script command extension. If a Script Command Object in the ASF file header can contain multiple “Command Type Fields”, then a separate script command extension is used for each such field.
[0073] The time parameter specifies the presentation time of the command. In certain embodiments, when basing the script command extension on the information in an ASF file header, the value of “Presentation Time” in the Script Command Object of the ASF file header is used as the value of the time parameter in the script command extension. In certain implementations, if the ASF file header specifies an amount of time to buffer data before starting to play the multimedia presentation (e.g., in the “Preroll” field of the File Properties Object), then that specified amount of time is subtracted from the value of “Presentation Time” in the Script Command Object of the ASF file header, and the resulting difference is used as the value of the time parameter in the script command extension.
[0074] The command parameter specifies the text (or other data) that is to be displayed or the identifier of the web page(s) that should be displayed (e.g., within a web browser). In certain embodiments, when basing the script command extension on the information in an ASF file header, the value of “Command Name” in the Script Command Object of the ASF file header is UTF-8 encoded and used as the value of the command parameter in the script command extension.
[0075] The “a=script” attribute may optionally include time and command parameters for multiple script commands. Each parameter pair is separated from the previous parameter pair by a space character (or alternatively by some other character(s), such as a comma, colon, period, etc.).
[0076] Leaky Bucket
[0077] The leaky bucket extension specifies, when playing back variable bit-rate content at a constant bit-rate, how much data of the media stream(s) the client should buffer. A leaky bucket refers to a buffer that empties at a constant positive leak rate, into which bits can be dumped at irregular times and in irregular amounts. A leaky bucket is specified by its leak rate (e.g., in bits per second) and its size or capacity (e.g., in bits). The leaky bucket extension is included in the session level description using an “a=bucketinfo” attribute.
[0078] In certain embodiments, the parameters for the leaky bucket extension are obtained by accessing the Extended Content Description Object in an ASF file header associated with the multimedia presentation. The Extended Content Description Object includes a name-value pair named “ASFLeakyBucketPairs”. The value of the “ASFLeakyBucketPairs” name-value pair is the leaky bucket information, which is used as the parameters for the leaky bucket extension. Alternatively, the parameters for the leaky bucket extension may come from elsewhere in an ASF file header, such as the Extended Stream Description Object. If there are multiple such Extended Content Description Objects having “ASFLeakyBucketPairs” name-value pairs (and/or multiple such “ASFLeakyBucketPairs” name-value pairs within an Extended Content Description Object) in the ASF file header, then a single leaky bucket extension can be used to identify all of the multiple “ASFLeakyBucketPairs” name-value pairs. Alternatively, a separate leaky bucket extension may be included in the session description message for each of those multiple Extended Content Description Objects or multiple “ASFLeakyBucketPairs” name-value pairs.
[0079] The syntax for the “a=bucketinfo” attributes is defined as follows:
[0080] a=bucketinfo:R1;B1 R2;B2
[0081] The R1 parameter specifies the bit rate (the leak rate) for the first leaky bucket, and the B1 parameter specifies the size (e.g., in milliseconds) of the first leaky bucket. The R2 parameter specifies the bit rate (the leak rate) for the second leaky bucket, and the B2 parameter specifies the size of the second leaky bucket. Although only two leaky buckets are shown in the syntax definition, the “a=bucketinfo” attribute may provide parameter pairs Rx;Bx for an unlimited number (x) of leaky buckets. Each parameter pair is separated from the previous pair by a space character (or alternatively some other character, such as a comma, colon, period, etc.).
[0082] In certain embodiments, when basing the leaky bucket extension on the information in an ASF file header, the value of the “ASFLeakyBucketPairs” name-value pair in the Extended Content Description Object of the ASF header file is used as the value of the R and B parameters in the leaky bucket extension. The first part of the “Descriptor Value” (e.g., the first four bytes) specifies the bit rate for the bucket (the R parameter), while the second part of the “Descriptor Value” (e.g., the second four bytes) specifies the size for the bucket (the B parameter).
[0083] Caching Information
[0084] The caching information extension specifies information about caching of the media stream(s), such as whether the stream(s) can be cached, how long the stream(s) are considered fresh, and so forth. In certain embodiments, the caching information is determined based on the caching policy implemented by the server device (e.g., server device 104). The caching information extension is included in the session level description using an “a=cachectrl” attribute.
[0085] The syntax of the “a=cachectrl” attribute is as follows:
[0086] a=cachectrl:Rights
[0087] The Rights parameter is one or more directives, separated by space characters (or alternatively some other characters, such as commas, periods, semicolons, colons, etc.). A directive can be either a name-value pair, where the name and the value are separated by an “=” character (or alternatively some other character), or a single “name”, without a “value”.
[0088] Different directives can be included in the Rights parameter. In certain embodiments, these directives include a no-cache directive, a no-splitting directive, and an expiration directive.
[0089] The no-cache directive is defined as “no-cache”, and indicates to the client device, as well as any intermediate devices between the server and client devices, that the device is not allowed to cache the media stream(s) for playback at a later time.
[0090] The no-splitting directive is defined as “no-splitting”, and indicates to the client device, as well as any intermediate devices between the server and client devices, that the device is not allowed to rebroadcast or redistribute the content. Splitting of streaming media content refers to the same content being communicated to multiple clients. The no-splitting directive indicate that such splitting is not allowed.
[0091] The “a=cachectrl” attribute may also include an expiration directive, which is a name-value pair that is defined as follows:
[0092] expiration=Timeout
[0093] The Timeout parameter specifies when cached copies of the media stream(s) are considered stale (no longer fresh). The Timeout parameter may specify a period of time (e.g., a number of seconds, minutes, days, etc.) until the cached copies are considered stale, or alternatively may specify a particular date and/or time (e.g., Apr. 15, 2004 at 3:00 pm) when the cached copies become stale. In certain embodiments, a device with a cached copy is not allowed to use stale media stream(s). In other embodiments, the device can use a stale cached copy of a media stream(s), but the device should attempt to determine if a newer version of the media stream(s) is available, and use that newer version instead if possible.
[0094] If the expiration directive is not included, then the media stream(s) do not become stale. If the “a=cachectrl” attribute is not included, then caching and splitting of the media stream(s) is allowed, and cached content does not become stale.
[0095] RTP Encapsulation
[0096] The RTP encapsulation extension specifies codec initialization parameters generically across a broad variety of codecs for data transmitted over RTP. A variety of different codecs can be used with RTP, and these different codecs oftentimes have their own encapsulation schemes and their own initialization parameters. The RTP encapsulation extension allows the same syntax (which is the RTP encapsulation extension) to describe the properties of a variety of different codecs, thereby alleviating the need for many different syntaxes to describe many different codes. The RTP encapsulation extension is included in the media level description using an “a=fmtp” attribute.
[0097] a=fmtp:pt MIME config=config-info
[0098] The pt parameter is the RTP payload type number, which identifies the format or type of the RTP payload. In certain implementations, any number between 0 and 127 is valid.
[0099] The MIME parameter is an identifier of the codec used in the media stream. In certain embodiments, the MIME parameter is a MIME (Multipurpose Internet Mail Extensions) type that is formed according to the rules in “WAVE and AVI Codec Registries”, Network Working Group Request for Comments (RFC) 2361, June 1998. In other embodiments, the MIME parameter can take the following form:
[0100] application/vnd.asf-codec=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx where the parameter xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is replaced by an identifier of the codec. In certain implementations, this identifier is the codec GUID from the ASF file. The identifier may be stored in the ASF file as, for example, the Media Type GUID from the Stream Properties Object in the ASF file, or the Type-Specific Data section of the Stream Properties Object in the ASF file.
[0101] The config=config-info parameter identifies the codec initialization data, where config-info is replaced by a series of sub-parameters. In certain implementations, the sub-parameters are Base64 encoded. These sub-parameters are separated by “/” characters, or alternatively other characters (e.g., periods, commas, colons, semi-colons, etc.). The syntax of config-info is as follows:
[0102] MajorType/FixedSizeSamples/TemporalCompression/SampleSize/FormatType/FormatData
[0103] The MajorType sub-parameter is an identifier (e.g., a GUID (Globally Unique ID)) that identifies the type of the media stream. In certain implementations, valid values include “73647561-0000-0010-8000-00AA00389B71” for an audio stream, and “73646976-0000-0010-8000-00AA00389B71” for a video stream.
[0104] The FixedSizeSamples sub-parameter indicates whether the codec uses fixed size samples (packets). In certain implementations, the FixedSizeSamples sub-parameter is “1” if the codec uses fixed size media samples (packets), or “0” otherwise. For example, usually this field will be “1” for audio and uncompressed video, but “0” for compressed video.
[0105] The TemporalCompression sub-parameter indicates whether the stream uses temporal compression. In certain implementations, the TemporalCompression sub-parameter is “1” if the stream uses temporal compression, meaning that not all media samples are “key-frames”. Otherwise, it is set to “0”. This field may be set to “1” for many types of compressed video, because such streams may have non-key frame media samples.
[0106] The SampleSize sub-parameter indicates the size of the media samples when the codec uses fixed size samples (packets). In certain implementations, the SampleSize sub-parameter is a decimal number which gives the size of the media samples when FixedSizeSamples is “1”. The SampleSize sub-parameter can be set to “0”, and should be ignored, when FixedSizeSamples is “0”.
[0107] The FormatType sub-parameter is an identifier (e.g., a GUID) that identifies the format of the FormatData sub-parameter. The FormatData sub-parameter is the codec initialization data identified by the FormatType sub-parameter. Any of a variety of different structures that describe properties of a codec can be used for the FormatData sub-parameter. For example, the data structure describing properties of a codec for an audio stream may include information about the audio sample rate and the number of bits per sample. By way of another example, the data structure describing properties of a codec for a video stream may include information about the width and height (e.g., in pixels) of the video information, as well as the pixel aspect ratio. In certain implementations, each byte in the codec initialization data is represented as two hexadecimal digits in SDP. Alternatively, other representations may be used such as Base64 encoding.
[0108] Bandwidth Sharing
[0109] The bandwidth sharing extension specifies streams that share bandwidth in such a way that the maximum bandwidth of the set of specified streams is less than the sum of the maximum bandwidths of the individual specified streams. The bandwidth sharing extension is included in the session level description using an “a=bwshare” attribute.
[0110] In certain embodiments, the parameters for the bandwidth sharing extension are obtained by accessing the Bandwidth Sharing Object in an ASF file header associated with the multimedia presentation. The parameters identified in the ASF file header are retrieved and used as the parameters of the bandwidth sharing extension. If there are multiple Bandwidth Sharing Objects in the ASF file header, then a separate bandwidth sharing extension is included in the session description message for each of those multiple Bandwidth Sharing Objects.
[0111] The syntax for the “a=bwshare” attribute is defined as follows:
[0112] a=bwshare:SharingType R B SessionList
[0113] The SharingType parameter can be set to different values to indicate the type of sharing. For example, the SharingType parameter may be set to “PART” to indicate that any number of the specified streams may be streaming data at any given time, but set to “EXCL” if only one of the specified streams may be streaming data at any given time. In certain embodiments, when basing the bandwidth sharing extension on the information in an ASF file header, if the value of the “Sharing Type” GUID in the Bandwidth Sharing Object of the ASF file header is ASF_Bandwidth_Sharing_Partial then the SharingType parameter is set to “PART”, and if the value of the “Sharing Type” GUID in the Bandwidth Sharing Object of the ASF file header is ASF_Bandwidth_Sharing_Exclusive then the SharingType parameter is set to “EXCL”.
[0114] The R parameter specifies the leak rate (e.g., in bits per second) of a leaky bucket that contains the data portion of all of the streams without overflowing. The size of the leaky bucket is specified as the B parameter. In certain embodiments, when basing the bandwidth sharing extension on the information in an ASF file header, the R parameter is the value of the “Data Bitrate” field in the ASF file header, expressed as a decimal number.
[0115] The B parameter specifies the size (e.g., in milliseconds) of the leaky bucket. In certain embodiments, when basing the bandwidth sharing extension on the information in an ASF file header, the B parameter is the value of the “Buffer Size” field in the ASF file header, expressed as a decimal number.
[0116] The SessionList parameter consists of one or more decimal numbers, separated by space characters. Each number identifies one of the specified streams that is covered by the bandwidth sharing relationship expressed by this “a=bwshare” attribute. The streams are identified by their RTP session numbers.
[0117] Stream Prioritization
[0118] The stream prioritization extension specifies which streams in the multimedia presentation should have priority over which other streams. This prioritization can be used, for example, to identify which streams should or should not be dropped in the event of network congestion.
[0119] The stream prioritization extension is included in the session level description using an “a=prio” attribute. The “a=prio” attribute lists each RTP session in priority order, with the highest priority RTP session listed first. The “a=prio” attribute includes a list of parameters that are identifiers of the RTP sessions.
[0120] Certain RTP sessions can be identified as mandatory, which indicates that those certain sessions are not supposed to be dropped in response to network congestion. Mandatory RTP sessions are indicated in the “a=prio” attribute by appending the character ‘m’ after the RTP session number.
[0121] The following example illustrates the syntax of the “a=prio” attribute.
[0122] a=prio:1m 2m 3
In this example, RTP sessions 1 and 2 are mandatory. RTP session 3 has lower priority than the other sessions, and may be dropped in the event of network congestion.
[0123] In certain embodiments, the stream priorities are obtained by accessing the Stream Prioritization Object in an ASF file header associated with the multimedia presentation. The streams identified in the ASF file header correspond to RTP sessions, and the stream priorities identified in the ASF file header are used as the priorities for the corresponding RTP sessions. If the “Mandatory Flag” is set for a particular ASF stream, then the corresponding RTP session is also considered mandatory.
[0124] Referring now to FIG. 5 , FIG. 5 illustrates a general computer environment 300, which can be used to implement the techniques described herein. The computer environment 300 is only one example of a computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the computer and network architectures. Neither should the computer environment 300 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary computer environment 300.
[0125] Computer environment 300 includes a general-purpose computing device in the form of a computer 302. Computer 302 can be, for example, a client device 102 or server device 104 of FIGS. 1 and 2 . Computer 302 can also be an encoder device that is the source of a multimedia presentation. The components of computer 302 can include, but are not limited to, one or more processors or processing units 304, a system memory 306, and a system bus 308 that couples various system components including the processor 304 to the system memory 306.
[0126] The system bus 308 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus.
[0127] Computer 302 typically includes a variety of computer readable media. Such media can be any available media that is accessible by computer 302 and includes both volatile and non-volatile media, removable and non-removable media.
[0128] The system memory 306 includes computer readable media in the form of volatile memory, such as random access memory (RAM) 310, and/or non-volatile memory, such as read only memory (ROM) 312. A basic input/output system (BIOS) 314, containing the basic routines that help to transfer information between elements within computer 302, such as during start-up, is stored in ROM 312. RAM 310 typically contains data and/or program modules that are immediately accessible to and/or presently operated on by the processing unit 304.
[0129] Computer 302 may also include other removable/non-removable, volatile/non-volatile computer storage media. By way of example, FIG. 5 illustrates a hard disk drive 316 for reading from and writing to a non-removable, non-volatile magnetic media (not shown), a magnetic disk drive 318 for reading from and writing to a removable, non-volatile magnetic disk 320 (e.g., a “floppy disk”), and an optical disk drive 322 for reading from and/or writing to a removable, non-volatile optical disk 324 such as a CD-ROM, DVD-ROM, or other optical media. The hard disk drive 316, magnetic disk drive 318, and optical disk drive 322 are each connected to the system bus 308 by one or more data media interfaces 326. Alternatively, the hard disk drive 316, magnetic disk drive 318, and optical disk drive 322 can be connected to the system bus 308 by one or more interfaces (not shown).
[0130] The disk drives and their associated computer-readable media provide non-volatile storage of computer readable instructions, data structures, program modules, and other data for computer 302. Although the example illustrates a hard disk 316, a removable magnetic disk 320, and a removable optical disk 324, it is to be appreciated that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like, can also be utilized to implement the exemplary computing system and environment.
[0131] Any number of program modules can be stored on the hard disk 316, magnetic disk 320, optical disk 324, ROM 312, and/or RAM 310, including by way of example, an operating system 326, one or more application programs 328, other program modules 330, and program data 332. Each of such operating system 326, one or more application programs 328, other program modules 330, and program data 332 (or some combination thereof) may implement all or part of the resident components that support the distributed file system.
[0132] A user can enter commands and information into computer 302 via input devices such as a keyboard 334 and a pointing device 336 (e.g., a “mouse”). Other input devices 338 (not shown specifically) may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and/or the like. These and other input devices are connected to the processing unit 304 via input/output interfaces 340 that are coupled to the system bus 308, but may be connected by other interface and bus structures, such as a parallel port, game port, or a universal serial bus (USB).
[0133] A monitor 342 or other type of display device can also be connected to the system bus 308 via an interface, such as a video adapter 344. In addition to the monitor 342, other output peripheral devices can include components such as speakers (not shown) and a printer 346 which can be connected to computer 302 via the input/output interfaces 340.
[0134] Computer 302 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computing device 348. By way of example, the remote computing device 348 can be a personal computer, portable computer, a server, a router, a network computer, a peer device or other common network node, and the like. The remote computing device 348 is illustrated as a portable computer that can include many or all of the elements and features described herein relative to computer 302.
[0135] Logical connections between computer 302 and the remote computer 348 are depicted as a local area network (LAN) 350 and a general wide area network (WAN) 352. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.
[0136] When implemented in a LAN networking environment, the computer 302 is connected to a local network 350 via a network interface or adapter 354. When implemented in a WAN networking environment, the computer 302 typically includes a modem 356 or other means for establishing communications over the wide network 352. The modem 356, which can be internal or external to computer 302, can be connected to the system bus 308 via the input/output interfaces 340 or other appropriate mechanisms. It is to be appreciated that the illustrated network connections are exemplary and that other means of establishing communication link(s) between the computers 302 and 348 can be employed.
[0137] In a networked environment, such as that illustrated with computing environment 300, program modules depicted relative to the computer 302, or portions thereof, may be stored in a remote memory storage device. By way of example, remote application programs 358 reside on a memory device of remote computer 348. For purposes of illustration, application programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computing device 302, and are executed by the data processor(s) of the computer.
[0138] Various modules and techniques may be described herein in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.
[0139] An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise “computer storage media” and “communications media.”
[0140] “Computer storage media” includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices.
[0141] “Communication media” typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves or other transport mechanisms. Communication media also includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.
[0142] Although the description above uses language that is specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the invention.
Claims
The invention claimed is:
1. One or more computer readable storage media having stored thereon a plurality of instructions for generating a session description message that describes properties of a multimedia presentation to be streamed to a client device, the plurality of instructions, when executed by one or more processors, causing the one or more processors to:
access an ASF file header of the multimedia presentation;
identify a subset of a plurality of objects of the ASF file header;
generate, for each object in the subset of the plurality of objects, a different one of a plurality of extensions for the session description message that are separate from the ASF file header, the plurality of extensions including:
a caching information extension that specifies information about caching of the multimedia presentation, the information identifying whether the multimedia presentation can be cached, a length the multimedia presentation is considered fresh, when cached copies of media streams of the multimedia presentation are considered stale, whether to use a stale cached copy of a media stream, and whether to determine if a newer version of the media stream is available when the media stream is stale;
an encapsulation extension that specifies codec initialization parameters for one or more of a plurality of different codecs; and
a bandwidth sharing extension that is separate from the ASF file header and that specifies media streams of the multimedia presentation that share bandwidth such that a maximum bandwidth of the specified media streams is less than a sum of maximum bandwidths of each of the specified media streams; and
for each object in the subset of the plurality of objects:
retrieve one or more parameters from the object, and
use the retrieved parameters as the parameters for one of the plurality of extensions.
2. One or more computer readable storage media as recited in claim 1, wherein one of the plurality of extensions comprises a mutual exclusivity extension that specifies which of a plurality of media streams of the multimedia presentation are mutually exclusive.
3. One or more computer readable storage media as recited in claim 1, wherein one of the plurality of extensions comprises a marker extension specifies an index into the multimedia presentation.
4. One or more computer readable storage media as recited in claim 1, wherein one of the plurality of extensions comprises a script command extension that specifies data that is to be presented during playback of the multimedia presentation.
5. One or more computer readable storage media as recited in claim 1, wherein one of the plurality of extensions comprises a stream prioritization extension that specifies which of a plurality of media streams of the multimedia presentation should have priority over which other of the plurality of media streams and which of the plurality of streams should or should not be dropped when there is network congestion.
6. One or more computer readable storage media having stored thereon a plurality of instructions that, when executed by one or more processors, causes the one or more processors to:
generate a session description message that describes properties of a multimedia presentation to be streamed to a client device, the multimedia presentation having a plurality of media streams, and the session description message having a plurality of extensions, the plurality of extensions including:
a caching information extension that is separate from any ASF file header of the multimedia presentation and that specifies information about caching of the multimedia presentation, the information identifying whether the multimedia presentation can be cached, a length the multimedia presentation is considered fresh, when cached copies of any of the plurality of media streams of the multimedia presentation are considered stale, whether to use a stale cached copy of a media stream, and whether to determine if a newer version of the media stream is available when the media stream is stale;
an encapsulation extension that specifies codec initialization parameters for one or more of a plurality of different codecs; and
a bandwidth sharing extension that is separate from any ASF file header and that specifies media streams of the multimedia presentation that share bandwidth such that a maximum bandwidth of the specified media streams is less than a sum of maximum bandwidths of each of the specified media streams; and
include, as part of data streamed to the client device, the session description message.
7. One or more computer readable storage media as recited in claim 6, wherein the session description message is a Session Description Protocol (SDP) message.
8. One or more computer readable storage media as recited in claim 6, wherein the instructions that cause the one or more processors to generate the session description message further cause the one or more processors to:
identify an object of an ASF file header of the multimedia presentation;
retrieve one or more parameters from the object; and
analyze the retrieved one or more parameters to determine the parameters for the caching information extension.
9. One or more computer readable storage media as recited in claim 6, wherein the information about caching of the multimedia presentation comprises information specifying whether the client device is allowed to cache the multimedia presentation.
10. One or more computer readable storage media as recited in claim 6, wherein the information about caching of the multimedia presentation comprises information specifying whether the client device is allowed to rebroadcast the multimedia presentation.
11. One or more computer readable storage media having stored thereon a plurality of instructions that, when executed by one or more processors, causes the one or more processors to:
generate a session description message that describes properties of a multimedia presentation to be streamed to a client device, the multimedia presentation having a plurality of media streams, and the session description message having a plurality of extensions, the plurality of extensions including:
a caching information extension that specifies information about caching of the multimedia presentation, the information identifying whether the multimedia presentation can be cached, a length the multimedia presentation is considered fresh, when cached copies of any of the plurality of media streams of the multimedia presentation are considered stale, whether to use a stale cached copy of a media stream, and whether to determine if a newer version of the media stream is available when the media stream is stale;
an encapsulation extension that is separate from any ASF file header of the multimedia presentation and that specifies codec parameters for one or more of a plurality of different codecs; and
a bandwidth sharing extension that is separate from the ASF file header and that specifies media streams of the multimedia presentation that share bandwidth such that a maximum bandwidth of the specified media streams is less than a sum of maximum bandwidths of each of the specified media streams; and
include, as part of data streamed to the client device, the session description message.
12. One or more computer readable storage media as recited in claim 11, wherein the session description message includes a plurality of encapsulation extensions, each of the plurality of encapsulation extensions having the same syntax but being for a different one of the plurality of different codecs.
13. One or more computer readable storage media as recited in claim 11, wherein the instructions that cause the one or more processors to generate the session description message further cause the one or more processors to:
identify an object of an ASF file header of the multimedia presentation;
retrieve one or more parameters from the object; and
analyze the retrieved one or more parameters to determine the parameters for the encapsulation extension.
14. One or more computer readable storage media as recited in claim 11, wherein the codec parameters include an identifier of a type of a media stream of the multimedia presentation that is to be decoded by the one or more codecs.
15. One or more computer readable storage media as recited in claim 11, wherein the codec parameters include an indication of whether a media stream of the multimedia presentation that is to be decoded by the one or more codecs uses temporal compression.
16. One or more computer readable storage media as recited in claim 11, wherein the codec parameters include initialization data for the one or more codecs.
17. One or more computer readable storage as recited in claim 16, wherein the codec parameters include a format of the initialization data in the session description message.
Patent Citations (131)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4963995(A) | 1990-10-01 | Lang | Applicant |
| US5057932(A) | 1991-10-01 | Lang | Applicant |
| US5132964(A) | 1992-07-01 | Esaki | Applicant |
| US5164839(A) | 1992-11-01 | Lang | Applicant |
| US5262875(A) | 1993-11-01 | Mincer et al. | Applicant |
| US5440334(A) | 1995-08-01 | Walters et al. | Applicant |
| US5568181(A) | 1996-10-01 | Greenwood et al. | Applicant |
| US5710970(A) | 1998-01-01 | Walters et al. | Applicant |
| US5758076(A) | 1998-05-01 | Wu et al. | Applicant |
| US5787472(A) | 1998-07-01 | Dan et al. | Applicant |
| US5822524(A) | 1998-10-01 | Chen et al. | Applicant |
| US5822537(A) | 1998-10-01 | Katseff et al. | Applicant |
| US5835495(A) | 1998-11-01 | Ferriere | Applicant |
| US5850449(A) | 1998-12-01 | McManis | Applicant |
| US5872920(A) | 1999-02-01 | Hausman et al. | Applicant |
| US5884027(A) | 1999-03-01 | Garbus et al. | Applicant |
| US5890010(A) | 1999-03-01 | Nishigami | Applicant |
| US5913038(A) | 1999-06-01 | Griffiths | Applicant |
| US5931961(A) | 1999-08-01 | Ranganathan et al. | Applicant |
| US5963202(A) | 1999-10-01 | Polish et al. | Applicant |
| US5978567(A) | 1999-11-01 | Rebane et al. | Applicant |
| US5983263(A) | 1999-11-01 | Rothrock et al. | Applicant |
| US5995705(A) | 1999-11-01 | Lang | Applicant |
| US5996015(A) | 1999-11-01 | Day et al. | Applicant |
| US6005621(A) | 1999-12-01 | Linzer et al. | Applicant |
| US6014694(A) | 2000-01-01 | Aharoni et al. | Applicant |
| US6014706(A) | 2000-01-01 | Cannon et al. | Applicant |
| US6041345(A) | 2000-03-01 | Levi et al. | Applicant |
| US6054943(A) | 2000-04-01 | Lawrence | Applicant |
| US6111567(A) | 2000-08-01 | Savchenko et al. | Applicant |
| US6118817(A) | 2000-09-01 | Wang | Applicant |
| US6120149(A) | 2000-09-01 | Hosoi | Applicant |
| US6161201(A) | 2000-12-01 | Payne et al. | Applicant |
| US6195692(B1) | 2001-02-01 | Hsu | Applicant |
| US6209041(B1) | 2001-03-01 | Shaw et al. | Applicant |
| US6216163(B1) | 2001-04-01 | Bharali et al. | Applicant |
| US6262990(B1) | 2001-07-01 | Ejiri | Applicant |
| US6272148(B1) | 2001-08-01 | Takagi et al. | Applicant |
| US6292834(B1) | 2001-09-01 | Ravi et al. | Applicant |
| US6292880(B1) | 2001-09-01 | Mattis et al. | Applicant |
| US6314492(B1) | 2001-11-01 | Allen et al. | Applicant |
| US6327421(B1) | 2001-12-01 | Tiwari et al. | Applicant |
| US6329165(B1) | 2001-12-01 | Chattoraj et al. | Applicant |
| US6343298(B1) | 2002-01-01 | Savchenko et al. | Applicant |
| US6351767(B1) | 2002-02-01 | Batchelder et al. | Applicant |
| US6369835(B1) | 2002-04-01 | Lin | Applicant |
| US6385647(B1) | 2002-05-01 | Willis et al. | Applicant |
| US6405256(B1) | 2002-06-01 | Lin et al. | Applicant |
| US6407680(B1) | 2002-06-01 | Lai et al. | Applicant |
| US6421348(B1) | 2002-07-01 | Gaudet et al. | Applicant |
| US6449269(B1) | 2002-09-01 | Edholm | Applicant |
| US6480498(B1) | 2002-11-01 | Gaudet et al. | Applicant |
| US6484199(B2) | 2002-11-01 | Eyal | Applicant |
| US6493748(B1) | 2002-12-01 | Nakayama et al. | Applicant |
| US6502135(B1) | 2002-12-01 | Munger et al. | Applicant |
| US6553376(B1) | 2003-04-01 | Lewis et al. | Applicant |
| US6611868(B1) | 2003-08-01 | Arutyunov | Applicant |
| US6611898(B1) | 2003-08-01 | Slattery et al. | Applicant |
| US6614763(B1) | 2003-09-01 | Kikuchi et al. | Applicant |
| US6643259(B1) | 2003-11-01 | Borella et al. | Applicant |
| US6691312(B1) | 2004-02-01 | Sen et al. | Applicant |
| US6725333(B1) | 2004-04-01 | Degenaro et al. | Applicant |
| US6735634(B1) | 2004-05-01 | Geagan, III et al. | Applicant |
| US6757255(B1) | 2004-06-01 | Aoki et al. | Applicant |
| US6760749(B1) | 2004-07-01 | Dunlap et al. | Applicant |
| US6760765(B1) | 2004-07-01 | Asai et al. | Applicant |
| US6765878(B1) | 2004-07-01 | Carlson | Applicant |
| US6772375(B1) | 2004-08-01 | Banga | Applicant |
| US6779043(B1) | 2004-08-01 | Crinion | Applicant |
| US6785288(B1) | 2004-08-01 | Enns et al. | Applicant |
| US6792449(B2) | 2004-09-01 | Colville et al. | Applicant |
| US6801947(B1) | 2004-10-01 | Li | Applicant |
| US6892354(B1) | 2005-05-01 | Servan-Schreiber et al. | Applicant |
| US6952424(B1) | 2005-10-01 | Bass et al. | Applicant |
| US6954430(B2) | 2005-10-01 | Haglund | Applicant |
| US6986018(B2) | 2006-01-01 | O'Rourke et al. | Applicant |
| US6990070(B1) | 2006-01-01 | Aweya et al. | Applicant |
| US6990512(B1) | 2006-01-01 | Major et al. | Applicant |
| US7007090(B1) | 2006-02-01 | Spangler et al. | Applicant |
| US7020087(B2) | 2006-03-01 | Hagai et al. | Applicant |
| US7051110(B2) | 2006-05-01 | Hagai et al. | Applicant |
| US7054774(B2) | 2006-05-01 | Batterberry et al. | Applicant |
| US7054911(B1) | 2006-05-01 | Lango et al. | Applicant |
| US7054949(B2) | 2006-05-01 | Jennings | Applicant |
| USRE39184(E) | 2006-07-01 | Schloss et al. | Applicant |
| US7073028(B2) | 2006-07-01 | Lango et al. | Applicant |
| US7076560(B1) | 2006-07-01 | Lango et al. | Applicant |
| US7096481(B1) | 2006-08-01 | Forecast et al. | Applicant |
| US7133881(B2) | 2006-11-01 | Sirivara et al. | Applicant |
| US7185082(B1) | 2007-02-01 | del Val et al. | Applicant |
| US7359373(B2) | 2008-04-01 | Kuusinen et al. | Examiner |
| US2002/0047899(A1) | 2002-04-01 | Son et al. | Applicant |
| US2002/0048448(A1) | 2002-04-01 | Daniels | Applicant |
| US2002/0049817(A1) | 2002-04-01 | Drory et al. | Applicant |
| US2002/0077900(A1) | 2002-06-01 | Thompson et al. | Applicant |
| US2002/0090027(A1) | 2002-07-01 | Karczewicz et al. | Applicant |
| US2002/0097727(A1) | 2002-07-01 | Prakash | Applicant |
| US2002/0138641(A1) | 2002-09-01 | Taylor et al. | Applicant |
| US2002/0170067(A1) | 2002-11-01 | Norstrom et al. | Applicant |
| US2002/0184510(A1) | 2002-12-01 | Shieh | Examiner |
| US2002/0194608(A1) | 2002-12-01 | Goldhor | Applicant |
| US2003/0018799(A1) | 2003-01-01 | Eyal | Applicant |
| US2003/0055809(A1) | 2003-03-01 | Bhat | Applicant |
| US2003/0061372(A1) | 2003-03-01 | Agarwalla et al. | Applicant |
| US2003/0099364(A1) | 2003-05-01 | Thompson et al. | Applicant |
| US2003/0188009(A1) | 2003-10-01 | Agarwalla et al. | Examiner |
| US2003/0236902(A1) | 2003-12-01 | Weiss et al. | Applicant |
| US2003/0236912(A1) | 2003-12-01 | Klemets et al. | Applicant |
| US2004/0003101(A1) | 2004-01-01 | Roth et al. | Applicant |
| US2004/0054912(A1) | 2004-03-01 | Adent et al. | Examiner |
| US2004/0190606(A1) | 2004-09-01 | Deshpande | Applicant |
| US2004/0196849(A1) | 2004-10-01 | Aksu et al. | Examiner |
| US2004/0244010(A1) | 2004-12-01 | Kleyman et al. | Applicant |
| US2005/0083909(A1) | 2005-04-01 | Kuusinen et al. | Examiner |
| US2005/0152400(A1) | 2005-07-01 | Suzuki | Applicant |
| US2005/0157714(A1) | 2005-07-01 | Shlissel et al. | Applicant |
| US2005/0256941(A1) | 2005-11-01 | Armstrong et al. | Applicant |
| US2007/0223443(A1) | 2007-09-01 | Wang et al. | Examiner |
| JP2003229843(A) | 2003-08-01 | Applicant | |
| JP2004038970(A) | 2004-02-01 | Applicant | |
| KR20020069272 | 2002-08-01 | Applicant | |
| RU2157000 | 2000-09-01 | Applicant | |
| RU2181929 | 2002-04-01 | Applicant | |
| WO9817006 | 1998-04-01 | Applicant | |
| WO143445 | 2001-06-01 | Applicant | |
| WO230125 | 2002-04-01 | Applicant | |
| WO245372 | 2002-06-01 | Applicant | |
| WO2058388(A1) | 2002-07-01 | Applicant | |
| WO3052631(A2) | 2003-06-01 | Applicant | |
| WO3058485(A1) | 2003-07-01 | Applicant | |
| WO2004030358(A1) | 2004-04-01 | Applicant |
Non-Patent Literature (39)
- “SDP: Session Description Protocol draft-ietf-mmusic-sdp-new-15.txt” Handley, M. Jacobson, V. Perkins, C. , Oct. 27, 2003, Network Working Group Internet-Draft (http://tools.ietf.org/html/draft-ietf-mmusic-sdp-new-15).Examiner
- “TAPI 3.0 Connection and Media Services” Microsoft Windows 2000 Server Copyright 1999 pp. 1-23.Applicant
- Aboobaker, et al , “Streaming Media Congestion Control Using Bandwidth Estimation” Lecture Notes in Computer Science 2002 vol. 2496 pp. 89-100.Applicant
- “Advanced Systems Format (ASF) Specification” Revision 01.20.01e Microsoft Corporation Sep. 2003 pp. i-vi and 1-93.Applicant
- Braun, et al., “Multicast for Small Conferences” Proceedings of the Sixth IEEE Symposium on Computers and Communications Jul. 3, 2001 pp. 145-150.Applicant
- Camarillo, et al., “Grouping of Media Lines in the Session Description Protocol (SDP)” Network Working Group Requests for Comments: 3388 The Internet Society Dec. 2002 pp. 1-21.Applicant
- Coulson, “A Distributed Object Platform Infrastructure for Multimedia Applications,” Comptuer Communications, Jul. 1998, 27 pages, vol. 21, No. 9.Applicant
- Dutta, et al. “A Streaming architecture for next generation internet”, ICC 2001, 2001 IEEE International Conference on Communications. Helsinky, Finland, Jun. 11-14, 2001, 1303-1309.Applicant
- Fielding, et al., “Hypertext Transfer Protocol —HTTP/1.1” Network Working Group Request for Comments: 2616; The Internet Society (Jun. 1999); Category: Standards Track pp. 1-176.Applicant
- Fleischman, “WAVE and AVI Codec Registries” Network Working Group Request for Comments: 2381 The Internet Society Jun. 1998 pp. 1-71.Applicant
- Guo, et al., “RCache: Design and Analysis of Scalable Fault Tolerant Multimedia Stream Caching Schemes” Scalability and Traffic Control in IP Networks Proceedings of SPIE vol. 4526 pp. 68-86.Applicant
- Handely, et al., “SDP: Session Description Protocol” Network Working Group Request for Comments: 2327 The Internet Society Apr. 1998 pp. 1-42.Applicant
- Hayes, et al., “Impact of Flow Control on quality of service driven packet scheduling disciplines” Proceedings of the 1999 IEEE International Conference on Control Applications Kohala Coast HI Aug. 22, 1999; pp. 1454-1459.Applicant
- Jin, et al., “Accelerating Internet Streaming Media Delivery using Network-Aware Partial Caching” 2002 IEEE pp. 153-160.Applicant
- Kamiyama N et al. “Renegotiated CBR transmission in interactive video-on-demand system”, Multimedia Computing and Systems '97 Proceedings, IEEE International Conference, Ottawa ONT, Canada Jun. 3-6, 1997. pp. 12-19.Applicant
- Khalis et al., “Performance considerations for TCP/IP in wide area networks” Proceedings 19th Conference on Oct. 2-5, 1994 pp. 166-175.Applicant
- “Measuring Bandwidth” INFOCOM '99; Eighteenth Annual Joint Conference of the IEEE Computer and Communications Societies Proceedings; IEEE New York NY USA Mar. 21, 1999 pp. 235-245.Applicant
- Lixin Gao et al. “Supplying instantaneous video-on-demand services using controlled multicast”, Multimedia Computing and Systems, 1999, IEEE International Conference on Florence, Italy Jun. 7,11, 1999, pp. 117-121.Applicant
- Microsoft Computer Dictionary 5th Edition.Applicant
- Minshall, et al., “Application performance pitfalls and TCP's Nagle algorithm” vol. 27 No. 4 Mar. 2000 pp. 36-44.Applicant
- Moldeklev, et al., “How a large ATM MTU causes deadlocks in TCP data transfers” IEEE/ACM Transactions on Networking vol. 3 Issue 4 Aug. 1995 pp. 409-422.Applicant
- Muuss, “The Research Interests of Mike Muuss”; Oct. 8, 1999; retreived from the Internet Archive at: http://web.archive.org/web/1991008020453/ftp.arl.mil/mike/.Applicant
- Muuss, “The Story of the PING Program”; Oct. 18, 1999: retrieved from the Internet Archive at : http://web.archive.org/web/19991018225218/ftp.arl.mil/mike/ping.html.Applicant
- Nagle, “Congestion Control in IP/TCP Internetworks,” RFC 896, Jan. 6, 1984, 8 pages.Applicant
- Nishida, et al., “Congestion Control Mechanism for TCP with Packet Pair Scheme” IEICE Transactions on Information and Systems Institute of Electronics Information and Comm. Egn. Tokyo JP vol E82-D No. 4 Apr. 1999 pp. 854-862.Applicant
- Paknikar, et al., “A Caching and Straming Framework for Multimedia” ACM Multimedia 2000 Los Angelos CA; pp. 13-20.Applicant
- Petit, et al. “Bandwidth resource optimization in ivdeo-on-demand network architectures”, Community Networkign Integrated Multimedia Services to the Home, 1994, Proceedings of the 1st International Workshop on San Francisco, CA Jul. 13-14, 1994, pp. 91-97.Applicant
- Schulzrinne, et al., “Real Time Streaming Protocol (RTSP)” Network Working Group Request for Comments: 2326; The Internet Society (Apr. 1998) pp. 1-92.Applicant
- Schulzrinne, et al., “RTP: A Transport Protocol for Real-Time Applications” Network Working Group Request for Comments: 3550 Jul. 2003 pp. 1-104.Applicant
- Shannon, “A Mathematical Theory of Communication” reprinted with corrections from The Bell System Technical Journal vol. 27 pp. 379-423 623-656 Jul. Oct. 1948 (pages renumbered as 1-55).Applicant
- Stevens, “TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms,” RFC, Jan. 1997, 6 pages.Applicant
- From the Internet: http://www.freesoft.org/CIE/Topics/83.htm, “TCP Protocol Overview,” Connected: An Internet Encyclopedia, retrieved on May 31, 2000.Applicant
- From the Internet: http://www.scit.wlv.ac.uk/˜jphb/comms/tcp.html, “Transmission Control Protocol,” retrieved on May 31, 2000.Applicant
- Kamiyama, Noriaki “An Efficient Transmission Protocol for Multicast Video-on-Demand System”, Technical Report of IEICE (the Institute of Electronics, Information and Communication Engineers), Japan, The Institute of Electronics, Information and Communication Engineers, Mar. 2001, vol. 100, No. 672, pp. 121-128.Applicant
- Kawachiya, et al., “Videoproxy: A Media and Protocol Converter for Internet Video”, Global Information Infrastructure (GII) Evolution: Interworking Issues. Interworking '96. Third International Symposium on Interworking. Nara (Japan), Oct. 1-3, 1996, Amsterdam, IOS, NL, Oct. 1, 1996 pp. 541-550.Applicant
- Quicktime: “Quicktime Streaming Server Mondules” , retrieved from the internet: <URL:http://netmedia.kjist.ac.kr/courses/dic1698-2002sp/reports/QTSS.pdf> p. 85-87, Quicktime, Feb. 2002, pp. 1-194.Applicant
- Dey, et al., “Playback Restart in Interactive Streaming Video Applications”, IEEE, Jun. 3-6, 1997, pp. 458-465.Applicant
- Official Notice of Rejection for European Patent Application No. 02011057.3 mailed Apr. 18, 2008, 6 pgs.Applicant
- Gulbransen, “Special Edition Using XML, Second Edition”, Jul. 16, 2002, pp. 1-8.Applicant