Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1998-03-13
2002-09-03
Lintz, Paul R. (Department: 2777)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000, C707S793000, C707S793000
Reexamination Certificate
active
06446079
ABSTRACT:
FIELD OF THE INVENTION
This invention relates to communications network management systems and more particularly to a protocol for improving the retrieval of specified items of information from network management systems and managed elements.
BACKGROUND
Protocols used by communications Network Management Systems (NMSs) for retrieving information from managed elements (MEs) or other NMSs commonly define a “getnext” operation. The getnext operation is used in order to retrieve one or more items of information (called objects), when the NMS does not know beforehand how many objects exist, or even if any objects exist. The NMS typically sends repeated getnext commands to retrieve all objects contained in a series (such as all rows in a logical table), starting at the beginning of the series and continuing until either no more reply is received to the getnext command, or else a reply is received containing an object which lies outside of the desired series.
Similarly, a “getbulk” command is typically defined, which allows an NMS to simultaneously retrieve all items in a series, by specifying (a) the object at the start of the desired series, and (b) the maximum number of successive objects to be retrieved.
The shortcoming of these approaches occurs when the same objects may be viewed as belonging to different series simultaneously. For example, a ME that is a packet switching device may have a table of cross connection objects. Within the table, there are types of cross connections, such as Permanent Virtual Circuits (PVCs), Switched Virtual Circuits (SVCs), and Soft Permanent Virtual Circuits (SPVCs). For the purposes of accounting for total utilization of the ME, the NMS may wish to retrieve information on all cross connections on the ME, regardless of type. For the purposes of allowing a user of the NMS to view and manage only particular types of cross connections (for example, only PVCs and SPVCs), the NMS may wish to retrieve information on these types but not on any other.
PRIOR ART
There are two prior art solutions to the problem of retrieving only selected objects from a series.
In the first prior art solution, the NMS retrieves all items in the series, and discards all those of a type which is not desired, before processing the information further. This has the major shortcoming that it is inefficient, from the point of view of:
a) processing resources on the ME (to copy information on each object into the “get” reply);
b) processing resources on the NMS (to retrieve and examine each object from the reply); and
c) the amount of bandwidth utilized for communications between the ME and the NMS.
In the second prior art solution, different logical series of data are defined on the ME for the same information. For example, cross connections on a packet switch can be retrieved from an “all cross connections” table, from a “PVC” table, from a “SVC” table, etc. The same objects would be accessible from different tables, depending on their type and the definition of the table. The NMS can therefore select whichever table is desired, to fulfill a particular management request. The shortcoming of this approach is that it is inflexible. The NMS cannot make “ad hoc” queries, that are for new or different types or combinations of types of objects within a series, unless the providers of the NMS and ME have previously agreed upon all types of series that will be supported.
SUMMARY OF THE INVENTION
It is an object of the present invention to provide an improved protocol for network management systems to retrieve objects from managed elements within the network or from other network managers.
Therefore in accordance with the present invention there is provided in a communications network management system in which items of information respecting managed elements within the network are retained within the managed elements, a protocol for improving retrieval of information from the managed elements, the improvement comprising adding one or more qualifiers to the items of information wherein the qualifiers represent subclasses of the information.
REFERENCES:
patent: 5367635 (1994-11-01), Bauer et al.
patent: 5539870 (1996-07-01), Conrad et al.
patent: 5561769 (1996-10-01), Kumar et al.
patent: 5659736 (1997-08-01), Hasegawa et al.
patent: 5706508 (1998-01-01), Chen et al.
patent: 5920867 (1999-07-01), Van Huben et al.
Bosloy Jonathan
Burns John
Muller Robert
Tooker Mark
Alcatel Networks Corporation
Larson & Taylor PLC
Lintz Paul R.
Shah Sanjiv
LandOfFree
Network management protocol for efficient retrieval operations does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Network management protocol for efficient retrieval operations, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Network management protocol for efficient retrieval operations will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2841005