WO2024042589A1 - Configuration input device, configuration input method, and configuration input program - Google Patents

Abstract

This controller (10) has a connection point management database (113) that stores information in which a combination of an ordinary connection point for connecting closed networks together and a redundant connection point for connecting the closed networks together is associated with a combination of an area and a closed network. The controller (10): acquires, from the connection point management database (113), a combination of an ordinary connection point and a redundant connection point that corresponds to an area and a connection network to which two locations belong; and creates a configuration to execute a settings process for setting an ordinary communication pathway that passes through the ordinary connection point and a redundant communication pathway that passes through the redundant connection point, the communication pathways connecting the two locations. The controller (10) inputs the configuration to a transfer device that is included in the ordinary communication pathway and the redundant connection pathway.

Description

Config input device, config input method, and config input program

The present invention relates to a configuration input device, a configuration input method, and a configuration input program.

Conventionally, a method is known in which connection points between networks are selected according to traffic characteristics (for example, see Non-Patent Document 1).

Takei et al., “Deployment position determination method for inter-network connection functions according to traffic characteristics” IEICE 2021 General Conference, B6-21, Mar.9, 2021.

However, the conventional technology has a problem in that it may not be possible to efficiently set up redundant communication paths.

For example, Non-Patent Document 1 does not describe that the redundancy setting of whether the communication path is ACT (normal use) or SBY (redundant use) is automatically performed. In that case, it is considered that the redundancy setting of the communication path will be manually performed by the operator.

In order to solve the above-mentioned problem, the configuration input device combines a normal connection point that connects the closed networks and a redundant connection point that connects the closed networks in the combination of the area and the closed network. A storage unit that stores the associated information and a combination of a normal connection point and a redundant connection point corresponding to the area and closed network to which the two bases belong are acquired from the storage unit, and Executing a setting process for setting a communication route connecting the bases, including a normal communication route that passes through the normal connection point and a redundant communication route that passes through the redundant connection point. The present invention is characterized by comprising: a configuration processing unit that creates a configuration to be configured, and a configuration input unit that inputs the configuration to a transfer device included in the normal communication path and the redundant connection path.

According to the present invention, it is possible to efficiently set redundant communication paths.

FIG. 1 is a diagram illustrating communication paths in a network. FIG. 2 is a diagram showing an example of a network configured by transfer devices. FIG. 3 is a diagram showing an example of the configuration of a system including a controller. FIG. 4 is a diagram for explaining an overview of the setting section. FIG. 5 is a diagram showing an example of connection point information stored in the connection point management DB. FIG. 6 is a diagram illustrating an example of setting processing stored in the setting management DB. FIG. 7 is a diagram for explaining a template used by the controller. FIG. 8 is a diagram illustrating a method of setting a main route and a redundant route. FIG. 9 is a diagram illustrating a method of setting a main route and a redundant route. FIG. 10 is a diagram for explaining an overview of the device determining section. FIG. 11 is a diagram showing an example of device information stored in the device information DB. FIG. 12 is a flowchart illustrating an example of a processing procedure of the controller. FIG. 13 is a flowchart illustrating an example of a procedure for identifying a connection point. FIG. 14 is a flowchart illustrating an example of a procedure for determining a transfer device. FIG. 15 is a sequence diagram showing an example of a processing procedure of the controller. FIG. 16 is a sequence diagram showing an example of the processing procedure of the controller. FIG. 17 is a diagram showing an example of the configuration of a computer that executes a configuration input program.

Hereinafter, modes for carrying out the present invention (embodiments) will be described with reference to the drawings. The invention is not limited to the embodiments described below.

[Overview of embodiment]
The embodiment relates to inputting a configuration to a transfer device that transfers data in a network.

In the embodiment, by separating configuration orders into each scenario and managing information for each device or each user as parameters, it becomes possible to create a configuration for inter-network connections only by changing parameters of a template.

Furthermore, in the embodiment, the positioning logic (delay, capacity limit, etc.) of the transfer device based on real-time information of the network and user requirement information enables flexible deployment or selection of tunnel functions according to requirements. Details of the transfer device will be described later.

Here, consider the case where multiple routes can be configured on the network, as shown in FIG. It is assumed that each of the plurality of routes has a different combination of connection points that they pass through. Note that the connection point is a transfer device that connects closed networks included in the network.

The entire network is composed of multiple closed networks. A closed network may span multiple areas. Further, each closed network may have a different communication carrier, for example, and may have different communication quality.

In the example of FIG. 1, the closed network Nx and the closed network Ny both span areas with area IDs "A", "B", and "C". Further, it is assumed that the closed network Nx has lower communication quality than the closed network Ny. Communication quality is determined by the transfer speed, the difficulty of communication interruptions, etc.

Areas with area IDs "A", "B", and "C" are geographical regions that are different from each other. The area may be an area of a municipality such as a prefecture, city, or ward, or a wide area of a block such as a plurality of prefectures.

For example, a logical communication path connecting the head office and branch office of the user U1 is configured on a physical network including the closed network Nx and the closed network Ny. In this case, the logical communication path includes a main path using a normal (ACT) tunnel and a redundant path using a redundant (SBY) tunnel. A redundant route is used when the main route cannot be used due to a failure, etc.

[Transfer device and controller]
The transfer device 40 to which the controller 10 inputs the configuration and the controller 10 will be described with reference to FIG. 2.

The transfer device 40 is a device that transfers data at L2 (layer 2) or L3 (layer 3), and is communicably connected via a network (see reference numeral 101 in FIG. 2). Each of the transfer devices 40 has a tunnel function, and when a tunnel is set up with another transfer device 40, data transfer is performed using the tunnel. Note that in the following description, the tunnel may be an L3 tunnel or an L2 tunnel.

For example, it is assumed that two user NWs (networks) exist, as shown by reference numeral 102 in FIG. Each user NW is provided with a tunnel function by the transfer device 40.

Here, for example, consider adding a plurality of communication paths (logical NWs) that connect two user NWs via tunnels. In this case, the controller 10 of the transfer device 40 inputs a configuration for adding a tunnel to the transfer device 40 configuring the logical NW, as indicated by reference numeral 104.

[System configuration example]
Next, a configuration example of a system including the controller 10 will be described using FIG. 3. The system 1 includes, for example, a controller 10, a real-time information DB (database) 20, an external information collection system 30, and a transfer device 40 (40_1, 40_2, . . . , 40_N).

The controller 10 is a device that controls each transfer device 40. For example, when the controller 10 receives an order to set up a tunnel between the transfer devices 40 from a higher-level Ops (operation system), the controller 10 sets up the tunnel by referring to information collected from the real-time information DB 20, external information collection system 30, etc. Create a config to do this. Then, the controller 10 inputs the created configuration to the transfer device 40 to which the tunnel is set.

The real-time information DB 20 stores information indicating the communication status between each transfer device 40. The information indicating the communication status between the transfer devices 40 is, for example, information indicating communication delay time, jitter, communication band, etc. between each transfer device 40. The information in this real-time information DB 20 is updated, for example, at every predetermined period.

The external information collection system 30 collects information on the communication status (for example, communication delay time, jitter, communication band, etc.) between each transfer device 40. For example, the external information collection system 30 collects information on communication status between designated transfer devices 40 based on a request from the controller 10 and outputs it to the controller 10.

[controller]
The controller 10 includes a setting section 11 and a device determining section 12. The setting unit 11 creates a configuration for tunnel setting and inputs it to the transfer device 40 to which the tunnel is set. The device determining unit 12 determines the transfer device 40 to which the configuration is to be input by the setting unit 11, based on information indicating the communication status between the transfer devices 40, the communication requirements (user requirements) of the users of the tunnel, and the like.

[Settings section]
The setting section 11 includes an order receiving section 111 , an order dividing section 112 , a connection point management DB 113 , a setting management DB 114 , a template DB 115 , a setting processing section 116 , and a configuration inputting section 117 . Note that the connection point management DB 113, setting management DB 114, and template DB 115 described above are installed in a storage unit (not shown) of the controller 10.

First, an overview of the setting section 11 will be explained using FIG. 4. As shown in FIG. 4, the order receiving unit 111 of the setting unit 11 receives a tunnel setting order from, for example, a higher-level Ops (S1). Thereafter, the order dividing unit 112 divides the setting order received in S1 (S2) and stores it in the setting management DB 114 (S3). After that, the setting processing unit 116 reads out the setting process from the setting management DB 114 and processes it (S4).

Furthermore, the configuration order received by the order reception unit 111 includes information on the base of the user to whom the communication route is added. At that time, in S4, the setting processing unit 116 generates information such as the tunnel role (normal use (ACT) or redundancy use (SBY)) and priority (hereinafter referred to as priority information) based on the base information, It is saved in the setting management DB 114. Further, the setting processing unit 116 stores information regarding the base in the setting management DB 114.

Next, returning to FIG. 3, the setting section 11 will be explained in detail. The order accepting unit 111 of the setting unit 11 accepts tunnel setting orders. The tunnel configuration order includes, for example, any of the configuration processes shown in (1) to (4) below, or a combination thereof.

(1) New registration settings or deletion of a tunnel user (2) New settings or deletion of a transfer surface using a tunnel (3) New settings, deletion, or configuration changes of a tunnel interface (4) Incidental to each configured interface Changing parameter settings

Note that among the setting orders, the information regarding the setting process (1) includes, for example, the user's ID. Further, the information regarding the setting process (2) includes, for example, the type of transfer plane (for example, L3 or L2), device information used in the transfer plane (for example, the device ID of the transfer device 40), and the like. Further, the information regarding the setting process (3) includes information such as the type of tunnel and the IP address of the interface used in the tunnel. Further, the information regarding the setting process (4) includes the type of parameter to be set (for example, BGP (Border Gateway Protocol), QoS (Quality of Service), end point address, etc.), parameter values, etc.

The order dividing unit 112 divides the setting order received by the order receiving unit 111 into predetermined setting processing units. For example, the order dividing unit 112 divides the setting order into the setting processes shown in (1) to (4) above. Furthermore, priority information is generated based on the setting order. After that, the order dividing unit 112 saves the divided setting process in the setting management DB 114 together with the priority information and the information regarding the base.

The generation of priority information by the setting processing unit 116 will be explained. The priority information is information including the role of the tunnel (normal use (ACT) or redundancy use (SBY)) and priority.

The order reception unit 111 receives information indicating the areas of the two bases and information indicating the closed network to which they belong.

The setting processing unit 116 refers to the connection point management DB 113 and identifies a normal connection point (transfer device) and a redundant connection point (transfer device) corresponding to the base.

FIG. 5 is a diagram showing an example of connection point information stored in the connection point management DB. As shown in FIG. 5, the connection point management DB 113 stores a transfer device ID (ACT) and a transfer device ID (SBY) that correspond to the area ID of the base and the affiliated NW. Further, a plurality of transfer device IDs (ACT) or transfer device IDs (SBY) may be associated with the area ID and the belonging NW.

The area ID is information that identifies the area of the base. The belonging NW is information that identifies the closed network of the base. Further, each transfer device ID is information that identifies the transfer device. It is also assumed that each record in the connection point management DB 113 has been registered in advance.

In this way, the connection point management DB 113 associates a combination of an area and a closed network with a combination of a normal connection point that connects the closed networks and a redundant connection point that connects the closed networks. Remember information.

For example, the order reception unit 111 receives information that the area ID is "A" and the belonging NW is "Ny" as information on the first base, and receives the area ID as information on the second base. It is assumed that information has been received that the affiliated NW is "A" and the affiliated NW is "Ny".

In this case, the setting processing unit 116 refers to the connection point management DB 113, specifies "40_2" as the transfer device ID (ACT), and specifies "40_1" as the transfer device ID (SBY).

As a result, the setting processing unit 116 generates priority information indicating that the transfer device corresponding to the transfer device ID "40_2" is for normal use, and the transfer device corresponding to transfer device ID "40_1" is for redundant use. Note that a communication path passing through a normal transfer device is given a higher priority than a communication path passing through a redundant transfer device.

Here, for example, as shown in FIG. 6, the order dividing unit 112 divides the setting order into the setting processes shown in (1) to (4) above, and in (3), based on the priority information. Add a role (ACT or SBY), add priority based on the role to (4), and create a tree structure of mutually related setting processes together with information about the base in (5) and save it in the setting management DB 114. do.

Through (3), a process for setting a normal communication path and a redundant communication path is performed. Further, (3) is a configuration that executes a process of setting priority based on whether the communication path is a normal communication path or a redundant communication path.

In this way, the setting processing unit 116 acquires the area to which the two bases belong and the combination of the normal connection point and the redundant connection point corresponding to the closed network from the connection point management DB 113, and config that executes the setting process to set up the communication route that connects between the create.

For example, as shown in FIG. 6, this tree structure includes, from the top to the bottom of the tree, (1) user-related settings → (2) transfer-related settings → (3) interface-related settings → (4) parameters. The connection is made in the following order: setting processing related to the base → (5) setting processing related to the base.

Returning to the explanation of FIG. 3. The setting management DB 114 stores setting orders (see FIG. 6) divided into setting processing units by the order dividing unit 112.

The template DB 115 stores templates for executing each setting process, which are stored in the setting management DB 114. For example, the template DB 115 stores templates for sequentially executing the setting processes (1) to (5) described above.

The setting processing unit 116 executes the setting process indicated in the setting order by reflecting the information indicated in each setting process divided by the order dividing unit 112 into the template for executing the setting process read from the template DB 115. Create a configuration for execution.

For example, the setting processing unit 116 reads out templates corresponding to the setting processes (1) to (5) described above from the template DB 115 from the upper elements of the divided setting process tree (see FIG. 6). Create a configuration by reflecting the changes in order.

For example, as shown in FIG. 7, the setting processing unit 116 performs (1) user registration processing → (2) new transfer surface creation processing → (3) interface creation and tunnel creation processing → (4) Create a config that executes settings in the order of parameter settings and change processing.

Note that the creation of an interface in (3) is, for example, the creation of a tunnel IF or VLAN-IF. Further, the parameter setting and changing process in (4) includes, for example, changing BGP, and changing parameters such as QoS and filters.

Additionally, the configuration processing unit 116 requests the device determination unit 12 to determine the transfer device 40 (configuration device) to which the configuration will be input.

For example, the configuration processing unit 116 outputs to the device determining unit 12 a request to determine the configured device, which includes parameters included in the tunnel configuration order. Note that these parameters include, for example, the user ID, the type of tunnel, the setting amount (for example, the bandwidth used by the tunnel), the device ID or IP address of the transfer device 40 that is a tunnel setting candidate, and the network to which the transfer device 40 is connected. Information, etc. For this parameter, for example, the contents of the setting process read from the setting management DB 114 by the setting processing unit 116 may be used.

When the setting processing unit 116 receives the determination result of the transfer device 40 to which the configuration is to be input from the device determination unit 12, it requests the configuration input unit 117 to input the configuration to the transfer device 40. The configuration input unit 117 inputs the configuration to the transfer device 40 based on a request from the setting processing unit 116.

A method for setting the main route and redundant route will be explained using FIGS. 8 and 9. Here, an example will be described in which the configuration processing unit 116 inputs a configuration based on a configuration order as shown in FIG. 6.

As shown in FIG. 8, the "head office" that is the user's base exists in the area with area ID "A" and is connected to the closed network Ny. The "second branch office" that is the user's base exists in the area with the area ID "B" and is connected to the closed network Nx. Note that the fact that a base is connected to a closed network means that a device such as a server that performs data communication provided at the base is connected to a network outside the base via the closed network.

As mentioned above, the transfer device IDs specified as connection points are "40_1" and "40_2". Further, it is assumed that the transfer device ID of the transfer device 40_1 is “40_1” and the transfer device ID of the transfer device 40_2 is “40_2”.

Therefore, as shown in FIG. 9, there is a main route (ACT) via the transfer device 40_2 and a redundant route (SBY) via the transfer device 40_1 between the base "head office" and the base "second branch". ) is constructed.

In this case, the main route (ACT) has a higher priority, so the closed network Ny with high communication quality is normally used for communication across areas.

With conventional technology, when performing redundant settings such as ACT/SBY, it was possible to manage policy settings such as priority according to user requirements as parameters for each device or each user. However, in that case, it is necessary for the operator to design the network for each user and set which route to set ACT or SBY.

This embodiment reduces the burden on the operator, eliminates the need to set different parameters for each device or user, and simplifies parameter management.

In this embodiment, by using the connection point management DB 113, connection point selection policies can be grouped for each base area and closed network, and connection points can be statically selected. As a result, according to this embodiment, it is possible to efficiently set redundant communication paths.

[Device determination section]
Next, the device determining section 12 will be explained. Note that the transfer device that functions as a connection point is determined by the method described above. The device determining unit 12 determines a transfer device other than the connection point to which the configuration is input. The transfer device other than the connection point is, for example, a transfer device that transfers data only within a closed network.

The device determining unit 12 includes a requirements accepting unit 121, a user requirements DB 122, a real-time information acquiring unit 123, a device information DB 124, and a device determining processor 125. The user requirements DB 122 and the device information DB 124 are installed in a storage unit (not shown) of the controller 10.

First, an overview of the device determining section 12 will be explained using FIG. 10. As shown in FIG. 10, upon receiving a user requirement (communication requirement of a user), the requirement reception unit 121 of the device determination unit 12 stores the user requirement in the user requirement DB 122 (S11).

After S11, when the device determination processing unit 125 receives a request for determining a configuration device including the above parameters from the configuration processing unit 116 (see FIG. 3), the device determination processing unit 125 selects a corresponding candidate device (candidate configuration device A transfer device 40) is selected (S12).

For example, the device determination processing unit 125 selects candidate candidates based on the above parameters, the type of tunnel that each transfer device 40 can support, and the resource status (for example, the upper limit of resources, consumed resources, etc.) shown in the device information DB 124. Select device.

After S12, the real-time information acquisition unit 123 acquires information indicating the communication status of the candidate device selected in S12 from the real-time information DB 20 or the external information collection system 30 (S13).

For example, if the candidate devices are transfer devices #1 to #4 shown in FIG. get.

After S13, the device determination processing unit 125 determines a setting device from among the candidate devices selected in S12, using information indicating the communication status of the candidate devices and user requirements (S14).

For example, the device determination processing unit 125 uses information indicating the communication status of candidate devices indicated by reference numeral 601 and user conditions indicated by reference numeral 602 to select transfer devices that satisfy the user conditions from transfer devices #1 to #4. Device #1 and transfer device #4 are determined as setting devices. Then, the device determination processing unit 125 outputs information about the determined transfer device #1 and transfer device #4 to the setting processing unit 116.

Returning to FIG. 3, the device determining section 12 will be explained in detail. When the requirement reception unit 121 of the device determination unit 12 receives the input of user requirements, the requirement reception unit 121 stores the input in the user requirement DB 122. The user requirements DB 122 stores user requirements. The user requirements are information indicating the communication requirements of each user. For example, the user requirements, as shown by reference numeral 602 in FIG. 10, are information indicating, for each user, the amount of delay (delay time) allowed for the user's communication, the guaranteed bandwidth value (guaranteed bandwidth), etc. .

The real-time information acquisition unit 123 acquires information indicating the communication status between each transfer device 40. The information indicating the communication status between each transfer device 40 is, for example, as shown by reference numeral 601 in FIG. 10, information indicating the delay time, traffic amount, etc. for each section connecting the transfer devices 40. The information is obtained from each transfer device 40 in real time, for example.

The device information DB 124 stores device information of each transfer device 40. The device information is information indicating the allocated resource amount and resource consumption amount of the transfer device 40.

For example, as shown in FIG. 11, the device information is information indicating the device ID, model, OS (Operating System) version, compatible tunnel type, resource upper limit, consumed resources, etc. of the transfer device 40. .

Note that the resource upper limit is, for example, information indicating the upper limit of the number of tunnel users, the upper limit of the number of tunnels, etc. that can be set in the transfer device 40. Further, the amount of consumed resources is information indicating, for example, the number of tunnel users, the number of tunnels, etc. set in the transfer device 40.

Returning to the explanation of FIG. 3. The device determination processing section 125 determines the setting device based on the setting device determination request output from the setting processing section 116. This determination request from the configuration device includes parameters included in the tunnel configuration order. For this parameter, for example, the contents read out from the setting management DB 114 by the setting processing unit 116 and shown in each setting process are used.

As described above, the parameters include, for example, the user ID, the type of tunnel, the setting amount, the device ID or IP address of the transfer device 40 that is a tunnel setting candidate, or the network information of the connection destination.

For example, the device determination processing unit 125 determines the user ID included in the above parameters, the transfer device 40 that is a tunnel setting candidate, and the allocated resource amount and consumed resource amount of each transfer device 40 indicated in the device information of the device information DB 124. Based on the information indicating the communication status between each transfer device 40 collected by the real-time information acquisition unit 123, select a transfer device 40 that satisfies the communication requirements of the user from among the transfer devices 40 that are candidates for setting the tunnel. , to be determined as the setting device. Then, the device determination processing section 125 outputs the transfer device 40 determined as the setting device to the setting processing section 116.

According to such a controller 10, a tunnel setting order is divided into a plurality of setting processes and a config is created using a template, so the config can be easily created. Further, the controller 10 stores the divided setting processing in the setting management DB 114 in a tree structure, for example. This makes it easier to manage the configuration and make partial changes and extensions.

Further, the controller 10 uses the communication status between each transfer device 40 to determine a transfer device 40 that satisfies the user's communication requirements as a configuration input destination. Thereby, the controller 10 can flexibly determine the transfer device 40 to which the tunnel is to be set, depending on the communication status between the respective transfer devices 40.

[Example of processing procedure]
Next, an example of the processing procedure of the controller 10 will be described using FIG. 12. For example, first, the order receiving unit 111 of the controller 10 receives a tunnel setting order from a higher-level Ops (S101). Next, the order dividing unit 112 divides the setting order received in S101 into a plurality of setting processes (S102: dividing the setting order). Then, the order dividing unit 112 stores the divided setting processing in the setting management DB 114 (S103).

After S103, the setting processing unit 116 reads the setting process from the setting management DB 114 (S104). Furthermore, the configuration processing unit 116 requests the device determination unit 12 to determine the transfer device 40 (configuration device) to which the configuration will be input (S105).

After S105, the device determining unit 12 determines the transfer device 40 to which the configuration will be input based on the request (S106). Details of the process of S106 will be described later. Then, the setting processing unit 116 uses the template in the template DB 115 to create a configuration that reflects the setting process read out in S104 (S107). Thereafter, the configuration input unit 117 inputs the configuration created in S107 to the transfer device 40 determined in S106 (S108).

Here, for the transfer device functioning as a connection point, the setting processing unit 116 additionally performs the process shown in FIG. 13 in step S103.

As shown in FIG. 13, the setting processing unit 116 first reads the area and closed network information of the two bases (S201). Next, the setting processing unit 116 refers to the connection point management DB 113 and specifies the normal connection point and redundant transfer device corresponding to the area and closed network (S202). Further, in S104, the setting processing unit 116 stores information identifying the transfer device specified as the connection point in the setting management DB 114.

In S106, the device determining unit 12 can determine the transfer device functioning as the connection point as the configuration input destination based on the information read from the configuration management DB 114.

Next, using FIG. 14, S106 in FIG. 12 will be explained in detail regarding a transfer device that does not function as a connection point. First, the device determination processing section 125 of the device determination section 12 receives a request to determine a setting device (S121). As described above, this configuration device determination request includes parameters included in the tunnel configuration order (for example, user ID, tunnel type, configuration amount, device ID or IP address of the transfer device 40 that is a tunnel configuration candidate, or connection destination network information, etc.).

After S121, the device determination processing unit 125 obtains the device information of the transfer device 40 that is a tunnel configuration candidate included in the parameters of the configuration device determination request from the device information DB 124 (S122). Then, the device determination processing unit 125 determines, based on the acquired device information, whether or not each transfer device 40 that is a tunnel setting candidate is compatible with the type of tunnel indicated by the above parameters (S123: tunnel) and whether or not there is free space in the resource is determined (S124).

For example, the device determination processing unit 125 selects one transfer device 40 as a tunnel setting candidate, and determines whether it is compatible with the type of tunnel indicated by the above parameters (S123: Is it a compatible type of tunnel)? It is determined whether there is a free resource (S124). Then, if there is a transfer device 40 that is an unselected setting candidate (S125: Are there other candidates → Yes), the device determination processing unit 125 sends the transfer device 40 of the unselected setting candidate device in S123 and The process of S124 is executed.

On the other hand, if there is no transfer device 40 that is an unselected setting candidate (S125: Are there other candidates → No), the device determination processing unit 125 determines whether there is a transfer device 40 that satisfies the requirements indicated by the above parameters. is determined (S126). Here, if the device determination processing section 125 determines that there is no transfer device 40 that satisfies the requirements (S126→No), it returns NG to the setting processing section 116 (S137).

On the other hand, if the device determination processing unit 125 determines that there is a transfer device 40 (candidate device) that satisfies the requirements indicated by the above parameters (S126 → Yes), the device determination processing unit 125 informs the real-time information acquisition unit 123 of the communication status of the candidate device. (S131: Information request).

After S131, if the real-time information DB 20 has information indicating the communication status of the candidate device (S132: Is the information in the DB?→Yes), the real-time information acquisition unit 123 outputs the information to the device determination processing unit 125. do. Thereby, the device determination processing unit 125 receives information indicating the communication status of the candidate device (S134).

On the other hand, if the information indicating the communication status of the candidate device is not in the real-time information DB 20 (S132: Is the information in the DB → No), the real-time information acquisition unit 123 requests the external information collection system 30 to acquire the information. A request is made (S133). When the real-time information acquisition unit 123 acquires the information from the external information collection system 30, it outputs it to the device determination processing unit 125. Thereby, the device determination processing unit 125 receives information indicating the communication status of the candidate device (S134).

After S134, the device determination processing unit 125 determines whether there is a candidate device that satisfies the user requirements by comparing the information received in S134 with the user requirements (S135). Here, if the device determination processing unit 125 determines that there is a candidate device that satisfies the user requirements (S135 → Yes), the configuration processing unit 116 (S136).

On the other hand, if the device determination processing unit 125 determines that there is no candidate device that satisfies the user requirements (S135→No), it returns NG to the setting processing unit 116 (S137).

Next, an example of the processing procedure of the device determining unit 12 will be described using the sequence diagram shown in FIG. 15. For example, when the requirement reception unit 121 of the device determination unit 12 receives input of user requirements from a higher-level Ops (S141), the requirements acceptance unit 121 registers the user requirements in the user requirement DB 122 (S142).

After S142, the device determination processing section 125 receives a request for determining the tunnel setting device from the setting processing section 116 (S143). As described above, this configuration device determination request includes parameters included in the configuration order (for example, user ID, tunnel type, list of transfer devices 40 that are tunnel configuration candidates (device ID, IP address, etc.), etc.).

After S143, the device determination processing unit 125 acquires the device information of the transfer device 40 that is a setting candidate included in the above parameters from the device information DB 124 (S144). Then, the device determination processing unit 125 selects a candidate device using the device information acquired in S144 (S145).

For example, based on the device information acquired in S144, the device determination processing unit 125 selects, from the transfer device 40 that is a setting candidate, a transfer device that is capable of supporting the type of tunnel indicated by the above parameters and that has free resources. 40 is selected as a candidate device.

After S145, the device determination processing unit 125 requests the real-time information acquisition unit 123 for information indicating the communication status of the candidate device selected in S145 (S146: information request). Then, the real-time information acquisition unit 123 acquires information indicating the communication status of the candidate device based on the request (S147). For example, the real-time information acquisition unit 123 first searches the real-time information DB 20 for information indicating the communication status of the candidate device. Here, if there is no information in the real-time information DB 20, the real-time information acquisition unit 123 requests the external information collection system 30 to acquire information indicating the communication status of the candidate device, and requests the external information collection system 30 to acquire information indicating the communication status of the candidate device. get.

After S147, the real-time information acquisition unit 123 returns information to the device determination processing unit 125 (S148). For example, the real-time information acquisition unit 123 outputs information indicating the communication status of the candidate device acquired in S147 to the device determination processing unit 125.

After S148, the device determination processing unit 125 acquires the user requirements corresponding to the user ID included in the above parameters from the user requirement DB 122 (S149). Then, the device determination processing unit 125 compares the answer obtained in S148 (information indicating the communication status of the candidate device) with the user requirements obtained in S149, and determines the candidate device that satisfies the user requirements as the setting device ( S150: Determination of setting device). Then, the device determination processing section 125 sends the device information of the setting device determined in S150 to the setting processing section 116 (S151).

Next, using the sequence diagram shown in FIG. 16, the processing after the setting processing unit 116 receives the response of the device information of the setting device in S151 of FIG. 15 will be described.

Based on the device information of the setting device (for example, device ID, IP address, etc. of the setting device) received from the device determination processing section 125, the setting processing section 116 determines whether the setting device is a connection point from the connection point management DB 113. The base area and closed network are read (S161). The setting processing unit 116 also retrieves the device information of the setting device from the device information DB 124 (for example, the (S162). Next, the setting processing unit 116 reads a template from the template DB 115 (S163). Then, the setting processing unit 116 inputs each setting process stored in the setting management DB 114 and the device information of the setting device read in S162 into the template read in S163 to the setting device. A configuration is created (S164).

After S164, the setting processing unit 116 requests the configuration input unit 117 to input the configuration created in S164 (S165: configuration request). Then, the config input unit 117 inputs the config created in S164 to the transfer device 40 (for example, transfer device #1), which is a configuration setting device, based on the input request (S166: config input). Thereafter, when the configuration processing unit 116 receives the configuration input result notification (S167), the configuration processing unit 116 updates the device information in the device information DB 124 based on the result notification (S168). For example, the setting processing unit 116 updates the value of consumed resources in the device information (see FIG. 11) regarding the transfer device 40 to which the configuration is input.

According to such a controller 10, a tunnel setting order is divided into a plurality of setting processes and a config is created using a template, so the config can be easily created. Further, the controller 10 stores the divided setting processing in the setting management DB 114 in a tree structure, for example. This makes it easier to manage the configuration and make partial changes and extensions.

Further, the controller 10 uses the communication status between each transfer device 40 to determine a transfer device 40 that satisfies the user's communication requirements as a configuration input destination. Thereby, the controller 10 can flexibly determine the transfer device 40 to which the tunnel is to be set, depending on the communication status between each transfer device 40 .

[System configuration, etc.]
Further, each component of each part shown in the drawings is functionally conceptual, and does not necessarily need to be physically configured as shown in the drawings. In other words, the specific form of distributing and integrating each device is not limited to what is shown in the diagram, and all or part of the devices can be functionally or physically distributed or integrated in arbitrary units depending on various loads, usage conditions, etc. Can be integrated and configured. Furthermore, all or any part of each processing function performed by each device may be realized by a CPU and a program executed by the CPU, or may be realized as hardware using wired logic.

Further, among the processes described in the embodiments described above, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed manually. All or part of this can also be performed automatically using known methods. In addition, information including processing procedures, control procedures, specific names, and various data and parameters shown in the above documents and drawings may be changed arbitrarily, unless otherwise specified.

[program]
The controller 10 described above can be implemented by installing a program on a desired computer as packaged software or online software. For example, by causing the information processing device to execute the above program, the information processing device can be made to function as the controller 10. The information processing device referred to here includes a desktop or notebook personal computer. In addition, information processing devices include mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone System), as well as terminals such as PDAs (Personal Digital Assistants).

The controller 10 can also be implemented as a server device that uses a terminal device used by a user as a client and provides services related to the above processing to the client. In this case, the server device may be implemented as a web server, or may be implemented as a cloud that provides services related to the above processing through outsourcing.

FIG. 17 is a diagram showing an example of a computer that executes a configuration input program. Computer 1000 includes, for example, a memory 1010 and a CPU 1020. The computer 1000 also includes a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These parts are connected by a bus 1080.

The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012. The ROM 1011 stores, for example, a boot program such as BIOS (Basic Input Output System). Hard disk drive interface 1030 is connected to hard disk drive 1090. Disk drive interface 1040 is connected to disk drive 1100. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into disk drive 1100. Serial port interface 1050 is connected to, for example, mouse 1110 and keyboard 1120. Video adapter 1060 is connected to display 1130, for example.

The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, a program that defines each process executed by the controller 10 described above is implemented as a program module 1093 in which computer-executable code is written. Program module 1093 is stored in hard disk drive 1090, for example. For example, a program module 1093 for executing processing similar to the functional configuration of the controller 10 is stored in the hard disk drive 1090. Note that the hard disk drive 1090 may be replaced by an SSD (Solid State Drive).

Furthermore, data used in the processing of each embodiment described above is stored as program data 1094 in, for example, the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads out the program module 1093 and program data 1094 stored in the memory 1010 and the hard disk drive 1090 to the RAM 1012 and executes them as necessary.

Note that the program module 1093 and the program data 1094 are not limited to being stored in the hard disk drive 1090, but may be stored in a removable storage medium, for example, and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and the program data 1094 may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). The program module 1093 and program data 1094 may then be read by the CPU 1020 from another computer via the network interface 1070.

1 System 10 Controller 11 Setting section 12 Device determining section 20 Real-time information DB
30 External information collection system 40 Transfer device 111 Order reception section 112 Order division section 113 Connection point management DB
114 Settings management DB
115 Template DB
116 Setting processing unit 117 Configuration input unit 121 Requirement reception unit 122 User requirements DB
123 Real-time information acquisition unit 124 Device information DB

Claims (6)

a storage unit that stores information associating combinations of areas and closed networks with combinations of normal connection points that connect the closed networks and redundant connection points that connect the closed networks;
A communication path that connects the two bases by acquiring a combination of a normal connection point and a redundant connection point corresponding to an area to which the two bases belong and a closed network from the storage unit, a setting processing unit that creates a configuration that executes a setting process for setting a normal communication path that passes through the normal connection point and a redundant communication path that passes through the redundant connection point;
A config input device comprising: a config input section that inputs the config to a transfer device included in the normal communication path and the redundant connection path. an order reception unit that accepts tunnel setting orders;
The tunnel configuration order is processed through a first configuration process related to user configuration registration, a second configuration process related to the transfer surface of the tunnel, and a configuration process related to the interface of each transfer device used in the tunnel of the transfer surface, an order dividing unit that divides into a third setting process including a process of setting the normal communication route and the redundant communication route, and a fourth setting process regarding parameters to be set in the interface, and stores the results in a storage unit; and,
It further has
The configuration processing unit creates a configuration for executing the tunnel configuration process indicated in the configuration order by reflecting information indicated in each of the configuration processes in a template prepared for each configuration process,
2. The configuration input device according to claim 1, wherein the configuration input unit inputs the configuration to a transfer device to which the tunnel is set. 1. The setting processing unit creates a configuration for executing processing for setting priorities based on whether the communication path is a normal communication path or a redundant communication path. Config input device described in . The configuration input device according to claim 1, wherein the setting processing unit further stores information regarding the two bases in the storage unit. A config input method executed by a config input device, the method comprising:
From the storage unit that stores information that associates combinations of areas and closed networks with combinations of normal connection points that connect the closed networks and redundant connection points that connect the closed networks, two Obtain a combination of a normal connection point and a redundant connection point corresponding to the area and closed network to which the base belongs, and create a communication path that connects the two bases, and select the normal connection point. a setting processing step of creating a config that executes setting processing for setting a normal communication route to be passed through and a redundant communication route to be passed through the redundant connection point;
A config input method comprising: a config input step of inputting the config to a transfer device included in the normal communication path and the redundant connection path. From the storage unit that stores information that associates combinations of areas and closed networks with combinations of normal connection points that connect the closed networks and redundant connection points that connect the closed networks, two Obtain a combination of a normal connection point and a redundant connection point corresponding to the area and closed network to which the base belongs, and create a communication path that connects the two bases, and select the normal connection point. a setting processing step of creating a config that executes setting processing for setting a normal communication route to be passed through and a redundant communication route to be passed through the redundant connection point;
A configuration input program that causes a computer to execute a configuration input step of inputting the configuration to a transfer device included in the normal communication path and the redundant connection path.

Images