his section, the notification feature is taken as a sample MTOSI feature for discussion. Some of the event notifications provided by MTOSI include: Creation of a particular object Attribute value changes for attributes of an object Conveying all the change information in single notification The interface offers capability for both single event inventory notifications like the creation of a particular entity or attribute value changes for several attributes of a given entity, as well as multievent inventory notifications, which is a direct method for getting bulk inventory updates from the source OS to other interested OSs. To get a feel of notification generation like object creation notification (OCN) and attribute value change (AVC) notification, let us discuss two methods by which a new network entity is announced on CCV. The first method requires the discovery OS to keep track of the planned entities, and the network entities to be planned and named at the interface before they are discovered. The steps in the first method are: 1. A network entity is entered into the inventory OS. 2. The network entity is represented by the object created by inventory OS. 3. This object is transferred to the planning resource state. The network entity has not been installed now. 4. The "Object Creation Notification" is sent from the inventory OS to the dis- covery OS. 5. The network entity is actually installed later. 6. The discovery os detects the installed entity and issues an "Attribute Value Change" notification on the resource state of the network entity. 7. This results in change from planning to installing. In the second method the new network entity is first announced on the CCV by the discovery os before it is given a unique name. Here we will deal with object discovery notification (ODscN) and object creation notification (OCN). The steps in the second method are: 1. A network entity that has not been announced by the inventory OS at the interface is directly detected by the discovery OS. 2. The discovery OS then s