# Patent

## Title
Video conferencing system which allows endpoints to perform continuous presence layout selection

## Abstract

In various embodiments, a Multipoint Control Unit (MCU) or another video conferencing device (e.g., an endpoint) may generate a video frame that includes video images of two or more video conferencing endpoints. The video frame may then be sent to another video conferencing device that may receive the video frame and separate the two or more video images into separate video images. In some embodiments, the video frame may be separated into its separate images using, for example, metadata sent along with the video frame. The metadata may include video image identifiers and location information (e.g., coordinates in the video frame) of the video images. In some embodiments, the separated video images may be provided to a compositor that may composite the separated video images, for example, into a new layout.

## Background
PRIORITY
This application claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 60/945,723 titled “Virtual Decoders”, filed on Jun. 22, 2007, whose inventors are Keith C. King and Wayne E. Mock, which is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
This application also claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 60/945,734 titled “Videoconferencing Device which Performs Multi-way Conferencing”, filed on Jun. 22, 2007, whose inventors are Keith C. King and Wayne E. Mock, which is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
This application also claims the benefit of priority of U.S. Provisional Patent Application titled “Virtual Multiway Scaler Compensation”, Ser. No. 60/949,674, which was filed Jul. 13, 2007, whose inventors are Keith C. King and Wayne E. Mock, which is hereby incorporated by reference in its entirety as though fully and completely set forth herein.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates generally to conferencing and, more specifically, to video conferencing.
2. Description of the Related Art
Video conferencing may be used to allow two or more participants at remote locations to communicate using both video and audio. Each participant location may include a video conferencing endpoint for video/audio communication with other participants. Each video conferencing endpoint may include a camera and microphone to collect video and audio from a first or local participant to send to another (remote) participant. Each video conferencing endpoint may also include a display and speaker to reproduce video and audio received from a remote participant. Each video conferencing endpoint may also be coupled to a computer system to allow additional functionality into the video conference. For example, additional functionality may include data conferencing (including displaying and/or modifying a document for two or more participants during the conference).
Video conferencing involves transmitting video streams between video conferencing endpoints. The video streams transmitted between the video conferencing endpoints may include video frames. The video frames may include pixel macroblocks that may be used to construct video images for display in the video conferences. Video frame types may include intra-frames, forward predicted frames, and bi-directional predicted frames. These frame types may involve different types of encoding and decoding to construct video images for display. Currently, in a multi-way video conference call, a multipoint control unit (MCU) may composite video images received from different video conferencing endpoints onto video frames of a video stream that may be encoded and transmitted to the various video conferencing endpoints for display.
SUMMARY OF THE INVENTION
In various embodiments, an MCU or another video conferencing device (e.g., an endpoint) may generate a video frame that includes video images of two or more video conferencing endpoints. The MCU may also transmit coordinate information along with the video frame (e.g., as metadata). The metadata may include video image identifiers and location information (e.g., coordinates in the video frame) of the video images. The video frame may then be sent to a video conferencing endpoint that may receive the video frame and separate the two or more video images into separate video images. In some embodiments, the coordinate information sent along with the video frame may be used by the video conferencing endpoint to determine the locations of the video images in the video frame to facilitate separation of the video images.
In some embodiments, after the video conferencing endpoint separates out the video images, the separated video images may be provided to a compositor that may composite the separated video images into a new video image layout. Other video images (e.g., from local video or received from other video conferencing endpoints) may also be composited into the new video image layout. In some embodiments, the new video image layout may be configured to be displayed (e.g., as a continuous presence image). In some embodiments, participants at each video conferencing endpoint may use their local video conferencing endpoints to customize their continuous presence layout. For example, participants may rearrange the video images and/or replace one or more video images in the video image layout (e.g., with a current video image from their local video source).



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a video conferencing endpoint network, according to an embodiment.
FIG. 2 illustrates a video conferencing endpoint, according to an embodiment.
FIG. 3 illustrates a flowchart of a method for compositing a video image layout at an MCU and forming a new layout at the endpoint, according to an embodiment.
FIGS. 4a-d illustrates an MCU transmitting a video frame comprising multiple video images, according to an embodiment.
FIG. 5a illustrates an overall view of the re-compositing process including a virtual decoder, according to an embodiment.
FIG. 5b illustrates several embodiments of composite video images.
FIG. 6 illustrates a video image layout, according to an embodiment.
FIG. 7 illustrates separated video images from the video image layout, according to an embodiment.
FIG. 8 illustrates a new video layout using the separated video images, according to an embodiment.
FIG. 9 illustrates a coordinate system for a video frame, according to an embodiment.
FIG. 10 illustrates various video image layouts, according to various embodiments.



While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be 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. Note, the headings are for organizational purposes only and are not meant to be used to limit or interpret the description or claims. Furthermore, note that the word “may” is used throughout this application in a permissive sense (i.e., having the potential to, being able to), not a mandatory sense (i.e., must). The term “include”, and derivations thereof, mean “including, but not limited to”. The term “coupled” means “directly or indirectly connected”.
DETAILED DESCRIPTION OF THE EMBODIMENTS
Incorporation by Reference
U.S. Patent Application titled “Speakerphone”, Ser. No. 11/251,084, which was filed Oct. 14, 2005, whose inventor is William V. Oxford is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. Patent Application titled “Videoconferencing System Transcoder”, Ser. No. 11/252,238, which was filed Oct. 17, 2005, whose inventors are 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 titled “Speakerphone Supporting Video and Audio Features”, Ser. No. 11/251,086, which was filed Oct. 14, 2005, whose inventors are 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 titled “Virtual Decoders”, Ser. No. 12/142,263, which was filed Jun. 19, 2008, whose inventors are Keith C. King and Wayne E. Mock, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. Patent Application titled “Video Conferencing Device which Performs Multi-way Conferencing”, Ser. No. 12/142,340, which was filed Jun. 19, 2008, whose inventors are Keith C. King and Wayne E. Mock, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. Patent Application titled “Video Decoder which Processes Multiple Video Streams”, Ser. No. 12/142,377, which was filed Jun. 19, 2008, whose inventors are Keith C. King and Wayne E. Mock, is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
U.S. Patent Application titled “Integrated Videoconferencing System”, Ser. No. 11/405,686, which was filed Apr. 17, 2006, whose inventors are Michael L. Kenoyer, Patrick D. Vanderwilt, Craig B. Malloy, William V. Oxford, Wayne E. Mock, Jonathan I. Kaplan, and Jesse A. Fourt is hereby incorporated by reference in its entirety as though fully and completely set forth herein.
FIG. 1 illustrates an embodiment of a video conferencing system network 100. FIG. 1 illustrates an exemplary embodiment of a video conferencing system network 100 which may include a network 101, endpoints 103a-103d (e.g., video conferencing systems), and a Multipoint Control Unit (MCU) 108. Although not shown in FIG. 1, the video conferencing system network 100 may also include other devices, such as gateways, a service provider, conference units, and plain old telephone system (POTS) telephones, among others. Endpoints 103a-103d may be coupled to network 101 via gateways (not shown). Gateways may each include firewall, network address translation (NAT), packet filter, and/or proxy mechanisms, among others.
The endpoints 103a-103d may include video conferencing system endpoints (also referred to as “participant locations”). Each endpoint 103a-103d may include a camera, display device, microphone, speakers, and a codec or other type of video conferencing hardware. In some embodiments, endpoints 103a-103d may include video and voice communications capabilities (e.g., video conferencing capabilities) and include or be coupled to various audio devices (e.g., microphones, audio input devices, speakers, audio output devices, telephones, speaker telephones, etc.) and include or be coupled to various video devices (e.g., monitors, projectors, displays, televisions, video output devices, video input devices, cameras, etc.). In some embodiments, endpoints 103a-103d may include various ports for coupling to one or more devices (e.g., audio devices, video devices, etc.) and/or to one or more networks. Endpoints 103a-103d may each include and/or implement one or more real time protocols, e.g., session initiation protocol (SIP), H.261, H.263, H.264, H.323, among others. In an embodiment, endpoints 103a-103d may implement H.264 encoding for high definition (HD) video streams.
In some embodiments, the MCU 108 may function as a Multipoint Control Unit to receive video from two or more sources (e.g., endpoints 103a-d) and provide video (e.g., with composited video images) to two or more recipients (e.g., endpoints). “MCU” as used herein is intended to have the full breath of its ordinary meaning.
The network 101 may include a wide area network (WAN) such as the Internet. The network 101 may include a plurality of networks coupled together, e.g., one or more local area networks (LANs) coupled to the Internet. The network 101 may also include public switched telephone network (PSTN). The network 101 may also include an Integrated Services Digital Network (ISDN) that may include or implement H.320 capabilities. In various embodiments, video and audio conferencing may be implemented over various types of networked devices.
In some embodiments, endpoints 103a-103d and MCU 108 may each include various wireless or wired communication devices that implement various types of communication, such as wired Ethernet, wireless Ethernet (e.g., IEEE 802.11), IEEE 802.16, paging logic, RF (radio frequency) communication logic, a modem, a digital subscriber line (DSL) device, a cable (television) modem, an ISDN device, an ATM (asynchronous transfer mode) device, a satellite transceiver device, a parallel or serial port bus interface, and/or other type of communication device or method.
In various embodiments, the methods and/or systems described may be used to implement connectivity between or among two or more participant locations or endpoints, each having voice and/or video devices (e.g., endpoints 103a-103d and MCU 108, etc.) that communicate through network 101.
In some embodiments, the video conferencing system network 100 (e.g., endpoints 103a-d and MCU 108) may be designed to operate with network infrastructures that support T1 capabilities or less, e.g., 1.5 mega-bits per second or less in one embodiment, and 2 mega-bits per second in other embodiments. In some embodiments, other capabilities may be supported (e.g., 6 mega-bits per second, over 10 mega-bits per second, etc). The video conferencing system may support HD capabilities. The term “high resolution” includes displays with resolution of 1280×720 pixels and higher. In one embodiment, high-definition resolution may include 1280×720 progressive scans at 60 frames per second, or 1920×1080 interlaced or 1920×1080 progressive. Thus, an embodiment of the present invention may include a video conferencing system with HD “e.g. similar to HDTV” display capabilities using network infrastructures with bandwidths T1 capability or less. The term “high-definition” is intended to have the full breath of its ordinary meaning and includes “high resolution”.
FIG. 2 illustrates an exemplary embodiment of a video conferencing system endpoint 103 (e.g., 103a), also referred to as an endpoint or participant location. The endpoint 103 may have a system codec box 209 to manage both a speakerphone 205/207 and the video conferencing devices. The speakerphones 205/207 and other video conferencing system components may be coupled to the codec box 209 and may receive audio and/or video data from the system codec box 209.
In some embodiments, the endpoint 103 may include a camera 204 (e.g., an HD camera) for acquiring video images of the participant location (e.g., of participant 214). Other cameras are also contemplated. The endpoint 103 may also include a display 201 (e.g., an HDTV display). Video images acquired by the camera 204 may be displayed locally on the display 201 and may also be encoded and transmitted to other video conferencing endpoints 103 in the video conference, e.g., through the MCU 108.
The endpoint 103 may also include a sound system 261. The sound system 261 may include multiple speakers including left speakers 271, center speaker 273, and right speakers 275. Other numbers of speakers and other speaker configurations may also be used. The endpoint 103 may also use one or more speakerphones 205/207 which may be daisy chained together.
In some embodiments, the video conferencing endpoint components (e.g., the camera 204, display 201, sound system 261, and speakerphones 205/207) may be coupled to the system codec (“compressor/decompressor”) box 209. The system codec box 209 may be placed on a desk or on a floor. Other placements are also contemplated. The system codec box 209 may receive audio and/or video data from a network (e.g., network 101). The system codec box 209 may send the audio to the speakerphone 205/207 and/or sound system 261 and the video to the display 201. The received video may be HD video that is displayed on the HD display. The system codec box 209 may also receive video data from the camera 204 and audio data from the speakerphones 205/207 and transmit the video and/or audio data over the network 101 to another conferencing system. The conferencing system may be controlled by a participant through the user input components (e.g., buttons) on the speakerphones 205/207 and/or remote control 250. Other system interfaces may also be used.
In various embodiments, the system codec box 209 may implement a real time transmission protocol. In some embodiments, a system codec box 209 may include any system and/or method for encoding and/or decoding (e.g., compressing and decompressing) data (e.g., audio and/or video data). In some embodiments, the system codec box 209 may not include one or more of the compressing/decompressing functions. In some embodiments, communication applications may use system codec box 209 to convert an analog signal to a digital signal for transmitting over various digital networks (e.g., network 101, PSTN, the Internet, etc.) and to convert a received digital signal to an analog signal. In various embodiments, codecs may be implemented in software, hardware, or a combination of both. Some codecs for computer video and/or audio may include MPEG, IndeoTM, and CinepakTM, among others.
In some embodiments, the endpoint 103 may capture a local image of the local participants and provide a video stream to the MCU 108. The MCU 108 may also receive video streams from other endpoints 103. The MCU 108 may create a composite image of two or more of the received video streams and provide the composite image to each of the endpoints 103. The composite image, generated by the MCU 108, may have a certain layout. According to one embodiment, the MCU 108 may also generate coordinate information (or metadata) that describes the locations of the various images in the composite image. The endpoint 103 may use the coordinate information to separate the plurality of images from the composite image, and then generate a new composite image having a new layout, e.g., as specified by the user. The endpoint 103 may also use a virtual decoder technique in separating out the received composite image, as described below. In some embodiments, separating may include copying, replacing, and/or modifying data from the video images to be used to create a new composite image.
FIG. 3 illustrates a flowchart of a method for compositing a video image layout at an MCU 108 and forming a new layout at the endpoint 103, according to an embodiment. It should be noted that in various embodiments of the methods described below, one or more of the elements described may be performed concurrently, in a different order than shown, or may be omitted entirely. Other additional elements may also be performed as desired.
At 301, the MCU 108 may receive video images 555 from a plurality of endpoints 103. The endpoints 103 may be remote (e.g., endpoints 103a, 103b, and 103c) or local (e.g., local endpoint 103d including a local camera) and the video images 555 may include video (e.g., from camera 204) or presentations (e.g., from a Microsoft PowerpointTM presentation). In some embodiments, the MCU 108 may use one or more decoders 409 (e.g., three decoders 409) to decode the received video images 555 from the respective endpoints 103. For example, video packets for the video frames with the respective received video images 555 may be assembled as they are received (e.g., over an Internet Protocol (IP) port) into the MCU 108. FIGS. 4a-d illustrate embodiments of MCUs 108.
In some embodiments, the MCU 108 may also receive video image layout preferences from one or more of the endpoints 103. For example, endpoint 103 may receive a video image layout preference from one or more video conferencing participants 214 (e.g., through a menu on an on-screen interface) and may transmit that preference to the MCU 108. In some embodiments, a button on remote 250 may allow a video conference participant 214 to cycle through two or more available layout preferences. The video image layout preference may include a layout type (e.g., layout type 1001, 1003, 1005, 1007, 1009, or 1011 as seen in FIG. 10). Other layout types are also possible. The video image layout preference may specify which endpoint's video image to place in each of the available layout positions (e.g., which endpoint video image should be placed in the main layout position and which endpoint video images should be placed in the other layout positions). In some embodiments, the MCU 108 may not receive a video image layout preference from one or more endpoints 103. In some embodiments, the video image layout preference may be generated at the MCU 108. For example, software on the MCU 108 may determine which endpoint 103 has the current speaker/presenter and may place the corresponding video image in a main video image window of the layout (e.g., with other endpoint video images arranged around the main video image). Other layout selection methods are also contemplated.
In some embodiments, the MCU 108 may also be operable to receive other information from the endpoints 103. For example, an endpoint 103 may send data to the MCU 108 to move a far end camera (e.g., on another endpoint). The MCU 108 may subsequently transmit this information to the respective endpoint to move the far end camera.
At 303, the MCU 108 may generate a composite video image comprising two or more video images 555 (for example, from the endpoints 103 (such as video images 555a, 555b, 555c, and 555d)). In some embodiments, the MCU 108 may have one or more scalers 411 (e.g., four scalers) and compositors 413 to scale received video images 555 and composite two or more of the video images 555 from the endpoints 103 into, for example, a composite video image 505 (e.g. which may include one or more video images 555 in, for example, a continuous presence layout). Example composite video images 505 are illustrated in FIG. 5b (e.g., composite video images 505a, 505b, 505c, and 505d).
In some embodiments, scalers 411 may be coupled to video decoders 409 (e.g., through crosspoint switch 499 shown in FIG. 4c) that decode video images 555 from the various video sources (e.g., endpoints 103). The scalers 411 may scale the video images 555 after the video images 555 are decoded. In some embodiments, one or more of the video images 555 may not be scaled. For example, the two or more video images 555 may be rearranged into a composite video image 505 without being scaled. In some embodiments, the scalers 411 may be 7-15 tap scalers. The scalers 411 may use linear combinations (e.g., with similar or different coefficients) of a plurality of pixels in a video image 555 for each pixel scaled. Other scalers 411 are also contemplated. In some embodiments, the video images 555 may be stored in shared memory 495 after being scaled. In some embodiments, the scaler 411, compositor 421, compositor 413, and scalers 415 may be included on one or more FPGAs (Field-Programmable Gate Arrays). Other processor types and processor distributions are also contemplated. For example, FPGAs and/or other processors may be used for one or more other elements shown on FIG. 4b. 
In some embodiments, compositors 413 may access the video images 555 (e.g., from shared memory 495) to form composited video images. In some embodiments, the MCU 108 may composite the video images 555 into the respective video image layouts requested by the endpoints 103. For example, the MCU 108 may composite two or more of the received video images 555 into a continuous presence layout (e.g., see layout types 1001, 1003, 1005, 1007, 1009, or 1011 in FIG. 10). In some embodiments, the MCU 108 may form multiple composite video images according to respective received video image layout preferences.
In some embodiments, the output of the compositors 413 may again be scaled (e.g., by scalers 415 (such as scalers 415a, 415b, and 415c)) prior to being encoded by video encoders 453. The video data received by scalers 415 may be scaled according to the resolution requirements of a respective endpoint 103. In some embodiments, the output of a compositor 413 may not be scaled prior to being encoded and transmitted to the endpoints 103. In some embodiments, the composite video image 505 may be transmitted as a video frame 507 through video stream 500 (see FIG. 5a) to the respective endpoints 103.
In some embodiments, the MCU 108 may determine the coordinates of the video images 555 in the composite video image 505. For example, the coordinate information 519 may indicate the start/stop locations of one or more of the video images 555 in the video frame 507. This coordinate information 519 may be stored on the MCU 108.
At 305, the MCU 108 may transmit the composite video image 505 (which includes one or more video images 555) and the coordinate information 519 to each endpoint 103. For example, the MCU 108 may transmit a respective composite video image 505 (with the respective coordinate information 519 for the respective composite video image 505) to a respective endpoint 103 (e.g., according to the video image layout preference received from the respective endpoint 103). The MCU 108 may also transmit the coordinate information 519 to the endpoints 103. The coordinate information 519 sent to a respective endpoint 103 may be specific to the respective composite video image 505 sent to that endpoint 103. The coordinate information 519 may identify the locations of specific video images 555 in the received composite video image 505. In some embodiments, the coordinate information 519 may be transmitted as metadata 901 with the composite video image 505. The metadata 901 may include coordinate information 519 for a video frame 507 with the start (and/or stop) information for a video image 555 (e.g., video image boundaries and/or pixel start/stop points) corresponding to an endpoint 103. The metadata 901 may also include attributes of each of the plurality of endpoints 103 including identifying information respective to the corresponding endpoints 103 for each video image 555. Other information in the metadata 901 is also contemplated.
At 307, the endpoint 103 may receive the composite video image 505 and the coordinate information 519 (e.g., in metadata 901). For example, video frame 507 comprising two or more video images 555 may be received. The video frame 507 may be received as a series of video packets 503 in video stream 500 at decoder 515. The decoder 515 may assemble the video packets 503 into their respective video frames 507 for further processing in virtual decoder 517.
In some embodiments, the coordinate information 519 may include a size of an original composite video image. For example, after determining the coordinate information 519, the MCU 108 may need to subsequently scale the composite video image (e.g., scale down the composite video image to be sent over a reduced bandwidth network connection) to be sent to one or more endpoints 103. In some embodiments, the composite video image 505 may be scaled to a scaled composite video image in a scaler (e.g., scaler 415). The coordinate information 519 may be included in metadata 901 passed with a video frame 507 that includes the scaled composite video image. In some embodiments, the coordinate information 519 may be reformatted (e.g., at the MCU 108 or at the receiving endpoint 103) to reflect the new coordinates of one or more of the resized video images in the scaled composite video image. For example, when the endpoint 103 receives the scaled composite video image, the endpoint 103 may detect the actual size of the scaled composite video image and may determine the new coordinates of one or more of the video images 555 in the scaled composite video image using, for example, a ratio of the size of the original composite video image (which may be indicated in the coordinate information 519) to the size of the scaled composite video image detected by the endpoint 103. These new coordinates may then be used to separate one or more of the resized images in the scaled composite video image (see 309 below) to use in compositing a new composite video image (see 311 below). For example, see U.S. Provisional Patent Application titled “Virtual Multiway Scaler Compensation”, Ser. No. 60/949,674, which was filed Jul. 13, 2007, whose inventors are Keith C. King and Wayne E. Mock, which was incorporated by reference above.
At 309, the endpoint 103 may separate the video images 555 using the coordinate information 519. Virtual decoders 517 at one or more of the endpoints 103 may separate the composite video image 505 (e.g., a continuous presence layout) into two or more separate video images 559. In some embodiments, the coordinate information 519 may be used to find video image boundaries of the video images 555 within the video frame 507. In some embodiments, the coordinate information 519 may be used to determine where the respective video images 555 start and stop in the video frame 507. These start/stop locations may be used by the virtual decoder 517 to separate one or more video images 555 from the video frame 507. For example, the separate video images may be defined and/or scaled out of the composite video image 505. For example, the coordinate information 519 may be used by the virtual decoder 517 to crop the respective video images 555 (e.g., video images 555a and 555b) in the video frame 507. In some embodiments, separating the video images 555 may include, for example, storing the separated video images 559 in separate locations of a memory. In some embodiments, separating the video images 555 may include storing start and/or stop locations of the separated video images 559 in a memory. Other means for separating the video images 555 are also contemplated. For example, separating may include copying, replacing, and/or modifying data from the video images 555 of the composite video image 505 to be used to create a new composite image layout (see 311 below).
FIG. 9 illustrates an example of a use of coordinate information 519 to locate the boundaries of four video images (e.g., video images 555a-d) in order to separate the video images 555. For example, the User 1 video image 555a may have a left boundary at 0, a top boundary at 0, a right boundary at 639 (e.g., 639 pixels to the right of the left edge of the video frame 507), and a bottom boundary at 359. Similarly, the user 2 video image 555b may have a left boundary at 640, a top boundary at 0, a right boundary at 1279, and a bottom boundary at 359. Coordinate information 519 (e.g., boundary information) for other video images (e.g., video images 555c and 555d) may also be provided e.g., in metadata 901. In some embodiments, coordinate information for a respective video image may be placed in a row of information for the respective video image. For example, row one of data in metadata 901 may include a call identifier, system name, number, Internet Protocol (IP) address, and left, top, right, bottom coordinates (e.g., 0, 0, 639, and 359) for a respective video image (other information may also be included).
While four video images 555 are shown with respect to video frame 507, it is noted that video frame 507 may include a composite video image 505 with other combinations and layouts of two or more video images 555. For example, as seen in FIG. 5b, composite video image 505b may include four video images 555 stacked on top of each other. In some embodiments, each video image of the stacked video images may be 1280 by 720 pixels (e.g., for a total size of 1280 by 2880) (other dimensions and number of video images are also contemplated). In some embodiments, composite video image 505c may include four images side by side. As another example, the composite video image 505d may include two video images (e.g., each 640 by 360 pixels) arranged side by side in a 1280 by 360 pixel video frame. The video frame 507 may then be separated into two 640 by 360 pixel video images. Other combinations and layouts are also contemplated. In some embodiments, the number of video images 555 composited in the composite video image 505 may depend on the number of participating endpoints 103 in the video conference. For example, each participating endpoint may have a corresponding video image (which may be, for example, 1280 by 720) in the composite video image 505.
FIG. 6 shows an example of a composite video image 600 with three video images 601, 603, and 605 originating from different endpoints 103. The composite video image 600 may include a main video image 601 of the endpoint with the current speaker/presenter and two or more side video images (e.g., side video images 603 and 605) of other endpoints participating in the video conference. Coordinate information 519 for coordinates 609, 611, and 613 may be sent with the video frame 507 and used by the virtual decoder 517 to separate the video images into separated video images 701, 703, and 705 (as seen in FIG. 7).
In some embodiments, the virtual decoder 517 may be implemented as a software abstraction on hardware such as an FPGA or other processor. In some embodiments, one or more virtual decoders 517 may be implemented on a single ASIC (Application Specific Integrated Chip). Other virtual decoder configurations are also contemplated. In some embodiments, a separate processor may implement the virtual decoder 517 by issuing commands to reprogram at least one FPGA to implement the virtual decoder 517. Other configurations are also contemplated.
At 311, the endpoint 103 may generate a new composite video image based, for example, on user preference. In some embodiments, one or more of the separated video images 559 may be provided to one or more scalers 513. The video images (including scaled video images, if any) may then be provided to one or more compositors 515. One or more compositors 515 may composite the video images into a new video image layout 559 (e.g., requested by a local participant 214 through their local endpoint 103d). In some embodiments, a local participant may cycle through the layout offerings from the endpoint 103 (e.g., by clicking an icon to cycle to the next available layout). In some embodiments, the scalers 513 and compositors 515 may be implemented in hardware or software. In some embodiments, icon scalers may be used (e.g., if all of the endpoint's other scalers are being used).
As an example, if the main video image 701 and each of the two side video images 703 and 705 are to be placed in a video image layout with equal sized video images, the main video image 701 may be scaled down and the two side video images 703 and 705 may be scaled up (or not scaled at all). Other scaling combinations are also contemplated. In some embodiments, the separated video images may not be scaled (e.g., the separated video images may be only rearranged).
In some embodiments, the endpoint 103 may form a new composite video image that includes its current local video image 555e (see FIG. 5a) as one of the video images. In some embodiments, the layout of the received video image layout and the new video image layout may be the same. In some embodiments, the current local video image 555e may be more current than the local video image 555c originally sent to the MCU 108 and received in the composite video image 505.
At 313, the endpoint 103 may display the new composite video image. FIG. 8 illustrates an example of a new video image layout with three similar sized video images 801, 803, and 805 on display. FIG. 10 illustrates other possible video image layouts, according to various embodiments. Other video image layouts are also contemplated. In some embodiments, the metadata 901 may be displayed (e.g., with each respective video image in the video image layout).
Embodiments of a subset or all (and portions or all) of the above may be implemented by program instructions stored in a memory medium or carrier medium and executed by a processor. A memory medium may include any of various types of memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a Compact Disc Read Only Memory (CD-ROM), floppy disks, or tape device; a computer system memory or random access memory such as Dynamic Random Access Memory (DRAM), Double Data Rate Random Access Memory (DDR RAM), Static Random Access Memory (SRAM), Extended Data Out Random Access Memory (EDO RAM), Rambus Random Access Memory (RDRAM), etc.; or a non-volatile memory such as a magnetic media, e.g., a hard drive, or optical storage. The memory medium may include other types of memory as well, or combinations thereof. In addition, the memory medium may be located in a first computer in which the programs are executed, or may be located in a second different computer that connects to the first computer over a network, such as the Internet. In the latter instance, the second computer may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums that may reside in different locations, e.g., in different computers that are connected over a network.
In some embodiments, a computer system at a respective participant location may include a memory medium(s) on which one or more computer programs or software components according to one embodiment of the present invention may be stored. For example, the memory medium may store one or more programs that are executable to perform the methods described herein. The memory medium may also store operating system software, as well as other software for operation of the computer system.
Further modifications and alternative embodiments of various aspects of the invention may be apparent to those skilled in the art in view of this description. Accordingly, this description is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the general manner of carrying out the invention. It is to be understood that the forms of the invention shown and described herein are to be taken as embodiments. Elements and materials may be substituted for those illustrated and described herein, parts and processes may be reversed, and certain features of the invention may be utilized independently, all as would be apparent to one skilled in the art after having the benefit of this description of the invention. Changes may be made in the elements described herein without departing from the spirit and scope of the invention as described in the following claims.

## Claims

1. A video conferencing endpoint, comprising:
a decoder;
a virtual decoder communicatively coupled to the decoder;
a compositor communicatively coupled to the virtual decoder;
wherein the video conferencing endpoint is configured to transmit a video image to an MCU;
wherein the video conferencing endpoint is configured to receive a composite video image, through the decoder, from the MCU comprised of at least two video images, each from a respective video conferencing endpoint;
wherein the video conferencing endpoint is configured to receive coordinate information from the MCU, wherein the coordinate information includes information on a location of a video image of the at least two video images within the composite video image;
wherein the video conferencing endpoint is configured to use the coordinate information to separate each of the video images from the composite video image using the virtual decoder;
wherein the at least one video conferencing endpoint is configured to generate a new composite video image; and
wherein the at least one video conferencing endpoint is configured to display the new composite video image.

2. The video conferencing endpoint of claim 1, wherein the coordinate information is comprised in metadata transmitted with a video frame comprising the composite video image.

3. The video conferencing endpoint of claim 1, wherein the new composite video image comprises at least one video image derived from local video of the video conferencing endpoint.

4. The video conferencing endpoint of claim 1, wherein the composite video image from the MCU has a first layout and wherein the new composite video image has a second different layout.

5. A method, comprising:
transmitting a video image to an MCU from a video conferencing endpoint;
receiving a composite video image, through a decoder at the video conferencing endpoint, from the MCU comprised of at least two video images, each from a respective video conferencing endpoint;
receiving coordinate information from the MCU, wherein the coordinate information includes information on a location of a video image within the composite video image;
separating each of the video images from the composite video image using a virtual decoder; wherein the virtual decoder uses the coordinate information to separate the video images;
generating a new composite video image; and
displaying the new composite video image.

6. The method of claim 5, wherein the coordinate information is comprised in metadata transmitted with a video frame comprising the composite video image.

7. The method of claim 5, wherein the new composite video image comprises at least one video image derived from local video of the video conferencing endpoint.

8. The method of claim 5, wherein the composite video image from the MCU has a first layout and wherein the new composite video image has a second different layout.

9. The video conferencing endpoint of claim 1, wherein the virtual decoder is implemented in software of the video conferencing endpoint.

10. The video conferencing endpoint of claim 1, wherein the video conferencing endpoint further comprises:
one or more processors; and
one or more memory mediums coupled to the one or more processors, wherein the memory medium stores program instructions executable by the one or more processor to implement the virtual decoder.

11. The video conferencing endpoint of claim 1, wherein the virtual decoder is implemented within an integrated circuit.

12. The video conferencing endpoint of claim 1, wherein the virtual decoder is implemented within a programmable gate array.

13. The method of claim 5, wherein the virtual decoder is implemented in software of the video conferencing endpoint.

14. The method of claim 5, wherein the virtual decoder is implemented within an integrated circuit.

15. The method of claim 5, wherein the virtual decoder is implemented within a programmable gate array.