Information Architecture

1. Information Architecture Fifteen Meeting

2. What is Information Architecture • Exchange information • Enable information exchange to take place in an open environment • Adopting object-oriented • This openness is achieved by principles to define managed objects. • Operates the logical processes regardless of manufacturer.

3. Managing system Contains many managers Operate within the management functions. Each function is divided into management layers. Communication system Includes a communication network Each network provide connections between managers and the agents. Abstract view Managed system Contains one or more agent Is made up of network elements Conceptual Components

4. Manger Issue request commands (operations) to agent Receive notifications from the agent. Agent React to operations through notifications. Common Management Information Protocol (CMIP). Is the protocol that defines the communication between managers and agents Interaction Between Manager And Agent

5. TMN Resources • It can be used to refer to the entity that is to be managed. • Physical resource • Network elements • Logical resource • Record within a network element. • Managed object relationship with a resource • one-to-one • many-to-one • one-to-many or • a one-to-hierarchy

6. Resource Relationship

7. Communication with Managed Objects • Management Information Base (MIB) • Is a database of all object representation • Is implemented in a distributed database (many storage areas) • Holds details of each managed object and their relationships • Manager • Makes decisions on the basis of the information in the MIB • Contacts particular managed objects when it requires information, • Sends operations to a managed object to carry out some action. • Notification is a message sent by an agent, from managed objects • CMIP • Defines operations that can be carried out on managed objects • Examples of common management operations are ‘GET’ and ‘SET’.

8. Network Information Model • Inheritance hierarchy • Managed object classes are organized in a hierarchy • Their position in the hierarchy is defined by a name, • Termination point • Bidirectional termination point.

9. Boundary emphasized by the abstract view of the resource showing five managed object classes for three resources Objects/Managed Resource Relationship

10. Trail Reference Point

11. Transmission Fragment

12. Transmission Point (TP) Class

13. Termination Point (TP) Class

14. Behaviour description of the managed object General description in a natural language Algorithm suitable for implementation in a programming language. Attributes contain data items which can be accessed by the manager Actions Operations that the object can be asked to perform. Managed Objects Each managed object class has a unique relative distinguished name (RDN)

15. Termination Point Objects Termination Point Class Three managed Object classes

16. Cross-connect Objects

17. A connection can be established by joining together two bi-directional termination points. If this connection is made using a crossconnect, then the managed object class for the cross-connect can be added to the termination point objects. Adding to Termination Point Object

18. Cross-connect Objects and Agents