Highlighted objects window

Field of the invention

0001The invention is directed to management of communication networks and in particular to a highlighted object window for a network management graphical user interface.

Background of the Invention

0002Due to recent explosive technological development and the ensuing growing size of the communication networks, the network management became a very complex task. Numerous factors contribute to this growing complexity. For example, modern communication networks use heterogeneous equipment provided by different vendors and/or use a multitude of data communication technologies and protocols, a multitude of network management and service provisioning protocols, etc. In addition, the topology of the network is changing at a fast pace. Not only new network elements (NE) are added, removed, moved or replaced with newer versions, but they are also more geographically dispersed. In many cases, the customers wish to divide their network into different regions based on political or business boundaries; quite frequently two or more regions overlap, presenting a challenge given the current engineering limits. All these changes cause significant technological challenges to the nature of network management.

0003In a network management system, each managed node is defined by a plurality of "variables". A management station or the operator can monitor the nodes by examining (reading) the values of these variables, and can control the nodes by remotely changing (writing) the values of these variables. Network information is usually presented in the form of network maps which show graphic symbols (icons) of the NEs on a video display screen of a video display terminal on a workstation. This is called a graphical user interface, or GUI. Each window of the GUI provides the user with the ability to manipulate the information of interest utilizing a mouse, or the like. This user action causes the GUI to process the request by performing the respective action or displaying a map of another hierarchical level.

0004It is important that the information displayed by the GUI clearly identifies the network entities for which information is being presented. It is also important for the GUI to provide the user with the ability to select additional information about a particular network entity and to present the information in a clear and well organized display. Finally, displays of network information should be flexible to accommodate differing network configurations and differing network management requirements.

0005The networks dynamics causes significant technological challenges to the way in which information is presented to a user. As generally the scale of a communications network is too large and too complex to display all objects of the respective network in a single network map window, the network is divided into hierarchical layers of network object groups, which are shown in separate windows, ranging from upper layer maps of hundreds of network nodes, to lower layer maps of network elements at a certain selected node. This same information can also be represented in a complex tree of objects.

0006As the number of network layers increases, it becomes a time consuming job for the user to search through many windows since this involves clicking symbols in a window to open the respective sub-layer map and then clicking on the respective sub-layer map symbols, etc. The complexity of finding the correct object in a tree view representation is equally high. In many cases, this operation could also fail, as it is not easy to follow correctly the hierarchical layers conducting to the desired end result. In practice, a customer evaluates the efficiency of a GUI in terms of the number of mouse clicks it takes an operator to perform a certain function.

0007Some network managers (such as Alcatel's 5620 NM) enable customers to highlight objects displayed on a map or a list. The highlighting changes the background color of an object(s), and is used to trace a specific object through a managed system. However, the operator needs to trace an object through different layers of the object hierarchy, so that after performing the highlight function, the operator would still have to navigate through each layer of the hierarchy, one layer at a time.

0008Although an attempt to drastically reduce the number of hierarchical layers is impractical because it necessitates overall reconfiguration of the network object containment, it is the usual practice to merge two or more windows by transferring symbols from a lower layer to an upper layer. However, deletion and re-registration of the transferred symbols are necessary. In addition, current network display systems do not allow lower layer maps to be displayed within an upper layer window.

0009There is a need to provide a faster, automated way to obtain information on a highlighted chain of objects in a network.

Summary of the Invention

0010It is an object of the present invention to provide a GUI of a communication network with a highlighted objects window that enables fast access through many layers of hierarchical objects of a network.

0011The invention provides a method of displaying highlighted objects information on a graphical user interface (GUI) comprising: a) highlighting a primary object <i>O(n)</i> displayed on a GUI window at a selected hierarchically level (n); b) identifying a highlighted object <i>O(n-1)</i> subtended by the primary object at a hierarchically next lower level <i>(n-1);</i> c) selecting the highlighted object <i>O(n-1)</i> from an object storage means and placing same in a list of highlighted objects; and d) repeating steps b) and c) for all <i>n</i> available hierarchical levels until all highlighted objects corresponding to the primary object are identified and placed in said list.

0012According to a further aspect, the invention further provides a highlighted objects window system for a graphical user interface (GUI) of the type provided with highlighting capabilities and adapted to transmit commands and display information with a view to enable management of a communication network. The system comprises means for identifying all highlighted objects in a highlighted hierarchy corresponding to a primary object highlighted on the GUI; and means for selecting only the highlighted objects from an object storage means and placing the objects in a list, the GUI displaying the list in a highlighted objects window where the highlighted objects are arranged in a specified order.

0013Still further, the invention provides a method of using a graphical user interface (GUI) of the type provided with highlighting capabilities and adapted to transmit commands and display information with a view to enable management of a communication network, comprising: a) highlighting an original object on a topological map at a selected hierarchically level; b) identifying all highlighted objects corresponding to the original object in all hierarchical levels subtended from the selected hierarchically level; c) selecting all the highlighted objects from an object storage means and placing same in a list in their hierarchical order of identification; and d) displaying the list as a highlighted objects window for obtaining information of interest about the primary object.

0014Advantageously, use of the highlighted objects window according to the invention, results in important reduction of the amount of time it takes a user to navigate through the chain of hierarchical objects to obtain the relevant information for the managed objects of interest. In other words, the present solution results in a reduced number of "point and click" operations required for obtaining the information of interest.

0015Still another advantage of the invention resides in the ability of the GUI to display the list of objects in the highlight hierarchy, as well as additional information relevant to each object, such as the object type, status, specification, name, etc.

Brief Description of the drawings

0016The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of the preferred embodiments, as illustrated in the appended drawings, where: <ul id="ul0001" list-style="none" compact="compact"><li><b>Figure 1</b> shows an example of a network map with a highlighted object;</li><li><b>Figure 2</b> shows the highlighted objects window corresponding to the example of Figure 1;</li><li><b>Figure 3a</b> is a block diagram of the units that enable generation of the highlighted object window according to the invention; and</li><li><b>Figure 3b</b> illustrates how a highlighted objects window list is generated for the example of Figures 1 and 2.</li></ul>

Detailed Description

0017Figure 1 shows an example of a very simple network management map <b>10</b>, illustrating a first node <b>ND1</b>, housing a first network device, a second node <b>ND2</b>, housing a second network device, and a link <b>20</b> between the two network devices. Let's assume that the operator wishes to find the ports on the respective devices that are the ends of link <b>20</b>. According to the invention, the operator only has to click and highlight link <b>20</b> to obtain a list of all objects involved in this connection.

0018Figure 2 shows a highlighted objects window <b>30</b> for the example of Figure 1, which displays a list <b>30'</b> of the objects in the highlight heirarchy. This example has been simplified for clarity, as normally a link will have multiple nodes along the way, each with the respecive shelves, slots, cards, ports, etc. Also, each node could be in a group that could be inside another group, inside another group, etc. In this simplified example, window <b>30</b> displays a list <b>30'</b> showing the group the nodes <b>ND1</b> and <b>ND2</b> reside in (ON1 in this example), the first node <b>ND1</b> and the first network device <b>ND-1 P2</b> at node <b>ND1</b>. The icons of the respective network elements such as group icon <b>31</b>, node icon <b>32</b> and network device icon <b>33</b> are provided in this example in the first column, and the object specification (node identification) in the second column. The object names are also specified in list <b>30'</b>. In this example, the network device <b>ND-1 P2</b> resides in an "Ontario Group", at an "Ottawa Node" and is called "Ottawa Node P2".

0019The next rows show the objects contained in first network device from the top to bottom of the hierarchy. In this example they are shelf <b>ND1-P2-1</b> identified by icon <b>34,</b> card <b>ND1-P2-1-1</b> identified by icon <b>35</b> and port <b>ND1-P2-1-1-3</b> identified by icon <b>36.</b> For a general case, if we denote the hierarchical level of the map of interest (highest level, original map <b>10</b>) with <i>n</i> and the objects highlighted on this map with <i>O(n)</i>, the lower hierarchy objects are denoted with <i>O(n-1), O(n-2)</i> and <i>O(n-3)</i>, while the respective levels are denoted with <i>(n-1), (n-2)</i> and respectively <i>(n-3)</i>.

0020Link <b>20</b> is listed next, and is shown using icon <b>37.</b> The object specification for this highlighted object indicates the bandwidth of the link "OC48" and the object name gives in this example the direction "Toronto-Ottawa" for the connection over this link.

0021The next rows (not shown) list the highlighted objects at the second node <b>ND2</b>, namely the objects relevant to the connection over link <b>20</b> at a second network device <b>ND-2P2</b>. These are preferably shown hierarchically from bottom to the top so that the end ports of the link <b>20</b> appear in the list above and below the row with the link object. Let's assume that these are port <b>ND2-P2-1-1-1</b>, card <b>ND2-P2-1-2</b>, shelf <b>ND2-P2-1</b>. Toronto end network device <b>ND2-P2</b>, and node <b>ND2</b> end the list of highlighted objects. If <b>ND2</b> belongs to a node group, this is also shown in list <b>30'</b>.

0022Icons <b>31-37</b> in the leftmost column quickly identify the object type and status. The colour of the icon indicates its status, therefore locating an alarmed object (e.g. coloured red) in the list is fast.

0023Additional columns, such as a status column shown in Figure 2, may also be provided depending on the level of information available at the resepective node. Still further, list <b>30'</b> may include a column with the count of all the objects in the highlighted hierarchy. As all the managed objects of the hierarchically lower layers are shown on the list, the amount of time it takes a user to navigate through the highlight chain and evaluate each iobject is greatly reduced. In addition, GUI <b>40</b> enables the operator to select objects in the list <b>30'</b> for viewing further details if necessary and available.

0024List <b>30'</b> can be sorted by the highlight hierarchy or by any of the displayed columns. Window <b>30</b> may also be provided with a refresh button (not shown) for enabling the operator to update list <b>30'</b> of highlighted objects. Double clicking on a row (line) item in the list provides access to that item.

0025Figure 3a show a high-level block diagram of the main units involved in generating the highlighted objects window according to the invention. It is to be noted that this figure illustrates only the units at the node relevant to this invention, for simplicity. GUI <b>40</b> performs conventional user interface functions enabling an operator to monitor and manage the network as well known. For the example used in this specification, GUI <b>40</b> provides an operator with a map (or tree) of interest, here map <b>10</b>, that is displayed on the screen of workstation <b>5</b>, as well known. In addition, GUI <b>40</b> enables the operator to highlight objects displayed in the window. In this example, the operator clicks on link <b>20</b> to highlight it.

0026The object highlighted on map <b>10</b>, here link <b>20</b>, and all objects of interest subtended by this primary highlighted object are identified by identifier block <b>25</b> based on the GUI <b>40</b> object highlight capability. An object list selector <b>45</b> accesses the respective objects and object specification information relevant to all the objects identified by unit <b>25</b>. Once the information pertinent to the highlighted objects is collected, GUI <b>40</b> generates list <b>30'</b> that is displayed on the screen <b>5</b>.

0027It is to be mentioned that the location or the way the object specification information is stored at the node is not relevant to the invention; relevant is only availability of this information. In general, all nodes maintain an object library <b>50</b> that comprises data pertinent to all network elements at the respective node, available for use by various network management applications. The place where object data is stored is called herein generically "object specification storage" and is denoted with <b>50</b>. The information about the ports used by a specified connection is also available at the node, shown generically in Figure 3a by connectivity database <b>55</b>; if this information is not readily available, it may be imported from the routing database.

0028Figure 3b shows how list <b>30'</b> of highlighted objects is generated for the example of Figures 1 and 2. It is to be noted that this Figure does not illustrate the objects at the device, node and node group level for simplification. To reiterate, the highlighted objects window <b>30</b> provides a list of all the objects that are highlighted in a certain window presented by the GUI, from all the layers of the object hierarchy. The objects are arranged in the list in a specified order, as described above.

0029First, the operator clicks on link <b>20</b> to highlight it, as shown by arrow <b>a</b>. The highlighted objects identifier <b>25</b> (see Figure 3a) identifies the objects on map <b>10</b> pertinent to the operator's request. Then, the object list selector <b>45</b> (see Figure 3a) collects hierarchically the highlighted object data from the object storage <b>15</b> that includes generically the pertinent databases with the objects specifications and connectivity data, by first locating the highlighted node group, node and network device information and placing it in list <b>30'</b> (not shown).

0030Next, the highlighted shelf <b>ND1-P2-1</b> is identified in shelf domain <b>51</b> corresponding to the first network device, as shown by arrow <b>b.</b> Shelf <b>ND1-P2-1</b> is placed in list <b>30'</b> together with the relevant information in the respective columns. Then, objects list selector <b>45</b> searches domain <b>52</b> of cards subtended by this shelf to locate the highlighted card <b>ND1-P2-1-1,</b> as shown by arrow <b>c.</b> Card <b>ND1-P2-1-1</b> and the relevant information are now placed in the next row of the list <b>30',</b> and the respective columns of the list are completed with the relevant information. Arrow <b>d</b> shows how the port information is located by searching the domain <b>53</b> of ports available on card <b>ND1-P2-1-1.</b> The object selector identifies highlighted port <b>ND1-P2-1-1-3</b> and places it in list <b>30'.</b>

0031<b>[00031]</b> Link <b>20</b> data is searched next, arrow <b>e,</b> in routing domain <b>54</b> as it provides the connection between the port-3/card-1/shelf-1 /node-P2/ND1 and port -1 at the Toronto end. This information is also provided to the GUI for insertion in list 30'.

0032[00032] Next, highlighted objects identifier <b>25</b> identifies the objects at the second end of link <b>20</b> for completing list <b>30'</b>. As described above, the respective object storage unit <b>15</b> at the second node maintains the data pertinent to network device <b>ND2-P5</b> at the Toronto node <b>ND2.</b> For this example, these are port <b>ND2-P5-1-1-1</b> in domain <b>53'</b> with the ports of card <b>ND2-P5-1-2,</b> card <b>ND2-P5-1-2</b> from the domain <b>52'</b> with the cards of shelf <b>ND2-P5-1</b>and shelf <b>ND2-P5-1</b> from the domain <b>51'</b> with the shelves of the second network device <b>ND2.</b> The last items on list <b>30'</b> are the second network device <b>ND-2P2</b> and the second node <b>ND2.</b> As before, arrows <b>f, g, h</b> and <b>i</b> indicate how the collection of the data proceeds at network device ND2.