CA2148603A1 - A management agent system for the support of multiple network managers, and a method for operating such a system - Google Patents
A management agent system for the support of multiple network managers, and a method for operating such a systemInfo
- Publication number
- CA2148603A1 CA2148603A1 CA 2148603 CA2148603A CA2148603A1 CA 2148603 A1 CA2148603 A1 CA 2148603A1 CA 2148603 CA2148603 CA 2148603 CA 2148603 A CA2148603 A CA 2148603A CA 2148603 A1 CA2148603 A1 CA 2148603A1
- Authority
- CA
- Canada
- Prior art keywords
- communication device
- configuration
- management agent
- database
- manager
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims description 6
- 238000004891 communication Methods 0.000 claims abstract description 74
- 238000013507 mapping Methods 0.000 claims description 4
- 230000008520 organization Effects 0.000 claims description 2
- 238000000926 separation method Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 35
- 150000002500 ions Chemical class 0.000 description 7
- 238000010200 validation analysis Methods 0.000 description 5
- 230000006399 behavior Effects 0.000 description 3
- 238000013499 data model Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- NLZUEZXRPGMBCV-UHFFFAOYSA-N Butylhydroxytoluene Chemical compound CC1=CC(C(C)(C)C)=C(O)C(C(C)(C)C)=C1 NLZUEZXRPGMBCV-UHFFFAOYSA-N 0.000 description 1
- 241000905957 Channa melasoma Species 0.000 description 1
- 101150105088 Dele1 gene Proteins 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009118 appropriate response Effects 0.000 description 1
- 238000013506 data mapping Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
- H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/022—Multivendor or multi-standard integration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/024—Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Debugging And Monitoring (AREA)
Abstract
2148603 9508794 PCTABScor01 A communication system allows for the separation between the logical, external view of a network manager (10, 12) and the physical, internal view of the communication device (18, 20). A single management agent (108, 110) represents a single network manager (100, 102). The management agent (108, 110) is responsible for interpreting requests from that network manager (100, 102).
Description
' !,'~
~ ` VVO 9S/087g4 PCI`/US94/~8934 ~., `` -` 21~8603 .,, A MANAGE~AENT AGENT SYSTEM FC)P~ THE 5UPPORT OF MULTIPLE
NE~TWORK MANA~;ERS, A~JD A METHOD F~R OPER~TING 5UCH A
`' ~;YSTEM
-~ Field of the Invention This inYention relat~s generally to communications nehArorks, and sp~cifically to th~ nanagemen~ of a cornmunication network Back~round of the 3nvention .~ A c~mmunication ne~work consis~s of a number of users communicating throu~h various inter-connected 6 comrnunication devices. The Gommunioation d~vic~s could be terminals, host computers, multiplex~rs, frame handlers, etc.
I ~
jSuch a n~tNork may serve:a large number of us~rs. The : management of such a ne~work may be difficult and complex.
20 For example, if one user desir~s to transfer informati~n to another user in the ne~ork, the ne~work mus~ determine ~h~
most e~ficient path from one uscr to the other, det~rmine the typ~s of d~vices used to interface the ussr to the network, and configure the path so that the information will flow 2 5 ~fficiently betwesn the users.
' A comrnunica~ion device may have a number of Hviews~. A
view is a logieal grouping of one or (typically) more data itBmS
together to form a logical abstraction that repres~nts a higher 30 IBVel concept f~r that group:of parameters. For example, orle ~:vi~w of a "port" may be ~hat it is made up o~ 14 par~icular parameters (timers, lead valuès, etc). A different view of that same port may be that it is made up of 10 of thos~ paramet~rs plus 2 ~ifferent parameters. The view may change d~pending on the information n~eded to configur~ C)F monitor the port.
.
WO ~5/08794 PCT/VS94/08934 i ~,`,i X ~ 6~3 2 When th~ ability to manage rnultiple views is not a~ailable, then all network managers on a network must share the same Vi8W. If the multipl~ network manag~rs can not share the same view, then mul~iple versions of each ''!~ configuration m~na~er on the communications d~vice must be produced (one for each netAr~rk manager), or each rnanagem~nt , ag~nt in the comrnunicatiorls d~vice must maintain a cornplete und~rstanding of the system view of the communication .~ ~ o cevice. Either alternative adds to the amount of memory used by the device which adds to the cost andlor reduces the available throughplJt of the device. Bo~h alternatives also add ,~ significantly to the maint~nanee cost of ~he softwar~.
A system that solves the probiem of supporting multiple, diverse network managers by providing a means to transtate multiple management views into the noirmalized, tnternal view j of the communication d~vice would thus be valuable.
; . ' ` :
i ~ o Brief Description of the Drawings !
? FIG. 1 is a ciJstomer nehNork.
` 1 FIG. 2 is a management a~ent system for ~he 2~; network/commllnication device.
FIG. 3 is a block diagram of the mu3tiple views suppor~d within the communication device.
Fl~3. 4 is a flow chart showing the handling of a management r-quest by ~he management agent system.
.
."i'~ WO ~5/0879'1 PCTIUS94108934 6 ~ 3 .
.,,j ~j Description of the Preferred Embodiment ,,~
A system i5 shown ~hat allows for th~ separation betwesn the logical, ~xternal view of a network manager and the physical, int@rnal vi~w of the communication device. A
sin~le management agent repres~nts ~ single network manager and is responsible for interpreting requesl:s from that network ~;~ manager.
,~
A Third Normal Form (3NF) data model of the communication d~vice, embodied in base tables within a r~lational databas~, allow the communieation device managem~nt agent - on behalf of th~ ne~work rnanager - and communication device's configuration manager~ to map each other's spscific data to this normalized view of th~
communic~tion device.
~' This management ag~nt system is thus easily adaptable to a communication device's changing re~uir~ments and 20 complex data modeling environment, reducin0 the cost of building and main~aining the system.
FIG. 1 shows a n~twork consisting of multiple communication d~vices 14, t6, 18, 20 interconnQcted by public 25 or privat~ leased lines through th~ Public Switched Telephone NehNork (PSThl3 22. Commllnication devices 14, 16, 18, 20 rray be t~rminals, host c~rnpLIt~rs, multipl~xers, fram@
! ~ ~ . 'I hand~ers, ~ et~. Communication devif~e~ 14, 16, 18, 2Q
transport customer voic and data ~raffic through the network.
30 AKach~d to the comrnunicatio?l :devices at the edges of the custom~r n~twnrk is a proprietary network manager 10.
Proprietary network manager 10 configures and rnonitors the comrnwnication deYices 14, 16, 18, 20. The Simpt@ N~twork M~nagem~nt Protocol (SNMP) Managsr 12 is coup3ed with the 3~ network thr~ugh commLInication d~vice 16. Th~ SNMP Manag~r ~ r~
WO ~5/087~q PCTfUS94/08934 ~'. ! `~ 2 ~ I
,~ 4 ,~
is also used to configure and monitor communica~ion devices 14, 16, 18, ~0.
,~
FIG. 2 shows the elem nts of the managem~nt agent system. Proprietary n~twork manager 100 is connected to ! communication d~vice 104. SNMP Manager ~02 is also .~ connect~d to communication deviee 104.
Int~rnal to ~he communication d~Yice 104, a proprietary o management agent 108 provides agent functionality within communication dsvice 104: for propri~tary network manager lOû by using the protocol and s~man~ics that are native to network manager 100. Lik~wise, proprietary managem~nt ~'r' , agent 110 provides agent function~lity within communication 5 devic~ 104 for SNMP manager 102 by using the protocol and semantics that are nati~e to SNMP manager 102.
j, .~ The protocol and semantics native to each network manager are d~fined as a s~t of managed objects. A "managed 2 o obj~ct~ is a "view", as defined earlier, specifically defined by each network m~nager. A managed obJect Yil3W may b made s~p of data attributes, speratiQns and ~behavior (whi~h describes what the abs~ract "view~ such as a port will do under different conditions~. ;
~ ~s ~3 For example, proprietary nstwork manager 100 may send I ; an operation to communications device 104 to s~t the output .ead of a~particular port to a specific wltage level. The lead itself wouid be defined as a data at~ribute of th~ port managed 30 object. The behavior would be that when that attribu~e is ~et to a particular value, then the output lead is changed to a particular yoitage lev~l. The opsration, the attribut~ and the b~havior are all part of that man ged obj~ct "view". A
differ~nt "vi~w" of that same port from the SNMP manag~r may :
:
~f WO 951087g4 PCT/US94/08934 2 1 4 8 ~ 0 3 .`
require a different attribute and op~ration to achieve the sam~
result.
Managernent agents 1û8 and 110 also maintain limited 5 modsling knowled~e of comrnunication device 104, including knowledge of the database schema an~ how managed objects are configured together. Th da~abase schema is the set of logical relationships and organization applied ~o ghe data in th~ databa~e. The databas~ maintains a normalized (third o normal form - 3NF) representation of the configuratisn data for communica~ions device 10~. This is a "view" of ~he da~a which is commonly understood by all agents and configuration rnanagers that ref~rence the database.
Management agents 1 08, 11 0 translate the network manager rnanaged object "view" into the comrnunication d~vi~e normalized t'vi@w" in the database.
, A request by ne~ork manager 100, 102 can be broke~
il 2 o down into the following categorie-~:
~ Create Configuration--identifies a new instance of a managed object "view7'. Since there are many port~ on communication d~vice 104, each individuat port is identified ~y an individual instance. Greating a new : instarce makes it avai~able for configuration and monitoring .:
Delete Gonfiguration--removes an instance of a managed obje~t "view" for the list of instances availabi~ for configuration and monitorin~.
' Read Configura~ion--query partioular data at~ributes from a: particular instaMc~ of a managed object "YieW~
~ ~ 35 r WO 9~;108794 PCT/US94/OB934 2 ~ Q 3 6 o Modify Configuration--alters the value of a particular data attribute in a par~icu~ar instance of a managed object n~ ww ~ Perform an Action ~such as activate a call)--executes par~icuiar operations on an instanee of a managed object "Yiew" that can not o~herwise be performed by modifying the configuration.
Each managem~nt agent 108, 110 is also able to send m~s~ages to its respective n~tworh manager 100, 1~2 whenever significant events occur on communications det~ice 104.
Management agents 108, 110 interpr~t the requesg from its respective network manager 1 ûO, 102, by translating it in~o a da~abase read or write request. Configuration is validated at the managem~nt agent 108, 110, resources are validated and rsserved, and th~n all the data written to th~
~o database. Mana~ement agent 108, tlO th~n no~ifies th~
appropriat~ communication device configuration managers 114, 116. Communi~ation managers 114, 116 irnplement the request. Managernent agent 108,110 ~hen formuiates an appropriate response messag~ back to the respec~ive network 2 ~ manager 10~,102.
~ .
Valida~ion of a request by managemen~ agents 108, 110 ~re p~rformed within the context of the managed object. Ea~h manag~ment agent 108, ~10 p~rforms Yalidation of network 30 manager requ~sts to th0 extent that the reque-~t can be accepted into the database. This includes checking per parameter validation. such as checking data attribute boundri~es (within minimumlmaximum Yalues allow~d for ~he a~ribllte); intra-managed object r~lationships, svch as ~5 wh~ther: on~ attribute will work wi~h another attribute s2t to ::
.~ WO ~5/08794 PCTIU~;94/08934 ii -, 2 I ~ 3 ~ 7 a particular value; and in~er-managed object validation, which may be the same as inter-rnanaged object validation, but the attribu~es tha~ are compared may be in different mana~ed obj~ct views". The validation is concemed primarily with the 5 configuration definitioTl, and is performed within the cont~xt of th~ current nodal configuration. It do~s not account for the instan~iation of the configur~tion.
!~ .
Not only doe~ the manag~ment ag~n~ embody th network ~,, 10 management view, it aiso has a limited understanding of the '':, system view o~ communicati~n device 104. It must know when a request is dependent on the behavior of multiple ;~ configuration managers, ~nd how the reques~ must be coordinated b~twesn those configuration managers 114, 116.
Each management agent 108, 110 perForms th~ foilowing tasks:
Translation from network manager manag~d ` 2 o object "view" into communication device normalized h~tieYYU
, ~ ~ V~lidation of netw~rk manager requ~sts as it pcrtains to the managed obj~ct "views".
Physical resource validation & reservation (such 2~ as ports).
: , Storing con~iguration data in the database.
Sending notifications to ~he appropria~e 3 0 commvnication device configuration r~ianagers r~garding , changes to~the configuration daitabase.
.
, ` D Transtate and route managed objec~-spQcific actions to the appropri te communication device configuration ; : 3~ manager.
,, : :
~ .
WO 9!S/08794 PCTIUS94108934 f Translate and route event messages from the communication device corlfi~uration mana~rs ~o the network , ~ manager.
Database serYer 112 (DBS) stores configuration da~a in a relational form, and thefsby allows multiple views of data.
DBS may be cQmposed of a memory, such as random access memory and disk storage. DBS 112 can suppor~ having tW9 o databases open at one time.
The database of DBS 1t2 provides a unified, normaliz~d approach for managing configuration data, regardless of how the network manag~r-~ and configuration rnanagers "vi~w" the 5 data. The abstraction of communication devic~ 104 is captur~d in th~ databas~, where data can be ascess~d by specifying ~ppropriate crit~ria. Direct users of DBS 1t2 (~.9., management ag~nts or configuration managers) translate their private "vi~ws" into and out of the norm~lized tab!~s ~hat mak@ up the ~o database. Thes~ direct us~rs then us~ the databas~ to cr~at~, dele~&, query,: update, and search ~hese t~bles according to varying criteria. The datab~se contains all nodal configura~ion data~
: ~5 When notified of configuration changes to: the on-lin~
configuration, confi~uration managers 114, î 16, read those ~:: changes from E:)BS 112, :and initiate tlleir impiementation in th~ node. ~
: 3 0 Configuration managers 1 14, 1 16 impl~ment configLIration requests within communication devics ~ 04 along : ~unctional bol~ndaries. Con~igLIration managers ~114, 1~6 knDw: ~ abou~a~single, on-line database which: it uses ~o r~trieve ~ : configuration data. Configuration managers 11 4, 1~ 6 : ~ : : 3~ implement the r~quest by generatiny their own re~uests to the ~ ~: : : , : :
: ~ :
, WO 951087~4 PCT/US94tû8934 8~3 entity or entitiPg to be configured, stJch as port 11~ or call 120. Port 118 may ~e an EIA232 port connPcted to a host computer, or a T1 port connected to frame handler. Call 120 may be a connection through the communications network from one EIA232 port to another EIA232 port on another communicatiorls device.
Configura~ion manag~rs ~14, 116 r~ad the da~abase via C)BS 112 ~o obtain ~onfiguration updates and initialization o data. When updatss haYe been made, configuration managers 114, 116 r~ad the update so that it can instantiate the change.
Configuration managers 114, ~16 also read the database via DE~S 11 ? during node is initialization.
3 15 The o,~erations betwe@n 0ither management ag~n~ 108, 110 and either or both configuration managers 114, 116 is specifi~d as part of th~ configuration mana~er interface i I specification. There ar~ a generic set of operations that are ' available cn all eonfiguration managers 114, 116. Th~se operations are the same as, and follow the sarne definitions given earlier for Greate, Del~te and Modify.
FIG. 3 shows the support of multiple views by the database. C)ne of the functions of the relational database is to 2 ~ provid~ the ability for its multiple users (clients) to maintain separat~ and distin t vi~w of th~ data in the database. Th~
view of proprietary network manager 100 (FIG. 2) view is ; ~mbodi~d in a Propri~tary managsment~agent (200). Simitarly, the view of SNMP manager 102 (FIG. 2) is ~mbodied by SNMP
managemen~agent 202. A rela~ional database 204 contains base tables: defined in 3NF. Relational database 204 con~ains the implementation of: th~ data model of communication d~vice 1û4 (FIG. 2) and the implementation view of c~mmunication dgvice: 104 as ernbodied by configuration manag~rs 114, 116.
3~ :
~ ` VVO 9S/087g4 PCI`/US94/~8934 ~., `` -` 21~8603 .,, A MANAGE~AENT AGENT SYSTEM FC)P~ THE 5UPPORT OF MULTIPLE
NE~TWORK MANA~;ERS, A~JD A METHOD F~R OPER~TING 5UCH A
`' ~;YSTEM
-~ Field of the Invention This inYention relat~s generally to communications nehArorks, and sp~cifically to th~ nanagemen~ of a cornmunication network Back~round of the 3nvention .~ A c~mmunication ne~work consis~s of a number of users communicating throu~h various inter-connected 6 comrnunication devices. The Gommunioation d~vic~s could be terminals, host computers, multiplex~rs, frame handlers, etc.
I ~
jSuch a n~tNork may serve:a large number of us~rs. The : management of such a ne~work may be difficult and complex.
20 For example, if one user desir~s to transfer informati~n to another user in the ne~ork, the ne~work mus~ determine ~h~
most e~ficient path from one uscr to the other, det~rmine the typ~s of d~vices used to interface the ussr to the network, and configure the path so that the information will flow 2 5 ~fficiently betwesn the users.
' A comrnunica~ion device may have a number of Hviews~. A
view is a logieal grouping of one or (typically) more data itBmS
together to form a logical abstraction that repres~nts a higher 30 IBVel concept f~r that group:of parameters. For example, orle ~:vi~w of a "port" may be ~hat it is made up o~ 14 par~icular parameters (timers, lead valuès, etc). A different view of that same port may be that it is made up of 10 of thos~ paramet~rs plus 2 ~ifferent parameters. The view may change d~pending on the information n~eded to configur~ C)F monitor the port.
.
WO ~5/08794 PCT/VS94/08934 i ~,`,i X ~ 6~3 2 When th~ ability to manage rnultiple views is not a~ailable, then all network managers on a network must share the same Vi8W. If the multipl~ network manag~rs can not share the same view, then mul~iple versions of each ''!~ configuration m~na~er on the communications d~vice must be produced (one for each netAr~rk manager), or each rnanagem~nt , ag~nt in the comrnunicatiorls d~vice must maintain a cornplete und~rstanding of the system view of the communication .~ ~ o cevice. Either alternative adds to the amount of memory used by the device which adds to the cost andlor reduces the available throughplJt of the device. Bo~h alternatives also add ,~ significantly to the maint~nanee cost of ~he softwar~.
A system that solves the probiem of supporting multiple, diverse network managers by providing a means to transtate multiple management views into the noirmalized, tnternal view j of the communication d~vice would thus be valuable.
; . ' ` :
i ~ o Brief Description of the Drawings !
? FIG. 1 is a ciJstomer nehNork.
` 1 FIG. 2 is a management a~ent system for ~he 2~; network/commllnication device.
FIG. 3 is a block diagram of the mu3tiple views suppor~d within the communication device.
Fl~3. 4 is a flow chart showing the handling of a management r-quest by ~he management agent system.
.
."i'~ WO ~5/0879'1 PCTIUS94108934 6 ~ 3 .
.,,j ~j Description of the Preferred Embodiment ,,~
A system i5 shown ~hat allows for th~ separation betwesn the logical, ~xternal view of a network manager and the physical, int@rnal vi~w of the communication device. A
sin~le management agent repres~nts ~ single network manager and is responsible for interpreting requesl:s from that network ~;~ manager.
,~
A Third Normal Form (3NF) data model of the communication d~vice, embodied in base tables within a r~lational databas~, allow the communieation device managem~nt agent - on behalf of th~ ne~work rnanager - and communication device's configuration manager~ to map each other's spscific data to this normalized view of th~
communic~tion device.
~' This management ag~nt system is thus easily adaptable to a communication device's changing re~uir~ments and 20 complex data modeling environment, reducin0 the cost of building and main~aining the system.
FIG. 1 shows a n~twork consisting of multiple communication d~vices 14, t6, 18, 20 interconnQcted by public 25 or privat~ leased lines through th~ Public Switched Telephone NehNork (PSThl3 22. Commllnication devices 14, 16, 18, 20 rray be t~rminals, host c~rnpLIt~rs, multipl~xers, fram@
! ~ ~ . 'I hand~ers, ~ et~. Communication devif~e~ 14, 16, 18, 2Q
transport customer voic and data ~raffic through the network.
30 AKach~d to the comrnunicatio?l :devices at the edges of the custom~r n~twnrk is a proprietary network manager 10.
Proprietary network manager 10 configures and rnonitors the comrnwnication deYices 14, 16, 18, 20. The Simpt@ N~twork M~nagem~nt Protocol (SNMP) Managsr 12 is coup3ed with the 3~ network thr~ugh commLInication d~vice 16. Th~ SNMP Manag~r ~ r~
WO ~5/087~q PCTfUS94/08934 ~'. ! `~ 2 ~ I
,~ 4 ,~
is also used to configure and monitor communica~ion devices 14, 16, 18, ~0.
,~
FIG. 2 shows the elem nts of the managem~nt agent system. Proprietary n~twork manager 100 is connected to ! communication d~vice 104. SNMP Manager ~02 is also .~ connect~d to communication deviee 104.
Int~rnal to ~he communication d~Yice 104, a proprietary o management agent 108 provides agent functionality within communication dsvice 104: for propri~tary network manager lOû by using the protocol and s~man~ics that are native to network manager 100. Lik~wise, proprietary managem~nt ~'r' , agent 110 provides agent function~lity within communication 5 devic~ 104 for SNMP manager 102 by using the protocol and semantics that are nati~e to SNMP manager 102.
j, .~ The protocol and semantics native to each network manager are d~fined as a s~t of managed objects. A "managed 2 o obj~ct~ is a "view", as defined earlier, specifically defined by each network m~nager. A managed obJect Yil3W may b made s~p of data attributes, speratiQns and ~behavior (whi~h describes what the abs~ract "view~ such as a port will do under different conditions~. ;
~ ~s ~3 For example, proprietary nstwork manager 100 may send I ; an operation to communications device 104 to s~t the output .ead of a~particular port to a specific wltage level. The lead itself wouid be defined as a data at~ribute of th~ port managed 30 object. The behavior would be that when that attribu~e is ~et to a particular value, then the output lead is changed to a particular yoitage lev~l. The opsration, the attribut~ and the b~havior are all part of that man ged obj~ct "view". A
differ~nt "vi~w" of that same port from the SNMP manag~r may :
:
~f WO 951087g4 PCT/US94/08934 2 1 4 8 ~ 0 3 .`
require a different attribute and op~ration to achieve the sam~
result.
Managernent agents 1û8 and 110 also maintain limited 5 modsling knowled~e of comrnunication device 104, including knowledge of the database schema an~ how managed objects are configured together. Th da~abase schema is the set of logical relationships and organization applied ~o ghe data in th~ databa~e. The databas~ maintains a normalized (third o normal form - 3NF) representation of the configuratisn data for communica~ions device 10~. This is a "view" of ~he da~a which is commonly understood by all agents and configuration rnanagers that ref~rence the database.
Management agents 1 08, 11 0 translate the network manager rnanaged object "view" into the comrnunication d~vi~e normalized t'vi@w" in the database.
, A request by ne~ork manager 100, 102 can be broke~
il 2 o down into the following categorie-~:
~ Create Configuration--identifies a new instance of a managed object "view7'. Since there are many port~ on communication d~vice 104, each individuat port is identified ~y an individual instance. Greating a new : instarce makes it avai~able for configuration and monitoring .:
Delete Gonfiguration--removes an instance of a managed obje~t "view" for the list of instances availabi~ for configuration and monitorin~.
' Read Configura~ion--query partioular data at~ributes from a: particular instaMc~ of a managed object "YieW~
~ ~ 35 r WO 9~;108794 PCT/US94/OB934 2 ~ Q 3 6 o Modify Configuration--alters the value of a particular data attribute in a par~icu~ar instance of a managed object n~ ww ~ Perform an Action ~such as activate a call)--executes par~icuiar operations on an instanee of a managed object "Yiew" that can not o~herwise be performed by modifying the configuration.
Each managem~nt agent 108, 110 is also able to send m~s~ages to its respective n~tworh manager 100, 1~2 whenever significant events occur on communications det~ice 104.
Management agents 108, 110 interpr~t the requesg from its respective network manager 1 ûO, 102, by translating it in~o a da~abase read or write request. Configuration is validated at the managem~nt agent 108, 110, resources are validated and rsserved, and th~n all the data written to th~
~o database. Mana~ement agent 108, tlO th~n no~ifies th~
appropriat~ communication device configuration managers 114, 116. Communi~ation managers 114, 116 irnplement the request. Managernent agent 108,110 ~hen formuiates an appropriate response messag~ back to the respec~ive network 2 ~ manager 10~,102.
~ .
Valida~ion of a request by managemen~ agents 108, 110 ~re p~rformed within the context of the managed object. Ea~h manag~ment agent 108, ~10 p~rforms Yalidation of network 30 manager requ~sts to th0 extent that the reque-~t can be accepted into the database. This includes checking per parameter validation. such as checking data attribute boundri~es (within minimumlmaximum Yalues allow~d for ~he a~ribllte); intra-managed object r~lationships, svch as ~5 wh~ther: on~ attribute will work wi~h another attribute s2t to ::
.~ WO ~5/08794 PCTIU~;94/08934 ii -, 2 I ~ 3 ~ 7 a particular value; and in~er-managed object validation, which may be the same as inter-rnanaged object validation, but the attribu~es tha~ are compared may be in different mana~ed obj~ct views". The validation is concemed primarily with the 5 configuration definitioTl, and is performed within the cont~xt of th~ current nodal configuration. It do~s not account for the instan~iation of the configur~tion.
!~ .
Not only doe~ the manag~ment ag~n~ embody th network ~,, 10 management view, it aiso has a limited understanding of the '':, system view o~ communicati~n device 104. It must know when a request is dependent on the behavior of multiple ;~ configuration managers, ~nd how the reques~ must be coordinated b~twesn those configuration managers 114, 116.
Each management agent 108, 110 perForms th~ foilowing tasks:
Translation from network manager manag~d ` 2 o object "view" into communication device normalized h~tieYYU
, ~ ~ V~lidation of netw~rk manager requ~sts as it pcrtains to the managed obj~ct "views".
Physical resource validation & reservation (such 2~ as ports).
: , Storing con~iguration data in the database.
Sending notifications to ~he appropria~e 3 0 commvnication device configuration r~ianagers r~garding , changes to~the configuration daitabase.
.
, ` D Transtate and route managed objec~-spQcific actions to the appropri te communication device configuration ; : 3~ manager.
,, : :
~ .
WO 9!S/08794 PCTIUS94108934 f Translate and route event messages from the communication device corlfi~uration mana~rs ~o the network , ~ manager.
Database serYer 112 (DBS) stores configuration da~a in a relational form, and thefsby allows multiple views of data.
DBS may be cQmposed of a memory, such as random access memory and disk storage. DBS 112 can suppor~ having tW9 o databases open at one time.
The database of DBS 1t2 provides a unified, normaliz~d approach for managing configuration data, regardless of how the network manag~r-~ and configuration rnanagers "vi~w" the 5 data. The abstraction of communication devic~ 104 is captur~d in th~ databas~, where data can be ascess~d by specifying ~ppropriate crit~ria. Direct users of DBS 1t2 (~.9., management ag~nts or configuration managers) translate their private "vi~ws" into and out of the norm~lized tab!~s ~hat mak@ up the ~o database. Thes~ direct us~rs then us~ the databas~ to cr~at~, dele~&, query,: update, and search ~hese t~bles according to varying criteria. The datab~se contains all nodal configura~ion data~
: ~5 When notified of configuration changes to: the on-lin~
configuration, confi~uration managers 114, î 16, read those ~:: changes from E:)BS 112, :and initiate tlleir impiementation in th~ node. ~
: 3 0 Configuration managers 1 14, 1 16 impl~ment configLIration requests within communication devics ~ 04 along : ~unctional bol~ndaries. Con~igLIration managers ~114, 1~6 knDw: ~ abou~a~single, on-line database which: it uses ~o r~trieve ~ : configuration data. Configuration managers 11 4, 1~ 6 : ~ : : 3~ implement the r~quest by generatiny their own re~uests to the ~ ~: : : , : :
: ~ :
, WO 951087~4 PCT/US94tû8934 8~3 entity or entitiPg to be configured, stJch as port 11~ or call 120. Port 118 may ~e an EIA232 port connPcted to a host computer, or a T1 port connected to frame handler. Call 120 may be a connection through the communications network from one EIA232 port to another EIA232 port on another communicatiorls device.
Configura~ion manag~rs ~14, 116 r~ad the da~abase via C)BS 112 ~o obtain ~onfiguration updates and initialization o data. When updatss haYe been made, configuration managers 114, 116 r~ad the update so that it can instantiate the change.
Configuration managers 114, ~16 also read the database via DE~S 11 ? during node is initialization.
3 15 The o,~erations betwe@n 0ither management ag~n~ 108, 110 and either or both configuration managers 114, 116 is specifi~d as part of th~ configuration mana~er interface i I specification. There ar~ a generic set of operations that are ' available cn all eonfiguration managers 114, 116. Th~se operations are the same as, and follow the sarne definitions given earlier for Greate, Del~te and Modify.
FIG. 3 shows the support of multiple views by the database. C)ne of the functions of the relational database is to 2 ~ provid~ the ability for its multiple users (clients) to maintain separat~ and distin t vi~w of th~ data in the database. Th~
view of proprietary network manager 100 (FIG. 2) view is ; ~mbodi~d in a Propri~tary managsment~agent (200). Simitarly, the view of SNMP manager 102 (FIG. 2) is ~mbodied by SNMP
managemen~agent 202. A rela~ional database 204 contains base tables: defined in 3NF. Relational database 204 con~ains the implementation of: th~ data model of communication d~vice 1û4 (FIG. 2) and the implementation view of c~mmunication dgvice: 104 as ernbodied by configuration manag~rs 114, 116.
3~ :
4 PCT/US94/08g34 2 ~ ~ a Database 204 allows support of multiple versions of I configurati~n data: on-line (or active~, off-~ine (or alternate), ~tc. Fo, example, I'off-line~ configuration data can be specifi~d, validated, and stored in da~abase 204 without r~quiring communicatioT~ device 104 to implement such configuration. Communication device 104 can be subsequently rebocted to use this offline database. Only one con~iguration is "on-line~ or active at any particular time.
o FK3. 4 is a flow chart for the handling of management requests by the management ag@n~ sys~em shown in FlGs. 2 and 3. Proprietary network mana~er 100 sends a management request to oomrnunication device 104 to ~onfigure a new port 118 (Step 302). The management request is r~ceiv~d by c~mmunication device 104 and routed to the apprspriate manag~ment aQent, in this case proprietary management ag@nt 108 (Step 304). The management agent 108 validat~s the port configuration request for syr6tactic and semantic c~rrectness (Step 306). If th~ request is: not valid (Step 308), the management agent 10~ returns an err~r response to the ! network mana9er 100 (Step 310). If: the mana~ment request is valid, the management agent 10~ maps the network manager-organized configuration data for the port into th~ 3NF
norrnalized form. (Step 312). Management agent 108 updates th~ bas~ tables containing por~ configuration using the database server 112 (Step 314). After the database is updated, management ag~nt 108 notifies configuration manag~r 114 ~hat there îs a new port con~iguration data~in the database (Step; 316j. Configuration managér 114 reads the new port configuration data in 3NF ~orm using the s~rvices of the database server 112 (Step~31~ Configuration manager 114 maps the data from 3NF form into the communieation devic@
114 spe~ific form requir~d tD implement the portts configwration (Step 320). The eonfiguration rnanag~r 11 4 implements the port configuration by ~alking to the port 118 .
, .
W~ 95/08794 lPCT/lJS94/08934 2 ~ q ~ fi Q ~ !
and providing it the configuration data (S~ep 322). The configuration manager 114 responds to the management agen~
108 that the port has been configured (Step 324). The management agen~ 108 sends a management response back to 5 the network manag~r 100 indicating the management request was successfully complete~ (Step 326). Finally, the network manager tO0 receives the management r~sponse from the manag~m~nt agent 108 ~S~p 328).
0 Conclusion This combination of the following 21ements relational network managers 100l 102, management agents 108, 100 and databas~ 204 storing information in (3NF) isolates the 1~ ex~ernal managem~nt Vi@W from the internai physical view by the us~ of data mapping is n~w. This scheme allows for the easy addition of new "views" (e.g. management agents), which are independent from ~xisting viewsl and therefDre have no impact to th~ existing views.
E3ecause each view of communication device 104 has its own model for looking at its data, these views ~external models) are mapped onto a "normalized" data model which is in 3NF form. The intern~l views (e.g., configuraticn: rnanag~r-~
114, 116) also map to ~he da~abase #nf view. This allows for muttiple interpretations of the management model by different portions of th~ communieation device.
Since external modsling of a communication devic~ c n often be orthogonal to the actual internal impl~mentation, a means to redu~e the complexity of this mapping is ess~ntial.
Doing ~his mapping using data (via a databass) inst~ad of code is the means offered in this invention.
Wo 95/08794 PCT/US94/08934 ` 23!~.8~o3 ' i ~ -~
Thus, the described system supports ~he capability to provide multiple vi~ws easi~y. This management agent system is easily adaptable to a communication device's changin~
requirements and complex data modeling ~nvironment. Further, the complexity of mapping between network manager and the comrnunication devic~ is reduc3d.
The system also avoids imposing the network managemen~/user vi~w on ~he int~rnal communication device, . 1 0 and avoids imposing internal implementa~ions within the communication device on the network management/user view.
, This avoids haYing changes in one view af~ec~ ~he other view, resulting in greater efficiency and adaptability.
~he network manager/user view is hidden from in~ernal 1 implementations,: altowing: either to chanye as required:by the '. netwark. Further, the addition ~f mui~ip~e network managers ~: ~ may ~e easily accomplished by adding :new management agents.
; : :
All of these advantages~add up to r~duced development : and maintenan~e costs for communications device 104, as well : ` ~ : : as reduced random access memory utilization in :the device, ~ thereby reducing its eost ~to manu~acture.
,: : :
~: : ~
, ~ .
,
o FK3. 4 is a flow chart for the handling of management requests by the management ag@n~ sys~em shown in FlGs. 2 and 3. Proprietary network mana~er 100 sends a management request to oomrnunication device 104 to ~onfigure a new port 118 (Step 302). The management request is r~ceiv~d by c~mmunication device 104 and routed to the apprspriate manag~ment aQent, in this case proprietary management ag@nt 108 (Step 304). The management agent 108 validat~s the port configuration request for syr6tactic and semantic c~rrectness (Step 306). If th~ request is: not valid (Step 308), the management agent 10~ returns an err~r response to the ! network mana9er 100 (Step 310). If: the mana~ment request is valid, the management agent 10~ maps the network manager-organized configuration data for the port into th~ 3NF
norrnalized form. (Step 312). Management agent 108 updates th~ bas~ tables containing por~ configuration using the database server 112 (Step 314). After the database is updated, management ag~nt 108 notifies configuration manag~r 114 ~hat there îs a new port con~iguration data~in the database (Step; 316j. Configuration managér 114 reads the new port configuration data in 3NF ~orm using the s~rvices of the database server 112 (Step~31~ Configuration manager 114 maps the data from 3NF form into the communieation devic@
114 spe~ific form requir~d tD implement the portts configwration (Step 320). The eonfiguration rnanag~r 11 4 implements the port configuration by ~alking to the port 118 .
, .
W~ 95/08794 lPCT/lJS94/08934 2 ~ q ~ fi Q ~ !
and providing it the configuration data (S~ep 322). The configuration manager 114 responds to the management agen~
108 that the port has been configured (Step 324). The management agen~ 108 sends a management response back to 5 the network manag~r 100 indicating the management request was successfully complete~ (Step 326). Finally, the network manager tO0 receives the management r~sponse from the manag~m~nt agent 108 ~S~p 328).
0 Conclusion This combination of the following 21ements relational network managers 100l 102, management agents 108, 100 and databas~ 204 storing information in (3NF) isolates the 1~ ex~ernal managem~nt Vi@W from the internai physical view by the us~ of data mapping is n~w. This scheme allows for the easy addition of new "views" (e.g. management agents), which are independent from ~xisting viewsl and therefDre have no impact to th~ existing views.
E3ecause each view of communication device 104 has its own model for looking at its data, these views ~external models) are mapped onto a "normalized" data model which is in 3NF form. The intern~l views (e.g., configuraticn: rnanag~r-~
114, 116) also map to ~he da~abase #nf view. This allows for muttiple interpretations of the management model by different portions of th~ communieation device.
Since external modsling of a communication devic~ c n often be orthogonal to the actual internal impl~mentation, a means to redu~e the complexity of this mapping is ess~ntial.
Doing ~his mapping using data (via a databass) inst~ad of code is the means offered in this invention.
Wo 95/08794 PCT/US94/08934 ` 23!~.8~o3 ' i ~ -~
Thus, the described system supports ~he capability to provide multiple vi~ws easi~y. This management agent system is easily adaptable to a communication device's changin~
requirements and complex data modeling ~nvironment. Further, the complexity of mapping between network manager and the comrnunication devic~ is reduc3d.
The system also avoids imposing the network managemen~/user vi~w on ~he int~rnal communication device, . 1 0 and avoids imposing internal implementa~ions within the communication device on the network management/user view.
, This avoids haYing changes in one view af~ec~ ~he other view, resulting in greater efficiency and adaptability.
~he network manager/user view is hidden from in~ernal 1 implementations,: altowing: either to chanye as required:by the '. netwark. Further, the addition ~f mui~ip~e network managers ~: ~ may ~e easily accomplished by adding :new management agents.
; : :
All of these advantages~add up to r~duced development : and maintenan~e costs for communications device 104, as well : ` ~ : : as reduced random access memory utilization in :the device, ~ thereby reducing its eost ~to manu~acture.
,: : :
~: : ~
, ~ .
,
Claims (10)
1. A management agent system for a communication device comprising:
a network manager for configuring the communication device, the network manager having configuration information for configuring the communication device;
a communication device management agent, coupled to the network manager, where the communication device management agent handles management requests on behalf of the network manager;
a communication device database, coupled to the communication device management agent, where the communication device management agent stores configuration information for the communication device;
a communication device configuration manager; coupled to the communication device database and the communication device, the communication device configuration manager reading the configuration information from the communication device:
database, and then configuring the communication device.
a network manager for configuring the communication device, the network manager having configuration information for configuring the communication device;
a communication device management agent, coupled to the network manager, where the communication device management agent handles management requests on behalf of the network manager;
a communication device database, coupled to the communication device management agent, where the communication device management agent stores configuration information for the communication device;
a communication device configuration manager; coupled to the communication device database and the communication device, the communication device configuration manager reading the configuration information from the communication device:
database, and then configuring the communication device.
2. The management agent system of claim 1 where there are a plurality of network managers.
3. The management agent system of claim 2 where the communication device management agent maps the communication device information into the communication device database.
4. The management agent system of claim 3 where the mapping of the communication device information into the communication device database converts the communication device information into a third normal form.
5. The management agent system of claim 4 where at least two of the network managers have different organizational views of the communication device information.
6. The management agent system of claim 5 where the communication device configuration manager converts the communication device information stored in the communication device database from third normal form into information for configuring the communication device.
7. A method of configuring a communication device comprising the steps of:
storing configuration information about a communication device in a communication device database;
reading the configuration information from the communication device database;
configuring the communication device from the configuration information.
storing configuration information about a communication device in a communication device database;
reading the configuration information from the communication device database;
configuring the communication device from the configuration information.
8. The method of claim 7 where the step of storing configuration information includes the step of converting the configuration information into third normal form and the step of reading the configuration information from the communication device database includes converting the configuration from third normal form into a configuration information organization recognizable by the communication device.
9. The method of claim 8 where the step of configuring the communication device includes sending a command to the communication device instructing the communication device to begin configuration.
10. The method of claim 9 where the step of configuring the communication device includes the step of updating one of more of the versions of the configuration data in the communication device database.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US12365793A | 1993-09-20 | 1993-09-20 | |
| US08/123,657 | 1993-09-20 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2148603A1 true CA2148603A1 (en) | 1995-03-30 |
Family
ID=22410038
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA 2148603 Abandoned CA2148603A1 (en) | 1993-09-20 | 1994-08-08 | A management agent system for the support of multiple network managers, and a method for operating such a system |
Country Status (4)
| Country | Link |
|---|---|
| EP (1) | EP0670060A4 (en) |
| AU (1) | AU7558094A (en) |
| CA (1) | CA2148603A1 (en) |
| WO (1) | WO1995008794A1 (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5758083A (en) * | 1995-10-30 | 1998-05-26 | Sun Microsystems, Inc. | Method and system for sharing information between network managers |
| US6131112A (en) * | 1996-05-17 | 2000-10-10 | Cabletron Systems, Inc. | Method and apparatus for integrated network and systems management |
| GB9725855D0 (en) | 1997-12-04 | 1998-02-04 | 3Com Ireland | Network management communication |
| US6195689B1 (en) * | 1999-05-05 | 2001-02-27 | Mediaone Group, Inc. | Headend provisioning agent |
| US7730172B1 (en) | 1999-05-24 | 2010-06-01 | Computer Associates Think, Inc. | Method and apparatus for reactive and deliberative service level management (SLM) |
| US6292099B1 (en) | 1999-09-20 | 2001-09-18 | Telefonaktiebolaget L M Ericsson (Publ) | Event management system utilizing dynamic adaptation for external devices |
| US20020029207A1 (en) | 2000-02-28 | 2002-03-07 | Hyperroll, Inc. | Data aggregation server for managing a multi-dimensional database and database management system having data aggregation server integrated therein |
| US7249170B2 (en) * | 2000-12-06 | 2007-07-24 | Intelliden | System and method for configuration, management and monitoring of network resources |
| JP5743724B2 (en) | 2011-02-15 | 2015-07-01 | キヤノン株式会社 | Management apparatus and management method, management system and network device |
| US10318702B2 (en) | 2016-01-19 | 2019-06-11 | Ford Motor Company | Multi-valued decision diagram reversible restriction |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4622633A (en) * | 1983-12-06 | 1986-11-11 | Tri Sigma Corporation | Object building method for self configuring computer network |
| US5165018A (en) * | 1987-01-05 | 1992-11-17 | Motorola, Inc. | Self-configuration of nodes in a distributed message-based operating system |
| US5175800A (en) * | 1987-03-23 | 1992-12-29 | Case Group Plc | Expert and data base system and method for communications network |
| EP0329779B1 (en) * | 1987-09-04 | 1992-12-09 | Digital Equipment Corporation | Session control in network for digital data processing system which supports multiple transfer protocols |
| US5023873A (en) * | 1989-06-15 | 1991-06-11 | International Business Machines Corporation | Method and apparatus for communication link management |
-
1994
- 1994-08-08 WO PCT/US1994/008934 patent/WO1995008794A1/en not_active Application Discontinuation
- 1994-08-08 AU AU75580/94A patent/AU7558094A/en not_active Abandoned
- 1994-08-08 EP EP94925777A patent/EP0670060A4/en not_active Withdrawn
- 1994-08-08 CA CA 2148603 patent/CA2148603A1/en not_active Abandoned
Also Published As
| Publication number | Publication date |
|---|---|
| AU7558094A (en) | 1995-04-10 |
| EP0670060A1 (en) | 1995-09-06 |
| EP0670060A4 (en) | 1996-10-30 |
| WO1995008794A1 (en) | 1995-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5726979A (en) | Network management system | |
| US6047320A (en) | Network managing method and system | |
| US6181776B1 (en) | Network management of automatic call distributor resources | |
| EP1715619B1 (en) | Generating MIBs from WMI classes | |
| CA2148603A1 (en) | A management agent system for the support of multiple network managers, and a method for operating such a system | |
| AU2003237737B2 (en) | Management system and method for service subscription provisioning | |
| JPH07504543A (en) | network management system | |
| CA2535440C (en) | System architecture method and computer program product for managing telecommunication networks | |
| US6735626B1 (en) | Network managing method and system | |
| AU678701B2 (en) | A data storage device | |
| Cheah et al. | Design and implementation of an MMS environment on ISODE | |
| Fossa et al. | Implementing interactive configuration management for distributed systems | |
| Panti et al. | A FIPA compliant agent platform for federated information systems. | |
| Koerner | Design of a proxy for managing CMIP agents via SNMP | |
| Knizak et al. | Modular agent design for field bus management | |
| Park et al. | The integration of OSI network management and TCP/IP Internet management using SNMP | |
| US7447767B2 (en) | System for use in a communications network management system for automatic management of network plant | |
| Lee | A managed object view interface mechanism for distributed network management systems | |
| Chan et al. | Web-based distributed object simulation framework | |
| García et al. | Self-configuration of grid nodes using a policy-based management architecture | |
| KR100513864B1 (en) | CO-LAN Information Management Method based on Directory | |
| Wessels et al. | Applying distributed object technology to network planning | |
| Wimmers et al. | A Component framework for the configuration management of networks | |
| Helmy et al. | Impact of representation approach on modeling TMN interfaces | |
| Lee et al. | One service management architecture for distributed systems using DCE |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Dead |