Patent Grant
9521006
The following description relates to using switching technologies to stream media in digital conferencing applications.
Video conferencing generally describes a process whereby conferencing participants can communicate remotely with one another through the use of video equipment that typically includes some form of camera and a video display. Increased usage of the Internet has resulted in an increased demand for video conferencing and a corresponding need for cost effective multimedia communications solutions.
In one general aspect, data units may be transmitted by using a switch to receive from at least two conferencing participants a stream of data units that each include a payload portion and an attribute portion. The switch duplicates at least a subportion of the payload portion of a data unit within the stream of data units, and enables access to the duplicated subportion of the data unit by two or more conferencing participants.
In another general aspect, a conferencing participant may participate in an electronic conference by interfacing with a network that includes a switch that duplicates the stream of data units sent by two or more conferencing participants and makes the duplicated stream of data units accessible to more than one conferencing participant. The streams are received from the switch, with each stream including a payload portion that has been duplicated by the switch and an attribute portion that has been transmitted by more than one other conferencing participant.
In another general aspect, a conferencing participant participates in an electronic conference by interfacing with a network that includes one or more switches capable of duplicating at least a payload portion of a data unit within a stream of data units. The conferencing participant transmits the stream of data units to the switches for duplication of at least the payload portion for transmission to two or more conferencing participants.
In another general aspect, a conferencing participant participates in an electronic conference by interfacing with a network that includes a switch capable of duplicating a stream. The participant transmits a stream to the switch and receives duplicated streams from the switch.
Implementations may include one or more of the following features. For example, the data unit may include an Internet Protocol packet. The attribute portion of the data unit may include an Internet Protocol header, or one or more pieces of layer three information.
Implementations may include using the switch to generate and associate different attribute portions with duplicates of the payload portion generated by the switch. Using the switch to duplicate at least the payload portion may include duplicating only the payload portion of the data unit. Using the switch to associate different attribute portions with the data unit and duplicates of the payload portion may include specifying destination information that differs among the duplicates of the payload portion. Using the switch to generate and associate different attribute portions may include changing an IP destination address. Changing the IP destination address may include changing the IP destination address to an IP address corresponding to one or more conferencing participants to which access to the payload portion will be enabled.
Using the switch to duplicate may include using the switch to duplicate the payload portion and the attribute portion. The switch may enable the conferencing participants to access duplicated subportions of data units in response to receiving a request to access the stream of data units. The request may be received from at least a requesting one of the two or more conferencing participants, or from a device other than the conferencing participants.
Using the switch to enable access to the duplicated subportions of the data unit may include transmitting two or more duplicated subportions to two or more conferencing participants using the switch. Using the switch to enable access to the duplicated subportions of the data unit by two or more conferencing participants may include transmitting two or more duplicated subportions from a transmitting participant to all of the conferencing participants using the switch, or from all of the conferencing participants to all of the conferencing participants using the switch. Transmitting two or more duplicated subportions from all of the conferencing participants to all of the conferencing participants may include enabling the switch to filter an originating stream so that a stream of data units from an originating conferencing participant is not transmitted back to the originating conferencing participant.
Implementations may include partitioning content from a stream that includes a combination of a forwarded signal and a filtered signal. The forwarded signal may differ from the filtered signal. For example, the underlying media format may be transcoded to a different bit rate.
Implementations may include determining whether one of the conferencing participants is attempting to actively participate. Using the switch to enable access to the duplicated subportions of the data unit by two or more conferencing participants may include enabling access to the streams of the conferencing participants attempting to actively participate most recently. The streams of conferencing participants that have not attempted to actively participate may not be duplicated.
Using the switch to enable access to the duplicated subportions may include prioritizing conferencing participants to determine which streams of the conferencing participants are duplicated. Access to the streams of conferencing participants with higher priorities may be enabled before enabling access to the data streams of conferencing participants with lower priorities. A priority for a participant may be specified by one of a service provider, a conference organizer, or a conference manager.
Using a switch to enable access to the duplicated subportion of the data unit by two or more conferencing participants may include using the conference manager to designate which of the conferencing participants' data streams are enabled to be accessed. Perceivable output may be displayed based on the stream of data units.
The details of one or more implementations are set forth in the accompanying drawings and the descriptions below. Other features and advantages will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
In general, switching technologies may be used to duplicate packets in a digital conference (e.g., digital video stream) sent from one workstation as part of an electronic conference. The switching technologies enable the multiple streams sent from the switch to the recipient workstations to be generated from a single digital stream sent from the sending workstation to the switch. Thus, a terminal participating in the conference does not need to transmit a stream for each participant.
By way of introduction,
Referring to
A transmitting participant 110 typically includes a computer system that converts a media feed into a stream. Transmitting participant 110 may be structured and arranged to convert the media source (e.g., a video or audio feed) into data units for transmission across a network 120. The transmitting participant 110 may include a general-purpose computer having a central processor unit (CPU) and memory/storage devices that store data and various programs such as an operating system and one or more application programs. Other examples of a transmitting participant 110 include a workstation, a server, a device, a special purpose device or component, a broadcast system, other equipment, or some combination thereof capable of responding to and executing instructions in a defined manner. The transmitting participant 110 also typically includes an input/output (I/O) device (e.g., one or more devices having a video and/or audio input and conversion capability), and peripheral equipment such as a communications card or device (e.g., a modem or a network adapter) for exchanging data with the network 120.
A communications link 115 is used to communicate data between the transmitting participant 110 and the network 120. Communications link 115 may include, for example, a telephone line, a wireless network link, a cable network, or a direct connection.
The network 120 typically includes hardware and/or software capable of enabling direct or indirect communications between the transmitting participant 110 and the switch 130. The network 120 may include a direct link between the transmitting participant 110 and the switch 130, or it may include one or more networks or subnetworks between them (not explicitly shown). Each network or subnetwork may include, for example, a wired or wireless data pathway capable of carrying and receiving data. Examples of network 120 include the Internet, the World Wide Web, a WAN (“Wide Area Network”), a LAN (“Local Area Network”), an analog or a digital wired or wireless telephone network (e.g., a PSTN (“Public Switched Telephone Network”), an ISDN (“Integrated Services Digital Network”), or a xDSL (“any form of Digital Subscriber Loop”)), and/or a radio network, a television network, a cable network, a satellite network, or some other delivery mechanism for carrying data.
The switch 130 typically is structured and arranged to receive streams of data units (e.g., from the transmitting participant 110 and the conferencing participants 150A and 150B), to duplicate the stream of data units, and to transmit the duplicated streams to two or more conferencing participants 150A and 150B.
In some implementations, the switch 130 is structured and arranged to perform filtering and forwarding between different domains at the same level of the protocol stack in the OSI (“Open System Interconnection”) reference model. For example, in some networks, switch 130 may forward Ethernet frames between different Ethernet segments. In another example, switch 130 may forward IP packets between different IP subnets.
Generally, switch 130 includes a device that performs network operations and functions in hardware (e.g., a chip or a part of chip). In some implementations, the device may include an ASIC (“Application Specific Integrated Circuit”) that implements network operations logic directly on a chip (e.g., logical gates fabricated on a silicon wafer then manufactured into a chip). For example, an ASIC chip may implement a logical gate structure in silicon to perform filtering by receiving a packet, examining the IP address of the received packet, and filtering based on the IP address.
Implementations of the device included in the switch 130 may use a Field Programmable Gate Array (FPGA). A FPGA is generally defined as including a chip or chips fabricated to allow third party designers to implement a variety of logical designs on the chip. For example, a third party designer may load a design within a FPGA to replace the received IP addresses with different IP addresses, or may load a design within the FPGA to segment and reassemble IP packets as they are modified while being transmitted through different networks.
Implementations of the device included in the switch 130 may include a network processor. A network processor generally is defined to include a chip or chips for allowing software to specify network operations to be performed. A network processor may perform a variety of operations. One example of a network processor may include several interconnected RISC (“Reduced Instruction Set Computer”) processors fabricated in a network processor chip. The network processor chip may implement software on some of the RISC processors to change an IP address of an IP packet. Other RISC processors in the network processor chip may implement software that determines which conferencing participants are receiving an IP stream.
Although various examples of network operations were defined with respect to different devices, each of the devices may to be programmable and capable of performing the operations of the other devices. For example, the FPGA device is described as the device used to replace IP addresses and segment and reassemble packets; however, a network processor and ASIC are generally capable of performing the same operations.
Data units handled by switch 130 may be accessed by or sent to conferencing participants 150A and 150B through network 140. As such, network 140 is structured and arranged to receive data units transmitted from the switch 130 for transmission to the conferencing participants 150.
The conference manager 135 may include one or more devices capable of enabling an electronic conference of two or more conferencing participants. The conference manager 135 may include a controller (not shown) that processes instructions received from or generated by a software application, a program, a piece of code, a device, a computer, a computer system, or a combination thereof, to direct operations of the conference manager 135. The instructions may be embodied permanently or temporarily in any type of machine, component, equipment, storage medium, or propagated signal that is capable of being delivered to the conference manager 135 or that may reside with the controller at the conference manager 135. The conference manager 135 may include a general-purpose computer (e.g., a personal computer) capable of responding to and executing instructions in a defined manner, a system or a component in the switch 130, other equipment, or some combination of these items that is capable of responding to and executing instructions.
For instance, in one implementation, the conference manager 135 includes one or more scheduling, management, and authentication applications (e.g., calendaring software) capable of establishing and managing one or more electronic conferences. These scheduling and authentication applications may run on a general purpose operating system and a hardware platform that includes a general purpose processor and specialized hardware for graphics, communications and/or other capabilities. In another implementation, conference manager 135 may include a switch designation component (e.g., a server or program) that determines the switch 130 with which the conferencing participants will be communicating. For example, the conference manager 135 may be structured and arranged to communicate to the conferencing participants which specific switch will host the conference (e.g., duplicate and transmit the streams of data units), or to communicate to the designated switch the required information and authorization to host the conference.
Implementations of the conference manager 135 may include a service provider or a conference organizer. For example, a service provider may offer conferencing services and arrange or set up conferences. In another example, a conference organizer (e.g., a user putting together an electronic conference) may act both as a conference manager 135 and a conferencing participant 150B.
The network 140 may include hardware and/or software capable of enabling direct or indirect communications between the switch 130 and the conferencing participant 150. As such, the network 140 may include a direct link between the switch 130 and the conferencing participant 150, or it may include one or more networks or subnetworks between them (not shown). Each network or subnetwork may include, for example, a wired or wireless data pathway capable of carrying and receiving data. Examples of the delivery network include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., PSTN, ISDN, or xDSL), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data. Network 120 and network 140 may share one or more hardware or software devices.
Conferencing participants 150A and 150B may include one or more devices capable of receiving the streams of data units transmitted by switch 130 through network 140. The conferencing participant 150A may include a controller (not shown) that processes instructions received from or generated by a software application, a program, a piece of code, a device, a computer, a computer system, or a combination thereof, to direct operations of the conferencing participant 150A. The instructions may be embodied permanently or temporarily in any type of machine, component, equipment, storage medium, or propagated signal that is capable of being delivered to the conferencing participant 150A or that may reside with the controller at the conferencing participant 150. The conferencing participant 150 may include a general-purpose computer (e.g., a personal computer) capable of responding to and executing instructions in a defined manner, a workstation, a laptop, a PDA (“Personal Digital Assistant”), a wireless phone, a component, other equipment, or some combination of these items that is capable of responding to and executing instructions.
For instance, in one implementation, the conferencing participant 150A includes one or more information retrieval software applications (e.g., a browser, a mail application, an instant messaging client, an Internet service provider client, or an AOL TV or other integrated client) capable of receiving one or more data units. The information retrieval applications may run on a general purpose operating system and a hardware platform that includes a general purpose processor and specialized hardware for graphics, communications and/or other capabilities. In another implementation, conferencing participant 150A may include a wireless telephone running a micro-browser application on a reduced operating system with general purpose and specialized hardware capable of operating in mobile environments.
Generally, conferencing participant 150A participates in an electronic conference by transmitting and receiving streams of data units. However, implementations may include having conferencing participants 150A participate in an a synchronous mode. For example, an electronic conference may incorporate a news feed that is being discussed and transmitted by a transmitting participant. In another example, a briefing may be incorporated into an electronic conference to enable wider participation. Other asynchronous modes may include conferencing participants that receive but do not transmit. For these and other reasons, aspects of the transmitting participant 110 may resemble, but are not limited to, aspects of the conferencing participant 150A.
Conferencing participant 150B may include a workstation that is identical to conferencing participant 150A, or conferencing participant 150B may include a device that differs from conferencing participant 150A. For example, conferencing participant 150A may include a PDA while conferencing participant 150B includes a workstation.
In another implementation, the conferencing participants 150A and 150B may have different input/output capabilities. For example, one conferencing participant 150A may not have a camera from which to generate video content. This may limit the conferencing participant 150A to only sending an audio stream of data units. In another implementation, the conferencing participant 150A may have limited graphical display capabilities (e.g., the conferencing participant may be a PDA). The conferencing participant 150A may receive text messages exchanged as part of the electronic conference without receiving video content.
In general, the conferencing applications 200A are logically organized from the top of the diagram down based on the resources required by those applications. For example, video conferencing applications 210A generally require more bandwidth than text conferencing applications 240A. Similarly, the computational resources required by the image and audio compression techniques to compress, decompress and/or display media generally decrease from video conferencing applications 210A to image conferencing applications 220A to audio conferencing applications 230A to text conferencing applications 240A. The resources required for one or more applications may lead one or more conferencing participants to participate in a less resource-intensive manner.
Typically, video conferencing application 210A encodes and displays audio and video content. Implementations of video conferencing application 210A use compression to reduce the bandwidth consumed by transmitting the stream of data units. For example, video conferencing protocols and techniques may reduce the resolution, detail, or frame rate to reduce the bandwidth consumed. In another example, the frame-to-frame differences may be encoded for transmission instead of encoding each frame. Similar techniques may be applied to the audio signal. For example, the sampling rate of the audio signal may be reduced or the signal may be compressed.
Image conferencing application 220A typically operates by displaying one or more images to conferencing participants. Although an image conferencing application may resemble, in some implementations, a video conferencing application 210A with a low frame rate, image conferencing application 220A typically has non-video implementations. For example, a conferencing participant may input a map into an electronic conference in which aspects of the map are discussed. Other implementations may include inputting a web page and/or a slide show for incorporation into the electronic conference. In an implementation that resembles video conferencing application 210A, an image of the conferencing participant may be displayed in an audio conference when that conferencing participant is speaking.
Audio conferencing application 230A involves the use of an audio signal (e.g., a stream of data units) for incorporation into an electronic conference. Typically, aspects of the audio conferencing application may resemble aspects of the audio signal in a video conferencing application 210A discussed above in that the signal may be compressed.
Text conferencing application 240A involves the exchange of text in an electronic conference. One common form of exchanging text may feature the use of “chat” (e.g., a “chat room”). Other text exchanging applications may include electronic mail, instant messaging, SMS (“Short Message Service”), and proprietary applications. Although some of the text exchanging applications may not commonly appear as text conferencing applications 240A, implementations may include using an underlying text exchanging application as a transport mechanism in the conferencing application. For example, an electronic conference may use electronic mail to exchange text messages between conferencing participants. In another example, when one conferencing participant receives an instant message from another conferencing participant, the instant message may be incorporated into the electronic conference.
Typically, video application 210B features the display of two other conferencing participants. In one implementation, each conferencing participant has related text and audio conferencing applications, and the first conferencing participant may be represented by a video conferencing application 212B, an audio conferencing application 232B, and a text conferencing application 242B. The second conferencing participant communicates with a video application 214B, an audio conferencing application 234B, and a text conferencing application 244B. A third conferencing participant without video conferencing capability may communicate using an imaging application 220B, an audio conferencing application 236B, and a text conferencing application 246B.
The audio conferencing application 230B depicts an implementation reflecting both common audio properties as well as properties specific to their originating sources. More precisely, general audio sources generated simultaneously may cause destructive interference that make them difficult to understand. For this reason, the audio channel may be structured so that one audio channel is broadcast at a time. For example, implementations may commonly manage all audio conferencing applications and apply the same operating instructions to all received audio signals. In one example, receiving several different audio sources simultaneously may cause user confusion or comprehension difficulties that may be avoided through the application of filtering criteria generic to several users. Alternatively, it may be desirable to provide source-specific operating and/or filtering instructions. For example, where the different audio signals are received at different strengths, the conferencing participant may wish to reduce the volume from one conferencing participant and increase the volume from another conferencing participant. In another implementation, a conferencing participant may wish to listen to everything from the conferencing participant in the audio conferencing application 232B and “mute” or suppress the audio conferencing application 234B. Each function may be enabled through filtering controls displayed in user environment 200B.
A text conferencing application 240B may be a common application to all participants (as represented by the application appearing across the breadth of participants) or may be specific to conferencing participants (as represented by text conferencing applications 242B, 244B, and 246B. In one implementation of text conferencing as a common application to all participants, when a conferencing participant enters a message to be communicated, the participant's identification may appear next to the message. In implementations of conferencing participant-specific text conferencing, the message may be displayed in association with its source (e.g., underneath the corresponding participant).
Each of conferencing participant 310, 320, 330, and 340 transmits one stream of data units to the switch 350 for duplication, and receives the duplicated streams of the other participants in return from the switch 350. When each conferencing participant receives the stream of data units of all the other conferencing participants, the total number of streams sent out by the switch is 2(N−1), where N is the number of conferencing participants (i.e., the switch sends out six streams when there are four participants). Although
Furthermore, although one switch is depicted, implementations may include using more than one switch. For example, several users may initiate an electronic conference at one switch. However, as additional users join the electronic conference, additional switches may be added to support the electronic conference. More specifically, in one implementation, a first switch with limited available capacity may initiate a connection to a second switch and send all new connections to the second switch. Initiating the connection to the second switch may include exchanging duplicated data units between the first and second switches. In another example, when the second switch is activated, several users may be transferred to the second switch to be hosted. Implementations also may include intelligent switch selection criteria that activate use of a second switch. For example, when the switch determines that several users are located in the same proximity, the switch may activate an additional switch that is closer to the users to host the conference so that duplicated streams are not being transmitted across large portions of the network.
The conference manager 401 generally initiates the conference (step 410) by, for instance, determining the identity of a switch to host the conference and enabling the switch to host the conference for two or more terminals. The conference may be initiated in response to a request from a conferencing participant to host the conference. The conference may be initiated by allocating switch resources and authenticating conferencing participants. Allocating switch resources may include load balancing conferencing participants among more than one switch to reduce network/switch congestion. Conferencing participants seeking to join an electronic conference being hosted on a switch may be authenticated to ensure conference confidentiality through a login process or through a more elaborate set of steps, such as the exchanging of public and/or private keys.
The request to initiate the conference is received by switch 402 (step 412), which also may verify and authenticate the message (not shown). In response to the request, the switch 402 establishes the conference (step 413). Although the conference is established in response to a request from a conference manager, in some configurations, the conference manager may reside on a conferencing participant. In any event, the switch 402 establishes a conference with conferencing participants 403-406 (step 414). Establishing the connection generally enables a conferencing participant to communicate a stream of data units to other conferencing participants through the switch 402 and to receive streams of data units from one or more other conferencing participants through the switch 402.
Terminal 403 transmits a stream of data units (step 416) that is received by the switch 402 (step 418). The switch duplicates the stream of data units (step 420). In general, duplicating the stream of data units includes receiving a data unit, identifying a payload portion within the data unit, enabling an instance of the payload to be modified for subsequent transmission, and adding header information to the data unit to reflect addressing information corresponding to one or more recipients (e.g., conferencing participants 403-406). The stream may be duplicated by copying the payload (e.g., content) of an IP packet and changing the header information to reflect the IP address of the destination conferencing participants for the payload, by storing one or more IP packets for modification (e.g., the IP packet may be stored), by loading the packet to memory and changing the IP destination address while preserving other parameters in the header, or by other techniques. Operations may be performed on the payload before transmitting the payload to a conferencing participant. For example, the switch may transcode the content of the payload to reduce the bit rate of the stream. Generally, transcoding involves modifying a compressed signal so that the characteristics of the modified signal correspond to specified criteria. For example, a high bit rate video signal may be transcoded by having the compressed video signal expanded, and recompressed at a higher compression ratio before transmitting the recompressed signal to a conferencing participant.
Another operation that may be performed includes partitioning a combined signal to extract a forwarded signal and remove a filtered signal. For example, a switch may remove an audio signal from a combined audio-visual signal to reduce the bandwidth required to transmit the forwarded signal.
Although
In any event, regardless of the operations used during duplication of the payload portion, the switch 402 ultimately transmits the duplicated streams to conferencing participants 404-406 (step 422), and the conferencing participants 404-406 ultimately receive the stream of data units (step 424).
As part of participating in the electronic conference, terminal 404 transmits a stream of data units (step 426). The switch 402 receives (step 428) and duplicates (step 430) the stream of data units, and then transmits (step 432) the duplicated streams of data units which are received (step 434) by the conferencing participants 403, 405 and 406.
As the third participant to transmit in an electronic conference, terminal 405 transmits a stream of data units (step 435) that are received (step 436) by switch 402. The switch 402 performs operations on the data units. First, the switch 402 transcodes the data units (step 438). Typically, transcoding the data units involves modifying the content portion or underlying media format of a data unit to give the stream of data units a desired characteristic. For example, lower quality video may be decompressed and recompressed at a higher data rate with more detail and resolution. In another example, the data rate may be reduced by reducing the number of frames, and resolution, and/or by using a lossier compression algorithm.
Next the switch 402 extracts or partitions content from within the stream of data units (step 440) by, for example, filtering a signal from a stream of data units whose content combines more than one type of media (e.g., another signal). In this manner, an audio signal may be extracted from a composite audio-video signal.
Although
The stream of data units is transmitted to terminals 403, 404, and 406 (step 442) in one or several formats. Additionally, the transmitted data units may be received in various formats based on the terminal to which they are transmitted. For instance, terminal 403 may receive or filter an audio stream of data units where the audio portion of a video signal has been partitioned (step 446), terminal 404 may receive or filter a lower bit rate video that has been transcoded (step 448), and terminal 406 may receive or filter text that has been partitioned and an image that has been transcoded from the underlying stream of data units (step 450).
Although a conferencing participant may receive output streams of data units from several sources concurrently (e.g., using several displays on one or more display devices), the conferencing participant may selectively receive and/or display a subset of the multiple streams at any given instant. For example, limited bandwidth to the conferencing participant may constrain the number of simultaneous connections, or comprehension issues may undermine the advantages otherwise obtained by receiving more than one stream at a time. In an example of seven conferencing participants, it may be advantageous to transmit data streams from only four of the seven conferencing participants to the conferencing participant to avoid bandwidth constraints or to avoid confusing the recipient conferencing participant.
It may therefore become necessary to prioritize among several competing or simultaneous data streams. For example, access to the streams of data units may be limited to the conference manager's stream and also those of the three most recent “active” participants. A conferencing participant may be considered “active” when the participant attempts to transmit during the electronic conference by, for instance, speaking into a microphone, moving while on camera, or typing text in a chat window.
In this example, conferencing participant 501 is talking initially (step 510). In response, conferencing participant 508 perceives conferencing participant 501 (step 512).
If, in the course of the electronic conference, conferencing participant 502 begins talking (step 514), conferencing participant 508 stops perceiving conferencing participant 501 (step 516) and begins perceiving conferencing participant 502 (step 518). When conferencing participant 501 begins talking again (step 520), conferencing participant 508 stops perceiving conferencing participant 502 (step 522) and begins perceiving conferencing participant 501 (step 524) due to the fact that there is a new “active” participant.
When a conferencing participant 503 is designated as having a lower priority than the conference participant currently being broadcast/perceived, other conferencing participants disregard communications by that conferencing participant, as illustrated by conferencing participant 508 disregarding communications by conferencing participant 503 while higher-priority conferencing participant 501 is being perceived (steps 526 and 528).
Participant prioritization may be implemented by network-centric techniques or by conferencing participant-centric techniques. For example, in a network-centric prioritization, the switch may assign users different priorities designated by, for example, conference manager 504. This prioritization may be forwarded by a conferencing participant to the switch, which will selectively duplicate and enable access to (e.g., transmit) subportions of the stream of data units. If conflicts exist in priorities, the conference organizer's priorities may take precedence.
In a participant-centric technique, the receiving device may determine which streams of data units the switches should filter out. For example, the conferencing participant may elect to always receive the stream of data units of a specified conferencing participant. In yet another example, the conferencing participant may receive filtering or prioritization parameters from a conference manager 504.
To illustrate prioritization based at the conference manager 504, the conference manager 504 enables priority for conferencing participant 502 when conferencing participant 501 is transmitting (step 530). Conferencing participant 502 receives the priority to transmit and have its stream duplicated before other conferencing participants (step 532). In one implementation, the switch may receive a prioritization message and selectively duplicate streams, or may forward the prioritization message to conferencing participants to allow the participants to selectively filter signals. In another implementation, the conference manager 504 may direct a prioritization message to conferencing participants without using the switch to replicate the message. In yet another example, the conference manager 504 may contact the transmitting conferencing participant (e.g., conferencing participant 501) and direct that participant to stop transmitting.
Regardless of the prioritization systems used, conferencing participant 502 begins talking (step 534). In response, conferencing participant 508 stops perceiving conferencing participant 501 (step 536) and starts perceiving conferencing participant 502 (step 538). Even though conferencing participant 502 receives a priority designation, conferencing participant 501 begins talking (step 540). However, because conferencing participant 502 has been designated to be a higher priority than conferencing participant 501, conferencing participant 508 disregards conferencing participant 501 (step 542).
Other implementations are within the scope of the following claims. In particular, in some implementations, the switch may perform one or more of the functions performed by the conference manager. The switch, conferencing participants, and networks also may be distributed across different entities in the communications system and may make use of one or more agents and/or proxies to perform certain functions. For example, the switch may receive a forwarded list of conferencing requirements from a server that arranges electronic conferences to be hosted on one or more switches.
In one example, the conference may be launched by existing applications. For example, a user may be participating in a chat room. One of the users may propose a chat by entering a URL (“Uniform Resource Locator”) that is launched by the users clicking on the URL. For example, the URL may contain a hyperlink to conference ID#10 on duplicating switch on IP address A.B.C.D. Launching the URL ‘connects’ the terminal to the duplicating switch. Upon receiving the URL request from the terminal, the duplicating switch may then look up ID#10 and determine that stream IDs 10-14 are associated with ID#10 and transmit those streams to the requesting terminal. The duplicating switch also may receive stream ID 15 from the requesting terminal and send stream ID 15 to other participants in conference ID#10.
The present application is a continuation of U.S. application Ser. No. 13/620,820, filed on Sep. 15, 2012, which is a continuation of U.S. application Ser. No. 13/053,903, filed on Mar. 22, 2011, now issued as U.S. Pat. No. 8,463,853, which is a continuation of U.S. application Ser. No. 11/549,934, filed on Oct. 16, 2006, now issued as U.S. Pat. No. 7,921,157, which is a continuation of U.S. application Ser. No. 10/134,439, filed Apr. 30, 2002, now issued as U.S. Pat. No. 7,124,166, which claims priority to and the benefit of U.S. provisional application No. 60/343,182 filed Dec. 31, 2001 and U.S. provisional application No. 60/286,964, filed Apr. 30, 2001. Each of the aforementioned patents and applications are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4809262 | Klose et al. | Feb 1989 | A |
| 4872160 | Hemmady et al. | Oct 1989 | A |
| 5014125 | Pocock et al. | May 1991 | A |
| 5283639 | Esch et al. | Feb 1994 | A |
| 5493568 | Sampat et al. | Feb 1996 | A |
| 5543856 | Rosser et al. | Aug 1996 | A |
| 5583561 | Baker et al. | Dec 1996 | A |
| 5600364 | Hendricks et al. | Feb 1997 | A |
| 5600646 | Polomski | Feb 1997 | A |
| 5604542 | Dedrick | Feb 1997 | A |
| 5608446 | Carr et al. | Mar 1997 | A |
| 5646675 | Copriviza et al. | Jul 1997 | A |
| 5682597 | Ganek et al. | Oct 1997 | A |
| 5689641 | Ludwig et al. | Nov 1997 | A |
| 5742597 | Holt et al. | Apr 1998 | A |
| 5774660 | Brendel et al. | Jun 1998 | A |
| 5778187 | Monteiro et al. | Jul 1998 | A |
| 5799002 | Krishman | Aug 1998 | A |
| 5802301 | Dan et al. | Sep 1998 | A |
| 5809237 | Watts et al. | Sep 1998 | A |
| 5815662 | Ong | Sep 1998 | A |
| 5819036 | Adams et al. | Oct 1998 | A |
| 5838790 | McAuliffe et al. | Nov 1998 | A |
| 5838912 | Poon et al. | Nov 1998 | A |
| 5841763 | Leondires et al. | Nov 1998 | A |
| 5867502 | Chang | Feb 1999 | A |
| 5872588 | Aras et al. | Feb 1999 | A |
| 5889950 | Kuzma | Mar 1999 | A |
| 5907324 | Larson et al. | May 1999 | A |
| 5913062 | Vrvilo et al. | Jun 1999 | A |
| 5917830 | Chen et al. | Jun 1999 | A |
| 5920700 | Gordon et al. | Jul 1999 | A |
| 5935245 | Sherer | Aug 1999 | A |
| 5946614 | Robbins et al. | Aug 1999 | A |
| 5961603 | Kunkel et al. | Oct 1999 | A |
| 5969770 | Horton | Oct 1999 | A |
| 5973722 | Wakai et al. | Oct 1999 | A |
| 5983005 | Monteiro et al. | Nov 1999 | A |
| 5995943 | Bull et al. | Nov 1999 | A |
| 6006265 | Rangan et al. | Dec 1999 | A |
| 6011782 | DeSimone et al. | Jan 2000 | A |
| 6018766 | Samuel et al. | Jan 2000 | A |
| 6034746 | Desai et al. | Mar 2000 | A |
| 6052805 | Chen et al. | Apr 2000 | A |
| 6061349 | Coile et al. | May 2000 | A |
| 6061504 | Tzelnic et al. | May 2000 | A |
| 6064376 | Berezowski et al. | May 2000 | A |
| 6097720 | Araujo et al. | Aug 2000 | A |
| 6101187 | Cukier et al. | Aug 2000 | A |
| 6115752 | Chauhan | Sep 2000 | A |
| 6119163 | Monteiro et al. | Sep 2000 | A |
| 6141336 | Bauchot et al. | Oct 2000 | A |
| 6151621 | Colyer et al. | Nov 2000 | A |
| 6151632 | Chaddha et al. | Nov 2000 | A |
| 6157635 | Wang et al. | Dec 2000 | A |
| 6173314 | Kurashima et al. | Jan 2001 | B1 |
| 6189039 | Harvey et al. | Feb 2001 | B1 |
| 6195680 | Goldszmidt et al. | Feb 2001 | B1 |
| 6201859 | Memhard et al. | Mar 2001 | B1 |
| 6208975 | Bull et al. | Mar 2001 | B1 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6226686 | Rothschild et al. | May 2001 | B1 |
| 6253238 | Lauder et al. | Jun 2001 | B1 |
| 6259701 | Shur et al. | Jul 2001 | B1 |
| 6266335 | Bhaskaran | Jul 2001 | B1 |
| 6298088 | Bhatt et al. | Oct 2001 | B1 |
| 6298089 | Gazit | Oct 2001 | B1 |
| 6298129 | Culver et al. | Oct 2001 | B1 |
| 6308327 | Liu et al. | Oct 2001 | B1 |
| 6314451 | Landsman et al. | Nov 2001 | B1 |
| 6314464 | Murata et al. | Nov 2001 | B1 |
| 6327622 | Jindal et al. | Dec 2001 | B1 |
| 6339761 | Cottingham | Jan 2002 | B1 |
| 6347090 | Ooms et al. | Feb 2002 | B1 |
| 6357042 | Srinivasan et al. | Mar 2002 | B2 |
| 6360195 | Liao et al. | Mar 2002 | B1 |
| 6363075 | Huang et al. | Mar 2002 | B1 |
| 6363429 | Ketcham | Mar 2002 | B1 |
| 6370112 | Voelker | Apr 2002 | B1 |
| 6377996 | Lumelsky et al. | Apr 2002 | B1 |
| 6381746 | Urry | Apr 2002 | B1 |
| 6389462 | Cohen et al. | May 2002 | B1 |
| 6404745 | O'Neil et al. | Jun 2002 | B1 |
| 6411773 | De Vos et al. | Jun 2002 | B1 |
| 6415312 | Boivie | Jul 2002 | B1 |
| 6415323 | McCanne et al. | Jul 2002 | B1 |
| 6418214 | Smythe et al. | Jul 2002 | B1 |
| 6434622 | Monteiro et al. | Aug 2002 | B1 |
| 6437830 | Horlander | Aug 2002 | B1 |
| 6449657 | Stanbach et al. | Sep 2002 | B2 |
| 6457043 | Kwak et al. | Sep 2002 | B1 |
| 6466550 | Foster et al. | Oct 2002 | B1 |
| 6490285 | Lee et al. | Dec 2002 | B2 |
| 6490320 | Vetro | Dec 2002 | B1 |
| 6493872 | Rangan et al. | Dec 2002 | B1 |
| 6505169 | Bhagavath et al. | Jan 2003 | B1 |
| 6510553 | Hazra | Jan 2003 | B1 |
| 6516350 | Lumelsky et al. | Feb 2003 | B1 |
| 6526426 | Lakritz | Feb 2003 | B1 |
| 6564003 | Marko et al. | May 2003 | B2 |
| 6564380 | Murphy | May 2003 | B1 |
| 6587138 | Vogt et al. | Jul 2003 | B1 |
| 6606581 | Nickerson et al. | Aug 2003 | B1 |
| 6615039 | Eldering | Sep 2003 | B1 |
| 6622174 | Ukita et al. | Sep 2003 | B1 |
| 6625773 | Boivie | Sep 2003 | B1 |
| 6646997 | Baxley et al. | Nov 2003 | B1 |
| 6665726 | Leighton et al. | Dec 2003 | B1 |
| 6684249 | Frerichs et al. | Jan 2004 | B1 |
| 6698020 | Zigmond et al. | Feb 2004 | B1 |
| 6701355 | Brandt et al. | Mar 2004 | B1 |
| 6704930 | Eldering et al. | Mar 2004 | B1 |
| 6708213 | Bommaiah et al. | Mar 2004 | B1 |
| 6711212 | Lin | Mar 2004 | B1 |
| 6718551 | Swix et al. | Apr 2004 | B1 |
| 6728356 | Carroll | Apr 2004 | B1 |
| 6728784 | Mattaway | Apr 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6744460 | Nimri et al. | Jun 2004 | B1 |
| 6751219 | Lipp et al. | Jun 2004 | B1 |
| 6785704 | McCanne | Aug 2004 | B1 |
| 6826185 | Montanaro et al. | Nov 2004 | B1 |
| 6839734 | Vega-Garcia et al. | Jan 2005 | B1 |
| 6847618 | Laursen | Jan 2005 | B2 |
| 6850707 | Chang et al. | Feb 2005 | B1 |
| 6856967 | Woolston et al. | Feb 2005 | B1 |
| 6873627 | Miller et al. | Mar 2005 | B1 |
| 6879565 | Baxley et al. | Apr 2005 | B2 |
| 6889385 | Rakib et al. | May 2005 | B1 |
| 6891828 | Ngai | May 2005 | B2 |
| 6910078 | Raman et al. | Jun 2005 | B1 |
| 6978470 | Swix et al. | Dec 2005 | B2 |
| 6993081 | Brunheroto et al. | Jan 2006 | B1 |
| 6996102 | Pegrum et al. | Feb 2006 | B2 |
| 7007235 | Hussein et al. | Feb 2006 | B1 |
| 7016351 | Farinacci et al. | Mar 2006 | B1 |
| 7039932 | Eldering | May 2006 | B2 |
| 7054949 | Jennings | May 2006 | B2 |
| 7062510 | Eldering | Jun 2006 | B1 |
| 7072972 | Chin et al. | Jul 2006 | B2 |
| 7089577 | Rakib et al. | Aug 2006 | B1 |
| 7100183 | Kunkel et al. | Aug 2006 | B2 |
| 7124160 | Saulsbury et al. | Oct 2006 | B2 |
| 7124166 | Brown | Oct 2006 | B2 |
| 7133922 | She et al. | Nov 2006 | B1 |
| 7142509 | Rovner et al. | Nov 2006 | B1 |
| 7187690 | Taylor | Mar 2007 | B2 |
| 7203758 | Cook et al. | Apr 2007 | B2 |
| 7237033 | Weigand et al. | Jun 2007 | B2 |
| 7266609 | Bill | Sep 2007 | B2 |
| 7292571 | Brown | Nov 2007 | B2 |
| 7299291 | Shaw | Nov 2007 | B1 |
| 7394850 | Gordon | Jul 2008 | B1 |
| 7430609 | Brown et al. | Sep 2008 | B2 |
| 7447738 | Andrews et al. | Nov 2008 | B1 |
| 7500258 | Eldering | Mar 2009 | B1 |
| 7548962 | Weber et al. | Jun 2009 | B2 |
| 7694013 | Weigand et al. | Apr 2010 | B2 |
| 7711791 | DuVall et al. | May 2010 | B2 |
| 7895076 | Kutaragi et al. | Feb 2011 | B2 |
| 7921157 | Brown | Apr 2011 | B2 |
| 7991911 | Weigand | Aug 2011 | B2 |
| 8028092 | Brown et al. | Sep 2011 | B2 |
| 8094647 | Elliott et al. | Jan 2012 | B2 |
| 8130755 | Brown | Mar 2012 | B2 |
| 8135620 | Barsade et al. | Mar 2012 | B2 |
| 8224991 | Weigand | Jul 2012 | B2 |
| 8463853 | Brown | Jun 2013 | B2 |
| 8572278 | Bill | Oct 2013 | B2 |
| 8762575 | Brown | Jun 2014 | B2 |
| 8769151 | Brown | Jul 2014 | B2 |
| 8843559 | Brown | Sep 2014 | B2 |
| 8904026 | Weigand et al. | Dec 2014 | B2 |
| 9049032 | Brown | Jun 2015 | B2 |
| 20010018771 | Walker et al. | Aug 2001 | A1 |
| 20010030667 | Kelts | Oct 2001 | A1 |
| 20010036198 | Arsenault et al. | Nov 2001 | A1 |
| 20010044851 | Rothman et al. | Nov 2001 | A1 |
| 20010047516 | Swain et al. | Nov 2001 | A1 |
| 20010048662 | Suzuki et al. | Dec 2001 | A1 |
| 20010049620 | Blasko | Dec 2001 | A1 |
| 20020013852 | Janik et al. | Jan 2002 | A1 |
| 20020015496 | Weaver et al. | Feb 2002 | A1 |
| 20020019845 | Hariton | Feb 2002 | A1 |
| 20020019984 | Rakib | Feb 2002 | A1 |
| 20020023267 | Hoang | Feb 2002 | A1 |
| 20020024956 | Keller-Tuberg | Feb 2002 | A1 |
| 20020026482 | Morishige et al. | Feb 2002 | A1 |
| 20020026636 | LeComte | Feb 2002 | A1 |
| 20020031126 | Crichton et al. | Mar 2002 | A1 |
| 20020040404 | Lahr | Apr 2002 | A1 |
| 20020059591 | Nakagawa | May 2002 | A1 |
| 20020065922 | Shastri | May 2002 | A1 |
| 20020082914 | Beyda et al. | Jun 2002 | A1 |
| 20020093963 | Roullet et al. | Jul 2002 | A1 |
| 20020097857 | Kwan | Jul 2002 | A1 |
| 20020103863 | Pearson | Aug 2002 | A1 |
| 20020103864 | Rodman et al. | Aug 2002 | A1 |
| 20020112004 | Reid et al. | Aug 2002 | A1 |
| 20020112069 | Sim | Aug 2002 | A1 |
| 20020114302 | McDonald et al. | Aug 2002 | A1 |
| 20020116532 | Berg | Aug 2002 | A1 |
| 20020124099 | Srinivasan et al. | Sep 2002 | A1 |
| 20020126685 | Leatherbury et al. | Sep 2002 | A1 |
| 20020131400 | Tinsley et al. | Sep 2002 | A1 |
| 20020161847 | Weigand et al. | Oct 2002 | A1 |
| 20020161910 | Bill et al. | Oct 2002 | A1 |
| 20020172508 | Zennou | Nov 2002 | A1 |
| 20020191543 | Buskirk et al. | Dec 2002 | A1 |
| 20020191950 | Wang | Dec 2002 | A1 |
| 20030005052 | Feuer et al. | Jan 2003 | A1 |
| 20030018966 | Cook et al. | Jan 2003 | A1 |
| 20030018968 | Avnet | Jan 2003 | A1 |
| 20030061278 | Agarwalla et al. | Mar 2003 | A1 |
| 20030067934 | Hooper et al. | Apr 2003 | A1 |
| 20030099202 | Lear et al. | May 2003 | A1 |
| 20030126197 | Black et al. | Jul 2003 | A1 |
| 20030145038 | Bin Tariq et al. | Jul 2003 | A1 |
| 20030188308 | Kizuka | Oct 2003 | A1 |
| 20040025186 | Jennings et al. | Feb 2004 | A1 |
| 20040205829 | Hane, III | Oct 2004 | A1 |
| 20050010653 | McCanne | Jan 2005 | A1 |
| 20050015796 | Bruckner et al. | Jan 2005 | A1 |
| 20050036030 | Forkner et al. | Feb 2005 | A1 |
| 20050149364 | Ombrellaro | Jul 2005 | A1 |
| 20060188084 | Rogers et al. | Aug 2006 | A1 |
| 20060248231 | O'Rourke et al. | Nov 2006 | A1 |
| 20090150937 | Ellis et al. | Jun 2009 | A1 |
| 20110173054 | Kutaragi et al. | Jul 2011 | A1 |
| 20110208582 | Hoyle | Aug 2011 | A1 |
| 20110225046 | Eldering et al. | Sep 2011 | A1 |
| 20110231255 | Urbanski et al. | Sep 2011 | A1 |
| 20130010794 | Bill | Jan 2013 | A1 |
| 20130016721 | Bill | Jan 2013 | A1 |
| 20130173821 | Weigand et al. | Jul 2013 | A1 |
| 20140351852 | Brown | Nov 2014 | A1 |
| 20140351853 | Brown | Nov 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2445869 | Nov 2002 | CA |
| 1511289 | Jul 2004 | CN |
| 1063814 | Dec 2000 | EP |
| 1071287 | Jan 2001 | EP |
| 1220542 | Jul 2002 | EP |
| 2395700 | Dec 2011 | EP |
| 2309849 | Aug 1997 | GB |
| 08-320800 | Dec 1996 | JP |
| 9270793 | Oct 1997 | JP |
| 11-232201 | Aug 1999 | JP |
| 11-261580 | Sep 1999 | JP |
| 2000-010895 | Jan 2000 | JP |
| 2000-029813 | Jan 2000 | JP |
| 2000-172618 | Jun 2000 | JP |
| 2000-244427 | Sep 2000 | JP |
| 2001-508258 | May 2001 | JP |
| 2002-280982 | Sep 2002 | JP |
| 2002-281483 | Sep 2002 | JP |
| 2002-330416 | Nov 2002 | JP |
| 2002-354449 | Dec 2002 | JP |
| 2003-111052 | Apr 2003 | JP |
| 2003-284041 | Oct 2003 | JP |
| 2004-536494 | Dec 2004 | JP |
| WO 9638961 | Dec 1996 | WO |
| WO 9831107 | Jul 1998 | WO |
| WO 9927741 | Jun 1999 | WO |
| WO 0028713 | May 2000 | WO |
| WO 0065775 | Nov 2000 | WO |
| WO 0065776 | Nov 2000 | WO |
| WO 0069101 | Nov 2000 | WO |
| WO 0069163 | Nov 2000 | WO |
| WO 0074373 | Dec 2000 | WO |
| WO 02088982 | Nov 2002 | WO |
| Entry |
|---|
| U.S. Appl. No. 13/549,205, filed Jul. 13, 2012, Weigand. |
| U.S. Appl. No. 14/702,505, filed May 1, 2015, Brown. |
| Keller et al., An Active Router Architecture for Multicast Video Distribution, St. Louis, Missouri, Dec. 2003. |
| Lockwood et al., Reprogrammable Network Packet Processing on the Field Programmable Port Extender (FPX), 2001, St. Louis Missouri. |
| Taylor et al., Dynamic Hardware Plugins (DHP): Exploitating Reconfigurable Hardware for High Performance Programmable Routers, 2002, St. Louis, Missouri. |
| Choi et al., Design of a Flexible Open Platform for High Performance Active Networks, 1999, St. Louis, Missouri. |
| PCT International Search Report, issued in PCT/US02/41769, Apr. 8, 2003, 6 pages. |
| International Search Report dated Jul. 2, 2003, (App No. PCT/US03/12086. |
| International Preliminary Examination Report (IPER), dated Feb. 24, 2004, App No. PCT/US02/13362. |
| F. Gong: Multipoint audio and video control for packet-based multimedia conferencing (1994), International Multimedia Conference, pp. 425-432, ISBN: 0-89791-686-7. |
| Chinese Office Action mailed Aug. 12, 2005 in Application No. 02810729.2. |
| Chinese Office Action mailed Nov. 2, 2007 in Application No. 02810729.2. |
| Chinese Office Action mailed May 30, 2008 in Application No. 02810729.2. |
| International Search Report dated Jul. 12, 2002, issued in PCT/US02/13363. |
| International Search Report dated Oct. 29, 2002, issued in PCT/US02/13362. |
| Office Action for Japanese Application 2002-586120 dated Apr. 10, 2008, 1 page. |
| Miyazaki, S., et al., “Stream Transmission Control Application Program Interface,” Technical Report of IEICE, vol. 100, No. 672, pp. 341-346, in Japanese with English-language Abstract and and English-language excerpt, 11 pages total. |
| Furht, B. et al., “IP Simulcast: A New Technique for Multimedia Broadcasting Over the Internet;” Cit. Journal of Computing and Information Technology, Zagreb, HR, vol. 6, No. 3, Sep. 1, 1998, pp. 245-254, XP000870379, ISSN: 1330-1136, *the whole document*. |
| ST2 Working Group L. Degrossi & L. Berger et al., “Internet Stream Protocol Version 2 (ST2) Protocol Specification—Version ST2+; rfc1819.txt” IETF Standard Internet Engineering Task Force, IETF, CH, Aug. 1, 1995, XP015007606 ISSN: 0000-0003, Chapter 1, p. 6-p. 19. |
| Examination Report for European Application No. 02734066.0, mailed Apr. 16, 2009. |
| Australian Office Action issued in 200205256 of Feb. 9, 2007. |
| Australian Office Action issued in 200205256 of May 26, 2008. |
| Canadian Intellectual Property Office, Office Action of Jan. 19, 2011, App No. 2,445,869 (3 pages). |
| Chinese Office Action issued in 02810728.4 on Feb. 29, 2008. |
| Chinese Office Action issued in 02810728.4 on Jul. 13, 2007. |
| Chinese Office Action issued in 02810728.4 on Jun. 23, 2006. |
| European Office Action issued EP 02725839.1 on Apr. 16, 2009, 5 pages. |
| Indian Office Action issued in 1764/DELNP/2003 on Apr. 16, 2008. |
| Office Action for Japanese Application 2002-586120 dated Oct. 10, 2008, 1 page. |
| Office Action for Japanese Application 2002-586120 dated Mar. 4, 2008, 1 page. |
| Supplemental European Search Report Issued in EP 02734066.0 on Jul. 31, 2006. |
| Oh-ishi, Tetsuya, et al. “Contents Delivery Function over Managed Network,” IEICE Technical Report, vol. 101, No. 120, Jun. 14, 2001. |
| Supplementary European Search Report issued in EP 02725839 on Nov. 18, 2008. |
| Chickering, David Maxwell et al. “Targeted advertising with inventory management.” Proceedings of the 2nd ACM conference on Electronic Commerce. Minneapolis, 2000. pp. 145-149. ACM Press. |
| Langheinrich, Marc et al. “Unintrusive Customization techniques for Web Advertising” Proceeding of the eighth international conference on World Wide Web. Computer Networks. Amsterdam, Netherlands, 1999. pp. 1259-1272. |
| Mobasher, Bamshad et al. “Effective Personalization based on Association Rule Discovery from Web Usage Data.” Proceedings of the 3rd International workshop on Web Information and Data Management. Atlanta, 2001. pp. 9-15. ACM Press. |
| Nakano, Tadashi et al. “User Adaptive Content Delivery Mechanism on the World Wide Web.” Proceedings of the 2002 ACM symposium on Applied Computing. Madrid, Spain. 2002. pp. 1140-1146. ACM Press. |
| Datta, Anindya et al. “An Architecture to support scalable online personalization on the web.” The VLDB Journal. vol. 10, Issue 1. Aug. 2001. Springer-Verlag New York. pp. 104-117. |
| Brassil, Jack et al “Enhancing Internet Streaming Media with Cueing Protocols.” Twentieth Annual Joint Conference of the IEEE Computer and Communications Societies. IEEE Press. 2001. vol. 1. 95-103. |
| McGrath, E. “Digital Insertion of Advertising into a Digital Stream.” Broadcasting Convention. 1997. 258-61. |
| International Search Report, PCT/US03/19774, dated Dec. 18, 2003. |
| International Search Report, PCT/US03/12873, dated Jul. 14, 2003. |
| Supplemental European Search Report, EP02725839, dated Nov. 24, 2008. |
| U.S. Appl. No. 09/893,692, Dec. 23, 2004, Office Action. |
| U.S. Appl. No. 09/893,692, Sep. 14, 2005, Notice of Allowance. |
| U.S. Appl. No. 09/893,692, Mar. 28, 2007, Notice of Allowance. |
| U.S. Appl. No. 10/090,727, May 10, 2005, Office Action. |
| U.S. Appl. No. 10/090,727, Jan. 3, 2007, Notice of Allowance. |
| U.S. Appl. No. 10/134,439, Jul. 25, 2005, Office Action. |
| U.S. Appl. No. 10/134,439, Jun. 12, 2006, Notice of Allowance. |
| U.S. Appl. No. 10/134,552, Oct. 11, 2005, Office Action. |
| U.S. Appl. No. 10/134,552, May 24, 2006, Office Action. |
| U.S. Appl. No. 10/134,552, Aug. 8, 2006, Office Action. |
| U.S. Appl. No. 10/134,552, Mar. 5, 2007, Office Action. |
| U.S. Appl. No. 10/134,552, Sep. 11, 2007, Office Action. |
| U.S. Appl. No. 10/134,552, Apr. 4, 2008, Notice of Allowance. |
| U.S. Appl. No. 10/157,909, Aug. 9, 2006, Office Action. |
| U.S. Appl. No. 10/157,909, Jan. 30, 2007, Notice of Allowance. |
| U.S. Appl. No. 10/157,909, May 25, 2007, Notice of Allowability. |
| U.S. Appl. No. 10/157,909, Jun. 8, 2007, Notice of Allowability. |
| U.S. Appl. No. 10/157,909, Sep. 10, 2007, Notice of Allowability. |
| U.S. Appl. No. 10/183,420, Dec. 13, 2005, Office Action. |
| U.S. Appl. No. 10/183,420, Jun. 22, 2006, Office Action. |
| U.S. Appl. No. 10/183,420, Dec. 12, 2006, Office Action. |
| U.S. Appl. No. 10/183,420, Jun. 28, 2007, Office Action. |
| U.S. Appl. No. 10/183,420, May 20, 2010 Office Action. |
| U.S. Appl. No. 10/183,420, Nov. 3, 2010, Office Action. |
| U.S. Appl. No. 10/183,420, Feb. 15, 2011 Office Action. |
| U.S. Appl. No. 10/183,420, Jun. 7, 2011, Notice of Allowance. |
| U.S. Appl. No. 11/549,934, Sep. 4, 2009, Office Action. |
| U.S. Appl. No. 11/549,934, Apr. 28, 2010, Office Action. |
| U.S. Appl. No. 11/549,934, Nov. 29, 2010, Notice of Allowance. |
| U.S. Appl. No. 11/754,661, Jun. 19, 2009, Office Action. |
| U.S. Appl. No. 11/754,661, Nov. 18, 2009, Notice of Allowance. |
| U.S. Appl. No. 11/761,050, Jul. 27, 2009, Office Action. |
| U.S. Appl. No. 11/761,050, Feb. 3, 2010, Office Action. |
| U.S. Appl. No. 11/761,050, Jul. 6, 2011, Notice of Allowance. |
| U.S. Appl. No. 11/761,050, Oct. 21, 2011, Notice of Allowance. |
| U.S. Appl. No. 11/848,430, Aug. 8, 2011, Office Action. |
| U.S. Appl. No. 11/848,430, Jun. 21, 2012, Notice of Allowance. |
| U.S. Appl. No. 11/848,430, May 9, 2013, Notice of Allowance. |
| U.S. Appl. No. 11/848,430, Aug. 19, 2013, Notice of Allowance. |
| U.S. Appl. No. 12/732,929, Oct. 7, 2010, Office Action. |
| U.S. Appl. No. 12/732,929, Mar. 18, 2011, Notice of Allowance. |
| U.S. Appl. No. 13/053,903, Nov. 28, 2012, Office Action. |
| U.S. Appl. No. 13/053,903, Apr. 15, 2013, Notice of Allowance. |
| U.S. Appl. No. 13/173,290, Jan. 3, 2012, Office Action. |
| U.S. Appl. No. 13/173,290, Mar. 16, 2012, Notice of Allowance. |
| U.S. Appl. No. 13/227,402, Feb. 10, 2012, Office Action. |
| U.S. Appl. No. 13/227,402, Aug. 29, 2012, Office Action. |
| U.S. Appl. No. 13/227,402, Jun. 13, 2013, Office Action. |
| U.S. Appl. No. 13/227,402, Oct. 28, 2013, Office Action. |
| U.S. Appl. No. 13/227,402, Feb. 10, 2014, Notice of Allowance. |
| U.S. Appl. No. 13/612,834, Apr. 28, 2014, Office Action. |
| U.S. Appl. No. 13/620,547, Aug. 7, 2013, Office Action. |
| U.S. Appl. No. 13/620,547, Nov. 15, 2013, Office Action. |
| U.S. Appl. No. 13/620,547, Apr. 11, 2014, Notice of Allowance. |
| U.S. Appl. No. 13/620,816, Jul. 17, 2013, Office Action. |
| U.S. Appl. No. 13/620,816, Jan. 13, 2014, Office Action. |
| U.S. Appl. No. 13/620,816, May 8, 2014, Office Action. |
| U.S. Appl. No. 13/620,816, Jul. 28, 2014, Notice of Allowance. |
| U.S. Appl. No. 13/620,820, Sep. 12, 2013, Office Action. |
| U.S. Appl. No. 13/620,820, May 7, 2014, Office Action. |
| U.S. Appl. No. 13/620,820, Oct. 10, 2014, Office Action. |
| U.S. Appl. No. 13/620,820, Mar. 3, 2015, Notice of Allowance. |
| U.S. Appl. No. 13/620,906, Aug. 15, 2013, Office Action. |
| U.S. Appl. No. 13/620,906, Feb. 21, 2014, Notice of Allowance. |
| U.S. Appl. No. 13/620,818, Jul. 19, 2013, Office Action. |
| U.S. Appl. No. 13/621,041, Feb. 5, 2014, Office Action. |
| U.S. Appl. No. 14/319,815, Jul. 13, 2015, Office Action. |
| U.S. Appl. No. 14/327,265, Sep. 1, 2015, Office Action. |
| U.S. Appl. No. 14/327,265, Mar. 4, 2016, Office Action. |
| Furht, B. et al., “IP Simulcast: A New Technique for Multimedia Broadcasting Over the Internet;” Cit. Journal of Computing and Information Technology, Zagreb, HR, vol. 6, No. 3, Sep. 1, 1998 (Sep. 1, 1998), pp. 245-254, XP000870379, ISSN: 1330-1136, *the whole document*. |
| ST2 Working Group L. Degrossi & L. Berger et al., “Internet Stream Protocol Version 2 (ST2) Protocol Specification—Version ST2+; rfc1819.txt” IETF Standard Internet Engineering Task Force, IETF, CH, Aug. 1, 1995 (Aug. 1, 1995), XP015007606 ISSN: 0000-0003, Chapter 1, *p. 6-p. 19.*. |
| U.S. Appl. No. 10/183,420, May 20, 2010, Office Action. |
| U.S. Appl. No. 10/183,420, Feb. 15, 2011, Office Action. |
| U.S. Appl. No. 13/620,816, Jul. 17, 2013 Office Action. |
| U.S. Appl. No. 14/327,265, Aug. 4, 2016, Office Action. |
| U.S. Appl. No. 14/702,505, Sep. 6, 2016, Notice of Allowance. |
| Number | Date | Country | |
|---|---|---|---|
| 20150222687 A1 | Aug 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60343182 | Dec 2001 | US | |
| 60286964 | Apr 2001 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13620820 | Sep 2012 | US |
| Child | 14688858 | US | |
| Parent | 13053903 | Mar 2011 | US |
| Child | 13620820 | US | |
| Parent | 11549934 | Oct 2006 | US |
| Child | 13053903 | US | |
| Parent | 10134439 | Apr 2002 | US |
| Child | 11549934 | US |
