Service route management device, management method, and program

Abstract

One aspect of a service route management device according to the present invention includes: a storage unit for storing communication service information and network configuration information associating a communication service and a network resource; an acquisition unit for acquiring failure information about the network resource; a conversion unit for acquiring used route information about the communication service and converting the used route information into connection information about the communication service; and a determination unit for determining whether the communication service is being affected by a failure occurrence location and a communication instability location in the network resource, and outputting affected service information based on the result of the determination.

Description

Service route management device, management method, and program

[0001] One aspect of the present invention relates to a service route management device, a management method, and a program for grasping a service level of a network.

[0002] The social importance of network services has been increasing in recent years. When a network service failure occurs, it is important to minimize the impact on communication services that use the network service and to restore the network service as quickly as possible. Therefore, accurate and prompt understanding of the situation is essential in failure response work.

[0003] As a method for dealing with a failure in a network service, for example, the relationship between network resources is managed to grasp the ripple effect from the failure point of the network service to related network resources. In conventional technology, the ripple effect is calculated by managing link information between network resources and extracting the network resources related to the failure point in a chain reaction from the link information.

[0004] For example, as a network resource management technology, a network management device that uses a general-purpose data format to manage individual networks in an integrated manner has been proposed (see, for example, Patent Document 1). Also, a network management device that does not require modification of programs for network visualization has been proposed (see, for example, Patent Document 2). Furthermore, a network management device that identifies the impact of a failure that occurs in a network has been proposed (see, for example, Patent Document 3).

[0005] Japanese Patent No. 6655524 Japanese Patent No. 6837022 Japanese Patent No. 7107158

[0006] However, there are various communication protocols for each communication service. Furthermore, since the communication destination and connection route differ for each communication service, it is not possible to uniquely link the communication service to the network resource. Furthermore, since the network resource configuration used by each communication service differs, it is not possible to link the relationship between the network resource and the communication service. Under these circumstances, understanding the impact on communication services requires manual investigation, which takes time.

[0007] Furthermore, there are various devices and vendors that make up communication services, and there are multiple ways to express route information. This means that dedicated functions must be built for each service. Furthermore, each time a new service is added, a new system must be built, which increases the system's cost and time.

[0008] This makes it difficult to determine the impact on communication services from the location of a network service failure, and the situation often remains unknown until a report is received from a service user.

[0009] This invention was made in light of the above circumstances, and its purpose is to provide a technology that links network resources and communication services in order to grasp the impact of failures at the communication service level.

[0010] In order to solve the above problem, one aspect of the service route management device of the present invention includes a memory unit that stores information about communication services and network configuration information that associates the communication services with network resources, an acquisition unit that acquires failure information about network resources, a conversion unit that acquires usage route information about the communication services and converts the usage route information into connection information about the communication services, and a determination unit that determines whether the communication services are affected by failure locations and unstable communication locations in the network resources and outputs affected service information based on the determination result.

[0011] According to one aspect of the present invention, it is possible to manage route information used for each communication service and associate network resources with communication services. This makes it possible to automatically calculate the impact on communication services from the location of a network resource failure. This allows for accurate and rapid understanding of the status of communication services. Furthermore, it is possible to manage not only communication failures due to failures, but also targets with unstable communication.

[0012] Furthermore, according to one aspect of the present invention, by aggregating data into a general-purpose data model, calculation of the ripple effect on communication services can be implemented using common logic, which reduces the implementation cost and time compared to building dedicated functions.

[0013] FIG. 1 is a block diagram showing an example of the hardware configuration of a service route management device according to an embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of a service route management device according to an embodiment. FIG. 3 is a conceptual diagram showing an example of the configuration of resource management managed by a service route management device according to an embodiment. FIG. 4 is a conceptual diagram showing an example of management elements of a service. FIG. 5 is a diagram showing an example of a service and a network configuration. FIG. 6 is a table showing an example of service information corresponding to the service configuration shown in FIG. 5. FIG. 7 is a table showing an example of network configuration information corresponding to the network configuration shown in FIG. 5. FIG. 8 is a table showing an example of affected service information. FIG. 9 is a diagram showing a first specific example of a physical network configuration. FIG. 10 is a table showing an example of fault information corresponding to the physical network shown in FIG. 9. FIG. 11 is a table showing an example of utilization route information corresponding to the physical network shown in FIG. 9. FIG. 12 is a diagram showing a second specific example of a physical network configuration. FIG. 13 is a table showing an example of fault information corresponding to the physical network shown in FIG. 12. FIG. 14 is a table showing an example of utilization route information corresponding to the physical network shown in FIG. 12. FIG. 15 is a flowchart showing the overall flow of service route management in a service route management device according to an embodiment. FIG. 16 is a diagram showing services and network configurations in a first specific example of calculation of an impact path. FIG. 17 is a diagram showing services and network configurations in a second specific example of calculation of an impact path. FIG. 18 is a flowchart showing the flow of conversion of usage route information in a service route management device according to an embodiment. FIG. 19 is a diagram showing the configuration of usage conversion information and service A in a first specific example of conversion of usage route information. FIG. 20 is a diagram showing the configuration of usage conversion information and service B in the first specific example of conversion of usage route information. FIG. 21 is a diagram showing the configuration of usage conversion information and service A in a second specific example of conversion of usage route information. FIG. 22 is a diagram showing the configuration of usage conversion information and service B in the second specific example of conversion of usage route information. FIG. 23 is a flowchart showing the flow of service impact determination in a service route management device according to an embodiment.Fig. 24 is a diagram showing the service configuration and the determination result in a first specific example of service impact determination. Fig. 25 is a diagram showing the service configuration and the determination result in a second specific example of service impact determination. Fig. 26 is a diagram showing the service configuration and the determination result in a third specific example of service impact determination. Fig. 27 is a diagram showing the service configuration and the determination result in a fourth specific example of service impact determination.

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, components having the same functions and configurations will be given the same reference numerals.

[0015] (Hardware Configuration of Service Route Management Apparatus) First, an example of the hardware configuration of the service route management apparatus 1 will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the hardware configuration of the service route management apparatus 1.

[0016] 1, the service route management device 1 is a computer including a processor 10, a program storage unit 11, a data storage unit 12, a communication interface 13, and an input / output interface 14. The processor 10, the program storage unit 11, the data storage unit 12, the communication interface 13, and the input / output interface 14 are connected to each other via a bus provided in the service route management device 1.

[0017] The processor 10 is, for example, a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). The processor 10 controls the entire service route management device 1. The processor 10 executes a program stored in a program storage unit 11. The processor 10 realizes processing functions according to the embodiment in accordance with the program.

[0018] The program storage unit 11 includes, as storage media, nonvolatile memories that can be written to and read from as needed, such as hard disk drives (HDDs) and solid state drives (SSDs), and nonvolatile memories such as read-only memories (ROMs). The program storage unit 11 stores, as non-transitory storage media, programs for the processor 10 to execute various processes. The program storage unit 11 also stores an operating system (OS) and various application programs. One of the programs includes a service route management program.

[0019] The data storage unit 12 includes, as storage media, a nonvolatile memory such as an HDD or SSD that can be written to and read from at any time, and a volatile memory such as a RAM (Random Access Memory). The data storage unit 12 is used as a storage unit that stores data (information) acquired and created in the course of various processes.

[0020] The communication interface 13 is a wired or wireless communication unit for connecting to the network NW. For example, the service route management device 1 is connected to a linked system via the network NW. The linked system may be, for example, a network management device or a display device.

[0021] The input / output interface 14 is an interface with the input device 20 and the output device 30. The input / output interface 15 is connected to the input device 20 and the output device 30.

[0022] The service route management device 1 may include a display device.

[0023] (Functional Configuration of Service Route Management Apparatus) Next, an example of the functional configuration of the service route management apparatus 1 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the functional configuration of the service route management apparatus 1.

[0024] 2, the service route management device 1 includes, as its functional configuration, a failure location acquisition unit 101, a usage route information conversion unit 102, and an affected service determination unit 103. The functions of the failure location acquisition unit 101, the usage route information conversion unit 102, and the affected service determination unit 103 are realized by the processor 10 executing a service route management program stored in the program storage unit 11. Note that the failure location acquisition unit 101, the usage route information conversion unit 102, and the affected service determination unit 103 may also be realized in various other forms, including integrated circuits such as an application specific integrated circuit (ASIC), a graphics processing unit (GPU), a field-programmable gate array (FPGA), or a digital signal processor (DSP).

[0025] The data storage unit 12 includes a network configuration storage unit 121 and a service information storage unit 122. The network configuration storage unit 121 stores network configuration information received from the outside. The network configuration information is information that associates communication services with network resources. The service information storage unit 122 stores service information received from the outside. The network configuration information and service information are information that are registered before the service route management device 1 performs service route management. The configuration of the network configuration information and service information will be described later.

[0026] When a failure or unstable communication occurs in a network resource, the failure location acquisition unit 101 acquires information about the failure location and unstable communication location of the network resource (hereinafter referred to as "failure information"). The acquired failure information may be stored in the data storage unit 12. For example, based on the failure information and network configuration information, the failure location acquisition unit 101 calculates a path (hereinafter referred to as an "affected path") in the network resource that is affected by the failure or unstable communication. The failure location acquisition unit 101 transmits information about the calculated affected path to the affected service determination unit 103.

[0027] The usage route information conversion unit 102 acquires information (hereinafter referred to as "usage route information") about the network routes used by communication services (hereinafter simply referred to as "services") and converts this information into connection information for the communication services. More specifically, the usage route information conversion unit 102 acquires usage route information for each service. For example, the usage route information conversion unit 102 acquires which devices the traffic of each service passes through based on network traffic information. Alternatively, the usage route information conversion unit 102 acquires how the routes of each service are set based on routing table information for each device. The acquired usage route information may be stored in the data storage unit 12. For example, the usage route information conversion unit 102 extracts FREs (Forwarding Relationship Encapsulations) that connect the devices listed in the usage route information from the network configuration information. The usage route information conversion unit 102 transmits the converted usage route information (information about the extracted FREs) to the affected service determination unit 103.

[0028] The affected service determination unit 103 determines whether each service is affected by a failure or unstable communication in a network resource based on information obtained by converting network configuration information, service information, failure information, and usage route information. The affected service determination unit 103 generates affected service information as the determination result and outputs it.

[0029] (Configuration of resource management managed by service route management device) Next, an example of the configuration of resource management managed by the service route management device 1 will be described with reference to Fig. 3 and Fig. 4. Fig. 3 is a conceptual diagram showing an example of the configuration of resource management managed by the service route management device 1. Fig. 4 is a conceptual diagram showing an example of management elements of a service.

[0030] As shown in Fig. 3, resources managed by the service route management device 1 roughly include network resources and service resources. Network resources include physical resources and logical resources. The service route management device 1 manages management information of network resources by linking it with management information of service resources (service layer). The service route management device 1 manages this information in a common, general-purpose data format.

[0031] The physical resources include a physical layer. The management information of the physical layer includes information expressing, as general-purpose entities, each device (physical device) such as an optical communication transmission device TD, an L2 switch L2SW, an IP router RT, a communication building including these, a communication cable, an AGS (Aggregate Section), and a computer device PD used by a service user and a service administrator.

[0032] The logical resources include, for example, a transmission layer, an Ether layer, and an IP layer, but the configuration of layers included in the logical resources is not limited to these.

[0033] The management information of the transmission layer includes, for example, information that expresses point objects (hereinafter simply referred to as "points") and line objects (hereinafter simply referred to as "lines") of the transmission layer, transmission characteristics, and bandwidth using general-purpose entities.

[0034] The Ether layer management information includes information that expresses the points and lines of the Ether layer, Ether characteristics, and bandwidth using general-purpose entities.

[0035] The management information of the IP layer includes information that expresses the points and lines of the IP layer, IP characteristics, and bandwidth using general-purpose entities.

[0036] The service resources include a service layer, which is managed as a layer above the IP layer.

[0037] The service layer management information includes information that expresses the points and lines of the service layer, service characteristics, and bandwidth as general-purpose entities. The service route management device 1 decomposes and normalizes the service management information into points, lines, and service characteristics (and bandwidth), and manages it by linking it with the management information of network resources.

[0038] As shown in FIG. 4, the management elements of the service layer include end-to-end information for the service, information on all resources available for the service, information on the route in use, and information on service characteristics. The end-to-end information includes information on termination point encapsulation (TPE), which indicates the termination point of the service route (hereinafter also referred to as the "service path"). For example, the service route management device 1 uses the end-to-end information to grasp the impact on the service (hereinafter also referred to as the "service impact") caused by network resource failures and unstable communication. Furthermore, the information on all resources available for the service and the information on the route in use include information on points and lines in the network resources. The information on service characteristics may include service specifications, communication protocols, capacity (bandwidth, etc.), etc.

[0039] The service route management device 1 grasps the differences between different communication destinations, the relationships with network resources, and the relationships between services based on the management elements of the service layer.

[0040] The service route management device 1 manages resources in a general-purpose data format that is broken down into common elements (points and lines) that focus on connectivity between resources and service-specific elements (service characteristics). The service route management device 1 manages the common elements (points and lines) of each layer in a common data format. This allows the service route management device 1 to localize differences in expression and management that depend on services, devices, etc. By consolidating the relationships between resources into a common expression of points and lines, it is possible to understand service usage routes and build relationships between services and network resources using common logic. This reduces construction costs and shortens construction time compared to building dedicated functions for each resource individually.

[0041] (Specific Examples of Service Information and Network Configuration Information) Next, specific examples of service information and network configuration information will be described with reference to Figs. 5 to 7. Fig. 5 is a diagram showing an example of a service and network configuration. Fig. 6 is a table showing an example of service information corresponding to the service configuration shown in Fig. 5. Fig. 7 is a table showing an example of network configuration information corresponding to the network configuration shown in Fig. 5. Note that in the examples shown in Figs. 5 to 7, the explanation focuses on the common elements (dots and lines) of each layer, and therefore explanations regarding the characteristics of each layer are omitted.

[0042] The example shown in Fig. 5 shows service paths for two services (service A and service B), details of the service paths showing the service paths for each service, a logical network for logical resources, and a physical network for physical resources. Note that in the example shown in Fig. 5, for the sake of simplicity, descriptions of reference relationships between layers of intermediate devices are omitted.

[0043] In Figure 5, R1-1, R1-2, R2-1 to R2-4, R3-1, R3-2, R4-1, R4-2, and R5 in the physical network (physical resources) represent devices (physical devices). P1 to P8 in the logical network (logical resources) represent devices (logical devices). TPE1-1 to TPE1-4 and TPE2-1 to TPE2-4 in the service path and service path details represent the termination points of the service. NC1-1, NC1-2, NC2-1, and NC2-2 represent the NC (Network Connection) of the service, i.e., the end-to-end connection in the service. LC1-1 and LC1-2 represent the LC (Link Connect), i.e., the connection between devices.

[0044] As shown in FIG. 6, for example, in the service information, a service name is registered as an identifier. In the entry for each identifier, an attribute and a value corresponding to the attribute are registered. For example, a resource (i.e., a service path), the number of users of the service, and a bandwidth are registered as attributes. Note that information on service characteristics (protocol, etc.) may also be registered as an attribute. For example, the resource for service A is NC1-1, the number of users is 1,000, and the bandwidth is 100 Mbps. Furthermore, the resource for service B is NC1-2, the number of users is 2,000, and the bandwidth is 1 Gbps.

[0045] As shown in Fig. 7, common elements (dots and lines) of each layer are registered in the network configuration information. As identifiers of the network configuration information, the numbers of the entities constituting each service shown in Fig. 5 are registered. For example, the entities are NC, TPE, and LC. In the entry for each identifier, the resource type, attribute, and value corresponding to the attribute are registered.

[0046] For example, NC1-1 is registered as the identifier. In this case, the resource type is FRE (NC), i.e., a line. A reference TPE and a reference FRE are registered as attributes. TPE1-1 and TPE1-2 are registered as values ​​of the reference TPE. TPE1-1 and TPE1-2 are end-to-end information for service A. Furthermore, LC1-1 is registered as the value of the reference FRE. LC1-1 indicates the connection between TPE1-1 and TPE1-2.

[0047] For example, NC1-2 are registered as identifiers. In this case, the resource type is FRE (NC). Reference TPE and reference FRE are registered as attributes. TPE1-3 and TPE1-4 are registered as values ​​of reference TPE. Furthermore, LC1-2 are registered as values ​​of reference FRE.

[0048] For example, TPE1-1 is registered as the identifier. In this case, the resource type is TPE (TCP), i.e., a point. A reference TPE of a lower layer is registered as an attribute. In the example shown in FIG. 5, a TPE of service path details is registered. TPE2-1 is registered as the value of the attribute.

[0049] For example, TPE1-2 is registered as the identifier. In this case, the resource type is TPE (TCP). The reference TPE of the lower layer is registered as the attribute. TPE2-2 is registered as the value of the attribute.

[0050] For example, TPE1-3 are registered as identifiers. In this case, the resource type is TPE (TCP). The reference TPE of the lower layer is registered as the attribute. TPE2-3 are registered as the value of the attribute.

[0051] For example, TPE1-4 are registered as identifiers. In this case, the resource type is TPE (TCP). The reference TPE of the lower layer is registered as an attribute. TPE2-4 are registered as attribute values.

[0052] For example, LC1-1 is registered as the identifier. In this case, the resource type is FRE(LC), that is, a line. Reference FRE is registered as the attribute. NC2-1 is registered as the value of the attribute.

[0053] For example, LC1-2 is registered as the identifier. In this case, the resource type is FRE (LC). Reference FRE is registered as the attribute. NC2-2 is registered as the attribute value.

[0054] (Specific Example of Impact Service Information) Next, a specific example of impact service information will be described with reference to Fig. 8. Fig. 8 is a table showing an example of impact service information.

[0055] 8, the affected service information registers information about services that have been determined to be affected by the affected service determination unit 103. In the example shown in Fig. 8, service A is in a state where communication is impossible and has 1,000 users. Service B is in a state where communication is unstable and has 2,000 users.

[0056] (Specific Examples of Fault Information and Usage Route Information) Next, two specific examples of fault information and usage route information will be described with reference to Figs. 9 to 14. Fig. 9 is a diagram showing a first specific example of a physical network configuration. Fig. 10 is a table showing an example of fault information corresponding to the physical network shown in Fig. 9. Fig. 11 is a table showing an example of usage route information corresponding to the physical network shown in Fig. 9. Fig. 12 is a diagram showing a second specific example of a physical network configuration. Fig. 13 is a table showing an example of fault information corresponding to the physical network shown in Fig. 12. Fig. 14 is a table showing an example of usage route information corresponding to the physical network shown in Fig. 12.

[0057] First, a first specific example of the failure information and utilization route information will be described with reference to FIGS.

[0058] 9 and 10, in the first specific example, communication is not possible between R3-1 and R4-1, and between R4-1 and R4-2. The fault information includes information on the fault location and fault type. The fault types include, for example, communication not possible and communication unstable.

[0059] As shown in Figure 11, the usage route information registers devices on the usage route. For example, if R1-1 and R-2 are on the downstream side and R5 is on the upstream side, the upstream usage route for service A is the route connecting R1-1, R2-1, R3-1, R3-2, R4-2, and R5. The downstream usage route for service A is the route connecting R5 and R4-1. In this case, the downstream usage route for service A does not connect from R5 to R1-1.

[0060] The upstream route used by service B is a route connecting R1-2, R2-3, R3-1, R3-2, R4-2, and R5. The downstream route used by service B is a route connecting R5, R4-2, R3-2, R3-1, R2-3, and R1-2. In this case, the route used by service B connects R1-2 and R5 in both the upstream and downstream directions.

[0061] Next, a second specific example of the failure information and utilization route information will be described with reference to FIGS.

[0062] 12 and 13, in the second specific example, communication is unavailable between R2-1 and R3-1. Also, communication with R3-2 is unstable. In other words, communication between devices connected to R3-2 is unstable.

[0063] 14, the upstream route used for service A is a route connecting R1-1, R2-1, R2-2, R3-2, R3-1, R4-1, and R5. The downstream route used for service A is R5, R4-1, R3-1, R3-2, R2-2, R2-1, and R1-1. The route used for service A includes R3-2, where communication is unstable.

[0064] The upstream route used for service B is a route connecting R1-2, R2-3, R3-1, R4-1, and R5. The downstream route used for service B is R5, R4-1, R3-1, R2-3, and R1-2. The route used for service B does not include R3-2, where communication is unstable.

[0065] (Overall Flow of Service Route Management) Next, an example of the overall flow of service route management will be described with reference to Fig. 15. Fig. 15 is a flowchart showing the overall flow of service route management.

[0066] 15 , first, the service route management device 1 receives failure information and utilization route information (S1). More specifically, the failure location acquisition unit 101 receives the failure information. The utilization route information conversion unit 102 receives the utilization route information. The failure information and utilization route information may be input to the service route management device 1 from a system linked via the network NW, or may be input to the service route management device 1 by a user using the input device 20.

[0067] The failure location acquisition unit 101 calculates the affected path (S2). More specifically, the failure location acquisition unit 101 calculates the affected path from the network configuration information and the failure information.

[0068] Next, the usage route information conversion unit 102 converts the usage route information (S3). More specifically, the usage route information conversion unit 102 extracts FREs corresponding to devices and between devices in the usage route information as the usage route of each service. Note that the order of steps S2 and S3 may be reversed, or steps S2 and S3 may be executed in parallel.

[0069] Next, the affected service determination unit 103 determines the impact on each service (S4). For example, if the usage route does not connect the service path termination points (TPEs) or if the usage route includes a path that does not allow communication (hereinafter also referred to as an "affected path (communication unavailable)"), the affected service determination unit 103 determines that the service is communication unavailable (hereinafter also referred to as an "affected service (communication unavailable)"). Furthermore, for example, if a service that has been determined not to be an affected service (communication unavailable) includes a path with unstable communication (hereinafter also referred to as an "affected path (unstable)"), the affected service determination unit 103 determines that the service is communication unstable (hereinafter also referred to as an "affected service (unstable)"). The affected service determination unit 103 performs the determination for all services.

[0070] The affected service determination unit 103 outputs the determination result as affected service information (S5). For example, the affected service information may be stored in the data storage unit 12 or displayed on a display device. Furthermore, the affected service information may be notified to a user or a service administrator via the network NW.

[0071] (Specific Examples of Calculation of Influence Path) Next, two specific examples of calculation of influence paths in step S2 described using Fig. 15 will be described with reference to Fig. 16 and Fig. 17. Fig. 16 is a diagram showing services and network configurations in a first specific example of calculation of influence paths. Fig. 17 is a diagram showing services and network configurations in a second specific example of calculation of influence paths.

[0072] First, a first specific example of calculation of an influence path will be described.

[0073] As shown in FIG. 16, for example, communication is unavailable between R2-3 and R3-1, between R3-1 and R4-1, and between R4-1 and R4-2 in the physical network. This impact spreads to the logical network, which is a higher layer. For example, the logical network between P3 (corresponding to R2-3) and P5 (corresponding to R3-1), between P5 and P7 (corresponding to R4-1), and between P7 and P8 (corresponding to R4-2) are calculated as affected paths (communication unavailable). This impact further spreads to the service path details, which are higher layers. For example, in NC2-1, the path between P5 and P7 is calculated as an affected path (communication unavailable). Furthermore, in NC2-2, the paths between P3 and P5, between P5 and P7, and between P7 and P8 are calculated as affected paths (communication unavailable).

[0074] Next, a second specific example of calculation of an influence path will be described.

[0075] As shown in FIG. 17, for example, communication is unavailable between R2-1 and R3-1 in the physical network. Furthermore, communication is unstable at R3-2. This impact spreads to the logical network, which is a higher layer. For example, the path between P1 (corresponding to R2-1) and P5 in the logical network is calculated as an affected path (communication unavailable). Furthermore, P6 (corresponding to R3-2) is calculated as an affected path (unstable). This impact spreads to the service path details, which are even higher layers. For example, in NC2-1, the path between P1 and P5 is calculated as an affected path (communication unavailable). Furthermore, P6 is calculated as an affected path (unstable). Furthermore, in NC2-2, P6 is calculated as an affected path (unstable).

[0076] (Flow of Conversion of Usage Route Information) Next, the flow of conversion of usage route information in step S3 described with reference to Fig. 15 will be described with reference to Fig. 18. Fig. 18 is a flowchart showing the flow of conversion of usage route information.

[0077] 18, the utilization route information conversion unit 102 executes steps S31 and S32 (described later) for all services. That is, the utilization route information conversion unit 102 repeatedly executes steps S31 and S32 for each service.

[0078] First, the utilization route information conversion unit 102 refers to the utilization route information and the network configuration information to acquire the TPE and FRE of the lower layer (service path details) of the service path corresponding to the device on the utilization route (S31).

[0079] Next, the utilization route information conversion unit 102 acquires the FRE of the lower layer (service path details) of the service path corresponding to the devices along the utilization route (S32).

[0080] (Specific Examples of Conversion of Usage Route Information) Next, two specific examples of conversion of usage route information will be described with reference to Figs. 19 to 22. Fig. 19 is a diagram showing the configuration of usage conversion information and service A in a first specific example of conversion of usage route information. Fig. 20 is a diagram showing the configuration of usage conversion information and service B in the first specific example of conversion of usage route information. Fig. 21 is a diagram showing the configuration of usage conversion information and service A in a second specific example of conversion of usage route information. Fig. 22 is a diagram showing the configuration of usage conversion information and service B in the second specific example of conversion of usage route information.

[0081] First, a first specific example of conversion of utilization route information will be described.

[0082] 19, the usage route information conversion unit 102 refers to the usage route information. For example, the usage route information conversion unit 102 extracts FREs corresponding to the devices and between devices on the usage route indicated by the arrows as the usage path of the service path of service A. For example, in the case of service A, the usage routes are different for uplink and downlink, so different FREs are extracted for each.

[0083] 20, the utilization route information conversion unit 102 extracts FREs corresponding to the devices and between the devices on the utilization route indicated by the arrows as the utilization path of the service path of service B. For example, in the case of service B, the utilization route is the same for both the uplink and downlink, so the same FREs are extracted.

[0084] Next, a second specific example of conversion of utilization route information will be described.

[0085] As shown in Fig. 21, the usage route information conversion unit 102 refers to the usage route information. Then, the usage route information conversion unit 102 extracts FREs corresponding to the devices and between devices on the usage route indicated by the arrows as the usage path of the service path of service A. In the case of service A in the second specific example, the usage route is the same for both upstream and downstream. Therefore, the same FREs are extracted.

[0086] As shown in Fig. 22, the usage route information conversion unit 102 refers to the usage route information. Then, the usage route information conversion unit 102 extracts FREs corresponding to the devices and between devices on the usage route indicated by the arrows as the usage path of the service path of service B. In the case of service B in the second specific example, the usage route is the same for both upstream and downstream. Therefore, the same FREs are extracted.

[0087] (Flow of Service Effect Determination) Next, the flow of service effect determination in step S4 described with reference to Fig. 15 will be described with reference to Fig. 23. Fig. 23 is a flowchart showing the flow of service effect determination.

[0088] 23, the affected service determining unit 103 executes steps S41 to S47 (described later) for all services. That is, the affected service determining unit 103 repeatedly executes steps S41 to S47 for each service.

[0089] The affected service determining unit 103 checks the usage route of the service to be determined (S41).

[0090] First, the affected service determining unit 103 checks whether the route being used connects the service path termination points (TPE) (S42).

[0091] If the route used cannot connect the service path termination points (TPE) (Yes in step S42), the affected service determining unit 103 determines that the service is an affected service (communication impossible) (S45).

[0092] If the used route can connect the service path termination points (TPE) (step S42_No), the affected service determining unit 103 checks whether the used route includes an affected path (communication disabled) (S43).

[0093] If the utilization route includes an affected path (communication unavailable) (Yes in S43), the affected service determination unit 103 determines that the service is an affected service (communication unavailable) (S45).

[0094] If the utilization route does not include an affected path (communication unavailable) (S43_No), the affected service determination unit 103 checks whether the utilization route includes an affected path (unstable) (S44).

[0095] If the utilization route includes an affected path (unstable) (Yes in S44), the affected service determination unit 103 determines that the service is an affected service (unstable) (S46).

[0096] If the utilization route does not include an affected path (unstable) (S44_No), the affected service determination unit 103 determines that the service is normal (S47). In other words, the affected service determination unit 103 determines that the service is not an affected service.

[0097] (Specific Examples of Service Impact Determination) Next, four specific examples of service impact determination will be described with reference to Figs. 24 to 27. Fig. 24 is a diagram showing the service configuration and determination results in a first specific example of service impact determination. Fig. 25 is a diagram showing the service configuration and determination results in a second specific example of service impact determination. Fig. 26 is a diagram showing the service configuration and determination results in a third specific example of service impact determination. Fig. 27 is a diagram showing the service configuration and determination results in a fourth specific example of service impact determination.

[0098] First, a first specific example of service effect determination will be described.

[0099] 24, the route used does not connect the endpoints of the service path in the downstream direction of service A. In this case, the affected service determining unit 103 determines that the service is an affected service (communication impossible).

[0100] Next, a second specific example of service effect determination will be described.

[0101] 25, an affected path (communication unavailable) is included in the route used for the upstream of service B. In this case, the affected service determining unit 103 determines that the service is an affected service (communication unavailable).

[0102] Next, a third specific example of service effect determination will be described.

[0103] 26, an affected path (unstable) is included in the usage route for both the upstream and downstream of service A. In this case, the affected service determining unit 103 determines that the service is an affected service (unstable).

[0104] Next, a fourth specific example of service effect determination will be described.

[0105] 27, in the upstream and downstream of service B, the utilization route connects the termination points of the service path, and the utilization route does not include an affected path (communication unavailable) or an affected path (unstable). In this case, the affected service determination unit 103 determines that the service is normal.

[0106] According to the configuration of this embodiment, the service route management device 1 can manage service management information by linking it to management information about network resources. The service route management device 1 can manage the management information in a general-purpose data format. Furthermore, the service route management device 1 can manage the management information in a general-purpose data format that breaks it down into common elements (points and lines) that focus on the connectivity between resources and the characteristics of each layer. This allows the service route management device 1 to build the relationship between services and network resources using a common logic. Therefore, the service route management device 1 can mechanically calculate the impact on communication services from the locations of failures and locations of unstable communication in network resources. Therefore, the service route management device 1 can accurately and quickly grasp the status of communication services.

[0107] Furthermore, with the configuration according to this embodiment, the service route management device 1 can build management information using a common logic, which reduces the construction cost and time compared to building dedicated functions for each resource individually.

[0108] Other Embodiments The present invention is not limited to the above-described embodiment, and can be implemented in various modifications without departing from the spirit and scope of the present invention.

[0109] In short, this invention is not limited to the above-described embodiments, and in the implementation stage, the components can be modified and embodied without departing from the spirit of the invention. Furthermore, various inventions can be formed by appropriately combining multiple components disclosed in the above-described embodiments. For example, some components may be omitted from all the components shown in the embodiments. Furthermore, components from different embodiments may be appropriately combined.

[0110] DESCRIPTION OF SYMBOLS 1... Service route management device 10... Processor 11... Program storage unit 12... Data storage unit 13... Communication interface 14... Input / output interface 15... Input / output interface 20... Input device 30... Output device 101... Failure location acquisition unit 102... Usage route information conversion unit 103... Affected service determination unit 121... Network configuration storage unit 122... Service information storage unit

Claims

1. A service route management device comprising: a memory unit that stores service information of a communication service and network configuration information that associates the communication service with a network resource; an acquisition unit that acquires failure information of the network resource; a conversion unit that acquires utilization route information of the communication service and converts the utilization route information into connection information of the communication service; and a determination unit that determines whether the communication service is affected by a failure location and a location of unstable communication in the network resource, and outputs affected service information based on the determination result.

2. The service route management device according to claim 1, wherein the failure information includes information on the location of the failure and the location of the unstable communication.

3. The service route management device according to claim 1, wherein the service information includes information on a service path and a number of users of the communication service.

4. The service route management device according to claim 1, wherein the acquisition unit calculates paths affected in the network resources based on the failure information.

5. The service route management device of claim 1, wherein the determination unit determines that the communication service is not available when the route used for the communication service does not connect the end points of the service path, or when the route used includes a path that is not available for communication.

6. The service route management device of claim 5, wherein the determination unit determines that the communication service is unstable when the utilization route connects the termination points of the service path, the utilization route does not include a path that is unable to communicate, and the utilization route includes a path with unstable communication.

7. A method for managing service routes using a service route management device including a memory unit that stores service information of a communication service and network configuration information that associates the communication service with a network resource, the method comprising: acquiring failure information of a network resource; acquiring utilization route information of the communication service; calculating paths that are affected in the service path of the communication service; converting the utilization route information into connection information of the communication service; determining whether the communication service is affected by a failure location and a location of unstable communication in the network resource; and outputting affected service information based on the determination result.

8. A program comprising instructions for causing a computer to function as the service route management device according to any one of claims 1 to 6.

Images