IP Library Granted Patent US 10,050,749
Granted Patent B2
US 10,050,749 · App. 15/702,238 · Granted Aug 14, 2018

Video conference bridge setting sharing, pushing, and rationalization

Inventors: Amit Mishra (Pune, IN); Srinivasan Narayanan (Pune, IN); Anand Paithankar (Nanded, IN)
Assignee: Avaya Inc.
H04L1/1867G06F11/1443H04L12/1818H04L65/1069H04L65/403H04L65/80H04M3/567H04N7/15
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,050,749
App. No.
15/702,238
Granted
Aug 14, 2018
Kind
B2
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 (34)

1. A communication system, comprising:

a first multipoint control unit (MCU) in communication with a first communication endpoint, the first MCU comprising:

a memory operable to store first conference settings for the first communication endpoint, wherein the first conference settings for the first communication endpoint are used by the first MCU to configure the first communication endpoint to communicate with the first MCU in the first conference;

a processor in communication with the memory, the processor operable to execute a second conference associated with the first communication endpoint in accordance with the first conference settings, wherein the first conference settings for the first communication endpoint are used by the first MCU to configure the first communication endpoint to communicate with the first MCU in the second conference;

a second MCU in communication with the first MCU, the second MCU comprising:

a second memory operable to store the first conference settings for the first communication endpoint, wherein the first conference settings for the first communication endpoint are received from the first MCU;

a second processor in communication with the second memory, the second processor operable to:

normalize the first conference settings; and

execute a third conference associated with the first communication endpoint in accordance with the normalized first conference settings, wherein the normalized first conference settings for the first communication endpoint are used by the second MCU to configure the first communication endpoint to communicate with the second MCU in the third conference.

2. The communication system as defined in claim 1 , further comprising:

a second communication endpoint in communication with the second MCU;

wherein the second memory stores second conference settings for the second communication endpoint; and

wherein the second MCU sends the second conference settings to the first MCU.

3. The communication system as defined in claim 2 , wherein the second memory stores endpoint characteristics for the first communication endpoint and the second communication endpoint.

4. The communication system as defined in claim 3 , wherein the second memory stores endpoint call characteristics for the first communication endpoint and the second communication endpoint.

5. The communication system as defined in claim 4 , wherein the endpoint characteristics and the endpoint call characteristics are associated with the first conference settings or the second conference settings, and wherein the first conference settings are received by an RTP communication or other proprietary mechanism from the first MCU during the first conference.

6. The communication system as defined in claim 1 , wherein the first conference settings for the first communication endpoint comprise a type of codec used by the first communication endpoint in the first conference.

7. The communication system as defined in claim 6 , wherein the type of codec used by the first communication endpoint is one of a plurality of codecs supported by the first communication endpoint.

8. The communication system as defined in claim 1 , wherein the normalized first conference settings for the first communication endpoint that are used by the second MCU to configure the first communication endpoint to communicate with the second MCU in the third conference are based on a physical separation between the first communication endpoint and the second MCU.

9. The communication system as defined in claim 1 , wherein the second MCU sends the normalized first conference settings to the first communication endpoint in the third conference.

10. The communication system as defined in claim 1 , wherein the normalized first conference settings for the first communication endpoint that are used by the second MCU to configure the first communication endpoint to communicate with the second MCU in the third conference comprise a different codec setting.

11. A method, comprising:

storing, by a microprocessor in a first multipoint control unit (MCU), first conference settings for a first communication endpoint, wherein the first conference settings for the first communication endpoint are used by the first MCU to configure the first communication endpoint to communicate with the first MCU in the first conference;

executing, by the microprocessor, a second conference associated with the first communication endpoint in accordance with the first conference settings, wherein the first conference settings for the first communication endpoint are used by the first MCU to configure the first communication endpoint to communicate with the first MCU in the second conference;

sending, by the microprocessor, the first conference settings for the first communication endpoint to a second MCU, wherein the second MCU normalizes the first conference settings for the first communication endpoint, wherein the second MCU executes a third conference associated with the first communication endpoint in accordance with the normalized first conference settings, wherein the normalized first conference settings for the first communication endpoint are used by the second MCU to configure the first communication endpoint to communicate with the second MCU in the third conference.

12. The method as defined in claim 11 , wherein a second communication endpoint is in communication with the second MCU, wherein the second MCU stores second conference settings for the second communication endpoint, and wherein the second MCU sends the second conference settings to the first MCU.

13. The method as defined in claim 12 , wherein the second MCU stores endpoint characteristics for the first communication endpoint and the second communication endpoint.

14. The method as defined in claim 13 , wherein the second MCU stores endpoint call characteristics for the first communication endpoint and the second communication endpoint.

15. The method as defined in claim 14 , wherein the endpoint characteristics and the endpoint call characteristics are associated with the first conference settings or the second conference settings, and wherein the first conference settings are received by an RTP communication or other proprietary mechanism from the first MCU during the first conference.

16. The communication system as defined in claim 11 , wherein the first conference settings for the first communication endpoint comprise a type of codec used by the first communication endpoint in the first conference.

17. The communication system as defined in claim 16 , wherein the type of codec used by the first communication endpoint is one of a plurality of codecs supported by the first communication endpoint.

18. The communication system as defined in claim 11 , wherein the normalized first conference settings for the first communication endpoint that are used by the second MCU to configure the first communication endpoint to communicate with the second MCU in the third conference are based on a physical separation between the first communication endpoint and the second MCU.

19. The communication system as defined in claim 11 , wherein the second MCU sends the normalized first conference settings to the first communication endpoint in the third conference.

20. The communication system as defined in claim 11 , wherein the normalized first conference settings for the first communication endpoint that are used by the second MCU to configure the first communication endpoint to communicate with the second MCU in the third conference comprise a different codec setting.

Assignments (15)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 4, 2024
From: AVAYA LLC
To: ARLINGTON TECHNOLOGIES, LLC
Reel/Frame 067022/0780 →
INTELLECTUAL PROPERTY RELEASE AND REASSIGNMENT Recorded Mar 25, 2024
From: CITIBANK, N.A.
To: AVAYA LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 066894/0117 →
INTELLECTUAL PROPERTY RELEASE AND REASSIGNMENT Recorded Mar 25, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: AVAYA LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 066894/0227 →
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 5, 2018
From: MISHRA, AMIT; NARAYANAN, SRINIVASAN; PAITHANKAR, ANAND
To: AVAYA INC.
Reel/Frame 045450/0492 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
Continuity (3)
Division 13103230 · May 9, 2011
Division 14085506 · Nov 20, 2013
Related Publication 20180006772A1 · Jan 4, 2018