Arrangement and method relating to information managing systems

Electrical computers and digital processing systems: multicomput – Computer network managing – Network resource allocating

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C709S226000, C709S241000, C709S241000, C709S241000, C707S793000

Reexamination Certificate

active

06385650

ABSTRACT:

BACKGROUND
The present invention relates to a system comprising a number of managing systems and a number of managed systems which are managed by said managing system. Each managed system comprises a number of managed objects being of one or more different types. The managed objects represent or manage resources and the managed objects are arranged in a management information tree structure also called a naming tree structure having a root and a number of sub-trees.
The invention also relates to a managed system which comprises a number of managed objects of one or more types representing/managing a number of resources wherein the managed objects are arranged in a naming tree structure comprising the instance names of the managed objects. Still further the invention relates to a telecommunications system with a number of managing systems each managing a number of managed systems with a number of managed objects which represent resources. The managed objects are arranged in a naming tree structure with a number of sub-trees.
The invention also relates to methods for mapping between managed objects of managed systems and resources which are managed or represented by the managed objects and for providing information relating to the sub-tree of the naming tree structure.
System management is known from the fields of data communication and telecommunications. CCITT (now ITU-T) Recommendation M.3010 relates to telecommunications management networks and CCITT Recommendations X.701 and X.720 relate to systems management and management information models of data communication networks.
In a number of known systems managed systems comprise network elements and managing systems are known as operations systems which are used for monitoring and controlling purposes of the equipment and the services which are provided by the network elements.
In some telecommunications systems a network element may be connected to the rest of the telecommunication network via an exchange terminal within the network element which in turn may communicate over a PCM (pulse code modulated) link. The network element is controlled and monitored from an operations system which is connected to the network element over the Q
3
-interface. In order to provide for the controlling or monitoring of the network element managed objects are created e.g. comprising subscriber data for subscribers.
The managed objects are designed for the operations systems and they show those parts of the network element which are to be monitored and controlled from the operations systems. The internal working within the network element is not interesting to an operations system and this is therefore not shown to the operations systems. In practice there are a number of standardized managed objects for various traffic applications which means that network elements from different vendors can be monitored and controlled in a similar manner.
However, for example for switching network elements, seen from the management point of view, there may be an enormous amount of managed objects such as for example millions of managed objects. Therefore, in order to keep track of all the managed objects and to make it possible to give them all a unique name, the managed objects are kept in a tree structure called a naming tree or a management information tree, c.f. CCITT X.720. The naming tree forms the management view of a network element and the relationships forming the naming tree are denoted containment relations. A containment relationship means that a managed object of one class can contain other managed objects of the same or different classes and it is a relationship between managed object instances. A managed object is only contained within one containing managed object and containing managed objects may themselves be contained in other managed objects. The containing relationship is used for naming managed objects. Managed objects which are named in the terms of another object are denoted sub-ordinate objects of the other managed object and a managed object which establishes the name in question for other objects is called a superior managed object of these other objects which then form sub-ordinate objects. The highest level of the naming tree is denoted a root and it is an object having no associated properties.
All managed objects are given an instance name upon creation. All managed objects sub-ordinated another managed object must have different instance names which means that the instance name thus not have to be unique within the naming tree but two or more managed objects can have the same instance name on condition that they are sub-ordinated different managed objects, i.e. that they have different “parents”. Furthermore, every managed object has a distinguished name. This name is unique within the naming tree and the naming starts from the root of the naming tree and ends with the instance name of the managed object. Upon interaction with managed objects the actual traffic resources in the managed object, e.g. the network element, are manipulated. In order to enable manipulation of a resource, a mapping between the external name, i.e. the distinguished name, and an internal name, i.e. the name of the resource, is required and for management operations both resource mapping information and information about sub-trees of the naming tree is required.
In today known systems, the mapping of an external managed object name to an internal resource name and the retrieving of sub-trees is carried out with the use of tables, see e.g. “Design of Protocol Independent Management Agent to Support SNMP and CMIP Queries” by Subrata Mazumdar, International Symposium on Integrated Network, April 1993. In “Development of TMN to a Family of Switching Networks Elements” by M. Kantola et al, International Switching Symposium, Vol. 1 October 1992 is merely submitted that access to the information is needed, i.e. the information that is needed to associate each operation, object instance and attribute operated on to the appropriate resource in various DX 200 computer units. Nothing is however said about how this is provided. For performance reasons these tables are stored in random access memories RAM. However, if the number of managed objects is very high, the tables that are required need to be large. For example in a GSM telecommunications network having a Home Location Register including about 2 million subscribers the number of managed objects will be more than 50 millions and the tables will require approximately 5 Gbyte of RAM (this of course depends on the implementation; the estimation merely being given for illustrative purposes). The memory consumption of the two tables containing mapping and naming tree information is proportional to the number of managed objects. Moreover, the performance depends on how the access to the tables is provided etc. It is thus obvious that for large managed systems (e.g. network elements) comprising a high number of managed objects, the known solutions are unsatisfactory and if the managed systems (network elements) are very large, the known solutions will not even work.
SUMMARY
What is needed is therefore a system with a low memory consumption even if the number of managed object is high or very high. Furthermore a system is also needed wherein the performance is high even if the number of managed objects is high or even very high.
Particularly a system is needed in which resource mapping information between managed objects and resources can be provided in an adequate way without requiring a high memory consumption and advantageously without producing a decrease in performance even if the number of managed objects is high or very high. A system is also needed through which information about sub-trees of a naming tree can be provided in a satisfactory way without requiring a high memory consumption and without leading to a low performance irrespective of whether the managed systems are large or very large, or if the number of managed objects is high.
Furthermore a managed system comprising a number of managed objects

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Arrangement and method relating to information managing systems does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Arrangement and method relating to information managing systems, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Arrangement and method relating to information managing systems will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-2912773

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.