US20090116409A1 - Interactive Topology Graphs for Visualization and Characterization of Sonet Consumption Patterns - Google Patents

Interactive Topology Graphs for Visualization and Characterization of Sonet Consumption Patterns Download PDF

Info

Publication number
US20090116409A1
US20090116409A1 US12/349,333 US34933309A US2009116409A1 US 20090116409 A1 US20090116409 A1 US 20090116409A1 US 34933309 A US34933309 A US 34933309A US 2009116409 A1 US2009116409 A1 US 2009116409A1
Authority
US
United States
Prior art keywords
node
sonet
link
user
nodes
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/349,333
Inventor
Chuxin Chen
Ralph Gnauck
George T. Noll
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Labs Inc
Original Assignee
SBC Technology Resources Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by SBC Technology Resources Inc filed Critical SBC Technology Resources Inc
Priority to US12/349,333 priority Critical patent/US20090116409A1/en
Publication of US20090116409A1 publication Critical patent/US20090116409A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J2203/00Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0028Local loop
    • H04J2203/0039Topology
    • H04J2203/0042Ring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J2203/00Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057Operations, administration and maintenance [OAM]

Definitions

  • the present invention relates generally to telecommunications and more particularly, to a system and method for monitoring telecommunication network activities.
  • a monitoring system can show if a node or link in a network is up or down, and can set off alarms accordingly. Such monitoring works well with a realtime analysis of the hardware in the network.
  • SONET synchronized optical network
  • SONET was proposed by Bellcore in the middle 1980s as a standard for connecting fiber-optic transmission systems.
  • SONET defines interface standards at the physical layer, including a hierarchy of interface rates that allow data streams at different rates to be multiplexed.
  • SONET establishes Optical Carrier (“OC”) levels, or speeds. Typical OC levels include OC-1 for 51.85 Mbps, OC-3 for 155.52 Mbps, OC-12 for 622.08 Mbps, OC-24 for 1.244 Gbps, OC-48 for 2.488 Gbps, and OC-192 for 9.9532 Gbps.
  • OC Optical Carrier
  • TIRKS Trunks Integrated Record Keeping System
  • RBOC regional bell operating company
  • TIRKS provides a great detail of information
  • the method of acquiring the information is very long and tedious.
  • many steps must be performed on TIRKS.
  • the information provided by TIRKS is in a raw-data format, and must be manually complied into a tabular form to represent the desired information. For a typical SONET ring, this process takes between two to six hours.
  • What is desired is a system and method that allows a user to quickly determine the status of the SONET ring. This status can be related to such things as available bandwidth and other consumption-related items.
  • a system and method that can provide a great deal of information about a network to a user.
  • the information should be provided in a usable fashion, and should be responsive to user specific information for desired components of the network.
  • FIG. 1 is a simplified description of several typical SONET rings and a monitor system according to one or more embodiments of the present invention.
  • FIG. 2 illustrates a computer system for use with the monitoring system of FIG. 1 .
  • FIGS. 3-5 provide screen shots, such as from the computer system of FIG. 2 , that illustrate different embodiments of the present invention.
  • FIG. 6 is one embodiment of a simplified flow chart that illustrates one embodiment of a software program for implementing features of the present invention.
  • FIG. 7 is a simplified flow chart that illustrates another embodiment of a software program for implementing features of the present invention, including creating the screen shots of FIGS. 3-5 .
  • the present disclosure relates to monitoring systems, such as can be used in a synchronized optical network (“SONET”) ring.
  • SONET synchronized optical network
  • the following disclosure is divided into three different sections.
  • the exemplary network identifies two telecommunication networks that may benefit from the present invention, and the exemplary system provides an example of a system for providing a graphical user interface for monitoring either or both of the networks.
  • a plurality of screen shots are provided for illustrating the graphical user interface.
  • an exemplary software routine is discussed for implementing one embodiment of the graphical user interface.
  • the reference numerals 10 and 12 designate, in general, two simplified SONET rings.
  • the SONET rings 10 , 12 include a plurality of nodes 14 and a plurality of available bandwidth (generically described as links) 16 .
  • Some of the nodes exist in both rings 10 , 12 , and are therefore considered hubs. It is understood that there are various types of nodes, and that the present description is not limited to any particular type.
  • Any node 14 may be representative of a single component, a single facility, or a larger group of components and links.
  • each node includes a plurality of terminations where a service enters or exits the SONET ring 10 , 12 .
  • the nodes 14 are designated OC-48, and therefore each node has a potential of 48 “drop ports.” Also, it is understood that there are many types of links, with each link having various potentially available bandwidths.
  • a monitoring system 20 may be connected to one or more nodes of the networks 10 , 12 .
  • the monitoring system 20 includes a personal computer 21 with a graphics display 22 , a control unit 24 , and user inputs 26 such as a keyboard and pointer device.
  • the computer 21 is connected through a log-on connection 30 to a file server 32 , which also includes hardware components found in a typical server computer.
  • the file server 32 is further connected to an inventory system 34 , such as the TIRKS system discussed above. It is well known by those of ordinary skill in the art that various implementations can exist for the monitoring system 20 .
  • the monitoring system 20 may include a larger, mainframe-type computer that is either locally or remotely accessible by a terminal or personal computer.
  • the monitoring system 20 may include a series of computers.
  • the monitoring system may include or utilize a series of adjunct processors to one or more of the nodes 14 .
  • the monitoring system 20 can perform various software routines that can produce a series of graphical output images.
  • the images are arranged in a unique way to illustrate the status of the SONET ring 10 .
  • the images can locate a spare node from among the various nodes of the SONET ring 10 .
  • the images can identify usage patterns between two or more nodes.
  • the images can help identify spare bandwidths available.
  • the images are discussed and illustrated below by providing several screen shots, such as may appear on the graphics display 22 .
  • the following discussion is directed to a graphical user interface comprising several different images. Since the images are dynamic and interactive, screen shots of the images will be further discussed.
  • the screen shots relate to exemplary situations of a SONET ring, such as the network 10 or 12 of FIG. 1 , at a single moment in time. It is understood that different portions of the screen shots can be combined in various manners to produce even more examples of the graphical user interface.
  • a screen shot 100 can be used to illustrate a current condition of a SONET ring on the display of a monitoring system.
  • the screen 100 is divided into three main areas: a SONET ring area 102 , a link area 104 , and a node area 106 .
  • the main areas can be further divided, as necessary.
  • the node area 106 includes a node detail area 106 a.
  • a pictorial description of a SONET ring being monitored is displayed in a circular configuration 110 .
  • One benefit of the present embodiment is that many nodes and links can be simultaneously displayed. To illustrate this benefit, the SONET ring to be displayed will be larger than those illustrated in FIG. 1 , with many more nodes and links.
  • the ring configuration 110 includes eleven nodes N 1 -N 8 and N 10 -N 12 and a plurality of links L 1 -L 24 between the nodes for the SONET ring. (Note that node N 8 is connected to node N 10 . A node N 9 is skipped for future expansion).
  • the specific links L 1 -L 24 are chosen and highlighted by pull down menus 112 . In the present example, the configuration 110 illustrates the links L 1 -L 24 between each of the nodes N 1 -N 12 .
  • a legend 114 identifies that nodes N 2 , N 3 , N 4 , N 6 , N 7 , N 8 , N 11 , and N 12 are hubs.
  • the legend 114 also assigns specific colors to the various nodes and links to indicate a status for each. In FIGS. 3-5 , different colors are illustrated with different line styles or hatchings.
  • a first color 114 a indicates that a specific link or node is consumed.
  • a second color 114 b indicates that a specific link or node is available.
  • the nodes can have additional states, such as restricted 114 c , pending 114 d , and other 114 e .
  • a mismatch between two nodes can be quickly identified. For example, if one of the links between nodes N 2 and N 3 is inventoried differently in the two nodes, a mismatch would occur. As such, a status of each node and link can be immediately determined by a user's quick perusal of the ring configuration 110 .
  • the indicator 120 signifies that service on the corresponding link is dropping at that node. The link is therefore consuming one of the drop ports at the corresponding node. For example, there are 13 links dropping at node N 2 and 32 links dropping at node N 3 .
  • the links without the indicator 120 illustrate service that is passing through that node to another node. For example, at node N 3 , link L 4 passes straight through. Instead, link L 4 goes between (and consumes drop ports at) node N 2 and node N 4 .
  • the node N 1 has been “selected” for additional information.
  • the selection process can be performed by using the input devices 26 described above, with reference to FIG. 2 , or may be selected by the monitor system 20 .
  • link information for the selected node is provided in a series of columns: SYS Num, Direction, Usage, Detail, and Riding OC.
  • the column SYS Num provides a list of all the selected links from the pull-down menu 112 .
  • the columns Direction, Usage, and Detail provide directions east (E) or west (W) that identify the link and describe the service provided by the corresponding link.
  • the column Riding OC describes other systems riding on the corresponding drop ports.
  • the links L 1 -L 3 east and west are T 3 's.
  • T 3 's are synchronous digital carriers used to transmit a formatted digital signal at 45 Mb/s.
  • information for the selected node is provided in a series of columns: Mapped, HECI, Relay, Total, Spare, and Restricted.
  • Mapped, Relay, Total Spare, and Restricted columns describe the various drop ports associated with the node.
  • the HECI column identifies a human equipment common interface (HECI) value.
  • HECI value provides a summary of specific usage of a particular unit.
  • the HECI value can be provided in greater detail in the node detail area 106 a , when such information is available.
  • node N 1 is the selected node, but additional information may be desired for one of the non-selected nodes.
  • the pointer device 26 FIG. 2
  • the pointer device 26 is positioned over a node.
  • the pointer device 26 is positioned over node N 11 .
  • a window 122 appears with additional information for node N 11 .
  • the window 122 indicates that node N 11 is a central office identified as DLMRCA 12 , with a Relay value of 010131.14.
  • the relay has 19 working (W) drop ports, 1 restricted (X) drop port, and 4 spare (S) drop ports.
  • Node N 11 is also a hub node (reference number NSH61A), and may therefore connect to one or more additional networks.
  • a screen shot 130 illustrates bandwidth usage patterns in an interactive manner.
  • a pull-down menu 132 is used to select two nodes in a specific sequence, and a pull-down menu 134 is used to identify bandwidth usage.
  • the bandwidth usage patterns from node N 3 to node N 10 is illustrated.
  • links L 3 , L 5 , L 15 , and L 16 are highlighted as the available links between node N 3 and node N 10 .
  • the links are available because the drop ports 120 exist on the west side (W) of node N 3 and the east side (E) of node N 10 .
  • the pointer device 26 FIG. 2
  • the pointer device 26 can be positioned over the link.
  • the pointer device 26 is positioned over link L 3 .
  • a window 136 appears with additional information for link L 3 .
  • the window 136 indicates that link L 3 is a working T 3 connection between nodes N 3 and N 10 .
  • L 3 is a spare link between nodes N 6 and N 5 .
  • a screen shot 140 identifies spare links in an interactive manner.
  • a pull-down menu 142 is used to select all the links, and a pull-down menu 144 is used to identify a specific status of the links. For the sake of example, all of the spare links are to be identified.
  • the pointer device 26 can be positioned over the link.
  • the pointer device 26 is positioned over link L 13 .
  • a window 146 appears with additional information for link L 13 .
  • the window 146 indicates that link L 13 is a spare.
  • the screen shot 140 also illustrates how a user can select a specific link.
  • Pull-down menus 148 , 150 are used to identify the link, accordingly. For the sake of example, link L 13 is identified.
  • the link is in use between the node N 5 to N 3 , N 3 to N 0 , N 11 to N 8 , and N 8 to N 6 .
  • the link L 13 is available (spare) between nodes N 6 and N 5 .
  • the pointer device 26 can be positioned to identify more information about that link.
  • the pointer device 26 is positioned over link L 3 between nodes N 7 and N 6 .
  • a window 152 appears with additional information for link L 13 .
  • the window 152 indicates that link L 3 is a working T 3 link.
  • a computer program 180 can be used for visualizing and characterizing at least a portion of a SONET ring, such as the rings 10 , 12 of FIG. 1 .
  • Execution begins at step 182 , where one or more menus are provided from which a user may specify specific components of the SONET ring.
  • a graphical representation of the SONET ring illustrating each node and link of the SONET ring specified by the user is calculated and drawn.
  • a user selection for identifying one node of the SONET ring is received.
  • an inventory system such as TIRKS is accessed for data related to the user selection.
  • detailed information about the selected node is displayed.
  • FIG. 7 another software routine 200 can be implemented to visualize and characterize a portion of a SONET ring, such as the rings 10 , 12 of FIG. 1 .
  • the software routine 200 can provide the above described screen shots 100 , 130 , 140 of FIGS. 3-5 on the monitor system 20 .
  • Execution begins at step 202 where a first stage of user input is provided, such as the pull-down menus 112 , 132 - 134 , 142 - 144 , and 148 - 150 of FIG. 3-5 .
  • a user can select specific nodes for a specific size of display. It is understood that as more nodes and links are selected, the granularity of the information provided will also increase.
  • GUI graphical user interface
  • a visualization process (discussed in steps 204 - 214 , below) is a look-up and read process. This allows the user to quickly and easily determine the status of a SONET ring using one or more of the screen shots 100 , 130 , 140 discussed above.
  • a review process (discussed in steps 220 - 230 , below) is an automatically updated, periodic monitor of one or more SONET rings.
  • the visualization process begins at step 204 , where a user selection is received.
  • the user selection at this step of the process 200 is for determining the configuration for the SONET ring to be displayed.
  • a series of calculations and/or data queries are performed. Since the data queries often take a relatively long time (as compared to the calculations), these queries may be initiated first. For example, one or more queries can be implemented using TIRKS. The various nodes and links that have been specified are then queried and the information is returned.
  • the size and shape of the configuration for the SONET ring may be determined (e.g., ring configuration 110 of FIG. 3 ).
  • the SONET ring be configured in a circle, with evenly spaced nodes and links. Once the nodes and links are drawn, their color (or other aspect) is drawn according to the query results and a predetermined legend, such as the legend 114 of FIG. 3 , is provided.
  • a response is made to a selected link or node.
  • node N 1 is a default selection, but the user can select another node using the pointer device 26 .
  • execution proceeds to step 210 where additional information is provided for the selected node and corresponding links. In the examples of FIGS. 3-5 , this information is provided in the link area 104 and the node area 106 .
  • step 212 a response is made to a link or node identified using the pointer device 26 .
  • the identification of a link or node made at step 208 is different than that made at step 212 .
  • the link or node can be selected by “clicking” the pointer device or pressing an appropriated key on a keyboard.
  • step 212 the link or node is identified by merely positioning the pointer device over the corresponding component.
  • step 214 additional information is provided for the selected component. In the examples of FIGS. 3-5 , this information is provided in pop-up windows 122 , 136 , 146 , and 152 . Execution then returns to step 202 for additional user selection.
  • the review process begins at step 220 , where a series of calculations and/or data queries are performed. Since the data queries often take a relatively long time (as compared to the calculations), these queries may be initiated first. For example, one or more queries can be implemented using TIRKS. The various nodes and links that have been specified are then queried and the information is returned. Several calculations may be performed concurrently with the data queries.
  • a link exhaust calculation is made.
  • the link exhaust calculation is made by examining a usage trend (e.g., from the previous 12 months) and the amount of spare bandwidth (from the spare links), to predict when the network will be exhausted.
  • each link and node is reviewed, The review may consider the different technologies (e.g., OC-3, OC-12, TS3) of the components, as identified by a stored reference value (e.g., in the server 32 of the monitor system 20 ). Each technology can be detected and tracked, and exhaust conditions can be thereby determined. The information may then be presented to the user, such as through a demand and capacity (D&C) chart on the display 22 .
  • technologies e.g., OC-3, OC-12, TS3
  • a stored reference value e.g., in the server 32 of the monitor system 20 .
  • Each technology can be detected and tracked, and exhaust conditions can be thereby determined.
  • the information may then be presented to the user, such as through a demand and capacity (D&C) chart on the display 22 .
  • D&C demand and capacity
  • a predefined exhaust condition e.g., from 20% to 10% spare
  • the user can be notified in other manners.
  • the file server 32 can send an e-mail to the user notifying any upcoming exhaust conditions.
  • the review process may be performed on an automatic, cyclic basis. For example, the review process may be performed every week. To illustrate this process, the flow chart of FIG. 7 illustrates execution returns to step 220 . If an automatic process is not desired, execution returns to step 202 .
  • process 200 is illustrated in a top-down flow chart to provide a simple and clear description. In actuality, many steps may be performed simultaneously, and may actually be performed by different nodes and/or different components of the monitor system 20 and the SONET ring 10 . Such processing distribution is well known to those of ordinary skill in the art.
  • the system and method allow a user to quickly determine the status of the SONET ring. This status can be related to such things as available bandwidth and other consumption-related items.
  • the system may be interactive, and can quickly provide specific information without providing superfluous or unnecessary information to the user.
  • implementations of the various embodiments described above can be performed very quickly, as compared to conventional techniques, such as running a TIRKS online report facility.

Abstract

A computer-based monitoring system provides interactive topology information about a synchronized optical network (SONET). The monitoring system utilizes a trunks integrated record keeping system (TIRKS) connected to the SONET for collecting status data in a raw format. A computer system retrieves the raw format status data from TIRKS and provides the data in a simple graphical user interface to a user. The interface includes several menus from which the user may specify specific components of the SONET, and a graphical output for providing a graphical representation of the SONET. The graphical output illustrates each node and link and interactively provides more detailed information about any user selected link or node.

Description

    CROSS-REFERENCE
  • This application is a continuation of U.S. application Ser. No. 11/202,421, filed Aug. 11, 2005, which is a continuation of Ser. No. 09/675,628, filed Sep. 29, 2000, both of which are hereby incorporated by reference in their entirety.
  • BACKGROUND
  • The present invention relates generally to telecommunications and more particularly, to a system and method for monitoring telecommunication network activities.
  • It is often desired to monitor specific activities of various aspects of a telecommunication network. Traditionally, the monitoring has been hardware specific. For example, a monitoring system can show if a node or link in a network is up or down, and can set off alarms accordingly. Such monitoring works well with a realtime analysis of the hardware in the network.
  • However, it is often desired to monitor other aspects of the network. Consider for example a synchronized optical network (a “SONET”) ring or chain. SONET was proposed by Bellcore in the middle 1980s as a standard for connecting fiber-optic transmission systems. SONET defines interface standards at the physical layer, including a hierarchy of interface rates that allow data streams at different rates to be multiplexed. SONET establishes Optical Carrier (“OC”) levels, or speeds. Typical OC levels include OC-1 for 51.85 Mbps, OC-3 for 155.52 Mbps, OC-12 for 622.08 Mbps, OC-24 for 1.244 Gbps, OC-48 for 2.488 Gbps, and OC-192 for 9.9532 Gbps.
  • One way to track facility assignments and equipment inventory in a SONET ring or chain is to use a system called the Trunks Integrated Record Keeping System (“TIRKS”). TIRKS is commonly used to help a regional bell operating company (“RBOC”) determine if facilities exist to provide service, track order completion, fulfill circuit orders, and perform inventory planning.
  • Although TIRKS provides a great detail of information, the method of acquiring the information is very long and tedious. For example, in order to retrieve information such as consumption patterns of a SONET ring or chain, many steps must be performed on TIRKS. The information provided by TIRKS is in a raw-data format, and must be manually complied into a tabular form to represent the desired information. For a typical SONET ring, this process takes between two to six hours.
  • What is desired is a system and method that allows a user to quickly determine the status of the SONET ring. This status can be related to such things as available bandwidth and other consumption-related items.
  • Furthermore, what is desired is an interactive system and method for monitoring a network's status.
  • Further still, what is desired is a system and method that can provide a great deal of information about a network to a user. The information should be provided in a usable fashion, and should be responsive to user specific information for desired components of the network.
  • Furthermore, what is desired is a system and method for monitoring a network's status in a very fast manner, as compared to conventional techniques such as running a TIRKS online report facility.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a simplified description of several typical SONET rings and a monitor system according to one or more embodiments of the present invention.
  • FIG. 2 illustrates a computer system for use with the monitoring system of FIG. 1.
  • FIGS. 3-5 provide screen shots, such as from the computer system of FIG. 2, that illustrate different embodiments of the present invention.
  • FIG. 6 is one embodiment of a simplified flow chart that illustrates one embodiment of a software program for implementing features of the present invention.
  • FIG. 7 is a simplified flow chart that illustrates another embodiment of a software program for implementing features of the present invention, including creating the screen shots of FIGS. 3-5.
  • DETAILED DESCRIPTION
  • The present disclosure relates to monitoring systems, such as can be used in a synchronized optical network (“SONET”) ring. It is understood, however, that the following disclosure provides many different embodiments, or examples, for implementing different features of the invention. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to limit the invention from that described in the claims.
  • The following disclosure is divided into three different sections. First of all, an exemplary network and system is provided. The exemplary network identifies two telecommunication networks that may benefit from the present invention, and the exemplary system provides an example of a system for providing a graphical user interface for monitoring either or both of the networks. Secondly, a plurality of screen shots are provided for illustrating the graphical user interface. Thirdly, an exemplary software routine is discussed for implementing one embodiment of the graphical user interface.
  • Exemplary Network and System
  • Referring to FIG. 1, the reference numerals 10 and 12 designate, in general, two simplified SONET rings. The SONET rings 10, 12 include a plurality of nodes 14 and a plurality of available bandwidth (generically described as links) 16. Some of the nodes exist in both rings 10, 12, and are therefore considered hubs. It is understood that there are various types of nodes, and that the present description is not limited to any particular type. Any node 14 may be representative of a single component, a single facility, or a larger group of components and links. In the present example, each node includes a plurality of terminations where a service enters or exits the SONET ring 10, 12. In continuance of the example, the nodes 14 are designated OC-48, and therefore each node has a potential of 48 “drop ports.” Also, it is understood that there are many types of links, with each link having various potentially available bandwidths.
  • Referring also to FIG. 2, a monitoring system 20 may be connected to one or more nodes of the networks 10, 12. In one embodiment, the monitoring system 20 includes a personal computer 21 with a graphics display 22, a control unit 24, and user inputs 26 such as a keyboard and pointer device. The computer 21 is connected through a log-on connection 30 to a file server 32, which also includes hardware components found in a typical server computer. The file server 32 is further connected to an inventory system 34, such as the TIRKS system discussed above. It is well known by those of ordinary skill in the art that various implementations can exist for the monitoring system 20. For example, in some implementations, the monitoring system 20 may include a larger, mainframe-type computer that is either locally or remotely accessible by a terminal or personal computer. In other implementations, the monitoring system 20 may include a series of computers. In still other implementations, the monitoring system may include or utilize a series of adjunct processors to one or more of the nodes 14.
  • The monitoring system 20 can perform various software routines that can produce a series of graphical output images. The images are arranged in a unique way to illustrate the status of the SONET ring 10. For example, the images can locate a spare node from among the various nodes of the SONET ring 10. The images can identify usage patterns between two or more nodes. Furthermore, the images can help identify spare bandwidths available. The images are discussed and illustrated below by providing several screen shots, such as may appear on the graphics display 22.
  • Exemplary Screen Shots
  • The following discussion is directed to a graphical user interface comprising several different images. Since the images are dynamic and interactive, screen shots of the images will be further discussed. The screen shots relate to exemplary situations of a SONET ring, such as the network 10 or 12 of FIG. 1, at a single moment in time. It is understood that different portions of the screen shots can be combined in various manners to produce even more examples of the graphical user interface.
  • Referring also to FIG. 3, a screen shot 100 can be used to illustrate a current condition of a SONET ring on the display of a monitoring system. The screen 100 is divided into three main areas: a SONET ring area 102, a link area 104, and a node area 106. The main areas can be further divided, as necessary. For example, in the screen 100, the node area 106 includes a node detail area 106 a.
  • Referring to the SONET ring area 102, a pictorial description of a SONET ring being monitored is displayed in a circular configuration 110. One benefit of the present embodiment is that many nodes and links can be simultaneously displayed. To illustrate this benefit, the SONET ring to be displayed will be larger than those illustrated in FIG. 1, with many more nodes and links.
  • The ring configuration 110 includes eleven nodes N1-N8 and N10-N12 and a plurality of links L1-L24 between the nodes for the SONET ring. (Note that node N8 is connected to node N10. A node N9 is skipped for future expansion). The specific links L1-L24 are chosen and highlighted by pull down menus 112. In the present example, the configuration 110 illustrates the links L1-L24 between each of the nodes N1-N12.
  • Several of the nodes N1-N8 and N10-N12 serve as hubs. In the present example, a legend 114 identifies that nodes N2, N3, N4, N6, N7, N8, N11, and N12 are hubs. The legend 114 also assigns specific colors to the various nodes and links to indicate a status for each. In FIGS. 3-5, different colors are illustrated with different line styles or hatchings. A first color 114 a indicates that a specific link or node is consumed. A second color 114 b indicates that a specific link or node is available. The nodes can have additional states, such as restricted 114 c, pending 114 d, and other 114 e. In addition, a mismatch between two nodes can be quickly identified. For example, if one of the links between nodes N2 and N3 is inventoried differently in the two nodes, a mismatch would occur. As such, a status of each node and link can be immediately determined by a user's quick perusal of the ring configuration 110.
  • On several links there is an indicator 120. The indicator signifies that service on the corresponding link is dropping at that node. The link is therefore consuming one of the drop ports at the corresponding node. For example, there are 13 links dropping at node N2 and 32 links dropping at node N3. The links without the indicator 120 illustrate service that is passing through that node to another node. For example, at node N3, link L4 passes straight through. Instead, link L4 goes between (and consumes drop ports at) node N2 and node N4.
  • In addition to the information provided in the SONET ring area 102, more detailed information can be provided for a specific node. In the example illustrated in FIG. 3, the node N1 has been “selected” for additional information. The selection process can be performed by using the input devices 26 described above, with reference to FIG. 2, or may be selected by the monitor system 20.
  • Referring to the link area 104, link information for the selected node is provided in a series of columns: SYS Num, Direction, Usage, Detail, and Riding OC. The column SYS Num provides a list of all the selected links from the pull-down menu 112. The columns Direction, Usage, and Detail provide directions east (E) or west (W) that identify the link and describe the service provided by the corresponding link. The column Riding OC describes other systems riding on the corresponding drop ports. For example, the links L1-L3 east and west are T3's. T3's are synchronous digital carriers used to transmit a formatted digital signal at 45 Mb/s.
  • Referring to the node area 106, information for the selected node is provided in a series of columns: Mapped, HECI, Relay, Total, Spare, and Restricted. The Mapped, Relay, Total Spare, and Restricted columns describe the various drop ports associated with the node. The HECI column identifies a human equipment common interface (HECI) value. The HECI value provides a summary of specific usage of a particular unit. The HECI value can be provided in greater detail in the node detail area 106 a, when such information is available.
  • As discussed above, in the present example, node N1 is the selected node, but additional information may be desired for one of the non-selected nodes. To find the additional information, the pointer device 26 (FIG. 2) is positioned over a node. In the present example, the pointer device 26 is positioned over node N11. As a result, a window 122 appears with additional information for node N11. In the example shown in FIG. 3, the window 122 indicates that node N11 is a central office identified as DLMRCA 12, with a Relay value of 010131.14. The relay has 19 working (W) drop ports, 1 restricted (X) drop port, and 4 spare (S) drop ports. Node N11 is also a hub node (reference number NSH61A), and may therefore connect to one or more additional networks.
  • Referring now to FIG. 4, a screen shot 130 illustrates bandwidth usage patterns in an interactive manner. A pull-down menu 132 is used to select two nodes in a specific sequence, and a pull-down menu 134 is used to identify bandwidth usage. For the sake of example, the bandwidth usage patterns from node N3 to node N10 is illustrated.
  • In this example, links L3, L5, L15, and L16 are highlighted as the available links between node N3 and node N10. The links are available because the drop ports 120 exist on the west side (W) of node N3 and the east side (E) of node N10. To find additional information about a particular link, the pointer device 26 (FIG. 2) can be positioned over the link. In the present example, the pointer device 26 is positioned over link L3. As a result, a window 136 appears with additional information for link L3. In the example shown in FIG. 4, the window 136 indicates that link L3 is a working T3 connection between nodes N3 and N10. It is noted that as illustrated in FIG. 4, L3 is a spare link between nodes N6 and N5.
  • Referring now to FIG. 5, a screen shot 140 identifies spare links in an interactive manner. A pull-down menu 142 is used to select all the links, and a pull-down menu 144 is used to identify a specific status of the links. For the sake of example, all of the spare links are to be identified.
  • In this example, many links between various nodes are identified. The identified links are spares because there are no drop ports on either side. To find additional information about a particular link, the pointer device 26 (FIG. 2) can be positioned over the link. In the present example, the pointer device 26 is positioned over link L13. As a result, a window 146 appears with additional information for link L13. In the example shown in FIG. 4, the window 146 indicates that link L13 is a spare.
  • The screen shot 140 also illustrates how a user can select a specific link. Pull-down menus 148, 150 are used to identify the link, accordingly. For the sake of example, link L13 is identified.
  • In this example, the link is in use between the node N5 to N3, N3 to N0, N11 to N8, and N8 to N6. The link L13 is available (spare) between nodes N6 and N5. In addition to the color scheme provided, the pointer device 26 can be positioned to identify more information about that link. In the present example, the pointer device 26 is positioned over link L3 between nodes N7 and N6. As a result, a window 152 appears with additional information for link L13. In the example shown in FIG. 4, the window 152 indicates that link L3 is a working T3 link.
  • Software Description
  • Referring now to FIG. 6, a computer program 180 can be used for visualizing and characterizing at least a portion of a SONET ring, such as the rings 10, 12 of FIG. 1. Execution begins at step 182, where one or more menus are provided from which a user may specify specific components of the SONET ring. At step 184, a graphical representation of the SONET ring illustrating each node and link of the SONET ring specified by the user is calculated and drawn. At step 186, a user selection for identifying one node of the SONET ring is received. At step 188, an inventory system such as TIRKS is accessed for data related to the user selection. At step 190, detailed information about the selected node is displayed.
  • Referring now to FIG. 7, another software routine 200 can be implemented to visualize and characterize a portion of a SONET ring, such as the rings 10, 12 of FIG. 1. The software routine 200 can provide the above described screen shots 100, 130, 140 of FIGS. 3-5 on the monitor system 20. Execution begins at step 202 where a first stage of user input is provided, such as the pull-down menus 112, 132-134, 142-144, and 148-150 of FIG. 3-5. In this way, a user can select specific nodes for a specific size of display. It is understood that as more nodes and links are selected, the granularity of the information provided will also increase. It is further understood that generic aspects of a graphical user interface (GUI), such as pull-down menus, are well understood by those of ordinary skill in the art.
  • At step 203, the user can choose between two different operations of the routine 200. A visualization process (discussed in steps 204-214, below) is a look-up and read process. This allows the user to quickly and easily determine the status of a SONET ring using one or more of the screen shots 100, 130, 140 discussed above. A review process (discussed in steps 220-230, below) is an automatically updated, periodic monitor of one or more SONET rings.
  • The visualization process begins at step 204, where a user selection is received. The user selection at this step of the process 200 is for determining the configuration for the SONET ring to be displayed.
  • At step 206, a series of calculations and/or data queries are performed. Since the data queries often take a relatively long time (as compared to the calculations), these queries may be initiated first. For example, one or more queries can be implemented using TIRKS. The various nodes and links that have been specified are then queried and the information is returned.
  • Several calculations may be performed concurrently with the data queries. For example, the size and shape of the configuration for the SONET ring may be determined (e.g., ring configuration 110 of FIG. 3). In the embodiments of FIGS. 3-5, it is desired that the SONET ring be configured in a circle, with evenly spaced nodes and links. Once the nodes and links are drawn, their color (or other aspect) is drawn according to the query results and a predetermined legend, such as the legend 114 of FIG. 3, is provided.
  • At step 208, a response is made to a selected link or node. In the examples of FIGS. 3-5, node N1 is a default selection, but the user can select another node using the pointer device 26. Once selected, execution proceeds to step 210 where additional information is provided for the selected node and corresponding links. In the examples of FIGS. 3-5, this information is provided in the link area 104 and the node area 106.
  • Upon completion of steps 208-210 (or prior to their completion), execution proceeds to step 212 where a response is made to a link or node identified using the pointer device 26. In the present embodiment, the identification of a link or node made at step 208 is different than that made at step 212. For example, in step 208, the link or node can be selected by “clicking” the pointer device or pressing an appropriated key on a keyboard. In step 212, the link or node is identified by merely positioning the pointer device over the corresponding component. Once identified, execution proceeds to step 214 where additional information is provided for the selected component. In the examples of FIGS. 3-5, this information is provided in pop-up windows 122, 136, 146, and 152. Execution then returns to step 202 for additional user selection.
  • The review process begins at step 220, where a series of calculations and/or data queries are performed. Since the data queries often take a relatively long time (as compared to the calculations), these queries may be initiated first. For example, one or more queries can be implemented using TIRKS. The various nodes and links that have been specified are then queried and the information is returned. Several calculations may be performed concurrently with the data queries.
  • At step 222, a link exhaust calculation is made. The link exhaust calculation is made by examining a usage trend (e.g., from the previous 12 months) and the amount of spare bandwidth (from the spare links), to predict when the network will be exhausted.
  • At step 224, each link and node is reviewed, The review may consider the different technologies (e.g., OC-3, OC-12, TS3) of the components, as identified by a stored reference value (e.g., in the server 32 of the monitor system 20). Each technology can be detected and tracked, and exhaust conditions can be thereby determined. The information may then be presented to the user, such as through a demand and capacity (D&C) chart on the display 22.
  • At step 226, a determination is made as to whether the user has modified any preset values. For example, the user may modify a technology type for a component, may change a predefined exhaust condition (e.g., from 20% to 10% spare), and so forth. If the user does make modifications, execution returns to step 220.
  • At step 228, the user can be notified in other manners. For example, the file server 32 can send an e-mail to the user notifying any upcoming exhaust conditions.
  • At step 230, the review process may be performed on an automatic, cyclic basis. For example, the review process may be performed every week. To illustrate this process, the flow chart of FIG. 7 illustrates execution returns to step 220. If an automatic process is not desired, execution returns to step 202.
  • It is understood that the process 200 is illustrated in a top-down flow chart to provide a simple and clear description. In actuality, many steps may be performed simultaneously, and may actually be performed by different nodes and/or different components of the monitor system 20 and the SONET ring 10. Such processing distribution is well known to those of ordinary skill in the art.
  • CONCLUSION
  • Thus, there is disclosed a system and method for providing interactive topology graphs for visualization and characterization of SONET consumption patterns. In some embodiments, the system and method allow a user to quickly determine the status of the SONET ring. This status can be related to such things as available bandwidth and other consumption-related items. The system may be interactive, and can quickly provide specific information without providing superfluous or unnecessary information to the user. In addition, implementations of the various embodiments described above can be performed very quickly, as compared to conventional techniques, such as running a TIRKS online report facility.
  • While the invention has been particularly shown and described with reference to the preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing form the spirit and scope of the invention.

Claims (2)

1. An apparatus for visualizing at least a portion of a telecommunications network, the apparatus comprising a display, a processor for executing computer program instructions, and a computer program comprising instructions for:
providing one or more menus on the display from which a user may specify specific components of the telecommunications network;
calculating and drawing a graphical representation of the telecommunications network illustrating each node and link of the telecommunications network specified by the user;
receiving a user selection for identifying one node of the telecommunications network;
accessing an inventory system for data related to the user selection; and
providing the display with more detailed information about the selected node.
2. A method for visualizing at least a portion of a telecommunications network, the method comprising:
providing one or more menus on a computer display from which a user may specify specific components of the telecommunications network;
calculating and drawing a graphical representation of the telecommunications network illustrating each node and link of the telecommunications network specified by the user;
receiving a user selection for identifying one node of the telecommunications network;
accessing an inventory system for data related to the user selection; and
providing the computer display with more detailed information about the selected node.
US12/349,333 2000-09-29 2009-01-06 Interactive Topology Graphs for Visualization and Characterization of Sonet Consumption Patterns Abandoned US20090116409A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/349,333 US20090116409A1 (en) 2000-09-29 2009-01-06 Interactive Topology Graphs for Visualization and Characterization of Sonet Consumption Patterns

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09/675,628 US6981228B1 (en) 2000-09-29 2000-09-29 Interactive topology graphs for visualization and characterization of SONET consumption patterns
US11/202,421 US7475364B2 (en) 2000-09-29 2005-08-11 Interactive topology graphs for visualization and characterization of SONET consumption patterns
US12/349,333 US20090116409A1 (en) 2000-09-29 2009-01-06 Interactive Topology Graphs for Visualization and Characterization of Sonet Consumption Patterns

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/202,421 Continuation US7475364B2 (en) 2000-09-29 2005-08-11 Interactive topology graphs for visualization and characterization of SONET consumption patterns

Publications (1)

Publication Number Publication Date
US20090116409A1 true US20090116409A1 (en) 2009-05-07

Family

ID=35482809

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/675,628 Expired - Fee Related US6981228B1 (en) 2000-09-29 2000-09-29 Interactive topology graphs for visualization and characterization of SONET consumption patterns
US11/202,421 Expired - Fee Related US7475364B2 (en) 2000-09-29 2005-08-11 Interactive topology graphs for visualization and characterization of SONET consumption patterns
US12/349,333 Abandoned US20090116409A1 (en) 2000-09-29 2009-01-06 Interactive Topology Graphs for Visualization and Characterization of Sonet Consumption Patterns

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US09/675,628 Expired - Fee Related US6981228B1 (en) 2000-09-29 2000-09-29 Interactive topology graphs for visualization and characterization of SONET consumption patterns
US11/202,421 Expired - Fee Related US7475364B2 (en) 2000-09-29 2005-08-11 Interactive topology graphs for visualization and characterization of SONET consumption patterns

Country Status (1)

Country Link
US (3) US6981228B1 (en)

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7310666B2 (en) * 2001-06-29 2007-12-18 International Business Machines Corporation Method and system for restricting and enhancing topology displays for multi-customer logical networks within a network management system
US7013232B2 (en) * 2001-08-15 2006-03-14 National Insurance Corporation Network-based system for configuring a measurement system using configuration information generated based on a user specification
US7149975B1 (en) * 2001-12-26 2006-12-12 Nortel Networks Limited Optical network administration graphical user interface
US20050125517A1 (en) * 2002-04-04 2005-06-09 Joakim Norrgard Method for creating a map of available resources within an ip network
US7917854B1 (en) * 2002-10-28 2011-03-29 Nortel Networks Limited Telecommunications network administration graphical user interface
US7447161B2 (en) * 2002-12-18 2008-11-04 Atct Intellectual Property I, L.P System and method for enhanced SONET network analysis
US8051389B2 (en) * 2003-08-26 2011-11-01 Hewlett-Packard Development Company, L.P. Methods of displaying resources of overlapping but separate hierarchies
US20050049910A1 (en) * 2003-08-28 2005-03-03 Cemer Innovation, Inc. System and method for management interface for clinical environments
US20050060193A1 (en) * 2003-08-28 2005-03-17 Lancaster Brian J. System and method for evidence-based modeling of clinical operations
US7865375B2 (en) * 2003-08-28 2011-01-04 Cerner Innovation, Inc. System and method for multidimensional extension of database information using inferred groupings
EP1510940A1 (en) 2003-08-29 2005-03-02 Sap Ag A method of providing a visualisation graph on a computer and a computer for providing a visualisation graph
EP1510938B1 (en) * 2003-08-29 2014-06-18 Sap Ag A method of providing a visualisation graph on a computer and a computer for providing a visualisation graph
EP1510939A1 (en) * 2003-08-29 2005-03-02 Sap Ag A method of providing a visualisation graph on a computer and a computer for providing a visualisation graph
EP1510941A1 (en) * 2003-08-29 2005-03-02 Sap Ag A method of providing a visualisation graph on a computer and a computer for providing a visualisation graph
US7284165B2 (en) * 2004-06-15 2007-10-16 International Business Machines Corporation Computer generated documentation including diagram of computer system
USD609714S1 (en) * 2007-03-22 2010-02-09 Fujifilm Corporation Electronic camera
WO2009123562A1 (en) * 2008-04-01 2009-10-08 Nanyang Polytechnic Proactive wireless network management system
CN102014403B (en) * 2009-09-07 2014-12-10 中兴通讯股份有限公司 Method and system for transmitting network topology information
US9083560B2 (en) * 2010-04-01 2015-07-14 Microsoft Technologies Licensing, Llc. Interactive visualization to enhance automated fault diagnosis in networks
US9397898B2 (en) * 2012-06-29 2016-07-19 Infinera Corporation Digital link viewer
US9420359B2 (en) * 2013-02-22 2016-08-16 Nec Corporation Dynamic wavelength virtualization and/or on-demand flow provisioning in optical networks
USD749131S1 (en) * 2014-01-05 2016-02-09 Makerbot Industries, Llc Display screen with an icon
CN103942132B (en) * 2014-03-26 2017-05-24 广州杰赛科技股份有限公司 Method and device for adding goal node to data acquisition unit
US20160124695A1 (en) * 2014-11-05 2016-05-05 Ciena Corporation Network visualization system and method
US11507262B2 (en) * 2017-02-22 2022-11-22 Ciena Corporation Methods and systems for managing optical network services including capacity mining and scheduling
USD926787S1 (en) * 2019-05-14 2021-08-03 Doosan Machine Tools Co., Ltd. Display screen with graphical user interface for machine tool

Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5295244A (en) * 1990-09-17 1994-03-15 Cabletron Systems, Inc. Network management system using interconnected hierarchies to represent different network dimensions in multiple display views
US5412652A (en) * 1993-09-24 1995-05-02 Nec America, Inc. Sonet ring subnetwork management method
US5542047A (en) * 1991-04-23 1996-07-30 Texas Instruments Incorporated Distributed network monitoring system for monitoring node and link status
US5621383A (en) * 1993-06-11 1997-04-15 Nec Corporation Ring network system capable of detecting an alarm in each node
US5715432A (en) * 1995-04-04 1998-02-03 U S West Technologies, Inc. Method and system for developing network analysis and modeling with graphical objects
US5751965A (en) * 1996-03-21 1998-05-12 Cabletron System, Inc. Network connection status monitor and display
US5761429A (en) * 1995-06-02 1998-06-02 Dsc Communications Corporation Network controller for monitoring the status of a network
US5768552A (en) * 1990-09-28 1998-06-16 Silicon Graphics, Inc. Graphical representation of computer network topology and activity
US5774669A (en) * 1995-07-28 1998-06-30 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Scalable hierarchical network management system for displaying network information in three dimensions
US5867484A (en) * 1997-01-31 1999-02-02 Intellect Network Technologies Switchable multi-drop video distribution system
US5870558A (en) * 1996-06-25 1999-02-09 Mciworldcom, Inc. Intranet graphical user interface for SONET network management
US5909217A (en) * 1997-09-30 1999-06-01 International Business Machines Corporation Large scale system status map
US5910803A (en) * 1996-08-14 1999-06-08 Novell, Inc. Network atlas mapping tool
USRE36444E (en) * 1990-12-10 1999-12-14 International Business Machines Corporation Selecting and locating graphical icon objects to define and configure the workstations in data processing networks
US6031528A (en) * 1996-11-25 2000-02-29 Intel Corporation User based graphical computer network diagnostic tool
US6040834A (en) * 1996-12-31 2000-03-21 Cisco Technology, Inc. Customizable user interface for network navigation and management
US6058103A (en) * 1996-02-22 2000-05-02 Mci Communications Corporation Network management system
US6067093A (en) * 1996-08-14 2000-05-23 Novell, Inc. Method and apparatus for organizing objects of a network map
US6295540B1 (en) * 1997-10-02 2001-09-25 Nortel Networks Limited Alignment of tirks using network manager
US6330005B1 (en) * 1996-02-23 2001-12-11 Visionael Corporation Communication protocol binding in a computer system for designing networks
US6577327B1 (en) * 1999-09-15 2003-06-10 Nortel Networks Limited System, method and graphical user interface for building virtual private networks
US6735215B1 (en) * 2000-03-11 2004-05-11 Lucent Technologies Inc. Apparatus and method for automatic port identity discovery in heterogenous systems
US6772204B1 (en) * 1996-02-20 2004-08-03 Hewlett-Packard Development Company, L.P. Method and apparatus of providing a configuration script that uses connection rules to produce a configuration file or map for configuring a network device
US6959000B1 (en) * 2000-02-08 2005-10-25 Lucent Technologies Inc. Configuration management of a hybrid DCS-SONET ring network
US6992975B1 (en) * 2000-08-15 2006-01-31 Cisco Technology, Inc. Multiple ring support within a single network element
US7173936B1 (en) * 2000-09-11 2007-02-06 Ciena Corporation Method and apparatus for partitioning SONET frames into logical channels to optimize bandwidth utilization

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2784080B2 (en) * 1990-05-09 1998-08-06 富士通株式会社 Ring network, fault recovery method therefor, and node used in ring network
US5210762A (en) * 1991-10-02 1993-05-11 Alcatel Network Systems, Inc. Sonet pointer interpretation system and method
US5744669A (en) * 1992-11-25 1998-04-28 Uop Process for the conversion of a halogenated organic stream containing trace quantities of organic nitrates
US5355238A (en) * 1993-08-18 1994-10-11 Swl Inc. Method and apparatus for the monitoring and demarcation of synchronous optical networks
US6163544A (en) * 1995-12-08 2000-12-19 Telefonaktiebolaget Lm Ericsson Configuration method for auxiliary resources
WO1997022190A1 (en) * 1995-12-13 1997-06-19 British Telecommunications Public Limited Company Meshed optical network
US5808920A (en) * 1996-03-19 1998-09-15 Digital Lightwave, Inc. Communications line test apparatus with an improved graphical user interface
DE69738175T2 (en) * 1996-08-27 2008-01-31 Nippon Telegraph And Telephone Corp. Link transmission network
US5909175A (en) * 1997-02-28 1999-06-01 Fujitsu Limited Connection switching circuit for ring system
EP1005740B1 (en) * 1997-06-27 2006-02-22 Tellabs Denmark A/S A method of transmitting data in a ring-shaped teletransmission network, such as a network and a network element therefor
US6130876A (en) * 1997-09-24 2000-10-10 At&T Corp Method and apparatus for restoring a network
US6396852B1 (en) * 1997-11-18 2002-05-28 Jane Marie Simmons Ring bundling in the design of rings for telecommunications networks
US6278689B1 (en) * 1998-04-22 2001-08-21 At&T Corp. Optical cross-connect restoration technique
GB2350030B (en) * 1999-05-10 2001-06-13 3Com Corp Network mamagement apparatus and method

Patent Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5295244A (en) * 1990-09-17 1994-03-15 Cabletron Systems, Inc. Network management system using interconnected hierarchies to represent different network dimensions in multiple display views
US5768552A (en) * 1990-09-28 1998-06-16 Silicon Graphics, Inc. Graphical representation of computer network topology and activity
USRE36444E (en) * 1990-12-10 1999-12-14 International Business Machines Corporation Selecting and locating graphical icon objects to define and configure the workstations in data processing networks
US5542047A (en) * 1991-04-23 1996-07-30 Texas Instruments Incorporated Distributed network monitoring system for monitoring node and link status
US5621383A (en) * 1993-06-11 1997-04-15 Nec Corporation Ring network system capable of detecting an alarm in each node
US5412652A (en) * 1993-09-24 1995-05-02 Nec America, Inc. Sonet ring subnetwork management method
US5715432A (en) * 1995-04-04 1998-02-03 U S West Technologies, Inc. Method and system for developing network analysis and modeling with graphical objects
US5761429A (en) * 1995-06-02 1998-06-02 Dsc Communications Corporation Network controller for monitoring the status of a network
US5774669A (en) * 1995-07-28 1998-06-30 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Scalable hierarchical network management system for displaying network information in three dimensions
US6772204B1 (en) * 1996-02-20 2004-08-03 Hewlett-Packard Development Company, L.P. Method and apparatus of providing a configuration script that uses connection rules to produce a configuration file or map for configuring a network device
US6058103A (en) * 1996-02-22 2000-05-02 Mci Communications Corporation Network management system
US6330005B1 (en) * 1996-02-23 2001-12-11 Visionael Corporation Communication protocol binding in a computer system for designing networks
US5751965A (en) * 1996-03-21 1998-05-12 Cabletron System, Inc. Network connection status monitor and display
US5870558A (en) * 1996-06-25 1999-02-09 Mciworldcom, Inc. Intranet graphical user interface for SONET network management
US5910803A (en) * 1996-08-14 1999-06-08 Novell, Inc. Network atlas mapping tool
US6067093A (en) * 1996-08-14 2000-05-23 Novell, Inc. Method and apparatus for organizing objects of a network map
US6031528A (en) * 1996-11-25 2000-02-29 Intel Corporation User based graphical computer network diagnostic tool
US6040834A (en) * 1996-12-31 2000-03-21 Cisco Technology, Inc. Customizable user interface for network navigation and management
US5867484A (en) * 1997-01-31 1999-02-02 Intellect Network Technologies Switchable multi-drop video distribution system
US5909217A (en) * 1997-09-30 1999-06-01 International Business Machines Corporation Large scale system status map
US6295540B1 (en) * 1997-10-02 2001-09-25 Nortel Networks Limited Alignment of tirks using network manager
US6577327B1 (en) * 1999-09-15 2003-06-10 Nortel Networks Limited System, method and graphical user interface for building virtual private networks
US6959000B1 (en) * 2000-02-08 2005-10-25 Lucent Technologies Inc. Configuration management of a hybrid DCS-SONET ring network
US6735215B1 (en) * 2000-03-11 2004-05-11 Lucent Technologies Inc. Apparatus and method for automatic port identity discovery in heterogenous systems
US6992975B1 (en) * 2000-08-15 2006-01-31 Cisco Technology, Inc. Multiple ring support within a single network element
US7173936B1 (en) * 2000-09-11 2007-02-06 Ciena Corporation Method and apparatus for partitioning SONET frames into logical channels to optimize bandwidth utilization

Also Published As

Publication number Publication date
US7475364B2 (en) 2009-01-06
US6981228B1 (en) 2005-12-27
US20060080611A1 (en) 2006-04-13

Similar Documents

Publication Publication Date Title
US7475364B2 (en) Interactive topology graphs for visualization and characterization of SONET consumption patterns
US5771274A (en) Topology-based fault analysis in telecommunications networks
US5946373A (en) Topology-based fault analysis in telecommunications networks
US7596716B2 (en) Method and system for managing networks
US7149975B1 (en) Optical network administration graphical user interface
US6434514B1 (en) Rule based capacity management system for an inter office facility
US6957263B2 (en) Connection management system and graphical user interface for large-scale optical networks
US6718384B2 (en) System and method for monitoring and maintaining a communication network
EP0920752B1 (en) Telecommunications network management observation and response system
US7047496B2 (en) Method for visualization of optical network topology
JP4531215B2 (en) Method and apparatus for displaying information to user and computer program product
US20050091356A1 (en) Method and machine-readable medium for using matrices to automatically analyze network events and objects
US20030112958A1 (en) Overlay view method and system for representing network topology
US20080117068A1 (en) Intelligent Network Alarm Status Monitoring
US6950865B1 (en) Network audit tool
US20100138750A1 (en) Presenting network performance data in the context of a map of path model objects
CN108650140B (en) Automatic auxiliary analysis method and system for service fault of optical transmission equipment
US7424030B2 (en) Method, system and storage medium for providing a cross connect user interface
US7124368B1 (en) System and method for displaying usage information in a data network
US7167483B1 (en) System and method for managing subrate services in an optical network
US7107496B1 (en) Method, apparatus, computer-readable media and user interface for annunciating problems in a system
US6906734B2 (en) Method, system and storage medium for displaying communication network connections
US20050229113A1 (en) Highlighted objects window
US7447161B2 (en) System and method for enhanced SONET network analysis
KR100301293B1 (en) A searching method of transmitting data for optical communication system

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION