U.S. patent application number 09/919538 was filed with the patent office on 2003-02-06 for system and method for managing video network devices.
This patent application is currently assigned to VTEL Corporation. Invention is credited to Babka, James Joseph, Seebaldt, Kurtis L..
Application Number | 20030028679 09/919538 |
Document ID | / |
Family ID | 25442277 |
Filed Date | 2003-02-06 |
United States Patent
Application |
20030028679 |
Kind Code |
A1 |
Babka, James Joseph ; et
al. |
February 6, 2003 |
System and method for managing video network devices
Abstract
A video network platform manages video network devices with
management applications, such as scheduling, monitoring and
diagnostics applications, by representing the devices as interface
objects that support a network interface module, and application
objects used by the management applications and created by an
adapter engine that creates an application object for each
corresponding video network device interface object. A network
interface module associated with the video network platform invokes
the adapter engine to create an application object associated with
a device. The application object uses its dynamic attribute query
capabilities to build an interface object in the network interface
module and thus obtain device attributes such as device address
information. The application module populates itself with device
information for supporting management applications, thus allowing
conventional network interface modules to cooperate with
application specific objects.
Inventors: |
Babka, James Joseph; (Round
Rock, TX) ; Seebaldt, Kurtis L.; (Round Rock,
TX) |
Correspondence
Address: |
BAKER BOTTS L.L.P.
PATENT DEPARTMENT
98 SAN JACINTO BLVD., SUITE 1500
AUSTIN
TX
78701-4039
US
|
Assignee: |
VTEL Corporation
|
Family ID: |
25442277 |
Appl. No.: |
09/919538 |
Filed: |
July 31, 2001 |
Current U.S.
Class: |
719/310 ;
348/E7.084 |
Current CPC
Class: |
H04N 21/2408 20130101;
H04N 21/241 20130101; H04N 7/152 20130101; H04N 21/25808
20130101 |
Class at
Publication: |
709/310 |
International
Class: |
G06F 009/54; G06F
009/00 |
Claims
What is claimed is:
1. A video network platform for managing video network devices, the
video network platform comprising: a network interface module
operable to interface with the devices and to represent a device as
an interface object; one or more management applications operable
to manage a device represented as an application object; and an
adapter engine associated with the network interface module, the
adapter engine operable to create an application object for a
device, the application object corresponding to the interface
object for the device.
2. The video network platform of claim 1 further comprising: an
override interface object associated with the network interface,
the override object operable to accept a request meant for an
interface object and to direct the request to an application object
corresponding to the interface object.
3. The video network platform of claim 1 further comprising: a
discovery engine associated with the network interface, the
discovery engine operable to detect devices and initiate creation
of an object to represent a detected device.
4. The video network platform of claim 3 wherein the discovery
engine initiates creation of an application object by the adapter
engine, the adapter engine further operable to initiate creation of
a corresponding interface object by the network interface.
5. The video network platform of claim 4 wherein the adapter engine
incorporates attributes of the interface object into the
corresponding application object.
6. The video network platform of claim 1 wherein the interface
object comprises a managed object.
7. The video network platform of claim 1 wherein the application
object comprises a Management Bean.
8. The video network platform of claim 1 wherein the management
application comprises a scheduling application.
9. The video network platform of claim 1 wherein the management
application comprises a diagnostics application.
10. The video network platform of claim 1 wherein the management
application comprises a monitoring application.
11. A method for managing video network devices, the method
comprising: detecting a video device interfaced with the network;
creating an application object for the device; applying the
application object to build an interface object corresponding to
the application object, the interface object obtaining interface
information from the device; forwarding the interface information
to the application object; and populating the application object
with device information.
12. The method of claim 11 wherein the application object comprises
a Java management bean.
13. The method of claim 11 wherein the application object comprises
a Web NMS Managed Object.
14. The method of claim 11 further comprising: interfacing a
management application with a device through the application object
corresponding with the device.
15. The method of claim 14 wherein the management application
comprises a scheduling application.
16. The method of claim 14 wherein the management application
comprises a diagnostics application.
17. The method of claim 14 wherein the management application
comprises a monitoring application.
18. The method of claim 11 wherein applying the application object
to build an interface object further comprises: applying dynamic
attribute query capabilities to populate a corresponding interface
object.
19. The method of claim 11 wherein applying the application object
to build an interface object further comprises: creating an
interface object that corresponds to the application object.
Description
TECHNICAL FIELD
[0001] This invention relates generally to video network
communications, and more specifically relates to a system and
method for managing video network devices.
BACKGROUND OF THE INVENTION
[0002] Video conference calls have grown in popularity as the
expense of video conferencing devices has decreased and the
availability of broadband communication networks has increased.
Businesses often prefer the more personal communication available
through video conferences compared with telephone conferences, and
also enjoy savings in travel costs while still having a personal
presence among the participants that is not possible with audio
only communications. The increased popularity of video conferencing
has resulted in the deployment of video network devices in wide
ranging disparate locations with the devices interfaced by business
networks or the public network. Often, video calls involve the
interfacing of video network devices manufactured by a variety of
different manufacturers and using a variety of protocols and
network communication interfaces.
[0003] As video network devices grow in number, the task of
scheduling, monitoring and diagnosing problems of the devices grows
in complexity. For instance, a single video network might interface
with video end points, multi-call units (MCUs), and gateways each
manufactured by different manufacturers and using different
communication protocols. Each of these devices may include specific
management, maintenance and monitoring needs that makes central
management of a network difficult to accomplish.
[0004] One difficulty with management of video devices is
establishing a uniform representation of the devices for use by
management applications. Without a uniform means of communicating
with different types of devices, management applications generally
must be updated as devices on the video network are changed or
reconfigured. Thus, video network operational staff is typically
faced with a complex task of maintaining video networks by tracking
changes to the network and updating management applications and
devices on an individual basis. This increases the cost and
complexity of video networks and also results in reduced
reliability.
SUMMARY OF THE INVENTION
[0005] Therefore a need has arisen for a system and method which
manages video network devices through a centralized video network
platform.
[0006] A further need has arisen for a system and method which
provides a uniform representation of different types of video
network devices to reduce the complexity of managing the different
types of video network devices with management applications.
[0007] In accordance with the present invention, a system and
method are provided which substantially reduce the problems and
disadvantages of managing video network devices. A video network
platform includes a network interface operable to represent video
devices as interface objects. An adapter engine associated with the
network interface creates application objects for video devices
that correspond with the interface objects. Management applications
use the application objects to manage the video devices from the
video network platform.
[0008] More specifically, a network interface module provides a
uniform communication interface for the video network platform to
communicate with the video network, such as the WebNMS interface
commercially available from AdventNet for interfacing servers with
internet networks. The network interface module represents devices
of the network as interface objects, such as the managed objects of
WebNMS, with attribute get and set methods that are generic in
nature and that provide access to device attributes as sets of name
value pairs. A discovery engine associated with the network
interface module interrogates devices on the network to allow
creation of interface objects with appropriate attributes when a
device is added to or changed on the network.
[0009] An adapter engine communicates with the network interface
module and is called when the video network platform seeks to
represent a device on the video network. For instance, a network
operator who adds a device to the video network may initiate a call
to the adapter engine, or the discovery engine may initiate a call
to the adapter engine if a new device is detected on the network.
The adapter engine creates an application object and invokes the
network interface module to create a corresponding interface
object. The network interface module interrogates the device and
populates the interface object with appropriate attributes. The
adapter engine applies the interface object attributes to the
corresponding application object and the application object is then
able to directly interrogate the device to populate attributes of
the application object. For instance, the interface object is
populated with attributes to identify the address and device type.
These interface object attributes are forwarded to the application
object to allow a direct interface for the application object to
obtain desired attributes.
[0010] Management applications associated with the video network
platform perform management functions using the application object
representations of devices. In some instances, management
application queries to the network interface module for interface
objects that represent video devices are intercepted by a special
kind of interface object known as an override interface object. The
override interface object takes interface object requests and
forwards them to an application object that corresponds with the
requested interface object. Override interface objects enable
additional functionality for existing management applications that
use interface objects to communicate with devices. An override
interface object references to a corresponding application object
which in turn enables additional functionality otherwise not
available through an interface object. Thus, existing management
applications that use interface objects are easily adapted to use
application objects by re-directing requests with an override
interface object.
[0011] The present invention provides a number of important
technical advantages. One important technical advantage is that the
video network platform allows centralized management of video
devices of different types. Management applications for performing
such functions as scheduling, diagnostics and monitoring of video
network devices access the application object to perform the
management function. Application objects that are independent from
the interface objects provide greater flexibility for the use of
standardized network interfaces to reduce cost and complexity with
application objects available to provide information for specific
functionality.
[0012] Another important technical advantage of the present
invention is that the video network platform is flexible to adapt
for managing different types of network devices and new management
applications without substantially rearchitecting the interface
between the video network platform and the network devices. The
adapter engine creates application objects with needed attributes
for a given application without affecting the video network
platform's interface with the network devices. Instead, the
application objects are modified to handle necessary attributes
independent of the interface objects and the override object
directs queries from management applications for interface objects
to the application objects with the desired attributes.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] A more complete understanding of the present embodiments and
advantages thereof may be acquired by referring to the following
description taken in conjunction with the accompanying drawings, in
which like reference numbers indicate like features, and
wherein:
[0014] FIG. 1 depicts a block diagram of a video network platform
interfaced with a video call network;
[0015] FIG. 2 depicts a flow diagram of a process for creating and
populating application objects; and
[0016] FIG. 3 depicts a flow diagram for a process of interfacing a
management application with a video network platform.
DETAILED DESCRIPTION OF THE INVENTION
[0017] Preferred embodiments of the present invention are
illustrated in the figures, like numerals being used to refer to
like and corresponding parts of the various drawings.
[0018] Management of video network devices from a central video
network platform offers the advantage of applying applications for
scheduling, diagnostics, and monitoring of the devices even if the
devices are of different types. Conventional network management
systems, such as WebNMS from AdventNet, provide a suitable
interface for a video network platform with an internet
architecture to allow management communication between applications
and video devices. However, conventional network interface modules
like WebNMS represent network devices as managed objects that are
generic in nature. These managed objects provide good interface
objects for a wide range of network devices but due to the
proprietary nature of the network interface module they lack the
flexibility for adapting to specific devices and applications
without access to the source code of the network interface
module.
[0019] One standard for management of devices in Java, called JMX,
defines Management Beans, or Mbeans, to represent devices for
management. The JMX standard provides a variety of functions to
operate on Mbeans and are thus more flexible as application objects
for management applications to manage network devices. The Mbeans
encapsulate operational attributes of the devices for the
management applications to access and use. Thus, Mbeans offer
advantages as application objects over the use of managed objects
created to act as interface objects by a network interface module
such as WebNMS.
[0020] To take advantage of the cost savings and simplicity of a
conventional network interface module as well as the flexibility of
application specific object standards, the present invention
"hijacks" interface objects and creates corresponding application
objects for managing devices with management applications.
Referring now to FIG. 1, a video network platform 10 provides an
interface between management applications, including scheduling
application 12, diagnostics application 14 and monitoring
application 16, and network devices, including end point 18,
gateway 20 and MCU 22. Video network platform 10 communicates with
management applications and video network devices through a network
24, such as the internet or another TCP/IP based network.
[0021] Video network platform 10 supports a network interface
module 26 and an adapter engine 28. Network interface module 26 is
a commercially available network management system, such as Web
NMS, which manages network devices as represented by interface
objects 30. In the example of Web NMS, interface objects 30 are
called "managed objects" and have generic get properties and set
properties methods that provide access to device attributes as sets
of name/value pairs. Network interface module 26 includes a
discovery engine 32 which is operable to detect network devices and
create interface objects with appropriate attributes.
[0022] Adapter engine 28 communicates with network interface module
26 to ensure that network devices represented by interface objects
are also represented by a corresponding application object 34, such
as a Mbean. For instance, if discovery engine 32 detects a new
network device or an operator adds a network device, then a request
is sent to adapter engine 28 to create a new application object
corresponding to the new device. The adapter engine 28 then uses
the dynamic attribute query capabilities of the application object
to build an interface object corresponding to the device in the
network interface module 26. For instance, the application object
populates an existing shell interface object, such as an interface
object created by the discovery engine, with information.
Alternatively, the adapter engine may initiate creation of a
corresponding interface object. The new interface object 30 obtains
basic information that is available via attribute get and set
methods from the device, such as the device address and class type,
and this information is then forwarded to the corresponding
application object. Once the application object 34 has the
interface object attributes, application object 34 then is able to
obtain detailed device attributes directly from the device. This
method of creating the corresponding application and interface
objects ensures a reference to each other.
[0023] Once the application object is populated with the device
attributes, new management applications can access the application
objects to manage the network devices, while existing management
applications can access application objects through corresponding
override interface objects. If a request comes to an interface
object from an existing application that uses interface objects,
then the interface object acts as an override interface object 36
by accepting the request and overriding the methods of the
requested interface object to determine whether a corresponding
application object should be used instead. The override interface
object 36 takes the attribute names of the request and invokes the
appropriate method on the corresponding application object 34 to
determine if the application object supports the requested
attribute. If the application object supports the requested
attribute, it invokes the appropriate method on the device to
perform the gets or sets. If not, then override interface object 36
provides the attributes via the existing interface object
mechanisms.
[0024] Referring now to FIG. 2, a flow diagram depicts a process
for creating application objects and interface objects to support
devices of a video network. At step 38, the discovery engine
detects the network device interfaced with the network and invokes
the adapter engine. At step 40, the adapter engine creates an
application object corresponding to the detected device. At step
42, the adapter engine uses the dynamic attribute query capability
of the created application object to build an interface object in
the network interface module.
[0025] In some instances, a network operator may desire to input a
new device manually through the adapter engine. At step 44, the
adapter engine advertises the new device to the network interface
module and the network interface module creates an interface object
for the class of devices. At step 46, the discovery engine detects
network devices of the requested class and invokes the adapter
engine if devices are detected. At step 48, the adapter engine
creates application objects corresponding to the interface objects
of the detected devices.
[0026] Once the device or devices are detected, the interface
object populates the device attribute get and set methods and
forwards this information to the application object. Included in
the information forwarded to the application object is the address
of the device or devices so that the application object can
directly contact and communicate with the device. At step 52, the
application object applies the device address as forwarded by the
interface object and populates the device application attributes
with the detailed device information needed for management of the
device by the management applications. Because the application
objects are flexible and accessible for programming, the set of
attributes for the devices is flexible to allow management of the
devices as appropriate. Further, different types of devices with
different types of information are easily represented for use by
management applications.
[0027] At step 54, the application object completes population of
the interface object attributes as needed. Since the application
object is flexible and capable of defining attributes for specific
applications and devices, it will act as the primary reference for
management applications to manage devices.
[0028] In some instances, requests for device management may come
as requests to interface objects. For instance, network 24 may
include non-video devices such as routers that are managed through
interface objects. In these cases, no override interface object
functionality is used, but instead the existing interface objects
defined for those devices are used.
[0029] Referring now to FIG. 3, a flow diagram depicts the process
by which an override interface object forwards video network device
requests to the corresponding application object. At step 56, a
request is received at the video network platform for the device as
an interface object. At step 58, the override interface object
invokes the requested method on the corresponding application
object if one exists. At step 60, a determination is made of
whether the method of the application object supports the requested
attributes. If the method supports the requested attributes, then
at step 62 the override interface object invokes the request
attributes on the corresponding application object. If the method
does not support the requested attributes, then at step 64, the
override interface object invokes the requested attributes on the
interface object. In this manner, requests appropriately addressed
to an interface object are processed by the network interface
module.
[0030] Although the present invention has been described in detail,
it should be understood that various changes, substitutions and
alterations can be made hereto without departing from the spirit
and scope of the invention as defined by the appending claims.
* * * * *