U.S. patent application number 09/863791 was filed with the patent office on 2002-01-10 for element management system for heterogeneous telecommunications network.
Invention is credited to Davis, Kenton T., Dudley, William H., Gallagher, Derek, Gee, Ken, McCabe, Pauric, Podietz, Eric, Weidong, Shao.
Application Number | 20020004828 09/863791 |
Document ID | / |
Family ID | 27382622 |
Filed Date | 2002-01-10 |
United States Patent
Application |
20020004828 |
Kind Code |
A1 |
Davis, Kenton T. ; et
al. |
January 10, 2002 |
Element management system for heterogeneous telecommunications
network
Abstract
The element management system ("EMS") of the present invention
addresses the need for effective and efficient management of
heterogeneous telecommunications networks that include network
elements of different types, such as radios and fiber optic
devices, made by different manufacturers. This EMS provides a core
set of element-independent network management messages that support
basic network management functions such as fault and performance
monitoring and configuration management. Element-independent
messages to an individual network element are mapped to an
element-dependent message for that network element; messages from
individual network elements are correspondingly mapped into the
core set of element-independent messages. Management applications
and user interfaces in the EMS thus send and receive network
management information using the core set of messages, in the
common protocol of those messages. The EMS of the present invention
thus supports rapid and low-cost integration of additional network
elements of different types and different manufacturers, additional
management functionality and additional and modified
telecommunications services. The present invention also provides a
method for developing the core set of element-independent network
management messages for basic telecommunications management
functions.
Inventors: |
Davis, Kenton T.; (Falls
Church, VA) ; Dudley, William H.; (Addison, TX)
; Gallagher, Derek; (Washington, DC) ; Gee,
Ken; (Reston, VA) ; McCabe, Pauric;
(Arlington, VA) ; Podietz, Eric; (Dresher, PA)
; Weidong, Shao; (Greenbelt, MD) |
Correspondence
Address: |
Covington & Burling
Patent Docketing
1201 Pennsylvania Avenue, NW
Washington
DC
20004-2401
US
|
Family ID: |
27382622 |
Appl. No.: |
09/863791 |
Filed: |
May 24, 2001 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
09863791 |
May 24, 2001 |
|
|
|
09288622 |
Apr 9, 1999 |
|
|
|
6260062 |
|
|
|
|
60121429 |
Feb 23, 1999 |
|
|
|
60121425 |
Feb 23, 1999 |
|
|
|
Current U.S.
Class: |
709/223 ;
709/246 |
Current CPC
Class: |
H04L 41/022 20130101;
H04L 41/052 20220501; H04L 41/5003 20130101; H04L 41/0233 20130101;
H04L 41/5054 20130101; H04L 41/0226 20130101; H04L 41/046 20130101;
H04L 41/0213 20130101 |
Class at
Publication: |
709/223 ;
709/246 |
International
Class: |
G06F 015/173; G06F
015/16 |
Claims
We claim:
1. A method for developing a core set of messages for an element
management system for a telecommunications network, comprising the
steps of reviewing telecommunications network management functions
for each of a plurality of telecommunications network elements;
selecting the basic telecommnunications network management
functions; and creating an element-independent telecommunications
network management message, in a common telecommunications
management message protocol, for each selected telecommunications
management function.
2. The method according to claim 1, wherein more than one of the
plurality of telecommunications network elements are manufactured
by different manufacturers.
3. The method according to claim 1, wherein more than one of the
plurality of telecommunications network elements are different
equipment types.
4. An element management system for a telecommunications network,
comprising: means for receiving, from a software application, a
downstream element-independent network management message selected
from a core set of downstream element-independent network
management messages, for transmission to a telecommunications
network element; means for mapping the downstream
element-independent network management message into a downstream
element-dependent network management message, and into an
element-dependent protocol, for the telecommunications network
element; and means for transmitting the downstream
element-dependent network management message to the
telecommunications network element.
5. An element management system according to claim 4, wherein the
core set of downstream element-independent network management
messages results from the method of claim 1.
6. An element management system according to claim 4, wherein the
core set of downstream element-independent network management
messages comprises a reduced number of downstream network
management messages supporting basic telecommunications network
management functionality.
7. An element management system for a telecommunications network,
comprising: means for receiving an upstream element-dependent
network management message from a telecommunications network
element; means for mapping the upstream element-dependent network
management message into a upstream element-independent network
management message selected from a core set of upstream
element-independent network management messages, and into a common
element-independent message protocol; and means for transmitting
the upstream element-independent network management message to a
software application.
8. An element management system according to claim 7, wherein the
core set of upstream element-independent network management
messages results from the method of claim 1.
9. An element management system according to claim 7, wherein the
core set of upstream element-independent network management
messages comprises a reduced number of upstream network management
messages supporting basic telecommunications network management
functionality.
10. An element management system for a telecommunications network,
comprising: means for receiving an unsolicited element-dependent
network management message from a telecommunications network
element; means for mapping the unsolicited element-dependent
network management message into an element-independent network
management message identifying the telecommunications network
element and the nature and priority of the unsolicited
element-dependent network management message; and means for
transmitting the element-independent network management message to
a software application.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] In connection with this application, priority is claimed to
the following provisional applications: SYSTEM AND METHOD FOR
NETWORK CONFIGURATION MANAGEMENT, U.S. Ser. No. 60/121,425, filed
Feb. 23, 1999, and SYSTEM AND METHOD FOR NETWORK MANAGEMENT, U.S.
Ser. No. 60/121,429, filed Feb. 23. 1999.
FIELD OF THE INVENTION
[0002] The present invention relates to element management systems
for telecommunications networks. More particularly, the present
invention relates to element management systems designed to
monitor, control and configure a number of diverse network
elements, such as microwave radios and telecommunications
multiplexers, regardless of the communications protocol, type of
interface or manufacturer of the individual network elements.
BACKGROUND ART
[0003] Driven by government deregulation of telecommunications
services and the rapid introduction of new telecommunications
networking technologies, the telecommunications industry has
experienced unprecedented growth and change in recent years. The
increasing demand for distributed computing systems and instant
availability of online services and information has made access to
reliable high-speed telecommunications networks essential to the
daily activities of corporate enterprises and individuals alike. To
meet the demand for the latest technology and additional capacity,
literally hundreds of telecommunications vendors now compete with
each other in the marketplace for telecommunications solutions,
offering a large variety of services and technologies. some offered
as proprietary, some offered as "standard," and some offered as
"quasi-standard."
[0004] As competition among telecommunications vendors has grown,
so has the size, complexity and heterogeneity of modem
telecommunications networks. These complex heterogeneous
telecommunications networks, which may span thousands of miles of
territory, can--and frequently do--contain thousands of different
network elements of various types. made by different manufacturers,
and using different communications protocols.
[0005] Managing these large, complex and heterogeneous
telecommunications networks presents substantial challenges. For
each network element, a network manager needs to know whether the
elements are operating properly and what are the nature and
severity of any problems. For most networks, it is highly desirable
to obtain this information at a network management facility without
having to dispatch personnel to the physical location of the
network element. Systems that provide this information from a
network element to a network management center, usually by
telecommunications links, are known as element management systems
("EMSs"). Once management information regarding a network element
is transmitted to the network management center, the network
manager can analyze the information and direct corrective or other
appropriate action. Once again, it is desirable for at least
certain actions--such as shutting down an overheating radio before
it bums itself out, or rerouting traffic away from a malfunctioning
multiplexer--that the action be taken at the network element site
as the result of a command transmitted from a remote network
management center. Similarly, it is desirable, to the extent
possible, to control and configure network elements remotely from
the physical location of the individual elements. EMSs are used for
these purposes, as
[0006] Network elements of different types, such as radios and
multiplexers. typically require separate EMSs, even if they are
manufactured by the same company. Historically. an EMS for a
particular network element could only be obtained from the
element's vendor, usually at a substantial price. If, for example,
a telecommunications network contains four different models of
digital radios, the network administrator typically has to purchase
and support four different EMSs, even if all the radios are from
the same manufacturer. Thus, managing a telecommunications network
containing network elements of different types, different protocols
and different manufacturers is almost always costly.
[0007] In addition, different manufacturers frequently use
different protocols and commands for managing their network
elements. Often, the same manufacturer uses different protocols and
commands for different types of equipment that it manufactures.
Indeed, even when a manufacturer claims to use a "standard"
protocol for managing network elements (such as Q3, TL-1 or SNMP),
it is not uncommon for that manufacturer to implement that protocol
differently from other manufacturers. Moreover, documentation for a
specific EMS and a specific network element may be unavailable,
incomplete, out-of-date or incorrect. Hardware and software have
bugs and limitations which also must be addressed.
[0008] As a consequence of these and other problems, the expertise
required to program manage and troubleshoot a particular EMS for a
particular type of network element made by one manufacturer is
ordinarily of limited use when it comes to programming, managing
and troubleshooting a different EMS for a different type of network
element or even the same type of network element made by a
different manufacturer. Thus, people who become experts at
supporting particular EMSs and network elements ordinarily cannot
efficiently apply those skills to supporting other EMSs or other
types of network elements.
[0009] It is therefore not uncommon for a single operator to
maintain separate teams of experts for each type of network element
in its telecommunications network. Network administrators who have
already invested substantial sums of money in purchasing separate
EMS systems for a variety of network elements, potentially made by
different manufacturers, may also have to invest substantial sums
of money and resources to develop and maintain the expertise
required to support each type of network element made by each
manufacturer.
[0010] Network administrators trying to reduce the costs associated
with employing separate teams of expert programmers for each type
of network element have attempted to purchase and use commercial
off-the-shelf telecommunications network management solutions to
manage their network elements. These management solutions, however,
can be extremely expensive, frequently support only certain network
elements, and can require extensive system integration and
customization efforts. Consequently, a network administrator using
a commercial off-the-shelf network management application often
still has to purchase separate commercial off-the-shelf
applications for each type of network element. or for each
manufacturer of network elements used in the telecommunications
network.
[0011] Moreover, most commercial off-the-shelf network management
solutions are geared towards the "legacy" architectures of older
telecommunications network management solutions. These legacy-based
solutions frequently do not support the more recent protocols. such
as CORBA and Q3, or do not support a particular manufacturer's
implementation of the more recent protocols, without expensive
modifications. Indeed, some legacy--based solutions may require the
network administrator to change the methodology of managing the
entire telecommunications network.
[0012] In addition, due in large part to the problems discussed
above, many commercial element management systems available today
lack scalability. Each time an organization or network
administrator wants to add a new type of network element to the
telecommunications network, or to start using a new manufacturer, a
new team of experts or a new network management application, or
both, must also be added. This also usually means that the
organization or network administrator must be prepared to take on a
large and expensive integration effort, adding further to the costs
and complexity of upgrading the network.
[0013] Another problem faced by telecommunications network
administrators today is that commercial or third-party EMSs may not
provide the level of flexibility required for certain
telecommunications network applications. For example, if a
telecommunication network requires new or custom user interfaces,
new functionality or new reporting capabilities, many commercial
EMSs lack the flexibility to deploy such new or customized
applications easily and inexpensively.
[0014] Accordingly, today's telecommunications network
administrators are frequently captive to the type and manufacturers
of network elements utilized in their current network. Often, the
manufacturer and type of network elements already present in the
network effectively determine which type of network elements can be
added to the network. or from which manufacturer new network
elements can be obtained what kind of expertise must be obtained to
manage the new network elements and which brand of network
management software can be used. Once deployed, networks and their
management solutions must be supported for many years if the
organization has any hope of recouping the substantial initial
investments required. This often leads telecommunications network
managers to conclude that they have lost control over the growth
and development of their own telecommunications networks. This lack
of control severely restricts an organization's ability to expand
or modify its network, integrate new technology and respond in a
timely manner to their organizations telecommunications
requirements.
[0015] In an attempt to begin to address some of these problems,
the International Telecommunications Union ("ITU") promulgates a
set of telecommunications specifications known as
Telecommunications Management Network ("TMN") standards. The TMN
standards defines relationships between basic network building
blocks (i.e., different network elements, different network
protocols and different network management applications) in terms
of standard interfaces.
[0016] The TMN standards defines five major functional areas for
network management systems, based on key activities performed by
network management personnel. including:
[0017] Fault Management--including trouble management, corrective
actions for service. fault reporting and recovery;
[0018] Configuration Management--including resource provisioning
(timely deployment of resources to satisfy expected service
demands), service provisioning (assigning services and features to
end-users), and configuration of equipment and resources;
[0019] Performance Management--including processes that insure the
most efficient utilization of network resources and their ability
to meet service demands, and collection, correlation, and analysis
of data regarding the service performance of network resources;
[0020] Security Management--including control of access to and
protection of both the network and network management systems
against intentional and accidental abuse, unauthorized access, and
communications loss; and
[0021] Accounting Management--including processes that maintain
customer billing as well as resource inventory.
[0022] The TMN architecture provides for a division of management
capabilities according to layers. Each layer provides a set of the
functional elements (that is, Fault, Performance, Configuration,
Security, and Accounting Management). Not all functional elements
are required at each layer. The TMN Layers (from bottom to top)
are:
[0023] Network Element Layer--This layer typically provides the
interface for managing the NE itself.
[0024] Element Management Layer--This layer provides capabilities
provide for managing multiple network elements usually of the same
type or manufacturer. Typically, this layer emphasizes fault
management, configuration management, performance management and
security for the NEs.
[0025] Network Management Layer--This layer provides network
management for a full network, including circuit configuration.
performance, and fault management, as well as provisioning of
bandwidth.
[0026] Service Management Layer--This layer provides for network
management of the services provided by the network, such as
inventory (accounting management) of bandwidth and services.
[0027] Business Management Layer--This layer provides for network
management of billing, service allocation, and other business
aspects of the network.
[0028] A wide variety of protocols (e.g., Q3, CORBA, SNMP and TL-1)
is used as the communications media between TMN layers. The Q3
protocol is widely used in Europe and Asia as the network
management protocol of choice for numerous network
elements--especially transport networks, that is, networks that
transfer information at very high speeds using fiber optic and
digital microwave radio. Q3 has also seen a surge of activity in
the United States, especially in Synchronous Optical Network
("SONET") and Dense Wave Division Multiplexing ("DWDM")
deployments. Toolkits to build applications using Q3 are supplied
by companies such as Vertel, DSET Corporation. HP. and Sun
Microsystems.
[0029] In the telecommunications network management industry, the
Common Object Request Broker Architecture ("CORBA") is increasingly
being used for integration of telecommunications software
applications and NEs. Essentially, CORBA is a specification for an
object-oriented architecture for distributed applications. CORBA
implementations are provided by a number of companies; the most
widely deployed is called Orbix.TM. from IONA Technologies.
[0030] SNMP, or Simple Network Management Protocol, is a simple
protocol for managing TCP/IP (or Internet-based) computer networks.
SNMP is widely deployed as a management protocol for routers,
bridges and other computer-network related devices. In recent
years. SNMP has been extended as a management protocol for many
telecommunications network elements, most specifically, ATM
(Asynchronous Transfer Mode) switches and routers. The SNMP
protocol is in the public domain, consequently, there are numerous
deployments and implementations.
[0031] TL-1 is by far the most widely used protocol in
telecommunications management. Most of today's transport network
elements deploy TL-1 as the management protocol. Although there is
some standardization to TL-1, most vendors implement either a
subset or superset of the TL-1 commands.
[0032] Accordingly, there is a need for flexible and scalable
element management systems for telecommunications networks that can
monitor and manage very large, heterogeneous telecommunications
networks and support rapid, low-cost integration of new and
different network element types having a variety of protocols and a
variety of manufacturers.
SUMMARY OF THE INVENTION
[0033] An objective of the present invention is to provide a
telecommunications network element management system ("EMS") for
controlling a plurality of diverse network elements, regardless of
the type, protocol or manufacturer of the network elements
("NEs").
[0034] A further objective of the present invention is to provide
an EMS utilizino a core message set that all NEs in the network can
support, thereby reducing redundancy and minimizing the effort and
expense required to integrate new and diverse NEs.
[0035] Another objective of the present invention is to provide an
EMS sufficiently flexible to support network management functions
common to diverse NEs.
[0036] Another objective of the present invention is to provide a
highly-scalable EMS, capable of supporting a large number of
NEs.
[0037] A further objective of the present invention is to provide
an EMS having a mechanism for incorporating diverse network
management interfaces, thereby making the applications and services
of the EMS independent of the protocol used by individual NEs in
the telecommunications network.
[0038] The present invention, as broadly described herein, provides
a method for developing a core set of messages for an EMS for a
telecommunications network, comprising the steps of: reviewing
telecommunications network management functions for each of a
plurality of NEs; selecting the basic telecommunications network
management functions; and creating an element-independent
telecommunications network management message, in a common
telecommunications management message protocol, for each selected
telecommunications management function.
[0039] The present invention, as broadly described herein, also
provides an EMS for a telecommunications network comprising means
for receiving, from a software application, a downstream
element-independent network management message selected from a core
set of downstream element-independent network management messages.
for transmission to a NE. The EMS further includes means for
mapping the downstream element-independent network management
message into a downstream element-dependent network management
message, and into an element-dependent protocol, for the NE. The
EMS also includes means for transmitting the downstream
element-dependent network management message to the NE. As used in
this specification and the appended claims, the term "downstream"
means a logical transmission path towards a NE, regardless of the
actual physical implementation or embodiment.
[0040] The EMS of the present invention may further comprise means
for receiving an upstream element-dependent network management
message from a NE. This EMS also includes means for mapping the
upstream element-dependent network management message into a
upstream element-independent network management message selected
from a core set of upstream element-independent network management
messages, and into a common element-independent message protocol.
The EMS also includes means for transmitting the upstream
element-independent network management message to a software
application. As used in this specification and the appended claims,
the term "upstream" means a logical transmission path away from a
NE, regardless of the actual physical implementation or
embodiment.
[0041] In a preferred embodiment, the EMS in accordance with the
present invention optionally includes means for receiving an
unsolicited element-dependent network management message, such as
an alarm, from a NE, means for mapping the unsolicited
element-dependent network management message into an
element-independent network management message identifying the NE
and the nature and priority of the Lunsolicited element-dependent
network management message, and means for transmitting the
element-independent network management message to a software
application.
[0042] In a preferred embodiment, the EMS in accordance with the
present invention optionally provides support for NEs of more than
one type, or more than one manufacturer or both.
[0043] In a preferred embodiment of an EMS according to the present
invention, the core set of downstream element-independent network
management messages comprises a reduced number of downstream
network management messages supporting basic telecommunications
network management functionality. In a preferred embodiment, basic
network functionality comprises core network management functions
common to a broad array of equipment types and core network
management functions specific to particular equipment types. In
today's environment, a preferred embodiment of the present
invention would support equipment types such as microwave radios,
add/drop multiplexers, terminal multiplexers and fiber
regenerators.
[0044] Additional objects and advantages of the invention are set
forth in part in the description that follows, and in part are
obvious from the description, or may be learned by practice of the
invention. The objects and advantages of the invention may also be
realized and attained by means of the instrumentalities and
combinations particularly set ouit in the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0045] The accompanying drawings, which are incorporated in and
constitute part of the specification, illustrate preferred
embodiments of the invention, and, together with the description.
serve to explain the principles of the invention.
[0046] FIG. 1 provides flowchart of a method of the present
invention for developing a core set of messages for an element
management system for a telecommunications network.
[0047] FIG. 2 depicts an embodiment of an EMS according to the
present invention.
[0048] FIG. 3 depicts, in a preferred embodiment of an EMS
according to the present invention, the logical relationship
between network management messages in a core set of network
management messages.
[0049] FIG. 4 depicts the upstream and downstream flows of network
management messages in a preferred embodiment of an EMS according
to the present invention.
[0050] FIG. 5 depicts an alternate preferred embodiment of an EMS
according to the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0051] Reference will now be made in detail to the preferred
embodiments of the invention, examples of which are illustrated in
the accompanying drawings. Notably, the present invention may be
implemented using software, hardware or any combination thereof, as
would be apparent to those of ordinary skill in the art, and the
figures and examples below are not meant to limit the scope of the
present invention or its embodiments or equivalents.
[0052] A method of developing a core set of messages for an element
management system according to the present invention will now be
described in detail with reference to FIG. 1. That figure provides
a process flowchart illustrating the steps performed in developing
a core set of messages for an element management system in
accordance with the present invention, comprising the steps of (a)
reviewing telecommunications network management functions for each
of a plurality of telecommunications NEs; (b) selecting basic
telecommunications network management functions; and (c) creating
an element-independent telecommunications network management
message, in a common telecommunications message protocol, for each
selected telecommunications management function.
[0053] In a preferred embodiment depicted in FIG. 1, the step of
reviewing telecommunications network management functions for each
of a plurality of telecommunications NEs is performed at Review
Network Management Functions step 101. For this step the functional
specifications for each of a plurality of telecommunications NEs
may be obtained, for example, by requesting them directly from the
vendors, searching for them on the Internet, or by means generally
known to those of ordinary skill in the art.
[0054] Once the functional specifications of a network element are
obtained, they are reviewed and audited for several purposes,
including identification of the NEs network management functions,
such as retrieving the operating temperature of the device, and
identifying the specific network management protocols, such as Q3,
TL-1 or SNMP, used by the NE. These specifications are also
reviewed to ascertain which network management functions are common
to types of NEs made by several manufacturers, as well as different
types of NEs.
[0055] As depicted in FIG. 1, in a preferred embodiment the step of
selecting basic telecommunications network management functions is
performed at Select Basic Functions step 102. The goal of this step
is to develop, from the telecommunications management functions
reviewed at Review Network Management Functions step 101, a reduced
or core set of messages that encompasses no more and no less than
the basic functionality required to manage a telecommunications
network. Several considerations affect this selection process. In a
preferred embodiment, consideration is given to the commonality of
a network management function across different network element
types and manufacturers. The more common a function, the more
likely its inclusion in a core set of basic functions. In a
preferred embodiment, consideration is also given to industry-wide
consensus as to which management functions are considered basic or
necessary or essential, or merely desirable. In a preferred
embodiment, consideration is also given to projections as to future
types or features of NEs and the management functions they will
need to support and by which they will need to be supported. In a
preferred embodiment, consideration is also given to the importance
of the goal of keeping as small as practicable the number of
messages to implement basic network management functions. Achieving
this goal is important to scalability of an EMS and to the ability
quickly and efficiently to add NEs of different types and
manufacturers. At the same time, if the selected set of basic
management functions is too small, then important functions may be
excluded or NEs of certain types or manufacturers may not be
adequately supported. It is therefore contemplated that the core
set of network management functions selected according to the
present invention may change in response to changes in
telecommunications requirements. network implementation practices
and industry consensus.
[0056] Telecommunications NEs can usefully be classified according
to type. Various types of telecommunications NEs, such as microwave
radios and fiberoptic multiplexers. typically support and require
distinct kinds of network management functionality. Certain network
management functions for multiplexers, for example, are not
appropriate for microwave radios. For example, in a preferred
embodiment, where the NE is an add/drop multiplexer, pairs of
optical interfaces may be cross-connected on command from the EMS
to complete a circuit through the multiplexer. This operation is
not available--nor does it make sense--in the case where the NE is
a microwave radio.
[0057] On the other hand, certain network management functions
would be viewed by a person of ordinary skill in the art as common
to all telecommunications NEs within a telecommunications network,
regardless of the type of the NE. The network management function
of setting the time on a specified telecommunications NE, for
example, should be supported by all telecommunications NEs,
regardless of whether the element is a radio, a multiplexer or
another type of device.
[0058] In order to reduce redundancy in developing and using a core
set of network management messages according to the present
invention, in a preferred embodiment the basic common network
management functions are identified separately from the basic
network management functions for specific types of NEs. It is then
preferable, according to a preferred embodiment of the present
invention comprising a network with radio and fiber optic devices,
to subdivide the basic type-specific network management functions
into basic microwave radio network management functions and basic
fiber optic device network management functions. The two classes of
telecommunications NEs referenced herein. as well as the basic
network management functions related to these two classes. are
mentioned by way of example only. Other types of telecommunications
NEs having other basic network management functions, as known to
those of ordinary skill in the art. may also be present in the
telecommunications network and are envisioned to fall within the
scope of this invention.
[0059] In a preferred embodiment of the present invention, the
basic common network management functions, for each NE, include the
functions of:
[0060] Setting a time clock for the NE.
[0061] Retrieving performance data for a specified time period for
the telecommunications NE. Such data would include, for example.
the total number of seconds in a specified time period that the
telecommunications NE was unavailable, the total number of seconds
in a specified time period that the telecommunications NE sustained
severe errors, the total number of framing errors sustained by the
telecommunications NE in a specified time period, and other
performance data as would be apparent to one of skill in the
art.
[0062] Setting performance management threshold values for the
telecommunications NE. This function, for example, specifies which
attributes to monitor on the telecommunications NE and what kind of
alarm will be generated if any of these monitored values falls
outside the specified threshold. This function could be used. for
example, to generate a specific alarm when the number ot framing
errors on the telecommunications NE exceeds a certain value.
[0063] Updating the external output control attributes on the
telecommunications NE. For example, the state (e.g., polarity) of
an external output control may be changed from "normally ON" to
"normally OFF." Another example would be to set the "pulse"
attribute to indicate that the external output control is a "pulse"
instead of a "latch."
[0064] Sending a signal to the external output interface on the NE
for the purpose of controlling external equipment, such as a
generator. For example, by sending a pulse control, the generator
can be started.
[0065] Updating the external input control attributes on the
telecommunications NE. Such attributes include, by way of example,
the setting of the user label attribute to indicate the name of an
assigned input device and other attributes as would be apparent to
one of skill in the art. Such external input points are typically
assigned to external devices to be monitored by the EMS such as
shelter doors, power capabilities, shelter and equipment
temperatures, smoke and fire detectors, tower lights and other
input devices.
[0066] Retrieving operational status information of the
telecommunications NE, such as whether the NE is "in service" or
"out of service."
[0067] Retrieving, entering, editing and removing the
telecommunications NE from the EMS.
[0068] Retrieving and updating protection status for the
telecommunications NE. Protection status for a telecommunications
NE indicates whether the telecommunications NE has an active backup
facility, such as a redundant channel, for use if the primary
facility (or channel) becomes unavailable to carry traffic. For
example, a digital microwave may be configured as a "1+1." meaning
that there is one primary radio link between radio antennas and one
backup link. If the primary link goes down for any reason, the
radio will automatically switch to the backup radio link, using
separate antennas, separate receivers and separate
transmitters.
[0069] Processing the current standing alarms for the specified
telecommunications NE. Such alarms would include, for example
equipment, environmental, communications, facility, security,
quality of service and other standing alarms as would be apparent
to one of skill in the art.
[0070] Some functionality provided with various telecommunications
NEs may not considered essential to the satisfactory operation of
the telecommunications network and may therefore be excluded from
the list of essential common network management functions. In a
preferred embodiment, for example, as long as the element
management system has the capacity to set the current time on each
NE, it is not essential to the management of the telecommunications
network to support the function of setting the current time for the
entire network as a whole, since sending a "set time" command to
each NE would have the same effect. In a preferred embodiment,
other non-essential network management functions include, for
example:
[0071] retrieving the current time on a specified
telecommunications NE:
[0072] resynchronizing the entire network;
[0073] resynchronizing the current alarm list for the
telecommunications NE; and
[0074] resynchronizing the performance management data for a
specified time period for a specified telecommunications NE.
[0075] The basic microwave radio network management functions, in
accordance with a preferred embodiment, comprise the functions of
invoking and releasing protection for the telecommunications NE,
and requesting a manual exercise on one protection unit, related to
the regular channel on the telecommunications NE in order to insure
that the protection (or redundant) channel can carry traffic,
without actually switching traffic to the protection channel.
[0076] In a preferred embodiment, the basic fiber optic device
network management functions comprise the functions of retrieving,
entering, editing and removing a fiber optic facility (hardware and
software components used to provision a communication path) and
retrieving, performing and removing a cross-connection on the
telecommunications NE. In a preferred embodiment depicted in FIG.
1, after Select Basic Functions step 102, in the method of the
present invention the step of creating an element-independent
telecommunications management message, in a common
telecommunications network management protocol, for each selected
telecommunications management function. is performed in Create
Element-Independent Message step 103. This step is begun in a
preferred embodiment by defining a structural definition and
functional interface for the selected function. The functional
interface is characterized by creating a name, Syntax, parameter
list and associated callback method for the selected function.
[0077] For example, in a preferred embodiment, an
element-independent network management message for the function of
retrieving the current list of standing alarms from a specified
network element is created as follows. Using CORBA IDL (Interfact
Definition Language), a structure (or data type) is defined for the
function's input parameter:
[0078] Typedef string NEName;
[0079] This instruction creates a string data type, which can now
be used in subsequent function calls. Next a CORBA IDL function is
defined, as follows:
[0080] Oneway void RetrieveNEAiarms (in EMSCOMMON::NEName
neName);
[0081] As would be apparent to one of skill in the art, the phrase
"Oneway void" in the above function indicates that no immediate
response to the message is expected. In other words, this is a
"oneway" message. As suggested by its name, the function
"RetrieveNEAlarms" directs the NE to provide the EMS with the
current status of any alarms activated in the NE. As also apparent
to one of skill in the art, the word "in" in the above function
indicates that the parameter that follows ("neName") is an "input"
parameter, as opposed to "output" parameter. The input parameter
"neName" is supplied to the CORBA implementation function in order
to identify the telecommunications network element from which the
current list of alarms is to be extracted and the descriptor "EMS
COMMON" identifies a module containing the definition for the data
type "NEName" (in this case a string).
[0082] Thus, when the above-described "RetrieveNEAlarms" function
is used ("called") in an application program, an
element-independent network management message is created and sent
to the telecommunications network element. The message is
"element-independent" because it will operate on any
telecommunications network element in the network, regardless of
the network element's type, protocol or manufacturer. When all of
the standing alarms on the network element have been obtained, a
"callback" function is activated, which will supply the application
program with a list of standing alarms.
[0083] The example message above has one input parameter, "neName,"
and no output parameters. Other messages may be created in
accordance with the present invention and other programming
languages may be used, with or without incorporating multiple input
and output parameters and associated callbacks, as would be evident
to one of ordinary skill in the art. From the above example, it is
also readily apparent to those of ordinary skill in the art how to
create other element-independent network management messages for
specified network management functions in accordance with the
present invention.
[0084] In alternative preferred embodiments, basic network
management functions may be implemented by telecommunications
network elements, by devices connected to telecommunications
network elements, by other components, or by a combination of
elements, devices and components in the network or the EMS as would
be apparent to one of ordinary skill in the art.
[0085] In a preferred embodiment, the basic network management
functions identified in Select Basic Functions step 102 are
implemented in Create Element-Independent Message step 103, using
twenty-eight element-independent network messages:
[0086] set_NETime--Sets the time for a specified NE.
[0087] set_ThresholdData--Sets threshold values for performance
management attributes for an NE.
[0088] get_NE24HourPmData--Retrieves twenty-four hour performance
attributes for a specified NE for specified dates and sends the
response data upstream.
[0089] get_NE15MinPmData--Retrieves fifteen-minute performance
attributes for a specified connected NE and sends the response data
upstream.
[0090] get_CurrentNE15MinPmData--Retrieves current fifteen-minute
performance attributes for a specified NE and sends the response
data upstream.
[0091] set_ExternalOutputControl--Updates the external output
control attributes for a specified NE and sends a response code
upstream.
[0092] Perform_externalOutputControl--Sends a pulse or latch signal
to a specified pin on the external output interface of a specified
NE and sends a response code upstream.
[0093] set_ExternalInputPoint--Updates the external input control
attributes in a specified NE and sends a response code
upstream.
[0094] get_operationalState--Retrieves the current operational
state for a specified NE.
[0095] Get_Equipment--Retrieves a single equipment entity (e.g., a
circuit board) for a specified NE.
[0096] Get_MUXFacility--Retrieves a single fiber-optic device
facility (e.g., signal or port) for a specified NE.
[0097] Get_MUXCrossConnections--Retrieves existing cross
connections for a specified fiber-optic NE.
[0098] Enter_Equipment--Provides initial equipment attributes or
characteristics for a specified NE.
[0099] Edit_Equipment--Edits existing equipment attributes or
characteristics for a specified NE.
[0100] Remove_Equipment--Removes an existing equipment entity for a
specified NE.
[0101] Enter_MUX_Facility--Provides an initial fiber-optic device
facility for a single NE.
[0102] Edit_MUX_Facility--Edits the attributes or characteristcis
of an existing fiber-optic device facility for a single NE.
[0103] Remove_MUX_Facility--Removes an existing fiber-optic device
facility for a single NE.
[0104] Connect--Connects two optical or electrical termination
points for a fiber-optic device in order to create a circuit
through a specified NE at a specified rate, and sends a response
code and the identifier of the circuit upstream.
[0105] Disconnect--Disconnects an existing circuit for a specified
NE and sends a response code upstream.
[0106] Get_AllProtectionGroups--Retrieves protection group objects
(e.g.. protection subsystems) for a specified NE.
[0107] Get_ProtectionUnits--Retrieves protection unit objects (e.g.
redundant and normal channels) for a specified NE.
[0108] Invoke_Protection--Requests that a NE switch from its
regular channel or protection unit to a redundant or backup channel
or protection unit and sends a response code upstream.
[0109] ReleaseProtection--Requests that a NE switch back to its
normal channel or protection unit from a redundant or backup
channel or protection unit and sends a response code upstream.
[0110] RadioInvokeExercise--Requests that a NE perform a switch
from its regular channel or protection unit to a redundant or
backup channel or protection unit without actually routing traffic
onto the redundant channel or protection unit, and sends a response
code upstream.
[0111] RetrieveNEAlarms--Retrieves existing alarms for a specified
NE.
[0112] ClearAlarm--Clears a standing alarm within the EMS and for a
specified NE.
[0113] ProcessEVent--Passes unsolicited event and alarm information
(Notificationlnfo) throughout the EMS.
[0114] A core set of element-independent network management
messages may readily be divided into downstream element-independent
network management messages and upstream element-independent
network management messages, as is readily apparent to one ot skill
in the art.
[0115] FIG. 2 depicts a preferred embodiment of an element
management system in accordance with the present invention,
including (a) means for receiving, from a software application, a
downstream element-independent network management message selected
from a core set of downstream element-independent network
management messages. for transmission to a telecommunications NE;
(b) means for mapping the downstream element-independent network
management message into a downstream element-dependent network
management message, and into an element-dependent protocol. for the
telecommunications NE; and (c) means for transmitting the
downstream element-dependent network management message to the
telecommunications NE.
[0116] With reference to the preferred embodiment shown in FIG. 2,
the receiving means of an EMS system 202 according to the present
invention is Upstream Agent 212. As depicted in FIG. 2, Upstream
Agent 212 receives a downstream element-independent network
management message from a Network Management Layer software
application, depicted in FIG. 2 as NMS-EMS Interface 213, for
transmission to a telecommunications network element, depicted in
FIG. 2 as Network Element 230. Other Network Elements 231-239 are
also depicted in FIG. 2. In a preferred embodiment, the downstream
element-independent network management message received by Upstream
Agent 212 is selected from a core set of downstream
element-independent network management messages developed in
accordance with the method described with reference to FIG. 1.
Upstream Agent 212 provides an external interface, in a
standardized protocol, such as Q3 or other protocol known to one of
skill in the art, between EMS 202 and NMS-EMS Interface 207 and
Network Management Layer applications and products. such as Other
NMS Application 206 and Other NMS Application 208 in NMS
Applications 201. Upstream Agent 212 also receives messages to be
forwarded to NMS-EMS Interface 207. In a preferred embodiment.
Upstream Agent 212 may be implemented in hardware, software. or a
combination of both, as is known to persons of skill in the
art.
[0117] In the preferred embodiment depicted in FIG. 2, the means
for mapping the downstream element-independent network management
message into a downstream element-dependent network management
message is Adapter Block 220. Adapter Blocks 221-229 perform
similar functions. In the preferred embodiment depicted in FIG. 2,
Upstream Agent 212 passes an element-independent downstream message
to Request Broker 211. which in turn passes the element-independent
network management message to one of Adapter Blocks 220-229 serving
the NE identified in the network management message. Each adapter
block is suitably equipped to receive (and transmit) network
management messages. Request Broker 211 may be implemented using
hardware, software or a combination of both, as known to persons of
skill in the art, and using techniques for routing network
management messages to adapter blocks serving specific NEs as known
to persons of skill in the art.
[0118] As depicted in FIG. 2, Adapter Blocks 220 through 229 map
(or translate) the downstream element-independent message into an
element-dependent network management message and an
element-dependent protocol, such as TL-1, SNMP or Q3, for a
specified NE. Network Elements 230 through 239 may comprise, for
example, microwave radios, and fiber optic devices such as digital
multiplexers. In a preferred embodiment depicted in FIG. 2, Adapter
Block 220 serves Network Element 230 which is for example a radio.
Adapter Block 221 serves Network Element 231, which is for example
a multiplexer, and so forth. This service includes transmitting and
receiving network management messages, using suitable hardware and
software, to and from adapter blocks.
[0119] In a preferred embodiment, multiple units of the same type
and manufacture of a network element may be served by a single
adapter block. For example, all NEC microwave radios in a network
may be served by a single adapter block. It is also possible that a
single adapter block may serve network elements of different types
and different manufacturers. as would be apparent to one skilled in
the art, without departing from the present invention. Request
Broker 211 may thus route a single message to multiple adapter
blocks. For example, in the preferred embodiment depicted in FIG.
2, to reset the time on an entire network, Request Broker 211 would
send a single element-independent message to all Adapter Blocks 220
through 229.
[0120] With reference to FIG. 2, in a preferred embodiment, another
example of the mapping function occurs in connection with the
transmission by Request Broker 211 of an element-independent
network management message, "Connect," to Network Element 231 (a
fiber-optic add/drop multiplexer as depicted in FIG. 2). This
message instructs that multiplexer to establish a connection within
the multiplexer to form a circuit from point A to point B. The
element-independent message is transmitted to Adapter Block 221
serving Network Element 231, and includes information sufficient
for Network Element 231 to receive and execute the instruction.
Such information includes, for example, the identity of Network
Element 231 according to the specific telecommunications network,
the identifiers of the "from" and "to" ports, and an identifier
specifying the transmission rate.
[0121] In the preferred embodiment depicted in FIG. 2. Adapter
Block 221 receives the Connect message, and, using a combination of
hardware and software as is known to one of skill in the art,
selects an appropriate message for enabling Network Element 231 to
execute the instruction. In a preferred embodiment, this selection
is accomplished using a table lookup or other methods known to one
of skill in the art for mapping the element-independent network
management message to an appropriate corresponding
element-dependent message. Adapter Block 221 then creates an
element-dependent message, in the protocol utilized by the
particular type and manufacture of Network Element 231 (e.g., Q3),
including information sufficient to enable Network Element 231 to
execute the Connect instruction to establish a connection to form a
circuit between point A and point B within Network Element 231.
[0122] (In this example, at some later time Network Element 231
generates an element-dependent response to the Connect instruction,
in order to inform EMS 202 that the connection has been formed, and
providing an identifier for the connection. This response message
is an element-dependent upstream message. The mapping of
element-dependent upstream messages into element-independent
network management messages, and their upstream transmission from
network elements, are described in detail below.)
[0123] In a preferred embodiment depicted in FIG. 2, the means for
transmitting the downstream element-dependent network management
message to the telecommunications network element are Adapter
Blocks 220-229. This transmission is accomplished using equipment
and techniques as are known to those of skill in the art.
[0124] In another preferred embodiment (not depicted), the
functions of Upstream Agent 212. Request Broker 211 and Adapter
Blocks 220 through 229, as described above. may be implemented,
without diverging from the scope of the present invention, by
various structures. as would be apparent to those of ordinary skill
in the art. Similarly. in another preferred embodiment (also not
depicted) the functions of Upstream Agent 212. Request Broker 211
and Adapter Blocks 220 through 229, as described above, may also be
implemented by means of other separate structures or a combination
of structures, different from those depicted in FIG. 2.
[0125] As depicted in FIG. 2, an EMS of the present invention may
include (a) means for receiving an upstream element-dependent
network management message from a telecommunications network
element; (b) means for mapping the upstream elementdependent
network management message into a upstream element-independent
network management message selected from a core set of upstream
element-independent network management messages, and into a common
element-independent message protocol; and (c) means for
transmitting the upstream element-independent network management
message to a software application.
[0126] In a preferred embodiment depicted in FIG. 2, the means for
receiving an upstream message from Network Element 230 is Adapter
Block 220. Adapter Blocks 221-229 perform similar functions with
respect to Network Elements 231-239, respectively. As depicted in
FIG. 2, the receiving means may be implemented using techniques and
technologies as known to one of skill in the art. According to the
present invention, upstream element-dependent messages may be
solicited (for example in response to a downstream message) or
unsolicited (for example in response to an alarm triggered by a NE,
as known to one of skill in the art). Each Adapter Block 220-229
maps each received upstream element-dependent network management
message into an upstream element-independent network management
message. Again, these element-independent network management
messages are selected from a core set of upstream
element-independent network management messages created in
accordance with the method of the present invention described with
reference to FIGS. 1 and 2, above. Adapter Blocks 220 through 229
also translate the element-dependent message into a common
element-independent message protocol, as known to one of skill in
the art.
[0127] For example, with reference to FIG. 2, in a preferred
embodiment an unsolicited network element-dependent alarm message
may be generated by Network Element 230. The element-dependent
alarm message is transmitted in the protocol (e.g.. Q3) used by the
particular manufacturer for the particular equipment type of
Network Element 230. The message would typically specify the alarm
type (e.g., equipment alarm, software alarm, environmental alarm,
communications alarm) and the probable cause (e.g power loss,
software interruption, enclosure entry, signal loss). The
element-dependent alarm message is received by Adapter Block 220
serving Network Element 230. In a preferred embodiment, a
combination of computer hardware and software in Adapter Block 220,
as known to one of skill in the art, parses the element-dependent
alarm message, extracting the information to be transmitted to
Event Manager 210, including the identity of Network Element 220,
the fact that the messages is an unsolicited alarm message, the
type of the alarm, and the probable cause. The combination of
hardware and software in Adapter Block 220 then determines that
element-independent network management message "ProcessEvent" is
the appropriate network management message from the set of core
network management messages, for transmitting the alarm messagle
information to Event Manager 210. This determination is made using
a table look-up or other method, as is known to one of skill in the
art, for selecting the "ProcessEvent" message to beind in response
to the received element-dependent alarm message. The combination ot
hardware and software in Adapted Block 220 also creates an
element-independent network management message "ProcessEvent,"
using CORBA. including appropriate information, such as the
identity of Network Element 220, the type of the alarm, and
probable cause information. Adapter Block 220 then transmits that
element-independent message, via CORBA Backbone 215, to Event
Manager 210. In a preferred embodiment. unsolicited messages are
generally routed from the Adapter Blocks 220-229, directly to Event
Manager 210 where the messages (in the form of element-independent
messages) are then distributed to other EMS applications such as
Log Manager 213 and Upstream Agent 212.
[0128] As is apparent to one of skill in the art, the mapping of
other upstream element-dependent network management messages into
corresponding upstream element-independent network management
messages (and the mapping of downstream element-independent network
management messages into corresponding downstream element-dependent
network management messages) may be similarly accomplished. In a
preferred embodiment, a CORBA IDL compiler and Object Request
Broker implementation, available from IONA Technologies (Orbix.TM.
product) is used to facilitate the establishment of the
correspondences between element-dependent and element-independent
upstream network management messages, and between element-dependent
and element-independent downstream network management messages.
Other compilers and implementations may be used, as known to those
of skill in the art.
[0129] In a preferred embodiment, responses by the NEs to
downstream messages (as distin(guished from unsolicited upstream
messages) which are mapped to element-independent messages by
Adapter Blocks 220-229 are routed to Request Broker 211. which then
further routes the element-independent message (e.g.,
Connect_Response) as a callback to the originating application. In
a preferred embodiment, the message routing scheme of Adapter
Blocks 220-229 routes all unsolicited messages to Event Manager 210
and all Responses (to previous down-stream requests) to Request
Broker 211. In such an embodiment. Adapter Blocks 220-229 simply
note the type of messages received to determine how to route any
responsive element-independent upstream message.
[0130] In the preferred embodiment depicted in FIG. 2, the means
for transmitting the upstream element independent network
management message to a software application includes Request
Broker 211 and Upstream Agent 212. As depicted in FIG. 2, Request
Broker 211 receives network management messages from Adapter Blocks
220-299, and routes those messages to Upstream Agent 212, which in
turn transmits them upstream to NMS-EMS Interface 213 in NMS
Applications 201. Means, techniques and equipment for transmitting
messages to software applications are known to one of skill in the
art.
[0131] As depicted in FIG. 2, an EMS of the present invention may
include (a) means for processing fault management information; (b)
means for logging all network notifications and events into a
database; (c) means for forwarding email from the software
application; and (d) means for storing notifications and
events.
[0132] In a preferred embodiment depicted in FIG. 2, means for
processing fault management information is Event Manager 210, which
is the central processing entity for the EMS. responsible for
managing all "standing alarms," as well as providing
synchronization between itself and an optional fault management
software application (not depicted). In a preferred embodiment, all
events that are generated within the EMS are processed b Event
Manager 210. Event Manager 210 correlates events received from user
interface applications (not depicted) and Adapter Blocks 220-229,
and synchronizes this constatlytt changing list with registered
client applications.
[0133] In a preferred embodiment, Event Manager 210 also provides
alarm correlation (i.e., certain sets of alarms will invoke other
alarms), alarm translation, alarm filtering. e-mail user
notifications and external alarm feeds for other third-party
network management systems (typically through EMS-NMS Interface
207). In addition to receiving fault and alarm data, Event Manager
210 also processes performance data and forwards the performance
data to the appropriate log manager, depicted in FIG. 2 as Log
Manager 213 for insertion into an EMS Log 214.
[0134] In a preferred embodiment, Event Manager 210 receives three
types of messages from Adapter Blocks 220-229: unsolicited
messages, twenty-four hour performance data, and eight-hour
performance data (i.e., thirty-two sets of fifteen-minute
performance data). An unsolicited message is generated, for
example, when an alarm or other similar event has occurred on
Network Elements 230--239. In a preferred embodiment. Log Manager
Server 213 maps data as received, from Adapter Blocks 230-239
through Event Manager 210, into pre-defined schema objects in the
EMS Log 214.
[0135] FIG. 3 depicts, in a preferred embodiment of an EMS
according to the present invention, the logical relationship
between network management messages in the core set of network
management messages. In the preferred embodiment depicted in FIG.
3. Module EMSCommon 301 provides data-type definitions for core
network management messages common to all applications within the
EMS, including Module EMS Interface 310. Module Event Manager 320
and Module Log Manager 321. Module EMS Interface 310. which
provides the core network management messages common to all NEs in
the EMS. inherits (utilizes) the data-type definitions defined in
Module EMSCommon 301. So, for example, if Module EMSCommon 301
defines the data type for NEName as a "string," Module EMS
Interface 310 can utilize the NEName string type. Module Event
Manager 320 and Module Log Manager 321 are specific applications
that utilize data-type definitions from EMSCommon. In a preferred
embodiment, other applications (not shown in FIG. 3) such as a
request broker and an EMS agent, are implemented similarly.
[0136] In the preferred embodiment depicted in FIG. 3, Module Radio
311 and Module MUX 312 provide the core set of type-specific
network management messages for digital microwave radios and fiber
optic devices, respectively. In this embodiment, each of Module
Radio 311 and Module MUX 312 inherits the type definitions defined
in Module EMS Interface 310. NE-specific interfaces, depicted in
FIG. 3 as Module 2000S 313, Module IMT-150 314 and Module FLM-150
315 contain type definitions for core network management messages
for specific NEs. In the preferred embodiment depicted in FIG. 3,
Module 200S0313 inherits type definitions from Module Radio 311;
and Module IMT-150 314 and Module FLM-150 315 inherit type
definitions from Module MUX 312. In a preferred embodiment,
additional NE-specific modules are implemented similarly.
[0137] FIG. 4 depicts network management message flows in a
preferred embodiment of an EMS of the present invention. It should
be noted that each of the message flows depicted in FIG. 4 is a
logical message flow, and may be implemented. as is known in the
art. using a physical or electronic path different from the logical
message path. As depicted in FIG. 4, a preferred embodiment of an
EMS includes EMS Applications 501, NMS (Network Management System)
Applications 505, and EMS Domain 510. EMS Applications 501 includes
Fault Performance Applications module 503 and Configuration
Applications module 502. NMS Applications 505 includes NMS-EMS
Interface 506 and other NMS Applications 507.
[0138] In the preferred embodiment depicted in FIG. 4, EMS Domain
510 includes Event Manager 511, Request Broker 512, Upstream Agent
513, Log Manager 514, EMS Log 515, and EMS Platform 516. EMS
Platform 516, in turn, includes CORBA Backbone 517 and Adapter
Blocks 520,521,522 and 523. As is apparent to one of skill in the
art, adapter blocks may be added or removed from the embodiment
depicted in FIG. 4.
[0139] The functions and structures of each of the applications,
modules, domains platforms. managers, agents, blocks and other
elements depicted in FIG. 4 are described with reference to FIGS. 2
or 3, above, or are apparent to one of skill in the art in light of
those descriptions. Each of those functions may be implemented in
hardware or software, or a combination of hardware and software,
and in various structures as known to one of skill in the art.
[0140] In the preferred embodiment depicted in FIG. 4,
NE-independent network management messages are transmitted:
[0141] from Event Manager 511 to Fault/Performance Applications
503;
[0142] from Event Manager 511 to Upstream Agent 513;
[0143] from Event Manager 511 to Log Manager 514;
[0144] from Request Broker 512 to Configuration Applications module
502, and from Configuration Applications module 502 to Request
Broker 512;
[0145] from Request Broker 512 to Upstream Agent 513, and from
Upstream Agent 513 to Request Broker 512;
[0146] from Upstream Agent 513 to NMS-EMS Interface 506, and from
NMS-EMS Interface 506 to Upstream Agent 513; and
[0147] from Log Manager 514 to EMS Log 515;
[0148] from Request Broker 512 via CORBA Backbone 517 (the
NE-independent messages transmitted between these two modules
include NE-independent request messages and NE-independent messages
in response to those request messages);
[0149] via CORBA Backbone 517 to Event Manager 511 (including
unsolicited NE-independent alarm messages); and
[0150] via CORBA Backbone 517 to and from each of Adapter Blocks
520-523.
[0151] In the preferred embodiment depicted in FIG. 4, NE-dependent
network management messages flow in each direction between each of
Adapter Blocks 520, 521. 522 and 523 and the specific Network
Element 530, 531, 532 or 533 served by the respective Adapter
Block.
[0152] The composition of NE-independent and NE-dependent network
management messages, and the mapping between NE-independent and
NE-dependent network management messages are described in detail
with reference to FIGS. 1, 2 and 3. above.
[0153] In an example of another preferred embodiment of an EMS
according to the present insention. depicted in FIG. 5, multiple
EMSs may be distributed geographically to manage separate networks
or network segments as needed. In the example shown in FIG. 5.
Networks 601. 602, 603 and 604 are coupled to each other by means
of Ethernets 610. 620, 630 and 643, Routers 650, 651, 653 and 654,
and Frame Relay network 652. In Network 601. the EMS is distributed
among two structures, EMS Server Components 611 and EMS Server
Adapter Blks 612. In a preferred embodiment, EMS Server Components
611 contains basic EMS components described in detail above, such
as an Event Manager. a Log Manager. a Request Broker, and an
Upstream Agent (not depicted). The other structure in Network 601,
depicted as EMS Server Adapter Blks 612, contains all of the
adapter blocks serving Network Elements 613. The function and
operation of adapter blocks is described in detail with reference
to FIGS. 2 and 4. In the preferred embodiment depicted in FIG. 5,
user applications, such as an accounting program, may reside in yet
another structure, depicted in FIG. 5 as EMS User Applications 614.
In the EMS embodiment illustrated by Network 601, the EMS behaves
as it would if all components were deployed in a single
structure.
[0154] In the networks depicted in FIG. 5 as Networks 602 and 603,
all EMS Server components are deployed on a single structure,
illustrated in FIG. 5 by EMS Servers 622 and 631 for each of
Network 602 and Network 603, respectively. The EMS User
Applications 621 and 632 may be deployed on one or more separate
workstations. and those may be available over Ethemets 620 and 630,
for each of Networks 602 and 603.
[0155] In the preferred embodiment depicted in FIG. 5, Network 604
supports a network management center for Networks 601, 602 and 603.
EMS User applications 642 support NE management functions for each
of Networks 601, 602 and 603, thus enabling centralized management
of the NEs in each of those networks. NMS Server 644 and NMS User
Applications 641 support network management functions at the TMN
Network Laver. providing enhanced management capabilities at a
higher level, as known to one of skill in the art.
[0156] The connection of separate networks through Frame Relay 652
illustrates one embodiment of the present invention. In alternative
embodiments, the links between separate networks may be established
through other telecommunications networks and devices, as known to
one of skill in the art.
[0157] As more networks or network segments are added, additional
EMSs may be deployed as needed without impacting performance of any
existing EMSs. If a single EMS must manage a large number of NEs,
then the EMS itself may be distributed over several machines.
[0158] The present invention has been disclosed and described
herein in what is considered to be its most preferred embodiments.
It should be noted that variations and equivalents may occur to
those skilled in the art upon reading the present disclosure and
that such variations and equivalents are intended to come within
the scope of the invention and the appended claims.
* * * * *