Log Access Interface Between a Network and Repositories

This invention relates to a network management system. In particular, it relates to an interface between a telecommunication network and multiple types of repositories.

Communications networks, such as telecommunications networks, use network management systems to control and monitor the performance of devices attached to the network. Many such current network management systems use databases for persistent storage of various information relating to the network and devices attached to the network.

FIG. 1 shows an example of a telecommunication network 1. Devices connected to the network 1 generally include telephones 2, 3 and computer systems 4, 5, 6. An example of a computer system is the Hewlett Packard 9000 series computer. The interconnection cable 7 between the devices generally consists of many conductive wires or fiber optic lines. Typically, the computer systems and telephones are located at remote sites. One or more of the computer systems connected to the cable 7 may track events that occur on the network.

The network 1 will generally include switches or multiplexers which complete the connection from one computer system to another computer system, or from one telephone to another telephone. Events on the network can include changes in the status of the switches or multiplexers. Events on the network can also include broken cables or other faults on the network. As previously stated, one or more of the computer systems connected to the network may track and log the events on the network.

Various standards bodies have proposed a protocol called Common Management Information Protocol (CMIP) designed to carry information about operations to be executed and events which have occurred on the network. The CMIP protocol, however, does not provide a mechanism for interfacing with database repositories. The database repositories are controlled by the computer systems connected to the network. Therefore, a software interface operable on a computer system must be developed to allow the computer system to function as an interface between the CMIP network and the repository in which the CMIP network is logging events. The software interface is commonly referred to as a log agent.

Typically, a unique log agent interface must be developed for each type of repository. Examples of repositories include relational data base management systems (RDBMS), flat file management systems and object oriented data base management systems (OODBMS). The repository types can also vary between different repository manufacturers. Each type of repository has a different application specific interface (API). That is, each type of repository is controlled with a different sequence of control signals. The presently existing approach to network repository management requires a unique log agent to exist for each type of repository and each repository manufacturer.

The present approach is undesirable because the differences between the log agents for different types of repositories and different repository manufacturers are extensive. The CMIP is complicated and developing the log agents required to control different types of repositories can be time consuming and difficult.

FIG. 2 shows the prior art structure of an interface between a CMIP network 10 and several repositories 14, 15, 16. Several computers systems 11, 12, 13 function as the interface by operating log agents 17, 18, 19. The computer system 11 operates the log agent 17. The computer system 12 operates the log agent 18. The computer system 13 operates the log agent 19. The log agent 17 provides the interface control of the computer system 11 between the repository 14 and the CMIP network 10. The log agent 18 provides the interface control of the computer system 12 between the repository 15 and the CMIP network 10. The log agent 19 provides the interface control of the computer system 13 between the repository 16 and the CMIP network 10. A unique log agent is required for controlling each of the different types of repositories 14, 15, 16. That is, the log agents 17, 18, 19 are each different. The log agents 17, 18, 19 determine the sequence of the signals generated by the corresponding computer systems 11, 12, 13 which control the repositories 14, 15, 16 based on CMIP commands received by the computer systems 11, 12, 13 from the network 10.

The CMIP of the CMIP network 10 is defined by the CCITT (The International Telegraph and Telephone Consultative Committee) Recommendation X.711. The requirements of the log agents 17, 18, 19 are defined by the CCITT Recommendation X.735. The log agents 17, 18, 19 must interface the CMIP network 10 with the repositories 14, 15, 16 following the Recommendations.

Each repository type has a unique API. Each of the log agents 17, 18, 19 must be designed following the standards set by the CCITT Recommendation X.735, and interface the CMIP network with the unique API of each of the types of repositories.

In order to avoid customization of application, it is desirable to have a standard interface between networks employing the CMIP protocol and the repositories connected to the network. The interface should allow new repository types to be connected to the network without requiring the creation of new log agents.

The present invention provides a generalized software interface which provides control of an interconnection between a CMIP network and multiple types of repositories. The interface of this invention only requires modification of the interface command structure at the lowest level of abstraction for individual repository types. Therefore, connection of new types of repositories to the CMIP network can be accomplished without modification of the command structure of the log agent controlling the computer system connected between the CMIP network and the repositories.

An embodiment of this invention includes a telecommunications log access apparatus including a CMIP network. A computer system is connected to the CMIP network and receives events to be logged and requests for logged events. The computer system operates a log agent. The log agent processes the network events to be logged and requests for logged events by executing a set of standardized functions. A repository is connected to the computer system for storing the logged events. The repository is one of a plurality of types of repositories and has a unique application specific interface. The computer system operates a log access library. The log access library controls the repository through the application specific interface based upon the functions executed by the log agent.

Other aspects and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.

FIG. 1 shows a telecommunications network with devices attached to the network.

FIG. 2 shows the structure of a prior art interface between a CMIP network and several different types of repositories.

FIG. 3 shows an embodiment of this invention which interfaces a CMIP network and several different types of repositories wherein each repository is associated with a different computer system.

FIG. 4 shows the another embodiment of this invention which interfaces a CMIP network with several different types of repositories wherein several repositories are associated with a single computer system.

FIG. 5 is a flow chart that shows a method of logging telecommunications events occurring on a CMIP network to a repository controlled by a computer system connected to the CMIP network.

As shown in the drawings for purposes of illustration, the invention is embodied in an apparatus and method for interfacing a CMIP network through a computer system to a repository connected to the computer system. The apparatus includes the computer system operating a log agent and a log access library. The log agent and the log access library transform CMIP commands received from the network by the computer system into a form which can be used to control a repository connected to the computer system. The log agent includes a set number of standard functions. The log access library is a source code implementation of the standard functions of the log agent and is specific to a type of repository. A unique log access library is developed for each type of repository.

The log agent comprises a command structure at the highest level of abstraction. The log access library contains a command structure at the lowest level of abstraction. The introduction of a new repository merely requires a new log access library rather than a completely new and unique log agent. The high level command structure of the log agent remains intact and unchanged with the introduction of new types of repositories. This can significantly reduce the time and effort required to successfully connect a new type of repository to a CMIP network.

FIG. 3 shows an embodiment of the present invention interfacing a CMIP network with a plurality of repositories. A first computer system 40 is connected to a CMIP network 20 and a repository 22. A second computer system 42 is connected to the CMIP network 20 and a repository 24. The first computer system 40 operates a log access library 32 and a log agent 28. The second computer system 42 operates a log access library 34 and a log agent 29. The log access library 32 controls the repository 22, and the log access library 34 controls the repository 24. The log agent 28 of both the first computer system 40 and the log agent 29 of the second computer system 42 are identical. The connection of a third computer system having a different type of repository than the repositories 22, 24 merely requires the development of a new log access library. The third computer system can use the log agent 28 used in the first computer system 40 or the log agent 29 used in the second computer system 42.

The log agent 28 contains a standard structure as defined by the CCITT X.735 Recommendation. The computer system receives the CMIP commands which includes GET, SET, CREATE, DELETE, ACTION and EVENT, and the log agent translates the commands into a sequence of functions interpretable by the log access libraries 32, 34. As previously stated, the log agent is identical for all types of repositories.

For an embodiment of this invention, the functions which can be interpreted by the log access libraries include:

lal.sub.-- connect,

lal.sub.-- disconnect,

lal.sub.-- create.sub.-- repository,

lal.sub.-- delete.sub.-- repository,

lal.sub.-- create.sub.-- log.sub.-- record,

lal.sub.-- sizeof.sub.-- log.sub.-- record,

lal.sub.-- retrieve.sub.-- log.sub.-- record,

lal.sub.-- delete.sub.-- log.sub.-- records,

lal.sub.-- start.sub.-- log.sub.-- retrieve,

lal.sub.-- start.sub.-- log.sub.-- remove,

lal.sub.-- next.sub.-- log.sub.-- record,

lal.sub.-- free.sub.-- log.sub.-- record,

lal.sub.-- remove.sub.-- log.sub.-- record,

lal.sub.-- get.sub.-- log.sub.-- status,

lal.sub.-- get.sub.-- logfull,

lal.sub.-- set.sub.-- logfull.

The functions lal.sub.-- connect and lal.sub.-- disconnect, connect and disconnect a specified database repository to a network through the log agent. The functions lal.sub.-- create.sub.-- repository and lal.sub.-- delete.sub.-- repository, create and delete a log within the repository in which events are stored. The function lal.sub.-- create.sub.-- log.sub.-- record stores an event as a log record in an existing log. The function lal.sub.-- sizeof.sub.-- log.sub.-- record determines how much space in a repository is required for storing a given event. The function lal.sub.-- retrieve.sub.-- log.sub.-- record accesses a log record. The function lal.sub.-- delete.sub.-- log.sub.-- records synchronously deletes a selection of log records from a log.

The functions lal.sub.-- start.sub.-- log.sub.-- retrieve, lal.sub.-- next.sub.-- log.sub.-- record and lal.sub.-- free.sub.-- log.sub.-- record can be used to retrieve a multiple number of selected log records. The function lal.sub.-- start.sub.-- log.sub.-- retrieve specifies a filter that determines which selection of log records are accessed upon repeated execution of the lal.sub.-- next.sub.-- log.sub.-- record function. Execution of the function lal.sub.-- start.sub.-- log.sub.-- retrieve generates a response indicating whether the accessed repository has the capability to perform the desired level of filtering. If the repository cannot perform the desired level of filtering, then the repository will return all records and the log agent performs the desired level of filtering on all of the returned records. This scenario allows optimization of the required filtering. A repository is more efficient than a log agent in filtering records. However, if the accessed repository cannot perform the desired filtering, then the log agent must perform the required filtering of the log records.

Execution of the lal.sub.-- start.sub.-- log.sub.-- retrieve function fills program memory with log records. The lal.sub.-- free.sub.-- log.sub.-- record function serves the purpose of indicating that the previously retrieved log records no longer need to be stored in program memory. The execution of the lal.sub.-- free.sub.-- log.sub.-- record function frees program memory for other subsequent executions of the lal.sub.-- start.sub.-- log.sub.-- retrieve function.

The functions lal.sub.-- start.sub.-- log.sub.-- remove, lal.sub.-- next.sub.-- log.sub.-- record and lal.sub.-- remove.sub.-- log.sub.-- record can be used to asynchronously delete a multiple number of selected log records. The function lal.sub.-- start.sub.-- log.sub.-- remove specifies a filter that determines which selection of log records should be deleted. Execution of the lal.sub.-- start.sub.-- log.sub.-- remove generates a response indicating whether the accessed repository has the capability to perform the desired level of filtering. If the desired filtering is too complicated for the accessed repository, then the log agent repeatedly executes the lal.sub.-- next.sub.-- log.sub.-- record function which retrieves all records. The lal.sub.-- remove.sub.-- log.sub.-- record is then executed to select the records to be deleted.

The function lal.sub.-- get.sub.-- log.sub.-- status can be used to determine the size of a log and the number of log records in a log. The functions lal.sub.-- get.sub.-- log.sub.-- full and lal.sub.-- set.sub.-- logfull determine and specify when a log is full.

The computer systems 40, 42 receive CMIP commands from the CMIP network 20. The log agents 28, 29 transform the CMIP commands received by the computer systems 40, 42 into the set of standard functions. The log access libraries 32, 34 transform through a source code implementation the standard functions of the log agent to the application specific interface (API) of the repositories 22, 24. The command structure of the log access libraries is at the lowest level of abstraction. Therefore, none of the higher level commands of the log agent 28 needs to be modified to accommodate new types of repositories.

Each type of repository has its own unique API. For an embodiment of this invention, the log access library consists of C programming code which translates the functions of the log agent 28 to a form interpretable by the API of the repository. The functions of the log agent 28 are programmed within the log access libraries to carry out the defined functions. A unique log access library is designed for each unique API corresponding to each type of repository. The API for each repository is defined by the manufacturer of the repository.

FIG. 4 shows another embodiment of the present invention interfacing a CMIP network 20 with a plurality of repositories 22, 24, 26. The CMIP network 20 is interfaced with the plurality of repositories 22, 24, 26 through a computer system 21. The computer system operates a log agent 28 and a plurality of log access libraries 32, 34, 36. The repositories 22, 24, 26 are each different types of repositories.

For this invention, a single log agent 30 can be used for controlling the computer system which interfaces the CMIP network 20 with the plurality of repositories 22, 24, 26. The log agent 30 comprises the sixteen previously discussed functions which can be executed to carry out the commands received from the CMIP network 20. That is, the log agent 30 is identical to the log agents 28, 29 of FIG. 3. The log access libraries 32, 34, 36 are source code implementations of the sixteen pre-defined functions of the log agent 30. The repository types 22, 24, 26 each have a corresponding unique log access library 32, 34, 36. That is, repository 22 corresponds with log access library 32, repository 24 corresponds with log access library 34, and repository 26 corresponds with log access library 36.

FIG. 5 is a flow chart that shows a method of logging telecommunications events occurring on a CMIP network to a repository controlled by a computer system connected to the CMIP network. The first step 51 of the method includes generating a CMIP command instructing the logging of an event to a repository. The second step 53 includes translating the CMIP command into a combination of standardized functions, the translation being performed by a CCITT X.735 standardized log agent. Finally, the third step 55 includes translating the combination of standardized functions into a form which can be interpreted by an application programming interface of the repository, the translation being performed by a log access library.

Although specific embodiments of the invention have been described and illustrated, the invention is not to be limited to the specific forms or arrangements of parts so described and illustrated. The invention is limited only by the claims.