JP2001313638A - System for managing equipment of transmitting device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve problems such that many man-hours are needed because a differently managed ledger has to be confirmed in order to predict a circuit failure that occurs in device work, etc., and to preliminarily notify a user of the circuit failure in the conventional management system, that many spare packages have to be provided in order to fast correspond to the worst package failure in case the worst package failure occurs and that such spare packages consequently increase assets so that the spare packages can be a main cause of the cost increase in a fixed property tax, etc., because each device has to be provided with a spare package. SOLUTION: This system has management files such as a building housing device management file F1, device management files F21 to F2n, package management files F31 to F3n, section management files F41 to F4n, path management files F51 to F5n and circuit management files F61 to F 6n in order to manage a transmission network. The route confirmation of a circuit, the retrieval of customers to be notified at the time when a failure occurs and alternate package retrieval in the case a package failure occurs are immediately realized by retrieving the individual management files F1 to F6 with a designated algorithm.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for managing equipment of a transmission apparatus, and more particularly to a system for managing equipment of a transmission network constituted by transmission apparatuses.

[0002]

2. Description of the Related Art One example of a conventional network management system is disclosed in "New Synchronous Transmission Network System" of Japanese Patent Application Laid-Open No. 9-27792. This prior art,
A new synchronous transmission network system that can automatically create and change the transmission equipment management database, thereby improving the reliability of the transmission equipment management database and reducing human work when constructing it. Is disclosed.

[0003]

In the case of the above-mentioned prior art, the connection state between the devices is known, but the line lent to the user cannot be managed. That is, in order to predict a failure of a line which occurs due to the construction of the device and notify the user in advance, it is necessary to check a separately managed ledger, which requires a large number of man-hours. In the worst case, when a package failure occurs, it is necessary to provide a spare package for each device in order to respond quickly. However, the provision of a large number of spare packages results in an increase in equipment or assets, which causes a problem of increasing costs such as property tax.

[0004]

SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to provide an equipment management system for a transmission apparatus capable of easily obtaining information relating to a circuit route confirmation function, a troubled customer search function, and an alternative package search function. is there.

[0005]

SUMMARY OF THE INVENTION A facility management system for a transmission device according to the present invention is a package management system for managing packages included in a device in a transmission network system including a plurality of devices, packages, sections, paths and lines. A section management file for managing sections for connecting files and packages, a path management file for managing paths, and a line management file for managing lines are provided. Of which section of the map has passed.

According to a preferred embodiment of the equipment management system for transmission equipment according to the present invention, an equipment management file for managing the above-mentioned equipment is provided, and the equipment or package to be installed is designated based on this equipment management file, thereby Customer search means for searching for a customer that affects the customer. There is provided an alternative package search means for searching the device management file and the package management file, and searching for an alternative package when a failure occurs in the package. The plurality of devices are divided and accommodated in a plurality of stations in different areas. A device management file, a package management file, a section management file, a path management file, and a line management file are sequentially searched to make it possible to predict a failure occurring in the construction of the device.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The construction and operation of a preferred embodiment of a transmission equipment facility management system according to the present invention will be described below.
This will be described in detail with reference to the accompanying drawings.

First, FIG. 1 is a configuration diagram of a transmission network which is a preferred embodiment of a facility management system for a transmission device according to the present invention. This transmission network has an area /
It has a hierarchical structure in the order of station / device / package / section / path / line. It is classified into a case where there is a direct line under the section and a case where there is a path under the path. The device is composed of a plurality of units, and a package is provided inside the unit.

In the transmission network of FIG. 1, the area configuration includes an area A1 and an area A2. The station building composition is
The station B1 is located in the area A1, and the station B2 and the station B3 are located in the area A2. The devices include the device C1 in the station A1, the device C2 in the station B2, and the devices C3 and C4 in the station B3. The device C1 has 50M
A package D1 and a 150M package D2 are mounted. On the other hand, the device C2 has a 150M package D
3,6M package D4 and 144K package D5
Has been implemented. Further, a 6M package D6 and a 1.5M package D7 are mounted on the device C3. Further, the device C4 includes a 144K package D8,6.
A 4K package D9 and a 144K package D10 are mounted.

[0010] Between the above-mentioned packages D1 to D10,
Connected in section. Sections E1 and E2 are connected to the package D1, and one end of each of the sections E1 and E2 is connected to a device not managed by this system. The packages D2 and D3 are connected by a section E3. Section E4 is connected to packages D4 and D6, section E5 to packages D5 and D8, and section E6 and E7 to packages D7 and D6, respectively.
9 is connected.

In the path (PATH), the path BC is accommodated in the section E4. The path AC is accommodated in sections E3 and E4. Other path AX is in section E1, path AB is in section E3, path CX
Are housed in section E6. Line is line L
1 is contained in section E2, path AB, and sections E5 and E7. Line L2 is path AX, path AC
And the path CX.

Next, FIG. 2 shows a file configuration and a hierarchical relationship for managing the transmission network configuration described in FIG. On the top is the office building management file F1
This file F1 is associated with n (plurality) device management files F21 to F2n. here,
The number n of the device management files F21 to F2n varies depending on the network configuration. Device management files F21 to F
From 2n, they are associated with the package management files F31 to F3n in the devices C1 to C4. These package management files F31 to F3n are associated with a plurality of section management files F41 to F4n. Also, sections E1 to E7 include packages D1 to D10.
Section management file F4
1 to F4n include a plurality of package management files F31 to F4n.
F3n.

Here, the station accommodation apparatus management file F1
Is a file that is required in the system and manages the areas A1 and A2 and the stations B1 to B3 in the area, and the stations B1 to B3 and the devices C1 to C4 in the station. The device management files F21 to F2n are required by the number of the devices C1 to C4, and the packages D1 mounted on the devices C1 to C4 are required.
To D10. The device management files F21 to F2n also manage common parts of the devices C1 to C4. The common unit controls the entire device C1 to C4 and does not directly pass a signal of the network. The package management files F31 to F3n are required for the number of managed packages,
This file manages the sections E1 to E7 registered in .about.D10. Sections E1 to E7 are
Since the device is opposed to the devices C1 to C4, the opposed devices C1 to C4 are also managed at the same time.

Section management files F41 to F4n
Are the paths AX to CX and the line L
1, L2, and a plurality of contained path management files F51 to F5n or line management files F
61 to F6n. In addition, the path / line accommodation position is also managed at the same time. Path management files F51 to F5n
Manages the lines L1 and L2 housed therein, and stores a plurality of housed line management files F61 to F61.
Refer to F6n. In addition, the storage locations of the lines L1 and L2 are simultaneously managed. The line management files F61 to F6n are
A file which is the smallest constituent unit on the network and exists for each line, and manages the importance and the name of the customer who lends the line. It also manages the contained paths / sections.

FIGS. 3 to 6 show the detailed internal structure (internal information) of each of the management files F1 to F6 shown in FIG. FIG. 3A shows a “station building accommodation device management file” F1.
The internal structure of is shown. Areas A1, A2 and stations B1 to B3 where the devices C1 to C4 are installed, and the devices C1 to C3
In the area A1, the station building B is managed.
1 indicates that the station B2 and the station B3 are accommodated in the area A2. The station B1 houses the device C1, and the station B2 houses the device C2. Further, it is shown that the station B3 houses the devices C3 and C4. Further, the device types of the devices C1 to C4 are also shown.

FIG. 3B shows a “device management file” F2.
1 to F2n, and manages mounting packages and mounting positions in each of the devices C1 to C4. In the case of the device C1 shown in (a) of FIG. 3B, it is indicated that the package of the package type CONT is mounted on the package 1 of the block 1 of the unit 1, and the "basic / expansion" column indicates "basic / extended". Is shown. This indicates that this package is necessary for operating the device C1.
Similarly, ALM package / 50M package / 150
An M package is also mounted. Since the basics of the ALM package are shown, the package is necessary for operating the device C1. Since the 50M and 150M packages are “extensions”, they are packages that are additionally used later. Similarly, (b) of FIG.
FIG. 3 (c) shows the device C3 and FIG.
(D) of (B) shows the device management file for device C4,
Each is shown.

Next, FIGS. 4A to 4J show "package management files" F31 to F3n. Device C1
To manage the additional packages mounted on C4 to C4. Which of the devices C1 to C4 each package D1 to D10 is mounted on, and the packages D1 to D1
0 shows the sections E1 to E7 housed in FIG. FIG. 4A shows that the package D1 is mounted on the device C1, the section E1 is stored in the storage position 1 in the package D1, and the section E2 is stored in the storage position 2. Show. In addition, by setting the non-management in the opposing device column of the section E1, it indicates that the opposing device is out of the management of the facility management system of this transmission device. FIG. 4B shows that the section E3 contained in the package D2 is opposed to the device C2 managed by the equipment management system of the transmission device. Column ". Other FIGS. 4 (c) to (i)
Are the packages D3, D4, D5, D6, D
7, devices C2 to C4 and sections E3 to E6 on which D8 and D9 are mounted. FIG.
(J) is for the package D10, and the accommodation position column is "blank", which means that it is mounted but not actually used, indicating that it can be used as a spare.

FIG. 5 shows details of the "section management files" F41 to F4n of FIG. 2 for managing the sections E1 to E7. It manages the packages D1 to D10 accommodating the sections E1 to E7 and the accommodation positions of the paths AX to CX or the lines L1 and L2 accommodated inside the sections E1 to E7. FIG. 5A is an example of the section E1. As shown in FIG. 1, the end A is housed in the package D1, and what is housed is the path AX. Therefore, the end A in the housed PKG column becomes the package D1, and the end Z is "none". Also, “PATH-AX” is set in the path / line name column of the accommodated path / line, and the type is set to “path”. Similarly, FIG. 5C shows an example of the section E3. In the case of the section E3, since both ends are managed by the equipment management system of this transmission apparatus, both the A end and the Z end are package management names. Set. That is,
The end A is the package D2, and the end Z is connected to the package D3. The accommodated paths are “PATH-AC” at accommodation position 1 and “PATH-AC” at accommodation position 2.
-AB ". In addition, FIGS. 5B and 5D to 5G show sections E respectively.
2, E4 to E7.

Next, FIG. 6A shows "path management files" F51 to F5n shown in FIG. 2 for managing the paths AX to CX.
FIG. It manages the sections E1 to E7 or the paths AX to CX in which the paths AX to CX are accommodated and the accommodation positions of the paths AX to CX or the lines L1 and L2 accommodated in the paths. (A) of FIG. 6 (A) shows PATH-AX
As shown in FIG. 1, since the accommodated section is E1, the name of the accommodated section / path column indicates E1, and the type is “section”.
The path PATH-AX accommodates the line L
2, the line / line name is set to “line L2” and the type is set to “line” in the accommodated path / line column. Since the accommodation position of the line L2 is 1, "1" is shown in the accommodation position column. FIG. 6B shows the PAT shown in FIG.
The example of H-AC is shown. PATH-AC, Section E
3 and “PATH-BC”, “E3” and “PATH”
H-BC ". PATH-BC is a path, so the type is “pass”. In addition, (c) of FIG.
(E) is an example of the path PATH-AB, PATH-BC, and PATH-CX.

FIG. 6B shows "line management files" F61 to F6n for managing the lines L1 and L2. Line L
1, manages the sections E1 to E7 or paths AX to CX in which L2 is accommodated, the corresponding customers who are the information of the lines L1 and L2, and the degree of importance of determining whether or not immediate response is required when a failure occurs. FIG. 6A shows an example of the line L1. As shown in FIG. 1, the accommodated sections / paths are a section E2, a path AB, and a section E
5, E7, so the names of the accommodated section / path columns are “section E2”, “PATH-AB”,
"Section E5" and "Section E7"
Type is section E2 / section E5 / section E
In the case of 7, a section is set, and in the case of PATH-AB, a path is set. The line L1 is lent to the customer A, and if there is a problem, it is necessary to take immediate action. Therefore, the customer corresponding to the line information is designated as the customer A, and the importance is set to the important line.

As described above, the management file shown in FIGS. 3 to 6 is created by the necessary input means using the configuration example of the transmission network shown in FIG. 1, and the service as described in the operation description is realized. First, an example in which the line route confirmation function confirms the line route of the customer A will be described. Since the customer A uses the line L1, the customer A refers to the name of the accommodated section / path column in (a) of FIG. 6B, thereby obtaining the section E2, the PATH-AB, the section E5, and the section E7. And a primary candidate sequence shown in FIG. 7A is created. From this array, "Section E
2 ”is extracted from the file for section E2 shown in FIG.
And that the other Z end is out of control. Next, FIG.
From (a), it is recognized that the package D1 is mounted on the device C1. In addition, the A end point is “C1 device”, the Z end point is “None”,
The section is set as “section E2”.

In the case of the path AB, (c) of FIG.
It recognizes that the contained section is one of the sections E3 from the "Path AB path management file". “Section E3” is set in the section of “storage device arrangement” shown in FIG. 7A, and then, from section E3, from “file for section E3” in FIG.
It is recognized that the A end of this section is the package D2 and the Z end is the package D3. Next, as shown in FIG. 4B, it is recognized from the recognized package D2 that this package is mounted on the device C1.
The “C1 device” is located at the A end point of the “storage device arrangement” in FIG.
Is set, and the package D3 is also changed to the device C2 from FIG.
Recognize that Further, “C2 device” is set at the Z end point of “accommodating device arrangement” in FIG. 7A. Hereinafter, similarly, for the sections E5 and E7, the “accommodating device arrangement” of FIG. 7A is created from the files of FIGS.

When the "accommodation device arrangement" is completed, the Z end point "none" of the "accommodation device arrangement" in FIG. As a result, since the section E2 corresponds, the section E2 is set at the first stage of the section order of the “route check result” shown in FIG. 7B, and the C1 device is set at the first stage of the device order. Next, in order to find out in which section the line exits from the C1 device, the C1 device is searched for the A endpoint and the Z endpoint of the "accommodation device array" shown in FIG. 7A. Recognizing that the section E3 is the corresponding section, the “section E3” is set in the second stage of the section order, and the “C2 device” shown by the Z end point in FIG. Is set. Follow the same procedure in section E5
And section E7, and finally section E7
Since the Z end point is “none”, the creation of the “route check result” shown in FIG. 7B ends.

With the completion of the "route confirmation result" in FIG. 7B, the line of the customer A is changed from "section E2" to "C1".
It can be seen that services are provided through the “device” to “section E3” to “C2 device” to “section E5” to “C4 device” to “section E7”. By using this data, the operator can immediately find out which device or section has a failure due to the line failure of the customer A.

Next, an example of a function for searching for a troubled customer that occurs in the construction of the apparatus will be described. The device to be constructed is, for example, a device C1. FIG. 3B shows a package mounted on the device C1.
8 is searched for, and recognized as the package D1 and the package D2.
A “package table of construction equipment” shown in FIG.
Next, based on the “package management file for package D1” shown in FIG. 4A, it is recognized that the contained sections are E1 and E2, and the “related section table” of FIG. 8B is created. Similarly, the package D2 can be searched for the section E3 from FIG. 4B.

Next, the path contained in the section E1 is searched from the "section management file for section E1" shown in FIG. 5A, and is recognized as the path AX.
The “relation path table” shown in FIG. 8C is created. Similarly, for the sections E2 and E3, FIG.
5C, the line L1 and the paths AC and AB are recognized, and the "related path table" shown in FIG. 8C and the "related line table" shown in FIG. create. However, in the “section management file for section E2” in FIG. 5B, since the contained path / line column indicates the line L1, the “related line table” shown in FIG. 8D is directly created. I do.

Next, the line accommodated in the path AX is searched from the “path AX path management file” shown in FIG. 6A, and is recognized as the line L2. d)
Create a "Related Line Table". Similarly, for the path AC, (b) of FIG. 6A is searched. FIG. 6 (A)
(B) shows that the line L2 is accommodated, but since this line L2 has already been created by searching for the path AX, no new creation is made. Similarly, for the path AB, since the line L1 has been searched in the search for the section E2, no new setting is made.

Thus, the search for the line related to the construction of the device is completed. In order to add information of each line, FIG.
Search for "line management file" shown in. The line L1 is set to “customer A” and the importance level is set to “important line”.
Sets "customer B" and importance "none". At the time of equipment construction, the customer A who is an important line based on the above information
Can be notified that construction should be performed. Further, the customer B can recognize that the notification is not required because the importance is “none”.

Finally, the alternative package search function will be described by taking the case where the package D5 of the device C2 has failed as an example. First, the type of the package D5 is confirmed from (b) of FIG.
It recognizes that it is 44K. Next, the other device 144
The device having K is searched from (a), (c) and (d) of FIG. 3B, and the packages D8 and D of device C4 are searched.
Recognize that there are ten. Next, it can be seen from the section in which the “package management file for package D8” in FIG. Recognize that this package cannot be used. Also, the other package, package D10,
It can be seen from FIG. 4 (j) that there is no section accommodated by the same search method, and that the package D10 can be used as an alternative.

Normally, in the case of this example, the network operator has a spare package in the device C2 and handles replacement. However, in this operation method, it is necessary to have many spare packages that are not normally used, and assets (equipment) increase. Therefore, there is an advantage that one apparatus can cope with a plurality of apparatuses by the method of the above-described example, and it is not necessary to have extra resources.

The configuration and operation of the preferred embodiment of the transmission equipment facility management system according to the present invention have been described in detail. However, it should be noted that such exemplary embodiments are merely examples of the present invention and do not limit the present invention in any way. It will be readily apparent to those skilled in the art that various modifications can be made without departing from the spirit of the invention.

As is clear from the above description, according to the transmission equipment facility management system of the present invention, the following remarkable practical effects can be obtained. First, it is possible to immediately search for a trouble customer that occurs in the construction of the device. The reason is that by sequentially searching for “device management file”, “package management file”, “section management file”, “path management file” and “line management file”, it is possible to predict failures that may occur during equipment construction. This is because it is possible to immediately respond to the related customers.

Second, there is no need to have many spare substitute packages, which are necessary in the event of a device failure. The reason is that by sequentially searching for the “device management file” and the “package management file”, it is possible to immediately search for which station has a spare package performing the same operation.

Third, it is possible to immediately determine which equipment or section of the lent customer's line is affected by a failure. The reason is "line management file",
"Path management file", "Section management file",
A line failure is currently occurring because the sequential search of the "package management file" and the "device management file" enables the immediate confirmation of the line route of the customer's line passing through which device and section. This is because it is possible to immediately determine whether the error has occurred due to another failure.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing an example of a transmission network for implementing a facility management system for a transmission device according to the present invention.

FIG. 2 is a diagram showing a reference relation of various files necessary for realizing the transmission device facility management system of the present invention.

FIG. 3 is a specific example of a station accommodation apparatus management file (A) and an apparatus management file (B) shown in FIG.

FIG. 4 is a specific example of a package management file shown in FIG. 2;

FIG. 5 is a specific example of a section management file shown in FIG. 2;

FIG. 6 is a specific example of a path management file (A) and a line management file shown in FIG.

FIG. 7 shows a line route confirmation (A) and a route confirmation result (B) in the present invention.

FIG. 8 is an explanatory diagram showing a failed customer confirmation step in the present invention.

[Explanation of symbols]

 A1, A2 Area B1 to B3 Station C1 to C4 Device D1 to D10 Package E1 to E7 Section AX to CX Path L1, L2 Line F1 Station accommodation device management file F21 to F2n Device management file F31 to F3n Package management file F41 to F4 F4n section management file F51-F5n path management file F61-F6n line management file

Claims (5)

[Claims] 1. A transmission network including a plurality of devices, packages, sections, paths, and lines, a package management file for managing the packages included in the devices, and a section for managing the sections connecting the packages. A management file, a path management file for managing the path, and a line management file for managing the line are provided, and a route check result creating unit checks which section of which device of the device the customer's line passes through. An equipment management system for a transmission device, wherein the equipment management system is enabled. 2. An apparatus according to claim 1, further comprising an apparatus management file for managing said apparatus, and a troubled customer search means for searching for a customer who affects the work by designating an apparatus or a package to be constructed based on the apparatus management file. The facility management system for a transmission device according to claim 1. 3. The transmission according to claim 2, further comprising an alternative package search unit that searches the device management file and the package management file, and searches for an alternative package when a package failure occurs. Equipment management system. 4. The apparatus according to claim 1, wherein said plurality of devices are divided and accommodated in a plurality of stations in different areas.
4. The equipment management system for a transmission device according to 2 or 3. 5. The apparatus according to claim 1, wherein the apparatus management file, the package management file, the section management file, the path management file, and the line management file are sequentially searched to make it possible to predict a failure occurring in the construction of the apparatus. Item 3. The equipment management system for a transmission device according to item 1 or 2.