MXPA01002975A - Interface system for integrated monitoring and management of network devices in a telecommunications network - Google Patents

Abstract

A graphical user interface (GUI) system (110) is provided for managing and controlling multiple network devices (160a, 160e) and client applications in a telecommunications network. The GUI system provides an integrated environment in which a user sends instructions and data to the network devices and client applications and receives back data related to status of the network devices and client applications. The integrated environment allows the user to access many window screens (226a-226c) which are all tied into one main window (234). The many window screens provide options for commands and views of data related to various areas of management and control of the telecommunications network. The one main window provides a point of reference so that the user does not have to log onto various systems numerous times or use different terminals dependent upon which command or data the user desires to send or receive. Training and operational time and costs are thus reduced from prior art systems.

Description

• - > 1 INTERFACE SYSTEM FOR MONITORING AND ADMINISTRATION INTEGRATED DEVICES OF A NETWORK IN A NETWORK OF TELECOMMUNICATIONS DESCRIPTION OF THE INVENTION The present invention relates to telecommunications networks and, more particularly, to a graphical user interface (GUI) system for the integrated monitoring and management of 10 network devices in a telecommunications network. Telecommunications networks, such as telephone networks, include a number of different components. Typically, telecommunication networks include network devices that are interconnected through links that facilitate communications. Examples of network devices are digital cross-connections (DXCs), multiplexing equipment, in-line termination equipment, computer systems, and fiber transmission systems. A "link", as is generally used herein, is a physical connection between the network devices that carry network traffic. An individual link can include multiple lines that are logical communication channels. The monitoring and administration of communication networks using the prior art systems is difficult due to the mixture of different types of systems and interfaces involved. By example, a restoration system that restores traffic in * ^ * * £ ¿^^^^ * A telecommunications network after a failure must be able to communicate with each of the different types of reset devices. These restoration systems require human intervention where many restoration functions are performed through the restoration management team. These reset functions include monitoring the network, analyzing network problems, configuring network devices and communication links, managing reset systems, and manually controlling network devices (for example, reset devices) used in particular for restore the network to a normal operational condition. The prior art restoration systems allow users to perform some of the reset functions from a single computer terminal. A computer terminal is well known in the art and includes a display screen and an input device, such as a keyboard. However, in the prior art, the restoration management (RM) equipment must use many different MR systems, which allows access to the various MR systems with different interfaces presented in the display screens of one or more RM terminals. In addition to the different interfaces, including graphical user interfaces (GUIs), the MRI team must use more than one terminate MRI, or register in more than one MRI system with the same MRI terminal. Slab RM systems, which employ RM terminals for different tasks such as pre-planned administration and dynamic real-time restoration, differ from each other, forcing the user to remember a broad classification of 5 keystroke commands and multiple meanings for Function keys due to inconsistent commands and function key definitions between RM systems. Many times, the commands and function keys are cryptic and difficult to remember. Due to the lack of integration of RM systems and RM terminals, no group The universal command is applicable, so it requires an extra effort to learn multiple commands for multiple systems for the same function or similar functions. As a result, additional training, review and operational time are necessary and additional costs are incurred to use the many interfaces involved and for performing the multiple registration tasks or using the multiple RM terminals required with the prior art systems. The present invention overcomes the limitations of the prior art, and provides additional benefits by providing a universal graphical interface for the monitoring or administration of a network. The graphical interface is based on windows and provides control features that greatly reduce any need for key commands, although it greatly increases the ease of learning and use of the systems involved. 25 A consistent graphical user interface on all '^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^. The present invention in this way reduces the amount of time required to learn and perform the same monitoring or administration tasks. The present invention is directed to a graphical user interface system for integrated monitoring or management of network devices or resources in a network. One aspect of the invention is in a telecommunications network having telecommunication network devices, wherein each communication network device has a specific device communication format for communications through the communications network. A telecommunications network monitoring or management system has a processor configured to execute communications monitoring or management processes and an internal communications process. The processor is configured to have access to the telecommunications network and data networks for process communications. The device interface processes are configured to run on the processor. Each device interface process is configured to communicate with one of the telecommunications network devices and with a graphical server process of the monitoring or administration processes of the telecommunications network. The device interface processes are configured to translate communications between a communications format of the graphical server process and the specific device communications format of one of the telecommunications network devices. The graphic server process is configured to communicate with telecommunication network devices through the device interface processes and other processes of monitoring or management of telecommunications network. The graphic interface processes are configured to communicate with a graphical server process and with user terminals through a data network, where communications are exchanged between user terminals and the processes of monitoring or administration of telecommunications ed. and between user terminals and telecommunications network devices. According to a further aspect of the invention, the processes of monitoring or administration of the telecommunications network include processes of analysis, restoration or maintenance of the telecommunications network. The telecommunications exchanged between the user terminals and the processes of monitoring or administration of telecommunications and between the user terminals and the telecommunications devices include data and commands. The telecommunications exchanged between the user terminals and the processes of monitoring or administration of the telecommunications network and between the user terminals and the telecommunications devices include audit commands, and in response to the audit commands, status information in the network of telecommunications, including the communication network link state and the network device status. According to another aspect of the invention, the user terminals are configured to represent a graphical user interface with a main window configured to integrate a plurality of windows used in the monitoring or administration of the telecommunications network. The graphical user interface has control options that comprise files, control, reset, reset equipment, devices or reports. The graphical user interface is configured to integrate access to all telecommunications network monitoring or management options and indicators of this under a main graphic user interface window. The graphic user interface has graphic objects indicating the state of the telecommunications network. Figure 1 is a block diagram of a generalized network topology of one embodiment of the present invention. Figure 2 is a block diagram of details of the illustrated embodiment of the present invention in Figure 1. Figure 3 is a block diagram of the internal communications process of the server of Figure 2. Figure 4 is a diagram of block showing data flows of server components of Figure 2. Figure 5 is a block diagram showing process data flows of a GUI component of Figure 4. Figure 6 is a block diagram showing data flows of processes of a data management component of Figure 4. Figure 7 is a block diagram showing process data flows of an RTR management component of Figure 4. Figure 8 is a block diagram showing data flows of processes of a failure analysis component of Figure 4. Figure 9 is a block diagram showing process data flows of a restoration control component of Figure 4. Figure 10 is a block diagram showing process process data flows of a network control component of Figure 4. Figure 11 is a representation of the main window of the GUI of a modality illustrated in Figure 2. Figure 12 shows a file pull-down menu of a file menu selection of Figure 11. Figure 13 shows a control menu dropdown of a control menu selection of Figure 11. Figure 14 shows a drop-down menu of resetting a selection of reset menu of Figure 11. Figure 15 shows a pull-down menu of reset fixes of a menu selection of reset fixes of Figure 11. Figure 16 shows a drop-down menu of devices from a menu selection of reset devices. Figure 11. Figure 17 shows a drop-down menu of reports from a menu selection of reports in Figure 11. A system interface, and in In particular, a corresponding apparatus and method for a graphical user interface (GUI) system for the monitoring and administration of network devices and resources in a network is described in detail below. In the following description, numerous specific details are provided, such as specific processes, restoration functions, specific component architectures, applications in a telecommunications network, etc., to provide a complete understanding of the embodiments of the invention. One skilled in the pertinent art, however, will recognize that the invention can be practiced without one or more of the specific details, or with other processes, architectures, hardware, etc. In other cases, well-known structures or operations are not shown or described in detail to avoid obscuring the description of the modalities. The "monitoring and administration" of network devices, such as devices in a telecommunications network, typically includes network monitoring, analysis of network problems, configuration of network devices and communication links, system administration of restoration, the maintenance of the telecommunications network, the manual control of network devices, the generation of restoration, maintenance and operational plans, among other functions and reset operations and particular maintenance of network analysis. The modality illustrated is described in particular terms in relation to the restoration of a telecommunications system. Nevertheless, the present invention is not restricted only to restoration systems, but includes all other functions that will be performed in a telecommunications monitoring and administration environment. Figure 1 shows a network topology, in a block diagram format, of a generalized embodiment of the present invention. The block diagram of Figure 1 shows how the operational elements involved are related to general network communications. A generalized GUI system 110 includes a Monitoring and Administration Server 120 (also generally referred to as a processor) and GUI terminals 130a, 130b and 130c. The GUI terminals 130a, 130b and 130c and external systems 140 communicate with the monitoring and administration server 120 over a computer network 150 (also generally referred to as a data network). In the illustrated embodiment, the monitoring and administration server 120 performs reset functions and hosts a reset system called a Real Time Reset (RTR) system. A GUI system for the RTR systems is displayed on the terminals' presentation screens GUI 130a, 130b and 130c. Typically, the user selects options that are presented in the GUI of a display screen of a GUI terminal 130. The user selects the options using a computer input device, such as a guide ball, mouse, or other input device. known in the art. Therefore, the illustrated embodiment provides a system and method in which all user options are integrated under a user-friendly, unified user interface for monitoring and managing communications networks 170. In an illustrated embodiment, the GUI terminals 130a, 130b and 130c are referred to as Reset Management (RM) terminals. The RM terminals are typically modeled as workstation terminals such as DEC Alpha workstations and are connected to the monitoring and administration server 120 hosted on a DEC Alpha server via DECNet messaging in the computer network 150. The computer 150 preferably is a local area network (LAN) or wide area network (WAN). The block diagram format in Figure 1 is not intended to limit the particular network topology to any type. For example, the computer network 150 may have a bus, ring, star, or any other type or combination topology. The external system 140 represents external systems that are connected to the computer network 150. The number of external systems is not limited to the external system 140 shown, but may include numerous other external systems. The external systems feed data to the monitoring and administration server 120. In the illustrated embodiment, the RTR system in the monitoring server and administrator 120 receives data from external systems through the computer network 150. These data may include topology data. and network failure analysis data. The external systems can also collect data from the monitoring and administration server 120, such as network alarm data. The monitoring and administration server 120 receives commands from the GUI terminals 130a, 130b and 130c on the computer network 150. In response to these commands, the monitoring and administration server 120 sends control signals to telecommunications devices 160a-160e to through telecommunications links 165. A telecommunications network 170 includes telecommunications devices 160a-160e and telecommunication links 165. Telecommunication network 170 is not limited by the block diagram format of Figure 1, but rather it can have a network topology of any type found in telecommunications technology. Telecommunications devices 160a-160e are any device found in a telecommunications network. In general, telecommunications devices and resources have specific device telecommunication formats to communicate over the telecommunications network. In the illustrated embodiment, these devices include reset devices used to reset the telecommunications network 170. An illustrative reset device is a digital crossover connection (DXC), which switches circuits based on external commands. A DXC 3/3, for example, has ports that support DS-3 lines and switches traffic between these DS-3 ports. A reset network typically includes several of these devices as part of the DS-3 transmission network, placed between the network switches. In the illustrated mode, the telecommunications network 170 uses X.25 protocols with T1 links. Figure 2 illustrates the internal process architecture of a monitoring and administration server 120 housing the RTR system designated as an RTR server 210. The GUI system 110 in the illustrated mode in a GUI system of RTR 212 and described below. The Network Provisioning Systems are particular systems housed in one of the external systems 140. In the illustrated embodiment, the external system 140 is a Topology Replication Server (TRS) 220. The network provisioning systems in the TRS 200 server provides network topology data through the computer network 150 to a real-time Topology Database 222 hosted on the RTR server 210. The GUI 130 terminals in the illustrated mode are restoration management (RM) terminals. 224 (usually also referred to as user terminals). Terminals RM 224 are 1- .i communicate through the computer network 150 to one or more processes of the GUI client 226 (also known as graphic interface processes) on the RTR server 210. Communications include sending and receiving data, commands such as audit commands for requesting the status of links and network devices and configuring network devices, and unsolicited alarms In the illustrated embodiment, the GUI system is an X window application. The clients 226 of the GUI system on the RTR server 210 transmit GUI windows to a terminal RM 224 on the computer network 150. Preferably, there is a GUI client 226 for each terminal RM 224. The GUI system clients 226 provide an integrated GUI display to the RM 224 terminals. As a result, the polished modality provides a consistent user-friendly interface for the monitoring and management functions of communication networks 170. The GUI presentation is described further elante. The users, through the RM 224 terminals, provide the clients with 226 GUIs with commands and data. In the illustrated embodiment, the telecommunication devices 160 are network reset devices 228 and communicate through a 230, X.25 link, with front-end network interface communication (NIFTE) 232 processes (generally known as network authentication processes). device interface) running on the RTR server 210 described later. As part of the illustrated mode, a single GUI server 234 running on the RTR server 210 provides an interface between all the GUI 226 clients and each process running on the RTR 210 server. After receiving user data and commands from an RM terminal 224, a client 226 GUI sends the data and commands along with registers and deregisters to the GUI server 234. The GUI server 234 performs most of the intelligent processing to enable the GUI functions. In addition, GUI clients 226 write event messages to customer records for system diagnostics and send text-based reports to local printers. Like all RTR processes, clients 226 GUI and GUI 234 server read in system logic at startup to initialize current time parameters. The system logic includes a run-time, a prompt mode and other modes of the RTR server 210. The RTR server 210 also hosts other processes related to the reset. The RTR 212 GUI system in the illustrated embodiment comprises an individual GUI server process 234 on the RTR server 210, one or more GUI 226 client processes on the RTR server 210, one or more RM 2224 terminals and various process interfaces between the server and GUI 234 and other processes in the RTR server 210. The key reset processes are shown in Figure 2 and are described as follows: Although the illustrated mode uses an RTR server 210 to host all processes, this does not limit the invention. In another embodiment, more than one RTR server 210 shares the processing load, so that the processes are distributed among more than one RTR server 210. Also, in the illustrated embodiment of the present invention, RTR 210 servers are used in duplicate as backup devices for the operational RTR server 210. It is well known in the art to distribute the processing load between more than one server and to use duplicate servers as backup devices. A plan administrator process 236 and a pre-plan file database 238 allow users of the RTR server 210 to perform the pre-planned network reset in addition to the real-time reset. The reset pre-plans are stored in the pre-plan file database 238. The plan administrator process 236 is responsible for generating, maintaining and retrieving pre-plans for implementation. A RTR 222 database includes the entire network topology for the External Network Provisioning Systems, housed in the TRC 220 system. The RTR 222 database is full of periodic data fed from external systems, including all topology data. These data are then filtered to fill a Real Time Network Device Database (RTNDD) 240. The RTNDD database 240 is implemented in the global shared memory of the RTR server 210. The RTNDD database 240 provides data in real time in the current configuration and topology of the reset network. The RTNDD database 240 includes an accessible memory resident database for processes hosted by the RTR server 210 (RTR processes) for data readiness and is accessible to some RTR processes for updating data in real time. A line / action database 242 stores log files for actions that have been dispatched and lines that are impacted by an exit. An action record in the line / action database 242 includes actions that have been dispatched to reset devices along with the results of each action. The actions are typically cross-connection or disconnection commands. The GUI server 234 reads the action record and transmits the actions that will be displayed in the GUI system of the RM 224 terminals through the GUI clients 226. A line record includes lines or links that have been identified as impacted by an output or production. The GUI server 234 reads the line record and sends this information through the GUI clients 236 to the RM 224 terminals to be displayed in the GUIs of the RM 224 terminals. A 244 control manager process serves as an interface for internal systems. The control administrator 244 receives commands from external systems, distributes these commands to the appropriate internal purposes, and ensures responses that are returned when necessary. It also maintains the system logic, which are running time parameters of the RTR server 210. The GUI server 234 sends all the changes and state and mode requests for the state to the process of ... A.;? TAáÉ¡ * ijfc. control manager 244. A failure analysis process 246 reads data in alarm from external systems together with network topology data from the RTNDD database 240 and the RTR database. The failure analysis process 246 employs inference machines to analyze this data to detect network faults. When a fault is detected, it sends a fault announcement to the GUI 234 server and other RTR processes. The control manager process 244 changes the status of the normal processes to alert when it receives a failure announcement from the failure analysis process 246. A restore coordination process 248 serves as the main interface for all processes that have a function of control of restoration. The restore coordinator 248 receives commands from the other RTR processes including commands from external systems through the 244 control manager and distributes the commands to RTR processes having a restore control function. The distribution of commands to other processes usually requires control of specific times and sequences, which the 248 restoration coordinator process controls. The restoration coordinator process 248 includes other processes that perform the real-time restoration. These processes are a break insulator, a dynamic route generator, and an action dispatcher process. As explained in more detail later, the system & * "&RTR GUI 212 allows a user to control many reset functions through the user interacting with the individual GUI system.The GUI system may have different display windows displayed on the RM 224 terminal display screen. , but all display windows are integrated under a common main display window Importantly, the display windows are similarly controlled to allow for ease of operation.Reinventing functions include sending manual reset commands to the display devices. reset 228. The GUI server 234 sends all the reset commands to the reset coordinator process 148 and receives return confirmations.The confirmations are used to display the status to the user in the GUI system displayed on the display screens of terminals RM 224 through the clients 226 of the GUI and the computer network 150. A verification administrator process 250 performs routines to verify the actual topology of the reset network and to update the network topology data in the RTNDD 240 database. Verification administrator 250 generally does not require human intervention. However, the GUI 110 system provides a control interface to the verification administrator process 250, so that users can initiate an audit of the limited capacity in the restoration network.

A report manager process 252 processes various data from the RTNDD database 240, the RTR database 22, and system registers 210 of the RTR server to provide report on the reset operations. The GUI 110 system provides a built-in GUI deployed in the RM 224 terminals to access the report manager process 252. Afterwards, a user can request reports and view reports online using a GUI system in an RM 234 terminal. A coordinator process Network Control (NCC) 254 and Frontal Network Interface Communications Processes (NIFTE) 232) provide necessary interfaces between the GUI server 234, with its particular communication format, and the reset devices 228 with their specific device communication formats. An individual NIFTE process 232 provides communications and controls interfaces for each reset device 228 for the RTR server 210. There is a process NIFTE 232 for each reset device 228. The server GUI 234 interconnects with the NCC process 254, wherein the NCC process 254 distributes GUI messages to the appropriate NIFTE 232 process. The processes on the RTR server 210 can communicate with each other through an internal communication process. In the illustrated mode, the internal communication process uses messages that pass between internal mailboxes. As shown in Figure 3, the RTR process 210 passes messages to other processes, such as the GUI server 234, through a server mailbox 312. In turn, the GUI server 234 passes messages to the RTR 310 process through RTP process mailbox 314. The messages are sent from the GUI server 234 to the client processes 226a, 226b and 226c of the GUI via client mails 318a, 318b and 318 c, respectively. The GUI clients 226a, 226b and 226c can send messages to the GUI server 234 through the mail of the server 312. The GUI server 210 both broadcasts messages to all currently registered GUI 226 clients and to individual GUI 226 clients. The RTR processes send messages to the GUI server 234, which then broadcasts the message to all GUI clients currently registered and listed in a broadcast list on the GUI server 234. When a GUI 226 client has an update notification, the notification it is sent to the GUI server and the GUI 234 server will broadcast the update to each of the other GUI clients or to an RTR process depending on the destination of the update. As a result, each GUI client process 226 only needs to have the mail address of the GUI server process 234 and be registered with the GUI server process 234. When a GUI client process 226 is started, it is registered with the client. GUI server 234 through GUI server mail 312. GUI client 226 passes a return address of GUI client 318 mail to GUI server 234 as part of the registration message. The GUI server 234 then connects to the GUI client mail 318, which allows the GUI client 226 to receive broadcast messages from the GUI server 234. If a user of a GUI client 226 requests to exit a GUI 226 client, the GUI client 226 sends a deregistration message to GUI server 234 that will be removed from the broadcast list of GUI server 234. In the rare case of an abnormal client GUI termination, GUI server 234 sends a periodic wave message to each GUI 226 client. If the GUI client 226 does not answer at a specific time or in a number of wave messages, the GUI server 234 will automatically remove the GUI client 226 from the broadcast list. In a similar way, if the GUI client 226 does not receive a wave message from the GUI server 234 at a specific time, then the GUI client 226 will re-register with the GUI server 234. Figure 4 shows a flow diagram of data for the processes on the RTR server 210. For ease of illustration, some processes are grouped into higher-level components, for example, the GUI server process 234 and the GUI 226 client processes are grouped in the GUI 410 component. The GUI component 410 is shown at a more detailed level in Figure 5 when both external and internal data flows are illustrated. Figure 4 and the data flow diagrams of Figures 5 to 10 are generally self-explanatory for those skilled in the art. These data flow diagrams identify various types of data and the appropriate route to and from other processes for such data, as shown in Figures 4 through 10. If you avoid obscuring other important aspects of the invention, only descriptions of the data are provided. summary of such figures. For a better understanding, those skilled in the pertinent art are directed to the same Figures. A data management component 412 of Figure 4 includes the RTR database 222 and the RTNDD database processes 240 of the RTR server 210 shown in Figure 2. The data management component 412 also includes a process of data manager 210, a creation RTNDD database process 612, and a report management process 614 as shown in Figure 6. The report management process 614 includes the report manager process 252 shown in Figure 2. A RTR management component 414 of Figure 4 includes the 244 control manager process of the RTR server process 210 shown in Figure 2. The RTR management component 414 also includes an update manager process 710, a server process of data 712 and a failure processing process 714, as shown in Figure 7. A failure analysis component 416 of Figure 4 includes the failure analysis process 246 of the RTR server of Figure 2. The analysis component of failure 416 also includes an 810 alarm collection process, a state 812 server process, a database server process 814, and a database server process and failure 816, as shown in Figure 8. A reset control component 418 of the figure 4 includes the restoration coordinator process 248 of the RTR server 210 of FIGURE 2. The restore control component 418 of FIGURE 4 also includes a 910 rupture isolator process, a 912 plan manager process, a generator process of route 914 and an action dispatcher process 916 as shown in Figure 9. A network control component 420 of Figure 4 includes the NCC process 254 and the NIFTE process 256 of the RTR server 210 of Figure 2. network control component 420 also includes an interactive device control system (IDCS) 1010 gateway process, as shown in Figure 10. The verification administration process 250 is shown together with a monitoring process 422 in Figure 4. The RTR 212 GUI system allows a user, at the RM 224 terminal, to manage and monitor the restoration of a telecommunications network in a way that is easy to learn and re-learn. alizar compared with systems of the prior art. The following functions are included in the administration and recovery monitoring processes. The RTR 212 GUI system allows a user to configure the RTR server 210, interfaces and links to the reset devices 228. A user can configure the parameters of the RTR server interfaces with each reset device 228. These include the parameters that NIFTE 232 processes read at the start, as well as operating time parameters. The parameters include, but are not limited to, link status, link audit intervals, and group of messages, which are well known in the art. A user can designate one telecommunications channel as primary and another telecommunications channel as return. Each X.25 link comprises four channels. Each channel handles either audit commands, connection / disconnection commands, administration commands, or unsolicited alarms. These channels can be configured through the GUI system of RTR 212 through a user placed in a terminal RM 224. With the GUI system of RTR 12 a user can configure X.25 switches to add, delete or modify addresses for devices of restoration. A user may change address and X.25 packet location devices to other sites having additional RTR servers 210 or switches. With the RTR GUI system 212, a user placed in the RM 234 terminal can change the X.25 links to a reset device 228 on or off. For example, a user can take one or more X.25 links out of service for maintenance. This could be the case where the RTR 210 server g ^^^^^^ ^^^^ - use backup communications. With the RTR 212 GUI system, a user can control the reset devices 228 manually during a reset process. A user can also redirect the traffic of a telecommunications device in order to perform maintenance activities. This can be done either in real time with direct interaction with the devices in a native RTR mode, or it can be pre-planned. The RTR 212 GUI system provides real-time presentations of the state and health of a telecommunications network that carries traffic. A user placed at the RM 224 terminal can receive alerts regarding any detected fault, as well as identification or impacted telecommunications lines. The GUI system of RTR 212 also allows a user to monitor the reset devices. Monitoring can be done both at a device level, where the device is represented as a single functional component, and at the port level, where each port of a device is monitored. By monitoring the ports, a user can effectively monitor lines between devices. The RTR 212 GUI system also allows a user to monitor X.25 links and switches between an RTR server 210 and the reset devices 228. A user can monitor in real time the status of each link as well as the traffic exchanged between an RTR server 210 and the reset devices 228. A user can also perform audits on the reset devices 228 and in X.25 links With the RTR 212 GUI system, a user can efficiently and effectively administer reset plans that have specific designated tasks, all with a unified GUI. This can be done for the previously planned restoration and to control the restoration network for maintenance activities. A reset group includes custom reset groups described below and fault extensions. A fault extension is a segment of the transmission network that can be restored with a single reset route in a previous plan. The user can create, delete or modify the reset groups. A user can also create, delete or modify previous plans and implement previous plans. A user can initiate the process of generation of previous plan in general or for certain groups of restoration in danger. A user can also monitor the status of previous plans and approved previous plans that have been generated. The RTR 212 GUI system also allows a user to effectively and efficiently monitor and manage RTR processes and the total RTR system by manipulating various parameters, all with a unified GUI. For example, a dynamic route generator (DRG) mode of an RTR system can be enabled or disabled. When enabled, the RTR system operates in a real-time reset mode. When disabled, the RTR system operates in a pre-plan mode. A user can also manage RTR processes by creating, deleting or modifying reset groups. The RTR 212 GUI system allows a user to perform the administration and monitoring functions as described above through a single GUI system to an individual GUI system, while in the RM 224 terminal in the illustrated embodiment of the invention. The resulting consistent pattern helps the user to control and perform the many functions involved without resetting for annoying commands and controls of the prior art systems. The functions themselves are performed through internal RTR processes. As shown in Figure 11, a main window 1100 of the GUI, as presented on the display screen of an RM 224 terminal, comprises a series of pull-down menus 1110, a series of status buttons 1130, and an announcement section. 1150. The pull-down menus 110 include file 1112, control 1114, reset 1116, reset groups 1118, devices 1120, reports 1122 and help 1124. The series of status buttons 1130 includes execution status 1132, status of RG 1134, mode readiness 1136, current mode 1138, link status 1140, previous plans not approved 1142, plan generator 1144 and alarm 1146. Drop-down menus 1110 provide users with easy access to most of the functions of the RTR system. From the main window of GUI 1100, a user can select the option of "file" 1112. Selecting option 1112 of "file" allows the user to access the menu of file 1200 as shown in Figure 12 The first option of the 1200 file menu is a 1212"refresh" option. The "refresh" option 1212 forces an update to a list displayed in the GUI 1100 main window. A "print" option 1214, when selected , causes the ads actually displayed in the 1150 ad section of the GUI 1100 main sale to be printed. An "exit" option 1216, when selected, causes the terminal RM 224 running the particular GUI main sale 1100 to terminate communications with the client process 226 of the GUI serving the particular RM terminal 224 and exit the GUI program that runs on terminal RM 224. A "control" option 114 of the main window GUI 1100, when selected, allows a user to access control menu 1300 as shown in Figure 13. A "change password" option 1312, when selected, allows a user to change a password used to access several RTR system functions. A "Disable I / O" 1314 option, when selected, allows a user to mute an audible alarm signal. A "maintenance mode" option 1316, when selected, allows a user to access maintenance functions. These maintenance functions are added to other reset functions Once added, the maintenance functions remain enabled until the user leaves the RTR system by selecting the "exit" option 1216. A "reset" option 1116 of the main window GUI 1100 of Figure 11, when selected, allows a user to access the reset menu 1400 as shown in Figure 14. A "presentation partner registration" option 1412, when selected, displays a record that displays successful and unsuccessful disconnect and connection commands sent to reset devices 2228. An "impacted presentation line registration" option 1414, when selected, allows a user to display a record comprising information regarding link lines impacted by problems with the telecommunications network 170. A "check path" option 1416, when selected, allows a user to verify traffic on any specific route, not just one line of a group / restoration path. A "real-time execution" option 1418, when selected, allows a user to enter start and end line entry points of lines that will be excluded from a reset task. The uncharacterized path generator previously presented does not generate routes using any line input of the real-time exclusions option 1418. A "repair events" option 1420, when selected, allows a user to track the status of events repair. This option allows a user to enter a time stamp and a comment detailing the repair event. The user can enter a time stamp and a comment detailing the repair event. After completing the repair event, the user can delete the event. A "reset group" option 1118 of the main GUI 1100 sale of Figure 11, when selected, allows a user to access the reset menu 1500 as shown in Figure 15. A "show list" option reset setting "1512, when selected, allows a user to see a list of a reset group in a lower option of the GUI 1100 main window. A" set danger2 1514"option, when selected, allows a The user identifies a problem on the network, and then finds and identifies reset groups to isolate areas for monitoring.A "find reset groups" option 1516, when selected, allows a user to search for reset groups based on identification One option to "create custom reset group" 1518, when selected, allows a user to add specific systems and lines to a new group of restoration. A user can either create a custom reset group through a previous population option or a copy option. The previous population option allows a user to specify portions of * * • - ^ f-^ ^^^^ a telecommunications network that will be included in a custom reset group either by specifying telecommunication nodes at stations, or by identifying equipment specifications of telecommunication network devices 228. Telecommunications devices and lines or links that are associated with the specified items are included in the custom reset group. For example, if two telecommunication stations are specified, the custom reset group also includes any line that extends between the two stations. The copy option allows a user to copy portions of fault extensions such as telecommunication lines or devices that will be included in a custom reset group. A "delete custom reset group" option 1520, when selected, allows a user to delete a custom reset group from the system. The "devices" option 1120 of the GUI 1100 main window of Figure 11, when selected, allows a user to access the 1600 device menu as shown in Figure 16. The device menu allows a user to select various maintenance functions, including configuration control of NIFTE 232 processes and X lines and switches .25. The execution of these maintenance functions causes the GUI 234 server process to send commands to the CC 254 process represented by the data flow from "GUI to NC Cmd", shown in Figure 4. The updates made by the GUI server process 234 are sent to the database process RTNDD 240 as represented by the data stream of "activation of data change GUI for data management", as shown in Figure 4. A link status option 1612, when selected, it opens a window that shows the real-time status of all DXC links in the network. A "native mode" option 1614, when selected, allows a user to directly interact with a reset device 228 using device commands through a NIFTE process 132 designated for the reset device 228. This option essentially opens a direct interface for the NIFTE 232 process for the selected reset device 228. The "scan" option 1616, when selected, allows a user to monitor the X.25 traffic for a selected link between a selected NIFTE process 232. When this option is selected, a trace window is displayed in the GUI interface on the RM 224 terminal. The X.25 messages for the selected link are displayed in the trace window as provided by the NIFTE 232 process. The "track" option 1616 is to troubleshoot when a device is not responding appropriately to a user's commands. The tracking window shows all the traffic that is sent by the user to the device, and the one that is sent to the user from the device as captured ^^^^^ j ^^^ g ^ g ^ by the selected NIFTE process 232. The "audit" option 1618, when selected, allows a user to initiate an audit on one or more reset devices 228. The RTR 210 server automatically performs audits on a scheduled basis. The "audit" option 1618, when selected, allows users to perform independent audits of any audit program. An audit window is displayed in a GUI interface in terminal RM224 showing the message record that results from the audit. The NIFTE 232 processes for the selected devices perform the audit and provide the messages that are displayed in the audit log. The results of the audit are written by the NIFTE 232 processes in the RTNDD database 240. The "start / stop" option 1620, when selected, allows a user to start or stop the selected NIFTE process 232. This can be used for maintenance tasks. The "operation" option 1622, when selected, provides current or historical performance data in NIFTE 232 processes. The "link handling" option 1624, when selected, allows a user to enable or disable X.25 links. selected for a reset device 22. The GUI 232 server sends messages to the NCC process 254 to start or stop a NIFTE 232 process for a particular link. The "device data" option 1626, when selected, allows a user to examine the RTNDD 240 database. A device data window is displayed, which has split windows A top window shows all the reset device data 228 and a lower window shows specific port data for the reset device 228. The option "set up operating time" 1628, when selected, allows a user to configure the parameters of a selected NIFTE process 232, while the NIFTE process 232 is current. The "configure device" 1630 option and the "configure switch" option 1632, when selected, allow a user to configure parameters for a DXC device and RTR switch, respectively, to be read by selected NIFTE processes 232 after the start of the NIFTE process selected 232. With these options to configure, the GUI server 234 sends updates directly to the selected NIFTE process 232 through the NCC 254 process. The "keep notification" option 1634, when selected, allows the user to determine if the GUI server 234 is registered to receive notifications of other processes on the RTR server 210. The option of "reports" 1122 of the main window GUI 1100 of Figure 11, when selected, allows a user to access a 1600 report menu as shown in FIG. shown in Figure 17. The "RTR status" option 1712, when selected, allows a user to display a message log of state. The "RTR users" option 1714, when selected, allows a user to display a list of users currently registered in the RTR system. The "circuit status" option 1716, when selected, allows a user to check the status of lines or links according to the identification of the circuit. The "generate PMR / IOR" option 1718, when selected, allows a user to create a post-mortem report or an initial fault report. An option to "annotate PMR" 1720, when selected, allows a user to add comments and time stamps to the post-mortem report. These comments and time stamps indicate when a fault was restored and normalized. The "maintenance list" option 1722, when selected, allows a user to display lines or links that are currently undergoing maintenance. The option "capacity with failure" 1724, when selected, allows a user to deploy the network capacity was unusable. The "self-monitoring report" option 1726, when selected, allows a user to gather designed excerpts from the post-mortem and breakdown reports. The "help" option 1124 of the main window GUI 1100 of Figure 11, when selected, allows a user to access an 1800 help menu shown in Figure 18. The "summary" option 1812, when selected , displays a general description of the RTR system running on the RTR server 210. The "this sale" option 1814, when selected, displays specific help text to a current window that is being displayed. Referring back to Figure 11, in addition to the drop-down menus 1110 of the main window 1100, the series of status buttons allows a user to control and access the information, in addition. The run status button 1132 of the main window 1100 of Figure 11 shows the actual execution status of the RTR server 210 in communication with the terminal RM 224 by displaying the execution status button 1132. The execution status of an RTR server can be "primary" or "backup". Once, one server is primary and another serves as a backup. The actual execution status is maintained by the control manager process 244. The GUI server process 234 retrieves an execution status with a command / response message exchange with the 244 control manager process. From the main window 1100 of the GUI interface in the terminal RM 224, a user, who has authorization through the password validation, can select the execution status button 1132 to change the execution status of the RTR server 210 in communication with the terminal RM 224 When selecting the run status button 1132, a user can initiate a process failure either in any direction, between the primary and backup RTR servers. In this case, the GUI server process 234 sends a message to the control manager process 244. The control administrator process 244 fails and changes the running status of the present RTR server. The control administrator process 244 also sends messages to the control manager processes of other RTR servers to change the execution states and notify each internal RTR component of the change in the execution state by sending a message to each internal RTR component. A dynamic route generation (DRG) state is enabled when the DRG algorithm in the route generator process 914 is enabled to perform the real-time reset. This is disabled when the previously planned reset is in place. The DRG status button 1134 of the main window 1100 of Figure 11 displays the actual status of the DRG algorithm. An authorized user through password verification can change the DRG state of the RTR server of the present 210, selected the status button DRG 1134. After selecting the DRG status button, the GUI server process 210 sends a message to the server. control manager process 244. In turn, the control administrator process 244 sends a change DRG status message to the reset control component 418. the 244 control manager process also sends notifications to each impacted process. A prompt mode is "normal" during the nominal operation and is "alert" if a fault has been detected. The change in the prompt mode is provided to the GUI server process 210 through the 244 control manager process in response to a failure announcement sent by the failure analysis process 246. An authorized user through password verification , manually you can change the selected prompt mode the prompt mode button 1136 of the main window 1100 of Figure 11. The GUI server process 210 then sends a message to the 244 control administrator process. The control administrator process 244 in turn sends a prompt message of change to all internal RTR processes to change the mode from normal to alert, or vice versa. A current mode status button 1138 of the main window 1100 of Figure 11 displays the current mode of the RTR processes. Current modes include demonstration and operational status. A link status button 1140 of the main sale 1100 of Figure 11 displays the status of X.25 links for the reset devices 228. the link status button 1140 indicates the status through the color of the button and a number presented on the button. If any reset device 228 is in a state where the two links are not working, the link status button 1140 will be a red color and the number of such reset devices 228 will be displayed on the button. If the link status button 1140 is not red, then the button will be yellow if any reset device 228 is in a state where just one of its two links is not working, and the number of such reset devices 228 will be displayed on the button. If the link status button 240 is not red or yellow, then the button will be green, indicating that all the links in the telecommunications network are working The GUI client process 226 obtains the link status directly from the requests to the RTNDD database The unapproved previous plans button 1142 of the main sale 1100 of Figure 11 shows, when selected, the number of previous plans that have been generated in the last previous plan generation process operation, but they have not yet been approved. The RTR server 210 has a self-approval method for previous plans that fall within a threshold of changes of a previous plan. This threshold of change is established as a percentage of lines that have changed. Previous plans that do not fall within this threshold of change must be manually approved. By selecting the button for unapproved pre-plans 1142, a user can open a list of previously unapproved plans. The plan generator status button 1144 indicates the operational status of a process that is necessary to generate plans. The plan generator status is either "stopped" or "running." The alarm state button 1146 is on when a reset group has been declared as "hit" by a fault based on the alarm analysis by the failure analysis process 246. A user of the GUI interface of the RM terminal 224 sees and recognizes alarm selected the alarm state button 1146 through the use of an input device by computer. The announcement section 1150 in the main window 1100 of the GUI system of Figure 11 shows the status of selected reset groups > by a user specifying a particular view of the window. For example, a user can specify that all reset groups with a status of "impacted" will be displayed in ad section 1150. A user can see the entire network or just a subgroup of the network. If one or more reset groups are listed as "impacted" the alarm status button 1146 is displayed as light. The data in the list of announcements is obtained directly from the database process RTNDD 240, with requests based on the identification of a user of a vision. The advertisement section 1150 of the main window of GUI 1100 of Figure 11 includes an initiator showing the actual number of advertisements, which in the case of Figure 11 is 10. For each advertisement, the data fields are displayed in the advertisement section 1150 of the main window GUI 1100 of Figure 11. A data field of "RS name" 1152 displays a name assigned to the particular reset group. A "type" data field 1154 displays the type of reset group including the fault or client extension. A client RS includes a manually assembled list of systems and lines, in contrast to a fault extension RS, which includes exactly all systems and lines within a non-branched, single, isolated portion of the network.

The RTR system treats a fault anywhere along a fault extension as a fault. A "state" data field 1156 displays the state of the reset group including the impacted, endangered, redirected, maintenance or normal. Impacted means that the items so marked have been classified as having a fault. Danger is a state assigned by a user to an RS to indicate that there is a broadcast on the telecommunications network ^ l 70 that can escalate to a fault situation. For example, a train derailment can damage the equipment associated with a nearby RS, so a user can place the RS in a dangerous state. Redirected means that the item so marked has its traffic operation on an alternate trajectory, due to a problem in its primary trajectory. Maintenance is a state assigned by a user to an RS to indicate that repair and maintenance operations are being performed on the equipment or segments associated with the RS. Normal means that the item so marked has its traffic operation in original paths and there is no fault present. An "ESPs interrupt" data field 1158 displays details of where an interruption occurred in a link. An interruption may occur, for example, at a particular station or between stations. A state data field 1160 indicates whether the state is inactive or active. An "IMP system" data field 1162 displays the number of systems in the particular reset group that are performed by the status displayed in the "state" data field 1156. This value obtains updates every 5 seconds. An "IMP line" data field 1164 displays a number for the lines in this reset group that have been made by the status displayed in the "state" data field 1156. This value is updated every 5 seconds. An "active" data field 1166 displays the number of lines carrying traffic in the reset group. This fault is updated every 5 seconds. A "capacity" data field 1168 displays the total number of lines available in the reset group. This fault is updated every 5 seconds. Although the invention is used to manage and monitor telecommunications systems involving reset functions, the invention can similarly be used to manage and monitor other telecommunication functions involved., such as, for example, construction, expansion, division, analysis and classification of telecommunications systems. In addition, the invention can be easily applied to a GUI system for monitoring and managing resources in a computer network, such as printer, modems, shared software applications, etc. These and other changes can be made to the invention in view of the description presented above. In general, in the following claims, the terms should not be construed to limit the invention to specific embodiments described in the specification and the claims, but rather they should be constructed to include all the user's graphical interface systems operating under the claims to provide a system for the monitoring and administration of network devices in telecommunication networks. Accordingly, the invention is not limited by the description, but rather its scope will be determined completely by the following claims.

Claims (33)

1. - A telecommunications network having telecommunication network devices, each telecommunications network device having a specific device communication format for communicating through the telecommunications network, a telecommunications network monitoring and administration system comprising: a processor configured to execute processes of monitoring or administration of telecommunications network, the processor configured to have access to the telecommunications network and data networks for process communications; a plurality of device interface processes configured to execute in the processor, each device interface process configured to communicate with one of the telecommunications network devices and with a graphical server process of network monitoring or administration processes telecommunications, device interface processes configured to translate communications between a communications format of the graphical server process and a specific device communications format of one of the telecommunications network devices, the graphical server process configured to communicate with telecommunication network devices through the device interface processes; and graphical interface processes configured to communicate with the graphical server process through the process of internal communications and with user terminals through the data network, where communications are exchanged between user terminals and the monitoring or administration processes of telecommunications network, and between user terminals and telecommunications network devices.

2. The telecommunications network monitoring or administration system according to claim 1, wherein the processes of monitoring or administration of telecommunications rd include processes of analysis, restoration or maintenance of telecommunications network.

3. The system of monitoring or administration of telecommunications network according to claim 1, wherein the communications exchanged between the user terminals and the processes of monitoring or administration of telecommunications and between user terminals and telecommunications devices they include data and commands.

4. The telecommunications network monitoring or administration system according to claim 1, wherein the monitoring or management processes of the telecommunications network include a network control coordinating process configured to direct communications between the graphics server processes and the process of device interaction.

5.- The monitoring system or network administration of u - ^ - jkt t ^ kiák ». telecommunications according to claim 1, which includes an internal communication process comprising electronic messages and emails.

6. The telecommunications network monitoring or administration system according to claim 1, wherein the communications exchanged between the user terminals and the processes of monitoring or administration of the telecommunications network and between the user terminals and the devices. of telecommunications include unsolicited alarms indicating problems in the telecommunications network.

7. The monitoring or administration system of telecommunications network according to claim 1, wherein the communications exchanged between the user terminals and the processes of monitoring or administration of the telecommunications network and between the user terminals and the Telecommunications devices include audit commands, and in response to audit commands, includes status information in the telecommunications network including the state of the telecommunications network link and the status of the network device.

8. The system of monitoring or administration of telecommunications network according to claim 1, wherein the communications exchanged between the user terminals and the processes of monitoring or administration of the telecommunications network and between the user terminals and the telecommunications devices include commands for configuring the telecommunications network devices.

9. The system of monitoring or administration of telecommunications network according to claim 1, wherein the user terminals are configured to present a graphical user interface with a main window configured to integrate a plurality of windows used to monitor or manage the telecommunications network.

10. A telecommunications monitoring or administration system for the monitoring or administration of a telecommunications network having telecommunication network devices or resources, the system comprises: a plurality of interface processes configured to communicate with the devices or resources of a telecommunications network. telecommunications network; and a user graphical interface system configured to provide a unified user graphical interface for communicating with telecommunications network devices or resources through the plurality of interface processes for the analysis, restoration or maintenance of the telecommunications network.

11. The monitoring system or telecommunication administration according to claim 10, wherein the user's graphical interface system has control options comprising files, control, reset, reset groups, devices or reports.

12. The system of monitoring or administration of telecommunications according to claim 10, wherein the graphical user interface system is also configured to communicate with processes of monitoring or administration of telecommunications network.

13. The telecommunications monitoring or administration system according to claim 10, wherein the user's graphic interface system is configured c) or to integrate access to all options of monitoring or administration of telecommunications network and indicators of been under the graphical interface of the unified user.

14. The telecommunications monitoring or administration system according to claim 10, wherein each telecommunications network device has different communication formats of specific device to communicate through the telecommunications network.

15. The system of monitoring or administration of telecommunications according to claim 10, e? where the processes of monitoring or management of telecommunications network include a process of control administrator, a process of analysis of failure, a process of coordinator of restoration, a process of administrator of verification, a process of administrator of reports, a process of network control coordinator, an online action data process, a process - "*" "» »» • Real-time network device database, a real-time restore database process, a file process of previous plans, or a plan administrator process.

16. The system of monitoring or administration of telecommunications according to claim 10, wherein the processes of monitoring or administration of telecommunications network comprise processes configured to communicate with external processes through a data network.

17.- The system of monitoring or administration of telecommunications according to claim 10, wherein the graphical user interface system has graphic objects indicating the state of the telecommunications network.

18. The telecommunications monitoring or administration system according to claim 17, wherein the state of the telecommunications network comprises the execution status, dynamic route generation, prompt mode, link status, prior plan status , or alarm.

19. The telecommunications monitoring or administration system according to claim 10, wherein the user's graphical interface system comprises a graphical user interface server, graphic user interface processes, and user terminals.

20. The system of monitoring or administration of telecommunications according to claim 19, wherein the user terminals are configured to be distributed among computer data networks.

21. A telecommunications network that has telecommunications network devices, each telecommunications device having a specific device communication format for communication through the telecommunications network, and a data network system, a method for the monitoring or administration of a telecommunications network that includes: executing processes of monitoring or administration of a telecommunications network and an internal communications process; communicate between the processes of monitoring or administration of the telecommunications network through the process of internal communications; provide access to telecommunications and data networks for the monitoring or management of telecommunications networks; translating communications between a communications format of a graphic server process and specific device communications formats of each of the communication network devices, wherein the graphic server process communicates with the telecommunications network devices; communicate between the processes of monitoring or administration of the telecommunications network and the graphic server process; and communicate between the graphical server process and user terminals through the data network, where the user terminals send and receive monitoring communications or . U ^ & , - administration of the telecommunications network to the telecommunications network devices and the processes of monitoring or administration of the telecommunications network through the graphic server process.

22. The method of monitoring or administration of telecommunications network according to claim 21, which further includes: integrating a plurality of graphic display windows under a main graphic display window, where all the graphic display windows are deployed in each of the user terminals for the monitoring or administration of the telecommunications network.

23.- The method of monitoring or administration of telecommunications network according to claim 21, e? where the telecommunications network monitoring or administration communications comprise communication, restoration or maintenance communications of the telecommunications network.

24. A telecommunications monitoring or administration system for monitoring or managing a telecommunications network having telecommunications network devices, the system comprising: a plurality of device interface processes configured to communicate with telecommunications network devices having formats specific device telecommunications; and a graphical user interface system configured to provide a unified user graphical interface for communicating with telecommunication network devices through the plurality of device interface processes.

25. The telecommunications monitoring or administration system according to claim 24, wherein the unified user graphical interface is configured to communicate communications of analysis, restoration or maintenance of the telecommunications network with telecommunications network devices.

26. The telecommunications network monitoring or administration system according to claim 24, wherein the communications exchanged between the user's graphical interface and the telecommunications network devices include audit commands, and in response to the commands of audit, include status information about the telecommunications network including in communication network link status and the status of the network device.

27. The telecommunications network monitoring or administration system according to claim 24, wherein the communications exchanged between the user's graphical interface and the telecommunications network devices include commands to configure the telecommunications network devices.

28. A monitoring system or network administration to monitor or manage a network that has devices or network resources, the system comprises: a plurality of device interface processes configured to communicate with network devices having communication formats; and a graphical user interface system configured to provide a unified user graphical interface for communicating with network devices through the plurality of device interface processes.

29. The network monitoring or administration system according to claim 28, wherein the unified user graphical interface is configured to communicate analysis, restoration or network maintenance communications with the network devices.

30. The network monitoring or administration system according to claim 28, wherein the communications exchanged between the graphical user interface and the network devices include commands to configure the network devices or audit commands, and in response to the audit commands, the exchanged communications include status information about the network including the network link status or network device status.

31.- A system for monitoring or administration of telecommunications to monitor or manage a telecommunications network having telecommunications network devices, the system comprises: a means to integrate user terminals distributed in a data network with a process server and telecommunication network devices distributed in a telecommunication network, wherein the user terminals provide telecommunications monitoring or management controls and options for monitoring or managing telecommunications network devices; a means to use graphical presentation objects to represent the options and controls of monitoring or administration of telecommunications network; a means to integrate graphic presentation objects into graphic windows and to integrate graphic windows under a main graphic window; and a means for presenting the graphical display windows including the main graphic window in each user terminal that will be used to monitor or manage the telecommunications network devices.

32. The telecommunications monitoring or administration system according to claim 31, wherein the options and controls of moni- toring or administration of the telecommunications network include options and controls for analysis, restoration or maintenance of the telecommunications network.

33. - The telecommunications monitoring or administration system according to claim 31, wherein the options and control of monitoring or administration of telecommunications network include commands to configure network devices or audit commands, and in response to commands of audit, the exchanged communications include status information in the network including network link status or network device status. 34.- A computer readable medium that stores executable instructions by computer under a method, the method comprises: integrating user terminals distributed in a data network with a process server and devices or telecommunication network resources distributed in a network of telecommunications, where user terminals provide controls and options for monitoring or administration of telecommunications, to monitor or manage telecommunications fed devices; use graphical presentation objects to represent the options and controls of monitoring or administration of the telecommunications network; integrate graphic presentation objects into graphic windows and integrate graphic windows under a main graphic window; and display the graphical presentation windows including the main graphic window in each user terminal that will be used to monitor or manage telecommunications network devices. 35.- The computer readable medium according to claim 30, which further includes: analyzing a telecommunications network; reestablish a telecommunications network; or maintain a telecommunications network. 36.- The computer readable medium according to claim 30, which further includes: configuring network devices; or audit the network status comprising the network link status or the network device status. rifigaüsjtife