Patent Grant
7990410
1. Field of the Invention
The present invention relates to videoconferencing systems.
2. Description of the Related Art
Videoconferencing systems allow people at two or more different locations to participate in a conference so that the people at each location can see and hear the people at the other location(s). Videoconferencing systems typically perform digital compression of audio and video signals in real time. The hardware or software that performs compression is called a codec (coder/decoder). The resulting digital stream of bits representing the audio and video data are subdivided into packets, which are then transmitted through a network of some kind (usually ISDN or IP) to the other locations or endpoints participating in the videoconference.
Videoconferences can be performed using dedicated videoconferencing equipment, i.e., devices especially designed for videoconferencing. For example, a dedicated videoconferencing device may include input ports for receiving video signals from local video sources and audio signals from local microphones, network ports for receiving the remote audio/video streams from and sending the local audio/video stream to the remote endpoints, and output ports for displaying the video data on a display device and sending the audio data to an audio output device. The dedicated videoconferencing device may also include specialized software and hardware for compressing and decompressing audiovisual data, generating a composite image of the video streams from the various participants, etc. The dedicated videoconferencing device may also include an interface allowing users to interact with the videoconferencing equipment, e.g., to pan, tilt, and zoom cameras, select a video input source to send to the remote endpoints, control volume levels, control placement of video windows on the display device, etc.
Videoconferences can also be performed using non-dedicated equipment, e.g., a general purpose computer system. For example, a typical desktop PC can be configured to add-on hardware boards and/or software to enable the PC to participate in a videoconference.
Various standards have been established to enable the videoconferencing systems at each endpoint to communicate with each other. In particular, the International Telecommunications Union (ITU) has specified various videoconferencing standards. These standards include:
H.320—This is known as the standard for public switched telephone networks (PSTN) or videoconferencing over integrated services digital networks (ISDN) basic rate interface (BRI) or primary rate interface (PRI). H.320 is also used on dedicated networks such as TI and satellite-based networks.
H.323—This is known as the standard for video over Internet Protocol (IP). This same standard also applies to voice over IP (VoIP).
H.324—This is the standard for transmission over POTS (Plain Old Telephone Service), or audio telephony networks.
In recent years, IP-based videoconferencing has emerged as a communications interface and standard commonly utilized by videoconferencing equipment manufacturers. Due to the price point and proliferation of the Internet, and broadband in particular, there has been strong growth and use of H.323 IP-based videoconferencing. H.323 has the advantage that it is accessible to anyone with a high speed Internet connection, such as a DSL connection, cable modem connection, or other high speed connection.
A videoconference may include a plurality of endpoints that share video signals among each other. At a given endpoint, there may be a display device that displays the video signals from the various endpoints. For example, a videoconferencing device at a given endpoint may receive a plurality of remote video signals from a plurality of remote endpoints and display the remote video signals simultaneously with each other on a display device, e.g., to form a continuous presence display. As another example, a videoconferencing device at a given endpoint may receive one or more remote video signals from one or more remote endpoints and display the one or more remote video signals simultaneously with a local video signal from a local video source (e.g., a video source at the local endpoint) to form a continuous presence display.
Various embodiments of a method for visually indicating status information on a continuous presence display in a videoconferencing system are described herein. The method may comprise receiving status information from one or more of the endpoints of the videoconference and displaying one or more status icons on the display device in response to the status information. Each status icon may correspond to a respective one of the endpoints and may have a graphical appearance that graphically indicates the status information received from the respective endpoint. Each status icon may also be displayed proximally to the displayed video signal of the respective endpoint to which it corresponds. Displaying each status icon proximally to the displayed video signal of the respective endpoint to which it corresponds may visually associate the status icons with their corresponding endpoints. This may allow the participants in the video conference to easily learn the status information for the various endpoints in the videoconference simply by looking at the various status icons displayed proximally to the respective video signals displayed on the continuous presence display.
Also described herein are various embodiments of a method for visually indicating control of an endpoint in the videoconference. For example, the videoconferencing device at a given endpoint may receive user input selecting a particular endpoint as an endpoint to control, e.g., in order to control one or more properties of the endpoint. As one example, the user (e.g., operator of the videoconferencing device) may select an endpoint in order to control various properties of a camera at the endpoint. In response to the user selecting the endpoint, the videoconferencing device may display a control icon on the continuous presence display, where the control icon is displayed proximally to the video signal of the selected endpoint. The control icon may have a graphical appearance that graphically indicates that the endpoint is currently selected for controlling one or more of its properties. The control icon displayed proximally to the video signal of the selected endpoint may serve as a visual indicator to the operator of the videoconferencing device that that particular endpoint is currently selected for control.
Various embodiments of a videoconferencing system which utilizes the aforementioned methods are also described herein.
A better understanding of the present invention may be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.
Incorporation by Reference
U.S. Provisional Patent Application Ser. No. 60/676,918, titled “Audio and Video Conferencing”, which was filed May 2, 2005, whose inventors were Michael L. Kenoyer, Wayne Mock, and Patrick D. Vanderwilt, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. patent application Ser. No. 11/252,238, titled “Video Conferencing System Transcoder”, which was filed Oct. 17, 2005, whose inventors were Michael L. Kenoyer and Michael V. Jenkins, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. patent application Ser. No. 11/251,084, titled “Speakerphone”, which was filed Oct. 14, 2005, whose inventor was William V. Oxford, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. patent application Ser. No. 11/251,086, titled “Speakerphone Supporting Video and Audio Features”, which was filed Oct. 14, 2005, whose inventors were Michael L. Kenoyer, Craig B. Malloy and Wayne E. Mock, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. patent application Ser. No. 11/251,083, titled “High Definition Camera Pan Tilt Mechanism”, which was filed Oct. 14, 2005, whose inventors were Michael L. Kenoyer, William V. Oxford, Patrick D. Vanderwilt, Hans-Christoph Haenlein, Branko Lukic and Jonathan I. Kaplan, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
As described in more detail below, a videoconference may include a plurality of endpoints that share video signals among each other. At a given endpoint, there may be a display device that displays the video signals from the various endpoints. As used herein, the term “continuous presence display” refers to simultaneously displaying video signals from multiple endpoints in a videoconference on a display screen of a display device. For example, a videoconferencing device at a given endpoint may receive a plurality of remote video signals from a plurality of remote endpoints and display the remote video signals simultaneously with each other on a display device to form a continuous presence display. As another example, a videoconferencing device at a given endpoint may receive one or more remote video signals from one or more remote endpoints and display one or more remote video signals simultaneously with a local video signal from a local video source (e.g., a video source at the local endpoint) to form a continuous presence display.
Various embodiments of a method for visually indicating status information on a continuous presence display in a videoconferencing system are described herein. As described in more detail below, the method may comprise receiving status information from one or more of the endpoints of the videoconference and displaying one or more status icons on the display device in response to the status information. Each status icon may correspond to a respective one of the endpoints and may have a graphical appearance that graphically indicates the status information received from the respective endpoint. Each status icon may also be displayed proximally to the displayed video signal of the respective endpoint to which it corresponds. Displaying each status icon proximally to the displayed video signal of the respective endpoint to which it corresponds may visually associate the status icons with their corresponding endpoints. This may allow the participants in the video conference to easily learn the status information for the various endpoints in the videoconference simply by looking at the various status icons displayed proximally to the respective video signals displayed on the continuous presence display.
Also described herein are various embodiments of a method for visually indicating control of an endpoint in the videoconference. For example, the videoconferencing device at a given endpoint may receive user input selecting a particular endpoint as an endpoint to control, e.g., in order to control one or more properties of the endpoint. As one example, the user (e.g., operator of the videoconferencing device) may select an endpoint in order to control various properties of a camera at the endpoint. In response to the user selecting the endpoint, the videoconferencing device may display a control icon on the continuous presence display, where the control icon is displayed proximally to the video signal of the selected endpoint. The control icon may have a graphical appearance that graphically indicates that the endpoint is currently selected for controlling one or more of its properties. The control icon displayed proximally to the video signal of the selected endpoint may serve as a visual indicator to the operator of the videoconferencing device that that particular endpoint is currently selected for control.
Various embodiments of a videoconferencing system which utilizes the aforementioned methods are also described herein.
Referring now to
The various locations of the videoconference participants are also referred to herein as “endpoints” in the videoconference. For example,
Although there are five endpoints 101 in this example, in other examples there may be any number of endpoints (as long as there are at least two). Also, the participants 80 at a given endpoint 101 may include any number of people. In one embodiment, each endpoint 101 includes at least one person as a participant 80. In other embodiments, one or more of the endpoints 101 may have no persons present as participants 80. For example, video information from a camera stationed at an endpoint 101A with no participants 80 may be sent to other endpoints 101 and viewed by participants 80 at the other endpoints 101, where the other endpoints 101 also share video information among each other.
In one embodiment, each endpoint 101 may send video information to all of the remote endpoints 101. In another embodiment, one or more of the endpoints may send video information to only a subset, but not all, of the remote endpoints. As one example, endpoints 101B-101E may each send video information only to endpoint 101A, and endpoint 101A may send video information to each of the endpoints 101B-101E. As described below, in some embodiments, each endpoint 101 may send video information to a device referred to as a Multipoint Control Unit (MCU). The MCU may then relay the received video information to the various endpoints 101. The MCU may be located at one of the endpoints 101 or may be in a separate location from any of the endpoints 101.
In another embodiment, one or more of the endpoints 101 may not send video information to any remote endpoint. As one example, a given endpoint 101 may receive video information from one or more of the remote endpoints, but may not send video information to any remote endpoint. As another example, a given endpoint 101 may not send video information to any remote endpoint or receive video information from any remote endpoint. In this example, the given endpoint 101 may participate in the videoconference by sharing audio information only, e.g., may receive audio information from one or more of the remote endpoints, as well as possibly sending audio information to one or more of the remote endpoints.
As noted above, in addition to sharing video information, the endpoints 101 may also share audio information. In one embodiment, each endpoint 101 that sends video information to one or more remote endpoints may also send audio information to the one or more remote endpoints 101. In one embodiment, each endpoint 101 may receive both video information and audio information from all of the other endpoints 101. In another embodiment, one or more of the endpoints 101 may send video information to one or more remote endpoints, but without sending audio information to the one or more remote endpoints. In another embodiment, one or more of the endpoints 101 may send audio information to one or more remote endpoints, but without sending video information to the one or more remote endpoints.
It will be appreciated that many other possible permutations of sending video and/or audio information among the various endpoints 101 in the videoconference are possible, other than the particular ones described above.
As noted above, in some embodiments, a device referred to as a Multipoint Control Unit (MCU) may be used to facilitate sharing video and audio information among the endpoints 101. The MCU may act as a bridge that interconnects calls from several endpoints. For example, all endpoints may call the MCU, or the MCU can also call the endpoints which are going to participate in the videoconference. An MCU may be located at one of the endpoints 101 of the videoconference or may be in a separate location from any endpoint 101. In one embodiment, the MCU may be embedded in a videoconferencing device at one of the endpoints 101.
At least one of the endpoints 101 in
As shown, the videoconferencing system 119 includes a videoconferencing device 120. As used herein, the term “videoconferencing device” refers to a device operable to receive video information from and send video information to remote endpoints in a videoconference. A videoconferencing device may also receive audio information from and send audio information to the remote endpoints.
In the example of
The videoconferencing device 120 may be operable to select one (or more) of the video input signals received from the video sources 130 as a video input signal to send to one or more of the remote endpoints in the videoconference: Thus, the video sources 130 are also referred to herein as “local video sources” and the respective video input signals that they produce are also referred to herein as “local video signals”. It is noted, however, that the local video sources may or may not be located physically together with or proximally to the videoconferencing device 120. For example, in one embodiment, one or more of the local video sources 130 may be located far away from the videoconferencing device 120 and may connect to the videoconferencing device 120 to provide a video input signal via a network. Thus, the video sources 130 are “local” in the sense of providing video input signals for possible selection for sending from the local endpoint 101 to the remote endpoints 101, but may or may not be local in the sense of physical location.
The local video input signal that is currently selected to be sent to the remote endpoints is also referred to herein as the “selected local video input signal” or simply the “selected video signal”. In some embodiments, the videoconferencing device 120 may be operable to send more than one local video input signal to the remote endpoints, and thus, there may be multiple selected video signals.
As shown, the videoconferencing device 120 may be coupled to the network 105. The videoconferencing device 120 may send the selected local video input signal to the remote endpoints 101 via the network 105. The videoconferencing device 120 may also receive video signals from the remote endpoints 101 via the network 105. The video signals received from the remote endpoints 101 are also referred to herein as “remote video signals”.
As used herein, the term “video signal” or “video input signal” refers to any kind of information useable to display video and does not imply that the information is in any particular form or encoded in any particular way. For example, in various embodiments, the local video signal from a local video source may be sent from an endpoint 101 to the remote endpoints 101 in any form and using any of various communication protocols or standards. In a typical embodiment, the local video signal is sent to the remote endpoints 101 as digital information, e.g., as ordered packets of information. Similarly, the remote video signals may be received over the network 105 in a digital form; e.g., as ordered packets of information.
Thus, if the local video source originally produces an analog signal, then the signal may be converted into digital information, or if the local video source originally produces a digital signal, the signal may be encoded in a different way or packetized in various ways. Thus, the video information that originates from a given video source 130 may be encoded, decoded, or converted into other forms at various stages between leaving the video source and arriving at the remote endpoints, possibly multiple times. The term “video signal” is intended to encompass the video information in all of its various forms.
Referring again to
The videoconferencing device 120 may be operable to display the remote video signals from the remote endpoints on the display device 122. The videoconferencing device 120 may also display one or more of the local video signals on the display device 122, e.g., may display the selected local video signal. As described above, the various video signals may be displayed together with each other as a continuous presence display. For example, the videoconferencing device 120 may include hardware logic which receives the remote video signals and the selected local video signal and creates a composite image which is then provided to the display device 122, e.g., so that the various video signals are tiled or displayed in different respective windows on the display device 122.
In some embodiments the videoconferencing device 120 may be operable to display a graphical user interface (GUI) on the display device 122, where the user (operator of the videoconferencing device 120) can interact with the GUI in order to provide input to the videoconferencing device 120, e.g., similar to the manner in which users commonly provide input to on-screen television displays in order to set various options or perform various functions. For example, the user may operate the remote control device 128 or other input device, such as a keyboard or buttons on the videoconferencing device 120 chassis, in order to request the videoconferencing device 120 to perform a particular operation. In response, the videoconferencing device 120 may display various GUI elements on the display device 122, e.g., where the GUI elements indicate various options or functions related to the requested operation. The user may then scroll to and select a desired GUI element.
In some embodiments the videoconferencing system 119 may include multiple display devices 122. The videoconferencing device 120 may be configured to distribute the various video signals across the multiple display devices 122 in any of various ways.
As shown, the videoconferencing device 120 may also couple to one or more audio devices 124. For example, the audio device(s) 124 may include one or more microphones or other audio input devices for providing local audio input to be sent to the remote endpoints 101, as well as one or more speakers or other audio output devices for audibly projecting audio information received from the remote endpoints 101.
Referring now to
In 301, video signals may be received from multiple endpoints of the videoconference, e.g., may be received by a videoconferencing device 120 at a local endpoint 101. The video signals may comprise remote video signals received from remote endpoints 101 and/or one or more local video signals received from local video sources at the local endpoint 101. The received video signals preferably include at least one remote video signal received from a remote endpoint 101.
In 303, the video signals may be displayed simultaneously (displayed together with each other) on the display device 122. For example, the videoconferencing device 120 may form a composite image of the received video signals and display them together with each other as a continuous presence display, as described above.
As indicated in 305, status information may be received from one or more of the endpoints 101. In one embodiment, status information may be received from each of the endpoints. In other embodiments, status information may be received from a subset, but not all, of the endpoints. For example, some of the videoconferencing devices at remote endpoints 101 may be operable to send status information and others may not.
The status information received from a given endpoint may indicate a current state of one or more variable properties of the endpoint. In various embodiments the status information may include information regarding any of various kinds of variable properties of the endpoint. For example, in one embodiment an endpoint may be operable to mute its audio, e.g., so that audio information from that endpoint is not sent to other endpoints in the videoconference while the audio is muted. In this example, the status information from the endpoint may indicate the mute state of the endpoint, e.g., may indicate whether the audio of the endpoint is currently muted. The status information may also or may alternatively include information regarding various other audio properties of the endpoint, such as a current volume level.
The state information from a given endpoint may also or may alternatively include information regarding variable properties of the endpoint other than audio properties. For example, in some embodiments, the state information may indicate current states of one or more video properties of the endpoint. As one example, the state information may indicate a current video source at the endpoint, e.g., may indicate which video source or what kind of video source is producing the video signal received from that endpoint. As another example, the state information may indicate states of various properties of a camera at the endpoint. For example, the state information may indicate a zoom value of the camera (e.g., how much the camera is zoomed in or zoomed out), a panning value of the camera (e.g., how far the camera is panned to the left or right), a tilt value of the camera (e.g., how far the camera is tilted up or down), etc.
In various embodiments, the status information and the video signals may be received using any of various communication protocols. In some embodiments, the status information from a given endpoint may be received together with the video signal from the endpoint. In other embodiments the status information may be received separately from the video signal, e.g., as a separate communication.
Referring again to
Displaying a status icon proximally to the displayed video signal of the respective endpoint to which it corresponds may comprise displaying the status icon on or near the video signal. For example, where the video signal is displayed in a window or screen portion on the continuous presence display, the status icon may be displayed in or next to the window or screen portion.
Displaying the one or more status icons proximally to the displayed video signals of the respective endpoints may visually associate the status icons with their corresponding endpoints. This may allow the participants in the video conference to easily learn the status information for the various endpoints in the videoconference simply by looking at the various status icons displayed proximally to the video signals displayed on the continuous presence display.
As used herein, the term “icon” refers to information comprising graphical or pictorial information. As noted above, each status icon preferably has a graphical appearance that graphically indicates at least a portion of the status information received from the respective endpoint. As one example, where the status information from a given endpoint indicates that audio is muted at the endpoint, a status icon may graphically indicate that the audio is muted. For example, the icon may comprise a picture of a speaker or microphone with a line crossed through it to indicate that the audio is muted. In one embodiment, a status icon may also include textual information in addition to graphical information. For example, in the above example of muted audio, the status icon may include the word “Mute” in addition to the graphical information.
In the preferred embodiment, each status icon has a small size, e.g., takes up only a small portion of the display screen. For example, each status icon may be substantially smaller than the video signal with which it is associated. Displaying the status icons at a small size may enable the status information to be visually presented without distracting viewers from the video signals displayed on the continuous presence display.
Referring now to
In 351, video signals may be received from multiple endpoints of the videoconference, e.g., may be received by a videoconferencing device 120 at a local endpoint 101, similarly as described above with reference to 301 of
In 351, the video signals may be displayed simultaneously on a display device 122, e.g., to form a continuous presence display, similarly as described above with reference to 303 of
In 355, user input selecting an endpoint to control may be received. For example, a user (e.g., operator of the videoconferencing device 120) may desire to control one or more properties of a particular endpoint. The videoconferencing device 120 may enable the user to select the endpoint using any of various techniques, such as by operating a remote control device 128, a keyboard, buttons located on the videoconferencing device 120 chassis, or any of various other kinds of input devices.
In various embodiments, the user may select the endpoint in order to control any of various kinds of properties of the endpoint. For example, the endpoint may be selected in order to control various properties of a camera at the endpoint, such as panning, tilting, zooming, etc. As another example, the endpoint may be selected in order to select a video source for the endpoint, e.g., in order to control which video signal from the endpoint is sent to other endpoints in the videoconference. As another example, the endpoint may be selected in order to control various audio properties for the endpoint, such as a volume level or mute state.
In response to the user selecting the endpoint to control, the videoconferencing device 120 may display a control icon proximally to the displayed video signal of the selected endpoint. The control icon may have a graphical appearance that graphically indicates that the endpoint is selected for controlling the one or more properties of the endpoint. The control icon displayed proximally to the video signal of the selected endpoint may serve as a visual indicator to the operator of the videoconferencing device that that particular endpoint is currently selected for control.
In
In
It is noted that in some embodiments the videoconferencing device 120 may be operable to display both status icons and control icons. For example,
The display screen also indicates other information regarding the remote endpoint, such as a name of the remote endpoint (“Mock01”) and an IP address of the remote endpoint (“10.10.11.159”).
In this example, a control icon is shown in the window of the local video signal, which indicates that the local endpoint is currently selected for controlling its video properties.
In
In
In various embodiments, the methods of
The videoconferencing device 120 of
The videoconferencing device 120 also includes a processor 404 coupled to a memory 406. The memory 406 may be configured to store program instructions and/or data: In particular, the memory 406 may store operating system (OS) software 409, driver software 408, and application software 410. In one embodiment, the memory 406 may include one or more forms of random access memory (RAM) such as dynamic RAM (DRAM) or synchronous DRAM (SDRAM). However, in other embodiments, the memory 406 may include any other type of memory instead or in addition.
It is noted that the processor 404 is representative of any type of processor. For example, in one embodiment, the processor 404 may be compatible with the x86 architecture, while in another embodiment the processor 404 may be compatible with the SPARC™ family of processors. Also, in one embodiment the videoconferencing device 120 may include multiple processors 404.
The processor 404 may be configured to execute the software and to operate on data stored within the memory 406. The application software 410 may interface with the driver software 408 in order to communicate with or control the FPGA hardware 402 in various ways.
In particular, the application software 410 may communicate with the FPGA hardware 402 via the driver software 408 in order to control how the FPGA hardware 402 creates the composite image from the local and remote video signals. For example, suppose that in a videoconference between the local endpoint 101 and a remote endpoint 101, the videoconferencing device 120 displays a composite image of a local video signal and a remote video signal, where the two video signals are displayed in different windows on the display device. The application software 410 may control where to display the windows on the display device in relation to each other, how large to make each window, etc.
The application software 410 may also cause the display of a graphical user interface (GUI), e.g., where various GUI elements are superimposed over the displayed video signals in the composite image. For example, the GUI may comprise GUI elements for receiving user input and/or GUI elements for displaying information to the user. In particular, the application software 410 may cause status and/or control icons to be displayed on the display screen, as described above.
Referring now to
As shown, the input FPGA 720 includes a pool of scalers 503. One or more of the input streams may be sent to the scalers 503 in order to change its resolution, e.g., to scale the resolution up or down. As one example, in one embodiment the S-video input streams may be scaled up to a higher resolution, e.g., so that they can be displayed at a larger size on the display screen. As another example, the HB1 and HB2 primary camera input streams, which may be high definition video, may be scaled down by the scalers 502, e.g., in order to be sent to an S-video output (e.g., for output to a VCR).
After possibly being scaled up or down, the input streams may be serialized by the HS Serial TX module 540 and sent to the output FPGA 730.
In the illustrated embodiment, the output FPGA 730 includes a memory-based (MB) scaler 593, which is operable to scale down the input streams for display as thumbnail images in the composite image. The DDR-to-Stream DMA module 562 may read the input streams from DDR memory 555b and feed them to the MB scaler 593. The MB scaler 593 may scale down the input streams to a low resolution for display as thumbnail images, e.g., where the thumbnail images are displayed at a relatively small size with respect to the size of the display device screen.
The MB scaler 593 provides the scaled-down input streams to the DDR-to-Stream DMA module 562. Each of the scaled-down input streams may be written by the DDR-to-Stream DMA module 562 to a different location in the DDR memory 555b than the original input stream.
One or more composite images may be created from the input streams received from the input FPGA 720 and/or from the scaled-down input streams created by the MB scaler 593. For example, the output FPGA 730 may be operable to provide composite images on various outputs, such as the outputs 580, 582, 584, and 586. Each output may be coupled to a respective compositor 509, which receives one or more of the input streams from the DDR memory 555b and creates a composite image suitable for the output type. For example, the compositor 509b may provide a composite image at S-video resolution on output 584 to an S-video output device, such as a DVD player or VCR.
In one embodiment, one or more of the composite images may be sent over a network, e.g., to videoconferencing devices at remote endpoints. For example, outputs 586A-C are coupled to video encoders 553. As illustrated in
The compositors 509 may be configured by the application software 410. In other words, the application software 410 may control which input streams are included in each of the composite images, where the respective input streams are placed within the composite image, etc.
As described above, the application software 410 may communicate with the FPGA hardware through driver software 408. For example, there may be a driver for the input FPGA 720 and another driver for the output FPGA 730.
In one embodiment, the application software 410 may control memory management for the various input streams. For example, the application software 410 may control where the Stream-to-DDR DMA module 560 writes each stream in the DDR memory 555b, may control which memory locations the compositors 509 read the streams from, etc.
The input FPGA 720 and the output FPGA 730 may both be coupled to a bus, such as PCI bus 530, which enables them to communicate with the processor 404, e.g., to receive instructions from the application software 410 through the driver software 408 as described above.
It is noted that various embodiments may further include receiving, sending or storing instructions and/or data implemented in accordance with the foregoing description upon a computer-readable memory medium. Generally speaking, a computer-readable memory medium may include storage media or memory media such as magnetic or optical media, e.g., disk or CD-ROM, volatile or non-volatile media such as RAM (e.g. SDRAM, DDR SDRAM, RDRAM, SRAM, etc.), ROM, etc. for storing program instructions. Such a computer-readable memory medium may store program instructions received from or sent on any transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link.
Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
This application claims priority to U.S. Provisional Patent Application Ser. No. 60/676,918, titled “Audio and Video Conferencing”, which was filed May 2, 2005, whose inventors were Michael L. Kenoyer, Wayne Mock, and Patrick D. Vanderwilt, and which is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5398309 | Atkins et al. | Mar 1995 | A |
| 5453780 | Chen et al. | Sep 1995 | A |
| 5528740 | Hill et al. | Jun 1996 | A |
| 5534914 | Flohr et al. | Jul 1996 | A |
| 5537440 | Eyuboglu et al. | Jul 1996 | A |
| 5572248 | Allen et al. | Nov 1996 | A |
| 5594859 | Palmer et al. | Jan 1997 | A |
| 5600646 | Polomski | Feb 1997 | A |
| 5617539 | Ludwig et al. | Apr 1997 | A |
| 5625410 | Washino et al. | Apr 1997 | A |
| 5629736 | Haskell et al. | May 1997 | A |
| 5640543 | Farrell et al. | Jun 1997 | A |
| 5649055 | Gupta et al. | Jul 1997 | A |
| 5657096 | Lukacs | Aug 1997 | A |
| 5684527 | Terui et al. | Nov 1997 | A |
| 5689641 | Ludwig et al. | Nov 1997 | A |
| 5719951 | Shackleton et al. | Feb 1998 | A |
| 5737011 | Lukacs | Apr 1998 | A |
| 5745161 | Ito | Apr 1998 | A |
| 5751338 | Ludwig, Jr. | May 1998 | A |
| 5764277 | Loui et al. | Jun 1998 | A |
| 5767897 | Howell | Jun 1998 | A |
| 5812789 | Diaz et al. | Sep 1998 | A |
| 5821986 | Yuan et al. | Oct 1998 | A |
| 5831666 | Palmer et al. | Nov 1998 | A |
| 5838664 | Polomski | Nov 1998 | A |
| 5859979 | Tung et al. | Jan 1999 | A |
| 5870146 | Zhu | Feb 1999 | A |
| 5896128 | Boyer | Apr 1999 | A |
| 5914940 | Fukuoka et al. | Jun 1999 | A |
| 5995608 | Detampel, Jr. et al. | Nov 1999 | A |
| 6038532 | Kane et al. | Mar 2000 | A |
| 6043844 | Bist et al. | Mar 2000 | A |
| 6049694 | Kassatly | Apr 2000 | A |
| 6078350 | Davis | Jun 2000 | A |
| 6101480 | Conmy et al. | Aug 2000 | A |
| 6122668 | Teng et al. | Sep 2000 | A |
| 6243129 | Deierling | Jun 2001 | B1 |
| 6285661 | Zhu et al. | Sep 2001 | B1 |
| 6288740 | Lai et al. | Sep 2001 | B1 |
| 6292204 | Carleton et al. | Sep 2001 | B1 |
| 6300973 | Feder et al. | Oct 2001 | B1 |
| 6373517 | Davis et al. | Apr 2002 | B1 |
| 6453285 | Anderson et al. | Sep 2002 | B1 |
| 6480823 | Zhao et al. | Nov 2002 | B1 |
| 6496216 | Feder et al. | Dec 2002 | B2 |
| 6526099 | Christopoulos et al. | Feb 2003 | B1 |
| 6535604 | Provencal et al. | Mar 2003 | B1 |
| 6564380 | Murphy | May 2003 | B1 |
| 6594688 | Ludwig et al. | Jul 2003 | B2 |
| 6603501 | Parry et al. | Aug 2003 | B1 |
| 6646997 | Baxley et al. | Nov 2003 | B1 |
| 6654045 | Allen et al. | Nov 2003 | B2 |
| 6657975 | Baxley et al. | Dec 2003 | B1 |
| 6728221 | Shaffer et al. | Apr 2004 | B1 |
| 6744460 | Nimri et al. | Jun 2004 | B1 |
| 6757005 | Elbaz et al. | Jun 2004 | B1 |
| 6760415 | Beecroft | Jul 2004 | B2 |
| 6816904 | Ludwig et al. | Nov 2004 | B1 |
| 7089285 | Drell | Aug 2006 | B1 |
| 7185054 | Ludwig et al. | Feb 2007 | B1 |
| 7304985 | Sojka et al. | Dec 2007 | B2 |
| 7574472 | Biby et al. | Aug 2009 | B2 |
| 20020188731 | Potekhin et al. | Dec 2002 | A1 |
| 20030067908 | Mattaway et al. | Apr 2003 | A1 |
| 20030105820 | Haims et al. | Jun 2003 | A1 |
| 20030174146 | Kenoyer | Sep 2003 | A1 |
| 20040183897 | Kenoyer et al. | Sep 2004 | A1 |
| 20060013416 | Truong et al. | Jan 2006 | A1 |
| 20060147009 | Greenlee et al. | Jul 2006 | A1 |
| 20070086445 | Mattaway et al. | Apr 2007 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20060256188 A1 | Nov 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60676918 | May 2005 | US |
