 break existing client OSs. The server os can send a newer version of an instance and still have the instance successfully processed. MTOSI allows a client OS to perform multiple operations on multiple objects using a single request to a server OS. In this approach, the transactional logic is delegated to the server OS facilitating in performance tasks like configuration of a managed element and all associated equipment and ports. Also the same operation can be Standard Interfaces performed on a large number of objects of the same type in an efficient manner. These requests may contain multiple actions and/or objects and the requests may be of long duration. 25.3 MTOSI Notifications In this 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 