U.S. patent application number 11/566178 was filed with the patent office on 2008-05-22 for direct binary file transfer based network management system free of messaging, commands and data format conversions.
Invention is credited to Mark Henrik Sandstrom.
Application Number | 20080120399 11/566178 |
Document ID | / |
Family ID | 39430658 |
Filed Date | 2008-05-22 |
United States Patent
Application |
20080120399 |
Kind Code |
A1 |
Sandstrom; Mark Henrik |
May 22, 2008 |
Direct Binary File Transfer Based Network Management System Free of
Messaging, Commands and Data Format Conversions
Abstract
Telecommunication network management operations are performed
based on accessing network management data (NMD) files via GUIs and
general purpose computers including a network management system
(NMS) server, and automatic routines for transferring binary NMD
files between the general purpose computers and remote network
elements (NEs) being managed. A system user produces configuration
files at the NMS server for NEs using a network management GUI, and
the hardware of NEs automatically complete the network management
operations indicated by the NMD files transferred to them from the
NMS server and produce their status files to the NMS server. The
network management GUI displays network status based on the latest
NE status files at the NMS server. This provides direct, binary
file transfer based NMS communication that avoids the complexity
and restrictions of intermediate messaging protocols or transaction
languages and conversions thereof.
Inventors: |
Sandstrom; Mark Henrik;
(Calgary, CA) |
Correspondence
Address: |
FENWICK & WEST LLP
SILICON VALLEY CENTER, 801 CALIFORNIA STREET
MOUNTAIN VIEW
CA
94041
US
|
Family ID: |
39430658 |
Appl. No.: |
11/566178 |
Filed: |
December 1, 2006 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
60866208 |
Nov 16, 2006 |
|
|
|
Current U.S.
Class: |
709/221 |
Current CPC
Class: |
H04L 41/00 20130101;
H04L 41/22 20130101; H04L 41/0846 20130101; G06F 9/4416 20130101;
H04L 41/0856 20130101 |
Class at
Publication: |
709/221 |
International
Class: |
G06F 15/177 20060101
G06F015/177 |
Claims
1. A method for managing network elements (NEs), the method
comprising: storing a plurality of NE configuration files in a
plurality of directories on a network management systems (NMS)
server, each directory associated with a particular NE and
containing a NE configuration file, where each NE configuration
file represents a set of intended binary contents of segments in
memory spaces of the associated NE; transferring, via a repeating
routine, one or more of the NE configuration files from the NMS
server to the associated NEs; and generating a NE status file at
one or more of the NEs, where each NE status file represents a set
of actual binary contents of segments in memory spaces of the
associated NE; and transferring, via a repeating routine, the NE
status files from the NEs to the directories in the NMS server
associated with each NE.
2. The method of claim 1, wherein transferring the NE configuration
files and transferring the NE status files occur independently of
each other.
3. The method of claim 1, wherein at least one of the NE
configuration files is a NE program file.
4. The method of claim 1, wherein at least one of the NE
configuration files is a NE control file that represents intended
contents of a NE control register segment within the memory space
of the NE associated with the NE configuration file.
5. The method of claim 1, wherein the NE status files represent
contents of a set of NE status register segments within the memory
spaces of the NEs associated with the NE status files.
6. A system for configuring and monitoring network elements (NEs),
the system comprising: a file server for storing binary network
management data (NMD) files so that each NMD file is associated
with a particular NE, where the file server is configured to
transfer the NMD files to the NEs associated therewith; a plurality
of NEs in communication with the file server, each NE configured to
store, via a repeating routine, NMD files received from the file
server in a local memory so that intended actions associated with
the NMD files occur automatically as a consequence of storing the
NMD files in the local memory of the NE, each NE further configured
to copy, via a repeating routine, their status register contents
via an NMD file to the file server; and a user interface coupled to
the file server for providing user access to the NMD files at the
file server, wherein the user interface is configured to present a
current network status based on the NMD files copied from the NEs
to the file server.
7. The system of claim 6, wherein the file server provides a
dedicated directory for storing the (NMD) files associated with
each NE configured and monitored by the system.
8. The system of claim 6, wherein the NMD files represent contents
of segments in the local memories of the NEs associated
therewith.
9. The system of claim 6, wherein one or more of the NMD files
comprise a NE control file that represents intended contents of a
NE control register segment within the local memories of the NE
associated with the NMD file.
10. The system of claim 6, wherein one or more of the NMD files
comprise a NE status file that represents contents of a NE status
register segment within the local memories of the associated
NE.
11. The system of claim 6, wherein one or more of the NMD files
comprise a file that represents contents of NE device registers at
the associated NE.
12. The system of claim 6, wherein one or more of the NMD files
comprise a NE program file for the associated NE.
13. The system of claim 12, wherein at least one of the NE program
files is a binary file for configuring NE hardware logic.
14. The system of claim 12, wherein the NE program files comprise
binary files for configuring NE hardware logic and binary
executable programs for microprocessors of the NEs associated
therewith.
15. A network management process comprising a set of sub-processes
including: transferring, via a set of repeating automatic file
transfer routines, binary network management data (NMD) files
between a network management system (NMS) server and network
elements (NEs), wherein each NMD file represents contents of
segments within memory spaces of the NE associated therewith;
performing, by each NE, a set of NE-side actions for network
management operations associated with the NMD files transferred
from the NMS server to the NE, at least some of the NE-side actions
performed automatically by hardware without software involvement;
and performing, by the NMS server and via a related user interface,
additional network management operations associated with the NMD
files.
16. The process of claim 15, wherein transferring the binary NMD
files comprises: copying, by each NE, NE configuration files
associated with the NE from a directory at the NMS server
designated for configuration files for the NE to local memories of
the NE, copying, by each NE, contents of a status register segment
within local memories of the NE as a NE status file to a directory
at the NMS server designated for status files from the NE.
17. The process of claim 16, wherein each NE status file represents
contents of device registers of the associated NE.
18. The process of claim 16, wherein each NE status file represents
contents of status registers of the associated NE.
19. The process of claim 16, wherein the NE configuration files
associated with a NE comprises at least one NE program file and one
NE control file.
20. The process of claim 19, wherein the NE control file represents
contents of control registers of the associated NE.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional
Application No. 60/866,208, filed Nov. 16, 2006, which is
incorporated by reference in its entirety (and referred to herein
with the reference number [5]).
[0002] This application is also related to the following, each of
which is incorporated by reference in its entirety: [1] U.S.
application Ser. No. 10/170,260, filed Jun. 13, 2002, entitled
"Input-Controllable Dynamic Cross-Connect"; [2] U.S. application
Ser. No. 10/192,118, filed Jul. 11, 2002, entitled "Transparent,
Look-Up-Free Packet Forwarding Method for Optimizing Global Network
Throughput Based on Real-Time Route Status"; [3] U.S. application
Ser. No. 10/382,729, filed Mar. 7, 2003, entitled
"Byte-Timeslot-Synchronous, Dynamically Switched Multi-Source-Node
Data Transport Bus System"; [4] U.S. application Ser. No.
11/245,974, filed Oct. 11, 2005, entitled "Automated, Transparent
System for Remotely Configuring, Controlling and Monitoring Network
Elements"; and [6] U.S. application Ser. No. 11/563,079, filed Nov.
24, 2006, entitled "Intelligent Network Alarm Status
Monitoring."
BACKGROUND
[0003] The present invention pertains to the field of telecom
network management systems, in particular to network management
communications.
[0004] Acronyms used in this specification are defined below:
[0005] GUI Graphical User Interface [0006] HW Hardware [0007] IF
Interface [0008] NE Network Element [0009] NMS Network Management
System [0010] PC Personal Computer [0011] SW Software
[0012] Conventional telecom network management systems (NMS) rely
on command and messaging based communications for transactions and
information distribution between various elements of the NMS and
the network being managed. Examples of such commonly used messaging
and command based NMS communications techniques are various
versions of Simple Network Management Protocol (SNMP), Transaction
Language 1 (TL1) and Common Management Information Protocol (CMIP).
Moreover, conventional NMS implementations are often based on
complex, technology and system vendor specific concepts, such as
Management Information Bases (MIBs), for storing or representing
various sets of network management objects, and various types of
methods to operate on, e.g., given MIB objects.
[0013] These conventional NMS transactions and methods are normally
event-triggered such that they can occur spontaneously or in an
unsolicited manner. For example, they may occur based on dynamic
events that take place on network data plane, based on automated
NMS response to particular information received from the network
being managed, or based on human operator initiated network
management operations. For instance, network defect or fault
activations and de-activations cause NMS messages among various
elements of NMS implementations with conventional NMS technologies.
Likewise, individual transactions, such as accessing a given
parameter at a network element (NE) (e.g., reading a NE performance
monitoring status register or re-configuring a NE control
register), involve their specialized messaging and command based
transactions with conventional NMS techniques. Moreover, to
complete even such a basic NMS transaction, several stages of
protocol, message, language and data format conversions are
involved with conventional NMS implementations. These messaging
based prior art NMS schemes are prone to become overloaded during
times of high loads of NMS and network event activities. As a
consequence, conventional network management and NMS communications
systems and methods are reactive in their nature and impulsive in
operation, causing several significant problems inherent with them.
These problems include the following: [0014] The conventional NMS
performance degrades when the NMS capabilities are most urgently
needed, e.g., during bursts of messaging and transaction triggering
network events, e.g., major network failures. [0015] Several
functional components of conventional NMS techniques are vendor
dependent or vendor specific. This causes the full system
integration to become complicated and requiring various stages of
integration SW, i.e., middleware to be designed between the
functional components, resulting in lost NMS transparency from NMS
user IF to the network element HW, reduced system flexibility and
increased cost. [0016] Many conventional NMS techniques are
specific to certain protocols, languages or data formats, causing
the need for various stages of protocol conversion agents and the
like, further complicating the conventional NMS implementations
while making them less transparent and less flexible. [0017] Since
NMS operations with conventional systems and technologies are
typically based on a predefined, fixed set of commands or methods
(e.g., requests, responses etc. predefined atomic transactions)
specific to and limited by the technologies in use at a given
implementation, the scope of possible functionality supported
through conventional NMS are commonly strictly restricted to only
such a subset of capabilities of the components of the NMS
implementation that is supported by each component throughout the
implementation.
[0018] It is thus observed that, even with their exhaustive
implementational complexity, conventional NMS techniques are
usually inefficient in operation. Accordingly, there is a need for
innovations that enable streamlined network management
communications, providing more intuitive, transparent and flexible
operational capabilities with architecturally improved scalability,
reliability and performance, especially under heavy load of network
management and network data plane event activities.
SUMMARY
[0019] Embodiments of the invention provide efficient systems and
methods for unrestricted network management operations based on the
transfer of binary network management data (NMD) files between a
network management systems (NMS) server and remote network elements
(NEs) being managed through the NMS.
[0020] In one embodiment, a method for managing NEs includes
repeatedly, via periodical routines, transferring NE program and
control files from NE-specific directories at the NMS server to
their related NEs, and transferring NE status files from NEs to
their associated directories at the NMS server. The NE control
files represent the intended binary contents of their corresponding
NE control register segments, and the NE status files represent the
binary contents of NE status register segments within the memory
space of their associated NEs.
[0021] In one embodiment, a network management system for
configuring and monitoring remote NEs comprises an NMS file server
for storing binary NMD files associated with the NEs. The system is
configured to periodically transfer NMD files between the file
server and the NEs. A graphical user interface (GUI) provides user
access to the NMD files at the NMS file server. The intended
actions associated with the NMD files transferred to the NEs
generally occur as automatic consequences of the NEs storing these
files at their local memories. The NMS GUI automatically displays
current network status based on the NMD files transferred from the
NEs to NMS file server. The NMS file server provides dedicated
directories for NMS files of each NEs being managed through the
NMS, and the NEs know which NMD file directories at the NMS server
to access based on their unique NE IDs configured individually for
each NE hardware unit, as the NE-specific NMD directory names at
the NMS server, in an embodiment of the invention, include the NE
ID for the NE associated with each directory.
BRIEF DESCRIPTION OF THE DRAWINGS
[0022] FIG. 1 illustrates the functional architecture for a network
management communications system involving an NMS file server and a
set of NEs, in accordance with an embodiment of the invention.
[0023] FIG. 2 is a diagram of a logical directory structure at the
NMS file server shown in FIG. 1.
[0024] FIG. 3 is a diagram of a logical structure of a local memory
space of an NE shown in FIG. 1
[0025] The following symbols and notations used in the
drawings:
[0026] A box drawn with a dotted line indicates that the set of
objects inside the box form an object of higher abstraction level,
such as in FIG. 2 an NE specific directory 29 comprising
sub-directories 26, 27 and 28.
[0027] Lines or arrows crossing in the drawings are decoupled
unless otherwise marked.
[0028] Arrows between boxes in the drawings represent a path of
information flow and can be implemented by any communications means
available, such as Internet or Local Area Network based
connections. A line connecting elements is considered a
bi-directional communication path unless a direction is indicated
with an arrow.
[0029] The symbol `\` represents a logical root of a file system or
a directory structure.
[0030] Three dots between instances of a given object indicate an
arbitrary number of instances of such an object, e.g. NEs 9 in FIG.
1, repeated between the drawn instances.
[0031] The figures depict various embodiments of the present
invention for purposes of illustration only. One skilled in the art
will readily recognize from the following discussion that
alternative embodiments of the structures and methods illustrated
herein may be employed without departing from the principles of the
invention described herein.
DETAILED DESCRIPTION
[0032] FIG. 1 presents an overview of functional architectural of
the network management process of present invention. At a
high-level, the NMS of the invention, via a set of automatic
routines, transfers binary network management data (NMD) files
between an NMS file server 7 and a set of NEs 9(a), 9(b), 9(c) etc.
(later referred simply to as NEs 9, or NE 9 for any individual one
of the NEs 9(a) through 9(z)), while network management actions
occur as automatic consequences of the contents of the NMD
files.
[0033] The NMS process of FIG. 1 is based on the following mutually
asynchronous and conceptually de-coupled sub-processes:
[0034] 1) A set of automatic file transfer routines transfers NMD
files between the NMS server 7 and the NEs 9;
[0035] 2) The NEs perform on their end the appropriate NMS actions
associated with the NMD files;
[0036] 3) The NMS GUI 4 acts on the NMD files at the NMS server 7,
to perform the NMS transactions on its end.
[0037] The sub-process 1) in one embodiment is based on a secure
Network File System (NFS), with the NMS server 7 providing NFS
server and the NEs 9 NFS client functionalities. This sub-process
further comprises the below two NMD file transfer routines that the
NEs repeat periodically, e.g. every 1, 5 or 10 seconds:
[0038] a) The NFS clients of the NEs 9 look for and copy 1 their
associated NMD program and control files, referred to as NE
configuration files, from directories at the NFS server 7
designated for configuration files intended for their respective
destination NEs, over a network 3 to the local memories at the NEs.
A NE looks for its new program and control files at their
respective, predefined directory locations designated to that NE at
the NMS server, and after copying such files from the NMS server,
stores its program files at a program memory segment, and its
control file at a control register segment within its local memory
space.
[0039] b) In addition, the NFS clients at the NEs 9 copy 2 contents
of their status register segments within their local memories via a
type of NMD file referred to as NE status file over a network 3 to
their associated directories at the NMS server 7 designated to
status files from the individual NEs managed through the NMS.
[0040] In one embodiment, the above routines of a) transferring NE
configuration files from the NMS server to NEs, and b) transferring
NE status files from NEs to the NMS server are independent
operations, i.e., neither one either triggers the other or is
caused by the other.
[0041] The sub-process 2) in one embodiment is performed by the NE
HW, e.g. per referenced application [5], automatically based on the
binary contents of the NE control files, normally without further
involvement by either NMS or NE SW. An exception to that is a case
when a NE control file contents contain such a value in a
particular NE control register, referred to as reboot control
register, that is intended to cause the NE SW to reboot, in which
case the NE SW will do a reboot of a type indicated by the reboot
control register value. Aside this reboot exception, i.e., in cases
when the reboot control register in a NE control file does not
indicate a reboot action, the NE hardware automatically, without SW
involvement, completes the network management actions indicated by
the contents of new NE control files copied 1 to the control
register segment in its local memory space. The NE also copies to
its program memory segment within its local memory space any new
program files from its associated directory at the NMS file server
designated for program files for that destination NE. In one
embodiment, the program memory segment of a NE comprises multiple
directories to allow storing multiple NE program files, and the
value of the NE reboot control register indicates both whether the
NE is to reboot, and using program files in which directory in the
program memory segment. In addition, the NE HW automatically
maintains and updates a set of NE status parameters in its status
register memory space, and the NE SW reads the contents of this
status register segment in the NE memory space to a NE status file
that the NE copies 2 to an appropriate directory at the NMS server
designated for status files from that source NE. In one embodiment,
the NE copies 2 also the contents of its control registers via its
NE status file back to the NMS server, allowing the user to verify
the actual values of also the NE control registers via GUI 4.
Hence, the phrase status NE status file herein shall include the
contents of both the NE control and status registers, collectively
referred to as NE device registers.
[0042] The sub-process 3) in one embodiment is performed by the NMS
GUI SW 4 via providing access in a human understood format for the
system user to the NMD files at the NE-specific directories at the
NMS file server 7. This sub-process involves write and read access
to control register values within the NE control files via the NMS
GUI, producing NE program files to appropriate folders at the file
server 7, and read access to the NE status files at the server 7.
Moreover, in one embodiment the NMS GUI 4 displays notifications of
significant events in the network such as NE alarm activations
according to principles per referenced applications [5] and
[6].
[0043] It is seen from the above discussion that the three main
sub-processes of the NMS process of the invention are mutually
de-coupled, other than through the contents of the NMD files that
indicate the intended actions to be performed by other elements of
the system to complete any given network management operation.
Compared against prior art messaging and command based NMS
techniques, this de-coupling between the functional elements of the
network management system and methods of the present invention
yields several benefits over the, including the below ones: [0044]
Heavy load of NMS or network event activity on one element of the
system per the invention does not negatively interfere with other
elements. For instance, while e.g. the NMS server 7 is heavily
loaded during for instance a network service contract testing
period when the NE control parameters are changed rapidly for test
case purposes, the file transfer routine, the SW of the NEs, and
even the HW of those NEs not under the test, are not at all
impacted. Likewise, a heavy load of e.g. network defect activity at
a given NE does not impact the NMD file transfer routines, the
other NEs, the NMS server or GUI SW; instead, in one embodiment,
e.g. per the referenced applications [5] and [6], just a single NE
alarm notification is generated at the NMS GUI when a previously
defect-free NE enters a defected state. As a consequence, the NMS
per the invention is highly reliable and scalable, providing a
predictable, steady performance under any load of NMS and network
event activities. [0045] The system per the invention is flexible
regarding any changes needed to the implementation of either the NE
9, NMS server 7, GUI 4 etc. elements of it, as well as any changes
to the network 3 through which the NMS and NEs transfer files, or
to the way the GUI and the NMS file server communicate 6.
Consequently, any of these system elements can change without
having to redesign the rest of the NMS system. [0046] The system
per the invention provides transparent NMS communications all the
way from the NMS GUI 4 to the NE 9 hardware device registers and
back, without intermediate messaging protocol conversion or command
translation agents etc. non-transparent middleware common with
prior art NMS communications techniques. Accordingly, the invention
inherently enables a more intuitive and flexible network
management, by allowing direct access to the NE parameters of
interest via an intuitive and transparent GUI, without requiring
the network operator's personnel to know about or deal with the
peculiarities of any intervening messaging protocol or command
language syntax.
[0047] A possible implementation of the NMS of the invention
further comprises a PC 5 hosting the NMS GUI application, e.g. HTML
based web browser 4. In such a system implementation, the GUI 4
connects to the NMS server 7 over a secure HTTP connection 6.
Regarding FIG. 1, it shall be understood that there is no implied
limit to the number of NEs supported by this network alarm
monitoring system, but that instead this system architecture
supports an arbitrary number of NEs 9, and that there can equally
well be multiple physical NMS server 7 and user computers 5 as well
as multiple concurrent NMS GUI applications 4.
[0048] FIG. 2 illustrates a logical directory structure according
to the invention at the NMS file server 7 for storing NMD files for
a set of NEs managed through the NMS. Below the file server
directory root 20, there is a directory structure 21 holding a set
of NE-specific directories 29(a) through 29(z) (later simply
directories 29 for the set, or a directory 29 when referring to any
one of the similarly structured directories 29(a), 29(b), 29(c)
etc.). Each of the directories 29 stores NMD files for its
associated NE 9, for example directory 29 (b) at the NMS server 7
stores NMD files associated with NE 9(b) (FIG. 1). In one
embodiment, each directory 29 comprises subdirectories 26, 27 and
28 for holding program, control and status files, respectively, of
the NE associated with the directory. These subdirectories have
been drawn in FIG. 2, as an example, for the case of directory
29(b) associated with NE 9(b) (FIG. 1). Each of the NE-specific
directories 29, however, have similar subdirectory structure as the
directory 29(b).
[0049] Operation of the NMS file server 7 in a process of
configuring and monitoring a given NE 9 in one embodiment is based
on the below principles:
[0050] 1) A system user, e.g., a network operator staff member,
produces desired types of NE program and control files for a NE 9,
using the NMS GUI client 4 and related server software at the NMS
files server 7, into the program file directory 26 and control file
directory 27 associated with the NE 9.
[0051] 2) The NE 9, via a repeating routine, for instance every
fifteen seconds, looks for and copies these files from its
associated directories 26 and 27 at its NMD directory 29 at the NMS
server to their appropriate locations within the local memory space
of the NE. The NE will consequently autonomously complete on its
end the NMS operations indicated via each new NE configuration
file.
[0052] 3) The NE 9, also via a repeating routine performed e.g.
once every second, copies the contents of its device status
registers via its NE status file to the folder 28 at its directory
29 at the NMS server 7. The NMS SW will consequently display NE
status data, along with a new NE alarm notification as necessary,
to the user via the GUI 4, based on the contents of the latest NE
status file at its associated directory 28 at the NMS server 7, in
one embodiment utilizing the network alarm monitoring principles
per the referenced applications [5] and [6].
[0053] The management process for a group of NEs, e.g. 9(a), 9(b)
and 9(c) in FIG. 1, is based on simply repeating, or executing in
parallel, the management process of a single NE described above.
Copying of files between directories at the NMS server 7 and the
NEs 9 in one embodiment is based on secure NFS, specifically NFS
version 4 in one embodiment. Also, in one embodiment, each NE
hardware unit 9 is identified by its unique NE ID number configured
at the factory on a non-volatile memory, e.g. flash drive, for each
NE unit 9, and the names of the NE-specific directories 29(a)
through 29(z) at the file server 7 include the NE ID of their
related NEs, based on which each NE 9 knows to access its
appropriate directory 29 at the NMS server 7.
[0054] It is observed that a need for identifiers for source,
destination, message or transaction is avoided with the present
invention for NMS communications between the NMS server 7 and the
NEs 9, in part via the use of NE-specific directories at the NMS
file server 7 for storing the NMD files associated with each one of
NEs 9(a) through 9(z) (FIG. 1). Note that transaction, source,
destination etc. identifiers are usually necessary with prior art
NMS communications schemes, per the prior art messaging protocols
(e.g. SNMP, CMIP, TL1 etc.), requiring related NMS messaging
protocol processing to be performed by prior art NMS and NE
devices, thus making the prior art network management systems
implementation, operation and administration more complicated and
less flexible compared to the plain binary NMD file transfer based
NMS communication of the present invention. Besides its more
straightforward and transparent implementation and more flexible
and intuitive operation, benefits of the invention enabled via the
NE-specific NMD file folders include elimination of NMS
communications overhead that is needed with prior art system for
their NMS messaging protocols, and the clarity and intuitiveness of
the NMS file server structure based on a repeated set of similar NE
specific directories 29(a) through 29(z) for the set of NMD files
26, 26 and 28 per each NE 9(a) through 9(z).
[0055] It shall be understood that the term directory herein refers
to a file folder i.e. directory at any level of the file system
hierarchy, and that e.g. phrase NE-specific directory can be used
to denote a hierarchical directory with sub-directories for holding
NMD files of a given NE, as well as a bottom level directory used
to hold a single NMD file of a particular type. Also, it shall be
understood that there can be any desired number of NE specific
directories 29 at the NMS server 7, that there can be any desirable
number of levels of file system hierarchy within directory
structures 21, 26, 27, 28 and 29, and that the directory structure
21, as well as the sub-structures of directories 29, can include
other directories and files in addition to the ones shown in FIG.
2.
[0056] FIG. 3 illustrates logical structure of local memory space
of each NE 9 of the network management system of the invention
(FIG. 1). The embedded memory space of the NE 9 comprises a program
memory segment 36, a control register segment 37 and a status
register segment 38. It shall be understood that various
embodiments of NEs 9 can have various other memory segments, e.g.,
RAM, in addition to the three segments shown in FIG. 3, and that
there can be as many layers of hierarchy of NE logical directory
structure 31 below its root 30 as desired in each embodiment, as
well as that the shown memory segments 36, 37 and 38 can have
sub-directories. Reference specifications for one embodiment of a
NE, including NE device register descriptions with related
application notes, are provided in the referenced application
[5].
[0057] In one embodiment, the NE memory space is organized as a
logical directory structure 31, with the NE program memory segment
36 forming a logical subdirectory at the NE for holding the NE
program files, and the NE control register segment 37 and the NE
status register segment 38 each forming binary files under the NE
logical directory structure 31. The NE 9 may comprise a HW unit
with an embedded microprocessor and a set of embedded memories
organized from the NE SW perspective as a continuous directory
structure. In one NE HW embodiment, the NE program memory directory
36 is a flash drive, and the NE control and status files are
predefined address ranges within the embedded memory space of the
NE microprocessor containing the NE device control and status
registers, respectively. Furthermore, in one embodiment, the NE
device registers are implemented within a digital logic device that
is configured, at least in part via the NE program files stored at
the directory 36. In such an embodiment, NE digital logic device
completes on the NE side the network management operations
indicated via each new NE control file 37, as well as produces and
keeps updated a predefined set of NE status parameters on the NE
status file 38. Such NEs capable of operating autonomously and
dynamically with this type of NMD files, including with a NE
program files 36 and control file 37 that are static for a duration
of a network service contract the NE is deployed for, in one
embodiment are based on principles of referenced applications [1],
[2], [3], [5] and [6].
[0058] A possible NE hardware implementation comprises, besides the
embedded microprocessor and its memories, a programmable logic
device (PLD, or FPGA i.e. Field Programmable Gate Array) within
which, in one embodiment, both the microprocessor as well as the
hardware logic, including the NE device registers, are included.
With the programmable NE hardware, the NE program files in the
flash drive 36 (as well as files in directory 26 in FIG. 2) shall
contain both a binary file for configuring the programmable
hardware logic of the NE (its PLD/FPGA), as well as a binary
executable program for the NE microprocessor. Various embodiments
of NEs for the invention can naturally contain any number of
microprocessors, logic devices as well as other hardware
components.
[0059] The NE SW in one embodiment executes periodically, e.g. once
every ten seconds, a repeating routine comprising the below
steps:
[0060] 1) The NFS client of the NE 9 looks for and copies to its
local memory segments 36 and 37 new NE program and control files,
respectively, at its associated directories 26 and 27 at the NFS
server of the NMS server computer 7;
[0061] 2) The NE HW automatically completes the NMS actions
indicated via new NE control files 37;
[0062] 3) The NE NFS client copies its status file 38 to its
associated directory 28 at the NFS server 7.
[0063] While the step 2) generally is performed by the NE HW, the
NE SW in one embodiment however checks the value of a particular
address in the control register segment referred to as the reboot
control register after it has copied a new NE control file 37 from
the NMS server. In case that the reboot control register was set to
a value indicating NE reboot action, the NE SW will perform a type
of NE reboot specified by the value of the reboot control register.
However, as a general rule, i.e., in cases that the reboot control
register was not set in an active value, the NE HW will complete
all the network management operations indicated by each new NE
control file 37 automatically without any SW involvement. Benefits
of this NE functional architecture per the invention include that
the NE SW does not need to process the NE control or status files
37 and 38 or perform related consecutive actions, other than
checking the reboot command register in the NE control files and
rebooting the NE as necessary. Consequently, the processing load
for the NE SW is significantly reduced while the entire system
operation is made faster, transparent and more predictable and
reliable via HW automation, and elimination of intermediary
processing stages with the NMS communications.
[0064] Regarding the NE memory space structure depicted in FIG. 3,
it shall be understood in various embodiments the NE control and
status register segments 37 and 38 may consist of sub-segments in
their respective address space ranges, that the device register
segments 37 and 38 are not required to contain actual data storage
elements for each of their bit and byte address locations, that any
one or even all of the NE configuration file memory segments 36, 37
and 38 can comprise multiple files or directories, and that any two
or more of these memory segments 36, 37 and 38 can logically be
combined into a single file or directory.
Conclusions
[0065] This detailed description is a specification of various
embodiments of the present invention. Specific architectural,
system, process and logic implementation examples are provided in
this and the referenced patent applications for the purpose of
illustrating various embodiments and implementations of the
invented concepts. Naturally, there are multiple alternative ways
to implement or utilize, in whole or in part, the principles of the
invention as set forth in the foregoing.
[0066] For instance, while the presentation of the network
management system functional architecture of the invention (an
overview of which is shown in FIG. 1) is reduced to illustrating
the organization its basic elements, it shall be understood that
various implementations of that architecture can have any number of
NEs served by an NMS server, any number of NMS servers, and any
number of NMS GUIs, etc. Also, in different embodiments of the
invention, the sequence of software and hardware logic processes
involved with the network management communications system can be
changed from the specific sequence described, and the process
phases of the network management methods could be combined with
others or further divided in to sub-steps, etc., without departing
from the principles of the present invention. For instance, in an
alternative embodiment, the NMS server could copy status files from
the NEs and copy configuration files to the NEs, instead of NEs
copying their status files to the NMS server and copying
configuration files from the NMS server. Moreover, the logical
functions that are described as implemented in hardware could in
alternative implementations be implemented in software, and vice
versa.
[0067] Generally, those skilled in the art will be able to develop
different versions and various modifications of the described
embodiments, which, although not necessarily each explicitly
described herein, utilize the concepts of the present invention and
are thus included within its spirit and scope. It is thus intended
that the specification and drawings of this patent application
considered not in a restrictive sense, but as exemplary only, with
the scope of the invention being indicated by the following
claims.
* * * * *