Video conference bridge setting, sharing, pushing, and rationalization

• US 9,787,441 B2
• Filed: 11/20/2013
• Issued: 10/10/2017
• Est. Priority Date: 05/09/2011
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Mishra, Amit, Narayanan, Srinivasan, Paithankar, Anand
• Primary Examiner(s): Nguyen, Joseph J
• Application Number:
  US14/085,506
• Publication Number:
  US 20140082416A1
• Time in Patent Office: 1,420 Days
• CPC Class Codes: G06F 11/1443 Transmit or communication errors
• CPC Class Codes: H04L 1/1867 Arrangements specially adapted for the transmitter end
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04M 3/567 Multimedia conference systems
• CPC Class Codes: H04N 7/15 Conference systems

Abstract

A conference system is provided with enhanced settings capabilities. A controller can poll for settings at each endpoint in a conference system and be able via the video stream to selectively display and compare settings among the endpoints. One location can push its settings to one or more locations to overcome failures or degradation in the conference. The settings between different controllers may be rationalized via a common denominator method or tabular method to build a knowledge of how to configure conferences and to automate responses to problems.

Claims

1. A method for recovering from a failure during a conference, comprising:

establishing, by a microprocessor in a Multipoint Control Unit (MCU), a conference with a first set of conference settings, wherein the conference is a conference between a plurality of communication endpoints;

storing, by the microprocessor, the first set of conference settings, wherein the first set of conference settings comprise a type of codec used by a first communication endpoint in the conference, wherein the type of codec used by the first communication endpoint in the conference is made a default setting based on a previous successful conference;

detecting, by the microprocessor, the failure during the conference;

recovering from the failure, by the microprocessor, during the conference, wherein recovering from the failure during the conference comprises;

sending, to the first communication endpoint, the type of codec used by the first communication endpoint before the failure during the conference, wherein the first communication endpoint comprises a plurality of codecs; and

reestablishing, by the microprocessor, the conference using the first set of conference settings.

2. The method as defined in claim 1, wherein the failure is a failure of the first communication endpoint and the first communication endpoint loses the type of codec used by the first communication endpoint before the failure.

3. The method as defined in claim 2, wherein reestablishing the conference comprises detecting that the first communication endpoint has recovered from the failure and resending at least one other conference setting of the first set of conference settings to the first communication endpoint.

4. The method as defined in claim 1, wherein the failure is a failure of the MCU and the first communication endpoint reestablishes the conference using the type of codec used by the first communication endpoint before the failure with a second MCU.

5. The method as defined in claim 4, wherein the second MCU provides a second set of conference settings for the first communication endpoint, and wherein the second set of conference settings are different from the first set of conference settings.

6. The method as defined in claim 1, wherein sending the type of codec used by the first communication endpoint further comprises sending a setting for the type of codec.

7. The method as defined in claim 6, wherein the setting for the type of codec is based on a packet delay.

8. The system as defined in claim 6, wherein the setting for the type of codec is based on a Quality of Service measure.

9. The method as defined in claim 1, wherein the first set of conference settings further comprises delay information about which communication endpoints are involved in the conference.

10. The method as defined in claim 1, wherein the first set of conference settings further comprises jitter measures.

11. A system comprising:

a microprocessor; and

a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that program the microprocessor to execute;

a Multipoint Control Unit (MCU) that establishes a conference with a first set of conference settings, wherein the conference is a conference between a plurality of communication endpoints, stores the first set of conference settings, wherein the first set of conference settings comprise a type of codec used by a first communication endpoint in the conference, wherein the type of codec used by the first communication endpoint in the conference is made a default setting based on a previous successful conference, detects the failure during the conference, recovers from the failure during the conference by sending, to the first communication endpoint, the type of codec used by the first communication endpoint before the failure during the conference, wherein the first communication endpoint comprises a plurality of codecs, and reestablishes the conference using the first set of conference settings.

12. The system as defined in claim 11, wherein the failure is a failure of the first communication endpoint and the first communication endpoint loses the type of codec used by the first communication endpoint before the failure.

13. The system as defined in claim 12, wherein reestablishing the conference comprises detecting that the first communication endpoint has recovered from the failure and resending at least one other conference setting of the first set of conference settings to the first communication endpoint.

14. The system as defined in claim 11, wherein the failure is a failure of the MCU and the first communication endpoint reestablishes the conference using the type of codec used by the first communication endpoint before the failure with the MCU.

15. The system as defined in claim 14, wherein a second MCU provides a second set of conference settings for the first communication endpoint, and wherein the second set of conference settings are different from the first set of conference settings.

16. The system as defined in claim 11, wherein sending the type of codec used by the first communication endpoint further comprises sending a setting for the type of codec.

17. The system as defined in claim 16, wherein the setting for the type of codec is based on a packet delay.

18. The system as defined in claim 16, wherein the setting for the type of codec is based on a Quality of Service measure.

19. The system as defined in claim 11, wherein the first set of conference settings further comprises delay information about which communication endpoints are involved in the conference.

20. The system as defined in claim 11, wherein the first set of conference settings further comprises jitter measures.