US20040210944A1 - Program insertion in real time IP multicast - Google Patents
Program insertion in real time IP multicast Download PDFInfo
- Publication number
- US20040210944A1 US20040210944A1 US10/838,578 US83857804A US2004210944A1 US 20040210944 A1 US20040210944 A1 US 20040210944A1 US 83857804 A US83857804 A US 83857804A US 2004210944 A1 US2004210944 A1 US 2004210944A1
- Authority
- US
- United States
- Prior art keywords
- program
- content
- destination
- proxy
- advertising
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/23424—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving splicing one content stream with another content stream, e.g. for inserting or substituting an advertisement
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1895—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for short real-time information, e.g. alarms, notifications, alerts, updates
Definitions
- the present invention relates generally to inserting a secondary audio and/or video program into a real time multicast of a primary audio and/or video program.
- the invention relates to the insertion of advertisements, into real time multicasts of audio and/or video over the Internet.
- IP Internet Protocol
- the present invention is a system and method for supporting audio/video program insertion in real-time IP multicasts.
- Secondary programs are seamlessly inserted into multicast sessions of primary programs in a decentralized fashion. Relying on coordination of nodes using the Real Time Protocol (RTP) and IP multicast, inserted video and/or audio programs are displayed within the same ‘window’ as the primary program regardless if the primary and secondary streams originate from physically distinct sources. If the inserted content is an advertisement, viewers have the familiar experience of commercial advertising on broadcast television.
- RTP Real Time Protocol
- a primary content provider transmits its multimedia stream to a first proxy that transmits the data to a destination multicast session.
- a secondary content provider interested in inserting a program into that destination multicast session sends a request through a second proxy to the first proxy requesting a time slot to insert its secondary program.
- the request includes the duration of the secondary program.
- the first proxy responds with a time slot or a denial of the request depending if a time slot is available. Assuming an available time slot, at the appropriate time the first proxy transfers control of the destination multicast session to the second proxy which transmits the secondary program.
- the second proxy Upon completion of the secondary program the second proxy returns control of the session to the first proxy. All scheduling and control transfer occurs through the development of a new protocol to manage the transfer of control. Smooth transitions occur by manipulation of the RTP header in the packets and the associated RTCP stream.
- primary content providers e.g., advertisers
- viewers are afforded a far richer collection of relationships, opportunities and features than possible with traditional broadcast mediums.
- spontaneous meetings and relationships between primary and secondary content providers may be established; program insertions may be set at arbitrary times from arbitrary locations in a multicast tree; verifiable viewer demographics from Real Time Control Protocol messages may be sent to content providers; and the system may support multiple, simultaneous program transmissions with user-selectable reception and viewing.
- operation of the system of the present invention does not require any modifications to existing software viewers or players.
- the present invention is not dependent on IP being used from end-to-end, or that the network be public. Considerable applications of the system of the present invention exist outside of the Internet where IP multicast may be used on a more limited basis, such as with satellite distribution of audio/video feeds to “headends” for local internet or intranet distribution.
- FIG. 1 depicts one instance of the general architecture of the program insertion system of the present invention.
- FIG. 2 illustrates a typical packet header in accordance with real time protocol version 2 .
- FIG. 3 illustrates the interprocess communication in the s_proxy as operated in accordance with the present invention.
- FIG. 4 illustrates an example of a program insertion protocol in accordance with the system of the present invention.
- FIG. 5 illustrates a linear topology of a wide area network and the mean packet latency between various nodes therein between which the program insertion system of the present invention is implemented.
- FIG. 1 One instance of the architecture of the program insertion system and method of the present invention is shown in FIG. 1.
- the primary content provider is referred to as sender 10
- the secondary content provider is known as advertiser 16 .
- the denotation of a content provider as primary and secondary is arbitrary. It merely simplifies the following discussion to refer to the provider of the principle program as primary and the provider of the inserted program as secondary. Since one common and advantageous embodiment of the present invention is to insert advertisements into a primary program, we refer to the secondary provider as the advertiser. Indeed, a system for inserting commercial advertisements sets the foundation for a viable business model for television and radio over the Internet.
- the program insertion system of the present invention is operable with any application capable of sending and receiving RTP packets, or packets using an equivalent sending and receiving transport protocol which resides on the User Datgram Protocol (“UDP”).
- UDP User Datgram Protocol
- proxies are associated with sender 10 and advertiser 16 . Each proxy is responsible for broadcasting the content of their provider to receivers tuned to the destination multicast session. By using proxies, the method of the present invention is independent of multimedia viewers or players. Only one proxy forwards a Real Time Protocol (“RTP”) stream (an Internet standard protocol for transporting continuous media) at any time.
- RTP Real Time Protocol
- the s_proxy 12 and a_proxy 14 which are servers, form client-server pairs with their respective providers that coordinate switching between the providers, the streams being transmitted to receivers 18 and 20 .
- Each proxy (a_proxy 14 or s_proxy 12 ) software can be run on the same system as the content provider, (advertiser or sender, respectively) if desired.
- the terms a_proxy 14 and s_proxy 12 as used herein refer to both the application software and the system running the software. The systems running the proxy software appear to the user to be the actual broadcast sources (as opposed to sender 10 and advertiser 16 ).
- s_proxy 12 provides two basic services: First, when an advertisement is not in progress, s_proxy 12 will continuously relay packets received on a private unicast, or a multicast session, from the sender 10 to the destination (public) multicast session. As discussed more fully below, RTP header fields are usually modified as part of the relay function. When an advertisement is in progress, s_proxy 12 interrupts the packet relaying process, permitting the advertiser's proxy, a_proxy 14 to transmit its own stream to the destination multicast session. The second service performed by s_proxy 12 is receiving and scheduling incoming requests for future advertisements. This task includes passing RTP header information to advertisers to permit them to inject advertisements seamlessly.
- the content of either provider can be any audio and/or video, pre-recorded or live, encapsulated in RTP.
- the program comprises both audio and video, it is advantageous to transmit them as separate RTP streams, handled by separate proxies.
- a_proxy 14 Similar to the interaction of sender 10 with s_proxy 12 , advertiser 16 ordinarily transmits packets to a_proxy 14 on a private unicast or multicast address and a_proxy 14 transmits the content of advertiser 16 on the destination multicast session. As with s_proxy 12 , a_proxy 14 also provides two services: First, when an advertisement is in progress, it relays packets received from advertiser 16 to the destination multicast session, in which case RTP header fields are always modified, as explained below with reference to FIG. 2. When an advertisement is complete, a_proxy 14 terminates the packet relaying process.
- a_proxy 14 is also responsible for passing RTP header information back to the s_proxy 12 to permit a return to the primary content at the conclusion of the inserted program. Second, a_proxy 14 also schedules requests to place future advertisements and is responsible for properly handling denials of service (e.g. server responds that a desired time slot is unavailable) returned from the s_proxy 12 .
- Receivers 18 and 20 can be any destination capable of receiving and rendering audio/video in the encoding formats of both the sender and advertiser.
- the program insertion method and system of the present invention is independent of existing software players such as vic version 2.8, as described in S. McCanne and V.
- FIG. 1 reflects one specific instance where a vic player is used by sender 10 and rtpplay is used by
- the final element of the architecture is the insertion protocol.
- This protocol comprises a set of messages sent between the a_proxy 14 and s_proxy 12 .
- the purpose of the protocol is to coordinate the transfer of a token; only the token holder is permitted to transmit packets on the destination multicast session.
- the protocol has three logical phases. During the scheduling phase a_proxy 14 communicates with s_proxy 12 to arrange an insertion at a future time. Control is passed to a_proxy 14 at that scheduled time during the transfer phase, and control is returned to s_proxy 12 when the insertion is complete during the return phase.
- sender 10 and advertiser 16 and their respective proxies 12 and 14 can be implemented in any combination of one or more machines.
- the proxy functions could be integrated into the transmitting application of sender 10 and advertiser 16 .
- the synchronization source identifier is a random number which uniquely identifies the source of an RTP packet stream. Packets from a synchronization source are distinguished by a timestamp and sequence number. These fields are used by receivers for proper signal reconstruction and playout timing. The initial sequence number value is also random, and is incremented for each consecutively transmitted packet. Packets can and do arrive at their destination out-of-order.
- the timestamp indicates the time of the sampling instant of the RTP payload relative to the initial timestamp value, which is randomly selected.
- the sampling rate for many audio/video encoding formats is constant, well known, and registered with the Interent Assigned Numbers Agency (“IANA”). Other formats can have time-varying sampling rates.
- Media formats are specified by the Payload Type (PT) field. Multiple packets can have the same timestamp, as in the case where a large video frame is grabbed, encoded, but then transported in multiple packets.
- a list of contributing source identifiers is present only if multiple RTP streams have been mixed.
- the CSRC count (CC) field indicates the number of contributors, and the CSRC contains the original SSRC identifier of each contributing source.
- RTCP Monitoring and control protocol
- RTCP's primary functions is to provide feedback on reception quality, and distribute source identification and control information. This is realized by distributing messages including Sender Reports (SR), Receiver Reports (RR), and Source Descriptions (SDES).
- SR Sender Reports
- RR Receiver Reports
- SDES Source Descriptions
- a session's RTCP and RTP messages are ordinarily transmitted to separate ports on a shared destination multicast address.
- Advertiser 16 wishing to insert a secondary program contacts sender 10 immediately prior to insertion.
- Sender 10 may be transmitting an analog video signal captured from a live camera, encoded, packetized and transmitted as an RTP stream using vic, as shown in FIG. 1.
- An associated RTCP stream is transmitted on a different port.
- the RTP and RTCP streams are transmitted from sender 10 to s_proxy 12 and relayed from there to the destination multicast session.
- s_proxy 12 controls and manages the process of forwarding the sender's RTP session to receivers 18 and 20 on the destination multicast session. This function includes receiving, manipulating and forwarding the RTP and RTCP packets. It also receives and processes the insertion request by advertiser 16 , interrupting the relaying of the stream from sender 10 for the duration of the advertisement. Finally, it takes control of the RTP session at the advertisement termination time, and resumes relaying the stream from sender 10 .
- the relay process 30 establishes a software interface for network communication, called a socket for receiving the sender's RTP stream, and a second socket for transmitting the modified stream to the receivers.
- the process stores the sender's SSRC, as well as the timestamp and sequence number of the last packet received. It also maintains an offset timestamp and offset sequence number. These values are initially zero but change according to the offset values returned by the advertiser. The offsets are added to the timestamp and sequence numbers field in the header of each incoming packet to be forwarded.
- the server process 50 listens for a request from advertiser 16 on an incoming TCP connection. Each accepted connection creates a child server process. Information contained in a request is passed to the scheduler 40 using a queue structure. Advantageously the requests are queued and served on a first-come, first-serve basis as needed to handle multiple incoming insertion requests. This can be implemented using UNIX pipes for the interprocess communication. Each request from advertiser 16 contains the desired duration of the advertisement in seconds. Relaying the sender stream is stopped for the desired advertisement duration. At the end of the advertisement the server process receives current timestamp and sequence number values from advertiser 16 (on the still open TCP connection) and passes it to the relay process 30 to calculate new offsets.
- the scheduling phase is necessarily message based. Advertiser 16 seeking to insert a program must explicitly contact s_proxy 12 with a desired program start time and duration. s_proxy 12 must explicitly accept or deny the request, although the response can optionally contain additional information. For example, if an insertion request is denied because of a scheduling conflict, s_proxy 12 could return alternate available time slots. Reliability demands suggest that this portion of the protocol should be TCP-based.
- the scheduler process 40 receives the incoming request from a server process and schedules an interrupt of the relay process. It is also possible, if desired, to make the scheduler a null process. This results in each insertion request immediately becoming an interrupt.
- the scheduler process receives the value of the advertisement duration from the server process 50 and informs the relay process 30 to sleep for the specified duration.
- new timestamp and sequence number values are received from the advertiser (through the scheduler process) and are passed to the relay process 30 .
- the system can support multicast to multiple s_proxies.
- s_proxies As in broadcast television, it is desirable to permit multiple distributors of the same content, with each distributor having its own relations with advertisers.
- a typical use would be broadcasting an event of international interest (e.g., World Cup Soccer) with different agents assigned distribution rights by country. Different distributors could then cater to their own sets of advertisers, and their respective audiences.
- a_proxy 14 has a single process that does three jobs. First, it establishes a TCP connection to s_proxy 12 and requests an immediate time slot for program insertion. Only the intended secondary program duration is specified. For an immediate insertion, the SSRC and RTCP Session Description (SDES) parameters for sender 10 are returned, as well as the timestamp and sequence number of the most recently received sender packet.
- SDES Session Description
- a_proxy 14 then calculates offsets for both timestamp and sequence number. That is, for seamless insertion, it is necessary for the stream transmitted by a_proxy 14 to pick up where the s_proxy 12 left off. This requires receiving the incoming advertiser's private stream, modifying RTP headers, and multicasting the modified stream on public destination multicast session.
- Relaying the RTP stream from advertiser 16 begins immediately. For each incoming packet the advertiser's SSRC is changed to that of the s_proxy 12 , and appropriate timestamp and sequence number offsets are added. At the completion of the secondary program transmission, a_proxy 14 sends back to s_proxy 12 its last transmitted packet's timestamp and sequence number. At this time, the s_proxy 12 calculates new timestamp and sequence number offsets, then begins relaying the signal from sender 10 once again, picking up where advertiser 16 left off.
- Scheduling and control transfer phases can be implemented as coincident, or with arbitrary duration intervals between each phase. Note that in some applications scheduling insertions might be preceded by regular broadcast announcements of the availability of open time slots in a program schedule.
- This synchronized time is used by both a_proxy 14 and s_proxy 12 to determine when to start and stop relaying the respective content of advertiser 16 and sender 10 .
- Each party monitors RTP packets on the destination session, and infers from this an appropriate timestamp and sequence number offset to use at the assumption of control.
- a second embodiment uses messages based on the Real Time Streaming Protocol (RTSP) as described in H. Schulzrinne et al., “RTSP:A Transport Protocol for Real Time Applications,” Internet Draft (February 1998), hereby incorporated by reference as if fully set forth herein.
- RTSP Real Time Streaming Protocol
- Existing RTSP methods e.g., SETUP, PLAY
- sender's and advertisers' proxies operate in part as RTSP proxies. Control transfer messages between these proxies are based on existing (or extensions to existing) RTSP control messages.
- the RTSP SETUP method could be used to pass transport parameters (e.g. SSRC, timestamp, sequence number) to the advertiser's proxy.
- transport parameters e.g. SSRC, timestamp, sequence number
- the PLAY method would be sent by the sender's proxy to the advertiser's proxy to initiate advertisement playout.
- the communication between the sender and it's proxy, as well as the advertiser and its proxy could also be performed using RTSP messages.
- the sender's proxy could use the RTSP PAUSE method to interrupt the sender's communication, thus allowing the advertiser to insert content.
- a third embodiment of explicit messaging requires the destination multicast session be monitored by s_proxy 12 and a_proxy 14 .
- New RTCP application messages represent an explicit way to exchange necessary information to facilitate control transfer and return.
- extensions to RTCP messages could serve as control transfer messages between sender and receiver proxies.
- the IP multicast session itself is used to transfer program control.
- a new RTCP message could pass transport parameters (e.g. SSRC, timestamp, sequence number) from the sender's to the advertiser's proxy. This approach, however, is neither private (i.e., not unicast) nor reliable.
- remote playout could be triggered by an RTSP PLAY message sent in advance (e.g., several seconds or minutes) of a scheduled control transfer.
- a message would contain appropriate session control information (e.g. timestamp, sequence number and start time).
- advertiser 16 could simply monitor the session and estimate these parameters independently and begin when scheduled. In the worst case, advertiser 16 would begin only after detecting that active transmissions have ceased.
- a_proxy 14 transmits its first packet at exactly the time s_proxy 12 would have transmitted its next packet, that first packet will nominally arrive late due to the additional delay in receiver 25 .
- a_proxy's 14 first packet might arrive at receiver 27 before s_proxy's 12 final packet if the mean packet latency is not accounted for.
- sender 10 and advertiser 16 are not precisely synchronized and a_proxy 14 poorly estimates the stamp and sequence number, duplicate packets may result, causing the receivers to discard one or more packets. Poorly estimated timestamps could easily produce unintended, perceptible ‘freeze frame’, if for example the timestamp increases from frame to frame so that the playback is very slow. Conversely, ‘fast forward’ play occurs where the timestamp decreases from frame to subsequent frame.
- RTP requires that the identifiers be unique for each source in a session, and recommends actions for sources to take in the unlikely event of collision. Accordingly, the RTP header must be appropriately handled to assure display of the primary and secondary programs in the same window.
- the data payload may be of any encoding type that a viewer can decode.
- content providers may use any standard format for their audio and/or video.
- the secondary content provider should ensure that, independent of any chosen encoding scheme, with respect to video, a full frame should be sent first (e.g., an I-frame in MPEG-2). This is a common recommendation for any video mixing system, as described in Cable Television Laboratories, Inc. “Digital Program Insertion: Request for Information,” (April 1997), hereby incorporated by reference as if fully set forth herein.
- the system is operable with existing transmitters and viewers.
- secondary content providers can efficiently transmit their own content, obviating any need for first forwarding their programs to event broadcasters. Moreover, since the secondary content providers are responsible for transmitting their own content event broadcasters are relieved from unwanted administration and retransmission tasks.
- a further advantageous embodiment of the present invention is to provide for the simultaneous transmission of different secondary programs, such as advertisements, to different viewers.
- secondary programs such as advertisements
- the mask is a 32 bit number logically AND'ed with each incoming packet's 32 bit SSRC value. If the result equals the SSRC value of the desired session, then the packet is accepted as belonging to that stream.
- This approach effectively creates a set of SSRCs which can be used by advertisers to create separate. simulcast advertisement channels. For example, suppose receiver A has mask Oxffffff0f and receiver B has mask Oxffffff0. Both receivers are tuned to a multicast session with SSRC identifier 0x55555500. Then, if during a ‘commercial’ break one advertiser begins transmitting with an SSRC identifier 0x55555501, this content will be accepted and played out by receiver B as a logical continuation of a programming sequence. If a second advertiser begins transmitting with an SSRC identifier 0x55555510, this content will be accepted and played out by receiver A. In the event of conflicts (i.e., multiple simultaneous streams with valid SSRCs), a conflict resolution procedure is invoked (e.g., packets with the lowest valid SSRC are played out, packets with other SSRCs are discarded).
- conflicts i.e., multiple simultaneous streams with valid SSRC
Abstract
A system for broadcasting television programs over the Internet. A content provider, such as a broadcaster of a sports event, packages a television program into digital packets, and transmits the packets over the Internet to subscribers, from a first location. The content provider periodically pauses in transmitting the packets, to allow advertisers to transmit advertising messages during the pauses, from a second location. Arrangements are provided to synchornize the content provider and the advertisers.
Description
- The present invention relates generally to inserting a secondary audio and/or video program into a real time multicast of a primary audio and/or video program. In one specific embodiment the invention relates to the insertion of advertisements, into real time multicasts of audio and/or video over the Internet.
- With increased popularity and availability of the Internet, programmers, users and content providers are continuously searching for new applications of the Internet. One such application is real-time and near real-time audio and video transmitted over networks using the Internet Protocol (IP). With continued growth users will be able to view their television broadcasts and even listen to their radio programs over the Internet. While presently, the quality of the multimedia received over the Internet currently lags the quality that is received over more traditional medium, the technology is likely to soon rival existing audio/video broadcast technology.
- Expanding Internet connectivity, network infrastructure improvements, and more powerful computers are all supporting this growth. Access technologies already under deployment, such as cable modems, promise enough downstream bandwidth to support real-time multimedia transport to residences. The software required to receive and render low-rate video conferences is now bundled with new personal computers or freely available (e.g., NetMeeting). Personal computers are being equipped with inexpensive native peripherals, such as DVDs, cameras, and frame grabbers, supporting content creation, capture, editing and transmission. New video standards such as MPEG-4 are also emerging and are expected to improve IP video quality. Carrier backbone transmission and switching equipment is being upgraded to keep up with increasing traffic demands and quality of service requirements. Thus growing network and computing capabilities suggest continued growth in real-time multimedia transport over IP networks.
- Despite the considerable advances in network and end system technology, use of real-time IP multicast has grown at a relatively slow rate. Four reasons are typically cited for this limited growth: 1) limited available transmission bandwidth (particularly for residential users); 2) the predominance of packet loss at congested network routers; 3) the existing infrastructure's lack of a simple, scaleable multicast routing protocol; and 4) the lack of broadcast content for users to receive. The first two factors yield what is perceived as poor reception quality—for video in particular.
- To address the immediate problem of poor reception, most content providers have steered clear of multicast transport. The overwhelming majority of audio content is unicast and streamed in near real time (i.e., up to a few seconds delay). This, notwithstanding that IP multicast is better suited for reaching larger audiences, exchanging certain types of personal information, and satisfying advertisers. In addition, exciting new services and opportunities are more easily achieved in a multicast setting. While packet loss recovery mechanisms in streaming transport protocols assure users of the highest quality reception, it comes at the expense of unicasting to each individual user to emulate a broadcast medium.
- But, as discussed above, network infrastructure is being continuously upgraded, and routers and standards are being introduced to address existing network service quality deficiencies. These include the Reservations Protocol (“RSVP”) and Differentiated Services (“DiffServ”) which attempt to achieve quality of service, and Protocol Independent Multicast (“PIM”) which attempts to achieve a scaleable multicast protocol described in S. Deering, et al., “The PIM Architecture for Wide Area Multicast Routing,: IEEE/ACM Transactions on Networking vol. 4 no. 2, pp. 153-62 (1996), hereby incorporated by reference as if fully set forth herein. As for lack of content, while little video is currently transmitted on the Internet, much content is potentially available. Much of this content is of interest to smaller audiences than would be efficiently targeted by other technologies such as broadcast radio or television. Hence, the technical barriers to growth in real-time multicast are being addressed, and all indications are that this trend will continue.
- What limits further growth in IP multicasting, however, is the absence of a viable operational business model to justify an investment in broadcasting. Traditionally, advertisers pay for a time slot and provide a broadcaster with a pre-recorded tape of, or a disk containing an advertisement. While the content of television broadcasters can be either pre-recorded or televised live, the advertisements are broadcast by simply flipping a switch from the live camera or player feed of the feature presentation, to the player of the pre-recorded advertisement.
- Streaming audio over the Internet can be expensive and presently audiences are typically small. While traditional television broadcasts and cable profit from advertisements, it is difficult to interest advertisers to pay for programs viewed by small audiences on the Internet. Clearly, solutions for effective and efficient insertion of advertisements or other programs during a real time presentation of a feature program serviced over the Internet are desired. Furthermore, a viable business model will lead to further desirable infrastructure improvements.
- Consider a sporting event. The interested audience normally far exceeds the actual number of attendees. Event organizers recognize the potential value of broadcasting their content, but currently are unable to capture that value. Recording content for deferred, on-demand playback has little promise, since a sporting event's value diminishes rapidly as results become known. In some cases, organizers might consider a real-time broadcast on the multicast backbone (MBone). A significant barrier here is that multicasting forces the organizers to make an initial and often substantial, up-front investment. Yet no practical mechanism exists to enable the content owners to be compensated for their expense. Event organizers seek assured funding to finance broadcasting and to ensure programming quality.
- Accordingly, the present invention is a system and method for supporting audio/video program insertion in real-time IP multicasts. Secondary programs are seamlessly inserted into multicast sessions of primary programs in a decentralized fashion. Relying on coordination of nodes using the Real Time Protocol (RTP) and IP multicast, inserted video and/or audio programs are displayed within the same ‘window’ as the primary program regardless if the primary and secondary streams originate from physically distinct sources. If the inserted content is an advertisement, viewers have the familiar experience of commercial advertising on broadcast television.
- In accordance with the present invention a primary content provider transmits its multimedia stream to a first proxy that transmits the data to a destination multicast session. A secondary content provider interested in inserting a program into that destination multicast session sends a request through a second proxy to the first proxy requesting a time slot to insert its secondary program. The request includes the duration of the secondary program. The first proxy responds with a time slot or a denial of the request depending if a time slot is available. Assuming an available time slot, at the appropriate time the first proxy transfers control of the destination multicast session to the second proxy which transmits the secondary program. Upon completion of the secondary program the second proxy returns control of the session to the first proxy. All scheduling and control transfer occurs through the development of a new protocol to manage the transfer of control. Smooth transitions occur by manipulation of the RTP header in the packets and the associated RTCP stream.
- In accordance with the present invention, primary content providers, secondary content providers (e.g., advertisers) and viewers are afforded a far richer collection of relationships, opportunities and features than possible with traditional broadcast mediums. Thus for example spontaneous meetings and relationships between primary and secondary content providers may be established; program insertions may be set at arbitrary times from arbitrary locations in a multicast tree; verifiable viewer demographics from Real Time Control Protocol messages may be sent to content providers; and the system may support multiple, simultaneous program transmissions with user-selectable reception and viewing. In addition, operation of the system of the present invention does not require any modifications to existing software viewers or players.
- Furthermore, the present invention is not dependent on IP being used from end-to-end, or that the network be public. Considerable applications of the system of the present invention exist outside of the Internet where IP multicast may be used on a more limited basis, such as with satellite distribution of audio/video feeds to “headends” for local internet or intranet distribution.
- FIG. 1 depicts one instance of the general architecture of the program insertion system of the present invention.
- FIG. 2 illustrates a typical packet header in accordance with real
time protocol version 2. - FIG. 3 illustrates the interprocess communication in the s_proxy as operated in accordance with the present invention.
- FIG. 4 illustrates an example of a program insertion protocol in accordance with the system of the present invention.
- FIG. 5 illustrates a linear topology of a wide area network and the mean packet latency between various nodes therein between which the program insertion system of the present invention is implemented.
- One instance of the architecture of the program insertion system and method of the present invention is shown in FIG. 1. For ease of discussion the primary content provider is referred to as
sender 10, while the secondary content provider is known asadvertiser 16. In fact in accordance with the method and system of the present invention, the denotation of a content provider as primary and secondary is arbitrary. It merely simplifies the following discussion to refer to the provider of the principle program as primary and the provider of the inserted program as secondary. Since one common and advantageous embodiment of the present invention is to insert advertisements into a primary program, we refer to the secondary provider as the advertiser. Indeed, a system for inserting commercial advertisements sets the foundation for a viable business model for television and radio over the Internet. However, it should be clear that the following discussion is not limited in scope to advertisement insertion. Further applications include insertion of emergency broadcasts, video chat sessions, and virtual radio/television stations. Indeed, the program insertion system of the present invention is operable with any application capable of sending and receiving RTP packets, or packets using an equivalent sending and receiving transport protocol which resides on the User Datgram Protocol (“UDP”). - In accordance with the present invention proxies are associated with
sender 10 andadvertiser 16. Each proxy is responsible for broadcasting the content of their provider to receivers tuned to the destination multicast session. By using proxies, the method of the present invention is independent of multimedia viewers or players. Only one proxy forwards a Real Time Protocol (“RTP”) stream (an Internet standard protocol for transporting continuous media) at any time. H. Schulzrinne, at al., “RTP: A Transport Protocol for Real-Time Applications,” Internet RFC 1889 (January 1996), hereby incorporated by reference as if fully set forth herein. - The
s_proxy 12 anda_proxy 14, which are servers, form client-server pairs with their respective providers that coordinate switching between the providers, the streams being transmitted toreceivers a_proxy 14 or s_proxy 12) software can be run on the same system as the content provider, (advertiser or sender, respectively) if desired. Unless otherwise indicated, the terms a_proxy 14 ands_proxy 12 as used herein refer to both the application software and the system running the software. The systems running the proxy software appear to the user to be the actual broadcast sources (as opposed tosender 10 and advertiser 16). - s_proxy12 provides two basic services: First, when an advertisement is not in progress, s_proxy 12 will continuously relay packets received on a private unicast, or a multicast session, from the
sender 10 to the destination (public) multicast session. As discussed more fully below, RTP header fields are usually modified as part of the relay function. When an advertisement is in progress, s_proxy 12 interrupts the packet relaying process, permitting the advertiser's proxy, a_proxy 14 to transmit its own stream to the destination multicast session. The second service performed bys_proxy 12 is receiving and scheduling incoming requests for future advertisements. This task includes passing RTP header information to advertisers to permit them to inject advertisements seamlessly. - The content of either provider can be any audio and/or video, pre-recorded or live, encapsulated in RTP. However, if the program comprises both audio and video, it is advantageous to transmit them as separate RTP streams, handled by separate proxies.
- Similar to the interaction of
sender 10 withs_proxy 12,advertiser 16 ordinarily transmits packets to a_proxy 14 on a private unicast or multicast address and a_proxy 14 transmits the content ofadvertiser 16 on the destination multicast session. As withs_proxy 12, a_proxy 14 also provides two services: First, when an advertisement is in progress, it relays packets received fromadvertiser 16 to the destination multicast session, in which case RTP header fields are always modified, as explained below with reference to FIG. 2. When an advertisement is complete, a_proxy 14 terminates the packet relaying process. As part of this service, a_proxy 14 is also responsible for passing RTP header information back to thes_proxy 12 to permit a return to the primary content at the conclusion of the inserted program. Second, a_proxy 14 also schedules requests to place future advertisements and is responsible for properly handling denials of service (e.g. server responds that a desired time slot is unavailable) returned from thes_proxy 12. -
Receivers sender 10 and rtpplay is used byadvertiser 16. - The final element of the architecture is the insertion protocol. This protocol comprises a set of messages sent between the a_proxy14 and
s_proxy 12. The purpose of the protocol is to coordinate the transfer of a token; only the token holder is permitted to transmit packets on the destination multicast session. The protocol has three logical phases. During thescheduling phase a_proxy 14 communicates withs_proxy 12 to arrange an insertion at a future time. Control is passed to a_proxy 14 at that scheduled time during the transfer phase, and control is returned tos_proxy 12 when the insertion is complete during the return phase. - In one advantageous embodiment of the
present invention sender 10 andadvertiser 16 and theirrespective proxies sender 10 andadvertiser 16. - Referring to the RTP header format shown in FIG. 2, the first twelve bytes of the header are required by the protocol. The synchronization source identifier (SSRC) is a random number which uniquely identifies the source of an RTP packet stream. Packets from a synchronization source are distinguished by a timestamp and sequence number. These fields are used by receivers for proper signal reconstruction and playout timing. The initial sequence number value is also random, and is incremented for each consecutively transmitted packet. Packets can and do arrive at their destination out-of-order.
- The timestamp indicates the time of the sampling instant of the RTP payload relative to the initial timestamp value, which is randomly selected. The sampling rate for many audio/video encoding formats is constant, well known, and registered with the Interent Assigned Numbers Agency (“IANA”). Other formats can have time-varying sampling rates. Media formats are specified by the Payload Type (PT) field. Multiple packets can have the same timestamp, as in the case where a large video frame is grabbed, encoded, but then transported in multiple packets.
- A list of contributing source identifiers is present only if multiple RTP streams have been mixed. In this case, the CSRC count (CC) field indicates the number of contributors, and the CSRC contains the original SSRC identifier of each contributing source.
- Associated with RTP is a monitoring and control protocol called RTCP. RTCP's primary functions is to provide feedback on reception quality, and distribute source identification and control information. This is realized by distributing messages including Sender Reports (SR), Receiver Reports (RR), and Source Descriptions (SDES). A session's RTCP and RTP messages are ordinarily transmitted to separate ports on a shared destination multicast address.
- To illustrate the operation of the insertion protocol of the present invention, consider an implementation of the present invention where the system injects programs on demand, i.e. without advance reservation.
Advertiser 16, wishing to insert a secondaryprogram contacts sender 10 immediately prior to insertion.Sender 10 may be transmitting an analog video signal captured from a live camera, encoded, packetized and transmitted as an RTP stream using vic, as shown in FIG. 1. An associated RTCP stream is transmitted on a different port. The RTP and RTCP streams are transmitted fromsender 10 to s_proxy 12 and relayed from there to the destination multicast session. - s_proxy12 controls and manages the process of forwarding the sender's RTP session to
receivers advertiser 16, interrupting the relaying of the stream fromsender 10 for the duration of the advertisement. Finally, it takes control of the RTP session at the advertisement termination time, and resumes relaying the stream fromsender 10. - Referring to FIG. 3, the three separate tasks of
s_proxy 12, relay, scheduler and server processes, are shown. Therelay process 30 establishes a software interface for network communication, called a socket for receiving the sender's RTP stream, and a second socket for transmitting the modified stream to the receivers. The process stores the sender's SSRC, as well as the timestamp and sequence number of the last packet received. It also maintains an offset timestamp and offset sequence number. These values are initially zero but change according to the offset values returned by the advertiser. The offsets are added to the timestamp and sequence numbers field in the header of each incoming packet to be forwarded. - The
server process 50 listens for a request fromadvertiser 16 on an incoming TCP connection. Each accepted connection creates a child server process. Information contained in a request is passed to thescheduler 40 using a queue structure. Advantageously the requests are queued and served on a first-come, first-serve basis as needed to handle multiple incoming insertion requests. This can be implemented using UNIX pipes for the interprocess communication. Each request fromadvertiser 16 contains the desired duration of the advertisement in seconds. Relaying the sender stream is stopped for the desired advertisement duration. At the end of the advertisement the server process receives current timestamp and sequence number values from advertiser 16 (on the still open TCP connection) and passes it to therelay process 30 to calculate new offsets. - The scheduling phase is necessarily message based.
Advertiser 16 seeking to insert a program must explicitly contacts_proxy 12 with a desired program start time and duration.s_proxy 12 must explicitly accept or deny the request, although the response can optionally contain additional information. For example, if an insertion request is denied because of a scheduling conflict, s_proxy 12 could return alternate available time slots. Reliability demands suggest that this portion of the protocol should be TCP-based. - Thus the
scheduler process 40 receives the incoming request from a server process and schedules an interrupt of the relay process. It is also possible, if desired, to make the scheduler a null process. This results in each insertion request immediately becoming an interrupt. The scheduler process receives the value of the advertisement duration from theserver process 50 and informs therelay process 30 to sleep for the specified duration. At the end of the secondary program, new timestamp and sequence number values are received from the advertiser (through the scheduler process) and are passed to therelay process 30. - While in many instances the stream from a sender will be privately unicast to a single s_proxy, the system can support multicast to multiple s_proxies. As in broadcast television, it is desirable to permit multiple distributors of the same content, with each distributor having its own relations with advertisers. A typical use would be broadcasting an event of international interest (e.g., World Cup Soccer) with different agents assigned distribution rights by country. Different distributors could then cater to their own sets of advertisers, and their respective audiences.
- By design, the implementation of
a_proxy 14 is very similar to that ofs_proxy 12. However, the scaling issues that arise for the s_proxy 12 (possibly needing to handle frequent incoming scheduling requests from many a_proxies) are not anticipated fora_proxy 14, permitting a simpler implementation.a_proxy 14 has a single process that does three jobs. First, it establishes a TCP connection tos_proxy 12 and requests an immediate time slot for program insertion. Only the intended secondary program duration is specified. For an immediate insertion, the SSRC and RTCP Session Description (SDES) parameters forsender 10 are returned, as well as the timestamp and sequence number of the most recently received sender packet.a_proxy 14 then calculates offsets for both timestamp and sequence number. That is, for seamless insertion, it is necessary for the stream transmitted by a_proxy 14 to pick up where thes_proxy 12 left off. This requires receiving the incoming advertiser's private stream, modifying RTP headers, and multicasting the modified stream on public destination multicast session. - Relaying the RTP stream from
advertiser 16 begins immediately. For each incoming packet the advertiser's SSRC is changed to that of thes_proxy 12, and appropriate timestamp and sequence number offsets are added. At the completion of the secondary program transmission, a_proxy 14 sends back tos_proxy 12 its last transmitted packet's timestamp and sequence number. At this time, thes_proxy 12 calculates new timestamp and sequence number offsets, then begins relaying the signal fromsender 10 once again, picking up whereadvertiser 16 left off. - Scheduling and control transfer phases can be implemented as coincident, or with arbitrary duration intervals between each phase. Note that in some applications scheduling insertions might be preceded by regular broadcast announcements of the availability of open time slots in a program schedule.
- While scheduling requires explicit messaging, control transfer from
s_proxy 12 to a_proxy 14 and control return froma_proxy 14 to s_proxy 12 can be implemented with implicit, or explicit messaging. In the implicit messaging model, no messages are sent betweens_proxy 12 anda_proxy 14 during the control transfer and control return phases. Instead, it is assumed that both parties are time synchronized by a separate out-of-band mechanism such as the Network Time Protocol described in D. Mills, “Network Time Protocol (Version 3) Specification, Implementation & Analysis,” Internet RFC 1305 (March 1992), hereby incorporated by reference as if fully set forth herein. This mechanism should be able to realize modestly precise time synchronization (e.g., 20 ms). This synchronized time is used by both a_proxy 14 and s_proxy 12 to determine when to start and stop relaying the respective content ofadvertiser 16 andsender 10. Each party monitors RTP packets on the destination session, and infers from this an appropriate timestamp and sequence number offset to use at the assumption of control. - For explicit messaging, several alternatives exist to transfer control. One option transmits two messages over a single TCP connection. These messages simply contain the RTP header of the last packet transmitted to the destination multicast session by the active proxy. This approach works well where immediate program insertion occurs upon request and s_proxy12 and
a_proxy 14 are geographically closely located. - A second embodiment uses messages based on the Real Time Streaming Protocol (RTSP) as described in H. Schulzrinne et al., “RTSP:A Transport Protocol for Real Time Applications,” Internet Draft (February 1998), hereby incorporated by reference as if fully set forth herein. Existing RTSP methods (e.g., SETUP, PLAY) could be used to trigger playout of stored advertisements located on video servers. In this embodiment, sender's and advertisers' proxies operate in part as RTSP proxies. Control transfer messages between these proxies are based on existing (or extensions to existing) RTSP control messages.
- For example, suppose an advertiser has scheduled a program insertion. Immediately prior to insertion time, the RTSP SETUP method could be used to pass transport parameters (e.g. SSRC, timestamp, sequence number) to the advertiser's proxy. At insertion time, the PLAY method would be sent by the sender's proxy to the advertiser's proxy to initiate advertisement playout. In this embodiment the communication between the sender and it's proxy, as well as the advertiser and its proxy, could also be performed using RTSP messages. For example, at a scheduled program insertion time, the sender's proxy could use the RTSP PAUSE method to interrupt the sender's communication, thus allowing the advertiser to insert content.
- A third embodiment of explicit messaging requires the destination multicast session be monitored by
s_proxy 12 anda_proxy 14. New RTCP application messages represent an explicit way to exchange necessary information to facilitate control transfer and return. In this embodiment, extensions to RTCP messages could serve as control transfer messages between sender and receiver proxies. Rather than using a separate communication channel (e.g. a TCP connection) between the proxies, the IP multicast session itself is used to transfer program control. For example, a new RTCP message could pass transport parameters (e.g. SSRC, timestamp, sequence number) from the sender's to the advertiser's proxy. This approach, however, is neither private (i.e., not unicast) nor reliable. - It is also possible to design a robust protocol by combining aspects of the foregoing three approaches. Deferred, remote playout could be triggered by an RTSP PLAY message sent in advance (e.g., several seconds or minutes) of a scheduled control transfer. Such a message would contain appropriate session control information (e.g. timestamp, sequence number and start time). In the event a deferred trigger message failed to arrive,
advertiser 16 could simply monitor the session and estimate these parameters independently and begin when scheduled. In the worst case,advertiser 16 would begin only after detecting that active transmissions have ceased. - Selecting from these alternatives should be done with an eye toward the goal of achieving “seamless” switching between
sender 10 andadvertiser 16. Switching between video sources transmitting less than 30 frames/sec fortunately affords some leeway in both the timing of transmitted packets and the calculation of timestamp offsets. - However, achieving seamless switching in a wide area setting requires consideration of the mean packet latency in the network. Consider the linear topology shown in FIG. 5 where two receivers,25 and 27, are connected to a_proxy 14 and
s_proxy 12 over links with specified mean packet latency. Suppose a_proxy 14 ands_proxy 12 are perfectly time synchronized,s_proxy 12 is to transfer control to a_proxy 14 which has the benefit of advance knowledge of the timestamp (time frame was captured), sequence number of packet and admission time (time packet was admitted in the network) of the last packet that s_proxy 12 will transmit. - If
a_proxy 14 transmits its first packet at exactly thetime s_proxy 12 would have transmitted its next packet, that first packet will nominally arrive late due to the additional delay inreceiver 25. On the other hand, a_proxy's 14 first packet might arrive atreceiver 27 before s_proxy's 12 final packet if the mean packet latency is not accounted for. Ifsender 10 andadvertiser 16 are not precisely synchronized anda_proxy 14 poorly estimates the stamp and sequence number, duplicate packets may result, causing the receivers to discard one or more packets. Poorly estimated timestamps could easily produce unintended, perceptible ‘freeze frame’, if for example the timestamp increases from frame to frame so that the playback is very slow. Conversely, ‘fast forward’ play occurs where the timestamp decreases from frame to subsequent frame. - RTP requires that the identifiers be unique for each source in a session, and recommends actions for sources to take in the unlikely event of collision. Accordingly, the RTP header must be appropriately handled to assure display of the primary and secondary programs in the same window.
- It is important to consider the handling of the RTCP messages which are critical to achieving the desired result. With respect to the data packet relayed by a proxy from provider to receiver, these two entities may be jointly owned or individually owned. Where the provider and proxy are jointly owned and operated by a single entity, the proxy could simply relay the provider's SDES and sender report (SR) messages, without modifying any identifying information (e.g. CNAME, EMAIL, PHONE, TOOL fields in SDES messages).
- Other applications, however, require that a content provider and its proxy (or proxies) be distinguished, as for example, where a content provider and one or more broadcasters are entirely separate entities. Here, each proxy should transmit its own session description and sender report messages, rather than relay these messages received from the provider.
- With respect to the relationship between the a_proxy and s_proxy, some applications such as advertisement insertion, editorial integrity and possibly legal and regulatory guidelines might require program and advertising content to be distinguishable by viewers. With other applications, however, a single broadcaster might wish to hide—or at least not call attention to—content being transmitted from distinct sources.
- In accordance with one embodiment of the present invention this is accomplished by insuring both content providers share a single SSRC identifier if they are to share a single window in the viewer. Other embodiments as explained below relax this requirement, relying instead on intelligent viewers.
- Similarly, current viewers will automatically open a second window upon receipt of an RTCP message containing a CNAME which is different from the CNAME associated with the RTP packet encapsulating the primary program. Thus proper handling of RTCP packets is necessary to assure the desired single window display. For example, it is possible to have the a_proxy modify and relay SDES messages from the advertiser so that they contain the same CNAME as any SDES messages issued by s_proxy. Some viewers, for example, the iCast viewer will accept this modification and perform the insertion with no difficulty. Other viewers, however, will recognize from the source IP address that the secondary program originated from a source different from the primary program and open a second window to display the secondary program. As applications such as program insertion become popular, uniform and proper handling of SSRC sharing among different viewers can be written into future versions of the RTP standard.
- Meanwhile it is still possible to implement program insertion in accordance with the present invention with current viewers by spoofing IP addresses, a technique known in the art, which can always be performed by a separate software mixer/translator application program located at any receiver. Such tools are widely available in the public domain. One such example is RTP Trans, available at http://www.cs.columbia.edu/˜hts/rtptools.
- In accordance with the RTP specification the data payload may be of any encoding type that a viewer can decode. Thus content providers may use any standard format for their audio and/or video. However, the secondary content provider should ensure that, independent of any chosen encoding scheme, with respect to video, a full frame should be sent first (e.g., an I-frame in MPEG-2). This is a common recommendation for any video mixing system, as described in Cable Television Laboratories, Inc. “Digital Program Insertion: Request for Information,” (April 1997), hereby incorporated by reference as if fully set forth herein.
- This recommendation is easily realized in stored programs. However, achieving this becomes more difficult for “live” insertions, and also when returning control to “live” programming content. One possible solution is to have each proxy, upon receiving session control, discard video data until a full frame is received. This suffers however, in that switching between sources will take a longer, more variable period of time (e.g., perhaps ½ second before receiving the next I-frame in a typical MPEG sequence).
- In accordance with the present invention as described above, several distinct advantages are enjoyed. First, the system is operable with existing transmitters and viewers. Second, secondary content providers can efficiently transmit their own content, obviating any need for first forwarding their programs to event broadcasters. Moreover, since the secondary content providers are responsible for transmitting their own content event broadcasters are relieved from unwanted administration and retransmission tasks. Third, because the transport medium is a bidirectional multicast network, there is no need to impose topological restrictions on program insertion points. Fourth, despite the fact that the source of packets varies during a session, viewers see seamless transitions between primary and secondary content.
- Fifth, advance scheduling of programs is not necessary because the secondary program is directly inserted by its owner (or proxy). Consequently, negotiating an insertion takes negligible time. Moreover, primary and secondary content providers should need no pre-existing relationship nor agreements. Furthermore, secondary content providers can tailor their insertions to current programming content, because spontaneous agreements can be realized. These advantages and others are not available with program insertion in either radio or television broadcasting.
- A further advantageous embodiment of the present invention is to provide for the simultaneous transmission of different secondary programs, such as advertisements, to different viewers. With multiple secondary programs available it is even possible for individual users to customize their reception by choosing among the different transmissions, or even choosing no advertisements at all. This can be accomplished by allowing viewers to specify an SSRC mask. The mask is a 32 bit number logically AND'ed with each incoming packet's 32 bit SSRC value. If the result equals the SSRC value of the desired session, then the packet is accepted as belonging to that stream.
- This approach effectively creates a set of SSRCs which can be used by advertisers to create separate. simulcast advertisement channels. For example, suppose receiver A has mask Oxffffff0f and receiver B has mask Oxfffffff0. Both receivers are tuned to a multicast session with SSRC identifier 0x55555500. Then, if during a ‘commercial’ break one advertiser begins transmitting with an SSRC identifier 0x55555501, this content will be accepted and played out by receiver B as a logical continuation of a programming sequence. If a second advertiser begins transmitting with an SSRC identifier 0x55555510, this content will be accepted and played out by receiver A. In the event of conflicts (i.e., multiple simultaneous streams with valid SSRCs), a conflict resolution procedure is invoked (e.g., packets with the lowest valid SSRC are played out, packets with other SSRCs are discarded).
- It should be noted that masking would require coordination of SSRCs among content providers. In addition each receiver would have to learn of and specify its desired SSRC mask. One manner in which this can be accomplished is through a session directory listings for a session and its related secondary program sub-channels.
- It should be obvious from the foregoing that back to back secondary programs are possible as well, much the same as multiple advertisements inserted during commercial breaks on radio and television. As requests for program insertion specify the length of the secondary program, the s_proxy is in a position to determine whether more than one request may be satisfied.
- In a further advantageous embodiment of the present invention, it is possible to minimize the perceived time required to switch between two sources by properly estimating an observed RTP stream's time stamp and sequence number at a future time. In general, conservative overestimates of future sequence numbers are preferred because receiving an RTP stream with missing sequence numbers is less harmful than receiving duplicates. Estimating a future timestamp for an RTP stream with a unknown constant timestamp rate is trivial. For unknown constant timestamp rates, acceptable estimates can be readily obtained after observing the session for just a few seconds.
- Returning to the plight of the sporting event organizers. With the ability for third parties to inject advertisements in real-time broadcasts, organizers now have a valuable commodity to sell—the ‘dead’ time in their programs. As we will see, the effort required is minimal and often simply an extension of what organizers are already doing by seeking industry sponsors and patrons. In the program insertion system of the present invention advertisers themselves are responsible for their ad production and insertion, freeing event organizers from involvement in re-broadcasting tasks. Advertisers would certainly seem to have considerable willingness-to-pay to place ads in content viewed by an audience with specific, identifiable and verifiable demographics. The additional revenues generated by advertising represent the assured funding required to enable organizers to broadcast a high quality production. These same revenues can indirectly contribute to network infrastructure improvement, since all parties are now interested in ensuring high quality viewer reception.
- The foregoing merely illustrates the principles of the present invention. Those skilled in the art will be able to devise various modifications, which although not explicitly described or shown herein, embody the principles of the invention and are thus within its spirit and scope.
Claims (15)
1. A program insertion system, comprising:
a) a primary program provider;
b) a first system for
i) transmitting a primary program from said primary program provider to subscribers, and
ii) receiving and scheduling at least one request for insertion of a secondary program during a pause in said transmission of said program;
c) a secondary program provider for providing said secondary program;
d) a second system for
i) transmitting said secondary program from said secondary program provider to subscribers, and
ii) issuing scheduling requests to said first system to insert said secondary program during said pause in said transmission of said primary program; and
e) an insertion protocol governing
i) the scheduling of transmission of said primary and secondary programs, and
ii) transfer of control between said first and said systems.
2. The program insertion system of claim 1 , wherein said secondary program provider is an advertiser and said secondary program comprises at least one advertisement.
3. The program insertion system of claim 1 , wherein said first system and said primary program provider are implemented in a single computer.
4. The program insertion system of claim 1 , wherein said second system and said secondary program provider are implemented in a single computer.
5. A method, comprising:
a) receiving program content from a content provider;
b) transmitting the program content over an Internet to a destination;
c) suspending transmission of the program content, to thereby suspend display of the program content at the destination, to allow an advertiser to send advertising over said Internet to said destination; and
d) resuming transmission of the program content to the destination.
6. Method according to claim 5 , and further comprising:
e) receiving a message indicating that a suspension should occur; and
f) suspending the transmission in response to the message.
7. Method according to claim 5 , and further comprising:
e) scheduling predetermined times and durations of suspension; and
g) suspending transmission of the program content at said predetermined times, for said durations.
8. Method according to claim 7 , wherein no messages are transmitted which induce the suspensions.
9. Method according to claim 5 , wherein the program content comprises audio, visual, or audio-visual material, and is transmitted in the form of packets, each containing a sequence number.
10. Method according to claim 9 , wherein sometimes a packet having a relatively late sequence number arrives at the destination before a packet having a relatively early sequence number.
11. Method according to claim 9 , wherein the advertising is transmitted in the form of packets, each containing a sequence number indicating its position in a sequence.
12. Method according to claim 11 , wherein,
i) prior to a suspension, a packet of program content having a sequence number N is transmitted; and then
ii) a packet of advertising having a sequence number N+1 is transmitted.
13. A method, comprising:
a) from a first location, transmitting program content over an Internet to a destination;
b) from the first location, sending a suspension signal to a second location indicating that transmission of the program content is to be suspended;
c) from the second location, in response to the suspension signal, transmitting advertising content over the Internet to the destination;
d) from the second location, transmitting a termination signal to the first location indicating that transmission of the advertising content is to be terminated; and
e) repeating the processes of paragraphs (a), (b), (c), and (d) at least once.
14. A method, comprising:
a) from a first location, transmitting program content over an Internet to a destination;
b) from a second location, transmitting advertising content over the Internet to the destination;
c) coordinating the transmissions from the first and second locations so that the transmissions arrive at the destination in the approximate chronological order of program—advertising—program—advertising—program—advertising, and so on,
thereby enabling equipment located at the destination to play the program content in a chronological sequence, interrupted periodically by the advertising content.
15. A method, comprising:
a) from a first location, transmitting program content over an Internet to a destination;
b) from a second location, transmitting advertising content over the Internet to the destination;
c) coordinating the transmissions from the first and second locations so that equipment located at the destination is able to construct both types of content in a chronological order following the following pattern: program—advertising—program—advertising—program—advertising, and so on.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/838,578 US20040210944A1 (en) | 1999-09-17 | 2004-05-04 | Program insertion in real time IP multicast |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/398,979 US6771644B1 (en) | 1999-09-17 | 1999-09-17 | Program insertion in real time IP multicast |
US10/838,578 US20040210944A1 (en) | 1999-09-17 | 2004-05-04 | Program insertion in real time IP multicast |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/398,979 Continuation US6771644B1 (en) | 1999-09-17 | 1999-09-17 | Program insertion in real time IP multicast |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040210944A1 true US20040210944A1 (en) | 2004-10-21 |
Family
ID=32771669
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/398,979 Expired - Lifetime US6771644B1 (en) | 1999-09-17 | 1999-09-17 | Program insertion in real time IP multicast |
US10/838,578 Abandoned US20040210944A1 (en) | 1999-09-17 | 2004-05-04 | Program insertion in real time IP multicast |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/398,979 Expired - Lifetime US6771644B1 (en) | 1999-09-17 | 1999-09-17 | Program insertion in real time IP multicast |
Country Status (1)
Country | Link |
---|---|
US (2) | US6771644B1 (en) |
Cited By (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010025377A1 (en) * | 1999-12-30 | 2001-09-27 | Hinderks Larry W. | High bandwidth transmission system and method having local insertion, delay play and demand play |
US20020023270A1 (en) * | 2000-04-17 | 2002-02-21 | Thomas C. Gomer | Three part architecture for digital television data broadcasting |
US20040151158A1 (en) * | 2002-11-08 | 2004-08-05 | Ecrio, Inc. | Method and apparatus for exchanging voice over data channels in near real time |
US20050021833A1 (en) * | 2001-08-29 | 2005-01-27 | Frank Hundscheid | Method and device for multicasting in a umts network |
US20050213668A1 (en) * | 2004-03-24 | 2005-09-29 | Kazunori Iwabuchi | Method and system for transmitting data of moving picture, and apparatus for delivering and receiving data of moving picture |
US20060013554A1 (en) * | 2004-07-01 | 2006-01-19 | Thomas Poslinski | Commercial storage and retrieval |
WO2006084503A1 (en) * | 2005-02-08 | 2006-08-17 | Telefonaktiebolaget Lm Ericsson (Publ) | On-demand multi-channel streaming session over packet-switched networks |
US20070079340A1 (en) * | 2005-09-30 | 2007-04-05 | Microsoft Corporation | Multi-room user interface |
US20070079325A1 (en) * | 2005-09-30 | 2007-04-05 | Microsoft Corporation | In-program content targeting |
US20070107011A1 (en) * | 2005-11-10 | 2007-05-10 | Zhi Li | System and method for differentiated service levels in an internet protocol television network |
US20070253675A1 (en) * | 2006-04-28 | 2007-11-01 | Weaver Timothy H | Methods, systems, and products for recording media |
US20070255915A1 (en) * | 2006-04-28 | 2007-11-01 | Timothy Weaver | Methods, systems, and products for recording media |
US20070294717A1 (en) * | 2005-07-08 | 2007-12-20 | Hill Peter N | Methods, systems, and products for conserving bandwidth |
US20070298772A1 (en) * | 2004-08-27 | 2007-12-27 | Owens Steve B | System and method for an interactive security system for a home |
GB2446201A (en) * | 2007-02-01 | 2008-08-06 | Wecomm Ltd | Switching between Real Time Protocol (RTP) streams |
US20080189338A1 (en) * | 2007-02-07 | 2008-08-07 | Weaver Timothy H | Methods, systems, and products for restoring media |
US20080189329A1 (en) * | 2007-02-07 | 2008-08-07 | Weaver Timothy H | Methods, systems, and products for targeting media |
US20080313669A1 (en) * | 2007-06-18 | 2008-12-18 | Swarup Acharya | Targeted Advertisement Insertion with Interface Device Assisted Switching |
US20090116458A1 (en) * | 2007-11-01 | 2009-05-07 | Rajaram Ramesh | Method and apparatus for efficient multimedia delivery in a wireless packet network |
US20090187941A1 (en) * | 2008-01-21 | 2009-07-23 | Att Knowledge Ventures L.P. | System and method for targeted advertising |
US20090210912A1 (en) * | 2008-02-19 | 2009-08-20 | Chris Cholas | Multi-stream premises apparatus and methods for use in a content-based network |
US20100050227A1 (en) * | 2008-08-25 | 2010-02-25 | Swarup Acharya | Update Process for Interface Device Based Targeted Information Insertion |
US20100058411A1 (en) * | 2006-11-16 | 2010-03-04 | Byung-Tak Lee | System and method supporting dynamic delivery of program time tables and broadcast programs |
US7697927B1 (en) | 2005-01-25 | 2010-04-13 | Embarq Holdings Company, Llc | Multi-campus mobile management system for wirelessly controlling systems of a facility |
US20100142521A1 (en) * | 2008-12-08 | 2010-06-10 | Concert Technology | Just-in-time near live DJ for internet radio |
US20100158047A1 (en) * | 2008-12-23 | 2010-06-24 | Samsung Electronics Co., Ltd. | Urgent packet transmission/reception apparatus and method for digital broadcast system |
US7765573B1 (en) | 2005-03-08 | 2010-07-27 | Embarq Holdings Company, LLP | IP-based scheduling and control of digital video content delivery |
US20100217885A1 (en) * | 2009-02-20 | 2010-08-26 | Swarup Acharya | Access Node Based Targeted Information Insertion |
US7840982B1 (en) * | 2004-09-28 | 2010-11-23 | Embarq Holding Company, Llc | Video-all call system and method for a facility |
US7840984B1 (en) | 2004-03-17 | 2010-11-23 | Embarq Holdings Company, Llc | Media administering system and method |
US20110078314A1 (en) * | 2009-09-29 | 2011-03-31 | Oki Networks Co., Ltd. | Signal processing device, signal processing program and communication system |
US8024765B2 (en) | 2006-07-26 | 2011-09-20 | Hewlett-Packard Development Company, L.P. | Method and system for communicating media program information |
US20110302600A1 (en) * | 2010-06-02 | 2011-12-08 | Time Warner Cable Inc. | Multicast Video Advertisement Insertion Using Routing Protocols |
US20120060184A1 (en) * | 2010-09-03 | 2012-03-08 | The Directv Group, Inc. | Method and system for automating advertising insertion and reconciliation |
US8237551B2 (en) | 2008-04-30 | 2012-08-07 | Centurylink Intellectual Property Llc | System and method for in-patient telephony |
US20130160047A1 (en) * | 2008-11-10 | 2013-06-20 | Time Warner Cable Inc. | System and method for enhanced advertising in a video content network |
US8819723B1 (en) * | 2000-04-27 | 2014-08-26 | The Directv Group, Inc. | System and method for brokering auxiliary data broadcasting services |
US20150229986A1 (en) * | 2012-08-30 | 2015-08-13 | Thomson Licensing | Rendering time control |
US9148707B2 (en) * | 2012-07-13 | 2015-09-29 | Lodgenet Interactive Corporation | System and method to provide out-of-band broadcast trigger synchronization and communication to insertion devices |
US20160073176A1 (en) * | 2014-09-10 | 2016-03-10 | Ericsson Television Inc. | Advertisement Targeting Scheme in a Multicast ABR Environment Based on Switched Video |
US20170070757A1 (en) * | 2015-09-09 | 2017-03-09 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (mabr) streaming network using multicast repeat segment bursts in a dedicated bandwidth pipe |
US20170070758A1 (en) * | 2015-09-09 | 2017-03-09 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (mabr) streaming network using multicast repeat segment bursts in a shared progressive abr download pipe |
US20180176624A1 (en) * | 2016-07-07 | 2018-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Bandwidth and ABR Video QoE Management Based On OTT Video Providers and Devices |
US10306301B2 (en) | 2007-06-13 | 2019-05-28 | Time Warner Cable Enterprises Llc | Apparatus and methods for use in a content distribution network |
US20190182520A1 (en) * | 2016-08-17 | 2019-06-13 | Nec Corporation | Bitrate instruction device, bitrate instruction method, and non-transitory recording medium |
USRE47819E1 (en) * | 2009-03-03 | 2020-01-14 | Ronald R. Davenport, JR. | Wired internet network system for the internet video streams of radio stations |
US20200037017A1 (en) * | 2016-09-30 | 2020-01-30 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
US20220124387A1 (en) * | 2020-01-16 | 2022-04-21 | Beijing Dajia Internet Information Technology Co., Ltd. | Method for training bit rate decision model, and electronic device |
US11317171B2 (en) | 2016-09-30 | 2022-04-26 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
EP3896575A4 (en) * | 2018-12-10 | 2022-11-02 | Kabushiki Kaisha Toshiba | Content distribution system, content distribution device, and method |
US20230247244A1 (en) * | 2020-08-18 | 2023-08-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Estimating video resolution delivered by an encrypted video stream |
US11856329B2 (en) * | 2008-04-11 | 2023-12-26 | Tivo Corporation | Dynamic advertisement stream replacement |
Families Citing this family (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6654933B1 (en) | 1999-09-21 | 2003-11-25 | Kasenna, Inc. | System and method for media stream indexing |
US7051337B2 (en) * | 2000-04-08 | 2006-05-23 | Sun Microsystems, Inc. | Method and apparatus for polling multiple sockets with a single thread and handling events received at the sockets with a pool of threads |
US6831917B1 (en) * | 2000-05-10 | 2004-12-14 | Cisco Technology, Inc. | Network address translation for multicast virtual sourcing |
US7191242B1 (en) | 2000-06-22 | 2007-03-13 | Apple, Inc. | Methods and apparatuses for transferring data |
US7136577B1 (en) * | 2000-06-29 | 2006-11-14 | Tandberg Telecom As | RTP-formated media clips |
US7310678B2 (en) * | 2000-07-28 | 2007-12-18 | Kasenna, Inc. | System, server, and method for variable bit rate multimedia streaming |
US7277956B2 (en) * | 2000-07-28 | 2007-10-02 | Kasenna, Inc. | System and method for improved utilization of bandwidth in a computer system serving multiple users |
US7221660B1 (en) * | 2000-08-08 | 2007-05-22 | E.F. Johnson Company | System and method for multicast communications using real time transport protocol (RTP) |
US7177520B2 (en) * | 2000-09-15 | 2007-02-13 | Ibm Corporation | System and method of timecode repair and synchronization in MPEG streams |
AU2002237748A1 (en) * | 2000-10-19 | 2002-05-21 | Loudeye Technologies, Inc. | System and method for selective insertion of content into streaming media |
WO2002041598A2 (en) * | 2000-11-17 | 2002-05-23 | Infineon Technologies North America Corp. | Priority handling of voice over data in a voice-over-internet protocol processor |
US7047273B2 (en) | 2000-11-28 | 2006-05-16 | Navic Systems, Inc. | Load balancing in set top cable box environment |
US7653743B2 (en) * | 2000-11-28 | 2010-01-26 | Microsoft Corporation | Protocol for throttling high volume messages |
JP2002209234A (en) * | 2001-01-11 | 2002-07-26 | Fujitsu Ltd | Communication system |
US20030018978A1 (en) * | 2001-03-02 | 2003-01-23 | Singal Sanjay S. | Transfer file format and system and method for distributing media content |
EP1374080A2 (en) * | 2001-03-02 | 2004-01-02 | Kasenna, Inc. | Metadata enabled push-pull model for efficient low-latency video-content distribution over a network |
US20020156841A1 (en) * | 2001-04-13 | 2002-10-24 | Bjorn Landfeldt | Accessing distributed proxy configurations |
AU2002312747A1 (en) * | 2001-05-15 | 2002-11-25 | Netadtack Aps | Method and system for transmitting multicast data signals |
US7401146B1 (en) * | 2001-05-21 | 2008-07-15 | Cisco Technology, Inc. | Method and apparatus for tracking related information in a network |
JP2003006085A (en) * | 2001-06-20 | 2003-01-10 | Nec Corp | Contents distribution system, its method and contents distribution program |
US20030028610A1 (en) * | 2001-08-03 | 2003-02-06 | Pearson Christopher Joel | Peer-to-peer file sharing system and method using user datagram protocol |
US7516236B2 (en) * | 2001-12-21 | 2009-04-07 | Nokia Corporation | Method to improve perceived access speed to data network content using a multicast channel and local cache |
EP1492089B1 (en) * | 2002-04-03 | 2007-06-06 | Dowa Mining Co., Ltd. | Powder for sublayer of coating type magnetic recording medium and magnetic recording medium comprising the same |
US20030227916A1 (en) * | 2002-06-06 | 2003-12-11 | Toni Paila | System and method for the multicast distribution of multimedia messaging service messages |
US20040199650A1 (en) * | 2002-11-14 | 2004-10-07 | Howe John E. | System and methods for accelerating data delivery |
US7417989B1 (en) | 2003-07-29 | 2008-08-26 | Sprint Spectrum L.P. | Method and system for actually identifying a media source in a real-time-protocol stream |
JP2005184640A (en) * | 2003-12-22 | 2005-07-07 | Fujitsu Ltd | Information distribution device and information distribution method |
US7567555B1 (en) * | 2004-03-22 | 2009-07-28 | At&T Corp. | Post answer call redirection via voice over IP |
US20050262245A1 (en) * | 2004-04-19 | 2005-11-24 | Satish Menon | Scalable cluster-based architecture for streaming media |
US7719992B1 (en) | 2004-07-14 | 2010-05-18 | Cisco Tchnology, Ink. | System for proactive time domain reflectometry |
US7870590B2 (en) * | 2004-10-20 | 2011-01-11 | Cisco Technology, Inc. | System and method for fast start-up of live multicast streams transmitted over a packet network |
SE0402876D0 (en) * | 2004-11-25 | 2004-11-25 | Ericsson Telefon Ab L M | TV-like standards-compliant unicast streaming over IP |
US20090064242A1 (en) * | 2004-12-23 | 2009-03-05 | Bitband Technologies Ltd. | Fast channel switching for digital tv |
US8730985B2 (en) | 2005-03-15 | 2014-05-20 | Time Warner Cable Enterprises Llc | Technique for providing on a program channel composite programming content attributed to different sources |
US7499395B2 (en) * | 2005-03-18 | 2009-03-03 | Cisco Technology, Inc. | BFD rate-limiting and automatic session activation |
US20060291468A1 (en) * | 2005-06-22 | 2006-12-28 | Rajendra Bopardikar | Selective re-transmission of lost multi-media data packets |
US8705515B2 (en) * | 2005-06-30 | 2014-04-22 | Qualcomm Incorporated | System and method for resolving conflicts in multiple simultaneous communications in a wireless system |
US8509727B2 (en) * | 2005-06-30 | 2013-08-13 | At&T Intellectual Property I, L.P. | Emergency alert systems and methods |
US20080320530A1 (en) * | 2005-08-26 | 2008-12-25 | Weaver Timothy H | Methods, apparatuses, and computer program products for delivering video on demand content |
US7429983B2 (en) * | 2005-11-01 | 2008-09-30 | Cheetah Omni, Llc | Packet-based digital display system |
US8340098B2 (en) * | 2005-12-07 | 2012-12-25 | General Instrument Corporation | Method and apparatus for delivering compressed video to subscriber terminals |
US8539091B2 (en) * | 2005-12-21 | 2013-09-17 | Cisco Technology, Inc. | Method and system for preempting control of data streaming |
US7793329B2 (en) * | 2006-02-06 | 2010-09-07 | Kasenna, Inc. | Method and system for reducing switching delays between digital video feeds using multicast slotted transmission technique |
US7965771B2 (en) | 2006-02-27 | 2011-06-21 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
US20090307732A1 (en) * | 2006-03-07 | 2009-12-10 | Noam Cohen | Personalized Insertion of Advertisements in Streaming Media |
US8218654B2 (en) * | 2006-03-08 | 2012-07-10 | Cisco Technology, Inc. | Method for reducing channel change startup delays for multicast digital video streams |
US7694002B2 (en) * | 2006-04-07 | 2010-04-06 | Cisco Technology, Inc. | System and method for dynamically upgrading / downgrading a conference session |
US20070263824A1 (en) * | 2006-04-18 | 2007-11-15 | Cisco Technology, Inc. | Network resource optimization in a video conference |
US8326927B2 (en) * | 2006-05-23 | 2012-12-04 | Cisco Technology, Inc. | Method and apparatus for inviting non-rich media endpoints to join a conference sidebar session |
US7466694B2 (en) * | 2006-06-10 | 2008-12-16 | Cisco Technology, Inc. | Routing protocol with packet network attributes for improved route selection |
US8526336B2 (en) * | 2006-08-09 | 2013-09-03 | Cisco Technology, Inc. | Conference resource allocation and dynamic reallocation |
US8358763B2 (en) * | 2006-08-21 | 2013-01-22 | Cisco Technology, Inc. | Camping on a conference or telephony port |
US7916653B2 (en) | 2006-09-06 | 2011-03-29 | Cisco Technology, Inc. | Measurement of round-trip delay over a network |
US8031701B2 (en) | 2006-09-11 | 2011-10-04 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US8120637B2 (en) * | 2006-09-20 | 2012-02-21 | Cisco Technology, Inc. | Virtual theater system for the home |
US7847815B2 (en) | 2006-10-11 | 2010-12-07 | Cisco Technology, Inc. | Interaction based on facial recognition of conference participants |
US20080109557A1 (en) * | 2006-11-02 | 2008-05-08 | Vinay Joshi | Method and system for reducing switching delays between digital video feeds using personalized unicast transmission techniques |
US8046479B2 (en) * | 2006-11-07 | 2011-10-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Media channel management |
US7693190B2 (en) * | 2006-11-22 | 2010-04-06 | Cisco Technology, Inc. | Lip synchronization for audio/video transmissions over a network |
US8121277B2 (en) * | 2006-12-12 | 2012-02-21 | Cisco Technology, Inc. | Catch-up playback in a conferencing system |
US8144631B2 (en) * | 2006-12-13 | 2012-03-27 | Cisco Technology, Inc. | Interconnecting IP video endpoints with reduced H.320 call setup time |
US8149261B2 (en) * | 2007-01-10 | 2012-04-03 | Cisco Technology, Inc. | Integration of audio conference bridge with video multipoint control unit |
US7616650B2 (en) * | 2007-02-05 | 2009-11-10 | Cisco Technology, Inc. | Video flow control and non-standard capability exchange for an H.320 call leg |
US8769591B2 (en) | 2007-02-12 | 2014-07-01 | Cisco Technology, Inc. | Fast channel change on a bandwidth constrained network |
US8014322B2 (en) * | 2007-02-26 | 2011-09-06 | Cisco, Technology, Inc. | Diagnostic tool for troubleshooting multimedia streaming applications |
US8208003B2 (en) * | 2007-03-23 | 2012-06-26 | Cisco Technology, Inc. | Minimizing fast video update requests in a video conferencing system |
US20080253369A1 (en) | 2007-04-16 | 2008-10-16 | Cisco Technology, Inc. | Monitoring and correcting upstream packet loss |
US8386304B2 (en) * | 2007-05-29 | 2013-02-26 | Yu Chen | Methods for interactive television and mobile device |
WO2008150540A1 (en) | 2007-06-04 | 2008-12-11 | Visible World, Inc. | Systems and methods for dynamic bit/bandwidth allocation |
US8289839B2 (en) * | 2007-07-05 | 2012-10-16 | Cisco Technology, Inc. | Scaling BFD sessions for neighbors using physical / sub-interface relationships |
US8526315B2 (en) * | 2007-08-23 | 2013-09-03 | Cisco Technology, Inc. | Flow state attributes for producing media flow statistics at a network node |
US8289362B2 (en) * | 2007-09-26 | 2012-10-16 | Cisco Technology, Inc. | Audio directionality control for a multi-display switched video conferencing system |
US9003302B1 (en) | 2007-12-05 | 2015-04-07 | Sprint Spectrum L.P. | Anonymous sidebar method and system |
US8700792B2 (en) * | 2008-01-31 | 2014-04-15 | General Instrument Corporation | Method and apparatus for expediting delivery of programming content over a broadband network |
US8787153B2 (en) | 2008-02-10 | 2014-07-22 | Cisco Technology, Inc. | Forward error correction based data recovery with path diversity |
US8935720B1 (en) | 2008-03-20 | 2015-01-13 | Sprint Communications Company L. P. | Multimedia ad delivery |
US9407940B1 (en) | 2008-03-20 | 2016-08-02 | Sprint Communications Company L.P. | User-targeted ad insertion in streaming media |
GB2458693A (en) * | 2008-03-28 | 2009-09-30 | Malcolm John Siddall | Insertion of advertisement content into website images |
US20090259764A1 (en) * | 2008-04-11 | 2009-10-15 | Mobitv, Inc. | Intro outro merger with bit rate variation support |
US8260950B1 (en) | 2008-06-11 | 2012-09-04 | Sprint Communications Company L.P. | Real-time transport protocol ad cue extensions |
US8752092B2 (en) * | 2008-06-27 | 2014-06-10 | General Instrument Corporation | Method and apparatus for providing low resolution images in a broadcast system |
US8631453B2 (en) * | 2008-10-02 | 2014-01-14 | Sony Corporation | Video branching |
CN101453474B (en) * | 2008-12-30 | 2011-12-07 | 中兴通讯股份有限公司 | Terminal, information inserting system and method |
US9525710B2 (en) * | 2009-01-29 | 2016-12-20 | Avaya Gmbh & Co., Kg | Seamless switch over from centralized to decentralized media streaming |
US9137708B2 (en) * | 2009-05-28 | 2015-09-15 | Citrix Systems, Inc. | Mechanism for application mobility in a cell site-based content distribution network |
US9357244B2 (en) * | 2010-03-11 | 2016-05-31 | Arris Enterprises, Inc. | Method and system for inhibiting audio-video synchronization delay |
US9277263B2 (en) * | 2010-03-15 | 2016-03-01 | At&T Intellectual Property I, Lp | System and method for in-band delivery of advertising decision data |
US9998890B2 (en) | 2010-07-29 | 2018-06-12 | Paul Marko | Method and apparatus for content navigation in digital broadcast radio |
US9319721B2 (en) | 2011-10-13 | 2016-04-19 | Electronics And Telecommunications Research Institute | Method of configuring and transmitting an MMT transport packet |
US9015555B2 (en) | 2011-11-18 | 2015-04-21 | Cisco Technology, Inc. | System and method for multicast error recovery using sampled feedback |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4404589A (en) * | 1980-10-21 | 1983-09-13 | Iri, Inc. | Cable television with multi-event signal substitution |
US6070186A (en) * | 1995-06-21 | 2000-05-30 | Nec Corporation | Video server and video-on-demand system capable of effectively transmitting a special video program |
US6172712B1 (en) * | 1997-12-31 | 2001-01-09 | Intermec Ip Corp. | Television with hard disk drive |
US6434319B1 (en) * | 1994-01-19 | 2002-08-13 | Thomson Licensing S.A. | Digital video tape recorder for digital HDTV |
US6487538B1 (en) * | 1998-11-16 | 2002-11-26 | Sun Microsystems, Inc. | Method and apparatus for local advertising |
US6698020B1 (en) * | 1998-06-15 | 2004-02-24 | Webtv Networks, Inc. | Techniques for intelligent video ad insertion |
US7006881B1 (en) * | 1991-12-23 | 2006-02-28 | Steven Hoffberg | Media recording device with remote graphic user interface |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5305195A (en) * | 1992-03-25 | 1994-04-19 | Gerald Singer | Interactive advertising system for on-line terminals |
WO1997012486A1 (en) * | 1995-09-29 | 1997-04-03 | Boston Technology, Inc. | Multimedia architecture for interactive advertising |
US5778187A (en) * | 1996-05-09 | 1998-07-07 | Netcast Communications Corp. | Multicasting method and apparatus |
US5854897A (en) * | 1996-12-27 | 1998-12-29 | Quantum Systems, Inc. | Network communications marketing system |
US6009409A (en) * | 1997-04-02 | 1999-12-28 | Lucent Technologies, Inc. | System and method for scheduling and controlling delivery of advertising in a communications network |
US6351467B1 (en) * | 1997-10-27 | 2002-02-26 | Hughes Electronics Corporation | System and method for multicasting multimedia content |
US6311185B1 (en) * | 1997-10-30 | 2001-10-30 | At&T Corp. | Method and apparatus for modifying an information page transmitted in a communications network |
US6160585A (en) * | 1997-12-15 | 2000-12-12 | Motorola, Inc. | System for selective multicasting in a communications system |
-
1999
- 1999-09-17 US US09/398,979 patent/US6771644B1/en not_active Expired - Lifetime
-
2004
- 2004-05-04 US US10/838,578 patent/US20040210944A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4404589A (en) * | 1980-10-21 | 1983-09-13 | Iri, Inc. | Cable television with multi-event signal substitution |
US7006881B1 (en) * | 1991-12-23 | 2006-02-28 | Steven Hoffberg | Media recording device with remote graphic user interface |
US6434319B1 (en) * | 1994-01-19 | 2002-08-13 | Thomson Licensing S.A. | Digital video tape recorder for digital HDTV |
US6070186A (en) * | 1995-06-21 | 2000-05-30 | Nec Corporation | Video server and video-on-demand system capable of effectively transmitting a special video program |
US6172712B1 (en) * | 1997-12-31 | 2001-01-09 | Intermec Ip Corp. | Television with hard disk drive |
US6698020B1 (en) * | 1998-06-15 | 2004-02-24 | Webtv Networks, Inc. | Techniques for intelligent video ad insertion |
US6487538B1 (en) * | 1998-11-16 | 2002-11-26 | Sun Microsystems, Inc. | Method and apparatus for local advertising |
Cited By (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010025377A1 (en) * | 1999-12-30 | 2001-09-27 | Hinderks Larry W. | High bandwidth transmission system and method having local insertion, delay play and demand play |
US20020023270A1 (en) * | 2000-04-17 | 2002-02-21 | Thomas C. Gomer | Three part architecture for digital television data broadcasting |
US7305696B2 (en) * | 2000-04-17 | 2007-12-04 | Triveni Digital, Inc. | Three part architecture for digital television data broadcasting |
US8819723B1 (en) * | 2000-04-27 | 2014-08-26 | The Directv Group, Inc. | System and method for brokering auxiliary data broadcasting services |
US20050021833A1 (en) * | 2001-08-29 | 2005-01-27 | Frank Hundscheid | Method and device for multicasting in a umts network |
US20040151158A1 (en) * | 2002-11-08 | 2004-08-05 | Ecrio, Inc. | Method and apparatus for exchanging voice over data channels in near real time |
US7840984B1 (en) | 2004-03-17 | 2010-11-23 | Embarq Holdings Company, Llc | Media administering system and method |
US20050213668A1 (en) * | 2004-03-24 | 2005-09-29 | Kazunori Iwabuchi | Method and system for transmitting data of moving picture, and apparatus for delivering and receiving data of moving picture |
US7681224B2 (en) * | 2004-03-24 | 2010-03-16 | Hitachi, Ltd. | Method and system for transmitting data of moving picture, and apparatus for delivering and receiving data of moving picture |
US20060013554A1 (en) * | 2004-07-01 | 2006-01-19 | Thomas Poslinski | Commercial storage and retrieval |
US7786891B2 (en) | 2004-08-27 | 2010-08-31 | Embarq Holdings Company, Llc | System and method for an interactive security system for a home |
US20070298772A1 (en) * | 2004-08-27 | 2007-12-27 | Owens Steve B | System and method for an interactive security system for a home |
US7840982B1 (en) * | 2004-09-28 | 2010-11-23 | Embarq Holding Company, Llc | Video-all call system and method for a facility |
US7697927B1 (en) | 2005-01-25 | 2010-04-13 | Embarq Holdings Company, Llc | Multi-campus mobile management system for wirelessly controlling systems of a facility |
US20080151885A1 (en) * | 2005-02-08 | 2008-06-26 | Uwe Horn | On-Demand Multi-Channel Streaming Session Over Packet-Switched Networks |
WO2006084503A1 (en) * | 2005-02-08 | 2006-08-17 | Telefonaktiebolaget Lm Ericsson (Publ) | On-demand multi-channel streaming session over packet-switched networks |
US7765573B1 (en) | 2005-03-08 | 2010-07-27 | Embarq Holdings Company, LLP | IP-based scheduling and control of digital video content delivery |
US20070294717A1 (en) * | 2005-07-08 | 2007-12-20 | Hill Peter N | Methods, systems, and products for conserving bandwidth |
US9432710B2 (en) | 2005-07-08 | 2016-08-30 | At&T Intellectual Property I, L.P. | Methods systems, and products for conserving bandwidth |
US20070079325A1 (en) * | 2005-09-30 | 2007-04-05 | Microsoft Corporation | In-program content targeting |
US8132203B2 (en) | 2005-09-30 | 2012-03-06 | Microsoft Corporation | In-program content targeting |
US20070079340A1 (en) * | 2005-09-30 | 2007-04-05 | Microsoft Corporation | Multi-room user interface |
US8713607B2 (en) * | 2005-09-30 | 2014-04-29 | Microsoft Corporation | Multi-room user interface |
US8745659B2 (en) | 2005-09-30 | 2014-06-03 | Microsoft Corporation | In-program content targeting |
US20070107011A1 (en) * | 2005-11-10 | 2007-05-10 | Zhi Li | System and method for differentiated service levels in an internet protocol television network |
US20070255915A1 (en) * | 2006-04-28 | 2007-11-01 | Timothy Weaver | Methods, systems, and products for recording media |
US8682857B2 (en) | 2006-04-28 | 2014-03-25 | At&T Intellectual Property I, L.P. | Methods, systems, and products for recording media |
US20070253675A1 (en) * | 2006-04-28 | 2007-11-01 | Weaver Timothy H | Methods, systems, and products for recording media |
US20100077166A1 (en) * | 2006-04-28 | 2010-03-25 | At&T Intellectual Property I, L.P. F/K/A Bellsouth Intellectual Property Corporation | Methods, systems, and products for recording media |
US7647464B2 (en) | 2006-04-28 | 2010-01-12 | At&T Intellectual Property, I,L.P. | Methods, systems, and products for recording media to a restoration server |
US8291182B2 (en) | 2006-04-28 | 2012-10-16 | At&T Intellectual Property I, L.P. | Methods, systems, and products for recording media |
US8364921B2 (en) | 2006-04-28 | 2013-01-29 | At&T Intellectual Property I, L.P. | Methods, systems, and products for recording media |
US8024765B2 (en) | 2006-07-26 | 2011-09-20 | Hewlett-Packard Development Company, L.P. | Method and system for communicating media program information |
US20100058411A1 (en) * | 2006-11-16 | 2010-03-04 | Byung-Tak Lee | System and method supporting dynamic delivery of program time tables and broadcast programs |
US20080209072A1 (en) * | 2007-02-01 | 2008-08-28 | Wecomm Limited | Data Transmission |
GB2446201A (en) * | 2007-02-01 | 2008-08-06 | Wecomm Ltd | Switching between Real Time Protocol (RTP) streams |
US20080189329A1 (en) * | 2007-02-07 | 2008-08-07 | Weaver Timothy H | Methods, systems, and products for targeting media |
US20100185613A1 (en) * | 2007-02-07 | 2010-07-22 | At&T Intellectual Property I, L.P. F/K/A Bellsouth Intellectual Property Corporation | Method, device, and computer program product for targeting media |
US20080189338A1 (en) * | 2007-02-07 | 2008-08-07 | Weaver Timothy H | Methods, systems, and products for restoring media |
US7711733B2 (en) | 2007-02-07 | 2010-05-04 | At&T Intellectual Property I,L.P. | Methods, systems, and products for targeting media for storage to communications devices |
US8150845B2 (en) | 2007-02-07 | 2012-04-03 | At&T Intellectual Property I, L.P. | Method, device, and computer program product for targeting media for storage to a communications device |
US7650368B2 (en) | 2007-02-07 | 2010-01-19 | At&T Intellectual Property I, L.P. | Methods, systems, and products for restoring electronic media |
US11641504B2 (en) | 2007-06-13 | 2023-05-02 | Time Warner Cable Enterprises Llc | Gateway apparatus and methods for use in a content distribution network |
US10306301B2 (en) | 2007-06-13 | 2019-05-28 | Time Warner Cable Enterprises Llc | Apparatus and methods for use in a content distribution network |
US20080313669A1 (en) * | 2007-06-18 | 2008-12-18 | Swarup Acharya | Targeted Advertisement Insertion with Interface Device Assisted Switching |
US8949886B2 (en) | 2007-06-18 | 2015-02-03 | Alcatel Lucent | Targeted advertisement insertion with interface device assisted switching |
US20120147860A1 (en) * | 2007-11-01 | 2012-06-14 | Rajaram Ramesh | Method and apparatus for efficient multimedia delivery in a wireless packet network |
CN101843074A (en) * | 2007-11-01 | 2010-09-22 | 爱立信电话股份有限公司 | Method and apparatus for efficient multimedia delivery in a wireless packet network |
US20090116458A1 (en) * | 2007-11-01 | 2009-05-07 | Rajaram Ramesh | Method and apparatus for efficient multimedia delivery in a wireless packet network |
US8155090B2 (en) * | 2007-11-01 | 2012-04-10 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for efficient multimedia delivery in a wireless packet network |
US8855086B2 (en) * | 2007-11-01 | 2014-10-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for efficient multimedia delivery in a wireless packet network |
US20090187941A1 (en) * | 2008-01-21 | 2009-07-23 | Att Knowledge Ventures L.P. | System and method for targeted advertising |
US9743142B2 (en) * | 2008-02-19 | 2017-08-22 | Time Warner Cable Enterprises Llc | Multi-stream premises apparatus and methods for use in a content delivery network |
US20090210912A1 (en) * | 2008-02-19 | 2009-08-20 | Chris Cholas | Multi-stream premises apparatus and methods for use in a content-based network |
US11856329B2 (en) * | 2008-04-11 | 2023-12-26 | Tivo Corporation | Dynamic advertisement stream replacement |
US8610576B2 (en) | 2008-04-30 | 2013-12-17 | Centurylink Intellectual Property Llc | Routing communications to a person within a facility |
US8237551B2 (en) | 2008-04-30 | 2012-08-07 | Centurylink Intellectual Property Llc | System and method for in-patient telephony |
US8910197B2 (en) | 2008-08-25 | 2014-12-09 | Alcatel Lucent | Update process for interface device based targeted information insertion |
US20100050227A1 (en) * | 2008-08-25 | 2010-02-25 | Swarup Acharya | Update Process for Interface Device Based Targeted Information Insertion |
US8566862B2 (en) * | 2008-11-10 | 2013-10-22 | Time Warner Cable Enterprises Llc | System and method for enhanced advertising in a video content network |
US20130160047A1 (en) * | 2008-11-10 | 2013-06-20 | Time Warner Cable Inc. | System and method for enhanced advertising in a video content network |
US20100142521A1 (en) * | 2008-12-08 | 2010-06-10 | Concert Technology | Just-in-time near live DJ for internet radio |
US20100158047A1 (en) * | 2008-12-23 | 2010-06-24 | Samsung Electronics Co., Ltd. | Urgent packet transmission/reception apparatus and method for digital broadcast system |
US20100217885A1 (en) * | 2009-02-20 | 2010-08-26 | Swarup Acharya | Access Node Based Targeted Information Insertion |
US9306765B2 (en) | 2009-02-20 | 2016-04-05 | Alcatel Lucent | Access node based targeted information insertion |
USRE47819E1 (en) * | 2009-03-03 | 2020-01-14 | Ronald R. Davenport, JR. | Wired internet network system for the internet video streams of radio stations |
US20110078314A1 (en) * | 2009-09-29 | 2011-03-31 | Oki Networks Co., Ltd. | Signal processing device, signal processing program and communication system |
US9264456B2 (en) * | 2009-09-29 | 2016-02-16 | Oki Electric Industry Co., Ltd. | Signal processing device, signal processing program and communication system |
US8910198B2 (en) * | 2010-06-02 | 2014-12-09 | Time Warner Cable Enterprises Llc | Multicast video advertisement insertion using routing protocols |
US9124928B2 (en) | 2010-06-02 | 2015-09-01 | Time Warner Cable Enterprises Llc | Multicast video advertisement insertion using routing protocols |
US20110302600A1 (en) * | 2010-06-02 | 2011-12-08 | Time Warner Cable Inc. | Multicast Video Advertisement Insertion Using Routing Protocols |
US8799941B2 (en) * | 2010-09-03 | 2014-08-05 | The Directv Group, Inc. | Method and system for automating advertising insertion and reconciliation |
US20120060184A1 (en) * | 2010-09-03 | 2012-03-08 | The Directv Group, Inc. | Method and system for automating advertising insertion and reconciliation |
US9148707B2 (en) * | 2012-07-13 | 2015-09-29 | Lodgenet Interactive Corporation | System and method to provide out-of-band broadcast trigger synchronization and communication to insertion devices |
US20150229986A1 (en) * | 2012-08-30 | 2015-08-13 | Thomson Licensing | Rendering time control |
US10057624B2 (en) * | 2012-08-30 | 2018-08-21 | Thomson Licensing | Synchronization of content rendering |
US9560404B2 (en) | 2014-09-10 | 2017-01-31 | Ericsson Ab | Advertisement targeting scheme in a multicast ABR environment based on ad caching |
US9756374B2 (en) * | 2014-09-10 | 2017-09-05 | Ericsson Ab | Advertisement targeting scheme in a multicast ABR environment based on throttled ad channel streaming |
US9621938B2 (en) * | 2014-09-10 | 2017-04-11 | Ericsson Ab | Advertisement targeting scheme in a multicast ABR environment based on switched video |
US20160073176A1 (en) * | 2014-09-10 | 2016-03-10 | Ericsson Television Inc. | Advertisement Targeting Scheme in a Multicast ABR Environment Based on Switched Video |
US20170070757A1 (en) * | 2015-09-09 | 2017-03-09 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (mabr) streaming network using multicast repeat segment bursts in a dedicated bandwidth pipe |
US9826261B2 (en) * | 2015-09-09 | 2017-11-21 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (MABR) streaming network using multicast repeat segment bursts in a dedicated bandwidth pipe |
US10194181B2 (en) | 2015-09-09 | 2019-01-29 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (MABR) streaming network using multicast repeat segment bursts in a dedicated bandwidth pipe |
US20170070758A1 (en) * | 2015-09-09 | 2017-03-09 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (mabr) streaming network using multicast repeat segment bursts in a shared progressive abr download pipe |
US9826262B2 (en) * | 2015-09-09 | 2017-11-21 | Ericsson Ab | Fast channel change in a multicast adaptive bitrate (MABR) streaming network using multicast repeat segment bursts in a shared progressive ABR download pipe |
US20180176624A1 (en) * | 2016-07-07 | 2018-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Bandwidth and ABR Video QoE Management Based On OTT Video Providers and Devices |
US10939153B2 (en) * | 2016-07-07 | 2021-03-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Bandwidth and ABR video QoE management based on OTT video providers and devices |
US20190182520A1 (en) * | 2016-08-17 | 2019-06-13 | Nec Corporation | Bitrate instruction device, bitrate instruction method, and non-transitory recording medium |
US10911804B2 (en) * | 2016-08-17 | 2021-02-02 | Nec Corporation | Bitrate instruction device, bitrate instruction method, and non-transitory recording medium |
US20200037017A1 (en) * | 2016-09-30 | 2020-01-30 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
US11317171B2 (en) | 2016-09-30 | 2022-04-26 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
US11044507B2 (en) | 2016-09-30 | 2021-06-22 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
US10931993B2 (en) * | 2016-09-30 | 2021-02-23 | British Telecommunications Public Limited Company | Viewer importance adaptive bit rate delivery |
EP3896575A4 (en) * | 2018-12-10 | 2022-11-02 | Kabushiki Kaisha Toshiba | Content distribution system, content distribution device, and method |
US20220124387A1 (en) * | 2020-01-16 | 2022-04-21 | Beijing Dajia Internet Information Technology Co., Ltd. | Method for training bit rate decision model, and electronic device |
US20230247244A1 (en) * | 2020-08-18 | 2023-08-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Estimating video resolution delivered by an encrypted video stream |
Also Published As
Publication number | Publication date |
---|---|
US6771644B1 (en) | 2004-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6771644B1 (en) | Program insertion in real time IP multicast | |
US7530086B2 (en) | Media program timing and identity delivery method and system | |
EP1854018B1 (en) | Playout-dependent unicast streaming of digital video content | |
JP5788473B2 (en) | Method and system for synchronizing terminal output | |
US7558262B2 (en) | Group hopping and channel zapping during transmission of multicast applications | |
JP5442766B2 (en) | Multimedia stream access delivery changes supported by the service layer | |
US9185151B2 (en) | Device, method and system for media packet distribution | |
EP1919113A2 (en) | Time-shifted broadcast delivery | |
US20070005792A1 (en) | Method and apparatus for managing bandwidth requirements for video on demand services | |
US20090168679A1 (en) | Method and Device for Providing Programs to Multiple End User Devices | |
CN101548275A (en) | Multicast delivery of multimedia content on demand | |
US9521466B2 (en) | Method and device for receiving and providing programs | |
KR20080106517A (en) | Methods, apparatus, and systems for providing media content over a communications network | |
EP2022209A1 (en) | Multicast control | |
Brassil et al. | Structuring internet media streams with cueing protocols | |
Brassil et al. | Program insertion in real-time IP multicasts | |
Brassil et al. | Enhancing internet streaming media with cueing protocols | |
JP3836843B2 (en) | Method for receiving content distributed by multiple channels via information network by one terminal | |
JP5225394B2 (en) | Method and system for distributing TV content via network | |
CN101188740A (en) | Multicast method for living broadcast network TV | |
US8239902B2 (en) | Method and apparatus for bandwidth optimization of a content on demand service | |
US20090240825A1 (en) | Delivering streaming data | |
WO2008095314A1 (en) | System and method for distributed and dynamic transcoding | |
Brassil et al. | Large-scale personalized video streaming with program insertion proxies | |
GB2605575A (en) | Content Delivery |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:ALCATEL-LUCENT USA INC.;REEL/FRAME:030510/0627 Effective date: 20130130 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033949/0016 Effective date: 20140819 |