GB2359691A - Distributed network monitoring with static/dynamic data discrimination - Google Patents
Distributed network monitoring with static/dynamic data discrimination Download PDFInfo
- Publication number
- GB2359691A GB2359691A GB0004284A GB0004284A GB2359691A GB 2359691 A GB2359691 A GB 2359691A GB 0004284 A GB0004284 A GB 0004284A GB 0004284 A GB0004284 A GB 0004284A GB 2359691 A GB2359691 A GB 2359691A
- Authority
- GB
- United Kingdom
- Prior art keywords
- data
- static
- static data
- controller
- communication system
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
-
- 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/052—Network management architectures or arrangements using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Communication Control (AREA)
Abstract
Method and communication system for exchanging data over a network between a plurality of network elements and a network control manager, the communication system including a communication processor unit, connected to the network control manager via a high-speed communication channel, and a plurality of monitor units, connected to the communication processor unit, wherein at least one of the network elements is connected to a selected one of the monitor units, thereby defining an interconnected pair, monitor units are connected to the communication processor unit via a low speed communication channel.
Description
2359691 TELECOMMUNICATION NETWORK MANAGEMENT
FIELD OF THE INVENTION
The present invention relates to network management in general, and to methods and systems for network management over lowspeed communication channels, in particular.
BACKGROUND OF THE INVENTION
Network management is becoming more and more important lo due to a very fast rate of growth of communication networks all over the world. The network management allows the monitoring of the status of a network and its operation to be controlled. A simple control system for a communication network consists of a Network Control Manager (NCM) unit and a plurality of Network Elements (NE) units. The NCM unit uses dedicated software to manage all the NE units connected to it by communication lines. The software installed at NCM unit allows communication with each of NE units, to receive all necessary information about their elements, characteristics, operation mode and the like, and to control their work.
In a Telecommunication Management Network (TMN) there exist guidelines and standards (e.g.]SO/IEC 10165-4), which determine specified communication protocols for use between the NCM unit and the NE units. The use of these standard protocols enables any NE, made by any vendor, to communicate to any of the NCM units. The protocols also dictate the format of the data reported from the NE units to the NCM unit. This format includes all the characteristics of the NE units: names, model numbers, real names (in English) of alarms, serial numbers and the like. These characteristics are considered Static Data. The NE also report to NCM unit Run-Time Data, which can include all real-time data, as power status (ON or OFF), measurement results and the like.
When a network starts to operate, the NCM unit communicates with each of the NE units and requests a predetermined "self discovery" information. Each of the NE units transmits to the NCM unit the respective Static and Run-Time Data. NCM unit builds its database according to this information and provides it to an operator. The foregoing operations are accomplished when a new NE unit is connected to the network. The new NE unit transmits its Static and Run-Time Data to the NCM unit, and NCM unit adds this information to its database.
After completing a "self discovery" phase of operation, the NE units continue to transmit to the NCM unit both Static and Run-Time Data, even if only Run-Time Data has been changed. Typically, communication lines between the NCM unit and the NE units are low-speed lines. Thus, transmission of the Static Data, when it is not required, is a useless waste of communication time. It would be advantageous to provide a method and system, which will allow to save the communication time, thereby increasing the speed of data transfer.
SUMMARY OF THE PRESENT INVENTION
In accordance with the present invention, there is thus provided a communication system for exchanging data over a network between a plurality of network elements and a network control manager. The communication system includes a communication processor unit, connected to the network control manager via a high-speed communication channel, and a plurality of monitor units, connected to the communication processor unit. At least one of the network elements is connected to a selected one of the monitor units, thereby defining an 10 interconnected pair.
In accordance with another aspect of the present inventioTI, there is provided a method for exchanging data over a network, between a plurality of network elements and a network control manager, via a mediating communication system. The mediating communication system is internally connected via a low-speed communication channel. The network elements are connected to a front-end of the mediating communication system and the network control manager is connected to a far-end of the mediating communication system. The method includes the steps of:
receiving data at the front-end of the mediating communication system from at least one of the network elements, the received data including static data and run-time data; storing static data and run-time data in the front-end storage unit of the mediating communication system; detecting changes in data or a request for data transmission; detecting the status of stored static data, thereby producing a first detection result therefrom; and transmitting run-time data to the far-end of the mediating communication system via the low-speed communication channel, when the first detection result indicates that the last version of static data was already transmitted to the far-end via the low-speed communication channel.
-5 BRIEF DESCRIPTION OF THE DRAWINGS
The present invention will be understood and appreciated more fully from the following detailed description taken in conjunction with the drawings in which:
Figure 1 is a schematic illustration of a network control system, constructed and operative in accordance with a preferred embodiment of the present invention, Figure 2 is a schematic illustration in detail of a monitor unit of the network control system of Figure 1, constructed and operative in 10 accordance with a further preferred embodiment of the present invention, Figure 3 is a schematic illustration in detail of a communication processor unit of the network control system of Figure 1, constructed and operative in accordance with a further preferred embodiment of the present invention, Figure 4 is a schematic illustration of a method for operating the monitor unit of Figure 2, operative in accordance with a further preferred embodiment of the present invention, and Figure 5 is a schematic illustration of a method for operating the communication processor unit of Figure 3, operative in accordance with a 20 further preferred embodiment of the present invention.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
With reference to figure 1 a network control system 10 includes a network control manager (NCM) unit 12, a communication processor unit 14, a plurality of monitor units 161, 162 to 16N, and a plurality of network elements (NE) 181, 182 and 18m. Communication processor unit 14 is connected to NCM unit 12 and to monitor units 161, 162,...16N. Each of monitor units 161, 162 and 16N is connected to at least one of dedicated network elements 181, 182and 18m. It is noted, that a network element can be any remotely controlled device, such as TV or radio re-translation lo station, electrical power relay station, alarmlsecurity units, monitoring devices and the like.
Each of network elements 181, 182 and 18m transmits its status data to a corresponding monitor unit. The status data of network elements 181, 182and 18m includes two types of data: static data and run-time data. Static data can include a network element name, serial and part numbers, description of every status and telemetry points, nominal values of their parameters and the like. In general, static data is the information that is not supposed to be changed, unless the network element itself is replaced, repaired, restarted or the like. Run-time data includes the actual values of the network element parameters, measurement results, alarm conditions, network elernent status (e.g., ON or OFF) and the like. It is noted that a monitor unit, connected to a specific network element, can be adapted to communicate with that network element using the specific communication protocol of that network element.
Each of monitor units 161, 162 and 16N receives static and runtime data from the associated network element and checks the data for correspondence to predetermined criteria. Each of monitor units 161, 162 and 16N, depending on the result of the checking process, either transmits both run-time and static data to communication processor unit 14, or transmits only run-time data. It is noted that, typically, a data communication channel between the monitor units 161, 162 and 16N and lo communication processor unit 14 is a low-speed channel. It can be, for example, a telephone line incorporating modems with a speed between 1200 bps and 9600 bps, a narrow RF channel and the like. Thus, transmission of only the run-time data can significantly reduce communication time. Any appropriate protocol for low-speed data communication can be used for data transmission, as for example, Motorola Data Link Communication (MDLC) protocol. The detailed disclosure of the forgoing criteria will be presented herein below.
Communication processor unit 14 receives data from each of monitor units 161, 162 and 16N and performs its analysis. If both the static and run-time data was received, then communication processor unit 14 transmits this data further, to NCM unit 12. In case only run-time data was received, communication processor unit 14 checks if static data related to received run-time data is present in its storage Unit (not shown). If static data is present and there is no indication that it was changed, then communication processor unit 14 combines it with run-time data and transmits both to NCM unit 12.
If static data is missing or requires an update, then communication processor unit 14 requests new or updated static data from the respective monitor unit. The communication processor unit 14 stores the received static data in its storage unit thereof (not shown) and transmits the static and the associated run-time data to NCM unit 12.
It is noted, that a communication channel between communication processor unit 14 and NCM unit 12 is a high-speed channel. Typically, Local Area Networks (LAN) or Wide Area Networks (WAN) channels are used. Any appropriate protocol for data communication can be utilized, as, for example, Telecommunication Management Network (TNM) protocol, TCP/IP and the like.
Reference is now made to Figure 2, which is a schematic illustration in detail of monitor unit 161 (Figure 1), constructed and operative in accordance with a further preferred embodiment of the present invention. Monitor unit 161 includes communication interface 40, controller 42, low-speed communication interface 44 and storage unit 46.
Controller 42 is connected to communication interface 40, to storage unit 46 and to low-speed communication interface 44.
Controller 42 exchanges data with each of network elements 181, 182 and 18m, connected to it, via communication interface 40. Controller 42 receives static and run-time data from each of the network elements, connected thereto, and stores this data in storage unit 46. It is noted that static data and run-time data, which are stored in the storage unit 46, can be organized in corresponding databases.
Controller 42 further receives a data update request from communication processor unit 14 (Figure 1). The data update request can address some or all of the network elements, which are connected to monitor unit 16. Controller 42 checks if the latest version of the corresponding static data, presented in storage unit 46, was sent already to communication processor unit 14. If static data had been sent, then controller 42 transmits only run-time data, to communication processor unit 14, via low-speed communication interface 44. If static data had not been sent, then controller 42 sends it, together with corresponding runtime data, to communication processor unit 14, via low-speed communication interface 44. Controller 42 further adds an attribute "sent" to static data in storage unit 46, which was already sent to communication processor unit 14.
Reference is now made to Figure 3, which is a schematic illustration in detail of communication processor unit 14 of Figure 1, constructed and operative in accordance with a further preferred embodiment of the present invention. Communication processor unit 14 includes a low-speed communication interface 70, a high-speed communication interface 74, a controller 72 and a storage unit 76. Controller 72 is connected to low-speed communication interface 70, to 5 storage unit 76 and to high-speed communication interface 74.
Controller 72 exchanges data with monitor units 161, 162 and 16N via lowspeed communication interface 70. Controller 72 can receive either runtime data from monitor units 161, 162 and 16N, or both static and runtime data. In case controller 72 receives static and run-time data, it lo stores static data in storage unit 76 for future use. Controller 72 further transmits the received static and run-time data to NCM unit 12, via highspeed communication interface 74, using high-speed communication channel and corresponding communication protocol.
If controller 72 receives only run-time data, related to some specific NE, it checks first in storage unit 76 for the latest version of respective static data. If the latest version of respective static data is present, then controller 72 combines it with the received run-time data and sends the combined data to NCM unit 12. If the required static data is not present in storage unit 76, then controller 72 sends a request to the respective monitor unit for missing data. Upon reception of requested static data, controller 74 combines it with associated run-time data and sends the combined data to NCM unit 12. Controller 72 also stores received static data in storage unit 76 for future use.
Reference is now made to Figure 4, which is a schematic illustration of a method for operating monitor unit 16N (Figure 2), operative in accordance with a further preferred embodiment of the present invention.
In step 100, static and run-time data is received from the network elements, which are connected to a selected monitor unit. With reference to Figure 2, controller 42 of monitor unit 16Nreceives static data io and run-time data from network elements 18m-2, 18m-1 and 18m (Figure 1), connected thereto, via communication interface 40.
In step 102, static and run-time data is stored in a storage unit. With reference to Figure 2, controller 42 of monitor unit 16Nstores received static and run-time data in storage unit 46. Preferably, static data and run time data are stored in dedicated databases.
In step 104, a request for data transmission is received. With reference to Figure 2, controller 42 of monitor unit 16N receives a request for data transmission, from communication processor unit 14 (Figure 1), via low-speed communication interface 44. The data transmission request can be initiated, for example, by NCM unit 12, when it refreshes its database or interrogates the network elements at start-up.
In step 106, changes in data are detected. With reference to Figure 2, controller 42 of monitor unit 16Ndetects the changes in the static andlor run-time data, provided by at least one of the network elements 18M-2, 18m-1 and 18m (Figure 1), connected thereto. These changes can initiate the data transmission to communication processor unit 14. The exemplary events, triggering the data transmission, can be changes in a network element status, re-start or replacement of a network element and the like.
In step 108, a status of static data is checked. With reference to Figure 2, controller 42 of monitor unit 16Nprepares static and run-time data for transmission to communication processor unit 14 (Figure 1). Prior to transmission, controller 42 checks, if the latest version of static data had been sent to communication processor unit 14. If the last version of static data had been sent, then monitor unit 16Nproceeds to step 112, otherwise it proceeds to step 110.
In step 110, static data is transmitted to communication processor unit 14. With reference to Figure 2, controller 42 of monitor unit 16N transmits static data to communication processor unit 14, via communication interface 44. Controller 42 further assigns an attribute igsent" to this static data, so that the next time there will be a request for data transmission related to this specific data or associated network element, only the run-time portion of data will be sent.
In step 112, run-time data is transmitted to communication processor unit 14. With reference to Figure 2, controller 42 of monitor unit 16Nsends the required run-time data to communication processor unit 14, via low-speed communication interface 44.
Reference is now made to Figure 5, which is a schematic illustration of a method for operating communication processor unit 14 (Figure 3), operative in accordance with a further preferred embodiment of the present invention.
In step 150, data from at least one of the monitor units 161, 162 lo and 16Nis received. With reference to Figure 3, controller 72 receives data from at least one of the monitor units 161, 162 and 16N, via low-speed communication interface 70. Received data can include both static data and run-time data, or only run-time data. Received data can be related to the status of at least one of monitor units 161, 162 and 16N, which transmitted data, to the status of at least one of network elements 181, 182 and 18m, connected to the respective monitor unit, or to both.
In step 152, a check for static data within received data is performed. With reference to Figure 3, controller 72 checks if received data includes static data. If static data is present within received data, then controller 72 proceeds to step 160. If no static data is included in received data, then controller 72 proceeds to step 154.
In step 154, a check for static data in storage unit 76 is performed. With reference to Figure 3, controller 72 checks if the latest version of static data, associated with received data is present in storage unit 76. If controller 72 finds the required static data, it combines this data with respective run-time data and proceeds to step 162. If controller 72 does not find the required static data, it proceeds to step 156.
In step 156, static data is requested from the respective monitor unit. With reference to Figure 3, controller 72 requests missing static data, which is related to received run-time data, from the respective monitor unit, which in the present example is monitor unit 16N of Figure 1.
In step 158, requested static data is received. With reference to Figure 3, controller 72 receives requested static data from the corresponding monitor unit 16N of Figure 1, via low-speed communication interface 70.
In step 160, static data is stored in storage unit 76. With reference to Figure 3, controller 72 stores static data in storage unit 76. Stored static data can be either static data which was received together with run-time data, as described above (step 152), or it can be static data, which was received upon a request from controller 72 (step 158).
In step 162, run-time and static data are transmitted to NCM unit 12 (Figure 1). With reference to Figure 3, controller 72 combines run-time and static data, converts resulting data into an appropriate communication protocol, and transmits data to NCM unit 12 (Figure 1), via high-speed communication interface 74 and high speed communication channel.
It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Rather the scope of the present invention is defined only by the claims, which follow.
Claims (18)
1 Communication system for exchanging data over a network between a plurality of network elements and a network control manager, the communication system comprising: a communication processor unit, connected to said network control manager via a high-speed communication channel; and, a plurality of monitor units, connected to said communication processor unit, wherein at least one of said network elements is connected to a selected one of said monitor units, thereby defining an interconnected pair.
2.
The communication system according to claim 1, wherein said plurality of monitor units are connected to said communication processor unit via a low-speed communication channel.
The communication system according to claim 1, wherein each one of said monitor units includes: a controller; a communication interface, for connecting to at least one of said network elements, connected to said controller; a lowspeed communication interface, for connecting to said communication processor unit via said low speed communication channel, connected to said controller; and a storage unit, connected to said controller.
4. The communication system according to claim 1, wherein said communication processor unit includes: a controller; a high-speed communication interface, for connecting to said network control manager via said high-speed communication channel, connected to said controller; a low-speed communication interface for connecting to at least one of said monitor units via said low-speed communication channel, connected to said controller; and a storage unit, connected to said controller.
The communication system according to claim 1, wherein a network element and a monitor unit of a selected said interconnected pair, exchange data there between.
6. The communication system according to claim 5, wherein said data includes static data and run-time data. -18-
7. The communication system according to claim 3, wherein said monitor unit receives said static data and said run-time data from each of said network elements connected thereto, and wherein said controller stores said static and said run-time data in said storage unit.
8. The communication system according to claim 7, wherein said controller detects a request for data transmission, wherein said controller detects a status of said static data in said storage unit, providing a detection result thereby, wherein said monitor unit transmits said static data and said runtime data to said communication processor unit, when said detection result indicates that a last version of said static data was not transmitted to said communication processor unit yet, and wherein said monitor unit transmits only said run-time data to said communication processor unit, when said detection result indicates that said fast version of said static data was already transmitted to said communication processor unit.
9. The communication system according to claim 7, wherein said controller detects a change in said received static and/or run-time data, thereby generating a trigger for data transmission, wherein said controller detects a status of said static data in said storage unit, providing a detection result thereby, wherein said monitor unit transmits to said communication processor unit said run-time data together with said static data, when said detection result indicates that a last version of said static data was not transmitted to said communication processor unit yet, and wherein said monitor unit transmits to said communication processor unit only said run-time data, when said -detection. Tesuft indicates that said last version of said static data was already transmitted to said communication processor unit.
10. The communication system according to claim 4, wherein said communication processor unit receives data from selected one of said monitor units, said received data comprising at least run-time data, wherein said controller detects static data within said received data, producing a first detection result thereby, and, wherein said controller transmits said received data, to said network control manager, via said high-speed communication interface, when said first detection result indicates the presence of said static data within said received data.
11. The communication system according to claim 10, wherein said controller detects static data in said storage unit, said static data being respective to said received data, when said first detection result indicates that said static data is not present within said received data, producing a second detection result thereby, wherein said controller combines said static data with said received data when said second detection result indicates the presence of said static data in said storage unit, and wherein said controller transmits said combined data, via said high-speed communication interface, to said network control manager.
12. The communication system according to claim 11, wherein said controller requests said static data from said selected one of said monitor units, when said second detection result indicates that said static data is not present in said storage unit, wherein said controller receives said static data from said selected one of said monitor units, and, wherein said controller stores said received static data in said storage unit.
13. The communication system according to claim 12, wherein said controller combines said received static data with said run-time data, and wherein said controller transmits said combined data, via said high-speed communication interface, to said network control manager.
14. Method for exchanging data over a network, between a plurality of network elements and a network control manager, via a mediating communication system, the mediating communication system being internally connected via a low-speed communication channel, the network elements being connected to a front-end of the mediating communication system and the network control manager being connected to a far-end of the mediating communication system, the method comprising the steps of:
receiving data at said front-end of said mediating communication system from at least one of said network elements, said received data including static data and run-time data; storing said static data and said run-time data in said front-end storage unit of said mediating communication system; detecting changes in said data or a request for said data transmission; detecting the status of said stored static data, thereby producing a first detection result therefrom; and transmitting said run-time data to said far-end of said mediating communication system via said low-speed communication channel, when said first detection result indicates that the last version of said static data was already transmitted to said far-end via said low-speed communication channel.
15. The method according to claim 14, further comprising the step of: transmitting said static data and said run-time data to said farend of said mediating communication system via said low-speed communication channel, when said first detection result indicates that the last version of said static data was not transmitted to said far-end of said mediating communication system yet.
16. The method according to claim 15, further comprising the steps of: receiving said static data and said run-time data at said far-end of said mediating communication system; storing said static data in a far-end storage unit of said mediating communication system, and transmitting said static data and said run-time data to said network control manager via a high-speed communication channel.
17. The method according to claim 14, further comprising the steps of: receiving said run-time data at said far-end of said mediating communication system; combining said run-time data and previously stored respective static data, thereby producing data combination; and transmitting said data combination to said network control manager via said high-speed communication channel.
18. The method according to claim 17, further comprising the steps of: requesting said static data from said network element, when said respective static data is not present in said far-end storage unit; receiving said requested static data from said network element; storing said received static data in said far-end storage unit; combining said static data and respective run-time data, thereby producing data combination; and transmitting said data combination to network control manager, via said high-speed communication channel.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB0004284A GB2359691B (en) | 2000-02-23 | 2000-02-23 | Telecommunication network management |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB0004284A GB2359691B (en) | 2000-02-23 | 2000-02-23 | Telecommunication network management |
Publications (3)
Publication Number | Publication Date |
---|---|
GB0004284D0 GB0004284D0 (en) | 2000-04-12 |
GB2359691A true GB2359691A (en) | 2001-08-29 |
GB2359691B GB2359691B (en) | 2002-02-13 |
Family
ID=9886253
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB0004284A Expired - Fee Related GB2359691B (en) | 2000-02-23 | 2000-02-23 | Telecommunication network management |
Country Status (1)
Country | Link |
---|---|
GB (1) | GB2359691B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006097615A1 (en) * | 2005-03-16 | 2006-09-21 | Wavestorm | Device and method for communicating in a network |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0822498A1 (en) * | 1996-06-27 | 1998-02-04 | Bull S.A. | Procedure for monitoring a plurality of object types of a plurality of nodes from a managing node in an information system |
US5920565A (en) * | 1993-07-30 | 1999-07-06 | British Telecommunications Public Limited Company | Method and apparatus for intranetwork communication |
-
2000
- 2000-02-23 GB GB0004284A patent/GB2359691B/en not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5920565A (en) * | 1993-07-30 | 1999-07-06 | British Telecommunications Public Limited Company | Method and apparatus for intranetwork communication |
EP0822498A1 (en) * | 1996-06-27 | 1998-02-04 | Bull S.A. | Procedure for monitoring a plurality of object types of a plurality of nodes from a managing node in an information system |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006097615A1 (en) * | 2005-03-16 | 2006-09-21 | Wavestorm | Device and method for communicating in a network |
FR2883437A1 (en) * | 2005-03-16 | 2006-09-22 | Wavestorm Sarl | DEVICE AND METHOD FOR COMMUNICATION IN A NETWORK |
Also Published As
Publication number | Publication date |
---|---|
GB2359691B (en) | 2002-02-13 |
GB0004284D0 (en) | 2000-04-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6944623B2 (en) | Method for data synchronization in web-based communications management system | |
US7054922B2 (en) | Remote fieldbus messaging via Internet applet/servlet pairs | |
US20040205689A1 (en) | System and method for managing a component-based system | |
EP1720286A2 (en) | Network management system and method | |
US20050122958A1 (en) | System and method for managing a VoIP network | |
CN103944814A (en) | Data exchange method and system and gateway server | |
CN113504755A (en) | SCADA monitoring system and method based on hybrid cloud framework | |
EP0840969B1 (en) | Universal object translation agent | |
JP4673532B2 (en) | Comprehensive alignment process in a multi-manager environment | |
GB2359691A (en) | Distributed network monitoring with static/dynamic data discrimination | |
US20020019867A1 (en) | Data transmission to network management system | |
CN110572845A (en) | wireless talkback monitoring system and method | |
JP2004507849A (en) | Operation system of unmanned wireless transmitter, especially system for remote control and remote monitoring of unmanned wireless transmitter | |
US20040215765A1 (en) | Method for integrated infrastructure and facility management | |
KR19980026888A (en) | Remote fault management method using Simple Network Management Protocol (SNMP) in asynchronous transmission (ATM) device | |
KR101377461B1 (en) | Remote Maintenance and Monitoring Service Framework for Heterogeneous Device and System | |
KR100489941B1 (en) | The method for alarm status synchronization between NMS agent and network element | |
KR20030059367A (en) | Method for controlling home devices from remote place and server thereof | |
KR20000039704A (en) | Method for converting notification information between communication network agent and common object request broker architecture manager in atm | |
JP2804876B2 (en) | Communication method for network system including multiplex system | |
KR100535310B1 (en) | Fault management method in network management system | |
KR20030026743A (en) | Method of static table object retrieval | |
CN117056167A (en) | Robot log information management method and system based on IROS | |
KR100767553B1 (en) | How to manage communication status of remote device in optical transmission system | |
JP2003167803A (en) | Remote monitoring system and method using internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PCNP | Patent ceased through non-payment of renewal fee |
Effective date: 20040223 |