IP Library Granted Patent US 7,346,912
Granted Patent B2
US 7,346,912 · App. 10/212,400 · Granted Mar 18, 2008

Method and system for managing video devices

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 7,346,912
App. No.
10/212,400
Granted
Mar 18, 2008
Kind
B2
Abstract

Hot deployable video management modules maintain a video device management platform by integrating independently developed support for new or updated video devices at runtime. A video device module loader builds a management interface for the new or updated video device associated with the management module based on attributes and operations of the video device defined by an XML descriptor and based on access instructions. The management interface is used to create a video device instance in the management platform for each video device under management. The management platform manages a variety of different types of video devices with a video device management module added as a given video device is added to the management platform or an already managed video device is updated.

Claims (68)

1. A method for managing plural types of video teleconferencing devices configured to support video teleconferencing through a network, comprising:

defining within a video device management framework a video teleconferencing device management module for a first video teleconferencing device type, the video teleconferencing device management module having a corresponding first video teleconferencing device type description and one or more corresponding first video teleconferencing device type access modules,

the first video teleconferencing device type description including a list of first video teleconferencing device type attributes, and

each first video teleconferencing device type access module including instructions for managing one or more devices corresponding to the first video teleconferencing device type during at least one of scheduling, configuring and executing a video teleconference;

generating and storing a management interface for the first video teleconferencing device type from the first teleconferencing device type description and the first video teleconferencing device type access instructions;

detecting an addition of a second video teleconferencing device management module to the video device management framework with a video teleconferencing device module loader;

generating and storing a management interface for the second video teleconferencing device type from a corresponding second teleconferencing device type description including a list of second video teleconferencing device type attributes, and from corresponding second video teleconferencing device type access instructions; and

at least one of scheduling, configuring and executing a video teleconference between first and second video teleconferencing devices corresponding to at least one of the first and second video teleconferencing device types, wherein

said step of at least one of scheduling, configuring and executing a video teleconference includes one of

copying a stored management interface from the video device management framework to a video teleconference device management platform interfaced to the first and second video teleconferencing devices to create a corresponding video teleconferencing device instance, and

providing a run-time update to a video teleconferencing device instance already stored on the video teleconference device management platform.

2. The method of claim 1 , the step of generating a management interface comprising:

incorporating into the management interface device access instructions compliant with a standard protocol.

3. The method of claim 2 wherein the standard protocol comprises SNMP.

4. The method of claim 2 wherein the standard protocol comprises HTTP.

5. The method of claim 1 , wherein at least one of the first and second video teleconferencing devices are compliant with one of H.320 and H.323.

6. The method of claim 5 , wherein said first video teleconferencing device compliant with one of H.320 and H.323 comprises one of:

a first video teleconferencing endpoint;

a second video teleconferencing endpoint;

a video teleconferencing MCU;

a video teleconferencing gatekeeper; and

a video teleconferencing gateway.

7. The method of claim 5 , wherein the first and second video teleconferencing devices comprise:

a first video teleconferencing device made by a first manufacturer; and

a second video teleconferencing device made by a second manufacturer, respectively.

8. The method of claim 6 , wherein said second video teleconferencing device compliant with one of H.320 and H.323 comprises another of:

said first video teleconferencing endpoint;

said second video teleconferencing endpoint;

said video teleconferencing MCU;

said video teleconferencing gatekeeper; and

said video teleconferencing gateway.

9. The method of claim 1 , further comprising:

scanning a deployment directory within a video device management framework for a new or updated video device management module; and

deploying said new or updated video device management module.

10. A computer program stored in a computer readable storage medium, including instructions configured to cause a computer to implement a method of managing plural types of video teleconferencing devices supporting video teleconferencing through a network, comprising:

defining within a video device management framework a video teleconferencing device management module for a first vide teleconferencing device type, the video teleconferencing device management module having a corresponding first video teleconferencing device type description and one or more corresponding first video teleconferencing device type access modules,

the first video teleconferencing device type description including a list of first video teleconferencing device type attributes, and

each first video teleconferencing device type access module including instructions for managing the first video teleconferencing device type during at least one of scheduling, configuring and executing a video teleconference;

generating and storing a management interface for the first video teleconferencing device type from the first teleconferencing device type description and the first video teleconferencing device type access instructions;

detecting an addition of a second video teleconferencing device management module to the video device management framework with a video teleconferencing device module loader;

generating and storing a management interface for the second video teleconferencing device type from a corresponding second teleconferencing device type description including a list of second video teleconferencing device type attributes, and from corresponding second video teleconferencing device type access instructions; and

at least one of scheduling, configuring and executing a video teleconference between first and second video teleconferencing devices corresponding to at least one of the first and second video teleconferencing device types, wherein

said step of at least one of scheduling, configuring and executing a video teleconference includes one of

copying a stored management interface from the video device management framework to a video teleconference device management platform interfaced to the first and second video teleconferencing devices to create a corresponding video teleconferencing device instance, and

providing a run-time update to a video teleconferencing device instance already stored on the video teleconference device management platform.

11. The method of claim 10 , the step of generating a management interface comprising:

incorporating into the management interface device access instructions compliant with a standard protocol.

12. The method of claim 11 wherein the standard protocol comprises SNMP.

13. The method of claim 11 wherein the standard protocol comprises HTTP.

14. The method of claim 10 , wherein at least one of the first and second video teleconferencing devices are compliant with one of H.320 and H.323.

15. The method of claim 14 , wherein said first video teleconferencing device compliant with one of H.320 and H.323 comprises one of:

a first video teleconferencing endpoint;

a second video teleconferencing endpoint;

a video teleconferencing MCU;

a video teleconferencing gatekeeper; and

a video teleconferencing gateway.

16. The method of claim 14 , wherein the first and second video teleconferencing devices comprise:

a first video teleconferencing device made by a first manufacturer; and

a second video teleconferencing device made by a second manufacturer, respectively.

17. The method of claim 15 , wherein said second video teleconferencing device compliant with one of H.320 and H.323 comprise another of:

said first video teleconferencing endpoint;

said second video teleconferencing endpoint;

said video teleconferencing MCU;

said video teleconferencing gatekeeper; and

said video teleconferencing gateway.

18. The method of claim 10 , further comprising step for:

scanning a deployment directory within the video device management framework for a new or updated video device management module; and

deploying said new or updated video device management module.

Assignments (3)
CONFIRMATORY ASSIGNMENT Recorded Dec 1, 2011
From: TANDBERG TELECOM AS; CISCO SYSTEMS INTERNATIONAL SARL
To: CISCO TECHNOLOGY, INC.
Reel/Frame 027307/0451 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 5, 2005
From: FORGENT NETWORKS, INC.
To: TANDBERG TELECOM AS
Reel/Frame 015545/0634 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 5, 2002
From: SEEBALDT, KURTIS L.
To: FORGENT NETWORKS, INC.
Reel/Frame 013170/0254 →