JP3641247B2 - Communication path setting method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a communication path setting method implemented using a display screen of an operator terminal device used in an information transmission system such as an optical submarine cable system.
[0002]
[Prior art]
Generally, a transmission system is provided with a node that transmits communication data and a monitoring and control device that provides an OAM (Operations, Administration and Maintenance) service to a communication network. In addition to this, in recent years, a terminal device (hereinafter referred to as a worker terminal device) that can be carried and can easily perform processing such as simple setting and maintenance of nodes has been increasingly provided.
[0003]
By the way, in recent years, the number of devices constituting the network has increased due to the worldwide expansion of the network, and accordingly, the number of monitoring control objects (nodes, etc.) has increased. For this reason, not only the monitoring and control apparatus but also the operator terminal apparatus is complicated and sophisticated, and the burden on the operator is increased.
[0004]
[Problems to be solved by the invention]
As described above, in recent transmission systems, the operation and the sophistication of the monitoring control device and the worker terminal device are becoming increasingly complicated, and it is desired to provide some kind of solution.
[0005]
The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a communication path setting method capable of improving a human machine interface and improving operational convenience.
[0006]
[Means for Solving the Problems]
In order to achieve the above object, a communication path setting method according to the present invention includes a plurality of ring networks each having a plurality of nodes connected in a ring shape via a communication line on which a plurality of communication paths are multiplexed. A communication path setting method using a worker terminal device provided with a display device provided in a network system, wherein the display device is associated with a section between nodes in a ring network to which a node to which the device is connected belongs. A preparation step for dividing the screen into a plurality of areas and displaying arrows associated with communication paths existing in the section in the divided areas, and a low-speed channel of a node serving as a starting point of the communication path to be set And a second step for designating the low-speed channel of the node that is the end point of the communication path to be set. A third step of displaying an arrow associated with the communication path to be set in a display area corresponding to the node section specified in the first and second steps, and a communication path to be set elsewhere If there is, the fourth step of repeating the first to third steps and the communication path setting request corresponding to the arrow associated with the communication path to be set are related to the formation of the communication path. And a sixth step of sending a communication path setting request to a node that has received the communication path setting request, and forming a new communication path based on the request. In this way, since the path setting operation can be intuitively performed using the display screen of the operator terminal device, the user interface is improved and the convenience for the user can be improved.
[0007]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram of a transmission system in which a worker terminal device according to an embodiment of the present invention is installed. In FIG. 1, a plurality of nodes (NODE) 1-1 to 1-n are respectively installed in a plurality of stations ST-1 to ST-m. The nodes 1-1 to 1-n are connected to each other in a ring shape via the high-speed line OL, thereby forming a plurality of ring networks. That is, there are n ring networks, and each ring network is formed with m nodes 1-1, 1-2,.
[0008]
The high-speed line OL is realized as a synchronous multiplex line having a transmission capacity of, for example, STM-64 (equivalent to Synchronous Transfer Module-level 64: 10 Gbps) class. The high-speed line OL forming individual ring networks transmits optical signals. The wavelengths of the optical signals are different for each ring network, and the optical signals of these wavelengths are wavelength-multiplexed to form the wavelength multiplexing line FL.
[0009]
Nodes 1-1 to 1-n in each station ST-1 to ST-m are connected to an in-station monitoring and control device (SSE) 2 in each station. The SSE 2 is further connected to a supervisory control device (U-NME) 3 responsible for supervisory control over the entire area of the network via the LAN. A router 4 is connected to the LAN, and a supervisory control line ML is formed through the router 4 to connect the U-NMEs 3 of the respective stations. Note that the supervisory control line ML shown in FIG. 1 is displayed for convenience, and logically, a DCC (Data) provided in the SOH (Section Over Head) of the SDH frame transmitted through the wavelength division multiplexing line FL. Communication Channel).
[0010]
In addition, the system includes an operator terminal device (hereinafter referred to as Terminal) 5 according to the present invention. Terminal 5 is used by connecting to arbitrary nodes 1-1 to 1-n. In FIG. 1, it is connected to NODE 1-n of ST-2. For example, Terminal 5 is often used for assisting the startup of individual NODEs, and may be removed after the purpose has been achieved. It can also be attached as necessary for various settings and information acquisition, and the operation is simple. In short, Terminal 5 is positioned as a simple or general monitoring and control device.
[0011]
Terminal 5 sets the ring network to which the connected node belongs as a monitoring control target. In FIG. 1, the ring network stretched between the NODEs 1-n is the target of control. In this respect, it is distinguished from U-NME 3 that covers the entire network system.
[0012]
FIG. 2 is a block diagram showing the configuration of Terminal 5 according to the present invention. Terminal 5 includes a memory module 31, a processor module 32, a bridge 33, a SCSI (squeegee) controller 34, an HD (hard disk drive) 35, a graphic controller 37, an interface controller 38, a bus controller 39, an FDD (floppy disk drive) 310, an interface ( I / F) 311, display interface (I / F) 312, external interface (I / F) 313 serving as a connection interface with NODE 1 (1-1 to 1 -n), display 315, input devices such as a keyboard and a mouse 319, a sound controller 320, a buzzer interface (I / F) 321, and a buzzer 322.
[0013]
Of these, the human machine interface unit comprising the display 315, the keyboard / mouse 319, the buzzer 322, etc. is largely related to the idea of the present invention.
[0014]
Each function described below is newly implemented, for example, by applying a patch to a control program executed mainly by the processor module 32. This control program is written in a dedicated language and stored in the memory module 31, HD 35, or the like.
[0015]
In the following description, for the sake of convenience, it is assumed that the entire system includes 32 ring networks and that each ring network includes 7 NODEs. That is, it corresponds to n = 32 and m = 7 in FIG.
[0016]
(Network Alarm Summary Display)
FIG. 3 is a diagram showing a main screen of the display 315 of the Terminal 5. This screen is displayed when Terminal 5 is started up, and is a window called “Network Alarm Summary Display”. Various other windows are displayed on the display 315, and the window shown in FIG. 3 is displayed on the background of the various windows.
[0017]
In the window of FIG. 3, a schematic diagram of the ring network targeted by Terminal 5 is graphically displayed. In the figure, # 0 to # 6 indicate station icons corresponding to other NODE1-n belonging to the same ring network as NODE1-n to which Terminal 5 is connected. Here, a system with seven NODEs is shown. A double line connecting the stations # 0 to # 6 is a transmission line icon indicating a high-speed line having the same wavelength. The active transmission line (SRV) is indicated by a thick line, and the standby transmission line (PRT) is indicated by a thin line.
[0018]
Here, it is assumed that a failure has occurred in the transmission path on both sides (East (W) and West (W)) of station # 6. Terminal 5 obtains predetermined management information from the connected NODE 1-n and grasps that fact. At this time, on the screen, a transmission line icon corresponding to the transmission line in which the failure has occurred is displayed in a different display color depending on the degree of the failure. For example, if the fault is severe, it is displayed in red, and if it is medium, it is displayed in yellow. Further, transmission lines without trouble and stations # 0 to # 6 are displayed in green, for example.
[0019]
The menu bar at the top of the screen has clickable various function buttons. From left to right, Terminal button, Alarm button, Log button, Performance button, Path button, Protection button, Security button, System button, Node-Other button, Display button, Help button. When these buttons are clicked, a submenu as shown in FIGS. 4 to 6 is displayed, and various function windows are opened from there.
[0020]
Next, the operation of the above configuration will be described. In the following description, for the sake of convenience, the following nine are provided: <Node Alarm Summary>, <Notification>, <Alarm>, <Log>, <Protection>, <Security>, <System>, <Node-Other>, <Display>. A chapter is provided.
[0021]
<Node Alarm Summary>
When one of the station icons is clicked on the screen of FIG. 3, a Node Alarm Summary Display window that displays the status of failure occurrence in the NODE of FIG. 7 is opened. The window shown in FIG. 7 schematically shows the shelf configuration of the NODE selected in FIG. In this figure, the configuration of NODE # 0 is displayed. Each rectangle indicating each shelf is clickable. For example, when FAN is clicked, the window shown in FIG. 8 is opened. The window in FIG. 8 is referred to as a Shelf Alarm Summary Display window, and this window shows the card (board) configuration of the clicked shelf.
[0022]
By the way, in FIG. 7, the display color of the COM shelf is different from the others (in the figure, the shaded line: actually, for example, it is displayed in red), indicating that a failure has occurred in this shelf. Therefore, when the COM shelf in FIG. 7 is clicked, the Shelf Alarm Summary Display window in FIG. 9 is displayed. In the window of FIG. 9, a card having a failure in the COM shelf is displayed in a different display color. Here it can be seen that the Q INF card is faulty.
[0023]
In the window of FIG. 7, a rectangle indicating MAINT (Maintenance) is displayed. This is not a click button, but shows the maintenance status of the displayed NODE in different colors. If it is not under maintenance, for example, it is displayed in gray, but if the NODE is in a maintenance state, this is for example light blue. In FIG. 7, the color of the shelf on which the maintenance work (card exchange or the like) is being performed is distinguished from the others, and the details of the work are displayed in the lower column of the window.
[0024]
Terminal 5 knows whether each NODE is in a maintenance state or not from a notification from each NODE. The display form as shown in FIG. 7 allows the user to know the NODE maintenance state in detail.
[0025]
Each of the windows in FIGS. 7 to 9 is provided with a column indicating a list of alarm occurrence statuses in text format. The operator can obtain detailed information regarding the alarm by referring to this column. 7 to 9, the state is described in the scroll window for each item such as Card (board), Probable Cause (predicted cause), and Perceived Severity (degree of failure).
[0026]
<Notification>
The Notification Display window shown in FIG. 10 will be described.
[0027]
This Notification Display window is opened when Terminal 5 is launched. This Notification Display window may be minimized when opened by default. Further, the Notification Display window is opened so as to overlap the Network Alarm Summary Display which is the main screen when the maximization operation is performed on the window. With the setting described later, the Notification Display window can be automatically displayed (popped up) when notification information arrives from NODE.
[0028]
This Notification Display window displays a list of quality information such as notification information and performance data acquired by Terminal 5 from its connection destination NODE (here, NODE 1-n in ST-2 in FIG. 1) in a text format. Is.
[0029]
The Notification Display window shown in FIG. 10 includes a Detail button, a Mark1 / Mark2 button, a Row button and a Column button as Item Selection, a Properties button as a Window Control, an ACO (Alarm Cut Off) button, and a scroll window. Yes.
[0030]
(Scroll window)
In the scroll window, the acquired notification information is displayed in time series, for example, arranged from the top in the order of occurrence. The scroll window displays notification information attributes such as Time / Date, Event Type, Shelf (Object Class), and Card (Object Class). In addition, although hidden in FIG. 10, there are more attribute items on the right side of Card (Object Class). This can be displayed in the window by operating the horizontal scroll button. In the Time / Date column, the event occurrence date and time is shown. The Event Type field shows the type of event. In the Shelf (Object Class) column and the Card (Object Class) column, a shelf and a card in which an event has occurred are shown, respectively.
[0031]
After arbitrary information displayed in the scroll window of FIG. 10 is selected (when selected, the display is highlighted: indicated by hatching in the figure), and when the Detail button at the upper left of the window is clicked, FIGS. A Notification Detailed Display window such as 18 is displayed. These windows show the detailed contents of the selected information.
[0032]
Some events have a very large amount of information and cannot be displayed in a row in the scroll window of FIG. Therefore, in this embodiment, windows as shown in FIGS. 16 to 18 are provided to display details of information in an easy-to-understand manner. 17 shows information related to State Change, and FIG. 18 shows information related to Protection Switch Reporting. Both are events with a large amount of information. As shown in FIG. 18, these windows can be scrolled vertically.
[0033]
(Mark1 / Mark2 button)
When arbitrary information displayed in the scroll window of FIG. 10 is selected and the Mark1 / Mark2 button is clicked, the selected information can be marked. Regardless of how the window is scrolled, the Mark 1 / Mark 2 button can be clicked again to return to the marked information.
[0034]
By doing so, the search operation of the operator becomes easy especially when the number of notified information is large. By providing two mark buttons, it is possible to deal with two pieces of information, and it is also possible to clear a mark by providing a clear (Clr) button.
[0035]
(ACO button)
When an ACO (Alarm Cut Off) button is clicked in the window of FIG. 10, the Alarm Cut Off window of FIG. 11 is displayed. The window of FIG. 11 is a window for stopping the operation of the in-station alarm notified by a lamp, a bell sound, or the like. In the system of this embodiment, when a failure is detected by NODE, an alarm (not shown) provided in the station is operated to notify the operator, but Exec (execution) is executed in the window of FIG. When the) is clicked, the operation of the alarm can be stopped.
[0036]
(Item Selection)
There is a button shown as Item Selection in the window of FIG. That is, the Row button and the Column button. When the Row button is clicked, the Item Selection (Row) window shown in FIG. 12 is displayed. The window shown in FIG. 12 is for performing a narrowing search (filtering) in the scroll window shown in FIG. 10. When the OK button is clicked after arbitrarily checking the check box for each item, the window returns to the FIG. 10 window again. Only the narrowed contents are displayed. Clicking the Cancel button cancels the setting.
[0037]
When the Column button is clicked in FIG. 10, the Item Selection (Column) window in FIG. 13 is displayed. This window is for changing the display order in the scroll window shown in FIG. 10 (sorting). As setting items, (Common Item), (Alarm), (State Change), (Protection Switch Rep), (Security Alarm) ) Above each item, there is a button for setting the priority as Location. When this button is clicked, the display order can be set as shown. The items displayed in the scroll window of FIG. 10 are displayed in order from the left according to the priority set here.
[0038]
(Window Control)
When the Properties button is clicked in FIG. 10, the Notification Display Window Control window in FIG. 14 is displayed. This window is a window for setting processing when new notification information is received. For each item, either the On or Off radio button is checked.
[0039]
When Window Auto Open On is checked in the window of FIG. 14, the window of FIG. 10 is automatically displayed (popped up) when new notification information is received. When On of the Terminal is checked, when new notification information is received, the buzzer 332 (FIG. 2) is sounded to alert the operator. When Renewal On is checked, the screen is automatically scrolled to display the latest notification information in the scroll window of FIG. 10 when new notification information is received. If Renewal Off is checked, the scroll state does not change even when new notification information is received.
[0040]
When Clear Display of notifications is clicked in the window of FIG. 14, the display of the scroll window of FIG. 10 is cleared. Prior to this, the CAUTION window shown in FIG. 15 is opened, and a message indicating that the window is to be cleared is displayed to alert the operator. Even if the display is cleared, the data stored in the database of Terminal 5 is saved as it is.
[0041]
Since the window shown in FIG. 10 described above is the core of processing using Terminal 5, it is convenient to display it by default when the apparatus is started up. For example, the display can be switched to the main screen of FIG. 3 by one touch, or a dedicated icon (not shown) is provided in the main screen, and the window of FIG. 10 is opened by clicking this icon. May be.
[0042]
<Alarm>
Next, operations related to Alarm will be described. As for the Alarm relationship, as shown in FIG. 4, submenus of Alarm Severity Control, Maintenance Control, and SD Threshold Control are prepared.
[0043]
(Alarm Severity Control)
First, the Alarm Severity Control window shown in FIG. 19 will be described. This window is opened when Alarm Severity Control is clicked from the submenu (shown in FIG. 4) displayed when Alarm is clicked on the main screen of FIG.
[0044]
When the Node / Category / Probable Cause button is clicked in the window of FIG. 19, the Node / Category / Probable Cause Selection window of FIG. 20 is displayed. In this window, select any NODE (within the ring network to which the connected NODE belongs), and the importance or urgency of the alarm information notified from the NODE to Terminal 5 (own device) for each alarm type Is set to
[0045]
When the Node button is clicked in FIG. 20, the Node Selection window in FIG. 21 is opened. In this window, NODE to be operated is selected. In the present embodiment, since seven NODEs exist in one ring network as shown in FIG. 3, a user's desired NODE is selected from these seven NODEs. When any NODE is selected, the screen display returns to FIG.
[0046]
In the example of FIG. 21, up to 16 NODEs can be displayed. However, if there is no problem on the system or the performance of the terminal 5, more numbers may be displayed.
[0047]
In the window of FIG. 20, when the Read button is clicked after each item (Category, LS Channel Operation Mode) to be operated is selected, the current setting state of the selected NODE is read. Then, the screen display returns to FIG. 19, and the item selected in FIG. 20 is reflected in the display contents of FIG. The read result is displayed line by line in a scroll window written as (Assignment Profile Perceived Severity) in FIG.
[0048]
When one row is selected in FIG. 19 and the level of warning (Critical Major Minor Warning Non-Alarmed: the risk level increases from the left) is set in the Perceived Severity column, the operation target is clicked when the Set button is clicked. The contents of the setting in FIG. 19 are set for NODE. Information such as whether the set has been completed normally (OK) or not completed normally (NG) is displayed in the Console column.
[0049]
In this way, it is possible to arbitrarily set the urgency level of an alarm sent from each node from the Terminal 5 side. As a result, the following becomes possible. For example, when an NODE operation test, installation work, or card exchange work is performed, a large amount of various alarms are generated on the NODE side. When all these alarms are notified to the U-NME 3, communication resources are consumed to notify the alarms, which may adversely affect system operation. This is particularly noticeable for AIS (Alarm Indication Signal).
[0050]
Therefore, by setting the urgency level arbitrarily for each type of alarm using the above function, it is possible to perform settings such as issuing a minimum necessary alarm during the test. As a result, convenience in system operation can be achieved. Also, by arbitrarily setting the urgency level of the alarm, it is possible to perform color coding on the screen according to the urgency level.
[0051]
(Maintenance Control)
The Maintenance Control window shown in FIG. 22 will be described. This window is opened when Maintenance Control is clicked from the submenu shown in FIG. The window of FIG. 22 is used to change the operation mode of the target NODE. NODE has an operation mode of either Maintenance (maintenance mode) or Not Maintenance (non-maintenance mode). In the window of FIG. 22, for example, a target node is selected by the same procedure as that of FIG. After that, when one of Maintenance / Not Maintenance is checked and the Exec button is clicked, the setting contents are notified to the target NODE.
[0052]
(Maintenance Signal Insertion Control)
The Maintenance Signal Insertion Control window shown in FIG. 23 will be described. This window is opened when Maintenance Signal Insertion Control is clicked from the submenu shown in FIG.
In the window of FIG. 23, an arbitrary node is designated, and permission or non-permission of transmission of an alarm signal (Maintenance Signal) related to maintenance is set for the designated node. An example of the maintenance signal is the AIS described above.
[0053]
When the Node button is clicked in the window of FIG. 23, the NODE Selection window of FIG. 24 is opened. After the target node is selected in the window of FIG. 24, the Read button is clicked. Then, the current setting contents for the selected node are read and displayed in the scroll window of FIG.
[0054]
An arbitrary item (channel) is clicked and selected in the scroll window. Then, the Maintenance Signal Insertion Setting window of FIG. 25 is opened, and either Allow (permitted) or Inhibit (non-permitted) is selected for each Operation Mode (SRV, PRT, P / T). When the Set button is clicked, the screen display returns to the window shown in FIG. In this way, each channel is set.
[0055]
After completing the setting for each item in the window of FIG. 23, when Modify is clicked, the set content is notified to the target node, and the set content is set. The node that has received the notification transmits a maintenance signal in accordance with the above setting contents.
[0056]
(SD Threshold Control)
The SD Threshold Control window shown in FIG. 26 will be described. This window is opened when SD Threshold Control is clicked from the submenu shown in FIG. The window shown in FIG. 26 is used to set a threshold value when an SD (Signal Degrade) alarm is issued, among alarm information.
[0057]
When Node is clicked in the window of FIG. 26, the NODE Selection window of FIG. 24 is opened. A target node is selected in the window of FIG. 24, and “Read” is clicked to read the current setting contents, and the contents are displayed in the scroll window of FIG.
[0058]
When an arbitrary channel is clicked in the scroll window of FIG. 26, the SD Threshold Setting window of FIG. 27 is opened, and a threshold is selected for each selected operation mode (SRV, PRT, P / T) for the selected channel. The When Modify in FIG. 26 is clicked after the setting of each item is completed, each setting content is notified to the target node, and the setting content is set in the notified node.
[0059]
<Log>
Next, operations related to Log will be described. As for the log relationship, as shown in FIG. 4, sub menus of NODE Log Control, NODE Record Retrieval, and Terminal Access Record Retrieval are prepared.
[0060]
(NODE Log Control)
The NODE Log Control window shown in FIG. 28 will be described. This window is opened when NODE Log Control is clicked in the submenu (shown in FIG. 4) that is opened when Log is clicked on the main screen of FIG. The window of FIG. 28 is a window related to the operation of the log stored in the NODE database of the terminal 5 connection partner.
[0061]
As shown in FIG. 28, the NODE database stores a log having items of Alarm, Object Creation / Deletion, State Change, Protection Control, and Security Alarm. Each of these items is an event detected on the NODE side, and its history is stored in each NODE itself, and is databased as a history (the same contents are sent as notification information to SSE2 or U-NME3, and SSE2 Or it is accumulated as a log in the database of U-NME3).
[0062]
In the window of FIG. 28, the maximum log size for each item is set. When the Read button is clicked in the window of FIG. 28, the current setting contents are read from the NODE of the connection partner and displayed in FIG. The setting items in the window of FIG. 28 include Max Log Size (maximum log size in storage resource: unit Kbyte) and Number of Records (maximum number of logs in storage resource). After these items are set by numerical values, when the Set button is clicked, the setting contents are set in the destination NODE.
[0063]
By default, an equal log size is assigned to each of Alarm to Security Alarm, for example. On the other hand, by performing the above operation, for example, a setting can be made such that the maximum log size is assigned according to the occurrence frequency of each item. For example, Creation / Deletion events are less likely to occur than other events, so the allocation log size is reduced. Instead, you can reserve more sizes for more frequent Alarm events. By doing so, there is an advantage that storage resources in NODE can be effectively utilized.
[0064]
As the log is accumulated, data that exceeds the maximum log size is overwritten (Wrap mode) by default, and is erased in order from the oldest. Since logs are cyclically overwritten as time passes, all accumulated logs are erased when the log size is changed. Therefore, a warning window is displayed when the Set button in FIG. 28 is clicked. FIG. 29 shows an example of a warning window. This window displays “All log records will be deleted. Click the OK button if you want, or click the Cancel button to cancel.”
[0065]
(NODE Record Retrieval)
The NODE Record Retrieval window shown in FIG. 30 will be described. This window is opened when NODE Record Retrieval is clicked from the submenu shown in FIG. This window is a window for setting conditions for retrieving desired data from the log recorded in the database.
[0066]
In the window of FIG. 30, one of Alarm, Object Creation / Deletion, State Change, Protection Control, and Security Alarm (not shown) is selected as the Node Record Retrieval Type. Either All (no time is specified) or Time (time is specified) is specified in the Condition column. When Time is specified, the time in the range of (Start) to (End) is specified in Event Time (Start / End). When the Read button is clicked after each item is specified in the window of FIG. 30, the search result is displayed in the (Alarm) Record Retrieval Report window of FIG.
[0067]
In the window of FIG. 31, the notification retrieved from the history in relation to the selected Record Type (in FIG. 31, Alarm is shown in the window title. This title varies depending on the selected Record Type). A list of information is displayed in text form in a scroll window. The window of FIG. 31 is different from the window of FIG. 10 in that the search result of the notification information accumulated as a history in the database is displayed. The acquired notification information is displayed in real time in the window of FIG. 10, whereas the search result from the data log is displayed in the window of FIG.
[0068]
Also in the window of FIG. 31, a mark can be attached to arbitrary information displayed in the scroll window by using the Mark1 / Mark2 button as in FIG. And from anywhere in the scroll window, clicking the Mark1 / Mark2 button allows you to return to the marked information. The clear (Clr) button is the same as in FIG. FIG. 32 shows a display example of search results related to Protection Control.
[0069]
(Terminal Access Record Retrieval)
The Terminal Access Record Retrieval window shown in FIG. 33 will be described. This window is opened when Terminal Access Record Retrieval is clicked from the submenu shown in FIG. This window is a window for setting conditions for searching for data related to the access log from Terminal 5 among logs stored in NODE.
[0070]
In the window of FIG. 33, for example, when the search condition is specified and the Read button is clicked in the same manner as in FIG. 30, the search result is displayed in the Terminal Access Record Retrieval Report window of FIG. The login user name is displayed in the Login Name of the scroll window, and the operation content of the login user is displayed in the Function.
[0071]
<Performance>
Next, the performance-related operation will be described. As for the performance relationship, as shown in FIG. 4, a sub menu of Performance Data Record Retrieval and Quality of Service Alarm Control is prepared.
[0072]
(Performance Data Record Retrieval)
The Performance Data Record Retrieval window shown in FIG. 35 will be described. This window is opened when Performance Data Record Retrieval is clicked in the submenu (shown in FIG. 4) that is opened when Performance is clicked on the main screen of FIG. This window is used to retrieve the quality log from the NODE database of the connection partner.
[0073]
In the window of FIG. 35, items of the channel of the counterpart NODE and Operation Mode are specified. In the Channel item, the channels of the high-speed lines (HS W (West) and HS E (East)) and the channels of the low-speed lines (LS1 to LS32) accommodated by the NODE are specified. In the Operation Mode item, SRV (service channel: active system), PRT (protection channel: standby system), and P / T (part time system) transmission path types are specified. These items are selected in a drop-down list.
[0074]
When the Read button is clicked in the window of FIG. 35, the current state of the selected target is retrieved from the NODE database, and a list of the results is displayed in the Performance Data Record Retrieval Report (Graph) window of FIG. The In this window, the functions of the Mark1 / Mark2 button and the clear (Clr) button can be used.
[0075]
(Quality of Service Alarm Control)
The Quality of Service Alarm Control window shown in FIG. 37 will be described. This window is opened when Quality of Service Alarm Control is clicked from the submenu shown in FIG. In the system according to the present embodiment, when the quality information measured by each NODE indicates an excessive deterioration in quality, the monitoring control device 3 is notified of this as an alarm. The window of FIG. 37 is a window for setting conditions for sending an alarm. The conditions set in the window of FIG. 37 are notified to the selected NODE, and the NODE that has received the notification operates according to this condition.
[0076]
Quality information includes TCCV (Total Count of Code Violation), BBE (Background Block Error), ES (Errored Second), SES (Severely Errored Seconds), UAS (Unavailable Seconds), OFS (Out of Frame Second), and the like. .
[0077]
When the NODE / Channel / Selection button is clicked in the window of FIG. 37, the NODE / Channel / Section Selection window of FIG. 38 is displayed. In the window of FIG. 38, it is set which quality information about which node, which channel, and which section in the ring network is targeted. That is, in the window of FIG. 38, not only the NODE of the connection partner but all NODEs belonging to the ring network including the NODE can be targeted.
[0078]
When the Read button is clicked in the window of FIG. 38, the current setting content is read from the target NODE and displayed in the window of FIG. Based on the contents displayed in the window of FIG. 37, the operator of Terminal 5 changes or corrects the conditions for sending an alarm for each of the quality information (TCCV to OFS).
[0079]
In the window of FIG. 37, On or Off is selected in the Notify column, and alarm notification or non notification is set. In the Perceived Severity column, any one of Critical, Major, Minor, and Warning is selected, and the alarm ranking to be notified is set. In the Threshold field, a threshold value related to alarm notification / non-notification is set by numerical input.
[0080]
After the above setting is made for each quality information, when the Set button is clicked, the setting content is notified to the target NODE. The NODE that has received the notification notifies the monitoring control device 3 of an alarm in accordance with the notified setting content. With the above functions, convenience in managing communication quality can be improved.
[0081]
<Path>
Next, the operation related to Path will be described. As for the Path relationship, as shown in FIG. 5, submenus of Path Configuration Control, Ring Map Administrative Control, Ls Group Type Control, and APS Control are prepared.
[0082]
(Path Configuration Control)
The Path Configuration Control window shown in FIG. 39 will be described. This window is opened when Path Configuration Control is clicked from the submenu (shown in FIG. 4) that is opened when Path is clicked on the main screen of FIG. The window in FIG. 39 is a window for setting a path in the network.
[0083]
The Path Configuration Control window shown in FIG. 39 includes Function, Edit, and View menus. In Function, Read Path, Update Path, and Invalid are prepared as submenus (not shown).
[0084]
First, when setting a path, the operator needs to know the current path setting state. Therefore, when the upper left Function in FIG. 39 is clicked and the Read Path button in the submenu is clicked, the Read Path window in FIG. 40 is displayed.
[0085]
The window of FIG. 40 is a window for designating NODE for acquiring the path setting state. In the window of FIG. 40, a mode for obtaining the setting state is designated. In FIG. 40, in the Scope Mode column, the target for acquiring the path setting status is all NODEs (All Nodes) in the ring network, or the NODE (Local Node) of the connection partner of the own device (Terminal 5). Whether to do is selected. Then, when one of SRV, P / T, or both Operation Modes is designated and the Read button is clicked, the current path setting content is read from the selected target. The read contents are reflected in the display (scroll window) of FIG.
[0086]
In the scroll window shown in FIG. 39, # 0 to # 3 are displayed respectively corresponding to NODE shown on the main screen of FIG. FIG. 39 shows an example in which one ring network includes four nodes. In FIG. 39, reference numeral # 1 surrounded by a square indicates the NODE to which the own terminal (Terminal 5) is currently connected. The left side is the high speed side West line and the right side is the East line toward the scroll window. On the left side of the scroll window, time slots that are time-division multiplexed on the high-speed side line are displayed with numbers, and one time slot corresponds to one path.
[0087]
For example, between NODE # 3 and NODE # 0, one double arrow is displayed at each of the timeslots 2 and 3 positions. Each arrow corresponds to one path, indicating that the path is dropped on the LS side at the node at the tip of the arrow.
[0088]
A mark indicating the drop type of the path is displayed at the tip of each arrow. For example, in time slot 2, a triangle mark (head) is displayed on NODE # 0, a square mark (Tail) is displayed on NODE # 3, and a white circle mark (Drop & Continue) is displayed on the NODE # 0 side of NODE # 1. . This indicates that the path added from the LS side at NODE # 0 is dropped to the LS side at NODE # 3 and is also dropped to the LS side at the intermediate NODE # 1. Such a path is called a dual homing path. In addition, a Drop & Continue with Add path is indicated by a double circle.
[0089]
The numbers at the tip of each arrow in FIG. 39 indicate the channel number on the low speed side that is the path drop destination. The path drop destination can also be shown in more detail, for example, as shown in FIG. In FIG. 45, for the notation “17B1”, the first 17 is the channel number, the next B is the board type (A is the STM-4 board, B is the STM-16 board), and the next 1 is LS (low speed). Side channel) time slot number.
[0090]
In FIG. 39, in the SRV section between NODE # 03 and NODE # 02, arrows are displayed at the positions of time slots 9 to 12, respectively. These arrows indicate a single concatenation path as a whole. That is, one path is formed by four time slots. “17B1a” or “65B1a” indicates a drop state of the path. For example, when “17B1a” is written, the first “17” indicates the channel number on the low speed side where the path is dropped. The next “B” indicates the board type to which the path is dropped. “B” means an STM-16 substrate, and “A” means an STM-4 substrate. The next “1” indicates the time slot number in the low-speed channel. The last “a” indicates the type of concatenation, and indicates that the concatenation signal indicated by this arrow is an AU-4-4c signal equivalent to STM-4.
[0091]
A path setting method using the window of FIG. 39 will be described.
First, the start point and end point of the path to be set are specified. For example, when the area around the dotted line in FIG. 39 (time slot 12, NODE # 0: not actually displayed) is clicked, the Node Information window in FIG. 41 is opened. In FIG. 41, the current path state related to the NODE corresponding to the clicked location is displayed.
[0092]
In the window of FIG. 41, the path type (Head, Tail, etc.) is specified in the Path Type column pull-down menu, and the concatenation type of the path to be set is specified in the Concatenation Type column. In FIG. 41, AU-4 equivalent to STM-1, AU-4-4c equivalent to STM-4, and AU-4-16c equivalent to STM-16 can be selected. In this field, AU-4-64c equivalent to STM-64 may be provided. In the LS Channel field, the channel that will be the start or end point of the path is selected from the pull-down menu. After each item is selected, the Create button or Modify button is clicked.
[0093]
Then, when Update Path (not shown) in the Function submenu of FIG. 39 is clicked, the Update Path Control window of FIG. 43 is displayed. The window in FIG. 43 is a window for instructing update of data including path setting. When the Exec button is clicked after each item in the window of FIG. 43 is checked, the setting contents are validated and a new path is set in the network.
[0094]
In addition, if APS functions during path setting work, there is a risk of erroneous traffic connection. In order to avoid erroneous connection, in the system of this embodiment, the APS function in the ring network is locked prior to the path setting operation. When the APS is locked, redundant system switching is not executed even if a failure occurs. In order to unlock the APS, Release is checked in the Release Lockout column of the window of FIG.
[0095]
Note that the Initialize Path Display window shown in FIG. 42 is a warning window that is displayed when the path editing operation is cleared. If OK is clicked here, the edited contents are cleared.
[0096]
The Invalid Path window shown in FIG. 44 will be described. This window is displayed when Invalid (not shown) in the Function submenu of FIG. 39 is clicked. The window in FIG. 44 is a window for confirming whether there is an invalid path among the paths displayed in FIG. In the scroll window of FIG. 44, “Extra” is displayed to indicate an extra path that should not exist. In addition, the missing path is indicated as “Shortage”.
[0097]
(Ring Map Administrative Control)
The Ring Map Administrative Control window shown in FIG. 46 will be described. This window is opened when the Ring Map Administrative Control button is clicked from the submenu shown in FIG. The window of FIG. 46 is a window for individually setting APS function lock (locked) / unlock (unlocked) for each node. This window is used, for example, when the locked APS function is not released for some reason when the path is set, or when it is manually opened.
[0098]
When the Node Condition button is clicked in FIG. 46, the Node Condition window in FIG. 47 is opened. In the window of FIG. 47, it is selected whether one NODE is specified or all NODEs in the ring network are specified. Then, when the Read button is clicked, the current state of the target NODE is acquired, and the acquired contents are displayed in FIG. From this state, either Locked or Unlocked state is selected in FIG. When the Set button is clicked, a message is sent to the target NODE, and the APS state is set to Locked or Unlocked.
[0099]
(Ls Group Type Control)
The Ls Group Type Control window shown in FIG. 48 will be described. The window in FIG. 48 is a window for setting a redundancy switching format for the low speed (LS) system. In FIG. 48, when Node / LS Shelf is clicked, the Node / Shelf Selection window of FIG. 49 is opened. In the window of FIG. 49, the target NODE and the low speed shelf are selected and the Read button is clicked. Then, the current setting contents of the LS group type are read and displayed in the LS No. and Group Type columns of FIG.
[0100]
When a desired row is selected in this column, the type of switching method is displayed in the pull-down menu in the Group Type column. Types of switching methods include “0: 1” corresponding to intra-device redundancy switching, “1 + 1 cP / T” with a part-time system, and the like. In addition, there are “1 + 1c”, “1: 1”, “1: 1 P / T”, and the like. Here, an arbitrary switching method is selected, and “Create” (create group type) or “Delete” (delete group type) is selected in the Edit Type column, and then the Set button is clicked. Then, the setting contents are notified to the selected NODE.
[0101]
The same applies to other windows, but the result of communication with NODE is displayed as, for example, OK / NG in the Console column. In addition, the access contents of the current communication are sequentially displayed in the footer portion (rectangle) at the bottom of the window.
[0102]
(APS Control)
The APS Control window shown in FIG. 50 will be described. The window shown in FIG. 50 is displayed when APS Control is clicked in the submenu shown in FIG. 4, and is used to set various parameters of the APS function. When the Node / Channel button is clicked in the window of FIG. 50, the window of FIG. 51 is opened. When the NODE and Channel to be operated are selected in the window of FIG. 51 and the Read button is clicked, the current setting content is read from the target NODE, and the content is displayed in FIG.
[0103]
In FIG. 50, there are items of Wait-to-Restore Time, Wait-to-Response Time, and Request Guard Time. These items are all temporal parameters related to APS. The current set value is displayed in the [] column. When an arbitrary numerical value is set in this field and the Set button is clicked, the setting contents are notified to the selected NODE and set.
[0104]
<Protection>
Next, the operation related to Protection will be described. As for the protection relationship, as shown in FIG. 5, submenus of Protection Switching Control, APS Exerciser Control, and Timing Mode Control are prepared.
[0105]
(Protection Switching Control)
The Protection Switching Control window shown in FIG. 52 will be described. This window is opened when Protection Switching Control is clicked from the submenu (shown in FIG. 4) that is opened when Protection is clicked on the main screen of FIG. This window is a window for manually performing switching by APS.
[0106]
Also here, first, Node / Section Selection is clicked, and the Node Section Selection window of FIG. 53 is displayed. 53, the target NODE is selected, and HS, Equipment, and LS are selected in the Section column. Equipment is an item related to switching within the apparatus. In particular, when LS is selected, LS Channel (low-speed side channel) is also specified. When Read is clicked after each item is specified, the current setting content is read and displayed in FIG. The display form in FIG. 52 also changes according to the selection contents in FIG.
[0107]
The scroll window of FIG. 52 displays the current status of parameters such as Protection Status, Request Source, Switch Status, Auto Switch Condition, and Switch Type. For example, when Equipment is specified in the Section field, two scroll windows are opened, and each window can be set individually. This corresponds to the two-way switching of East and West for Equipment and HS switching. Therefore, when LS is specified, only one scroll window is opened.
Incidentally, when HS is specified in Section, the columns displayed as LS1-LS64 and LS65-LS128 in FIG. 52 are displayed as EAST and WEST (regardless of the display order).
[0108]
In the Control Section field, a section to be set is specified, a scroll window is selected, and a switch type (Forced Switch, Manual Switch, etc.) is selected by Switch Type Control. When the Exec button is clicked after specifying either Invoke (execution of switching) or Release (returning from the switching state) in the Action column, the setting contents are notified to the selected node, A new switching state is set for this node. In this way, it is possible to control the switching state of any node from the Terminal 5 side.
[0109]
(APS Exerciser Control)
The APS Exerciser Control window shown in FIG. 54 will be described. This window is opened when APS Exerciser Control is clicked from the submenu shown in FIG. 4, and is a window for conducting a test related to transmission / reception of signals related to the APS function. In the window of FIG. 54, Node / Channel is clicked, and the NODE and channel to be operated are selected. Then, when Span (Line) or Ring is selected in the Exercise Type column and the Exec button is clicked, an APS operation test for the selected NODE is executed. Note that actual switching is not performed here, and only a test is performed as to whether or not K-bytes are exchanged normally.
[0110]
(Timing mode Control)
The NODE Timing mode Control window shown in FIG. 55 will be described. This window is opened when Timing Mode Control is clicked in the submenu shown in FIG. 4, and is a window for manually setting the operation clock (Timing Mode) for each node.
[0111]
The Node button is clicked in the window of FIG. 55, the target NODE is selected, and the current clock supply status is displayed in a list in FIG. When the Set button is clicked after each item of System Timing Mode, Select Clock, Select Card, Synchronization Mode, and Transmitting S1 (WEST and EAST) is specified in FIG. 55, a message is sent to the target NODE. The clock synchronization state is set.
[0112]
<Security>
Next, a security-related operation will be described. As for the security relationship, as shown in FIG. 5, submenus of User Control and Machine-Machine Control are prepared.
[0113]
(User Control)
The User Control window shown in FIG. 56 will be described. This window is opened when the User Control button is clicked from the submenu opened when Security is clicked from the main screen of FIG.
[0114]
A list of user names (operator names) currently registered in Terminal 5 is displayed in the window of FIG. Each user has a unique password, and this password is used when logging in to Terminal 5, for example. In the above window, the password expiration date is written in the “Password Valid Date” field. In addition, each user has a rank indicating “to what extent it can be operated” for various functions in the system as an access level, and there are ranks Level-A to Level-C.
[0115]
When the Add User button is clicked in FIG. 56, the Add User window in FIG. 57 is displayed. This window is a window for newly registering a user who can access Terminal 5. The window of FIG. 57 includes a user name input field, a password input field, a field for reconfirming the password, and a field for setting an access level.
[0116]
Conversely, when an arbitrary user is clicked and selected in the window of FIG. 56 and then the Delete User button is clicked, the registration of the selected user is deleted. At this time, a CAUTION window for confirming whether deletion is possible may be displayed.
[0117]
When an arbitrary user is clicked and selected in the window of FIG. 56 and then the Change Access Level button is clicked, the Change Access Level window of FIG. 58 is displayed. The window shown in FIG. 58 is for changing the access level of the selected user, and one of the radio buttons is checked to set the access level.
[0118]
When an arbitrary user is clicked and selected in the window of FIG. 56 and then the Change Password button is clicked, the Change Password window of FIG. 59 is opened. The window in FIG. 59 is a window for changing the password of the selected user. In this window, a column in which the selected user name is displayed, a column in which the user's old password, that is, a current password is input, a password input column to be newly set, and a password reset are displayed. And a field for confirmation.
[0119]
When an arbitrary user is clicked and selected in the window of FIG. 56 and then the Password Validity button is clicked, the Password Validity Configuration window of FIG. 60 is displayed. This window is a window for setting the expiration date of the password of the selected user. The window can be specified in a pull-down menu format on a monthly basis.
[0120]
(Machine-Machine Control)
The Machine-Machine Control window shown in FIG. 61 will be described. The window shown in FIG. 61 is opened when a Machine-Machine Control button is clicked from the submenu shown in FIG. This window is for managing the access level from the monitoring device in the system to the monitored device. That is, in the windows of FIGS. 56 to 60, human access authority to the device is managed. On the other hand, in the window of FIG. 61, the access authority for the device is managed. The monitoring device referred to here includes U-NME3 and SSE2 in addition to Terminal5.
[0121]
In the window of FIG. 61, the Node button is clicked to select the operation target NODE, and the current settings of the selected NODE are displayed in the Manager Name and Access Level columns.
When the Add button is clicked in the window of FIG. 61, the Add Manager window of FIG. 62 is opened. The window in FIG. 62 is a window used to newly register a monitoring device for the monitored device selected in FIG. When the Manager Name and its access level are specified in this window and the Set button is clicked, the access level of the selected monitoring device is set.
[0122]
When any of the monitoring devices displayed in FIG. 61 is selected and the Change button is clicked, the Change Manager Level window in FIG. 63 is displayed. The window in FIG. 63 is a window for changing the access level of the selected monitoring device. In this window, when one of the radio buttons is checked and then the Set button is clicked, the new setting becomes effective.
[0123]
Conversely, when any of the monitoring devices displayed in the scroll window in FIG. 61 is selected and the Delete button is clicked, the registration of the selected monitoring device is deleted. At that time, a CAUTION window as shown in FIG. 65 may be displayed.
[0124]
The Auto Logout Time Setting window shown in FIG. 64 will be described. The window of FIG. 64 is opened when Auto Logout Time Setting is clicked from the submenu shown in FIG. This window is a window for setting the time in the auto logout function. The auto logout function is a function for automatically logging off when no operation is performed in the terminal 5 in the logged-in state for a predetermined time. This type of function is well known as being effective in ensuring security. In the window of FIG. 64, a time from the last operation to logoff (that is, auto logout time) is set.
[0125]
<System>
Next, a system-related operation will be described. As for the system relationship, as shown in FIG. 6, sub menus of System Time Setting, Software Information, and Ring APS Control are prepared.
[0126]
(System Time Setting)
The System Time Setting window shown in FIG. 66 will be described. This window is opened when the System Time Setting button is clicked from the submenu (shown in FIG. 5) that is opened when System is clicked from the main screen of FIG. This window is a window for designating a device in the network system and setting its operation reference time.
[0127]
In the window of FIG. 66, when the Node button is clicked, a window for designating the NODE to be set for time is opened, and the NODE to be set is designated in this window. The current setting state is read from the NODE selected here, and the contents are reflected in FIG. In the window of FIG. 66, if the Set button is clicked after the operation time is set in the Date / Time field, the time setting for the selected NODE becomes valid.
[0128]
As described above, by setting the operation time for an arbitrary device, all devices existing in the network system can be operated in synchronization with the same time. Accordingly, when the network system is installed across an area having a time difference from each other, it is possible to set the operation time of each device to the universal standard time (UTC). Of course, it is possible to set a different operation time for each apparatus as required.
[0129]
(Ring APS Control)
The Ring APS Control window shown in FIG. 67 will be described. The window shown in FIG. 67 is displayed when Ring APS Control is clicked from the submenu shown in FIG. This window is a window for setting various parameters related to the high-speed redundancy switching function called Ring Aps.
[0130]
Parameters related to the Ring APS function include the number of NODEs constituting the ring network, the node ID unique to each NODE, the number of time slots for high-speed side service traffic, the number of time slots for high-speed side extra traffic, and the NODE connection relationship ( Ring Topology Map).
[0131]
In the window of FIG. 67, when the Read button is clicked, the current value of each parameter related to the ring network to which the NODE of the connection partner belongs is acquired in Terminal 5. The acquired parameter values are displayed in the window of FIG. 67. When a numerical value is input for each parameter item and the Set button is clicked, the input value becomes valid.
[0132]
When the Ring Topology Map button is clicked in FIG. 67, the Ring Topology Map Configuration window in FIG. 68 is opened. The window of FIG. 68 is a window for arbitrarily setting the connection relationship of each NODE in the ring network. In the window of FIG. 68, Nodes displayed as A to P indicate the NODEs adjacent in the ring in order. For example, if # 0 is A in the network configuration shown in FIG. 3, # 1 is B, # 2 is C,. For each NODE, a unique ID in the ring network and an individual NODE ID are individually set.
[0133]
(Software Information)
The Software Information window shown in FIG. 69 will be described. The window in FIG. 69 is displayed when the Software Information button is clicked in the submenu shown in FIG. This window is a window for designating NODE and displaying information regarding software installed in the NODE. When the Node button is clicked in this window and NODE is selected, the software version information and the date of installation are read from the designated NODE. This read content is displayed in the window of FIG. 69 together with the name of the node.
[0134]
<Node-Other>
Next, the operation related to Node-Other will be described. As for the Node-Other relationship, as shown in FIG. 6, submenus of LS Card Control and Notification Reporting Control are prepared.
[0135]
(LS Card Control)
The LS Card Control window shown in FIG. 70 will be described. This window is displayed when the LS Card Control button is clicked in the submenu (shown in FIG. 6) that is opened when Node-Other is clicked on the main screen of FIG. This window is for selecting a NODE and setting whether a card (board) mounted on the selected NODE is to be monitored or deleted from the U-NME 3.
[0136]
That is, in each NODE 1-1 to 1-n, the low speed side substrate (LS Card) can be freely inserted and removed. In order to operate the system, it is necessary for the U-NME 3 to grasp each time the card mounting state has changed due to card replacement or expansion. In the window of FIG. 70, a setting is made to delete a board that is no longer mounted due to being removed from the NODE from the target of monitoring by the U-NME 3.
[0137]
When the Node button is clicked in FIG. 70, a window for selecting a NODE to be operated is opened. After any NODE is selected in this window, the low speed side shelf is selected with the Select Shelf button. When the Select Card button is clicked, a Card Selection window shown in FIG. 71 is opened, and a low-speed card in the shelf is selected in this window. In the window of FIG. 71, “Left” or “Right” can be designated in the LS Card Type column, and the mounting position in the shelf can be selected.
[0138]
An arbitrary board is selected as described above, and either LS Card Deletion (deletion of target board) or LS Card Type Setting (change of board type) is selected in the Action column. When the Exec button is clicked, the set contents are notified to the target NODE as a message and set.
[0139]
By doing in this way, the effect as shown below can be acquired. Suppose that in any NODE, one STM-4 substrate having equivalent processing capability is replaced instead of four STM-1 substrates. Then, three of the slots where the STM-1 board was originally inserted become empty, and an alarm indicating that no board is mounted in the slot is detected. Even in the slot where the STM-4 board is inserted, an alarm indicating that the wrong board is mounted is detected. If this state is left unattended, the state in which these alarms are notified to the U-NME 3 will continue indefinitely, causing trouble in system operation.
[0140]
Therefore, by giving a message to NODE as described above, the board and the slot from which the board has been removed are excluded from monitoring, and the board type can be changed to avoid the above problem.
[0141]
(Notification Reporting Control)
The Notification Reporting Control window shown in FIG. 72 will be described. This window is opened when the Notification Reporting Control button is clicked from the submenu shown in FIG. 6, and is a window for setting a destination from which notification information is notified to any NODE from the Terminal 5 side. is there. That is, the window shown in FIG. 72 is a window for manually rewriting the EFD (Event Forwarding Discriminator) of each node from the Terminal 5 side.
[0142]
When the Node / Notification button in FIG. 72 is clicked, the Node / Notification Selection window in FIG. 73 is opened. In the window of FIG. 73, the target NODE is selected, and the type of notification information (for example, Alarm) that is the target of EFD rewriting is selected in the Notification column.
[0143]
When the Read button is clicked in the window of FIG. 73, the current setting contents are read, and the read value is displayed in FIG. In the Destinations column of FIG. 72, the name of the U-NME 3 that is the destination of the notification information at the current time by the selected node is displayed. An arbitrary U-NME 3 is selected in this field, and either “Allow” or “Inhibit” is designated in the “Notification Reporting” field below.
[0144]
In this way, whether or not to notify the notification information is individually set for each U-NME 3. When the Set button is clicked, a message notifying the set contents is sent to the NODE that is the operation target. The NODE that has received this message operates according to the set contents.
[0145]
In this way, the following effects can be obtained. If any U-NME 3 fails, notifying the notification information to the failed U-NME 3 causes inconvenience in terms of system operation. This is because the notified notification information is lost in the failed U-NME 3. Therefore, by rewriting EFD as described above, inconveniences such as loss of important data can be avoided. Further, the traffic when raising the notification information to the U-NME 3 occupies a relatively large band. Therefore, by setting the notification information to be notified only to the minimum necessary U-NME 3 using the above function, the notification information can be notified with the minimum necessary traffic. Can be reduced.
[0146]
<Display>
Next, the display-related operation will be described. As for the display relationship, as shown in FIG. 6, submenus of Display Control and Terminal Configuration are prepared.
[0147]
(Display Control)
The Display Control window shown in FIG. 74 will be described. This window is opened when Display Control is clicked from the submenu (shown in FIG. 6) that is opened when Display is clicked on the main screen of FIG. In this window, clickable Color buttons are provided for items such as Critical, Major, Minor, Warning, Clear, Other Notifications, and Maintenance indicating the alarm level. The current display color of each alarm level is displayed in the left square [□] across the Color button, and the newly set display color is displayed in the right square □. Although not shown in the figure, each square is colored.
[0148]
When the Color button is clicked in the window of FIG. 74, the color palette shown in the Color Selection window of FIG. 75 is displayed. Using this palette, an arbitrary color is selected for each alarm level. The display colors set in the window of FIG. 74 are applied to, for example, color coding of the faulty station building and faulty line on the main screen of FIG. In short, the display colors set here are all reflected in the above-described color coding in the window for graphically displaying the failure state in the network.
[0149]
In the window of FIG. 74, an item “Date Type” is displayed. In this item, either Time Date or Date Time is specified in the Order column. In accordance with the designation here, the date and time when various data are displayed in the window is displayed in the order of (time, date) or (date, time). In the Type column, the date display format is set as MM-DD-YYYY (month / day / year).
[0150]
In the Sorting column in the window of FIG. 74, the data display order is set. That is, it is selected whether to display data displayed in an arbitrary window in order from the latest data (Latest) or to display data from the oldest data (Earliest).
[0151]
(Terminal Configuration)
The Terminal Configuration window shown in FIG. 76 will be described. This window is displayed when Terminal Configuration is clicked from the submenu shown in FIG. The window in FIG. 76 is a window for manually inputting information of a remote station (NODE that is not a connection partner) into Terminal 5 in advance.
[0152]
That is, when the various functions described above are executed, the Terminal 5 may read the information of the remote station NODE via the communication line. At that time, the amount of data to be downloaded is large and it often takes time to read. Therefore, the time required for data acquisition is shortened by providing information in advance and storing it using the window shown in FIG.
[0153]
In the Ring Network Configuration of the window of FIG. 76, the number of NODEs constituting one ring network is set in the Number of Ring Node column. With the down arrow button, the ring formed by NODE A to F is rotated to the right or left, and for example, the local node (the partner NODE to which Terminal 5 is connected) is displayed at the top.
[0154]
In Node Configuration, for each NODE indicated in Ring Network Configuration, items 1, 2, and 3 are set with numbers, and configuration information for each NODE is set.
[0155]
As described above, according to the present embodiment, the human-machine interface can be improved, and it is possible to provide a monitoring and control apparatus that improves operational convenience.
[0156]
The present invention is not limited to the above embodiment.
For example, although the function in Terminal 5 has been described in the above embodiment, SSE 2 can also have the same function within the scope of its role sharing.
In the above embodiment, one U-NME 3 is installed in each station. However, depending on the system configuration, the entire network may be monitored and controlled by one U-NME 3, or an arbitrary station. The U-NME 3 may be installed in
Further, the names of the windows and function buttons, the arrangement of display objects in the windows, the positions of function buttons, and the like are not limited to the above embodiments.
In addition, various modifications can be made without departing from the scope of the present invention.
[0157]
【The invention's effect】
As described above, according to the present invention, it is possible to provide a communication path setting method capable of improving the human machine interface and improving operational convenience.
[Brief description of the drawings]
FIG. 1 is a system diagram showing a configuration of a transmission system in which an operator terminal device (Terminal) according to the present invention is installed.
FIG. 2 is a block diagram showing a configuration of an operator terminal device (Terminal) 5 according to the present invention.
FIG. 3 is a diagram showing a main screen of a display of Terminal 5.
FIG. 4 is a diagram showing a state where a sub menu is displayed in FIG. 3;
FIG. 5 is a diagram showing how a sub menu is displayed in FIG. 3;
6 is a diagram showing how a sub menu is displayed in FIG. 3;
FIG. 7 is a diagram showing a Node Alarm Summary Display window.
FIG. 8 is a diagram showing a Shelf Alarm Summary Display window.
FIG. 9 is a diagram showing a Shelf Alarm Summary Display window.
FIG. 10 is a diagram showing a Notification Display window.
FIG. 11 is a diagram showing an Alarm Cut Off window.
FIG. 12 shows an Item Selection (Row) window.
FIG. 13 is a view showing an Item Selection (Column) window.
FIG. 14 is a diagram showing a Notification Display Window Control window.
FIG. 15 is a diagram showing an example of a CAUTION window.
FIG. 16 is a diagram showing a Notification Detailed Display window.
FIG. 17 is a diagram showing a Notification Detailed Display window.
FIG. 18 is a diagram showing a Notification Detailed Display window.
FIG. 19 is a diagram showing an Alarm Severity Control window.
FIG. 20 is a diagram showing a Node / Category / Probable Cause Selection window.
FIG. 21 is a diagram showing a Node Selection window.
FIG. 22 is a diagram showing a Maintenance Control window.
FIG. 23 is a diagram showing a Maintenance Signal Insertion Control window.
FIG. 24 is a diagram showing a Selection window.
FIG. 25 is a diagram showing a Maintenance Signal Insertion Setting window.
FIG. 26 is a diagram showing an SD Threshold Control window.
FIG. 27 is a diagram showing an SD Threshold Setting window.
FIG. 28 is a diagram showing a NODE Log Control window.
FIG. 29 is a diagram showing an example of a CAUTION window.
FIG. 30 is a diagram showing a NODE Record Retrieval window.
FIG. 31 is a diagram showing an Alarm Record Retrieval Report window.
FIG. 32 is a diagram showing a Protection Record Retrieval Report window.
FIG. 33 is a diagram showing a Terminal Access Record Retrieval window.
FIG. 34 is a diagram showing a Terminal Access Record Retrieval Report window.
FIG. 35 is a diagram showing a Performance Data Record Retrieval window.
FIG. 36 is a diagram showing a Performance Data Record Retrieval Report window.
FIG. 37 is a diagram showing a Quality of Service Alarm Control window.
FIG. 38 is a diagram showing a NODE Selection window.
FIG. 39 is a diagram showing a Path Configuration Control window.
FIG. 40 is a diagram showing a Read Path window.
FIG. 41 is a diagram showing a Node Information window.
FIG. 42 shows an Initialize Path Display window.
FIG. 43 is a diagram showing a Path Update window.
FIG. 44 is a diagram showing an Invalid Path window.
FIG. 45 is a diagram showing a Path Configuration Control window.
FIG. 46 is a diagram showing a Ring Map Administrative Control window.
FIG. 47 is a diagram showing a Node Condition window.
FIG. 48 is a diagram showing an LS Group Type Control window.
FIG. 49 is a diagram showing a NODE / LS Shelf Selection window.
FIG. 50 is a diagram showing an APS Control window.
FIG. 51 is a diagram showing a Node / Channel Selection window.
FIG. 52 is a diagram showing a Protection Switching Control window.
FIG. 53 is a diagram showing a Node / Section Selection window.
FIG. 54 is a diagram showing an APS Exerciser Control window.
FIG. 55 shows a NODE Timing mode Control window.
FIG. 56 is a diagram showing a User Control window.
FIG. 57 shows an Add User window.
FIG. 58 is a diagram showing a Change Access Level window.
FIG. 59 is a diagram showing a Change Password window.
FIG. 60 shows a Change Valid Date window.
FIG. 61 is a diagram showing a Machine-Machine Security window.
FIG. 62 shows an Add Manager window.
FIG. 63 is a diagram showing a Change Manager Level window.
FIG. 64 is a diagram showing an Auto Logout Time Setting window.
FIG. 65 shows a Delete Manager window.
66 is a diagram showing a System Time Setting window. FIG.
FIG. 67 shows a Ring APS Control window.
FIG. 68 is a diagram showing a Ring Topology Map Configuration window.
FIG. 69 shows a Software Information window.
FIG. 70 shows an LS Card Control window.
FIG. 71 shows a Card Selection window.
FIG. 72 shows a Notification Reporting Control window.
FIG. 73 shows a Node / Notification Selection window.
FIG. 74 is a diagram showing a Display Control window.
FIG. 75 is a diagram showing a Color Selection window.
FIG. 76 is a diagram showing a Terminal Configuration window.
[Explanation of symbols]
ST-1 to ST-m ...
1-1 to 1-n ... node (NODE)
ST ... Station
OL ... High speed line
FL: wavelength division multiplexing line
ML: Monitoring and control line
2 ... Monitoring and control equipment (SSE)
3 ... Supervisory control device (NME)
4 ... Router
5 ... Terminal device for workers
31 ... Memory module
32 ... Processor module
33 ... Bridge
34 ... SCSI controller
35 ... HD (Hard Disk Drive)
37 ... Graphic controller
38 ... Interface controller
39 ... Bus controller
310 ... FDD (floppy disk drive)
311 ... Interface
312: Display interface
313: External interface
315 ... Display
319 ... Input device
320 ... Sound controller
321 ... Buzzer interface
322 ... Buzzer

Claims (4)

A plurality of communication paths is connected to one of said plurality of nodes of a network system comprising a plurality of ring network comprising a plurality of nodes each being connected in a ring to each other via a communication line to be multiplexed, the user operation A communication path setting method using a worker terminal device having a function of acquiring management information from the plurality of nodes via the communication line according to the display ,
The screen of the display unit is divided into a plurality of areas in association with sections between the nodes in the ring network to which the node to which the device is connected, and arrows respectively associated with communication paths existing in the section are displayed. A preparation step for displaying in the segmented area;
A first step of designating a low-speed channel of a node that is a starting point of a communication path to be set;
A second step of designating a low-speed channel of a node that is an end point of a communication path to be set;
A third step of displaying an arrow associated with the communication path to be set in a display area corresponding to the node section designated in the first and second steps;
If there is another communication path to be set, a fourth step that repeats the first to third steps;
A fifth step of sending a communication path setting request corresponding to an arrow associated with the communication path to be set to a node related to the formation of the communication path;
A node that has received a communication path setting request includes a sixth step of forming a new communication path based on the request ;
The communication path setting method , wherein the preparing step is a step of reflecting the current path setting state on the display content of the screen of the display based on the acquired management information .   2. The step according to claim 1, wherein the first step and the second step are steps of designating a type of concatenation of a communication path to be set in addition to designating a channel on a low speed side of the node. Communication path setting method. When the communication path to be set is a dual homing path,
And a seventh step of designating a low-speed channel of a node that is an intermediate drop point of the communication path to be set,
2. The communication path setting method according to claim 1, wherein the first, second, and seventh steps are steps of setting a node type in addition to specifying a low-speed channel of the node. The communication line comprises a working line and a protection line,
In the case where each of the plurality of ring networks includes a traffic detour unit that diverts service traffic transmitted through the working line to the protection line,
The sixth step includes
An eighth step in which the node that has received the communication path setting request locks its own traffic detour means;
After the completion of the eighth step, a ninth step of forming a new communication path based on the communication path setting request;
The communication path setting method according to claim 1, further comprising: a tenth step of releasing the lock of the traffic detour unit after the ninth step is completed.

Images