A database architecture for TMN

This paper describes an architecture for using a database within the fundamental components of a TMN. The manager and agent components act in a client and server fashion while using the database to store instances of managed objects the TMN is responsible for. The database is also used to store events reflecting changes in status for these managed objects. The managed objects and their relationships are described with GDMO and ASN.1. The primary emphasis is an architecture that is not dependent upon any individual database technology or system. This is achieved by database-independent client-server API. The virtual managed object address (VMOA) is also introduced. This is a class that represents a managed object reference in a database in a fashion that allows all, some, or none of the object's attributes to be in the database.