JP4463869B2 - Information processing device - Google Patents

Description

The present invention relates to an information processing equipment.

In recent years, with the advancement of information technology, the amount of data exchanged between computers has increased, and the demand for faster communication lines has increased. Along with this, construction of optical cable networks is progressing rapidly.
Various techniques for managing such an optical cable network have also been developed (see, for example, Patent Document 1).

JP 2003-233629 A

An optical cable network is configured by connecting a large number of optical cables in a complicated manner over a wide area. Each optical cable includes a number of core wires.
Such management of the core of the optical cable network must be performed accurately and reliably, but in recent years, the number of users of the optical cable network has increased rapidly, and the laying of optical cables has been rapidly advanced.
For this reason, there is a demand for a technique for quickly and accurately maintaining and managing the core of an optical cable network and reducing the work load.

  The present invention has been made in view of the above-described problems, and provides an information processing apparatus, an information processing apparatus control method, and a program for quickly and accurately performing maintenance and management of cores in an optical cable network and reducing work load. The main purpose.

  The information processing apparatus according to the present invention is as follows.

That is, the information processing apparatus according to the present invention is
For each optical cable that makes up the optical cable network, information for identifying the optical cable, information indicating whether or not a line has been set for each core in the optical cable, and a line set for each core in the optical cable are in operation. A core assignment management database for storing information indicating whether or not
A setting reservation input unit that receives input of information specifying an optical cable and the number of cores to be secured in the specified optical cable;
If the input number of cores to be secured does not exceed the number of cores for which no line has been set in the designated optical cable, it indicates that the line has not been set in the core assignment management database. Update the number of reserved cores for each core of the specified optical cable in which information is stored, and rewrite the information to indicate that the cores have been secured by the number of input cores to be secured. And
A temporary setting input unit that receives input of information specifying an optical cable and the number of cores temporarily reserved in the specified optical cable;
Even if the number of cores to be temporarily reserved exceeds the number of cores for which no line has been set in the specified optical cable, the number of cores to be temporarily reserved is the specified. If the number of cores not in operation in the optical cable does not exceed the number, the temporary allocation is secured in the core assignment management database for each of the cores in the specified optical cable that are not in operation. And a temporary line setting unit that rewrites information indicating that the cores are already secured .

  With such an embodiment, it is possible to secure a core wire (reserve the line setting) for a core wire for which no line is set. Today, optical communication is rapidly spreading, and new lines are set up one after another. For example, if there is an apartment under construction, if you reserve in advance the core line near the apartment, Immediately after construction, it becomes possible to provide an optical line to the residents of the apartment using the reserved core. Here, in this aspect, since the reservation specifying the number of cores is made, there is a degree of freedom compared with the case of making a reservation specifying cores in advance, and it is possible to prevent the design from being hindered. Become.

In the case of an extraordinary case, it is possible to secure the cores for the cores that are not operated, including the reserved cores. Thereby, it becomes possible to secure the core wire in an emergency.

In this information processing apparatus, it is preferable to adopt the following configuration.
In other words, when displaying an image showing the connection relation of each optical fiber in the optical cable network with a line drawing figure representing each optical fiber core, for the optical fiber for which a temporary line has been set, the other A connection display unit for displaying by a drawing method different from the line drawing figure to be represented;
It is preferable to provide.
According to such an aspect, a core wire for which a line is temporarily set can be visually distinguished from other core wires. As a result, when the temporary state is canceled and the line setting is restored, it is possible to distinguish between the core wire in which the temporary line has been set and the core line in which the line has been normally set. It becomes possible to facilitate the work of returning to the original state.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the column of the best mode for carrying out the invention and the drawings.

  ADVANTAGE OF THE INVENTION According to this invention, the maintenance management of the core wire in an optical cable network can be performed rapidly and correctly, and a work burden can be reduced.

It is a figure which shows the whole structure of the optical cable core management system which concerns on this Embodiment. It is a figure which shows the structure of the optical cable core management server which concerns on this Embodiment, and a user terminal. It is a figure which shows the structure of the memory | storage device of the optical cable core management server which concerns on this Embodiment. It is a figure which shows the structure of the memory | storage device of the user terminal which concerns on this Embodiment. It is a figure which shows the closure management database which concerns on this Embodiment. It is a figure which shows the station management database which concerns on this Embodiment. It is a figure which shows the customer management database which concerns on this Embodiment. It is a figure which shows the building management database which concerns on this Embodiment. It is a figure which shows the CTF / IDF management database which concerns on this Embodiment. It is a figure which shows the cable management database which concerns on this Embodiment. It is a figure which shows the core wire management database which concerns on this Embodiment. It is a figure which shows the core wire connection attribute management database which concerns on this Embodiment. It is a figure which shows the relay installation selection process in the core wire connection setting which concerns on this Embodiment. It is a figure which shows the core wire connection process in the core wire connection setting which concerns on this Embodiment. It is a figure which shows the connection attribute setting process in the core wire connection setting which concerns on this Embodiment. It is a figure which shows the core wire selection process in the core wire connection setting which concerns on this Embodiment. It is a figure which shows the core wire termination | terminus process in the core wire connection setting which concerns on this Embodiment. It is a figure which shows the core symbol determined according to the core connection state which concerns on this Embodiment. It is a figure which shows the connection symbol defined according to the core wire connection method which concerns on this Embodiment. It is a figure which shows the termination | terminus symbol defined according to the core wire connection method which concerns on this Embodiment. It is a figure which shows the cable selection process in the core wire connection setting via the coupler which concerns on this Embodiment. It is a figure which shows the coupler setting process in the core wire connection setting via the coupler which concerns on this Embodiment. It is a figure which shows the connection attribute setting process in the core wire connection setting via the coupler which concerns on this Embodiment. It is a figure which shows the connection destination setting process in the core wire connection setting via the coupler which concerns on this Embodiment. It is a flowchart which shows the flow of the core wire connection setting process which concerns on this Embodiment. It is a figure which shows the core wire setting process in the core wire securing process which concerns on this Embodiment. It is a figure which shows the core wire attribute setting process in the core wire securing process which concerns on this Embodiment. It is a figure which shows the core search process in the core ensuring process which concerns on this Embodiment. It is a figure which shows the core wire securing number input process in the core wire securing process which concerns on this Embodiment. It is a figure which shows the registration process in the core wire ensuring process which concerns on this Embodiment. It is a flowchart which shows the flow of the core wire ensuring process which concerns on this Embodiment.

=== Example of Overall Configuration ===
An overall configuration of an optical cable core management system 900 including an optical cable core management server 200 according to the present embodiment is shown in FIG. The optical cable core management server 200 corresponds to the information processing apparatus described in the claims.

<Optical cable core management system>
The optical cable core management system 900 is configured such that the user terminal 100 is communicably connected to the optical cable core management server 200 via the network 500.

  The optical cable core management system 900 is a system for core design / management based on a system diagram showing how each optical cable in an optical cable network is connected by a relay facility such as a station or a closure. In the optical cable management system 900, a station, a closure, a drop closure, a building, a CTF / IDF (Cable Terminating Frame / Intermediate Distribution Frame), customer information, and the status and operation status of the optical cable connecting these, closure, It is possible to manage the core wire connection status and its operation status in the CTF / IDF, the line superimposed on the core wire and its operation status.

  The optical cable core management system 900 has the following features. First, the optimum route can be selected from the search results of a plurality of routes while grasping the connection of the entire system diagram. In addition, it has a plan management function for equipment and core connection, and a reservation management function for a line superimposed on the core. Furthermore, in order to perform a quick design of FTTH (Fiber To The Home), consideration is given to not being affected by a decrease in response in communication speed. The multi-window environment allows editing of core and line attributes while opening multiple system diagrams and various forms on the screen. In addition, the download function allows you to download drawings and database lists such as system diagrams and single-line diagrams, and use them as attachments to construction specifications. In addition, the upload function allows efficient management of the number of cores owned for each cable section.

<Optical cable core management server>
The optical cable core management server 200 is a computer for supporting management of the optical cable network.

  The optical cable network is configured by connecting core wires in a plurality of optical cables to each other. Each optical cable typically includes tens to thousands of cores. In some optical cables, each core wire is bundled with a tape or the like every predetermined number to form a core wire bundle.

  Each optical cable usually has a length of several hundred meters to several thousand meters. And it is taken into each relay equipment, such as a closure and a station. The optical cable taken into the relay facility may be connected to another optical cable or may pass through the relay facility. Here, the connection with other optical cables is performed by fusing the cores together, when connecting the cores with a connector, or connecting the cores with a coupler (a core branching device). There is a case.

  When a customer applies for use of an optical communication line, a customer line is set in the core of the optical cable network. As a result, the customer can perform optical communication using the core wire. If there is no core wire that can set a line, it is necessary to newly lay an optical cable. The case where there is no settable core is, for example, when all the cores have already been set to other customer's lines and there are no open cores, or optical cables are not laid in the first place. .

  Usually, the line setting is performed across a plurality of optical cables. Therefore, in each relay facility, it is necessary to accurately manage which core wire is connected to which core wire for each core wire.

  The optical cable core management server 200 according to the present embodiment can visually display and set the connection relationship between the cores in each relay facility by a mechanism described later. Furthermore, it is possible to make a reservation for setting a line for the optical fiber in each optical cable. As a result, the efficiency of line setting work for the core wire is improved.

<User terminal>
The user terminal 100 is a computer that is communicably connected to the optical cable core management server 200 and is used when managing the optical cable network such as the line setting work. The optical cable network can be managed without using the user terminal 100. In this case, the user terminal 100 may be omitted.

=== Configuration of optical cable core management server and user terminal ===
Next, the configuration of the optical cable core management server 200 and the user terminal 100 will be described. Both the optical cable core management server 200 and the user terminal 100 are computers, and the hardware configuration is basically the same. Therefore, these hardware configurations are summarized in one block diagram and shown in FIG.

<Optical cable core management server>
The optical cable core management server 200 is a computer including a CPU (Central Processing Unit) 210, a memory 220, a port 230, a recording medium reading device 240, an input device 250, an output device 260, and a storage device 280.

  The CPU 210 is responsible for overall control of the optical cable core management server 200, and is an optical cable core management server control program (consisting of codes for performing various operations according to the present embodiment stored in the storage device 280 ( Various functions as the optical cable core management server 200 are realized by reading 710 (corresponding to the program described in the claims) 710 into the memory 220 and executing it.

  For example, the optical cable core management server control program 710 is executed by the CPU 210 and cooperates with hardware devices such as the memory 220, the port 230, the input device 250, the output device 260, and the storage device 280. Core connection attribute management database, relay facility designation input section, core line display section, first core line designation input section, second core line designation input section, connection status input section, connection display section, connection information writing section , Connection method designation input section, coupler input terminal designation input section, coupler output terminal designation input section, core wire assignment management database, setting reservation input section, reserved number of core wires update section, temporary setting input section, temporary line setting section Realized. The memory 220 can be constituted by a semiconductor memory device, for example.

  The recording medium reading device 240 is a device for reading a program and data recorded on a recording medium 400 such as a flexible disk, a magnetic tape, and a compact disk. The read program and data are stored in the memory 220 and the storage device 280. Therefore, for example, the optical cable core management server control program 710 recorded on the recording medium 400 is read from the recording medium 400 using the recording medium reader 240 and stored in the memory 220 or the storage device 280. it can. The recording medium reading device 240 can be built in the optical cable core management server 200 or can be externally attached.

  The storage device 280 can be, for example, a hard disk device or a semiconductor storage device. As shown in FIG. 3, the storage device 280 includes an optical cable core management server control program 710, a closure management database 600, a station management database 610, a customer management database 620, a building management database 630, a CTF / IDF management database 640, a cable. A management database 650, a core wire management database 660, and a core wire connection attribute management database 670 are stored. Among these, the core management database 660 corresponds to the core assignment management database described in the claims. The core connection attribute management database 670 corresponds to the core connection attribute management database described in the claims.

  The closure management database 600 is a database for managing closures. The closure is one of the relay facilities that take in each optical cable in the optical cable network. The closure management database 600 is shown in FIG. In the “closure name” column of the closure management database 600, information for specifying a closure is described. In the “connection information (cable name)” column, the name of the optical cable is described as information for specifying the optical cable to be taken into each closure. In the “connection information (section name)” column, information for specifying the relay facility into which the optical cable is taken is described. The “operation status” column describes the operation status of the closure.

  The station management database 610 is a database for managing stations. The station is also one of the relay facilities that take in each optical cable in the optical cable network. The station management database 610 is shown in FIG. In the “station name” column of the station management database 610, the name of the station is described as information for identifying the station. In the “building name” column, the name of the building indicating the location of the station is written.

  The customer management database 620 is a database for managing customers who are customers using the optical cable network. Customers are also one of the relay facilities that take in each optical cable in the optical cable network. The customer management database 620 is shown in FIG. In the “Customer Name” column, the customer name is described as information for identifying the customer. In the “building name” column, the name of the building indicating the customer's location is written.

  The building management database 630 is a database for managing building information indicating the location of a station or a customer. The building management database 630 is shown in FIG. In the “label” column, the name of the building is described as information for identifying the building. In the “Transition Destination System Diagram” column, identification information of a system diagram in which information related to the optical cable laid in the building is described.

  The CTF / IDF management database 640 is a database for managing CTF / IDF installed in a station or customer's building. A CTF / IDF management database 640 is shown in FIG. In the “CTF / IDF name” column, information for specifying the CTF / IDF is described. In the “connection information (cable name)” column, information for specifying an optical cable taken into each CTF / IDF is described. In the “connection information (section name)” column, information for specifying the relay facility into which the optical cable is taken is described.

  The cable management database 650 is a database for managing each optical cable constituting the optical cable network. The cable management database 650 is shown in FIG. In the “cable name” column, information for specifying each optical cable is described. In the “cable section name” column, information for specifying a relay facility into which the optical cable is taken is described. In the “tape type” column, the number of cores in each core bundle in the optical cable is described. When “2” is described in the tape type column, it indicates that each core bundle includes two cores. The “total number of cores” column describes the number of cores in the optical cable. Information indicating the length of the optical cable is written in the “cable actual length” column.

  The core management database 660 is a database for managing each core in each optical cable. The core wire management database 660 is shown in FIG. In the “cable name” column, information for specifying an optical cable including each core wire is described. In the “cable section name” column, information for specifying a relay facility into which each optical cable is taken is described. In the “core number” column, information for specifying each core is described. In the “tape number” column, information for identifying each core bundle is described. In the “empty state” column, information indicating whether or not a line has been set for each core wire is described. When “in use” is described, it indicates that a line has been set for the core. When “free” is described, it indicates that no line has been set for the core. In the “core line state” column, the presence or absence of abnormality of each core line is described. When “defect” is described, the core wire indicates that the optical communication cannot be performed. In the “core wire owner” column, information for identifying the owner of each core wire is described. In the “operation status” column, the operation status of each core wire whose “empty” column is “in use” is described. The operation status includes “operation”, “reservation”, and “reservation”. When “operation” is written, this indicates that the core is in operation. When “secured” is described, it indicates that the core wire has been secured. When “reserved” is described, the core line indicates that the setting is reserved.

  The core connection attribute management database 670 includes information for specifying a relay facility for each relay facility into which an optical cable constituting an optical cable network is taken in, information for specifying each core of an optical cable taken into the relay facility, and each of the above cores. Information identifying each core wire of the other party connected to the wire, and an output connected to the other core wire among a plurality of output terminals in a coupler (core wire branching device) interposed between the connected core wires It is a database that stores information that specifies terminals, information that indicates the connection status of cores connected to each other, information that indicates the connection method of cores connected to each other, and associated information. The core wire connection attribute management database 670 is shown in FIG.

  In the “equipment name” column, information specifying the relay equipment such as the name of the station or the closure is described. In the “left cable section name” column, information for specifying an optical cable taken into the relay facility is described. In the “left core number” column, information for specifying each core of the optical cable is described. In the “right cable section name” column, information for specifying the optical cable described in the “left cable section name” column and the optical cable of the other party to which the cores are connected is described. In the “right core number” column, information specifying each core of the optical cable described in the “right cable section name” column is described. In addition, when each core wire of the left optical cable and each core wire of the right optical cable are connected via a coupler, in the “left core number” column, together with information for specifying the core of the left cable, Information specifying the output terminal of the coupler connected to the core of the right optical cable is described. In the example of FIG. 12, “1-1”, “1-2”, “1-3”, and “1-4” are described in the “left core number column”. It represents that the core wire identified by the number “1” is branched through the coupler and output from the four output terminals of the coupler.

  In the “connection / termination” column, information indicating whether each core wire is connected to another core wire is described. When it is connected to another core wire, it is described as “connection”, and when it is not connected to another core wire, it is described as “termination”. In the “method” column, a connection method for connecting the cores is described. As the connection method, there are “fusion”, “connector connection”, “pass”, “coupler connection” and the like. In the case of “coupler connection”, the type of coupler is described in the “coupler type” column. As types of couplers, there are FTTH couplers and CS couplers. In the “coupler branch” column, the number of branches by the coupler is described. In the “operation status” column, information indicating the connection status of the cores connected to each other is described. The operation status includes “operation”, “reservation”, “reservation”, and “to be abolished”. “Operation” indicates that the operation is in progress. “Reservation” indicates that the supply destination is determined and the design is completed. “Securing” indicates that the supplier is in the planning stage. “Deprecated” indicates that it is in the phase of deprecation.

  In the “loss value” column, information indicating the amount of light attenuation is described. The amount of light attenuation (dB conversion) is determined according to the connection method between the core wires. In the example shown in FIG. 12, 0.4 (dB) in the case of “fusion”, 0 (dB) in the case of “pass”, and 18 (dB) in the case of “coupler 32 branch”.

The input device 250 is a device used for data input to the optical cable core management server 200 and functions as a user interface. For example, a keyboard or a mouse can be used as the input device 250.
The output device 260 is a device for outputting information to the outside and functions as a user interface. For example, a display or a printer can be used as the output device 260.

  The port 230 is a device for performing communication. For example, communication with other computers such as the user terminal 100 performed via the network 500 can be performed via the port 230. Further, for example, the optical cable core management server control program 710 may be received from another computer via the port 230 via the network 500 and stored in the memory 220 or the storage device 280.

<User terminal>
The user terminal 100 includes a CPU 110, a memory 120, a port 130, a recording medium reading device 140, an input device 150, an output device 160, and a storage device 180.
The functions of these devices are the same as those of the devices included in the optical cable core management server 200 described above.
Further, as shown in FIG. 4, a user terminal control program 700 is stored in the storage device 180 of the user terminal 100 and executed by the CPU 110, thereby realizing various functions as the user terminal 100. . For example, the user terminal control program 700 controls communication with the optical cable core management server 200 and realizes a browser function.

=== Connection setting process for core wire ===
Next, the setting process for the connection of the cores performed by the optical cable core management server 200 according to the present embodiment will be described with reference to FIGS. FIGS. 13 to 20 are diagrams illustrating a setting process when cores are directly connected to each other, and FIGS. 21 to 24 are diagrams illustrating a setting process when cores are connected via a coupler. It is. FIG. 25 is a flowchart showing the flow of the setting process of the connection of the core wires.

  FIG. 13 shows a system diagram showing how each optical cable in the optical cable network is connected by a relay facility such as a station or a closure. Here, the system diagram shown in FIG. 13 is assumed to be displayed on the display that is the output device 160 of the user terminal 100, but of course is displayed on the display that is the output device 260 of the optical cable core management server 200. It may be the case.

  First, on the screen of the system diagram shown in FIG. 13, when the mouse cursor is overlapped and clicked on an icon indicating a relay facility, information specifying the relay facility is input to the optical cable core management server 200. Then, when the mouse cursor is overlaid on the “core connection attribute” field shown in FIG. 13 and clicked, the screen shown in FIG. 14 is displayed.

  The screen shown in FIG. 14 displays figures (core line boxes) representing the cores of the optical cables taken into the designated relay facility, arranged side by side for each optical cable. In FIG. 14, the core number is written in each core box.

  In FIG. 14, when the name of the optical cable is entered in the “Cable Selection” field displayed one by one on the left and right, the optical cable core management server 200 performs the above input from the optical cables taken into the relay facility. A core box is displayed for each core of the optical cable specified by the designated name (S1000).

  Next, when a core wire box selected from the core wire boxes displayed side by side as shown in FIG. 14 is clicked, information specifying one of the core wires connected to each other in the relay facility Is input to the optical cable core management server 200 (S1010). In the example of FIG. 14, the core number “1” is input to the optical cable core management server 200.

  Then, by inputting each information in the “connection attribute” column shown in FIG. 15, the connection attribute is input to the optical cable core management server 200 (S1020). As the connection attribute, for example, information indicating the connection status of cores connected to each other (information displayed in the “operation status” column in FIG. 15), information indicating the connection method (“method” column in FIG. 15), “Connector (other)” column, “coupler type” column, “coupler branch” column) can be entered. It is also possible to input whether the selected core box is a terminal or a connection (information displayed in the “connection / terminal” column in FIG. 15).

  When “connection” is input in the “connection attribute” field (S1030), as shown in FIG. 16, the other core wire box connected to the selected core wire box is selected. As a result, information specifying the other core connected to the specified one core is input to the optical cable core management server 200 (S1040). Then, the optical cable core management server 200 displays the line drawing figure that connects the figures representing the one and the other designated core lines with a drawing method determined according to the designated connection status, and the above A graphic determined according to the connection method of the one and the other core wires is displayed so as to overlap the line drawing graphic.

  In the example shown in FIG. 16, since “operation” is input in the operation status column, the optical cable core management server 200 displays the line drawing figure connecting the cores with a solid line. The drawing method corresponding to the operation status is determined as shown in the “operating state of superimposed line” column in FIG. In other words, “Pending” is displayed with a broken line, “Pending” is displayed with a dotted line, “In operation” is displayed with a solid line, and “Deprecated” is displayed with a dashed line. The

  In the example shown in FIG. 16, since “fusion” is input in the method column, the optical cable core management server 200 displays a black circle superimposed on the line drawing figure connecting the cores. The figure corresponding to the connection method of the core wire is determined as shown in FIG.

  When the “Registration” column (not shown) is clicked on the screen shown in FIG. 16, the input connection attribute and information specifying the cores connected to each other are written in the core connection attribute management database 670 ( S1050). That is, information specifying the one core wire, information specifying the other core wire, information specifying the relay facility, information indicating the connection status of one and the other core wires, and the one and the other heart Information indicating the line connection method is associated with the information and written in the core connection attribute management database 670.

  On the other hand, when “Termination” is entered in the “Connection attribute” field in FIG. 15 (S1030), as shown in FIG. 17, “Termination method”, “Operation status”, “Termination” are operated by mouse operation. By selecting and inputting “method type”, a figure corresponding to the input information is displayed. FIG. 20 shows a list of figures determined according to the connection method.

  Then, when the “Registration” column (not shown) is clicked on the screen shown in FIG. 17, information for specifying the input connection attribute core is written in the core connection attribute management database 670 (S1050).

Next, a process for setting a connection between the core wires connected via a coupler will be described.
First, on the screen of the system diagram shown in FIG. 13, when the mouse cursor is clicked on the icon indicating the relay facility, information specifying the relay facility is input to the optical cable core management server 200. Then, when the mouse cursor is placed on the “core connection attribute” field shown in FIG. 13 and clicked, the optical cable core management server 200 displays the screen shown in FIG.

  The screen shown in FIG. 21 displays figures (core wire boxes) representing the cores of the optical cables taken into the designated relay facility, arranged side by side for each optical cable.

  In FIG. 21, when the name of an optical cable is entered in the “Cable Selection” field displayed one by one on the left and right, it is specified by the inputted name from among the optical cables taken into the relay facility. A core box can be displayed for each core of the optical cable (S1000).

  Next, as shown in FIG. 22, when a core box selected from among the core boxes displayed side by side is clicked, one of the cores connected to each other via a coupler in the relay facility is displayed. Information specifying the line is input to the optical cable core management server 200 (S1010). In the example of FIG. 22, the core number “1” is input to the optical cable core management server 200.

  Then, by selecting and inputting “connection method”, “operation status”, “coupler type”, and “coupler branch number” by operating the mouse, as shown in FIG. A graphic representing the coupler corresponding to the input information is displayed. At this time, the optical cable core management server 200 connects the graphic representing the one core and the graphic representing the input terminal of the coupler by connecting them with a line graphic.

  Then, by inputting each information in the “connection attribute” column shown in FIG. 23, the connection attribute is input to the optical cable core management server 200 (S1020). As the connection attribute, for example, information indicating the connection status of the core wires connected to each other, information indicating the connection method, and the like can be input. It is also possible to input whether the selected core box is a terminal or a connection.

  When “connection” is entered in the “connection attribute” field (S1030), as shown in FIG. 24, the selected core box connected to the selected core box via the coupler is selected. To do. As a result, information for designating the designated one core wire and the other core wire connected via the coupler is input to the optical cable core management server 200 (S1040). In the example shown in FIG. 24, the core wire specified by the core wire number 2 is designated. Then, the output terminal of the coupler connected to the other core wire is selected. Then, the optical cable core management server 200 connects and displays the graphic representing the output terminal of the coupler and the graphic representing the other core using graphic drawing.

  Then, when the “Registration” column in FIG. 24 is clicked, the input connection attributes and information specifying the cores connected to each other are written in the core connection attribute management database 670 (S1050). That is, the information for specifying the one core wire, the information for specifying the other core wire, the information for specifying the output terminal of the coupler interposed between the one and the other core wires, and the information for specifying the relay facility Are associated and written to the core connection attribute management database 670 (S1050).

  As described above, the setting process of the connection of the core wire in each relay facility is performed. Thereby, it becomes possible to perform the setting operation of the connection of the core wire in the relay facility into which the optical cable is taken in while visually grasping it. As a result, the setting work of the core wire is made efficient, and the work load of the core wire can be reduced. Also, in each relay facility, there are various types of connection status of the core wires, such as those in the planning stage, those in operation, and those to be abolished. When setting, it shows how the cores are connected by a drawing method according to the connection status of the cores, so it is possible to visually grasp the connection status and reduce the work load. .

=== Core securing process ===
Next, processing for securing a core wire in an optical cable constituting an optical cable network using the optical cable core management server 200 according to the present embodiment will be described with reference to FIGS. FIG. 31 is a flowchart showing the flow of a process for securing a core of a line.

  First, in the screen shown in FIG. 26, when “new line” is selected and clicked with the mouse, the optical cable core management server 200 displays the screen shown in FIG. Then, in the screen shown in FIG. 27, when the “operation status” column is “secured” and “core addition” is clicked with the mouse, the optical cable core management server 200 displays the screen shown in FIG.

  Next, in the screen shown in FIG. 28, when information is appropriately entered in the “search condition” field and the “search start” field is clicked with the mouse, it is stored in the cable management database 650, the core management database 660, or the like. Based on the information, optical cables that match the information entered in the “search condition” field are searched and displayed in a list.

  Then, from among the optical cables displayed in the list, select the optical cable for which the core wire is to be secured, and click the “Select” column with the mouse. Then, information specifying the optical cable is input to the optical cable core management server 200 (S2000). Then, the optical cable core management server 200 displays the screen shown in FIG.

  The optical cable core management server 200, as shown in FIG. 29, displays “cable section” and “number of free core wires” for the specified optical cable in the “line configuration” column based on the core management database 660. Is displayed. The number of empty cores is calculated based on the information described in the empty state column of the core management database 660.

  Here, the number of cores to be secured can be entered in the “number of reserved” column in the “line configuration” column (S2010). In the example of FIG. 29, since 1 is input, it is indicated that the number of cores to be secured is one.

  When the optical cable core management server 200 receives an input of the number of cores to be secured, the input number of cores to be secured exceeds the number of cores for which no line has been set in the designated optical cable. Judge whether or not there is. Then, the optical cable core management server 200 stores the input core wire to be secured for each core wire of the designated optical cable in which information indicating that the line has not been set is stored in the fiber core management database 660. Is rewritten to information indicating that the line has been secured. That is, the “empty state” column is updated to “in use” by the number of cores to be secured, out of the core wires described as “empty” in the “empty state” column. Then, the “operation status” column is updated to “reserved”. The core management database 660 is updated after “Register” described below is clicked (S2030).

  In FIG. 29, when the “addition of cores” column is clicked, the cores can be secured for other optical cables. In this case, the optical cable core management server 200 displays the screen shown in FIG. 28 again. Then, a core securing process is performed for the optical cable specified from the optical cables searched in the same manner as in the above procedure (S2020).

  When finishing the core wire securing process, “Register” is clicked on the screen of FIG. Thereby, the core management database 660 is updated for each of the designated optical cables.

  In the screen shown in FIG. 27, if the “operation status” column is “temporary”, a temporary cord can be secured. In the case of an extraordinary case, even if the empty state of the core is “in use”, the core can be secured as long as the operation status is not “operation”. In this case, in the screen shown in FIG. 28, when appropriate information is entered in the “search condition” field and the “search start” field is clicked with the mouse, it is stored in the cable management database 650, the core management database 660, etc. Based on the stored information, optical cables that match the information entered in the “search condition” field are searched and displayed in a list.

Then, from among the optical cables displayed in the list, select an optical cable to temporarily secure a core, and click the “Select” column with the mouse.
Then, when the number of cores temporarily reserved for the selected optical cable is input, the optical cable core management server 200 determines that the number of cores to be temporarily reserved is based on the core wire management database 660. It is determined whether or not the number of cores in the designated optical cable is exceeded. The optical cable core management server 200 determines that the number of the cores to be temporarily reserved is the number of the cores for which the line is not set in the specified optical cable (the number of the cores whose free state is “free”). Even if the number of cores to be temporarily secured is the number of cores that are not in operation in the specified optical cable (the vacant state is “free” or the operation status is “ If the number of cores that are “reserved” or “reserved” is not exceeded, the number of lines that are temporarily reserved for each non-operating core in the specified optical cable Set up.

  Note that when a temporary core is secured in this way, the optical cable core management server 200 uses, for example, a line drawing representing each core of the optical cable as shown in FIG. When displaying an image indicating the connection relationship, the core line temporarily secured is displayed by a drawing method different from the line drawing figure representing other core lines. For example, for a line drawing figure of a core line temporarily reserved, the color, thickness, line type, etc. are displayed differently from other core lines, or displayed blinking.

  As described above, the core wire in the optical cable can be secured. As a result, it is possible to secure a core wire for a core wire for which no line is set. Moreover, in the case of a temporary case, a core wire can be secured for a core wire that is not in operation. Thereby, it becomes possible to secure the core wire in an emergency. Furthermore, the core wire temporarily secured can be visually distinguished from other core wires and displayed. As a result, when the temporary state is canceled and the securing of the core wire is restored, it is possible to distinguish between the core wire that has been temporarily secured and the core wire that has been normally secured. The returning operation can be facilitated.

  Although the best mode for carrying out the present invention has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

DESCRIPTION OF SYMBOLS 100 User terminal 200 Optical cable core management server 400 Recording medium 500 Network 600 Closure management database 610 Station management database 620 Customer management database 630 Building management database 640 CTF / IDF management database 650 Cable management database 660 Core management database 670 Core connection Attribute management database 700 User terminal control program 710 Optical cable core management server control program 900 Optical cable core management system

Claims (2)

For each optical cable that makes up the optical cable network, information for identifying the optical cable, information indicating whether or not a line has been set for each core in the optical cable, and a line set for each core in the optical cable are in operation. A core assignment management database for storing information indicating whether or not
A setting reservation input unit that receives input of information specifying an optical cable and the number of cores to be secured in the specified optical cable;
If the input number of cores to be secured does not exceed the number of cores for which no line has been set in the designated optical cable, it indicates that the line has not been set in the core assignment management database. Update the number of reserved cores for each core of the specified optical cable in which information is stored, and rewrite the information to indicate that the cores have been secured by the number of input cores to be secured. And
A temporary setting input unit that receives input of information specifying an optical cable and the number of cores temporarily reserved in the specified optical cable;
Even if the number of cores to be temporarily reserved exceeds the number of cores for which no line has been set in the specified optical cable, the number of cores to be temporarily reserved is the specified. If the number of cores not in operation in the optical cable does not exceed the number, the temporary allocation is secured in the core assignment management database for each of the cores in the specified optical cable that are not in operation. A temporary line setting unit that rewrites information indicating that the core wire has been secured,
An information processing apparatus comprising: When displaying an image showing the connection relation of each optical fiber in the optical cable network with a line drawing figure representing each optical fiber core, the optical fiber for which a temporary line has been set is displayed for other optical fibers. A connection display unit for displaying by a drawing method different from the figure,
The information processing apparatus according to claim 1 , further comprising: