Source: https://patents.google.com/patent/US8446455B2/en
Timestamp: 2018-04-26 12:24:59
Document Index: 539041596

Matched Legal Cases: ['art 100', 'art 200', 'art 100', 'art 200', 'art 200', 'art 100', 'art 100', 'art 300', 'art 100', 'art 100']

US8446455B2 - System and method for exchanging information in a video conference environment - Google Patents
System and method for exchanging information in a video conference environment Download PDF
US8446455B2
US8446455B2 US12963324 US96332410A US8446455B2 US 8446455 B2 US8446455 B2 US 8446455B2 US 12963324 US12963324 US 12963324 US 96332410 A US96332410 A US 96332410A US 8446455 B2 US8446455 B2 US 8446455B2
US12963324
US20120147123A1 (en )
TiongHu Lian
A method is provided in one example embodiment and includes monitoring a plurality of inputs associated with end users involved in a video session in which a plurality of displays are used. At least one of the inputs is associated with a frequency of speech of the end users. The method also includes determining a participation level for each of the end users based on the inputs, and determining which image data associated with the end users is to be rendered on a selected one of the plurality of displays based on the participation levels.
This disclosure relates in general to the field of communications, and more particularly, to exchanging information in a video conference environment.
Video services have become increasingly important in today's society. In certain architectures, service providers may seek to offer sophisticated videoconferencing services for their end users. The videoconferencing architecture can offer an “in-person” meeting experience over a network. Videoconferencing architectures can deliver real-time, face-to-face interactions between people using advanced visual, audio, and collaboration technologies. Some issues have arisen in videoconferencing scenarios when a multiscreen endpoint joins a multipoint meeting, where there may be more participants than the number of available displays. The ability to optimize display use during a video conference presents a significant challenge to developers and designers, who attempt to offer a videoconferencing solution that is realistic and that mimics a real-life meeting.
FIG. 1 is a simplified schematic diagram of a communication system for exchanging information in a conferencing environment in accordance with one embodiment;
FIG. 2 is a simplified block diagram of a communication system for optimizing image rendering in a conferencing environment in accordance with one embodiment;
FIG. 3 is a simplified diagram of an example display configuration in accordance with one embodiment;
FIG. 4 is a simplified flowchart illustrating example operations associated with one embodiment of the communication system;
FIG. 5 is a simplified flowchart illustrating example operations associated with calculating participation values in an embodiment of the communication system; and
FIG. 6 is a simplified flowchart illustrating example operations associated with analyzing participation values in an embodiment of the communication system.
In more specific implementations, the determining of the participation level includes calculating numeric values associated with the participation levels, where the numeric values are used to assign virtual positions for the end users during the video session. In other instances, one of the participation levels of the end users is preconfigured to have a base level that is higher than the participation levels of the other end users. The base level can be set in accordance with an identity of one of the end users (e.g., title, rank, employment status, organizational hierarchy, etc.).
In yet other example configurations, the inputs include body language characteristics and eye gaze metrics of the end users. Additionally, the inputs can include a volume of speech associated with the end users. The inputs can be weighted differently in order to determine the participation levels for each of the end users. The participation levels can be adjusted by an administrator during the video session. In general, a higher participation level for a selected one of the end users is prioritized over a lower participation level for another one of the end users. Hence, the end user having the highest participation level would have their associated image data rendered on a given display.
Turning to FIG. 1, FIG. 1 is a simplified schematic diagram illustrating a communication system 10 for conducting a video conference in accordance with one example embodiment. FIG. 1 includes multiple endpoints associated with various end users of the video conference. In general, endpoints may be geographically separated, where in this particular example, endpoints 12 a-c are located in San Jose, Calif. and counterparty endpoints are located in Chicago, Ill. FIG. 1 includes a multipoint manager element 20 coupled to endpoints 12 a-c. Note that the numerical and letter designations assigned to the endpoints do not connote any type of hierarchy; the designations are arbitrary and have been used for purposes of teaching only. These designations should not be construed in any way to limit their capabilities, functionalities, or applications in the potential environments that may benefit from the features of communication system 10.
In this example, each endpoint is fitted discreetly along a desk and is proximate to its associated participant. Such endpoints could be provided in any other suitable location, as FIG. 1 only offers one of a multitude of possible implementations for the concepts presented herein. In one example implementation, the endpoints are videoconferencing endpoints, which can assist in receiving and communicating video and audio data. Other types of endpoints are certainly within the broad scope of the outlined concept, and some of these example endpoints are further described below. Each endpoint is configured to interface with a respective multipoint manager element, such as multipoint manager element 20, which helps to coordinate and to process information being transmitted by the end users.
As illustrated in FIG. 1, a number of cameras 14 a-14 c and displays 15 a-15 c are provided for the conference. Displays 15 a-15 c render images to be seen by the end users and, in this particular example, reflect a three-display design (e.g., a ‘triple’). Note that as used herein in this specification, the term ‘display’ is meant to connote any element that is capable of rendering an image during a video conference. This would necessarily be inclusive of any panel, screen, Telepresence display or wall, computer display, plasma element, television, monitor, or any other suitable surface or element that is capable of such rendering.
The components of communication system 10 may use specialized applications and hardware to create a system that can leverage a network. Communication system 10 can use Internet protocol (IP) technology and can run on an integrated voice, video, and data network. The system can also support high quality, real-time voice, and video communications using broadband connections. It can further offer capabilities for ensuring quality of service (QoS), security, reliability, and high availability for high-bandwidth applications such as video. Power and Ethernet connections for all end users can be provided. Participants can use their laptops to access data for the meeting, join a meeting place protocol or a Web session, or stay connected to other applications throughout the meeting.
As a general proposition, the videoconferencing technology of communication system 10 can be configured to create an in-person meeting experience for its participants. To replicate the conference room experience, the architecture is configured to provide a mechanism for intelligently (and autonomously) rendering images (on videoconferencing displays) of certain participants, who exude high levels of participation. Conversely, the system can also identify low levels of involvement of participants and, accordingly, minimize their associated images on the displays. This can better simulate the experience of a conversation that occurs in an actual conference room.
For purposes of illustrating certain example techniques of communication system 10, it is important to understand the communications that may be traversing the network. The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. One objective in videoconferencing is to maintain eye gaze and balance amongst the participants. For example, a videoconferencing system employing three panels would seek to avoid a scenario in which eleven people are competing for one panel, while a single (potentially inactive) person is being rendered on another panel. Hence, screen real estate is a scarce resource in videoconferencing architectures. Accordingly, it needs to be optimally managed to enhance the end user experience. In the aforementioned scenario, certain screen real estate is in contention, whereas other screen real estate is available for immediate use.
Current videoconferencing architectures use blunt mechanisms to determine image rendering of participants during a video session. For example, many existing videoconferencing systems use a ‘least-recently-used’ kickout scheme for the placement of their end users. As someone new begins speaking, whoever has not spoken recently (and who is currently being shown) would be displaced by a different end user. In one general sense, there is nominal intelligence behind this image rendering decision. Furthermore, such systems fail to provide a realistic environment that mimics in-person meetings. For example, in any conversation, a natural hierarchy typically emerges amongst the end users. This can be attributed to the activity levels of the participants, their command of the subject matter, their stature in an organization, etc. Ideally, when a video session involves a number of individuals forced to share display space (i.e., no party has an exclusive display devoted to their image), there is one active, authoritative person at each screen of the videoconferencing architecture.
In accordance with one embodiment, communication system 10 can overcome these shortcomings (and others) in providing an intelligent videoconferencing architecture that dynamically adjusts its image rendering operations based on various inputs. This would enhance the user experience by offering an effective placement of participants on screens in a multiscreen endpoint. More specifically, communication system 10 can maintain positioning priorities, such as spatial consistency and eye-gaze alignment, while also monitoring the behavior of end users over the course of a conference. Each end user may be assigned a virtual position based on participation levels (e.g., numeric values). The virtual position determines the display for rendering image data associated with a given end user.
The participation value may be normalized, used to indicate the relative importance of a participant in a conference, and derived based on various participation inputs. For example, an end user may be assigned a participation value when the end user first speaks, and that value may diminish as time passes without further speaking. Thus, an active speaker can accumulate more value than a passive end user can. Another example criterion may relate to the eye contact of participants, where a lack of eye contact would reduce the participation levels. [Note that the term ‘eye contact’ is included within the broader term ‘eye gaze metrics’ as used herein in this Specification.] Eye gaze metrics could further include instances weighing against the participation level such as when individuals stare downward (e.g., at a laptop), turn to counterparties (e.g., indicative of a private conversation outside the video conference), become preoccupied and look away from the video screens (e.g., when a given individual uses their own private telephone), etc. The participation level can then be correlated to the intelligent placement of individuals on the screens.
In operation during a video session, the total participation value of a participant is used by multipoint manager element 20 to assign a virtual position to the end user and, further, to determine when the end user should be displayed (or displaced) to improve the meeting experience. However, frequent virtual position adjustment can also adversely affect the meeting experience, and communication system 10 may further incorporate appropriate limits on the frequency of participant re-positioning.
Thus, image rendering on specific screens can be based on participation levels, which may further include an active level of speech, body language, eye gaze metrics, or any other suitable characteristic that would be indicative of a participation level. Operationally, the initial participation level settings can be preconfigured before a video conference was initiated. However, even if the participation levels were to the preconfigured, the participation levels can still be dynamically updated, manually updated (e.g., by administrator, by the individual themselves, etc.), or adjusted using any appropriate feedback mechanisms, as outlined here in this Specification.
Logistically, multipoint manager element 20 is configured to monitor (i.e., access, evaluate, determine, assess, etc.) the video session (e.g., in real-time) for a variety of inputs. As used herein in this Specification, the term ‘input’ is inclusive of volume of speech, eye gaze, body language characteristics (inclusive of nodding, slouching, hand and arm gestures, posture, leg crossing, fidgeting, etc.), frequency of speech, identity of an individual, rank of the individual relative to other individuals, job title, default inputs, preconfigured inputs, or any other suitable parameter, attribute, or characteristic that can be associated with participation levels. All of these inputs can be assessed on a numeric scale (e.g., 1-100).
Furthermore, as these inputs are monitored, they can be evaluated or weighted differently (e.g., speech being accorded a higher weight for determining the participation level, in contrast to simple body language, which may be less certain to quantify). In another instance, nodding (which is part of the body language) may be accorded a higher weight than eye gaze. All of these inputs can be used in conjunction with inputs associated with identity, pre-configurations, default settings, etc. in order to determine appropriate participation levels of participants.
In various embodiments presented herein, one of the inputs to be used as a basis for forming a participation level can include the identity of the person. In such a configuration, a given individual may be attributed to a higher base level of participation, where that individual may represent an authoritative speaker, a manager, a vice president, etc. Such individuals would have a higher participation level initially (e.g., provisioned by default). Reciprocally, individuals can be assigned lower participation levels from the outset of the videoconferencing session. For example, a vice president (even though his stature may dictate one type of participation level) may be relegated to a lower initial participation level based on his minimal involvement in a particular subject area or project, which is to be discussed during the videoconferencing call. Furthermore, a given administrator can personally assess participation levels (e.g., notices someone who is highly involved in the discussion, or who is preoccupied, etc.) and tweak the participation levels, or suitably override the current participation levels such that image rendering can be managed directly by that administrator. Any such provisioning can readily be accommodated by the flexible architecture of communication system 10.
Before turning to some of the additional operations of communication system 10, a brief discussion is provided about some of the infrastructure of FIG. 1. Endpoint 12 a may be used by someone wishing to participate in a video conference in communication system 10. The term ‘endpoint’ may be inclusive of devices used to initiate a communication, such as a switch, a console, a proprietary endpoint, a telephone, a bridge, a computer, a personal digital assistant (PDA), a laptop or electronic notebook, an i-Phone, an iPad, a Google Droid, any other type of smartphone, or any other device, component, element, or object capable of initiating voice, audio, or data exchanges within communication system 10.
Endpoint 12 a may also be inclusive of a suitable interface to an end user, such as a microphone, a display, or a keyboard or other terminal equipment. Endpoint 12 a may also include any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating a voice or a data exchange within communication system 10. Data, as used herein, refers to any type of video, numeric, voice, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another. Additional details relating to endpoints are provided below with reference to FIG. 2.
In operation, multipoint manager element 20 can be configured to establish, or to foster a video session between one or more end users, which may be located in various other sites and locations. Multipoint manager element 20 can also coordinate and process various policies involving endpoints 12 a-c. In general, multipoint manager element 20 may communicate with endpoints 12 a-c through any standard or proprietary conference control protocol. Multipoint manager element 20 includes a switching component that determines which signals are to be routed to individual endpoints 12 a-c. Multipoint manager element 20 can also determine how individual end users are seen by others involved in the video conference. Furthermore, multipoint manager element 20 can control the timing and coordination of this activity. Multipoint manager element 20 can also include a media layer that can copy information or data, which can be subsequently retransmitted or simply forwarded along to one or more endpoints 12 a-c.
Turning to FIG. 2, FIG. 2 is a simplified block diagram illustrating one possible set of details associated with communication system 10. In this example, endpoints 12 a and 12 c in San Jose are configured to interface with multipoint manager element 20, which is coupled to a network 40. Along similar rationales, endpoints 12 e and 12 f in Chicago are configured to interface with a counterparty multipoint manager element 50, which is similarly coupled to network 40. In the particular implementation of FIG. 2, endpoints 12 a, 12 c, 12 e, 12 f include a respective processor 32 a, 32 c, 32 e, 32 f, a respective memory element 44 a, 44 c, 44 e, 44 f, a respective network interface 46 a, 46 c, 46 e, 46 f, a respective transmitting module 48 a, 48 c, 48 e, 48 f, and a respective receiving module 42 a, 42 c, 42 e, 42 f. Any one or more of these internal items of the endpoints may be consolidated or eliminated entirely, or varied considerably, where those modifications may be made based on particular communication needs, specific protocols, etc.
In one example implementation, multipoint manager elements 20, 50 include respective processors 52 a-52 b, respective memory elements 54 a-54 b, and respective participation level modules 56 a-b, which may dictate the images that are to be rendered on a given display for end users in a video session. Multipoint manager elements 20, 50 can be aware of (and potentially store) information about who is being seen by the end users of the video conference. Multipoint manager elements 20, 50 can selectively distribute signals to various end users using any suitable inputs (e.g., associated with eye gaze, body language, speaker volume, pre-configurations, etc.).
In one particular instance, multipoint manager elements 20, 50 are configured to exchange data in a network environment such that the intelligent screen management functionality discussed herein is achieved. As used herein in this Specification, the term ‘network element’ is meant to encompass various types of routers, switches, gateways, bridges, loadbalancers, firewalls, servers, inline service nodes, proxies, processors, modules, or any other suitable device, component, element, or object operable to exchange information in a network environment. The network element may include appropriate processors, memory elements, hardware and/or software to support (or otherwise execute) the activities associated with using a processor for screen management functionalities, as outlined herein. Moreover, the network element may include any suitable components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.
In a specific implementation, multipoint manager elements 20, 50 include software to achieve (or to foster) the screen management operations, as outlined herein in this document. For example, this could include participation level modules 56 a-b, which can be configured to execute many of the activities discussed herein with respect to screen management functions. Furthermore, in one example, multipoint manager elements 20, 50 can have an internal structure (e.g., have a processor, a memory element, etc.) to facilitate some of the operations described herein. In other embodiments, all of these screen management features may be provided externally to these elements or included in some other network element to achieve this intended functionality. Alternatively, any other network element can include this software (or reciprocating software) that can coordinate with multipoint manager elements 20, 50 in order to achieve the operations, as outlined herein.
Note that in certain example implementations, the screen management functions outlined herein may be implemented by logic encoded in one or more tangible media (e.g., embedded logic provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by a processor, or other similar machine, etc.). In some of these instances, a memory element [as shown in FIG. 2] can store data used for the operations described herein. This includes the memory element being able to store software, logic, code, or processor instructions that are executed to carry out the activities described in this Specification. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor [as shown in FIG. 2] could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.
Turning to FIG. 3, FIG. 3 illustrates one possible operational scenario in which communication system 10 may provide positioning of remote end users on multiple multiscreen displays 70, 72, 74 associated with an endpoint. By way of example, display 70 may represent the screens at the beginning of a meeting, while display 74 may represent the same screens at the end of a meeting, while display 72 may represent the screens at some interim stage of the meeting. Each display 70-74 includes a LEFT, CENTER, and RIGHT screen in this example. In general, each screen is represented in communication system 10 as a virtual position. The capital letters A-I below each screen represent a specific end user.
In this instance, at the beginning of a meeting, communication system 10 may assign end users B, E, and H to a virtual position rendered on the LEFT screen of display 70, assign end users A, D, and G to a virtual position on the CENTER screen, and assign end users C, F, and I to a virtual position on the RIGHT screen. This assignment may be arbitrary, based on a round-robin protocol, or other balancing algorithm so that the number of end users is distributed evenly among available virtual positions (e.g., or based on some pre-determined criteria such as a participant's location). In one example embodiment, a participant's virtual position is sticky so that the end user systematically appears on the same display (subject to modification as described below).
As the meeting progresses, communication system 10 may monitor the participation level of each end user and assign a participation value to each end user. More specifically, in this example, communication system 10 has determined that end user A has a participation value of 5 (as indicated parenthetically below display 72 in FIG. 3), end user B has a participation value of 70, end user C has a participation value of 4, and so forth. Based on these participation values, end users B, E, and G appear to be participating much more actively than end users A, C, D, F, H, and I. However, both B and E are initially assigned to a virtual position on the LEFT screen, which means that communication system 10 may be frequently switching the left screen to accommodate B and E, while the RIGHT screen is occupied by (relatively) inactive end users. Communication system 10 has the intelligence to effectively adjust participant placements to other virtual positions based on their participation values. This optimizes the limited screen real estate available for the video conference. In this example, the reassignment is depicted below display 74, where end user E has been switched to the RIGHT screen and end user I has been switched to the LEFT screen such that active end users B and E are no longer competing for the same screen.
FIG. 4 is a simplified flowchart 100 illustrating one potential operation associated with an embodiment of communication system 10. The operation starts at 105, which may correspond to the beginning of a video conference session. After a delay of time T at 110, participation data may be sampled at 115 and stored at 120 as participation history. At 125, participation values for each participant may be calculated based on the participation history. At 130, the participation values can be analyzed to determine if virtual positions should be switched to accommodate participants that are more active. If it is determined that participants should be switched, then the virtual positions may be updated at 135. If it is determined that participants do not need to be switched, then the process returns to 110, and the system may iterate through the same operations until the meeting is terminated, or until the process is otherwise interrupted.
FIG. 5 is a simplified flowchart 200 illustrating one potential process associated with calculating participation values, as may be done in 125 of flowchart 100. The operations may begin at 205, where the participation history can be evaluated, received, or accessed. In the example of flowchart 200, two values are extracted from the participation history at 210 and normalized if appropriate. These values in flowchart 200 are a volume 215 a and a frequency 215 b of a participant's speech during a video session. These values are, of course, only two possible indicators of activity (i.e., inputs) and are only being provided for illustration purposes. Any number (or combination) of relevant activity indicators can be used (e.g., inputs associated with eye contact, slouching, nodding, arm gestures, the lack of any body movement, or any other suitable body language, movement, gesturing, etc.). At 220 a and 220 b, these indicators may be multiplied by a set of predetermined weights 225 a and 225 b, respectively. For example, in many scenarios it may be reasonable to assume that frequency is a better indicator of active participation than volume and, therefore, a greater weight value may be assigned to the frequencies of participation than the voice volume of a speaker in this particular example.
In some embodiments, a negative weight may be assigned to a relevant input, such as in the case of a participant who is preoccupied with a laptop and who makes limited eye contact during the video session. In some embodiments, face recognition may also be used to assign weights. In other instances, face recognition can be coupled to a directory (e.g., in order to access an organizational hierarchy) that assigns an employment title a certain weight. The weighted values can be summed at 230. The process ends at 235, where the weighted values may be passed to another process (e.g., such as 130 in flowchart 100).
In terms of a practical extension to the scenario involving the activities of flowchart 100, the following example is provided. In this example, the values extracted from the participation history represent voice level and body language. Voice level may be normalized within an integer range, such as 1-100, which indicates how loud a participant is speaking. Body language may also be characterized by an integer range from 1-100, which represents how engaged a participant may be based on head movement, slouching, hand and arm gestures, or any other recognizable attribute. Both of these numbers may be generated by an endpoint and embedded in a media packet sent to a multipoint manager element for additional processing. Alternatively, these inputs may simply be monitored and identified by multipoint manager elements 20, 50, which can have the intelligence to suitably detect various input levels. The numerical values are indicative of participation levels and, therefore, dictate the virtual positions of the end users.
In this example, voice level has been identified as a stronger indicator of participation than body language, so voice level has been assigned a weight of 0.75 and body language has been assigned a weight of 0.25. Participation level module 56 a may monitor the voice level and body language data at any suitable interval. Each time data is sampled, the values may be weighed and combined to calculate a participation value for each participant.
Thus, at an example time T, participation level module 56 a is configured to monitor the participation data, which indicates: (1) participant A has a voice level of 75 and a body language of 20; (2) participant B has a voice level of 10 and a body language of 70; (3) participant C has a voice level of 60 and a body language of 10; and (4) participant D has a voice level of 80 and a body language of 60. Based on this participation data, the participation value of participant A is calculated as 61.25 (0.75*75+0.25*20). Similarly, the participation value of participant B is calculated as 25 (0.75*10+0.25*70), participant C is 47.5 (0.75*60+0.25*10), and participant D is 75 (0.75*80+0.25*60). These values can be used to intelligently adjust the images on corresponding screens during a video conference.
FIG. 6 is a simplified flowchart 300 illustrating one potential operation associated with analyzing participation values, as may be done in step 130 of flowchart 100. The operations may begin at 305, where a given manager element can access, evaluate, or otherwise receive participation values. At 310, active participants may be identified. In one embodiment, active participants are distinguished from passive participants based on a threshold participation value 311. The threshold participation value may itself be preconfigured, static, or dynamic in various embodiments. A dynamic threshold value, in one embodiment, is a threshold value that may be adjusted during the course of a meeting to accommodate varying participation levels. Additionally, historic participation levels can be used in this dynamic adjustment, or appropriate feedback mechanisms can be used (e.g., a manager that manually adjusts settings for image rendering based on his assessment of who is most attentive in the meeting).
After identifying active participants, the virtual position of each active participant is identified to determine if more than one active participant occupies a single virtual position. This is shown at 315. If no virtual position is overloaded with active participants, no action is taken and the process ends at 330. If at least one virtual position is overloaded, then other virtual positions are analyzed to determine if any such virtual position is occupied by inactive participants at 320. For purposes of illustration, a virtual position occupied by inactive participants is referred to here as an “inactive position.” If an inactive position is available, then one of the participants in the inactive position may be switched with (i.e., displaced by) an active participant in an overloaded virtual position, as shown at 325. Preferably, the least active participant in an inactive position is switched. The process ends at 330, where the virtual position assignments may be passed to another process (e.g., passed to 135 in flowchart 100). Hence, the system has used participation levels to effectively render the appropriate images (during the video session) on the corresponding displays such that a more lifelike meeting experience is achieved.
Note that with the examples provided above, as well as numerous other examples provided herein, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that communication system 10 (and its teachings) are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of communication system 10 as potentially applied to a myriad of other architectures. Additionally, although described with reference to particular scenarios, where a particular module, such as a participation level module, is provided within a network element, these modules can be provided externally, or consolidated and/or combined in any suitable fashion. In certain instances, such modules may be provided in a single proprietary unit.
monitoring a plurality of end users, wherein each user generates a plurality of inputs and the end users are involved in a video session in which a plurality of displays are used, wherein at least one of the inputs is associated with a frequency of speech of the end users;
determining a participation level for each of the end users based on the inputs; and
determining which image data associated with the end users is to be rendered on a selected one of the plurality of displays based on the participation levels.
2. The method of claim 1, wherein the determining of the participation level includes calculating numeric values associated with the participation levels, and wherein the numeric values are used to assign virtual positions for the end users during the video session.
3. The method of claim 1, wherein one of the participation levels of the end users is preconfigured to have a base level that is higher than the participation levels of the other end users, and wherein the base level is set in accordance with an identity of one of the end users.
4. The method of claim 1, wherein the inputs include body language characteristics and eye gaze metrics of the end users.
5. The method of claim 1, wherein the inputs include a volume of speech associated with the end users.
6. The method of claim 1, wherein the inputs are weighted differently in order to determine the participation levels for each of the end users.
7. The method of claim 1, wherein the participation levels can be adjusted by an administrator during the video session.
9. The logic of claim 8, wherein the determining of the participation level includes calculating numeric values associated with the participation levels, and wherein the numeric values are used to assign virtual positions for the end users during the video session.
10. The logic of claim 8, wherein one of the participation levels of the end users is preconfigured to have a base level that is higher than the participation levels of the other end users, and wherein the base level is set in accordance with an identity of one of the end users.
11. The logic of claim 8, wherein a higher participation level for a selected one of the end users is prioritized over a lower participation level for another one of the end users.
12. The logic of claim 8, wherein the inputs include body language characteristics and eye gaze metrics of the end users.
13. The logic of claim 8, wherein the inputs include a volume of speech associated with the end users.
a participation module; and
a processor operable to execute instructions associated with the data, wherein the processor, the participation module, and the memory element cooperate in order to:
determine a participation level for each of the end users based on the inputs; and
determine which image data associated with the end users is to be rendered on a selected one of the plurality of displays based on the participation levels.
15. The apparatus of claim 14, wherein the determining of the participation level includes calculating numeric values associated with the participation levels, and wherein the numeric values are used to assign virtual positions for the end users during the video session.
16. The apparatus of claim 14, wherein one of the participation levels of the end users is preconfigured to have a base level that is higher than the participation levels of the other end users, and wherein the base level is set in accordance with an identity of one of the end users.
17. The apparatus of claim 14, wherein the inputs include body language characteristics and eye gaze metrics of the end users.
18. The apparatus of claim 14, wherein the inputs include a volume of speech associated with the end users.
19. The apparatus of claim 14, wherein the inputs are weighted differently in order to determine the participation levels for each of the end users.
20. The apparatus of claim 14, wherein the participation levels can be adjusted by an administrator during the video session.
US12963324 2010-12-08 2010-12-08 System and method for exchanging information in a video conference environment Active 2031-08-15 US8446455B2 (en)
US12963324 US8446455B2 (en) 2010-12-08 2010-12-08 System and method for exchanging information in a video conference environment
US20120147123A1 true US20120147123A1 (en) 2012-06-14
US8446455B2 true US8446455B2 (en) 2013-05-21
ID=46198963
US12963324 Active 2031-08-15 US8446455B2 (en) 2010-12-08 2010-12-08 System and method for exchanging information in a video conference environment
US (1) US8446455B2 (en)
US3519744A (en) 1967-06-16 1970-07-07 Bell Telephone Labor Inc Apparatus for connecting visual telephone sets in a conference arrangement
US3718770A (en) 1971-08-05 1973-02-27 Bell Telephone Labor Inc Key telephone system wideband conferencing arrangement
US4267593A (en) 1979-06-15 1981-05-12 Wescom Switching, Inc. Method and means for digital conferencing
US20040264390A1 (en) * 2003-06-27 2004-12-30 Brother Kogyo Kabushiki Kaisha Television conference system
US20050050154A1 (en) 1999-09-08 2005-03-03 Xerox Corporation Interactive context preserved navigation of graphical data sets using multiple physical tags
US20090009587A1 (en) 2007-07-02 2009-01-08 David Jordan Lindbergh Tag-aware multipoint switching for conferencing
US20100182394A1 (en) 2007-09-28 2010-07-22 Wuzhou Zhan Method, system, and device of video communication
US20120147123A1 (en) 2010-12-08 2012-06-14 Cisco Technology, Inc. System and method for exchanging information in a video conference environment
"LG Electronics Unveils New Push-To-View Technology," Mobiledia, Feb. 14, 2005, 3 pages; http://www.mobiledia.com/news/25797.html.
"Samsung Demonstrates Push-To-All Technology," Samsung.com, Feb. 25, 2005, 1 page; http://www.samsung.com/us/news/newsPreviewRead.do?news-seq=2564.
"Samsung Demonstrates Push-To-All Technology," Samsung.com, Feb. 25, 2005, 1 page; http://www.samsung.com/us/news/newsPreviewRead.do?news—seq=2564.
Davis, Andrew, "Video Communications Industry Backgrounder," Wainhouse Research, 4 pages; [Retrieved and printed on Dec. 7, 2010] www.tandberg.net.
Froba, B., et al., "Rapid Hand Gesture Detection for Human Computer interface," (Abstract Only) Computer Graphics and Imaging-2002, 1 page; http://www.actapress.com/PaperInfo.aspx?PaperID=25959.
Froba, B., et al., "Rapid Hand Gesture Detection for Human Computer interface," (Abstract Only) Computer Graphics and Imaging—2002, 1 page; http://www.actapress.com/PaperInfo.aspx?PaperID=25959.
Johanson, Brad, et al., "Multibrowsing: Moving Web Content across Multiple Displays," Proc. Ubiquitous Computing Conference (UBICOMP), 2001, 9 pages; http://www.graphics.stanford.edu/papers/imultibrowsing/multibrowse-paper.html.
Johanson, Brad, et al., "Multibrowsing: Moving Web Content across Multiple Displays," Proc. Ubiquitous Computing Conference (UBICOMP), 2001, 9 pages; http://www.graphics.stanford.edu/papers/imultibrowsing/multibrowse—paper.html.
Lambert, Dave, "Polycom Video Communications," ©2004 Polycom, Inc., Jun. 20, 2004, 4 pages; http://www.polycom.com/global/documents/whitepapers/video-communications-h.239-people-content-polycom-patented-technology.pdf.
Lambert, Dave, "Polycom Video Communications," ©2004 Polycom, Inc., Jun. 20, 2004, 4 pages; http://www.polycom.com/global/documents/whitepapers/video—communications—h.239—people—content—polycom—patented—technology.pdf.
Quemada, Juan, et al., "Isabel: An Application for real time Collaboration with a flexible Floor Control," Collaborative Computing: Networking, Applications and Worksharing, 2005 International Conference; 9 pages; http://ieeexplore.ieee.org/iel5/10986/34623/01651238.pdf.
U.S. Appl. No. 12/963,387, entitled "System and Method for Controlling Video Data to be Rendered in a Video Conference Environment," filed Dec. 8, 2010; Inventor(s) Alan J. MacDonald et al.
USPTO Mar. 6, 2013 Non-Final Office Action from U.S. Appl. No. 12/963,387.
Weinstein, Ira, et al. "Emerging Technologies for Teleconferencing and Telepresence," Wainhouse Research, 2005, 54 pages. http://www.wrplatinum.com/content.aspx?Relo=1&CID=4382.
Ylitalo, Jukka, et al., "Re-thinking Security in IP based Micro-Mobility," 2005, 12 pages; www.tcs.hut.fi/Studies/T-79.5401/2005 AUT/ISC04- Vlitalo-4-al.pdf.
US20120147123A1 (en) 2012-06-14 application
US20070121530A1 (en) 2007-05-31 Method and apparatus for conference spanning
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIAN, TIONGHU;DUNN, CHRIS A.;BALDINO, BRIAN J.;REEL/FRAME:025467/0442