H E W L E
`
`T - P A C K A R D
`
`JOURNAL
`
`October 1996
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`H E W L E T T
`P A C K A R D
`
`Oracle/Dot Hill Ex. 1006, pg. 1
`
`

`
`H E W L E T T - P A C K A R D
`
`JOURNAL
`
`October 1996 Volume 47 • Number 5
`
`Articles
`6 A Platform for Building Integrated Telecommunication Network Management Applications,
`
`by Prabha G. Chadayammuri
`
`' Glossary
`
`17 Distributed Processing Environment: A Platform for Distributed Telecommunications
`
`Applications, by Frank Leong, Satya P. Mylavarabhata, Tmng Nguyen, and Frank Quemada
`
`1 Alarm Management in Telecommunications Networks, by Sujai Hajela
`
`HP OpenView Event Correlation Services, by Kenneth R. Sheers
`
`•sZL Correlation Node Types
`
`) Count Node
`
`s / U n l e s s N o d e
`
`j Table Node
`
`j Fact Store and Data Store
`
`1 Annotation
`
`43 A Modeling Toolset for the Analysis and Design of OSI Network Management Objects,
`
`by Jacqueline A. Bray
`
`Executive Robin Steve Beitler • Managing Editor, Charles L. Leath • Senior Editor, Richard P. Dolan • Assistant Editor, Robin Everest
`Publication Production Manager, Susan E. Wright • Distribution Program Coordinator, Renée D. Wright • Layout/Illustration, John Nicoara
`
`Advisory Board
`
`Rajeev Colorado Integrated Circuit Business Division, Fort Collins, Colorado
`William W. Brown, Integrated Circuit Business Division, Santa Clara California
`Rajesh Desai, Commercial Systems Division, Cupertino, California
`Kevin G. Ewert, Integrated Systems Division, Sunnyvale, California
`Bernhard Fischer, Bòblingen Medical Division, Bòblingen, Germany
`Douglas Gennetten, Greeley Hardcopy Division, Greeley, Colorado
`Gary Gordon, HP Laboratories, Palo Alto, California
`Mark Gorzynski, InkJet Supplies Business Unit, Corvallis, Oregon
`Matt J. Marline, Systems Technology Division, Roseville, California
`Kiyoyasu Hiwada, Hachioji Semiconductor Test Division, Tokyo, Japan
`
`r-orrest Kellert, Microwave lecnnoiogy Division, banta «osa, i
`Ruby B. Lee, Networked Systems Group, Cupertino, California
`Swee Kwang Lim, Asia Peripherals Division, Singapore
`Alfred Maute, Waldbronn Analytical Division, Waldbronn, Germany
`Andrew McLean, Enterprise Messaging Operation, Ptnewood, England
`
`Dona View, Miller, Worldwide Customer Support Division, Mountain View, California
`Mitchell J. Mfinar, HP-EEsof Division, Westlake Village, California
`Michael P. Moore, VXI Systems Division, Loveland, Colorado
`M. Shahid Mujtaba, HP Laboratories, Palo Alto, California
`Steven J. Narciso, VXI Systems Division. Loveland, Colorado
`Danny J. Oldfield, Electronic Measurements Division, Colorado Springs, Colorado
`Garry Orsolini, Software Technology Division, Roseville, California
`Ken Poulton, HP Laboratories, Palo Alto, California
`GünterRiebesell, Bòblingen Instruments Division, Bòblingen, Germany
`Marc Sabatella, Software Engineering Systems Division, Fort Collins, Colorado
`Michael B. Saunders, Integrated Circuit Business Division, Corvallis, Oregon
`Philip Stenton, HP Laboratories Bristol, Bristol, England
`Stephen R. Undy, Systems Technology Division, Fort Collins, Colorado
`Jim Willits, Network and System Management Division, Fon Collins, Colorado
`Koichi Yanagawa, Kobe Instrument Division, Kobe, Japan
`Dennis C. York, Corvallis Division, Corvallis, Oregon
`Barbara Zimmer, Corporate Engineering, Palo Alto, California
`
`Hewlett-Packard Company 1996 Printed in U.S.A.
`
`The Hewlett-Packard Journal is printed on recycled paper.
`
`October 1996 Hewlett-Packard Journal
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`Oracle/Dot Hill Ex. 1006, pg. 2
`
`

`
`' A T o o l k i t f o r D e v e l o p i n g T M N M a n a g e r / A g e n t A p p l i c a t i o n s , b y L i s a A . S p e a k e r
`
`•) / A Application Toolkit for Developing Telecommunications Application Components, byAlasdair
`' D . C o x
`
`70 Business Process Flow Management and its Application in the Telecommunications
`
`M a n a g e m e n t N e t w o r k , b y M i n g - C h i e n S h a n , J a m e s W . D a v i s , W e i m i n D u , a n d Q i m i n g C h e n
`
`H P O p e n V i e w A g e n t T e s t e r T o o l k i t , b y P a u l A . S t o e c k e r
`
`S t o r a g e M a n a g e m e n t S o l u t i o n s f o r D i s t r i b u t e d C o m p u t i n g E n v i r o n m e n t s , b y R e i n e r L o m h ,
`K e l l y A . E m o , a n d H o y M . V a n d o o m
`
`L j / j A n I n t r o d u c t i o n t o F i b r e C h a n n e l , b y M e r y e m P r i m m e r
`
`| T a c h y o n : A G i g a b i t F i b r e C h a n n e l P r o t o c o l C h i p , b y J u d i t h A . S m i t h a n d M e r y e m P r i m m e r
`
`Departments
`
`4 I n t h i s I s s u e
`5 C o v e r
`5 W h a t ' s A h e a d
`9 0 A u t h o r s
`
`The Hewlett-Packard Journal is published bimonthly by the Hewlett-Packard Company to recognize technical contributions made by Hewlett-Packard (HP)
`personnel. warranties the information found in this publication is believed to be accurate, the Hewlett-Packard Company disclaims all warranties of merchant
`ability damages, indirect, for a particular purpose and all obligations and liabilities for damages, including but not limited to indirect, special, or consequential
`damages, publication. and expert's fees, and court costs, arising out of orin connection with this publication.
`
`Subscriptions: The Hewlett-Packard Journal is distributed free of charge to HP research, design and manufacturing engineering personnel, as well as to
`qualified you individuals, libraries, and educational institutions. To receive an HP employee subscription you can send an e-mail message indicating your
`HP entity and mailstop to Idc Iitpro®hp-patoalto-gen13. om.hp.com Qualified non-HP individuals, libraries, and educational institutions in the U.S. can request
`a subscription to: either writing to: Distribution Manager, HP Journal, M/S 20BH, 3000 Hanover Street, Palo Alto, CA 94304, or sending an e-mail message to:
`hp journal@hp-paloalto-gBn13.om.hp.com. When submitting an address change, please send a copy of your old label to the address on the back cover.
`International subscriptions can be requested by writing to the HP headquarters office in your country or to Distribution Manager, address above. Free subscrip
`tions may not be available in all countries.
`
`The Hewlett-Packard Journal is available online via the World Wide Web (WWW). The uniform resource locator (URL) is:
`
`http://www.hp.com/hpj/journal.html
`
`S u b m i s s i o n s : H P - a r t i c l e s i n t h e H e w l e t t - P a c k a r d J o u r n a l a r e p r i m a r i l y a u t h o r e d b y H P e m p l o y e e s , a r t i c l e s f r o m n o n - H P a u t h o r s d e a l i n g w i t h H P -
`related considered or solutions to technical problems made possible by using HP equipment are also considered for publication. Please contact the Editor
`before submitting such articles. Also, the Hewlett-Packard Journal encourages technical discussions of the topics presented in recent articles and may
`publish letters expected to be of interest to readers. Letters should be brief, and are subject to editing by HP.
`
`C o p y r i g h t p u b l i c a t i o n t h a t C o m p a n y . A l t r i g h t s r e s e r v e d . P e r m i s s i o n t o c o p y w i t h o u t f e e a l l o r p a r t o f t h i s p u b l i c a t i o n i s h e r e b y g r a n t e d p r o v i d e d t h a t
`1)the copies are not made, used, displayed, or distributed for commercial advantage; 2) the Hewlett-Packard Company copyright notice and the title of the
`publication and date appear on the copies; and 3) a notice appears stating that the copying is by permission of the Hewlett-Packard Company,
`
`Please Hewlett-Packard inquiries, submissions, and requests to: Managing Editor, Hewlett-Packard Journal, M/S 20BH, 3000 Hanover Street, Palo Alto. CA 94304 U.S.A.
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`October 1996 Hewlett -Packard Journal
`
`Oracle/Dot Hill Ex. 1006, pg. 3
`
`

`
`In this Issue
`
`The components of a typical telecommunications network usually come from
`different vendors and the networks are usually distributed geographically. To
`manage these large-scale networks, a standards-based telecommunications
`network management system must be in place. Standards define the interfaces
`that system telecommunications equipment manufacturers, system integrators,
`and service providers to develop network management applications that allow
`their network to interoperate in a heterogeneous telecommunications network
`environment. These vendors need a development platform anda toolset to take
`care management the underlying standards-compliant requirements for management
`applications.
`
`The first telecommunications articles in this issue describe HP products targeted to meet the needs of telecommunications
`application developers. The article on page 6 introduces the HP OpenView Distributed Management (DM)
`Platform, a software foundation that provides the services for building standards-compliant telecommu
`nications management network applications. The article describes the Telecommunications Management
`Network (TMN) from ITU-T (International Telecommunications Union-Telecommunications), the features
`of the OSI-based version of HP OpenView DM, and the architecture of the new CORBA-based version of
`the HP Architecture) Platform. CORBA (Common Object Request Broker Architecture) is a service that en
`ables object-oriented to make and receive requests and responses in an object-oriented distributed environment.
`Developers creating applications to run in a distributed, heterogeneous telecommunications environment
`should They be concerned about what system their applications may be running on. They should be able to
`target their applications to run on a software architecture that handles all telecommunication management
`and control functions for distributed applications. The article on page 17 describes the HP Distributed Pro
`cessing Environment, which provides infrastructure services that facilitate rapid development, deployment,
`and management of distributed applications in the telecommunications arena.
`Network management relies on information, especially information from network elements such as
`bridges, routers, servers, and gateways. The article on page 22 describes the HP Open Element Man
`agement covers (OEMF), which is the implementation of the ITU-T recommendation that covers fault
`management, performance management, and other third-party applications. OEMF makes possible the
`detection, isolation, and correction of the abnormal operation of a telecommunications network. OEMF
`includes the HP OpenView Fault Management Platform (FMP), which is a platform and utility tool for
`managing alarms from multivendor devices and network element managers.
`When event fault occurs in a telecommunications system it can cause an event storm of several hundred
`events (ECS) second for tens of seconds. HP OpenView Event Correlation Services (ECS) helps operators
`determine the underlying cause for the thousands of events presented to them. ECS is made up of two
`components: the ECS engine, which executes a set of downloaded rules that control the processing of
`event streams, and the ECS Designer, which enables interactive development of correlation rules. ECS is
`described in the article on page 31.
`
`TMN uses OSI object-oriented paradigm, and its management principles are based on the OSI (Open Sys
`tem Interconnection) standard. Thus, in the TMN model, network and system resources are modeled as
`objects, to managed objects. Telecommunications management application developers need to
`specify and model these managed objects to create management applications. The article on page 43
`describes the HP OpenView GDMO (Guidelines for the Definition of Managed Objects) Modeling Toolset,
`which is specify integrated set of tools that enable developers to use a graphical user interface to specify
`and create a file containing managed objects. GDMO is an ITU-T recommendation that defines how
`network objects and their behavior are to be specified.
`
`Once managed developer has created the GDMO specifications for the managed objects, the next step is to
`develop applica applications that maintain and provide access to the objects and the manager applica
`tions This manage the network through request and response processing. This is the agent/manager
`model (page network management. The HP OpenView Managed Object Toolkit (page 52) uses the contents
`of the GDMO specification file to automatically generate OSI-conformant executable agent applications.
`
`October 1996 Hewlett-Packard Journal
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`Oracle/Dot Hill Ex. 1006, pg. 4
`
`

`
`The toolkit also provides a C++ interface that encapsulates the complexities of the underlying protocols,
`providing assistance in the development of management applications.
`The managed objects are stored in a database called the Management Information Base (MIB). The
`objects Under the MIB are defined by GDMO, organized hierarchically, and related by containment. Under
`standing this data and the operations required to access it are essential for developers implementing
`TMN management applications. The article on page 62 describes a prototype that addresses some of
`the requirements of TMN application developers by allowing them to explore the available management
`data and make enough sense of it to construct and deploy pieces of management applications.
`Once next manager and agent applications have been created, the next step is to test both of these applica
`tions simultaneously. To help with this task, the new HP OpenView Agent Tester Toolkit (page 77) generates
`tests During allow a developer to execute these tests individually or as a set. During agent development, the
`Agent transmit Toolkit is used to simulate requests sent from a manager, transmit these requests over the
`network to the agent, and then receive and process the responses from the agent.
`The TMN telecommunications defines five network management layers in which telecommunications applications
`can fit. layer. two top layers are called the business management layer and the service management layer.
`The business management layer contains functions that are responsible for the whole enterprise, such
`as budgeting and product planning, and the service management layer contains f unctions that are
`responsible for managing services provided to customers, such as service transactions and billing. The
`article HP page 70 describes an application called HP OpenPM, which fits into these two layers. HP
`OpenPM is an open, enterprise-capable, object-oriented business process flow management system
`(BPFM). HP OpenPM is a middleware service that provides the enabling technologies for defining and
`managing end- in areas such as resource allocation, task initialization and data exchange, and end-
`to-end communication and security.
`Telecommunications networks and distributed computing environments rely on reliable and consistent
`storage disk strategies. Today, storage management strategies involve more than just more disk
`drives. offline, also include storage management and different types of storage devices for offline, nearline,
`and online data storage. The article on page 81 provides an overview of HP hardware and software
`products, services, and partners that provide storage management solutions.
`Even they processor speeds continue to improve dramatically, they are barely keeping up with the
`increasing numbers of concurrently running applications and CPU-intensive applications with higher
`throughput requirements. Additionally, as the number of interconnects between systems and I/O devices
`continues to increase, I/O channels become bottlenecks to system performance. For all these reasons,
`today's parallel bus architectures are reaching their limits. In the search for a higher-performance serial
`interface, HP chose Fibre Channel because it overcomes the limitations mentioned above by supporting
`sustained gigabit data transfer rates. The article on page 99 describes Tachyon, which is HP's gigabit
`Fibre description chip. The article on page 94 presents a technical description of Fibre Channel.
`C.L Leath
`Managing Editor
`
`Cover
`An artistic rendition of telecommunications, showing a satellite antenna in the background and an HP
`OEMF foreground. map and alarm viewer for a mobile network in the foreground.
`
`What's Ahead
`The December issue will feature the design of the HP 83480 digital communications analyzer for SONET/
`SDH testing, the HP E5200A broadband service analyzer for ATM testing, HP SmartClock technology and
`products sur using the Global Positioning System as a time reference, and the HP HEDS-8000 Series sur
`face mount reflective optical shaft encoders. A pair of papers will describe a new, radially staggered 1C
`bonding technology, and a special section will celebrate the thirtieth anniversary of HP Laboratories.
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`Oc-iobcr l!)9(i Ilcwlcti-I'ackard Journal
`
`Oracle/Dot Hill Ex. 1006, pg. 5
`
`

`
`A Platform for Building Integrated
`Telecommunications Network
`Management Applications
`Telecommunications companies today are faced with rapid technological
`change, large heterogeneous environments, and a greater need to provide
`customers with products that ensure reliable, cost-effective network
`service. This means that these companies need a platform that has a
`visionary strategy that enables them to develop standards-compliant
`network management solutions for a continually changing environment.
`
`by Prabha G. Chadayammuri
`
`The telecommunications industry is going through phenome
`nal growth and change. This growth has made telecommu
`nications networks essential to the daily activities of the
`enterprise and individuals. It has also given rise to the need
`for better ways to manage and maintain heterogeneous and
`multivendor networks.
`
`Network management includes the operations, administra
`tion, maintenance, and provisioning (OAM&P) functions
`required to monitor, interpret, and control a network and
`the services it provides. When networks started to be used
`beyond the academic community and before deregulation
`and privatization of the telephone industry, there were fewer
`vendors, thus fewer multivendor management issues. Also,
`the rate of introduction of new network technologies was
`much slower. These conditions meant that network manage
`ment could be ad hoc and vendor-specific. Today, issues
`such as multivendor networks and equipment, the need to
`automate certain network management tasks, and the rapid
`integration of new technologies have driven the need to
`standardize telecommunications network management.
`
`Since the early 1980s, the standardization bodies have been
`developing and specifying a collection of standards for
`managing telecommunications networks. A portion of these
`standards, dealing with open systems, is contained in the
`X.7xx series of standards defined by the ITU-T (Interna
`tional Telecommunications Union — Telecommunications).
`Another series of standards, the M.3xxx series from ITU-T,
`defines a model known as the Telecommunications Manage
`ment Network (TMN).1
`
`TMN is based on the Open Systems Interconnection (OSI)
`systems management model, which is set of standards that
`define the rules for processing and transferring data over
`networks.2 Such systems are called open systems. Although
`not intrinsically part of TMN, OSI systems management stan
`dards were developed jointly by the ISO and ITU standards
`bodies.
`
`All of these standards, no matter how worthy, are simply
`collections of well-written guidelines without a platform and
`tools to build network management solutions. Choosing a
`
`network management platform is a critical strategic deci
`sion that has long-term implications. The development of
`large-scale telecommunications management systems
`requires a significant investment of resources. Solutions,
`once deployed, will be supported for many years.
`
`For equipment manufacturers and systems integrators, the
`network management foundation must enable rapid devel
`opment of applications that can differentiate and add value
`to their products. For telecommunications service providers,
`the network management foundation must enable rapid
`deployment of new services that improve competitiveness
`and new operations that increase efficiency.
`
`HP OpenView products provide the platform and enabling
`technologies required for network management solutions
`for today's telecommunications environment.
`
`HP OpenView DM
`The HP OpenView Distributed Management (DM) platform
`is a software platform for designing portable, standards-
`based systems for telecommunications management (see
`Fig. 1). HP OpenView DM products are focused on meeting
`the reliability, performance, distribution, and standards
`needs of telecommunications equipment manufacturers,
`service providers, and system integrators. The HP OpenView
`DM platform offers the following features for developing
`TMN applications.
`
`Standards Support. The HP OpenView DM products support
`protocol, object, and service specifications defined by ITU,
`OSI, X/Open®, the Internet Engineering Task Force (IETF)
`for SNMP (Simple Network Management Protocol), and the
`Network Management Forum (NMF).3
`
`There is also full support for network management protocols
`CMIP (Common Management Information Protocol), RFC
`1006 (TCP/IP), and SNMP.4'5
`
`Open Systems. The HP OpenView DM platform is built on an
`open systems architecture, enabling solutions to run on a
`variety of hardware platforms. Native support is implemented
`for HP 9000 workstations and servers running the HP-UX
`
`6 October 1996 Hewlett-Packard Journal
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`Oracle/Dot Hill Ex. 1006, pg. 6
`
`

`
`HP OpenView Windows
`
`Operational Support
`Systems Applications
`
`GDMO
`Development
`Toolkit
`
`ACSE
`Connections
`
`CMIP = Common Management Interface Protocol
`GDMO = Guidlines for the Definition of Managed Objects
`SNMP = Simple Network Management Protocol
`
`operating system and Sun SPARC workstations running the
`Solaris and SunOS operating systems. Support for HP Open-
`View is also provided on other hardware and software plat
`forms.
`
`Postmaster. The postmaster serves as the integration point
`for management protocol stacks such as CMIP and SNMP,
`management APIs, and related facilities (e.g., routing,
`events, and association control). The postmaster provides
`distributed message routing and access to applications and
`services through standard management protocols. Finally,
`the postmaster reliably creates and manages associations
`(connections), maps objects to network addresses and pro
`tocol stacks, and routes requests from manager systems and
`responses from managed systems (agents).
`
`Event Services. HP OpenView DM provides a set of services
`that management applications can use to control event and
`alarm messages from diverse network elements and systems.
`It includes a mediation service that collects, stores, filters,
`and extracts messages and an alarm management service
`that displays and correlates alarm messages and invokes
`external applications based on alarm data. Alarm manage
`ment and event correlation services are described in the
`articles on pages 22 and 31 respectively.
`HP Distributed Processing Environment (DPE). The HP DPE
`provides an Information Networking Architecture (INA)
`compliant platform for telecommunications services and
`operations systems. Trader services and an API framework
`simplify the development and deployment of distributed
`telecommunications applications. HP DPE is described in
`the article on page 17.
`
`Fig. 1. The main components of
`the HP OpenView Distributed
`Management Platform.
`
`and seamless integration of management functions, regard
`less of vendor or managed object type. HP OpenView win
`dows provides a common interface that simplifies the devel
`opment and use of management applications. Finally, the
`HP OpenView windows GUI is the key integration point for
`HP OpenView applications.
`
`Modeling Toolset. The HP OpenView GDMO (Guidelines for
`the Definition of Managed Objects)6 Modeling Toolset is an
`integrated suite of software tools for designing and analyzing
`objects used in network management applications. GDMO is
`an ISO standard that describes a consistent methodology for
`specifying managed objects in TMN applications.
`
`The HP OpenView GDMO Modeling Toolset has a forms-
`based GUI that enables developers to create GDMO specifi
`cations and export them as ASCII files for use by the next
`application in the tool chain, the Managed Object Toolkit.
`The HP OpenView GDMO Modeling Toolset is described in
`the article on page 43.
`
`Managed Object Toolkit. The HP OpenView Managed Object
`Toolkit is a C++ code generator that accelerates the devel
`opment of GDMO-based manager and agent applications
`(described below). The managed object toolkit includes an
`infrastructure that provides a collection of reusable objects
`that handle CMIS operations such as GET, SET, and ACTION.
`
`Agent application development is improved because the
`Managed Object Toolkit takes the GDMO ASCII file and
`automatically converts the GDMO specification into an
`OSI-conformant, executable agent. The Managed Object
`Toolkit is described in the article on page 52.
`
`Graphical User Interface. The HP OpenView windows graphical
`iisci inicri'ace (GUI) provides network operators and admin-
`isl ral < irs with a consistent view of the managed environment
`
`TMN Applications and HP OpenView
`HP OpenView products have been adopted by many promi
`nent equipment manufacturers and telecommunications
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`Ortohrr l!l!)(i Ilc'wlolt-I'arkard. Journal
`
`Oracle/Dot Hill Ex. 1006, pg. 7
`
`

`
`service providers to implement a variety of TMN solutions.
`Some of the areas in which TMN applications can be built
`upon the HP OpenView foundation include:
`• Services management for broadband networks including
`Synchronous Optical Network (SONET), Synchronous
`Digital Hierarchy (SDH), Asynchronous Transfer Mode
`(ATM), and residential services such as video-on-demand
`• Provisioning and monitoring applications for broadband
`networks
`• Network monitoring for outsourced customer networks
`managed by telecommunications service providers
`• Customer gateways into public networks for real-time moni
`toring and data management
`• Integration with other management platforms for TMN com
`patibility and a single view from a multivendor environment
`• Element management systems for new equipment and new
`data communications services.
`
`The HP OpenView DM platform has traditionally supported
`the OSI systems management model to provide TMN solu
`tions. However, in recent years the Common Object Request
`Broker Architecture (CORBA)7 from the Object Management
`Group (OMG) has attracted interest as a general model for
`distributed application development.
`
`The combination of the CORBA and OSI models is an ex
`tremely powerful solution for TMN application development.
`Thus, HP OpenView DM platform development is moving in
`that direction.
`
`The rest of this article will discuss various aspects of the
`TMN architecture and the OSI model and their relationship
`to the existing OSI-based HP OpenView DM platform and
`the evolving CORBA-based platform.
`
`TMN Architecture
`Fig. 2 shows the business, service, network, and element
`management layers of the TMN model and the interaction
`between applications in these different management layers.
`The functionality of applications in each of these layers is
`defined in ITU-T Recommendation M.3010.1
`
`Network Element Layer. Functionality at this layer is provided
`by the network elements (e.g., switches, multiplexers,
`repeaters, hubs, terminals, etc.). These functions include
`operations such as performance data collection, alarm
`collection, protocol conversion, and so on. Applications at
`this level are responsible for managing network elements.
`
`Element Management Layer. Functions at this layer are respon
`sible for managing a subset of network elements, performing
`as a gateway to network elements in the upper layers, and
`keeping statistical and historical information about network
`elements.
`
`Network Management Layer. Network management functions
`are used to support TMN applications that require a global
`view of the network. Data for this global view is collected
`from data summarized by the network element management
`layer. This layer is also responsible for the technical provi
`sion of services requested by the service management layer.
`
`Service Management Layer. This layer is responsible for man
`aging the services provided to customers. It provides the
`point of contact with customers for all service transactions,
`
`including billing, quality-of-service (QoS) data, service con
`tracts, and so on.
`
`Business Management Layer. This layer contains functions
`that are responsible for the whole enterprise. These func
`tions include goal setting and budgeting, product planning
`and definitions, and agreements between jurisdictions.
`
`Operation Systems and the Manager/Agent Model. The opera
`tions systems shown in Fig. 2 are integrated telecommunica
`tion management applications that implement the network
`management functions in the TMN layers. The operations
`systems are based on an agent/manager model. This model
`resembles the client/server paradigm in which applications
`in the manager role are clients and applications acting as
`agents would be servers. The agent/manager model is also
`called a managed system (agent) and managing system
`(manager) architecture in TMN terminology. The agent/man
`ager model is based on using objects to model the system
`being managed. Each object can have attributes that repre
`sent its state or relationship with other objects, its special
`ized behaviors (called actions), and notifications it issues to
`signal some event. Thus, an object encompasses a device's
`behavior as well as its physical characteristics. An agent
`resides in an object and reports the object's status to the
`manager. The manager, equipped with the capability to
`have a global view of the network, manages the agents and
`handles the notifications from agents.
`
`Q3 Interfaces. Operations systems within and between TMN
`layers are required to use a set of standard interfaces called
`Q3 interfaces for the exchange of management informa
`tion.8'9 Q3 interfaces are responsible for connecting an op
`erations system to a network element, an operations system
`to a Q adapter, an operations system to a mediation device,
`or two operations systems in the same TMN. Q3 specifica
`tions use the Common Management Information Service
`Element (CMISE) protocol10 for management and the file
`transfer access and management (ftam) protocol for bulk
`transfer.
`
`The standard way to convert a non-TMN function into a TMN
`function is called a Q adapter. Loosely stated, Q adaption
`is a translation between Q3 and the non-Q3 models at run
`time. Translation to a level less than Q3 requires a mediation
`device to raise the adaption to Q3 levels. The X reference
`points in Fig. 2 also perform an interface function. They pro
`vide an interface for communications with operations sys
`tems belonging to other TMNs or between TMN operations
`systems and non-TMN operations systems on other TMNs
`that support TMN-like interfaces. Q3 interfaces are generally
`regarded as appropriate for the X reference point.
`
`The HP OpenView DM platform supports the APIs and proto
`cols necessary for TMN applications. The HP OpenView DM
`platform provides the Q3 interfaces via the X/Open manage
`ment XOM/XMP APIs and the C++ classes generated by the
`Managed Object Toolkit described in the article on page 52.
`Faster APIs like the BER (Basic Encoding Rules) Manage
`ment Protocol (BMP) and the generic data type dictionary
`APIs are available on the platform.11 Application developers
`can build OSI applications using the APIs or the Managed
`Object Toolkit. The Managed Object Toolkit generates a
`
`8 October 1996 Hewlett-Packard Journal
`
`© Copr. 1949-1998 Hewlett-Packard Co.
`
`Oracle/Dot Hill Ex. 1006, pg. 8
`
`

`
`Business
`Management
`Layer
`
`Service
`Management
`Layer
`
`Element
`Management
`Layer
`
`Network
`Management
`Layer
`
`Network
`Elements
`Layer
`
`Fig. and TMN architecture showing the network management layers and
`
`Carious TMN elements in each layer