US20080052404A1 - Method and system for fault tolerant media streaming over the Internet - Google Patents
Method and system for fault tolerant media streaming over the Internet Download PDFInfo
- Publication number
- US20080052404A1 US20080052404A1 US11/928,042 US92804207A US2008052404A1 US 20080052404 A1 US20080052404 A1 US 20080052404A1 US 92804207 A US92804207 A US 92804207A US 2008052404 A1 US2008052404 A1 US 2008052404A1
- Authority
- US
- United States
- Prior art keywords
- stream
- media
- signal
- copies
- concentrator
- 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/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
- H04N21/26616—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel for merging a unicast channel into a multicast channel, e.g. in a VOD application, when a client served by unicast channel catches up a multicast channel to save bandwidth
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/613—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for the control of the source by the destination
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/70—Media network packetisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/75—Media network packet handling
- H04L65/765—Media network packet handling intermediate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
Definitions
- the present invention relates generally to digital signal transmission over a computer network and, in particular, to a method and system for streaming content over the Internet in a fault tolerant manner.
- Streaming is a technique for delivering web-based video, audio and multimedia files so that these files can be processed as a steady and continuous stream at the requesting client, typically using a browser plug-in, such as Microsoft NetPlayer, Apple QuickTime, Real Networks RealSystem G2, or the like.
- Streaming video for example, is an online video distribution mechanism that provides audio and video to Internet users, without the users having to wait while content completely downloads to their hard drives. Through caching, content is played as it is received, and buffering mechanisms ensure that content is played smoothly. Theoretically, streaming video plays to the end user, or viewer, as an immediate and ongoing broadcast.
- a splitter or repeater, reflector or mirror
- a splitter or repeater, reflector or mirror
- Each of the multiple signals is the same, and each is sent on to a different destination.
- splitters By cascading splitters in a tree-like fashion, a single source stream can be replicated into thousands or more identical copies. In this manner, a large number of viewers on the Internet can receive the same streaming signal simultaneously.
- FIG. 1 illustrates why this is the case.
- a source signal (A) is sent to a splitter (B), which then sends copies of the signal to ten splitters (C 1 , . . . , C 10 ).
- Each of the second level splitters then sends a copy of the signal to five end customers (D 1 , . . . , D 50 ).
- splitter C 1 sends a copy to end users D 1 -D 5
- splitter C 2 sends a copy to end users D 6 -D 10 , and so forth. If communications at a given splitter fail, however, certain users are unable to receive the original signal.
- the present invention provides a replication process to provide fault tolerance for a streaming signal in a computer network.
- the original or source signal is sent to several splitters which, in turn, each make copies of the signal and send the copies into a second layer of devices, which are referred to as “concentrators.”
- a given concentrator receives as input one or more copies of the source signal.
- a given concentrator receives two copies of the source signal from at least two different splitters.
- the concentrators process the incoming streaming signal copies, for example, by merging them into a single or composite copy of the original source signal according to a given processing algorithm.
- a given concentrator receives streams from multiple sources, removes duplicate packets, and then outputs a single stream.
- the output of a given concentrator may then be fed into a splitter, with the process then being repeated if desired to make an arbitrary large number of copies of the signal.
- the output of a splitter or a concentrator is fed directly or indirectly to an end user.
- the replication process is fault-tolerant, and thus the end user's signal is not interrupted regardless of signal or equipment problems within the distribution mechanism.
- One type of processing algorithm that is implemented at a concentrator simply transmits the first copy of each packet in the signal stream. Copies of packets that have already been transmitted are simply discarded.
- This algorithm may be implemented by maintaining a data array f(i) that has a first value (e.g., “1”) if packet i in the stream has been forwarded and f(i) that has a second value (e.g., “0”) otherwise.
- f(i) When a copy of packet i is received from one of the incoming streams, it is forwarded if and only if f(i) equals the second value.
- This technique is advantageous because a complete stream can be reconstructed from two or more partial streams. Thus, as long as the incoming copies of the stream collectively contain all the packets of the original stream, the concentrator produces a copy of the original stream.
- a buffering technique that may be implemented at a concentrator uses a buffering technique.
- a buffer of a given size is kept for each input stream to create an n-dimensional array, where n is the number of input streams.
- the concentrator transmits a smallest index packet (namely, a packet that is earliest in the stream sequence) contained in any of the stream buffers.
- the data in the array is updated so that future copies of the same packet can be discarded.
- This protocol enables the concentrator to reorder the packets in a stream so that they are output in a correct order.
- One or more concentrators as described above enable fault tolerant media streaming over a computer network such as the Internet, an intranet, a virtual private network, or the like.
- FIG. 1 is a simplified diagram of a known streaming architecture in which a plurality of splitters is used to transmit the source signal to a plurality of end users or viewers;
- FIG. 2 is a simplified diagram illustrative the inventive use of concentrators according to the teachings of the present invention
- FIG. 3 is a flowchart of a first type of processing routine that may be used in a concentrator
- FIG. 4 is a flowchart of a second type of processing routine that may be used in a concentrator
- FIG. 5 is a block diagram of a concentrator used in the present invention.
- FIG. 6 is a block diagram of a client-server computing environment in which the present invention may be implemented.
- FIG. 7 is a block diagram illustrating an implementation of the present invention.
- Streaming media is a type of Internet content that has the important characteristic of being able to play back while still in the process of being downloaded.
- a client can play the first packet of the stream, decompress the second, while receiving the third.
- the user can start enjoying the multimedia without waiting to the end of transmission.
- Streaming is very useful for delivering media because media files tend to be large, particularly as the duration of the programming increases.
- users To view a media file that is not streamed, users must first download the file to a local hard disk—which may take minutes or even hours—and then open the file with player software that is compatible with the file format.
- the user's browser opens player software, which buffers the file for a few seconds and then plays the file while simultaneously downloading it.
- streaming media files are not stored locally on users' hard disks. Once the bits representing content are used, the player discards them.
- Streaming media quality varies widely according to the type of media being delivered, the speed of the user's Internet connection, network conditions, the bit rate at which the content is encoded, and the format used. These last two concepts are explained in more detail below.
- streaming audio can be FM quality, but streaming video is poor by TV standards, with smaller screens, lower resolution, and fewer frames per second.
- the source for streaming media can be just about any form of media, including VHS or Beta tapes, audio cassettes, DAT, MPEG video, MP3 audio, AVI, and the like.
- the content Prior to streaming the content, the content must first be encoded, a process which accomplishes four things: conversion of the content from analog to digital form, if necessary; creation of a file in the format recognized by the streaming media server and player; compression of the file to maximize the richness of the content that can be delivered in real-time given limited bandwidth; and, establishing the bit rate at which the media is to be delivered.
- Streaming media uses lossy compression, which means that after decompression on the client end, some portions of the content are not retained. For example, compression may reduce a VHS video clip with 30 frames per second to just 15 fps.
- media must be encoded at a specific bit rate, such as 28 kbps, 56 kbps, 100 kbps, or the like.
- Content owners typically choose to encode media at multiple rates, so that users with fast connections get as good an experience as possible, but users with slow connections can also access the content. Obviously, the lower the encoding rate, the more original content must be discarded when compressing.
- Non-streaming content is standards-based in the sense that the server and client software developed by different vendors—Apache, Microsoft Internet Explorer, Netscape Communicator, and the like—generally work well together.
- Streaming media usually relies on proprietary server and client software.
- the server, client, production and encoding tools developed by a streaming software vendor are collectively referred to as a format.
- Streaming media encoded in a particular format must be served by that format's media server and replayed by that format's client.
- Streaming media clients are often called players, and typically they exist as plug-ins to Web browsers.
- Streaming media clients are also often capable of playing standards-based non-streaming media files, such as WAV or AVI.
- RealNetworks RealSystem G2 handles all media types including audio, video, animation, still images and text, but it does not support HTML.
- RealSystem G2 supports SMIL, an XML-based language that allows the content provider to time and position media within the player window.
- SMIL an XML-based language that allows the content provider to time and position media within the player window.
- RTSP To deliver the media in real time Real uses RTSP.
- WMT does not support SMIL or RTSP but has its own protocol that it calls HTML+Time.
- Apple QuickTime recently has added the capability to serve streaming media.
- QuickTime can support a number of formats including VR, 3D, Flash, and MP3.
- QuickTime Streaming uses RTSP to deliver the movies in realtime, and a dedicated media server is required.
- RTSP the Real Time Streaming Protocol
- RTSP is a client-server multimedia presentation protocol to enable controlled delivery of streamed multimedia data over IP network. It provides “VCR-style” remote control functionality for audio and video streams, like pause, fast forward, reverse, and absolute positioning. Sources of data include both live data feeds and stored clips.
- RTSP is an application-level protocol designed to work with lower-level protocols like RTP (Realtime Transport Protocol) and RSVP (Resource Reservation Protocol) to provide a complete streaming service over the Internet. It provides means for choosing delivery channels (such as UDP, multicast UDP and TCP), and delivery mechanisms based upon RTP.
- RTSP establishes and controls streams of continuous audio and video media between the media servers and the clients.
- each presentation and media stream is identified by an RTSP URL.
- the overall presentation and the properties of the media are defined in a presentation description file, which may include the encoding, language, RTSP URLs, destination address, port, and other parameters.
- the presentation description file can be obtained by the client using HTTP, email or other means.
- RTSP differs from HTTP for several reasons. First, while HTTP is a stateless protocol, an RTSP server has to maintain “session states” in order to correlate RTSP requests with a stream. Second, HTTP is basically an asymmetric protocol where the client issues requests and the server responds, but in RTSP both the media server and the client can issue requests. For example the server can issue a request to set playing back parameters of a stream.
- the transport layer of non-streaming content uses the Transmission Control Protocol, or TCP.
- TCP Transmission Control Protocol
- This is a connection-oriented protocol, which means a connection between server and client is established and maintained until the content has been completely received.
- One reason for the connection is that the client can report if any IP packets are not received, which are then retransmitted by the server.
- the result is that a file successfully transmitted over TCP, a logo for example, is always identical to its source—although the time required for transmission may vary widely depending on infrastructure.
- UDP User Datagram Protocol
- IP packets are sent from the server to the client without establishing a connection.
- This protocol enables streaming media's real-time nature: no need to wait to resend dropped packets. But it also means that the content quality may be degraded markedly between server and client, or that two different users may have a much different experience.
- the present invention is designed to be used with any streaming media source, encoding scheme, media format, and streaming (or other transport) protocol.
- a packet-switched network 200 in which the present invention is implemented comprises a signal source A, a set of splitters B 1 -Bn, and a set of end users D 1 -Dn.
- the network also includes a set of so-called “concentrators” C 1 -Cn that facilitate an inventive signal replication process. This process ensures that each end user will always receive a copy of the source signal irrespective of interruptions in the transmission, e.g., due to equipment, device or communication failures, that occur within other elements of the distribution system.
- concentrators C are positioned within the network in a physical and/or logical layer located between the splitters B and the end users D.
- the physical configuration illustrated in FIG. 2 is merely exemplary.
- An end user is typically a client computer that includes a browser or other graphics viewer having a plug-in or native support for streaming content.
- a concentrator C is a software program, namely, a set of computer instructions that comprise one or more processes, executable within a processor.
- each concentrator C receives as input one or more copies of the source signal data stream.
- each concentrator C receives a copy of the source signal data stream from at least two (2) different splitters B.
- the original signal is sent to several splitters B 1 , . . . , B 5 .
- These splitters make copies of the signal and send them to the concentrators C 1 , . . . , C 20 .
- Splitter B 1 sends a copy of the signal it received from source A to each of the concentrators C 1 , . . . , C 8 .
- Splitter B 2 sends a copy of the signal it received from source A to each of the concentrators C 9 , . . . , C 16 .
- Splitter B 3 sends a copy to concentrators C 17 , . . . , C 20 and C 1 , . . .
- each concentrator C receives a copy of the source signal data stream from precisely two splitters. Stated another way, each concentrator receives two streams, UDP 1 and UDP 2 , representing copies of the original source stream.
- the function of a concentrator it to process the incoming streams and to merge them into a single or composite copy of the source signal data stream that is then output from the concentrator.
- a concentrator removes duplicate packets and preferably outputs a single stream feed. This processing is quite advantageous. In particular, given several copies of a stream, even if they are all lossy, a single pristine stream can be generated from the remnants of the duplicate streams. The technique is very robust and can take a large number of failures before end user experience is impaired.
- FIG. 3 is a flowchart illustrating a first embodiment of the processing routine wherein the concentrator transmits only the first copy of each packet in the stream. Copies of packets that have already been transmitted are simply discarded.
- FIG. 4 illustrates a second embodiment of the processing routine wherein multiple copies of the streams are buffered to enable out-of-order packets to be reordered as the output is generated.
- a first embodiment of the processing routine utilizes an array f(i) for the source signal.
- An element in the data array has a given first value, e.g., 1, if packet i in the stream has been forwarded from the concentrator and a second value, e.g., 0, otherwise.
- the routine begins at step 300 .
- an instance of the processing routine is spawned, typically when the first packet of the stream arrives at the concentrator.
- the array is initialized.
- the processing routine then continues at step 306 to test whether a packet i has been received from one of the incoming streams. If not, the routine cycles.
- the processing routine parses packets as they arrive at the concentrator. If the parser has already seen the stream packet, the packet is discarded; otherwise, it is forwarded.
- the processing routine of FIG. 3 is advantageous in that it is simple to implement and does not introduce any delay into the streams (which, for example, might be caused by waiting for a particular copy of a packet to arrive).
- This routine also has the desirable feature that a complete stream can be reconstructed from two or more partial streams. Thus, as long as the incoming copies of the stream collectively contain all the packets in the original stream, then the concentrator will produce a copy of the original stream.
- each of the splitters e.g., B 1
- each of concentrators C 1 , . . . C 4 will still receive the stream from splitter B 3 and each of concentrators C 5 , . . . , C 8 will still receive the stream from splitter B 4 .
- each incoming stream at a concentrator has a buffer associated therewith.
- the concentrator may reorder the packets in the stream before output.
- the routine begins at step 400 .
- the buffers are initialized.
- the routine then continues at step 404 to test whether a given cycle has elapsed. If not, the routine continues at step 406 (for each stream) to test whether a given incoming packet (for the stream) has already been forwarded. If the outcome of the test at step 406 is positive, the routine discards the packet at step 408 . If the given incoming packet has not been forwarded, the packet is buffered at step 410 . Control then returns to step 404 .
- packets from stream UDP 1 are buffered in a first buffer
- packets from stream UDP 2 are buffered in a second buffer, and so on.
- a test is performed to determine whether this packet is out of sequence. If so, the routine reorders the packets as necessary at step 416 .
- the resulting stream is then output from the concentrator at step 418 .
- the array is updated to reflect the packets that have been forwarded. Step 418 is also reached if there is a negative outcome of the test at step 414 .
- a buffer of a given size is kept for each input stream copy.
- the concentrator transmits the smallest index packet contained in any of the buffers.
- the data in the array is updated so that future copies of the same packet can be discarded when they arrive at the concentrator.
- the protocol of FIG. 4 is similar to the routine of FIG. 3 except that it has the additional desired feature that it can reorder the packets in the stream so that they are output in the correct order.
- the larger the buffer size the more likely it is that out-of-order packets can be output in order. In this way, packets that are slowed down in the network have the opportunity to catch up at the buffer.
- the output of a given concentrator can then be fed back to a splitter or to an end user directly.
- the process can be repeated to make an arbitrarily large number of copies of the source signal data stream.
- the output of a splitter or concentrator (or some other device) is fed directly to a viewer.
- the resulting replication process is completely fault-tolerant. In particular, no matter what signal is destroyed, the end user's signal is not interrupted.
- the number of signals input to each concentrator determines the number of faulty streams that can be tolerated by the distribution system. For example, if every concentrator receives the signal from at least k different splitters, then the system can tolerate faults in any subset of k ⁇ 1 signals without compromising the signal received by any end user. If the faults in signals (or system components) are random, then the system can tolerate F faults before any end user's signal is interrupted, where F is about N ⁇ 1 ⁇ 1/k ⁇ and N is the number of components in the system. If the packet loss rate being experienced on each stream is p, then the loss rate, after concentration, is pk ⁇ the number of streams.
- a variant of the present invention is to incorporate given coding schemes within the splitters/concentrators to recover some of the bandwidth used to transmit multiple data streams.
- a stream is output from a given device (e.g., a splitter)
- it is encoded using an encoding routine.
- the stream enters the concentrator in the underlying layer, it is decoded and processed in the manner described above.
- coding techniques are used, then the copies of the data stream output from the splitters need not be identical; rather, the copies may vary as a result of the encoding algorithm used within a given device.
- a useful encoding scheme is the Rabin Information Dispersal Algorithm.
- Information dispersal involves the breaking-up of packets into a collection of subpackets that are routed in a greedylike fashion to their common destination along edge-disjoint paths.
- the advantage of information dispersal is that the dispersal of large packets into many small subpackets tends to results in very balanced communication loads on the edges of a network. As a consequence, the maximum congestion in the network is likely to be very low, and there is a good chance that packets will never be delayed at all.
- the Rabin Information Dispersal Algorithm is implemented within a given splitter and a given concentrator.
- FIG. 5 illustrates a representative concentrator 500 comprising a manager routine 502 , an array manager process 504 , and a set of stream concentration processes 506 a - n.
- One or more coding/decoding routines 508 may be provided as described in the variant above.
- the manager routine 502 is initialized upon startup of the concentrator. As an input data stream is received, the manager routine 502 launches an instance of the stream concentration process 506 , which manages the merging of the individual data streams into the stream that is then output from the concentrator.
- the array manager process is invoked by the manager routine 502 to establish an array (or other data structure or equivalent work area) for use by a given stream concentration process 506 .
- a given concentrator may be used to concentrate different content streams under the control of the manager routine.
- FIG. 6 illustrates a conventional client-server environment in which the streaming framework may be implemented.
- a plurality of Internet client machines 610 are connectable to a computer network service provider 612 via a network such as a telephone network 614 .
- the service provider 612 interfaces the client machines 610 to the remainder of the network 618 , which may include a plurality of web content server machines 620 .
- Network 618 typically includes other servers (not shown) for control of domain name resolution, routing and other control functions.
- a client machine typically includes a suite of known Internet tools. Various known Internet protocols are used for these services.
- a given client machine and the server may communicate over the public Internet, an intranet, or any other computer network. If desired, given communications may take place over a secure connection.
- a client may communication with the server using a network security protocol, such as Netscape's Secure Socket Layer (SSL) protocol or the like.
- SSL Netscape's Secure Socket Layer
- a representative client is a personal computer, notebook computer, Internet appliance or pervasive computing device (e.g., a PDA or palm computer) that is x86-, Pentium-, PowerPC®- or RISC-based.
- the client includes an operating system such as Microsoft Windows '98, Microsoft NT, Windows CE or PalmOS.
- the client includes a suite of Internet tools including a Web browser, such as Netscape Navigator or Microsoft Internet Explorer, that has a Java Virtual Machine (JVM) and support for application plug-ins or helper applications.
- JVM Java Virtual Machine
- a representative web server comprises a processor 622 , an operating system 624 (e.g., Linux, Windows NT, Unix, or the like) and a web server program 626 .
- OS 624 and web server program 626 are supported in system memory 623 (e.g., RAM).
- system memory 623 e.g., RAM
- any convenient server platform e.g., Apache, WebSphere, or the like
- the server may include an application programming interface 628 (API) that provides extensions to enable application developers to extend and/or customize the core functionality thereof through software programs including plug-ins, CGI programs, servlets, and the like.
- API application programming interface
- a representative concentrator is a computer or computer platform having an operating system and support for network connectivity.
- a representative concentrator comprises a computer running Windows NT (Intel and DEC Alpha), IBM AIX, HP-UX, Sun Solaris (SPARC and Intel Edition), Novell NetWare or Windows '98.
- FIG. 7 illustrates an implementation of the present invention.
- the system 700 comprises a pair of relay servers 702 and 704 residing, for example, at a streaming video production facility 706 .
- These servers are equipped, for example, with two (2) network cards each, one set of which are wired onto a common network with encoder machines 708 , and the other set of which is connected to the Internet 710 .
- the encoder machines 708 encode the video and audio data and send the encoded packets to a broadcast address of the network they share with the relay servers 702 and 704 .
- the relay servers pick up the packets and re-send them out, for example, over two dedicated T-1 lines to two different data centers 712 and 714 .
- each of the four data centers sends a copy of each packet to each of a set of regions 724 a - n, with each server region 724 comprising a set of content hosting servers 726 a - n.
- Each region includes a concentrator 728 , which removes the duplicates and feeds the single remaining stream to each server 726 in that region.
- the server regions may comprise part of a distributed content hosting system such as Akamai FreeFlowTM, which is a high-performance, fault-tolerant web content delivery service.
- the invention may be implemented in software executable in a processor, namely, as a set of instructions (program code) in a code module resident in the random access memory of the computer.
- the set of instructions may be stored in another computer memory, for example, in a hard disk drive, or in a removable memory, or downloaded via the Internet or other computer network.
Abstract
A replication process provides fault tolerance for a continuous media stream in a computer network. In one embodiment, the original or source signal is sent to several splitters which, in turn, each make copies of the signal and send the copies into a second layer of devices, which are referred to as “concentrators.” A given concentrator receives as input one or more copies of the source signal. In a preferred embodiment, a given concentrator receives two copies of the source signal from at least two different splitters. The concentrators process the incoming streaming signal copies, for example, by merging them into a single or composite copy of the original source signal according to a given processing algorithm. The output of a given concentrator may then be fed into a splitter, with the process then being repeated if desired to make an arbitrary large number of copies of the signal. At the end of the replication process, the output of a splitter or a concentrator is fed directly or indirectly to an end user. The replication process is fault-tolerant, and thus the end user's signal is not interrupted regardless of signal or equipment problems within the distribution mechanism.
Description
- This application is a continuation of prior application Ser. No. 10.457,266, filed Jun. 9, 2003, which application was a continuation of Ser. No. 09/478,571, filed Jan. 6, 2000.
- 1. Technical Field
- The present invention relates generally to digital signal transmission over a computer network and, in particular, to a method and system for streaming content over the Internet in a fault tolerant manner.
- 2. Description of the Related Art
- Most Internet users do not have fast enough access to the Internet to download large multimedia files quickly. Streaming is a technique for delivering web-based video, audio and multimedia files so that these files can be processed as a steady and continuous stream at the requesting client, typically using a browser plug-in, such as Microsoft NetPlayer, Apple QuickTime, Real Networks RealSystem G2, or the like. Streaming video, for example, is an online video distribution mechanism that provides audio and video to Internet users, without the users having to wait while content completely downloads to their hard drives. Through caching, content is played as it is received, and buffering mechanisms ensure that content is played smoothly. Theoretically, streaming video plays to the end user, or viewer, as an immediate and ongoing broadcast.
- From a network perspective, traditional approaches to streaming Internet content involve transmitting a streaming signal from a source to a device known as a splitter (or repeater, reflector or mirror), which, in turn, replicates the source signal into multiple signals. Each of the multiple signals is the same, and each is sent on to a different destination. By cascading splitters in a tree-like fashion, a single source stream can be replicated into thousands or more identical copies. In this manner, a large number of viewers on the Internet can receive the same streaming signal simultaneously.
- A critical problem with existing streaming methods of this type is that they are not fault tolerant.
FIG. 1 illustrates why this is the case. In this example, a source signal (A) is sent to a splitter (B), which then sends copies of the signal to ten splitters (C1, . . . , C10). Each of the second level splitters then sends a copy of the signal to five end customers (D1, . . . , D50). Thus, for example, splitter C1 sends a copy to end users D1-D5, splitter C2 sends a copy to end users D6-D10, and so forth. If communications at a given splitter fail, however, certain users are unable to receive the original signal. In the network ofFIG. 1 , this would be the case with respect to users D6-D10 if C2 fails. To overcome this problem, it is also known in the art to enable end users to detect they are no longer receiving the streaming signal and to enable such users to attempt to contact an alternative splitter (e.g., C3) in an effort to get another copy of the signal. Such approaches, however, can result in an interruption of the signal and are expensive to implement. - Thus, there remains a need in the art to provide improved streaming techniques that are fault tolerant. The present invention solves this important problem.
- The present invention provides a replication process to provide fault tolerance for a streaming signal in a computer network. In one embodiment, the original or source signal is sent to several splitters which, in turn, each make copies of the signal and send the copies into a second layer of devices, which are referred to as “concentrators.” A given concentrator receives as input one or more copies of the source signal. In a preferred embodiment, a given concentrator receives two copies of the source signal from at least two different splitters. The concentrators process the incoming streaming signal copies, for example, by merging them into a single or composite copy of the original source signal according to a given processing algorithm. Thus, preferably a given concentrator receives streams from multiple sources, removes duplicate packets, and then outputs a single stream. The output of a given concentrator may then be fed into a splitter, with the process then being repeated if desired to make an arbitrary large number of copies of the signal. At the end of the replication process, the output of a splitter or a concentrator is fed directly or indirectly to an end user. The replication process is fault-tolerant, and thus the end user's signal is not interrupted regardless of signal or equipment problems within the distribution mechanism.
- One type of processing algorithm that is implemented at a concentrator simply transmits the first copy of each packet in the signal stream. Copies of packets that have already been transmitted are simply discarded. This algorithm may be implemented by maintaining a data array f(i) that has a first value (e.g., “1”) if packet i in the stream has been forwarded and f(i) that has a second value (e.g., “0”) otherwise. When a copy of packet i is received from one of the incoming streams, it is forwarded if and only if f(i) equals the second value. This technique is advantageous because a complete stream can be reconstructed from two or more partial streams. Thus, as long as the incoming copies of the stream collectively contain all the packets of the original stream, the concentrator produces a copy of the original stream.
- Another type of processing algorithm that may be implemented at a concentrator uses a buffering technique. In this approach, a buffer of a given size is kept for each input stream to create an n-dimensional array, where n is the number of input streams. At a given cycle rate, the concentrator transmits a smallest index packet (namely, a packet that is earliest in the stream sequence) contained in any of the stream buffers. As each packet is transmitted, the data in the array is updated so that future copies of the same packet can be discarded. This protocol enables the concentrator to reorder the packets in a stream so that they are output in a correct order.
- One or more concentrators as described above enable fault tolerant media streaming over a computer network such as the Internet, an intranet, a virtual private network, or the like.
- The foregoing has outlined some of the more pertinent objects and features of the present invention. These objects should be construed to be merely illustrative of some of the more prominent features and applications of the invention. Many other beneficial results can be obtained by applying the disclosed invention in a different manner or modifying the invention as will be described. Accordingly, other objects and a fuller understanding of the invention may be had by referring to the following Detailed Description of the Preferred Embodiment.
- For a more complete understanding of the present invention and the advantages thereof, reference should be made to the following Detailed Description taken in connection with the accompanying drawings in which:
-
FIG. 1 is a simplified diagram of a known streaming architecture in which a plurality of splitters is used to transmit the source signal to a plurality of end users or viewers; -
FIG. 2 is a simplified diagram illustrative the inventive use of concentrators according to the teachings of the present invention; -
FIG. 3 is a flowchart of a first type of processing routine that may be used in a concentrator; -
FIG. 4 is a flowchart of a second type of processing routine that may be used in a concentrator; -
FIG. 5 is a block diagram of a concentrator used in the present invention; -
FIG. 6 is a block diagram of a client-server computing environment in which the present invention may be implemented; and -
FIG. 7 is a block diagram illustrating an implementation of the present invention. - Streaming media is a type of Internet content that has the important characteristic of being able to play back while still in the process of being downloaded. A client can play the first packet of the stream, decompress the second, while receiving the third. Thus, the user can start enjoying the multimedia without waiting to the end of transmission. Streaming is very useful for delivering media because media files tend to be large, particularly as the duration of the programming increases. To view a media file that is not streamed, users must first download the file to a local hard disk—which may take minutes or even hours—and then open the file with player software that is compatible with the file format. To view streaming media, the user's browser opens player software, which buffers the file for a few seconds and then plays the file while simultaneously downloading it. Unlike software downloads, streaming media files are not stored locally on users' hard disks. Once the bits representing content are used, the player discards them.
- Streaming media quality varies widely according to the type of media being delivered, the speed of the user's Internet connection, network conditions, the bit rate at which the content is encoded, and the format used. These last two concepts are explained in more detail below. In general, streaming audio can be FM quality, but streaming video is poor by TV standards, with smaller screens, lower resolution, and fewer frames per second. The source for streaming media can be just about any form of media, including VHS or Beta tapes, audio cassettes, DAT, MPEG video, MP3 audio, AVI, and the like. Prior to streaming the content, the content must first be encoded, a process which accomplishes four things: conversion of the content from analog to digital form, if necessary; creation of a file in the format recognized by the streaming media server and player; compression of the file to maximize the richness of the content that can be delivered in real-time given limited bandwidth; and, establishing the bit rate at which the media is to be delivered. Streaming media uses lossy compression, which means that after decompression on the client end, some portions of the content are not retained. For example, compression may reduce a VHS video clip with 30 frames per second to just 15 fps. Typically, media must be encoded at a specific bit rate, such as 28 kbps, 56 kbps, 100 kbps, or the like. Content owners typically choose to encode media at multiple rates, so that users with fast connections get as good an experience as possible, but users with slow connections can also access the content. Obviously, the lower the encoding rate, the more original content must be discarded when compressing.
- Non-streaming content is standards-based in the sense that the server and client software developed by different vendors—Apache, Microsoft Internet Explorer, Netscape Communicator, and the like—generally work well together. Streaming media, however, usually relies on proprietary server and client software. The server, client, production and encoding tools developed by a streaming software vendor are collectively referred to as a format. Streaming media encoded in a particular format must be served by that format's media server and replayed by that format's client. Streaming media clients are often called players, and typically they exist as plug-ins to Web browsers. Streaming media clients are also often capable of playing standards-based non-streaming media files, such as WAV or AVI.
- The three major streaming media formats in use today are: RealNetworks RealSystem G2, Microsoft Windows Media Technologies (“WMT”), and Apple QuickTime. RealSystem G2 handles all media types including audio, video, animation, still images and text, but it does not support HTML. RealSystem G2 supports SMIL, an XML-based language that allows the content provider to time and position media within the player window. To deliver the media in real time Real uses RTSP. To stream in WMT's Advanced Streaming Format, content providers must have Microsoft NT 4 Server installed. WMT does not support SMIL or RTSP but has its own protocol that it calls HTML+Time. Apple QuickTime recently has added the capability to serve streaming media. QuickTime can support a number of formats including VR, 3D, Flash, and MP3. QuickTime Streaming uses RTSP to deliver the movies in realtime, and a dedicated media server is required.
- By way of further background, RTSP, the Real Time Streaming Protocol, is a client-server multimedia presentation protocol to enable controlled delivery of streamed multimedia data over IP network. It provides “VCR-style” remote control functionality for audio and video streams, like pause, fast forward, reverse, and absolute positioning. Sources of data include both live data feeds and stored clips. RTSP is an application-level protocol designed to work with lower-level protocols like RTP (Realtime Transport Protocol) and RSVP (Resource Reservation Protocol) to provide a complete streaming service over the Internet. It provides means for choosing delivery channels (such as UDP, multicast UDP and TCP), and delivery mechanisms based upon RTP. RTSP establishes and controls streams of continuous audio and video media between the media servers and the clients. In RTSP, each presentation and media stream is identified by an RTSP URL. The overall presentation and the properties of the media are defined in a presentation description file, which may include the encoding, language, RTSP URLs, destination address, port, and other parameters. The presentation description file can be obtained by the client using HTTP, email or other means. RTSP differs from HTTP for several reasons. First, while HTTP is a stateless protocol, an RTSP server has to maintain “session states” in order to correlate RTSP requests with a stream. Second, HTTP is basically an asymmetric protocol where the client issues requests and the server responds, but in RTSP both the media server and the client can issue requests. For example the server can issue a request to set playing back parameters of a stream.
- The transport layer of non-streaming content uses the Transmission Control Protocol, or TCP. This is a connection-oriented protocol, which means a connection between server and client is established and maintained until the content has been completely received. One reason for the connection is that the client can report if any IP packets are not received, which are then retransmitted by the server. The result is that a file successfully transmitted over TCP, a logo for example, is always identical to its source—although the time required for transmission may vary widely depending on infrastructure.
- By contrast, the transport layer for streaming media uses User Datagram Protocol, or UDP. UDP is a connectionless protocol, under which IP packets are sent from the server to the client without establishing a connection. This protocol enables streaming media's real-time nature: no need to wait to resend dropped packets. But it also means that the content quality may be degraded markedly between server and client, or that two different users may have a much different experience.
- The present invention is designed to be used with any streaming media source, encoding scheme, media format, and streaming (or other transport) protocol.
- Referring now to
FIG. 2 , a packet-switchednetwork 200 in which the present invention is implemented comprises a signal source A, a set of splitters B1-Bn, and a set of end users D1-Dn. According to the invention, the network also includes a set of so-called “concentrators” C1-Cn that facilitate an inventive signal replication process. This process ensures that each end user will always receive a copy of the source signal irrespective of interruptions in the transmission, e.g., due to equipment, device or communication failures, that occur within other elements of the distribution system. - Preferably, concentrators C are positioned within the network in a physical and/or logical layer located between the splitters B and the end users D. The physical configuration illustrated in
FIG. 2 , of course, is merely exemplary. An end user, of course, is typically a client computer that includes a browser or other graphics viewer having a plug-in or native support for streaming content. In a preferred embodiment, a concentrator C is a software program, namely, a set of computer instructions that comprise one or more processes, executable within a processor. As illustrated inFIG. 2 , each concentrator C receives as input one or more copies of the source signal data stream. In a preferred embodiment of the invention, each concentrator C receives a copy of the source signal data stream from at least two (2) different splitters B. Thus, for example, in this embodiment, the original signal is sent to several splitters B1, . . . , B5. These splitters make copies of the signal and send them to the concentrators C1, . . . , C20. Splitter B1 sends a copy of the signal it received from source A to each of the concentrators C1, . . . , C8. Splitter B2 sends a copy of the signal it received from source A to each of the concentrators C9, . . . , C16. Splitter B3 sends a copy to concentrators C17, . . . , C20 and C1, . . . , C4, whereas B4 sends copies to C5, . . . , C12, and B5 sends copies to C13, . . . , C20. Again, these examples are not to be taken to limit the present invention in any way. In each case, however, it can be seen that every concentrator C receives a copy of the source signal data stream from precisely two splitters. Stated another way, each concentrator receives two streams, UDP1 and UDP2, representing copies of the original source stream. - Generally, the function of a concentrator it to process the incoming streams and to merge them into a single or composite copy of the source signal data stream that is then output from the concentrator. A concentrator removes duplicate packets and preferably outputs a single stream feed. This processing is quite advantageous. In particular, given several copies of a stream, even if they are all lossy, a single pristine stream can be generated from the remnants of the duplicate streams. The technique is very robust and can take a large number of failures before end user experience is impaired.
- The processing of the data streams may be accomplished in a number of different ways.
FIG. 3 , for example, is a flowchart illustrating a first embodiment of the processing routine wherein the concentrator transmits only the first copy of each packet in the stream. Copies of packets that have already been transmitted are simply discarded.FIG. 4 illustrates a second embodiment of the processing routine wherein multiple copies of the streams are buffered to enable out-of-order packets to be reordered as the output is generated. Each of the embodiments will now be described in detail. - Referring now to
FIG. 3 , a first embodiment of the processing routine utilizes an array f(i) for the source signal. An element in the data array has a given first value, e.g., 1, if packet i in the stream has been forwarded from the concentrator and a second value, e.g., 0, otherwise. The routine begins atstep 300. Atstep 302, an instance of the processing routine is spawned, typically when the first packet of the stream arrives at the concentrator. Atstep 304, the array is initialized. The processing routine then continues atstep 306 to test whether a packet i has been received from one of the incoming streams. If not, the routine cycles. If, however, the outcome of the test atstep 306 is positive, which indicates that the packet has been received, a test is performed atstep 308 to determine whether f(i)=0. If so (because this is the first occurrence of the packet i), the routine continues atstep 310 to forward the packet from the concentrator without delay. Atstep 312, the routine updates the array by setting the value of the packet i in the array equal to 0. Control then returns to step 306. If, however, the outcome of the test atstep 308 indicates that f(i) is not equal to 0, then the routine continues atstep 314 to discard the packet (since it has already been forwarded). - Thus, in effect, the processing routine parses packets as they arrive at the concentrator. If the parser has already seen the stream packet, the packet is discarded; otherwise, it is forwarded.
- The processing routine of
FIG. 3 is advantageous in that it is simple to implement and does not introduce any delay into the streams (which, for example, might be caused by waiting for a particular copy of a packet to arrive). This routine also has the desirable feature that a complete stream can be reconstructed from two or more partial streams. Thus, as long as the incoming copies of the stream collectively contain all the packets in the original stream, then the concentrator will produce a copy of the original stream. - As an example, and with reference to
FIG. 2 again, if one of the splitters (e.g., B1) ceases to function, then each of concentrators C1, . . . C4 will still receive the stream from splitter B3 and each of concentrators C5, . . . , C8 will still receive the stream from splitter B4. There is never an interruption of the signal transmitted by any of the concentrators in this illustrative example. This property is preserved irrespective of which splitter is not functioning. Indeed, even if two splitters (e.g., B1 and B3) suffer packet loss, it is still possible for each of the concentrators C1, . . . C4 to reconstruct the original signal using the process described above (provided that the packet loss is less than 50%). - Referring now to
FIG. 4 , an alternate embodiment is shown wherein each incoming stream at a concentrator has a buffer associated therewith. By buffering stream packets, the concentrator may reorder the packets in the stream before output. The routine begins atstep 400. Atstep 402, the buffers are initialized. The routine then continues atstep 404 to test whether a given cycle has elapsed. If not, the routine continues at step 406 (for each stream) to test whether a given incoming packet (for the stream) has already been forwarded. If the outcome of the test atstep 406 is positive, the routine discards the packet atstep 408. If the given incoming packet has not been forwarded, the packet is buffered atstep 410. Control then returns to step 404. Using the buffering scheme, for example, packets from stream UDP1 are buffered in a first buffer, packets from stream UDP2 are buffered in a second buffer, and so on. When the outcome of the test atstep 404 indicates that the given cycle has elapsed, control branches to step 412 to identify the packet that is the earliest in the stream sequence. Atstep 414, a test is performed to determine whether this packet is out of sequence. If so, the routine reorders the packets as necessary atstep 416. The resulting stream is then output from the concentrator atstep 418. Atstep 420, the array is updated to reflect the packets that have been forwarded. Step 418 is also reached if there is a negative outcome of the test atstep 414. - Thus, in the routine of
FIG. 4 , a buffer of a given size is kept for each input stream copy. At each cycle, the concentrator transmits the smallest index packet contained in any of the buffers. As each packet is transmitted, the data in the array is updated so that future copies of the same packet can be discarded when they arrive at the concentrator. As can be seen, the protocol ofFIG. 4 is similar to the routine ofFIG. 3 except that it has the additional desired feature that it can reorder the packets in the stream so that they are output in the correct order. The larger the buffer size, the more likely it is that out-of-order packets can be output in order. In this way, packets that are slowed down in the network have the opportunity to catch up at the buffer. - Regardless of which technique (
FIG. 3 orFIG. 4 ) is used at a given concentrator C, the output of a given concentrator can then be fed back to a splitter or to an end user directly. When the concentrator is output to a splitter, the process can be repeated to make an arbitrarily large number of copies of the source signal data stream. At the end of the replication process, the output of a splitter or concentrator (or some other device) is fed directly to a viewer. The resulting replication process is completely fault-tolerant. In particular, no matter what signal is destroyed, the end user's signal is not interrupted. - The number of signals input to each concentrator determines the number of faulty streams that can be tolerated by the distribution system. For example, if every concentrator receives the signal from at least k different splitters, then the system can tolerate faults in any subset of k−1 signals without compromising the signal received by any end user. If the faults in signals (or system components) are random, then the system can tolerate F faults before any end user's signal is interrupted, where F is about N{1−1/k} and N is the number of components in the system. If the packet loss rate being experienced on each stream is p, then the loss rate, after concentration, is pk×the number of streams.
- In a preferred embodiment, it is desirable to input two (2) input streams to a given concentrator. The cost of more streams, of course, is more network bandwidth for the distribution mechanism. Where multiple input streams are supplied to a concentrator (or output from a splitter), a variant of the present invention is to incorporate given coding schemes within the splitters/concentrators to recover some of the bandwidth used to transmit multiple data streams. In this variant, as a stream is output from a given device (e.g., a splitter), it is encoded using an encoding routine. As the stream enters the concentrator in the underlying layer, it is decoded and processed in the manner described above. When coding techniques are used, then the copies of the data stream output from the splitters need not be identical; rather, the copies may vary as a result of the encoding algorithm used within a given device.
- In an illustrative embodiment, a useful encoding scheme is the Rabin Information Dispersal Algorithm. Information dispersal involves the breaking-up of packets into a collection of subpackets that are routed in a greedylike fashion to their common destination along edge-disjoint paths. The advantage of information dispersal is that the dispersal of large packets into many small subpackets tends to results in very balanced communication loads on the edges of a network. As a consequence, the maximum congestion in the network is likely to be very low, and there is a good chance that packets will never be delayed at all. In addition, if the contents of a packet are encoded into a collection of subpackets in a redundant fashion, an information dispersal algorithm becomes more fault tolerant as only a fraction of the subpackets have to reach the destination for the original packet to be reconstructed. Further information about the Information Dispersal Algorithm may be found in the following reference, Leighton, Introduction To Parallel Algorithms and Architectures: Arrays, Trees, Hybercubes, Morgan Kaufmann (1992), Section 3.4.8, which is incorporated herein by reference. Thus, in an illustrative embodiment, the Rabin Information Dispersal Algorithm is implemented within a given splitter and a given concentrator.
- As noted above, a concentrator for use in the present invention is a software program executable on a computer.
FIG. 5 illustrates arepresentative concentrator 500 comprising amanager routine 502, anarray manager process 504, and a set of stream concentration processes 506 a-n. One or more coding/decoding routines 508 may be provided as described in the variant above. In operation, themanager routine 502 is initialized upon startup of the concentrator. As an input data stream is received, themanager routine 502 launches an instance of the stream concentration process 506, which manages the merging of the individual data streams into the stream that is then output from the concentrator. The array manager process is invoked by themanager routine 502 to establish an array (or other data structure or equivalent work area) for use by a given stream concentration process 506. By using multiple stream concentration processes, a given concentrator may be used to concentrate different content streams under the control of the manager routine. - The fault-tolerant distribution mechanism of the present invention may be implemented within a conventional client-server distributed computing environment.
FIG. 6 illustrates a conventional client-server environment in which the streaming framework may be implemented. In this example, a plurality ofInternet client machines 610 are connectable to a computernetwork service provider 612 via a network such as atelephone network 614. Theservice provider 612 interfaces theclient machines 610 to the remainder of thenetwork 618, which may include a plurality of webcontent server machines 620.Network 618 typically includes other servers (not shown) for control of domain name resolution, routing and other control functions. A client machine typically includes a suite of known Internet tools. Various known Internet protocols are used for these services. - A given client machine and the server may communicate over the public Internet, an intranet, or any other computer network. If desired, given communications may take place over a secure connection. Thus, for example, a client may communication with the server using a network security protocol, such as Netscape's Secure Socket Layer (SSL) protocol or the like.
- A representative client is a personal computer, notebook computer, Internet appliance or pervasive computing device (e.g., a PDA or palm computer) that is x86-, Pentium-, PowerPC®- or RISC-based. The client includes an operating system such as Microsoft Windows '98, Microsoft NT, Windows CE or PalmOS. The client includes a suite of Internet tools including a Web browser, such as Netscape Navigator or Microsoft Internet Explorer, that has a Java Virtual Machine (JVM) and support for application plug-ins or helper applications.
- A representative web server comprises a
processor 622, an operating system 624 (e.g., Linux, Windows NT, Unix, or the like) and aweb server program 626.OS 624 andweb server program 626 are supported in system memory 623 (e.g., RAM). Of course, any convenient server platform (e.g., Apache, WebSphere, or the like) may be supported. The server may include an application programming interface 628 (API) that provides extensions to enable application developers to extend and/or customize the core functionality thereof through software programs including plug-ins, CGI programs, servlets, and the like. - A representative concentrator is a computer or computer platform having an operating system and support for network connectivity. Thus, for example, a representative concentrator comprises a computer running Windows NT (Intel and DEC Alpha), IBM AIX, HP-UX, Sun Solaris (SPARC and Intel Edition), Novell NetWare or Windows '98.
-
FIG. 7 illustrates an implementation of the present invention. The system 700 comprises a pair ofrelay servers video production facility 706. These servers are equipped, for example, with two (2) network cards each, one set of which are wired onto a common network with encoder machines 708, and the other set of which is connected to theInternet 710. The encoder machines 708 encode the video and audio data and send the encoded packets to a broadcast address of the network they share with therelay servers different data centers concentrator 728, which removes the duplicates and feeds the single remaining stream to each server 726 in that region. Although not meant to be limiting, the server regions may comprise part of a distributed content hosting system such as Akamai FreeFlow™, which is a high-performance, fault-tolerant web content delivery service. - As noted above, the invention may be implemented in software executable in a processor, namely, as a set of instructions (program code) in a code module resident in the random access memory of the computer. Until required by the computer, the set of instructions may be stored in another computer memory, for example, in a hard disk drive, or in a removable memory, or downloaded via the Internet or other computer network.
- In addition, although the various methods described are conveniently implemented in a general purpose computer selectively activated or reconfigured by software, one of ordinary skill in the art would also recognize that such methods may be carried out in hardware, in firmware, or in more specialized apparatus constructed to perform the required method steps.
Claims (6)
1. A method of fault tolerant delivery of live media content, the content being available in a given media format as a stream of data packets, comprising:
receiving the stream at each of one or more data centers;
from at least one data center, outputting a copy of each packet in the stream to a set of remote server regions, wherein a remove server region comprises a set of one or more media servers associated with the given media format;
at a remote server region, feeding the stream to each of the set of one or more media servers associated with the given media format so that each of the set of one or more media servers in the remote server region is available to provide the stream of data packets;
within the remote server region, at each of the one or more media servers in the set of media servers, receiving the stream of data packets; and
in response to each end user request that is directed, via a content delivery network (CDN) domain name server, to one of the set of media servers in the remote server region that has received the stream of data packets, outputting the stream of data packets from a given media server in the remote server region.
2. The method as described in claim 1 wherein data packets are delivered to each server region via a non-streaming media protocol and the stream of data packets is output from the given media server over a streaming protocol.
3. The method as described in claim 2 wherein the streaming protocol is RTSP.
4. The method as described in claim 2 wherein the non-streaming media protocol is UDP.
5. The method as described in claim 1 further including the step of receiving, at a remote server region, two or more copies of the stream of data packets, with each copy being received from one of the set of multiple delivery sources.
6. The method as described in claim 1 wherein the stream is received from an encoder.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/928,042 US20080052404A1 (en) | 2000-01-06 | 2007-10-30 | Method and system for fault tolerant media streaming over the Internet |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/478,571 US6665726B1 (en) | 2000-01-06 | 2000-01-06 | Method and system for fault tolerant media streaming over the internet |
US10/457,266 US7296082B2 (en) | 2000-01-06 | 2003-06-09 | Method and system for fault tolerant media streaming over the internet |
US11/928,042 US20080052404A1 (en) | 2000-01-06 | 2007-10-30 | Method and system for fault tolerant media streaming over the Internet |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/457,266 Continuation US7296082B2 (en) | 2000-01-06 | 2003-06-09 | Method and system for fault tolerant media streaming over the internet |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080052404A1 true US20080052404A1 (en) | 2008-02-28 |
Family
ID=23900461
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/478,571 Expired - Lifetime US6665726B1 (en) | 2000-01-06 | 2000-01-06 | Method and system for fault tolerant media streaming over the internet |
US10/457,266 Expired - Lifetime US7296082B2 (en) | 2000-01-06 | 2003-06-09 | Method and system for fault tolerant media streaming over the internet |
US11/928,042 Abandoned US20080052404A1 (en) | 2000-01-06 | 2007-10-30 | Method and system for fault tolerant media streaming over the Internet |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/478,571 Expired - Lifetime US6665726B1 (en) | 2000-01-06 | 2000-01-06 | Method and system for fault tolerant media streaming over the internet |
US10/457,266 Expired - Lifetime US7296082B2 (en) | 2000-01-06 | 2003-06-09 | Method and system for fault tolerant media streaming over the internet |
Country Status (8)
Country | Link |
---|---|
US (3) | US6665726B1 (en) |
EP (1) | EP1247383B1 (en) |
JP (1) | JP4723151B2 (en) |
AT (1) | ATE506795T1 (en) |
AU (1) | AU774277B2 (en) |
CA (1) | CA2396261C (en) |
DE (1) | DE60144466D1 (en) |
WO (1) | WO2001050710A1 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060184670A1 (en) * | 2003-08-29 | 2006-08-17 | Beeson Jesse D | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US20060271293A1 (en) * | 2000-07-13 | 2006-11-30 | Global Locate, Inc. | Method And Apparatus For Locating Mobile Receivers Using A Wide Area Reference Network For Propagating Ephemeris |
US20060274727A1 (en) * | 2005-06-06 | 2006-12-07 | Microsoft Corporation | Transport-neutral in-order delivery in a distributed system |
US20080063003A1 (en) * | 2001-09-13 | 2008-03-13 | Network Foundation Technologies | System and method for broadcasting content to nodes on computer networks |
US20090097413A1 (en) * | 2003-08-29 | 2009-04-16 | Todd Marc A C | System and Method for Analyzing the Performance of Multiple Transportation Streams of Streaming Media in Packet-Based Networks |
US20100220622A1 (en) * | 2009-02-27 | 2010-09-02 | Yottaa Inc | Adaptive network with automatic scaling |
US20100223364A1 (en) * | 2009-02-27 | 2010-09-02 | Yottaa Inc | System and method for network traffic management and load balancing |
US20100228819A1 (en) * | 2009-03-05 | 2010-09-09 | Yottaa Inc | System and method for performance acceleration, data protection, disaster recovery and on-demand scaling of computer applications |
US20100251329A1 (en) * | 2009-03-31 | 2010-09-30 | Yottaa, Inc | System and method for access management and security protection for network accessible computer services |
US20110215893A1 (en) * | 2010-03-04 | 2011-09-08 | Michael Nussbaum | Planar audio amplifier output inductor with current sense |
US20110225454A1 (en) * | 2008-11-21 | 2011-09-15 | Huawei Device Co., Ltd | Method, recording terminal, server, and system for repairing media file recording errors |
US20110307584A1 (en) * | 2000-04-17 | 2011-12-15 | Akamai Technologies, Inc. | HTML delivery from edge-of-network servers in a content delivery network (CDN) |
US20120072604A1 (en) * | 2009-05-29 | 2012-03-22 | France Telecom | technique for delivering content to a user |
US8930563B2 (en) * | 2011-10-27 | 2015-01-06 | Microsoft Corporation | Scalable and extendable stream processing |
US10674387B2 (en) | 2003-08-29 | 2020-06-02 | Ineoquest Technologies, Inc. | Video quality monitoring |
Families Citing this family (123)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6275470B1 (en) | 1999-06-18 | 2001-08-14 | Digital Island, Inc. | On-demand overlay routing for computer-based communication networks |
US6868452B1 (en) * | 1999-08-06 | 2005-03-15 | Wisconsin Alumni Research Foundation | Method for caching of media files to reduce delivery cost |
US8543901B1 (en) | 1999-11-01 | 2013-09-24 | Level 3 Communications, Llc | Verification of content stored in a network |
US6339785B1 (en) * | 1999-11-24 | 2002-01-15 | Idan Feigenbaum | Multi-server file download |
US6519773B1 (en) | 2000-02-08 | 2003-02-11 | Sherjil Ahmed | Method and apparatus for a digitized CATV network for bundled services |
US6937814B1 (en) * | 2000-04-14 | 2005-08-30 | Realnetworks, Inc. | System and method for play while recording processing |
US6990616B1 (en) * | 2000-04-24 | 2006-01-24 | Attune Networks Ltd. | Analysis of network performance |
US7299291B1 (en) | 2000-05-18 | 2007-11-20 | Akamai Technologies, Inc. | Client-side method for identifying an optimum server |
US7587497B1 (en) * | 2000-06-20 | 2009-09-08 | Palmsource Inc. | Information exchange between a handheld device and another computer system using an exchange manager and uniform resource locator (URL) strings |
US7020709B1 (en) * | 2000-06-30 | 2006-03-28 | Intel Corporation | System and method for fault tolerant stream splitting |
US7346676B1 (en) * | 2000-07-19 | 2008-03-18 | Akamai Technologies, Inc. | Load balancing service |
US20020040479A1 (en) * | 2000-10-04 | 2002-04-04 | Eric Ehrman | Method and apparatus for streaming content via a network |
US7249185B1 (en) * | 2000-10-30 | 2007-07-24 | Cisco Technology, Inc. | Methods, devices and software for redundant transmission of voice data over a packet network connection established according to an unreliable communication protocol |
FR2817016B1 (en) * | 2000-11-21 | 2003-02-21 | Snecma Moteurs | METHOD FOR ASSEMBLING A FUEL INJECTOR FOR A TURBOMACHINE COMBUSTION CHAMBER |
US8554940B2 (en) | 2001-01-19 | 2013-10-08 | Single Touch Interactive, Inc. | System and method for routing media |
US20040025186A1 (en) * | 2001-01-19 | 2004-02-05 | Jennings Charles A. | System and method for managing media |
US20020147634A1 (en) * | 2001-01-31 | 2002-10-10 | Ronald Jacoby | System for dynamic generation of online streaming media advertisements |
US7154898B1 (en) | 2001-03-13 | 2006-12-26 | Intelsat, Ltd. | Scalable edge node |
US7237017B1 (en) | 2001-03-13 | 2007-06-26 | Panamsat Corporation | Micronode in a satellite based content delivery system |
US7174373B1 (en) | 2001-03-13 | 2007-02-06 | Panamsat Corporation | Self-contained demonstration node in a satellite based content delivery system |
US7130908B1 (en) | 2001-03-13 | 2006-10-31 | Intelsat Ltd. | Forward cache management between edge nodes in a satellite based content delivery system |
US7292571B2 (en) | 2001-04-30 | 2007-11-06 | Aol Llc, A Delaware Limited Liability Company | Load balancing with direct terminal response |
US8572278B2 (en) | 2001-04-30 | 2013-10-29 | Facebook, Inc. | Generating multiple data streams from a single data source |
US7266609B2 (en) * | 2001-04-30 | 2007-09-04 | Aol Llc | Generating multiple data streams from a single data source |
WO2003105006A1 (en) * | 2001-04-30 | 2003-12-18 | America Online, Inc. | Load balancing with direct terminal response |
US7124166B2 (en) | 2001-04-30 | 2006-10-17 | Aol Llc | Duplicating digital streams for digital conferencing using switching technologies |
US7237033B2 (en) * | 2001-04-30 | 2007-06-26 | Aol Llc | Duplicating switch for streaming data units to a terminal |
US6757735B2 (en) * | 2001-07-03 | 2004-06-29 | Hewlett-Packard Development Company, L.P. | Method for distributing multiple description streams on servers in fixed and mobile streaming media systems |
US20060259607A1 (en) * | 2001-09-13 | 2006-11-16 | Network Foundation Technologies, Llc | System and method for distributing data over a computer network |
US7860964B2 (en) | 2001-09-28 | 2010-12-28 | Level 3 Communications, Llc | Policy-based content delivery network selection |
JP4160506B2 (en) | 2001-09-28 | 2008-10-01 | レヴェル 3 シーディーエヌ インターナショナル インコーポレーテッド. | Configurable adaptive wide area traffic control and management |
US7373644B2 (en) | 2001-10-02 | 2008-05-13 | Level 3 Communications, Llc | Automated server replication |
US20030079027A1 (en) | 2001-10-18 | 2003-04-24 | Michael Slocombe | Content request routing and load balancing for content distribution networks |
US20030140156A1 (en) * | 2002-01-18 | 2003-07-24 | Sun Microsystems, Inc. | Method and apparatus for broadcasting world wide web content |
US9167036B2 (en) | 2002-02-14 | 2015-10-20 | Level 3 Communications, Llc | Managed object replication and delivery |
US7076544B2 (en) * | 2002-04-08 | 2006-07-11 | Microsoft Corporation | Caching techniques for streaming media |
US7409456B2 (en) | 2002-04-10 | 2008-08-05 | Akami Technologies, Inc. | Method and system for enhancing live stream delivery quality using prebursting |
US20030204602A1 (en) | 2002-04-26 | 2003-10-30 | Hudson Michael D. | Mediated multi-source peer content delivery network architecture |
US8117328B2 (en) * | 2002-06-25 | 2012-02-14 | Microsoft Corporation | System and method for automatically recovering from failed network connections in streaming media scenarios |
US8028092B2 (en) | 2002-06-28 | 2011-09-27 | Aol Inc. | Inserting advertising content |
FI116816B (en) * | 2002-10-14 | 2006-02-28 | Nokia Corp | Streaming media |
US7552192B2 (en) * | 2002-12-18 | 2009-06-23 | Ronnie Gerome Carmichael | Massively parallel computer network-utilizing MPACT and multipoint parallel server (MPAS) technologies |
US7715934B2 (en) | 2003-09-19 | 2010-05-11 | Macrovision Corporation | Identification of input files using reference files associated with nodes of a sparse binary tree |
US20050089014A1 (en) * | 2003-10-27 | 2005-04-28 | Macrovision Corporation | System and methods for communicating over the internet with geographically distributed devices of a decentralized network using transparent asymetric return paths |
US7877810B2 (en) * | 2004-03-02 | 2011-01-25 | Rovi Solutions Corporation | System, method and client user interface for a copy protection service |
US20050223277A1 (en) * | 2004-03-23 | 2005-10-06 | Eacceleration Corporation | Online storage system |
US7818444B2 (en) | 2004-04-30 | 2010-10-19 | Move Networks, Inc. | Apparatus, system, and method for multi-bitrate content streaming |
KR100636147B1 (en) * | 2004-06-24 | 2006-10-18 | 삼성전자주식회사 | Method for controlling content over network and apparatus thereof, and method for providing content over network and apparatus thereof |
US7558822B2 (en) * | 2004-06-30 | 2009-07-07 | Google Inc. | Accelerating user interfaces by predicting user actions |
US7587398B1 (en) | 2004-06-30 | 2009-09-08 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US8676922B1 (en) | 2004-06-30 | 2014-03-18 | Google Inc. | Automatic proxy setting modification |
US7565423B1 (en) | 2004-06-30 | 2009-07-21 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US8224964B1 (en) | 2004-06-30 | 2012-07-17 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US7437364B1 (en) | 2004-06-30 | 2008-10-14 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US7526566B2 (en) * | 2004-09-10 | 2009-04-28 | Sony Ericsson Mobile Communications Ab | Methods of operating radio communications devices including predefined streaming times and addresses and related devices |
US7436936B2 (en) * | 2005-02-22 | 2008-10-14 | Level 3 Communications, Llc | VoIP call through tester |
US7519074B2 (en) * | 2005-02-22 | 2009-04-14 | Level 3 Communications, Llc | Voice call coordinator |
US7870602B2 (en) * | 2005-09-14 | 2011-01-11 | At&T Intellectual Property I, L.P. | System and method for reducing data stream interruption during failure of a firewall device |
US7809943B2 (en) * | 2005-09-27 | 2010-10-05 | Rovi Solutions Corporation | Method and system for establishing trust in a peer-to-peer network |
US7685298B2 (en) | 2005-12-02 | 2010-03-23 | Citrix Systems, Inc. | Systems and methods for providing authentication credentials across application environments |
US8086722B2 (en) * | 2005-12-21 | 2011-12-27 | Rovi Solutions Corporation | Techniques for measuring peer-to-peer (P2P) networks |
US7716586B2 (en) * | 2006-02-17 | 2010-05-11 | International Business Machines Corporation | Apparatus, system, and method for progressively disclosing information in support of information technology system visualization and management |
US8151323B2 (en) | 2006-04-12 | 2012-04-03 | Citrix Systems, Inc. | Systems and methods for providing levels of access and action control via an SSL VPN appliance |
US7747749B1 (en) | 2006-05-05 | 2010-06-29 | Google Inc. | Systems and methods of efficiently preloading documents to client devices |
US8677007B2 (en) | 2006-08-03 | 2014-03-18 | Citrix Systems, Inc. | Systems and methods for bypassing an appliance |
US7953889B2 (en) | 2006-08-03 | 2011-05-31 | Citrix Systems, Inc. | Systems and methods for routing VPN traffic around network disruption |
US20080049720A1 (en) * | 2006-08-25 | 2008-02-28 | Sbc Knowledge Ventures, Lp | System and method of delivering data via a network |
WO2008064356A1 (en) * | 2006-11-22 | 2008-05-29 | Metis Enterprise Technologies Llc | Real-time multicast peer-to-peer video streaming platform |
US8065275B2 (en) | 2007-02-15 | 2011-11-22 | Google Inc. | Systems and methods for cache optimization |
US8812651B1 (en) | 2007-02-15 | 2014-08-19 | Google Inc. | Systems and methods for client cache awareness |
JP5014074B2 (en) * | 2007-11-12 | 2012-08-29 | 株式会社リコー | Multi-function input / output device |
US8849838B2 (en) | 2008-01-15 | 2014-09-30 | Google Inc. | Bloom filter for storing file access history |
US8593570B2 (en) * | 2008-11-07 | 2013-11-26 | Looxcie, Inc. | Video recording camera headset |
WO2011022405A2 (en) | 2009-08-17 | 2011-02-24 | Akamai Technologies, Inc. | Method and system for http-based stream delivery |
US8392748B2 (en) * | 2009-10-06 | 2013-03-05 | Microsoft Corporation | Reliable media streaming |
US8458769B2 (en) * | 2009-12-12 | 2013-06-04 | Akamai Technologies, Inc. | Cloud based firewall system and service |
US8769614B1 (en) | 2009-12-29 | 2014-07-01 | Akamai Technologies, Inc. | Security framework for HTTP streaming architecture |
US8880633B2 (en) | 2010-12-17 | 2014-11-04 | Akamai Technologies, Inc. | Proxy server with byte-based include interpreter |
US20120265853A1 (en) * | 2010-12-17 | 2012-10-18 | Akamai Technologies, Inc. | Format-agnostic streaming architecture using an http network for streaming |
US8867337B2 (en) | 2011-04-26 | 2014-10-21 | International Business Machines Corporation | Structure-aware caching |
US8737803B2 (en) | 2011-05-27 | 2014-05-27 | Looxcie, Inc. | Method and apparatus for storing and streaming audiovisual content |
US20120303797A1 (en) * | 2011-05-27 | 2012-11-29 | Saroop Mathur | Scalable audiovisual streaming method and apparatus |
US9432704B2 (en) | 2011-11-06 | 2016-08-30 | Akamai Technologies Inc. | Segmented parallel encoding with frame-aware, variable-size chunking |
US9742858B2 (en) | 2011-12-23 | 2017-08-22 | Akamai Technologies Inc. | Assessment of content delivery services using performance measurements from within an end user client application |
US9419852B1 (en) | 2011-12-30 | 2016-08-16 | Akamai Technologies, Inc. | Systems and methods for identifying and characterizing client devices |
US8875287B2 (en) | 2012-10-04 | 2014-10-28 | Akamai Technologies, Inc. | Server with mechanism for reducing internal resources associated with a selected client connection |
US9654579B2 (en) | 2012-12-21 | 2017-05-16 | Akamai Technologies, Inc. | Scalable content delivery network request handling mechanism |
US9509804B2 (en) | 2012-12-21 | 2016-11-29 | Akami Technologies, Inc. | Scalable content delivery network request handling mechanism to support a request processing layer |
US9729605B2 (en) | 2012-12-27 | 2017-08-08 | Akamai Technologies Inc. | Mechanism for distinguishing between content to be served through first or second delivery channels |
US9183261B2 (en) * | 2012-12-28 | 2015-11-10 | Shutterstock, Inc. | Lexicon based systems and methods for intelligent media search |
US9819721B2 (en) | 2013-10-31 | 2017-11-14 | Akamai Technologies, Inc. | Dynamically populated manifests and manifest-based prefetching |
US9485456B2 (en) | 2013-12-30 | 2016-11-01 | Akamai Technologies, Inc. | Frame-rate conversion in a distributed computing system |
US9866655B2 (en) | 2014-03-31 | 2018-01-09 | Akamai Technologies, Inc. | Server initiated multipath content delivery |
US9900643B2 (en) | 2014-10-10 | 2018-02-20 | At&T Intellectual Property I, L.P. | Method and apparatus for transmitting media content |
US9948709B2 (en) | 2015-01-30 | 2018-04-17 | Akamai Technologies, Inc. | Using resource timing data for server push in multiple web page transactions |
US10313463B2 (en) | 2015-02-19 | 2019-06-04 | Akamai Technologies, Inc. | Systems and methods for avoiding server push of objects already cached at a client |
US10630771B1 (en) | 2015-02-26 | 2020-04-21 | Akamai Technologies, Inc. | Content delivery network with network storage and support for on-demand content upload |
US9667619B1 (en) | 2016-10-14 | 2017-05-30 | Akamai Technologies, Inc. | Systems and methods for utilizing client side authentication to select services available at a given port number |
WO2018126134A1 (en) | 2016-12-30 | 2018-07-05 | Akamai Technologies, Inc. | Unified, browser-based enterprise collaboration platform |
US10084855B2 (en) | 2017-01-23 | 2018-09-25 | Akamai Technologies, Inc. | Pixel-based load balancing |
US9986269B1 (en) | 2017-03-03 | 2018-05-29 | Akamai Technologies, Inc. | Maintaining stream continuity counter in a stateless multiplexing system |
US11088940B2 (en) | 2017-03-07 | 2021-08-10 | Akamai Technologies, Inc. | Cooperative multipath |
US10764391B2 (en) | 2017-09-14 | 2020-09-01 | Akamai Technologies, Inc. | Origin and cache server cooperation for compute-intensive content delivery |
US10887385B2 (en) | 2017-09-20 | 2021-01-05 | Akamai Technologies, Inc. | Marker based reporting system for hybrid content delivery network and peer to peer network |
US10531134B2 (en) | 2017-11-10 | 2020-01-07 | Akamai Technologies, Inc. | Determining a time budget for transcoding of video |
US10581948B2 (en) | 2017-12-07 | 2020-03-03 | Akamai Technologies, Inc. | Client side cache visibility with TLS session tickets |
US10439925B2 (en) | 2017-12-21 | 2019-10-08 | Akamai Technologies, Inc. | Sandbox environment for testing integration between a content provider origin and a content delivery network |
US10810279B2 (en) | 2018-02-07 | 2020-10-20 | Akamai Technologies, Inc. | Content delivery network (CDN) providing accelerated delivery of embedded resources from CDN and third party domains |
US10764402B2 (en) | 2018-03-03 | 2020-09-01 | Akamai Technologies, Inc. | Leveraging time-windows generated by web browser pre-connections |
US10440142B2 (en) | 2018-03-06 | 2019-10-08 | Akamai Technologies, Inc. | Automated TTL adjustment using cache performance and purge data |
US10958649B2 (en) | 2018-03-21 | 2021-03-23 | Akamai Technologies, Inc. | Systems and methods for internet-wide monitoring and protection of user credentials |
US10681001B2 (en) | 2018-03-29 | 2020-06-09 | Akamai Technologies, Inc. | High precision mapping with intermediary DNS filtering |
US11039206B2 (en) | 2018-04-09 | 2021-06-15 | Hulu, LLC | Differential media presentation descriptions for video streaming |
US10452563B1 (en) | 2018-05-07 | 2019-10-22 | Akamai Technologies, Inc. | Cache eviction scheme for acceptable substitutes in online media |
US10667172B2 (en) | 2018-06-18 | 2020-05-26 | Akamai Technologies, Inc. | Download management with congestion mitigation for over the air content delivery to vehicles |
EP3808043A4 (en) | 2018-06-18 | 2021-09-15 | Akamai Technologies, Inc. | Download management with congestion mitigation for over the air content delivery to vehicles |
US11012362B2 (en) | 2018-06-18 | 2021-05-18 | Akamai Technologies, Inc. | Download management with congestion mitigation for over the air content delivery to vehicles |
US10834138B2 (en) | 2018-08-13 | 2020-11-10 | Akamai Technologies, Inc. | Device discovery for cloud-based network security gateways |
US10931695B2 (en) | 2018-08-22 | 2021-02-23 | Akamai Technologies, Inc. | Nonce injection and observation system for detecting eavesdroppers |
US10798006B2 (en) | 2018-10-12 | 2020-10-06 | Akamai Technologies, Inc. | Overload protection for data sinks in a distributed computing system |
US11245667B2 (en) | 2018-10-23 | 2022-02-08 | Akamai Technologies, Inc. | Network security system with enhanced traffic analysis based on feedback loop and low-risk domain identification |
US11019034B2 (en) | 2018-11-16 | 2021-05-25 | Akamai Technologies, Inc. | Systems and methods for proxying encrypted traffic to protect origin servers from internet threats |
US10958624B2 (en) | 2018-12-06 | 2021-03-23 | Akamai Technologies, Inc. | Proxy auto-configuration for directing client traffic to a cloud proxy with cloud-based unique identifier assignment |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6263371B1 (en) * | 1999-06-10 | 2001-07-17 | Cacheflow, Inc. | Method and apparatus for seaming of streaming content |
US6314466B1 (en) * | 1998-10-06 | 2001-11-06 | Realnetworks, Inc. | System and method for providing random access to a multimedia object over a network |
US6415323B1 (en) * | 1999-09-03 | 2002-07-02 | Fastforward Networks | Proximity-based redirection system for robust and scalable service-node location in an internetwork |
US6732162B1 (en) * | 1999-11-15 | 2004-05-04 | Internet Pictures Corporation | Method of providing preprocessed images for a plurality of internet web sites |
Family Cites Families (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5285441A (en) * | 1992-03-17 | 1994-02-08 | At&T Bell Laboratories | Errorless line protection switching in asynchronous transer mode (ATM) communications systems |
JPH0637764A (en) * | 1992-07-20 | 1994-02-10 | Fujitsu Ltd | Routing system for remote bridge and remote bridge device |
GB2281672A (en) * | 1993-09-03 | 1995-03-08 | Ibm | Video conferencing system |
DE4416718C2 (en) * | 1994-05-11 | 1997-08-21 | Siemens Ag | Circuit arrangement for the trouble-free rerouting of a message cell stream to an alternative path |
US5996001A (en) * | 1994-09-27 | 1999-11-30 | Quarles; Philip | High availability on-line transaction processing system |
JPH08139748A (en) * | 1994-11-08 | 1996-05-31 | Nec Corp | Broadcast communication processing method for store-and-forward switching device |
US5854898A (en) | 1995-02-24 | 1998-12-29 | Apple Computer, Inc. | System for automatically adding additional data stream to existing media connection between two end points upon exchange of notifying and confirmation messages therebetween |
DE19509602C1 (en) * | 1995-03-16 | 1996-05-30 | Siemens Ag | Redundancy optimised line network for ATM cells and SDH containers |
DE59611461D1 (en) * | 1995-03-16 | 2008-04-10 | Nokia Siemens Networks Gmbh | Redundancy-optimized communication network for the transmission of message signals |
US5623483A (en) * | 1995-05-11 | 1997-04-22 | Lucent Technologies Inc. | Synchronization system for networked multimedia streams |
CA2196622C (en) * | 1996-02-06 | 2001-10-16 | Hiroshi Jinzenji | Network data distribution system |
US5805785A (en) * | 1996-02-27 | 1998-09-08 | International Business Machines Corporation | Method for monitoring and recovery of subsystems in a distributed/clustered system |
US5831975A (en) * | 1996-04-04 | 1998-11-03 | Lucent Technologies Inc. | System and method for hierarchical multicast routing in ATM networks |
US5778187A (en) | 1996-05-09 | 1998-07-07 | Netcast Communications Corp. | Multicasting method and apparatus |
DE19741577A1 (en) * | 1997-09-20 | 1999-03-25 | Cit Alcatel | Methods and devices for establishing point-to-multipoint connections and multipoint-to-point connections |
US5928331A (en) * | 1997-10-30 | 1999-07-27 | Matsushita Electric Industrial Co., Ltd. | Distributed internet protocol-based real-time multimedia streaming architecture |
US6466574B1 (en) | 1998-06-05 | 2002-10-15 | International Business Machines Corporation | Quality of service improvement of internet real-time media transmission by transmitting redundant voice/media frames |
US6195680B1 (en) * | 1998-07-23 | 2001-02-27 | International Business Machines Corporation | Client-based dynamic switching of streaming servers for fault-tolerance and load balancing |
US6505240B1 (en) * | 1998-08-31 | 2003-01-07 | Trevor I. Blumenau | Ameliorating bandwidth requirements for the simultaneous provision of multiple sets of content over a network |
US6529475B1 (en) * | 1998-12-16 | 2003-03-04 | Nortel Networks Limited | Monitor for the control of multimedia services in networks |
US6594798B1 (en) * | 1999-05-21 | 2003-07-15 | Microsoft Corporation | Receiver-driven layered error correction multicast over heterogeneous packet networks |
US6697365B1 (en) * | 1999-06-10 | 2004-02-24 | Charles Hayes Messenger | Method of listener transmitted broadcasting |
US6496477B1 (en) * | 1999-07-09 | 2002-12-17 | Texas Instruments Incorporated | Processes, articles, and packets for network path diversity in media over packet applications |
US6339785B1 (en) * | 1999-11-24 | 2002-01-15 | Idan Feigenbaum | Multi-server file download |
-
2000
- 2000-01-06 US US09/478,571 patent/US6665726B1/en not_active Expired - Lifetime
-
2001
- 2001-01-02 CA CA002396261A patent/CA2396261C/en not_active Expired - Lifetime
- 2001-01-02 EP EP01900056A patent/EP1247383B1/en not_active Expired - Lifetime
- 2001-01-02 AT AT01900056T patent/ATE506795T1/en not_active IP Right Cessation
- 2001-01-02 DE DE60144466T patent/DE60144466D1/en not_active Expired - Lifetime
- 2001-01-02 WO PCT/US2001/000079 patent/WO2001050710A1/en active IP Right Grant
- 2001-01-02 AU AU23006/01A patent/AU774277B2/en not_active Expired
- 2001-01-02 JP JP2001550966A patent/JP4723151B2/en not_active Expired - Lifetime
-
2003
- 2003-06-09 US US10/457,266 patent/US7296082B2/en not_active Expired - Lifetime
-
2007
- 2007-10-30 US US11/928,042 patent/US20080052404A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6314466B1 (en) * | 1998-10-06 | 2001-11-06 | Realnetworks, Inc. | System and method for providing random access to a multimedia object over a network |
US6263371B1 (en) * | 1999-06-10 | 2001-07-17 | Cacheflow, Inc. | Method and apparatus for seaming of streaming content |
US6415323B1 (en) * | 1999-09-03 | 2002-07-02 | Fastforward Networks | Proximity-based redirection system for robust and scalable service-node location in an internetwork |
US6732162B1 (en) * | 1999-11-15 | 2004-05-04 | Internet Pictures Corporation | Method of providing preprocessed images for a plurality of internet web sites |
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8307088B2 (en) * | 2000-04-17 | 2012-11-06 | Akamai Technologies, Inc. | HTML delivery from edge-of-network servers in a content delivery network (CDN) |
US20110307584A1 (en) * | 2000-04-17 | 2011-12-15 | Akamai Technologies, Inc. | HTML delivery from edge-of-network servers in a content delivery network (CDN) |
US9599720B2 (en) * | 2000-07-13 | 2017-03-21 | Broadcom Corporation | Method and apparatus for locating mobile receivers using a wide area reference network for propagating ephemeris |
US20060271293A1 (en) * | 2000-07-13 | 2006-11-30 | Global Locate, Inc. | Method And Apparatus For Locating Mobile Receivers Using A Wide Area Reference Network For Propagating Ephemeris |
US8930137B2 (en) | 2000-07-13 | 2015-01-06 | Global Locate, Inc. | Method and apparatus for locating mobile receivers using a wide area reference network for propagating ephemeris |
US20090267833A1 (en) * | 2000-07-13 | 2009-10-29 | Van Diggelen Frank | Method and apparatus for locating mobile receivers using a wide area reference network for propagating ephemeris |
US20080063003A1 (en) * | 2001-09-13 | 2008-03-13 | Network Foundation Technologies | System and method for broadcasting content to nodes on computer networks |
US7843855B2 (en) * | 2001-09-13 | 2010-11-30 | Network Foundation Technologies, Llc | System and method for broadcasting content to nodes on computer networks |
US10674387B2 (en) | 2003-08-29 | 2020-06-02 | Ineoquest Technologies, Inc. | Video quality monitoring |
US9191426B2 (en) | 2003-08-29 | 2015-11-17 | Inequest Technologies, Inc. | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US8838772B2 (en) | 2003-08-29 | 2014-09-16 | Ineoquest Technologies, Inc. | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US8588069B2 (en) | 2003-08-29 | 2013-11-19 | Ineoquest Technologies, Inc. | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US20060184670A1 (en) * | 2003-08-29 | 2006-08-17 | Beeson Jesse D | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US10681574B2 (en) | 2003-08-29 | 2020-06-09 | Ineoquest Technologies, Inc. | Video quality monitoring |
US9590816B2 (en) * | 2003-08-29 | 2017-03-07 | Ineoquest Technologies, Inc. | System and method for creating multiple transportation streams of streaming media network test traffic in packet-based networks |
US20090097413A1 (en) * | 2003-08-29 | 2009-04-16 | Todd Marc A C | System and Method for Analyzing the Performance of Multiple Transportation Streams of Streaming Media in Packet-Based Networks |
US10681575B2 (en) | 2003-08-29 | 2020-06-09 | IneoQuesto Technologies, Inc. | Video quality monitoring |
US20120014254A1 (en) * | 2003-08-29 | 2012-01-19 | Todd Marc A C | System and method for creating multiple transportation streams of streaming media network test traffic in packet-based networks |
US7747894B2 (en) * | 2005-06-06 | 2010-06-29 | Microsoft Corporation | Transport-neutral in-order delivery in a distributed system |
US20060274727A1 (en) * | 2005-06-06 | 2006-12-07 | Microsoft Corporation | Transport-neutral in-order delivery in a distributed system |
EP2145427A4 (en) * | 2007-05-09 | 2010-09-29 | Network Foundation Technologie | System and method for broadcasting content to nodes on computer networks |
US20110225454A1 (en) * | 2008-11-21 | 2011-09-15 | Huawei Device Co., Ltd | Method, recording terminal, server, and system for repairing media file recording errors |
US8627139B2 (en) * | 2008-11-21 | 2014-01-07 | Huawei Device Co., Ltd. | Method, recording terminal, server, and system for repairing media file recording errors |
US20100223378A1 (en) * | 2009-02-27 | 2010-09-02 | Yottaa Inc | System and method for computer cloud management |
US8209415B2 (en) | 2009-02-27 | 2012-06-26 | Yottaa Inc | System and method for computer cloud management |
US20100223364A1 (en) * | 2009-02-27 | 2010-09-02 | Yottaa Inc | System and method for network traffic management and load balancing |
US20100220622A1 (en) * | 2009-02-27 | 2010-09-02 | Yottaa Inc | Adaptive network with automatic scaling |
US20100228819A1 (en) * | 2009-03-05 | 2010-09-09 | Yottaa Inc | System and method for performance acceleration, data protection, disaster recovery and on-demand scaling of computer applications |
US20100251329A1 (en) * | 2009-03-31 | 2010-09-30 | Yottaa, Inc | System and method for access management and security protection for network accessible computer services |
US20120072604A1 (en) * | 2009-05-29 | 2012-03-22 | France Telecom | technique for delivering content to a user |
US20110215893A1 (en) * | 2010-03-04 | 2011-09-08 | Michael Nussbaum | Planar audio amplifier output inductor with current sense |
US8930563B2 (en) * | 2011-10-27 | 2015-01-06 | Microsoft Corporation | Scalable and extendable stream processing |
Also Published As
Publication number | Publication date |
---|---|
CA2396261A1 (en) | 2001-07-12 |
WO2001050710A1 (en) | 2001-07-12 |
EP1247383A1 (en) | 2002-10-09 |
JP4723151B2 (en) | 2011-07-13 |
US7296082B2 (en) | 2007-11-13 |
AU774277B2 (en) | 2004-06-24 |
EP1247383B1 (en) | 2011-04-20 |
CA2396261C (en) | 2009-10-13 |
US20030200326A1 (en) | 2003-10-23 |
ATE506795T1 (en) | 2011-05-15 |
AU2300601A (en) | 2001-07-16 |
US6665726B1 (en) | 2003-12-16 |
JP2003519967A (en) | 2003-06-24 |
DE60144466D1 (en) | 2011-06-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6665726B1 (en) | Method and system for fault tolerant media streaming over the internet | |
US8473629B2 (en) | Method and system for enhancing live stream delivery quality using prebursting | |
US11470138B2 (en) | Apparatus, system, and method for multi-bitrate content streaming | |
US7657644B1 (en) | Methods and apparatus for streaming media multicast | |
US6751673B2 (en) | Streaming media subscription mechanism for a content delivery network | |
US20100312828A1 (en) | Server-controlled download of streaming media files | |
US20040003101A1 (en) | Caching control for streaming media | |
EP0961490A2 (en) | Internet convolution audio/video server | |
WO1997042582A9 (en) | Multicasting method and apparatus | |
WO2001080558A9 (en) | A system and method for multimedia streaming | |
Willebeek-LeMair et al. | Bamba—Audio and video streaming over the Internet | |
US10277957B2 (en) | Method for delivering an audio-video live content in multicast form | |
Hong et al. | QoS control for internet delivery of video data | |
WO2000077985A1 (en) | Method and apparatus for network traffic smoothing | |
Norberg et al. | Streaming in a UM System | |
Zimmermann et al. | Residential Broadband Services | |
Ödemir | A client-server architecture for live video streaming using object relational database | |
Thyagharajan et al. | Effective network models for multimedia streaming | |
AU2002229123A1 (en) | Streaming media subscription mechanism for a content delivery network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |