EP1676216B1 - Integration d'un message de description de session (SDP) dans un message de protocole de controle en temps réel RTCP) - Google Patents

Integration d'un message de description de session (SDP) dans un message de protocole de controle en temps réel RTCP) Download PDF

Info

Publication number
EP1676216B1
EP1676216B1 EP04779232A EP04779232A EP1676216B1 EP 1676216 B1 EP1676216 B1 EP 1676216B1 EP 04779232 A EP04779232 A EP 04779232A EP 04779232 A EP04779232 A EP 04779232A EP 1676216 B1 EP1676216 B1 EP 1676216B1
Authority
EP
European Patent Office
Prior art keywords
field
length
message
stream
rtcp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP04779232A
Other languages
German (de)
English (en)
Other versions
EP1676216A1 (fr
EP1676216A4 (fr
Inventor
Anders E. Klemets
Eduardo P. Oliveira
James M. Alkove
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Corp
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/693,430 external-priority patent/US7586938B2/en
Application filed by Microsoft Corp filed Critical Microsoft Corp
Priority to EP11004533.3A priority Critical patent/EP2365450B1/fr
Priority to EP11004532.5A priority patent/EP2365449B1/fr
Publication of EP1676216A1 publication Critical patent/EP1676216A1/fr
Publication of EP1676216A4 publication Critical patent/EP1676216A4/fr
Application granted granted Critical
Publication of EP1676216B1 publication Critical patent/EP1676216B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

Definitions

  • This invention relates to streaming media and data transfers, and particularly to embedding a session description message in an RTCP message.
  • Content streaming such as the streaming of audio, video, and/or text is becoming increasingly popular.
  • streaming is typically used to indicate that the data representing the content is provided over a network to a client computer on an as-needed basis rather than being pre-delivered in its entirety before playback.
  • the client computer renders streaming content as it is received from a network server, rather than waiting for an entire "file" to be delivered.
  • 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.
  • streaming multimedia, audio, video, or audio/visual coverage of noteworthy events can be broadcast over the Internet as the events unfold.
  • television and radio stations can transmit their live content over the Internet.
  • SDP Session Description Protocol
  • RRC Network Working Group Request for Comments 2327
  • 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.
  • RTSP Real-Time Streaming Protocol
  • HTTP HyperText Transfer Protocol
  • the network server may be streaming a series of multimedia presentations to the client computer, such as presentations listed in a play list.
  • the network server switches from streaming one presentation to the next, it is oftentimes difficult for the SDP information for the next presentation to be made available to the client computer.
  • Content streaming may also be multicast.
  • Conventional approaches to multicasting of streaming content typically involves providing content to be multicast to a server, which then multicasts the content over a network (i.e., without feedback from the clients receiving the streams).
  • the server typically multicasts the content in several streams having different formats (e.g., bit rates, languages, encoding schemes etc.)
  • Clients attached to the network can then receive the stream(s) appropriate for its resources.
  • one multicast approach requires that the server provide a file that provides "multicast information" that allows clients to open streams of content. Maintaining and publishing this file is typically a manual process that has a relatively high administrative cost.
  • clients may encounter problems, which can lead to customer dissatisfaction.
  • Another problem with this approach is that clients must keep their "multicast information" up-to-date so that they can properly access the content. This problem is exacerbated for clients that do not have a suitable back channel to request updates (e.g., clients with unidirectional satellite links).
  • EP 1 280 306 A2 relates to a system and method for providing rapid rerouting of real-time transport protocol (RTP) multi-media flows.
  • a RTCP packet format can be used between two multi-media routers (see [0038]).
  • RTCP packets that are of particular interest include a sender report and a receiver report.
  • the sender report includes sender transmission information and per receiver information, while the receive report includes the per receiver information.
  • Session statistics in a receiver report message that are of particular interest in deriving latency, jitter and dropped packets include fraction lost, cumulative lost, highest sequence number received, interarrival jitter, last session report timestamp, and/or delay since the last session report timestamp.
  • the object of the present invention is to embed a Session Description Protocol (SDP) session description message in a Real-Time Control Protocol (RTCP) message.
  • SDP Session Description Protocol
  • RTCP Real-Time Control Protocol
  • Embedded within at least some of the RTCP messages sent from a media content source to a recipient is a session description message that describes the media presentation being streamed to the recipient.
  • an RTCP message that embeds a session description message includes at least three fields.
  • the first field contains data identifying the RTCP message as being a type that embeds a session description message.
  • the second field contains data that is the session description message for a media presentation.
  • the third field contains data identifying a length of the RTCP message, generated by summing the length of the first field, the length of the second field, and the length of the third field.
  • the RTCP message is created at a device, such as a server device.
  • the session description message embedded within the RTCP message is associated with one of a plurality of pieces of media content in a play list of media content being streamed from the device to the recipient.
  • multimedia presentations are multicast using an announcement channel that includes presentation description information along with multiple channels for multiple streams of multimedia data to accommodate clients of different multimedia resources.
  • Clients can use the announcement channel to select channel(s) appropriate for their multimedia resources.
  • the channels are created in a predetermined manner (e.g., preselected logical addresses, preselected ports of an IP address, etc.) so that clients can immediately join a channel without (or concurrently with) joining the announcement channel to reduce startup latency.
  • a predetermined manner e.g., preselected logical addresses, preselected ports of an IP address, etc.
  • an acceleration channel may be created that provides blocks of data containing the current unit of the multimedia presentation along with a preselected number of previous units at a bit rate that is "faster than real-time" (i.e., at a rate that is faster than the bit-rate of the multimedia streams). This feature allows clients with suitable resources to more quickly buffer sufficient data to begin presenting the multimedia data to users.
  • the acceleration channel need not be "faster than real time” so that a client may concurrently join both the acceleration channel and another channel that multicasts multimedia data so that, in effect, the client receives the multimedia data at a rate that is "faster than real-time.”
  • Embedding a session description message in a Real-Time Control Protocol (RTCP) message is discussed herein.
  • a multimedia or single media presentation is streamed from a media content source, such as a server device, to a recipient, such as a client device, using Real-Time Transport Protocol (RTP) packets.
  • RTP Real-Time Transport Protocol
  • Control information regarding the presentation being streamed is also sent from the media content source to the recipient using RTCP messages.
  • Embedded within at least some of the RTCP messages is a session description message that describes the presentation being streamed.
  • multimedia presentations being streamed from a media content source to a recipient.
  • the media content source can be any source of media content, an example of which is a server device.
  • a recipient can be any recipient of media content, an example of which is a client device.
  • FIG. 1 illustrates an example network environment 100 that can be used to stream media using the session description message embedded in an RTCP message as described herein.
  • 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).
  • LANs local area networks
  • 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.
  • desktop PCs workstations
  • mainframe computers mainframe computers
  • gaming consoles handheld PCs
  • cellular telephones personal digital assistants
  • PDAs personal digital assistants
  • One or more of devices 102 and 104 can be the same types of devices, or alternatively different types of devices.
  • 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).
  • 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.
  • 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).
  • 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.
  • FIG. 2 illustrates example client and server devices that can stream media content using the session description message embedded in an RTCP message as described herein.
  • Multiple different protocols are typically followed at both client device 102 and server device 104 in order to stream media content from server device 104 to client device 102. These different protocols can be responsible for different aspects of the streaming process.
  • one or more additional devices e.g., firewalls, routers, gateways, bridges, etc. may be situated between client device 102 and server device 104.
  • an application level protocol 150 is used as part of the streaming process. Additional protocols not shown in FIG. 2 may also be employed (e.g., there may be an additional protocol(s) between application level protocol 150 and transport protocol 152).
  • Application level protocol 150 is a protocol at the application level for control of the delivery of data with real-time properties.
  • Application level protocol 150 provides a framework, optionally extensible, to enable controlled, on-demand delivery of real-time data, such as streaming audio and video content.
  • Application level protocol 150 is a control protocol for initiating and directing delivery of streaming multimedia from media servers.
  • Examples of application level protocol 150 include the Real-Time Streaming Protocol (RTSP) as described in Network Working Group Request for Comments (RFC) 2326, April 1998, and the HyperText Transport Protocol (HTTP) as described in Network Working Group Request for Comments (RFC) 1945, May 1996 or Network Working Group Request for Comments (RFC) 2068, January 1997.
  • RTSP Real-Time Streaming Protocol
  • HTTP HyperText Transport Protocol
  • Application level protocol 150 uses transport protocol 152 for the delivery of real-time data, such as streaming audio and video.
  • Transport protocol 152 defines a packet format for media streams.
  • Transport protocol 152 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.
  • Examples of transport protocol 152 include the Real-Time Transport Protocol (RTP) and the Real-Time Control Protocol (RTCP) as described in Network Working Group Request for Comments (RFC) 3550, July 2003.
  • RTP Real-Time Transport Protocol
  • RTCP Real-Time Control Protocol
  • Other versions, such as future draft or standardized versions, of RTP and RTCP may also be used.
  • RTP does not address resource reservation and does not guarantee quality-of-service for real-time services.
  • the data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide some control and identification functionality.
  • RTCP control protocol
  • the RTCP protocol groups one or more control messages together into a unit referred to as an RTCP packet. Embedded within one or more of the RTCP packets is a control message that includes a session description message.
  • the session description message describes properties of the multimedia presentation being streamed from server device 104 to client device 102.
  • the streaming media from server device 104 to client device 102 thus includes the session description message.
  • the transport protocol 152 uses delivery channel protocol(s) 154 for the transport connections.
  • Delivery channel protocol(s) 154 include one or more channels for transporting packets of data from server device 104 to client device 102. Each channel is typically used to send data packets for a single media stream, although in alternate embodiments a single channel may be used to send data packets for multiple media streams.
  • Examples of delivery channel protocols 154 include Transmission Control Protocol (TCP) packets and User Datagram Protocol (UDP) packets.
  • TCP ensures the delivery of data packets, whereas UDP does not ensure the delivery of data packets.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • delivery of data packets using TCP is more reliable, but also more time-consuming, than delivery of data packets using UDP.
  • FIG. 3 illustrates example client and server devices in a multicast environment that can stream media content using the session description message embedded in an RTCP message as described herein.
  • the protocols 150, 152, and 154 of FIG. 2 are included in the client and server devices of FIG. 3 , but have not been illustrated.
  • one or more additional devices e.g., firewalls, routers, gateways, bridges, etc. may be situated between client device 102 and server device 104.
  • a streaming module 182 of server device 104 streams the same multimedia presentation to each of multiple (x) client devices 102(1), 102(2), ..., 102(x).
  • Each client device 102 has a streaming media player 184 that receives the streamed multimedia presentation and processes the received stream at the client device 102, typically playing back the multimedia presentation at the client device 102.
  • the same data is streamed to each client device 102 at approximately the same time, allowing server device 104 to stream only one occurrence of the same multimedia presentation at a time, with the various client devices 102 listening in to this one occurrence being streamed.
  • the streaming media 186 includes RTCP messages having one or more session description messages embedded therein.
  • the same session description message may be broadcast multiple times during the streaming of the multimedia presentation, thereby allowing new client devices 102 to listen in to the streaming media after streaming has begun but still receive a session description message describing the multimedia presentation.
  • client devices 102 do not need to listen in to a separate stream or broadcast, potentially from a device other than server device 182, to receive the session description messages.
  • FIG. 4 illustrates example client and server devices in a server-side play list environment that can stream media content using the session description message embedded in an RTCP message as described herein.
  • the protocols 150, 152, and 154 of FIG. 2 are included in the client and server devices of FIG. 4 , but have not been illustrated.
  • one or more additional devices e.g., firewalls, routers, gateways, bridges, etc. may be situated between client device 102 and server device 104.
  • a streaming module 202 of server device 104 streams a multimedia presentation as streaming media 204 to a streaming media player 206 of client device 102.
  • Streaming media player 206 receives the streamed multimedia presentation and processes the received stream at the client device 102, typically playing back the multimedia presentation at the client device 102.
  • Server device 104 includes a play list 208 that identifies multiple (y) pieces of media content 210(1), 210(2),..., 210(y).
  • a play list 208 includes multiple entries, each entry identifying one of the multiple pieces of media content 210.
  • play list 208 may identify a single piece of media content, although in such situations the single piece of media content could simply be referenced by itself rather than through the use of a play list.
  • a client device 102 is able to select a single resource for playback, that resource identifying play list 208.
  • Streaming module 202 accesses the identified play list 208, and then accesses the individual pieces of media content 210 and streams those pieces 210 to client device 102.
  • the client device 102 is able to access a single resource, yet have multiple different pieces of media content streamed from server device 104.
  • the play list 208 is accessed by and referred to by server device 104 to identify the pieces of media content, rather than by client device 102, the play list 208 can also be referred to as a server-side play list.
  • Each piece of media content 210 includes one or more media streams. Different pieces of media content 210 can include different numbers of media streams. Each piece of media content 210 is typically a multimedia presentation. The manner in which a "piece" of content is defined can vary by implementation and based on the type of media. For example, for musical audio and/or video content each song can be a piece of content. Content may be separated into pieces along natural boundaries (e.g., different songs), or alternatively in other arbitrary manners (e.g., every five minutes of content is a piece). For stored content, different pieces of content can be stored as multiple files or alternatively as the same file.
  • FIGS. 3 and 4 Although illustrated as two separate drawings in FIGS. 3 and 4 , it is to be appreciated that pieces of media content referenced by a server-side play list as illustrated in FIG. 4 can be multicast as illustrated in FIG. 3 .
  • the data to be streamed form server device 104 to client device 102 is embedded in RTP packets.
  • Control information related to the data being streamed and the RTP packets is embedded in one or more control messages within an RTCP packet.
  • an RTCP packet consists of several messages of different types.
  • the first message in the RTCP packet is either a Receiver Report or a Sender Report.
  • the second message is an SDES (Source Description) message.
  • the SDES message contains one or more textual meta-data items.
  • the SDES message contains a CNAME (canonical name) item.
  • the CNAME item is a persistent transport-level identifier of the media content source and provides a mapping between the RTP synchronization source (SSRC) number and a textual string.
  • the SSRC is a source of a stream of RTP (and RTCP) packets.
  • the CNAME is used so that a sender or receiver that is participating in multiple RTP sessions that belong to the same presentation may use different SSRC values in each RTP session, but keep the CNAME value the same.
  • An additional type of message that can be included in an RTCP packet is a control message having embedded therein a session description message.
  • the session description message describes properties of the multimedia presentation being streamed from server device 104 to client device 102.
  • 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.
  • SDP Session Description Protocol
  • RFC Network Working Group Request for Comments
  • the session description message discussed herein is a message in accordance with the SDP format described in RFC 2327.
  • one or more session description messages are sent from server device 104 to client device 102 that include identifier(s) of the properties.
  • a single session description message may be sent by server device 104 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.
  • a session description message includes, for example, one or more of: an identification of various channels used to multicast the multimedia presentation; 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.
  • a session description message can be separated or fragmented across multiple RTCP control messages. Such situations can arise, for example, when the session description message is very large.
  • Each of these RTCP control messages is included in a different RTCP packet, and each contains a portion or fragment of the entire session description message.
  • Client device 102 upon receiving all of the portions or fragments, can combine them together to recreate the session description message.
  • FIG. 5 illustrates an example format of an RTCP control message 250 having an embedded session description message.
  • RTCP message 250 is discussed below as including multiple fields (also referred to as portions), each storing various data. It is to be appreciated that these fields can be arranged in different orders than the order in which they are discussed below and shown in FIG. 5 . Additionally, although sizes or lengths of these fields (e.g., in bits) are discussed below, it is to be appreciated that these are only examples and the fields may alternatively larger or smaller than these example sizes or lengths.
  • RTCP message 250 includes all of the fields shown in FIG. 5 . In alternate embodiments, RTCP message 250 includes fewer than all of the fields shown in FIG. 5 , or may include additional fields not shown in FIG. 5 .
  • RTCP message 250 can be viewed as being grouped into three groups: a header 290, an RTP-State block 292, and the session description message 284.
  • Header 290 includes various information about RTCP message 250.
  • RTP-State block 292 is optional, and when included is used to identify RTP-specific information about a stream of the multimedia presentation that is described in the session description message (e.g., to specify the SSRC and initial RTP sequence number of a stream in the session description message).
  • one RTP-State block 292 is associated with and included in RTCP message 250 for each media stream in the multimedia presentation.
  • Session description message 284 is the session description message embedded within RTCP message 250.
  • V (version) field 252 is a 2-bit field that identifies the version of RTP being used, which is the same in RTCP packets as in RTP packets. For example, the version defined by RFC 3550 is 2.
  • P (padding) field 254 is a single bit that, when set (e.g., to a value of 1), indicates that RTCP message 250 contains some additional padding at the end which is not part of the control information. This padding is included in the length field 262, but otherwise should be ignored. The amount of padding is included within the padding itself. In certain implementations, the additional padding is in octets, and the last octet of the padding is a count of how many padding octets are included (including itself) and thus should be ignored.
  • C (compression) field 256 is a single bit that, when set (e.g., has a value of 1), indicates that the data in SDP data field 284 has been compressed.
  • Different types of compression can be used, such as using Zlib compression as discussed in ZLIB Compressed Data Format Specification version 3.3, Network Working Group Request for Comments (RFC) 1950, May 1996.
  • Res (reserved) field 258 is a 4-bit reserved field. In certain implementations, Res field 258 should be set to zero.
  • PT (payload type) header field 260 is a 7-bit field set to a value (e.g., 141) to indicate that RTCP message 250 embeds a session description message.
  • Length field 262 is a 16-bit field that identifies the length of RTCP message 250. This length can be generated by summing the lengths of the various fields in RTCP message 250, including any headers and any padding. In certain implementations, the length is identified in 32-bit quantities minus one.
  • SDPMsgHash (SDP message hash) field 264 is a 16-bit field used to identify the session description message included in RTCP message 250 and an address (e.g., IP address) of the sender (e.g., server device 104).
  • the identifier in field 264 is calculated as a check-sum over the session description message and the address, so that if either changes, the value of the identifier in field 264 is also changed.
  • the value of SDPMsgHash field 264 is calculated in the same manner as the "msg id hash" field described in the Session Announcement Protocol (SAP), Network Working Group Request for Comments (RFC) 2974, October 2000. If the session description message is fragmented across multiple RTCP messages, as discussed below, the value of SDPMsgHash field 264 of each fragment should be identical.
  • F (more fragments) field 266 is a single bit that, when set (e.g., has a value of 1), indicates that the session description message has been fragmented into multiple RTCP messages, and that the current RTCP message does not contain the last fragment of the session description message. If F field 266 is not set (e.g., has a value of 0), then the session description message has not been fragmented (the complete session description message is included in RTCP message 250), or the session description message has been fragmented and RTCP message 250 contains the last fragment of the session description message.
  • FragSeqNum (fragment sequence number) field 268 is a 15-bit field used to identify different fragments of a session description message.
  • the fragments of a session description message are assigned identifiers in some manner known to both server device 104 and client device 102. For example, the identifiers may be assigned sequentially starting with the value of 0, so the first fragment has a value 0, the second a value 1, the third a value 2, and so forth. If RTCP message 250 does not contain a fragment of a session description message (i.e., RTCP message 250 contains a complete session description message), then FragSeqNum field 268 should be set to 0.
  • NumRtpState (number RTP state) field 270 is a 16-bit field used to specify the number of RTP-State blocks contained in RTCP message 250. Each RTP-State block is 14 bytes in size. The "NumRtpState" field is set to 0 when no RTP-State blocks are present. In the illustrated example of RTCP message 250, there is one RTP-State block 292. If there are multiple RTP-State blocks, then a field 272, 274, 276, 278, 280, and 282 is included for each of the multiple RTP-State blocks. If a session description message is fragmented into multiple RTCP messages 250, then only the RTCP message 250 containing the first fragment of the session description message should contain an RTP-State block(s).
  • a field 272 is a 1-bit field that is not set (e.g., has a value of 0) if PT field 274 contains a valid RTP Payload Type number. If A field 272 is not set, the information in RTP-State block 292 only applies to the RTP Payload Type number identified in PT field 274 and the SDP Flow ID identified in Flow ID field 276. If A field 272 is set (e.g., has a value of 1), then PT field 274 should be ignored, and the RTP-State block 292 applies to all RTP packets for the SDP Flow ID identified in Flow ID field 276, irrespective of the RTP Payload Type used.
  • PT field 274 is a 7-bit field specifying the RTP Payload Type number for the information in RTP-State block 292. If A field 272 is set (e.g., has a value of 1), then PT field 274 is not used and should be set to 0.
  • SSRC (synchronization source) field 278 is a 32-bit field which specifies the RTP SSRC field value used for the media stream which is identified by Flow ID field 276. If A field 272 is not set (e.g., has a value of 0), then SSRC field 278 only applies to RTP packets for this media stream that use the RTP Payload Type given by PT field 274.
  • RtpTime (RTP time) field 280 is a 32-bit field that specifies the value of the RTP Timestamp field that an RTP packet would have, if that packet was sent at exactly the beginning of the media stream identified by Flow ID field 276. For example, if the timeline of the media presentation begins at time T, the value of RtpTime field 280 is the value of the RTP Timestamp field of a packet that would be sent at exactly time T, even if no such RTP packet actually exists for the media stream identified by Rtp-State block 292.
  • RtpSeq (RTP sequence) field 282 is a 16-bit field that gives the value of the RTP sequence number field of the first RTP packet that is sent for the media stream identified by Flow ID field 276. If A field 272 is not set (e.g., has a value of 0), then RtpSeq field 282 only applies to RTP packets for this media stream that use the RTP Payload Type given by PT field 274.
  • SDP data field 284 is the session description message embedded in RTCP message 250. In situations where the session description message is fragmented, SDP data field 284 contains only a portion of the session description message (e.g., a single fragment of the session description message). In certain implementations, the session description message is a complete SDP description in UTF-8 format.
  • FIG. 6 illustrates an example session description message format. Although illustrated as a specific example in FIG. 6 , the session description message could have a format with fields or portions in different orders, or alternatively spread across different messages.
  • Session description message 320 includes a session level description portion 322 and zero or more media level description portions 324.
  • Session level description portion 322 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 322, on the other hand, includes one or more fields having data that applies only to a single media stream.
  • the data fields in media level description portion 322 describe properties for particular media streams. These properties may be in addition to properties described in session level description portion 322, or in place of properties described in session level description portion 322. For example, one or more properties in a particular media level description portion 322 may override, for the particular media stream associated with that particular media level description portion 322, properties identified in session level description portion 322.
  • Session description message 320 and the structure of message 320 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.
  • Session level description portion 322 begins with a particular field, referred to as the protocol version field.
  • media level description portions 324 each start with a particular field, referred to as a media name and transport address field.
  • 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).
  • Table I below illustrates example fields that may be included in session level description portion 322.
  • 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.
  • 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.
  • session name s The name of the session.
  • session information i Information about the session.
  • URI of description u A pointer to additional information about the session.
  • connection information c Connection data describing the connection for the session, such as network type, type of addressing being used, and a connection address.
  • 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.
  • 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.
  • Table III below illustrates example fields that may be included in a media level description portion 324.
  • 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.
  • the media announcement field is required whereas all other fields in Table III are optional.
  • Table III Name Type Description media announcement m The media type of the media stream, the transport 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 information c Connection data describing the connection for the media stream, such as network type, type of addressing being used, and a connection address.
  • bandwidth information b The proposed bandwidth to be used by the media 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.
  • FIG. 7 is a flowchart illustrating an example process 350 for embedding session description messages in an RTCP message when using a server-side play list.
  • FIG. 7 shows acts performed by a media content source, such as a server device 104 (e.g., of FIGS. 1 , 2 , 3 , or 4 ).
  • next piece of media content in the play list is identified (act 352).
  • the next piece is the first piece identified in the play list.
  • the next piece of media content is the piece that follows the piece whose end was reached. It should be noted that this next piece may be in the order defined by the play list, or the user may be able to navigate to a different piece within the play list (e.g., the user may be able to request that a particular piece in the play list be skipped or jumped over).
  • Information describing the identified piece of media content is then obtained (act 354).
  • This information can be obtained in one or more different manners.
  • One manner in which this information can be obtained is retrieval from a file or record.
  • at least some of the information is stored in a file or record associated with the identified piece of media content. This file or record is accessed in act 354 to retrieve the information stored therein.
  • Another manner in which this information can be obtained is receipt from a human user.
  • at least some of the information is received from a human user.
  • These user inputs are used in act 354 as at least some of the information to be included in the session description message.
  • Another manner in which this information can be obtained is automatic detection.
  • at least some of the information can be obtained automatically by a computing device by analyzing the source of the identified piece of media content or the identified piece of media content itself. This automatically detected information is used in act 354 as at least some of the information to be included in the session description message.
  • An RTCP message having a session description message that includes the obtained information is then created (act 356).
  • this RTCP message is in the form of RTCP message 250 of FIG. 5 discussed above.
  • the created RTCP message is then sent to the intended recipient of the next piece of media content (act 358).
  • the intended recipient of the next piece of media content is the device to which the media content is being streamed (e.g., client device 102 of FIGS. 1 , 2 , 3 , or 4 ).
  • the created RTCP message is included in an RTCP packet that is included as part of the streaming media being streamed to the intended recipient.
  • the first piece of media content identified in a play list may have two streams (e.g., an audio stream and a video stream), while the second piece of media content identified in a play list may have three streams (e.g., an audio stream, a video stream, and a text subtitle stream).
  • each media stream is typically using a different UDP channel that is received at the recipient on a different UDP port. If the recipient only opened two ports for the first piece of media content (e.g., one port for the audio stream and one port for the video stream), there would be no port available for the recipient to receive the text subtitle stream of the second piece of media content.
  • Such situations can be resolved in different manners.
  • such situations are resolved by streaming the additional media stream(s) over an open HTTP connection using TCP.
  • An indication is included in RTCP message 250 (e.g., as an additional RTP-State block 292 for each additional media stream) that the additional media stream(s) is being streamed in this manner.
  • such situations are resolved by having the recipient open one or two extra ports, often referred to as wildcard ports.
  • Each of these wildcard ports can be used to receive any media stream that the server device sends to the recipient.
  • An indication is included in RTCP message 250 (e.g., as an additional RTP-State block 292 for each additional media stream) of which of the wildcard ports the additional media stream(s) is being streamed to.
  • such situations are resolved by the server device sending the session description message to the recipient (e.g., in an RTCP message 250) that identifies all of the media streams available for the second piece of media content.
  • the server device then waits for the recipient to select which of the media streams the recipient desires to receive.
  • the recipient will make a selection (e.g., automatically or based on user input at the recipient), and send to the server device an indication of which media stream(s) were selected and which ports the selected media stream(s) are to be streamed to.
  • FIG. 8 is a flowchart illustrating an example process 380 for receiving session description messages in an RTCP message when using a server-side play list.
  • FIG. 8 shows acts performed by a recipient of streaming media, such as a client device 102 (e.g., of FIGS. 1 , 2 , 3 , or 4 ).
  • an RTCP message is received from a media content source (act 382).
  • the media content source is, for example, a server device 104 of FIGS. 1 , 2 , 3 , or 4 .
  • a session description message for a next piece of media content in the play list is extracted from the RTCP message (act 384).
  • this next piece of media content is the first piece of media content in the play list.
  • the next piece of media content is the next piece identified in the play list. It should be noted that this next piece may be in the order defined by the play list, or the user may be able to navigate to a different piece within the play list (e.g., the user may be able to request that a particular piece in the play list be skipped or jumped over).
  • session description message for the next piece of media content is typically received prior to playback of the current piece of media content being finished (to allow client device 102 to immediately begin playback of the next piece of media content when playback of the current piece of media content is finished).
  • the extracted session description message is then used in processing of the next piece of media content (act 386). This processing typically includes playback of the next piece of media content at client device 102.
  • FIG. 9 illustrates a system 500 for multicasting multimedia presentations, according to one embodiment.
  • system 500 includes a content source 502, a server 504, and clients 506 1 -506 X that are connected to server 504 via a network 508.
  • Network 508 can be any suitable type of wired (including optical fiber) or wireless network (e.g., RF or free space optical).
  • network 508 is the Internet, but in other embodiments network 508 can be a local area network (LAN), a campus area network, etc.
  • LAN local area network
  • campus area network etc.
  • server 504 includes an announcement generator 510.
  • announcement generator 510 generate streams containing information regarding multimedia presentations to be multicast over network 508. The operation of this embodiment of system 500500 in multicasting multimedia presentations is described below in conjunction with FIG. 10 through FIG. 12 .
  • FIG. 10 illustrates server operational flow of system 500500 of FIG. 9 in multicasting a multimedia presentation, according to one embodiment.
  • server 504 operates as follows to multicast a multimedia presentation.
  • server 504 receives a multimedia presentation via a connection 512.
  • server 504 receives the multimedia presentation from content source 502 via a link 512.
  • content source 502 provides multimedia content to be multicast over network 508.
  • the multimedia content can be generated in any suitable manner.
  • the multimedia content may be previously recorded/generated content that is then stored in a datastore (not shown), or a live performance that is captured (e.g., using a video camera, microphone, etc.) and encoded (encoder not shown).
  • the multimedia presentation will include multiple streams.
  • the multimedia presentation may include a video stream, an audio stream, another video stream encoded at a lower bit rate and another audio streams encoded at a lower bit rate.
  • the multimedia presentation may have more or fewer streams than those described in this example application.
  • server 504 receives the multimedia presentation in the form of one or more streams in block 524.
  • server 504 forms an announcement stream and multicasts the announcement stream over network 508 via a link 514.
  • announcement generator 510 of server 504 forms the announcement stream.
  • announcement generator 510 may be configured by an administrator, while in other embodiments announcement generator 510 may be configured to process stream(s) received in block 524 and extract information from the stream(s) to form the announcement stream
  • server 504 multicasts the announcement stream on a dedicated announcement channel (i.e., a channel without announcement information related to other multimedia presentations).
  • a channel can be a logical address such as a multicast Internet protocol (IP) address and port.
  • IP Internet protocol
  • a client can join a channel by listening to the logical address and port associated with the channel.
  • Clients may learn of the logical address in any suitable manner such as but not limited to email, invitations, website postings, and conventional Session Announcement Protocol (SAP) multicasts (e.g., as defined in Specification, IETF RFC-2974, entitled "Session Announcement Protocol".
  • SAP multicasts to announce a multimedia presentation, the SAP multicast need not include the detailed presentation description information that would be provided in an "in-line" announcement stream (described in more detail below).
  • the announcement stream is multicast "in-line" with a stream containing multimedia data.
  • the stream of multimedia data can be multicast using packets according to the Real-time Transport Protocol (RTP) and the announcement stream can be multicast using packets according to the Real-time Transport Control Protocol (RTCP).
  • RTP Real-time Transport Protocol
  • RTCP Real-time Transport Control Protocol
  • the RTP is defined in Request For Comments (RFC) 3550, Internet Engineering Task Force (IETF), July, 2003 (which includes the specification of the RTCP as well).
  • the RTP is extended to support announcement data in RTCP packets.
  • the announcement data can be sent "in-line" in the same RTP packets (or other protocol packets/datagrams) as the multimedia data.
  • the announcement channel can be out-of-band (e.g., when the announcement channel is multicast using SAP.
  • the announcement stream contains information that describes the multimedia presentation such as, for example, identification of various channels used to multicast the multimedia presentation, descriptions of the stream (e.g., indicating the type of stream (e.g., video or audio); bit-rate of the stream; language used in the stream, etc.) being transported by each of the channels, error correction information; security/authentication information; encryption information; digital rights management (DRM) information, etc.
  • the announcement stream is repeatedly multicast during the multimedia presentation so that clients joining at different times may receive the multimedia presentation description information. A client receiving this presentation description information via the announcement stream can then determine which channel(s) are suitable to join based in view of its resources.
  • server 504 multicasts stream(s) selected from the stream(s) of the multimedia presentation received in block 524. In some scenarios, server 504 multicasts all of the streams received in block 524. In some embodiments, an administrator can configure server 504 to multicast particular streams in preselected channels. In one embodiment, server 504 supports at least an announcement channel, a video channel and an audio channel. More typically, server 504 will also support additional channels of video and audio streams of different bit rates to accommodate clients having different resources available to process the multimedia presentation.
  • server 504 may be configured to support an announcement channel 532, an acceleration channel 534 (described below in conjunction with FIGS. 15 and 16 ), a high quality video channel 536, a high quality audio channel 538, an application channel 540, alternative language channels 542 1 -542 N , and alternative bit rate channels 544 1 -544 M (for audio and/or video streams).
  • application channel 540 can be used to multicast data used by applications expected to be running locally on the clients (e.g., a media player, or other applications that may require a plug-in to use the multicasted application data such as Microsoft PowerPoint® data).
  • server 504 may map a stream into only one channel, multiple channels or no channels. For example, if multimedia presentation from content source 502 includes an English language stream and a Spanish language stream, server 504 may be configured to map the Spanish language stream into all of channels 542 1 -542 N , or only channel 542 1 , or to no channel at all.
  • the "layout" of the channels is preselected.
  • the channels may be a set of sequential IP addresses in the range of IP addresses assigned for multicasting (i.e., the range of IP address 224.0.0.0 to IP address 239.255.255.255).
  • announcement channel 532 may be assigned to IP address 231.0.0.1
  • acceleration channel 534 may be assigned to IP address 231.0.0.2
  • high quality video channel 536 may be assigned to IP address 231.0.0.3, and so on.
  • the channels may be a set of sequential ports of a group IP address.
  • announcement channel 532 may be assigned to port 231.0.0.1:5000
  • acceleration channel 534 may be assigned to port 231.0.0.1:500
  • high quality video channel 536 may be assigned to port 231.0.0.1:5004, and so on (so that ports 5001, 5003 and 5005 can be used for the RTCP packets).
  • the approaches used by the above embodiments of system 500500 have several advantages. For example, because the announcement stream is multicast on a dedicated channel, a client can more quickly obtain the presentation description information, thereby advantageously reducing start up latency. In contrast, a conventional SAP multicast approach typically has a larger start up latency because SAP multicasts generally announce a large number of multicasts, which tends to reduce the frequency at which announcements for a particular multimedia presentation is multicast (which in turn tends to increase start up latency).
  • system 500 do not require that clients have a back channel to server 504, thereby providing more flexibility in delivering multimedia presentations to a desired audience.
  • system 500 eliminates the need for the server to provide a "multicast information" file required in the previously-described conventional system, and, thus, the costs involved in maintaining and publishing this file.
  • clients may choose to join particular channels without waiting to receive and process the multimedia presentation description information from announcement channel 532.
  • an aggressive client typically a client with relatively large resources
  • a client with large resources can be a client having a computing platform with high speed CPU and large buffering resources, and is connected to a highspeed computer network with a relatively large amount of available bandwidth. The high speed CPU and large buffering resources significantly reduce the risk of losing data.
  • FIG. 12 illustrates operational flow of client 506 1 ( FIG. 9 ) in receiving a multimedia presentation that is being multicast by server 504 ( FIG. 9 ), according to one embodiment.
  • Clients 506 2 -506 X ( FIG. 9 ) can operate in a substantially identical manner.
  • client 506 1 operates as follows in receiving the multimedia presentation.
  • client 506 1 having already received the logical address of the announcement channel of a multimedia presentation, joins announcement channel 532.
  • server 504 repeatedly multicasts presentation description information on a dedicated announcement channel.
  • client 506 1 can relatively quickly receive the presentation description information compared to conventional systems that generally multicast description information of a relatively large number of multimedia and/or other types of presentations.
  • client 506 1 then joins one or more of the channels that provide multimedia data streams, which are described in the received announcement stream.
  • client 506 1 can determine which channel(s) to join to have an optimal experience using the resources available to client 506 1 .
  • Client 506 1 then can receive the selected stream(s) of the multimedia presentation.
  • FIG. 12A illustrates operational flow of client 506 1 ( FIG. 9 ) in receiving a multimedia presentation that is being multicast by server 504 ( FIG. 9 ), according to another embodiment.
  • Clients 506 2 -506 X ( FIG. 9 ) can operate in a substantially identical manner.
  • client 506 1 operates as follows in receiving the multimedia presentation.
  • client 506 1 substantially concurrently performs block 562 (to join announcement channel 532 as described above) and a block 570.
  • client 506 1 also joins one or more preselected channels of the multimedia presentation in addition to announcement channel 532.
  • server 504 can be configured to multicast streams in preselected channels in a predetermined manner.
  • client 506 1 can take advantage of the preselected channel assignments to join desired channels without having to receive the presentation description information from announcement channel 532.
  • client 506 1 has relatively large resources to receive and process multimedia presentations, capable of handling typical high quality video and high quality audio streams. With these resources, client 506 1 can be configured to immediately join channels 536 and 538 to receive high quality video and high quality audio streams to reduce start up latency with a relatively high expectation that client 506 1 can properly process the streams.
  • client 506 1 determines whether it can optimally process the stream(s) received from the channel(s) it joined in block 570 in view of the resources available to client 506 1 .
  • client 506 1 uses the presentation description information received from announcement channel 532 to determine whether its resources can handle the streams received on these channels.
  • the streams of channels joined in block 570 may have bit rates (which will be described in the announcement stream) that are too great for client 506 1 to process without losing data (which can result in choppy audio playback for audio streams or blocky video playback for video streams).
  • client 506 1 determines in block 572 that it can optimally process the stream(s) of the preselected channel(s)
  • client 506 1 continues to receive the stream(s) from the channel(s) client 506 1 joined in block 570 until the multicasted multimedia presentation terminates.
  • client 506 1 in block 572 determines that it cannot optimally process the stream(s) of the preselected channel(s)
  • the operational flow proceeds to block 564 (previously described in conjunction with FIG. 12 ).
  • client 506 1 join one or more other channels that carry multimedia data streams that client 506 1 can optimally process.
  • client 506 1 may quit the preselected channels joined in block 570.
  • Client 506 1 continues to receive the stream(s) from the channels joined in block 564 until the multicasted multimedia presentation terminates or chooses to leave the channel.
  • FIG. 13 illustrates some of the components of server 504 ( FIG. 9 ), according to one embodiment.
  • server 504 in addition to announcement generator 510 (described above in conjunction with FIG. 9 ), server 504 includes a configuration controller 582, a configurable stream mapper 584, a source interface 586 and a network interface 588.
  • these elements are software modules or components that can be executed by a computing environment of server 504.
  • Source interface 586 is configured to receive one or more multimedia streams from content source 502 ( FIG. 9 ) via link 512.
  • Configurable stream mapper 582 is configured to receive the streams from source interface 586, an announcement stream from announcement generator 510, and control information from configuration controller 582.
  • configurable stream mapper 584 functions like a switch in mapping or directing one or more of the streams received from source interface 586 to multicast channel(s).
  • Network interface 588 multicasts the selected streams over network 508 ( FIG. 9 ).
  • configuration controller 582 configures configurable stream mapper 584 to map the received stream(s) of the multimedia presentation into channel(s).
  • configuration controller 582 directs announcement generator 510 in generating announcements. Operational flow of one embodiment of configuration controller 582 in is described below in conjunction with FIGS. 13 and 14 .
  • FIG. 14 illustrates operational flow of configuration controller 582 ( FIG. 13 ) in multicasting a multimedia presentation, according to one embodiment.
  • configuration controller 582 operates to multicast a multimedia presentation as described below.
  • this embodiment of configuration controller 582 receives configuration information from an administrator.
  • the administrator can manually provide configuration information to configuration controller 582 of server 504.
  • This configuration information may define each of the channels in terms of logical address, and include presentation description information (previously described).
  • the presentation information may include the media type(s) of the stream(s) of the multimedia presentation to be multicast, the bit-rate(s) of the stream(s); the language(s), error correction information; security/authentication information; encryption information; digital rights management (DRM) information, etc.
  • DRM digital rights management
  • configuration controller 586 may be configured to extract the presentation description information from the streams themselves, (e.g., from header or metadata information included in the streams) after being received from content source 502 ( FIG. 9 ) via source interface 586.
  • configuration controller 582 configures stream mapper 584 to map the announcement stream from announcement generator 510 and the multimedia data stream(s) from source interface 586 to the channels as described in the presentation description information.
  • This announcement stream is repetitively multicast over the announcement channel by server 504 during the multicast of the multimedia presentation.
  • configuration controller 582 provides presentation description information for the stream(s) to announcement generator 510.
  • announcement generator 510 forms the announcement stream that includes the presentation description information.
  • the "layout" of the channels may be preselected.
  • a client would be given a logical address (e.g., a URL) for joining a multicast multimedia presentation.
  • that first logical address is preselected to carry the announcement stream in one embodiment.
  • the next sequential logical address is preselected to carry the acceleration channel, while the next sequential logical address is preselected to carry a high quality video stream, and so on as shown in the embodiment of FIG. 11 .
  • Configuration controller 582 configures stream mapper 584 to map the announcement stream and the multimedia data streams according to the preselected channel layout.
  • FIG. 15 illustrates some of the components of server 504 ( FIG. 9 ), according to another embodiment.
  • This alternative embodiment of server 504 is substantially similar to the embodiment of FIG. 13 , except that this embodiment includes an accelerated stream generator 702.
  • accelerated stream generator 702 is configured to form a stream in which each unit of multimedia data that is multicast contains a current subunit of multimedia data and a preselected number of previous subunits of data. For example, an accelerated stream may be multicast so that a datagram contains the current frame(s) of the multimedia presentation and the frames of the previous five seconds.
  • accelerated stream generator 702 provides the accelerated stream to configurable stream mapper 584 to be mapped into a dedicated acceleration channel such as acceleration channel 534 ( FIG.11 ).
  • an acceleration channel datagram need not include the current frame(s).
  • FIG. 16 illustrates operational flow of server 504 with accelerated stream generator 702 ( FIG. 15 ), according to one embodiment. Referring to FIGS. 15 and 16 , this embodiment of server 504 operates as described below.
  • accelerated stream generator 702 forms a unit of multimedia data for multicast over network 508 ( FIG. 9 ).
  • accelerated stream generator 702 forms the unit using a current subunit of the multimedia presentation data and the previous Z subunits of multimedia presentation data.
  • the unit may be a datagram or packet, and the subunits may be frames of multimedia data.
  • Z is selected to ensure that the unit (i.e., packet or datagram) will contain a key frame needed to render or decode the multimedia data. In other embodiments, Z is selected without regard to whether the unit will be ensured of having a key frame.
  • a block 804 the unit of multimedia data formed in block 802 is multicast over network 508 ( FIG. 9 ).
  • accelerated stream generator 702 provides the unit of multimedia data to configurable stream mapper 584, which then maps the block to the acceleration channel.
  • Server 504 then multicasts the unit of multimedia data over network 508 ( FIG. 9 ) via network interface 588.
  • server 504 multicasts the unit at a rate that is "faster than real time" (i.e., at a bit rate that is faster than the bit rate of the underlying multimedia data). This approach advantageously allows a client having relatively large resources to join the acceleration channel and quickly fill the buffer of its multimedia player in receiving the unit so that rendering or playback can begin more quickly.
  • the multicasted unit of multimedia data includes a key frame.
  • the rate at which server 504 multicasts the unit need not be "faster than real time”. This approach may be used in applications in which the client concurrently joins both the acceleration channel and another channel that multicasts multimedia data so that, in effect, the client receives the multimedia data at a rate that is "faster than real-time.”
  • each unit e.g., datagram
  • Z represents a sliding window of the current subunit (e.g., frame) and the previous Z frames, with Z selected to be large enough to ensure that each unit has enough information to minimize the time needed to allow the client's multimedia player to start rendering/playback of the multimedia presentation.
  • Z may be selected to ensure that each unit has a key frame.
  • units of video and audio data are multicasted in an alternating manner on the same channel if the multimedia presentation includes both audio and video streams.
  • separate acceleration channels may be used for audio and video streams.
  • one embodiment of accelerated stream generator waits until at least Z subunits of multimedia data have been multicasted in the non-accelerated channel(s) before forming a unit of data in block 802.
  • FIG. 17 illustrates client operational flow in receiving an accelerated stream, according to one embodiment.
  • a client e.g., one of clients 506 1 -506 X of FIG. 9 .
  • the acceleration channel is part of the preselected channel layout and the client can join it either concurrently or without joining the announcement channel.
  • the acceleration channel can be advantageously used by a client having relatively large resources for receiving and processing multimedia presentations so that the client may reduce start up latency.
  • the client receives one or more units of multimedia data from the acceleration channel.
  • each unit of multimedia data is generated as described above in conjunction with FIG. 16 .
  • the client can then process each unit of multimedia data to relatively quickly begin the rendering or playback process.
  • the client receives a unit of video data and a unit of audio data, with the video data containing a key frame so that the client can begin the rendering/playback process as soon as possible.
  • a unit need not have a key frame in other embodiments.
  • the client can then join a non-accelerated channel such as high quality video channel 536 and high quality audio channel 538.
  • a non-accelerated channel such as high quality video channel 536 and high quality audio channel 538.
  • the non-accelerated channels that the client joins are preselected using the above-described preselected channel layout.
  • the client joins channel(s) based on the presentation description information contained in announcement stream.
  • the client quits the acceleration channel. In one embodiment, the client quits the acceleration channel immediately after receiving the unit or units of multimedia data needed to begin the rendering/playback process or processes.
  • blocks 902 through 908 are described as being performed sequentially, in the flow chart of FIG. 17 (as well as the other flow charts described herein) the blocks may be performed in orders different from that shown, or with some blocks being performed more than once or with some blocks being performed concurrently or a combination thereof.
  • blocks 902 and 906 are performed in parallel so that the operational flow is that the client joins accelerated and non-accelerated channels concurrently.
  • Block 904 is performed sequentially after block 902, with block 904 and 906 proceeding to block 908.
  • FIG. 17A illustrates an example scenario in which a client may join the acceleration channel and some preselected channels, and then join other channels (e.g., based on announcement information received from the announcement channel).
  • the client joins the acceleration channel (i.e., block 902) concurrently with joining one or more preselected non-accelerated channels (i.e., block 906).
  • the client receives one or more units of multimedia data from the acceleration channel (i.e., block 904) as well as multimedia and announcement data from the non-accelerated channel(s).
  • the client may decide to quit the preselected channel(s) and join other non-accelerated channels (i.e., blocks 572, 564 and 574).
  • the various multicasting embodiments described above may be implemented in computer environments of the server and clients.
  • An example computer environment suitable for use in the server and clients is described below in conjunction with FIG. 18 .
  • FIG. 18 illustrates a general computer environment 1000, which can be used to implement the techniques described herein.
  • the computer environment 1000 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 1000 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example computer environment 1000.
  • Computer environment 1000 includes a general-purpose computing device in the form of a computer 1002.
  • the components of computer 1002 can include, but are not limited to, one or more processors or processing units 1004, system memory 1006, and system bus 1008 that couples various system components including processor 1004 to system memory 1006.
  • System bus 1008 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.
  • bus 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, a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus, a PCI Express bus, a Universal Serial Bus (USB), a Secure Digital (SD) bus, or an IEEE 1394, i.e., FireWire, bus.
  • ISA Industry Standard Architecture
  • MCA Micro Channel Architecture
  • EISA Enhanced ISA
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnects
  • Mezzanine bus a PCI Express bus
  • USB Universal Serial Bus
  • SD Secure Digital
  • IEEE 1394 i.
  • Computer 1002 may include a variety of computer readable media. Such media can be any available media that is accessible by computer 1002 and includes both volatile and non-volatile media, removable and non-removable media.
  • System memory 1006 includes computer readable media in the form of volatile memory, such as random access memory (RAM) 1010; and/or non-volatile memory, such as read only memory (ROM) 1012 or flash RAM.
  • RAM random access memory
  • ROM read only memory
  • BIOS Basic input/output system
  • BIOS Basic input/output system
  • RAM 1010 typically contains data and/or program modules that are immediately accessible to and/or presently operated on by processing unit 1004.
  • Computer 1002 may also include other removable/non-removable, volatile/non-volatile computer storage media.
  • FIG. 10 illustrates hard disk drive 1016 for reading from and writing to a non-removable, non-volatile magnetic media (not shown), magnetic disk drive 1018 for reading from and writing to removable, non-volatile magnetic disk 1020 (e.g., a "floppy disk"), and optical disk drive 1022 for reading from and/or writing to a removable, non-volatile optical disk 1024 such as a CD-ROM, DVD-ROM, or other optical media.
  • Hard disk drive 1016, magnetic disk drive 1018, and optical disk drive 1022 are each connected to system bus 1008 by one or more data media interfaces 1025.
  • hard disk drive 1016, magnetic disk drive 1018, and optical disk drive 1022 can be connected to the system bus 1008 by one or more interfaces (not shown).
  • 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 1002.
  • a hard disk 1016, removable magnetic disk 1020, and removable optical disk 1024 it is 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 example computing system and environment.
  • RAM random access memories
  • ROM read only memories
  • EEPROM electrically erasable programmable read-only memory
  • Any number of program modules can be stored on hard disk 1016, magnetic disk 1020, optical disk 1024, ROM 1012, and/or RAM 1010, including by way of example, operating system 1026, one or more application programs 1028, other program modules 1030, and program data 1032. Each of such operating system 1026, one or more application programs 1028, other program modules 1030, and program data 1032 (or some combination thereof) may implement all or part of the resident components that support the distributed file system.
  • a user can enter commands and information into computer 1002 via input devices such as keyboard 1034 and a pointing device 1036 (e.g., a "mouse").
  • Other input devices 1038 may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and/or the like.
  • input/output interfaces 1040 that are coupled to system bus 1008, but may be connected by other interface and bus structures, such as a parallel port, game port, or a universal serial bus (USB).
  • Monitor 1042 or other type of display device can also be connected to the system bus 1008 via an interface, such as video adapter 1044.
  • other output peripheral devices can include components such as speakers (not shown) and printer 1046, which can be connected to computer 1002 via I/O interfaces 1040.
  • Computer 1002 can operate in a networked environment using logical connections to one or more remote computers, such as remote computing device 1048.
  • remote computing device 1048 can be a PC, portable computer, a server, a router, a network computer, a peer device or other common network node, and the like.
  • Remote computing device 1048 is illustrated as a portable computer that can include many or all of the elements and features described herein relative to computer 1002.
  • computer 1002 can operate in a non-networked environment as well.
  • Logical connections between computer 1002 and remote computer 1048 are depicted as a local area network (LAN) 1050 and a general wide area network (WAN) 1052.
  • LAN local area network
  • WAN wide area network
  • Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.
  • computer 1002 When implemented in a LAN networking environment, computer 1002 is connected to local network 1050 via network interface or adapter 1054. When implemented in a WAN networking environment, computer 1002 typically includes modem 1056 or other means for establishing communications over wide network 1052. Modem 1056, which can be internal or external to computer 1002, can be connected to system bus 1008 via I/O interfaces 1040 or other appropriate mechanisms. It is to be appreciated that the illustrated network connections are examples and that other means of establishing at least one communication link between computers 1002 and 1048 can be employed.
  • remote application programs 1058 reside on a memory device of remote computer 1048.
  • applications or 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 computing device 1002, and are executed by at least one data processor of the computer.
  • program modules include routines, programs, objects, components, data structures, etc. for performing particular tasks or implement particular abstract data types.
  • program modules and the like may be executed as native code or may be downloaded and executed, such as in a virtual machine or other just-in-time compilation execution environment.
  • functionality of the program modules may be combined or distributed as desired in various embodiments.
  • Computer readable media can be any available media that can be accessed by a computer.
  • Computer readable media may comprise "computer storage media” and "communications media.”
  • 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, but is not limited to, 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, or any other medium which can be used to store the desired information and which can be accessed by a computer.
  • Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave or other transport mechanism.
  • Communication media also includes any information delivery media.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • Primary Health Care (AREA)
  • Tourism & Hospitality (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Strategic Management (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Computer And Data Communications (AREA)

Claims (50)

  1. Support unique ou multiple lisible par un ordinateur comportant une pluralité d'instructions stockées sur celui-ci qui, lorsqu'elles sont exécutées par un ou plusieurs processeurs d'un appareil, font en sorte que le ou les processeurs :
    - reçoivent (382), depuis une source de contenu de média, un message de protocole de contrôle en temps réel, RTCP ;
    - extraient (384), du message de RTCP, un message de description de session (320) associé à une pièce parmi une pluralité de pièces de contenu de média dans une liste de lecture de contenu de média en cours de diffusion en flux de la source de contenu de média à l'appareil, le message de description de session étant un message de description de session d'un protocole de description de session, SDP ; et
    - traitent (386) la pièce parmi la pluralité de pièces de contenu de média en fonction, au moins en partie, du message de description de session.
  2. Support unique ou multiple lisible par un ordinateur selon la revendication 1, dans lequel le message de RTCP fait partie d'un paquet de RTCP.
  3. Support unique ou multiple lisible par un ordinateur selon la revendication 1, dans lequel les instructions faisant en sorte que l'un ou plusieurs processeurs traitent la pièce parmi la pluralité de pièces de contenu de média en fonction, au moins en partie, du message de description de session font en sorte que l'un ou plusieurs processeurs reproduisent la pièce parmi la pluralité de pièces de contenu de média au niveau de l'appareil.
  4. Support unique ou multiple lisible par un ordinateur selon la revendication 1, dans lequel les instructions font en outre en sorte que l'un ou plusieurs processeurs répètent la réception, l'extraction et le traitement de chacune des autres pièces de contenu de média parmi la pluralité de pièces de contenu de média.
  5. Support unique ou multiple lisible par un ordinateur selon la revendication 1, dans lequel le message de RTCP comprend :
    - un premier champ contenant des données identifiant le message de RTCP comme étant d'un type intégrant le message de description de session ;
    - un deuxième champ contenant des données qui sont le message de description de session ; et
    - un troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ et de la longueur du troisième champ.
  6. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un ou plusieurs blocs d'état RTP, chaque bloc d'état RTF identifiant des informations spécifiques au RTP sur un flux de média de la présentation de média ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur de l'un ou plusieurs blocs d'état RTP.
  7. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données qui identifient la version du protocole de transport en temps réel, RTP, en cours d'utilisation pour diffuser en flux la présentation de média et le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  8. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant si des éléments additionnels de remplissage sont inclus dans le message de RTCP ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  9. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant si les données du deuxième champ ont été compressées ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  10. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant le message de description de session et l'adresse de l'expéditeur du message de description de session ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  11. Support unique ou multiple lisible par un ordinateur selon la revendication 10, dans lequel les données identifiant le message de description de session et l'adresse de l'expéditeur du message de description de session comprennent une somme de contrôle calculée pour le message de description de session et l'adresse de l'expéditeur du message de description de session.
  12. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant le nombre de blocs d'état RTF contenus dans le message de RTCP ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  13. Support unique ou multiple lisible par un ordinateur selon la revendication 12, dans lequel le quatrième champ contient une valeur de zéro pour indiquer qu'aucun bloc d'état RTF n'est contenu dans le message de RTCP.
  14. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant si les données dans un bloc d'état RTP du message de RTCP s'appliquent à tous les paquets RTP ayant un identifiant ID Flow SDP particulier ou seulement aux paquets RTP ayant un numéro de type de charge transportée RTF particulier ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  15. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant un numéro de type de charge transportée RTP pour un bloc d'état RTF du message de RTCP ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  16. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant un flux de média de la présentation de média à laquelle un bloc d'état RTF du message de RTCP se réfère ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  17. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant la source d'un flux de média de la présentation de média à laquelle un bloc d'état RTF du message de RTCP se réfère ; et l'identifiant ID Flow ou seulement aux paquets RTP ayant un numéro de type de charge transportée RTF particulier ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  18. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant la valeur d'un champ d'estampille temporelle RTF qu'un paquet RTP pour un flux de média de la présentation de média aurait si le paquet RTP avait été envoyé au début du flux de média ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  19. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données identifiant la valeur d'un champ de numéro de séquence RTP d'un premier paquet RTP envoyé pour un flux de média de la présentation de média ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ et de la longueur du quatrième champ.
  20. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données indiquant que le message de RTCP contient un fragment du message de description de session ; un cinquième champ contenant des données identifiant le fragment ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ, de la longueur du quatrième champ et de la longueur du cinquième champ.
  21. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données qui identifient la version du protocole de transport en temps réel, RTP, en cours d'utilisation pour diffuser en flux la présentation de média ;
    - un cinquième champ contenant des données identifiant si des éléments additionnels de remplissage sont inclus dans le message de RTCP ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ, de la longueur du quatrième champ et de la longueur du cinquième champ.
  22. Support unique ou multiple lisible par un ordinateur selon la revendication 5, dans lequel le message de RTCP comprend en outre :
    - un quatrième champ contenant des données qui identifient la version du protocole de transport en temps réel, RTP, en cours d'utilisation pour diffuser en flux la présentation de média ;
    - un cinquième champ contenant des données identifiant si des octets additionnels de remplissage sont inclus dans le message de RTCP ;
    - un sixième champ contenant des données identifiant si les données du deuxième champ ont été compressées ; un septième champ contenant des données identifiant le message de description de session et l'adresse de l'expéditeur du message de description de session ;
    - un huitième champ contenant des données identifiant le nombre de blocs d'état RTF contenus dans le message de RTCP ;
    - un neuvième champ contenant des données identifiant si les données dans un bloc d'état RTF du message de RTCP s'appliquent à tous les paquets RTP ayant un identifiant ID Flow SDP particulier ou seulement aux paquets RTP ayant un numéro de type de charge transportée RTP particulier ;
    - un dixième champ contenant des données identifiant un numéro de type de charge transportée RTP pour le bloc d'état RTF du message de RTCP ;
    - un onzième champ contenant des données identifiant un flux de média de la présentation de média à laquelle le bloc d'état RTP du message de RTCP se réfère ;
    - un douzième champ contenant des données identifiant la source du flux de média de la présentation de média à laquelle le bloc d'état RTP du message de RTCP se réfère ;
    - un treizième champ contenant des données identifiant la valeur d'un champ d'estampille temporelle RTP qu'un paquet RTP pour le flux de média de la présentation de média aurait si le paquet RTP avait été envoyé au début de la présentation de média ;
    - un quatorzième champ contenant des données identifiant la valeur d'un champ de numéro de séquence RTP d'un premier paquet RTP envoyé pour le flux de média de la présentation de média ;
    - un quinzième champ contenant des données indiquant que le message de RTCP contient un fragment du message de description de session ;
    - un seizième champ contenant des données identifiant le fragment ; et
    - le troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ, de la longueur du troisième champ, de la longueur du quatrième champ, de la longueur du cinquième champ, de la longueur du sixième champ, de la longueur du septième champ, de la longueur du huitième champ, de la longueur du neuvième champ, de la longueur du dixième champ, de la longueur du onzième champ, de la longueur du douzième champ, de la longueur du treizième champ, de la longueur du quatorzième champ, de la longueur du quinzième champ et de la longueur du seizième champ.
  23. Procédé comprenant les étapes consistant à :
    - recevoir (524) des données d'une présentation multimédia, pour lequel les données incluent une première pluralité de flux ; et
    - multi-diffuser (526) une seconde pluralité de flux qui inclut un flux d'annonce dédié et un premier flux sélectionné parmi la première pluralité de flux, pour lequel le flux d'annonce inclut des informations de description de présentation de la présentation multimédia et est multi-diffusé sur un canal sur bande, pour lequel le flux d'annonce inclut un message de protocole de contrôle en temps réel, RTCP, qui inclut un message de description de session associé à la présentation multimédia, pour lequel le message de description de session est un message de description de session d'un protocole de description de session, SDP.
  24. Procédé selon la revendication 23, pour lequel la seconde pluralité de flux sont multi-diffusés sur des canaux différents.
  25. Procédé selon la revendication 24, pour lequel la seconde pluralité de flux sont multi-diffusés sur des canaux différents prédéterminés.
  26. Procédé selon la revendication 25, pour lequel les canaux différents prédéterminés comprennent des adresses logiques prédéterminées.
  27. Procédé selon la revendication 26, pour lequel les adresses logiques prédéterminées sont des adresses de protocole Internet, IP, avec des points d'accès prédéterminés.
  28. Procédé selon la revendication 25, pour lequel les canaux différents prédéterminés comprennent des points d'accès prédéterminés d'une adresse logique.
  29. Procédé selon la revendication 23, pour lequel la seconde pluralité de flux comprend en outre un deuxième flux incluant une pluralité d'unités de données de la présentation multimédia, chaque unité de la pluralité d'unités comprenant un nombre présélectionné de sous-unités antérieures de données de la présentation multimédia.
  30. Procédé selon la revendication 29, pour lequel chaque unité de la pluralité d'unités inclut une image clé.
  31. Procédé selon la revendication 23, pour lequel la seconde pluralité de flux comprend en outre des flux multiples de données vidéo ayant des débits binaires différents.
  32. Procédé selon la revendication 23, pour lequel la seconde pluralité de flux comprend en outre des flux multiples de données audio ayant des débits binaires différents.
  33. Procédé selon la revendication 23, pour lequel la seconde pluralité de flux comprend en outre des flux multiples de données multimédia dans des langues différentes.
  34. Procédé selon la revendication 23, pour lequel la seconde pluralité de flux comprend en outre un flux de données destiné à être utilisé par une application s'exécutant sur un système client recevant la seconde pluralité de flux.
  35. Procédé selon la revendication 23, pour lequel le flux d'annonce inclut des informations de correction d'erreur.
  36. Procédé selon la revendication 23, pour lequel le flux d'annonce inclut des informations de sécurité.
  37. Procédé selon la revendication 23, pour lequel le flux d'annonce est multi-diffusé sur un canal hors bande.
  38. Procédé selon la revendication 23, pour lequel le flux d'annonce est multi-diffusé pour se conformer à un protocole de contrôle de transport en temps réel, RTCP, le flux d'annonce étant entremêlé en bande avec un flux de données de présentation multimédia qui sont multi-diffusées pour se conformer à un protocole de transport en temps réel, RTF.
  39. Procédé selon la revendication 23, pour lequel le flux d'annonce est multi-diffusé de telle sorte que les données de flux d'annonce soient incluses dans un paquet contenant des données de présentation multimédia.
  40. Procédé selon la revendication 23, pour lequel le message de RTCP comprend :
    - un premier champ contenant des données identifiant le message de RTCP comme étant d'un type intégrant le message de description de session ;
    - un deuxième champ contenant des données qui sont le message de description de session ; et
    - un troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ et de la longueur du troisième champ.
  41. Système comprenant :
    - une première interface pour recevoir une première pluralité de flux d'une présentation multimédia ;
    - un générateur d'annonce (510) pour fournir un flux d'annonce contenant des informations de description de présentation concernant la présentation multimédia, dans lequel le flux d'annonce est multi-diffusé sur un canal en bande, dans lequel les informations de description de présentation comprennent un message de protocole de contrôle en temps réel, RTCP, qui inclut un message de description de session associé à la présentation multimédia, dans lequel le message de description de session est un message de description de session d'un protocole de description de session, SDP ;
    - un mappeur (584) pour mapper le flux d'annonce et un premier flux sélectionné parmi la première pluralité de flux vers une pluralité de canaux ; et
    - une seconde interface pour multi-diffuser une seconde pluralité de flux dans un réseau (508), dans lequel la seconde pluralité de flux, qui comprend le flux d'annonce mappé et le premier flux mappé, est multi-diffusée sur des canaux différents prédéterminés.
  42. Système selon la revendication 41, dans lequel les canaux différents prédéterminés comprennent des adresses logiques prédéterminées.
  43. Système selon la revendication 42, dans lequel les adresses logiques prédéterminées comprennent chacune une adresse de protocole Internet, IP, et un point d'accès.
  44. Système selon la revendication 41, dans lequel les canaux différents prédéterminés comprennent des points d'accès prédéterminés d'une adresse logique.
  45. Système selon la revendication 41, dans lequel la seconde pluralité de flux comprend en outre un deuxième flux qui, lorsqu'il est multi-diffusé, inclut une pluralité d'unités de données de la présentation multimédia, chaque unité de la pluralité d'unités comprenant un nombre présélectionné de sous-unités antérieures de données de la présentation multimédia.
  46. Système selon la revendication 45, dans lequel le deuxième flux inclut une image clé.
  47. Système selon la revendication 41, dans lequel le flux d'annonce inclut des informations de sécurité.
  48. Système selon la revendication 41, dans lequel le flux d'annonce est multi-diffusé pour se conformer à un protocole de contrôle de transport en temps réel, RTCP, le flux d'annonce étant entremêlé en bande avec un flux de données de présentation multimédia qui sont multi-diffusées pour se conformer à un protocole de transport en temps réel, RTF.
  49. Système selon la revendication 41, dans lequel le flux d'annonce est multi-diffusé de telle sorte que les données de flux d'annonce soient incluses dans un paquet contenant des données de présentation multimédia.
  50. Système selon la revendication 41, dans lequel le message de RTCP comprend :
    - un premier champ contenant des données identifiant le message de RTCP comme étant d'un type intégrant le message de description de session ;
    - un deuxième champ contenant des données qui sont le message de description de session ; et
    - un troisième champ contenant des données identifiant la longueur du message de RTCP, générée en faisant la somme de la longueur du premier champ, de la longueur du deuxième champ et de la longueur du troisième champ.
EP04779232A 2003-10-24 2004-07-28 Integration d'un message de description de session (SDP) dans un message de protocole de controle en temps réel RTCP) Expired - Lifetime EP1676216B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP11004533.3A EP2365450B1 (fr) 2003-10-24 2004-07-28 Integration d'un message de description de session dans un message de protocole de controle en temps reel (rtcp)
EP11004532.5A EP2365449B1 (fr) 2003-10-24 2004-07-28 Intégration d'un message de description de session dans un message de protocole de contrôle en temps réel (RTCP)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/693,430 US7586938B2 (en) 2003-10-24 2003-10-24 Methods and systems for self-describing multicasting of multimedia presentations
US10/836,973 US7492769B2 (en) 2003-10-24 2004-04-30 Embedding a session description message in a real-time control protocol (RTCP) message
PCT/US2004/024065 WO2005045704A1 (fr) 2003-10-24 2004-07-28 Integration d'un message de description de session dans un message de protocole de controle en temps reel (rtcp)

Related Child Applications (4)

Application Number Title Priority Date Filing Date
EP11004532.5A Division-Into EP2365449B1 (fr) 2003-10-24 2004-07-28 Intégration d'un message de description de session dans un message de protocole de contrôle en temps réel (RTCP)
EP11004532.5A Division EP2365449B1 (fr) 2003-10-24 2004-07-28 Intégration d'un message de description de session dans un message de protocole de contrôle en temps réel (RTCP)
EP11004533.3A Division-Into EP2365450B1 (fr) 2003-10-24 2004-07-28 Integration d'un message de description de session dans un message de protocole de controle en temps reel (rtcp)
EP11004533.3A Division EP2365450B1 (fr) 2003-10-24 2004-07-28 Integration d'un message de description de session dans un message de protocole de controle en temps reel (rtcp)

Publications (3)

Publication Number Publication Date
EP1676216A1 EP1676216A1 (fr) 2006-07-05
EP1676216A4 EP1676216A4 (fr) 2010-10-06
EP1676216B1 true EP1676216B1 (fr) 2012-10-24

Family

ID=34577154

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04779232A Expired - Lifetime EP1676216B1 (fr) 2003-10-24 2004-07-28 Integration d'un message de description de session (SDP) dans un message de protocole de controle en temps réel RTCP)

Country Status (9)

Country Link
EP (1) EP1676216B1 (fr)
JP (1) JP4603551B2 (fr)
KR (1) KR101117874B1 (fr)
AU (1) AU2004287133B2 (fr)
BR (1) BRPI0406609A (fr)
CA (1) CA2512191C (fr)
MX (1) MXPA05007090A (fr)
RU (1) RU2372647C2 (fr)
WO (1) WO2005045704A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3817321B1 (fr) * 2018-07-05 2022-10-26 Samsung Electronics Co., Ltd. Procédé et dispositif pour la fourniture d'un service multimédia dans un dispositif électronique

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9318152B2 (en) 2006-10-20 2016-04-19 Sony Corporation Super share
US20080162668A1 (en) 2006-12-29 2008-07-03 John David Miller Method and apparatus for mutually-shared media experiences
WO2009003685A1 (fr) * 2007-07-02 2009-01-08 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Appareil et procédé pour stocker et lire un fichier contenant un conteneur de données mutlimédias et un conteneur de métadonnées
WO2009022703A1 (fr) * 2007-08-14 2009-02-19 Nippon Hoso Kyokai Dispositif de distribution vidéo et programme de distribution vidéo
KR101705898B1 (ko) * 2010-04-02 2017-02-13 삼성전자주식회사 디지털 방송 시스템에서 타임시프트 서비스 제공 방법 및 시스템
US9615119B2 (en) 2010-04-02 2017-04-04 Samsung Electronics Co., Ltd. Method and apparatus for providing timeshift service in digital broadcasting system and system thereof
CN107529090B (zh) 2011-01-19 2021-01-26 三星电子株式会社 用于在广播系统中配置控制消息的装置
RU2485695C2 (ru) * 2011-07-26 2013-06-20 Государственное образовательное учреждение высшего профессионального образования Академия Федеральной службы охраны Российской Федерации (Академия ФСО России) Способ проверки виртуального соединения для передачи мультимедийных данных с заданными характеристиками
US9185346B2 (en) * 2011-10-21 2015-11-10 Telefonaktiebolaget L M Ericsson (Publ) Real-time communications methods providing pause and resume and related devices
EP2704391B1 (fr) * 2012-08-27 2019-05-01 Broadpeak Système et procédé pour délivrer un contenu audiovisuel à un dispositif client
KR101448550B1 (ko) * 2012-11-21 2014-10-13 서울대학교산학협력단 트래픽 분류 장치 및 방법
JP2015012305A (ja) * 2013-06-26 2015-01-19 ソニー株式会社 コンテンツ供給装置、コンテンツ供給方法、プログラム、端末装置、およびコンテンツ供給システム
MX358670B (es) * 2013-07-17 2018-08-31 Sony Corp Dispositivo de provisión de contenido, método de provisión de contenido, programa, dispositivo de terminal, y sistema de provisión de contenido.

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6275471B1 (en) * 1998-05-12 2001-08-14 Panasonic Technologies, Inc. Method for reliable real-time multimedia streaming
WO2001028909A1 (fr) 1999-10-21 2001-04-26 Mitsubishi Denki Kabushiki Kaisha Unite de commande de groupe de cabines d'ascenseurs
JP2002141964A (ja) * 2000-08-24 2002-05-17 Matsushita Electric Ind Co Ltd 送受信方法およびその装置
US7031311B2 (en) * 2001-07-23 2006-04-18 Acme Packet, Inc. System and method for providing rapid rerouting of real-time multi-media flows
US7237108B2 (en) * 2001-09-26 2007-06-26 General Instrument Corporation Encryption of streaming control protocols and their headers
AU2002359118A1 (en) * 2001-12-11 2003-07-09 Telefonaktiebolaget L M Ericsson (Publ) Method of rights management for streaming media

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3817321B1 (fr) * 2018-07-05 2022-10-26 Samsung Electronics Co., Ltd. Procédé et dispositif pour la fourniture d'un service multimédia dans un dispositif électronique

Also Published As

Publication number Publication date
EP1676216A1 (fr) 2006-07-05
MXPA05007090A (es) 2005-10-18
AU2004287133A1 (en) 2005-05-19
KR20060105424A (ko) 2006-10-11
EP1676216A4 (fr) 2010-10-06
RU2005120669A (ru) 2006-01-20
BRPI0406609A (pt) 2005-12-06
KR101117874B1 (ko) 2012-03-08
CA2512191A1 (fr) 2005-05-19
AU2004287133B2 (en) 2010-05-13
AU2004287133A2 (en) 2005-05-19
CA2512191C (fr) 2013-12-31
JP4603551B2 (ja) 2010-12-22
JP2007509573A (ja) 2007-04-12
WO2005045704A1 (fr) 2005-05-19
RU2372647C2 (ru) 2009-11-10

Similar Documents

Publication Publication Date Title
EP2365449B1 (fr) Intégration d'un message de description de session dans un message de protocole de contrôle en temps réel (RTCP)
AU2004202538B2 (en) RTP payload format
EP1741035B1 (fr) Extensions de messages de description de session
EP1676216B1 (fr) Integration d'un message de description de session (SDP) dans un message de protocole de controle en temps réel RTCP)

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20050621

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1092237

Country of ref document: HK

A4 Supplementary search report drawn up and despatched

Effective date: 20100903

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/06 20060101ALI20100830BHEP

Ipc: G06F 17/30 20060101AFI20050520BHEP

17Q First examination report despatched

Effective date: 20101203

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/18 20060101ALN20111109BHEP

Ipc: G06F 17/30 20060101ALI20111109BHEP

Ipc: H04L 29/06 20060101AFI20111109BHEP

RTI1 Title (correction)

Free format text: EMBEDDING A SESSION DESCRIPTION (SDP) MESSAGE IN A REAL-TIME CONTROL PROTOCOL (RTCP) MESSAGE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602004039796

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0017300000

Ipc: H04L0029060000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/06 20060101AFI20120412BHEP

Ipc: G06F 17/30 20060101ALI20120412BHEP

Ipc: H04L 12/18 20060101ALN20120412BHEP

RTI1 Title (correction)

Free format text: EMBEDDING A SESSION DESCRIPTION (SDP) MESSAGE IN A REAL-TIME CONTROL PROTOCOL (RTCP) MESSAGE

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 581408

Country of ref document: AT

Kind code of ref document: T

Effective date: 20121115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602004039796

Country of ref document: DE

Effective date: 20121220

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 581408

Country of ref document: AT

Kind code of ref document: T

Effective date: 20121024

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20121024

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130125

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130225

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1092237

Country of ref document: HK

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130124

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20130725

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20130204

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602004039796

Country of ref document: DE

Effective date: 20130725

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20130728

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130728

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130731

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130728

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602004039796

Country of ref document: DE

Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602004039796

Country of ref document: DE

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, REDMOND, US

Free format text: FORMER OWNER: MICROSOFT CORP., REDMOND, WASH., US

Effective date: 20121024

Ref country code: DE

Ref legal event code: R082

Ref document number: 602004039796

Country of ref document: DE

Representative=s name: GRUENECKER PATENT- UND RECHTSANWAELTE PARTG MB, DE

Effective date: 20150126

Ref country code: DE

Ref legal event code: R081

Ref document number: 602004039796

Country of ref document: DE

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, REDMOND, US

Free format text: FORMER OWNER: MICROSOFT CORP., REDMOND, WASH., US

Effective date: 20150126

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20121024

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20040728

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130728

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, US

Effective date: 20150724

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20180612

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20180717

Year of fee payment: 15

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602004039796

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200201

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190731